![]() Anyway, hope Samsung can fix this in the S24 series. Probably because the plastic back conducts less heat than glass back though. I used the S21 before and it never seemed to get hot. ![]() I've used many Galaxy S phones and it's a bit disappointing to see that the heat problem is still present. Guess the Snapdragon Gen 2 chipset is really efficient, especially with the increased clock speed tailored to S23 lineup. I'm surprised that the S23 has so much better battery life compared to the S22 with just a 200mah difference. Since k zoom was last galaxy to have optical zoom. Since samsung likes to copy xperia so much, should have use periscope with zoom lens as well. While xperia can use with any %, also for other apps not just games.Ĭopied the sensor with DRAM but did not take advantage of its capabilities.Ĭopied it 960fps, but with lower quality and zero control over it.Ĭopied the "stop charging after 80% to preserve battery".Ĭopied the "decrease charging speed to finish only when user wakes up".Ĭreated second photo app with more controls, still lack tons of stuff compared to xperia photo pro. You cant use it if battery is equal or below 20%. " To put it into simpler terms, once the feature is enabled, plugging in a charger into the phone will bypass charging of the battery and directly provide power to the processor, unless the phone has a 20% charge or lower." moreFrom phone arena (also, the menu where you turn on this fuction says it as well). Yes S23 is equally good/better but paying a hafty amount for 10% better battery is too much i think.but if you are not bothered about S23's higher price & don't want to compromise on anything then S23 is good to go.Īnonymous, I wonder where you got the information that the battery needs to be above 20% for this feature. Now S23 is literally best compact android phone you can get.īut since S22 is available for good discounts than S23 doesn't make a strong case for itself. So even if S23 only improves on battery life than its actually solves biggest problem with S22. OneUI is good but the huge number of pre-installed apps for everything is annoying.Samsung really needs to decrease pre-installed bloatware/apps or atleast give option to untick those while setup. Small size is very handy & lightweight also. Eventually, builds would hang or fail with OOM errors.I can say its near perfect phone.Everyrhing works smoothly except battery life.actually its not that bad as expected from 3700mAh phone but still noticeably lower.With power saving mode you can expect 6.30-7 hours SOT.Ĭameras are really good only thing i didn't like was smearing of fine details on 1:1 magnification.ĨG1 is very fast & with OneUI 5,not phone doesn't heat that much.ĭisplay is good & bright,Speakers are moderately loud with pleasing sound quality. ![]() What I would expect is that if there was a memory leak, the build would fill up the heap over time and permanently remain high. Are there multiple JVMs running (you can check with jps) that happen to be shutdown when you kill the daemon? The JVM is limited to ~3GB in your example, so it should not be able to consume more than that. I don't believe that the increasing class count alone would account for system wide troubles. The number of classes loaded does seem high in your case, but I can't tell if they would eventually be GC'd from the snapshot alone. Gradle needs to keep around classes between builds because that keeps them warmed up in the JVM and subsequent builds can benefit from that. Which version of the JDK are you using? Are you seeing high GC time or OutOfMemory errors? Unless you're seeing build failures with your current settings, I don't think there's necessarily a problem. Hi don't see anything too concerning in the snapshot you provided, although I do see that the number of classes loaded is going up a lot. =-Xmx3096m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8 Link for the JProfile snapshot of the gradle process while making 3 or 4 builds with minor changes to the project: Your Environment RAM usage is always increasing in an alarming rate, forcing the system to use the swap partion and making it unresponsive until the java process is killed Steps to Reproduce No incremental RAM usage on every build Current Behavior I used JProfile to check what happens when making some builds on the same deamon, and I believe that the issue is that loaded classes are not disposed after the build finishes, and every new build after that adds more classes to the process. Making sequential builds without killing gradle deamon leads to lots of memory consumed that is only released by killing the java process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |