Related
Which kernel do you guys prefer? Gladdos is awesome because I love its app with sound options . App seems to also work with Franco kernel though, but as far as reliability and performance goes, which do you guys like more?
Sent from my Galaxy Nexus using XDA
Both are very stable. Use the one that you like more. Franco also has an app.
Sent from my GT-P3113 using xda premium
Personally I'm a big fan of the CM9 kernel. I use CMPlus by Cheekybutt simply because headphones sound like crap without Ezekeel's high performance audio mod.
I use Glados. Its outstanding. I find I can oc higher much more reliably. I use 1.6 for everyday usage which is not even seen as an option on many other kernels. on a lot of other kernels, Franco included I can't run higher than 1.35 CPU and 384GPU. I run 1.6 and 512 with glados. And the app kicks ass with tons of adjustable features!
M3drvr said:
I use Glados. Its outstanding. I find I can oc higher much more reliably. I use 1.6 for everyday usage which is not even seen as an option on many other kernels. on a lot of other kernels, Franco included I can't run higher than 1.35 CPU and 384GPU. I run 1.6 and 512 with glados. And the app kicks ass with tons of adjustable features!
Click to expand...
Click to collapse
512 GPU doesn't make a difference.. neither really does OC or UC
"Long is the way, and hard, that out of hell leads up to light."
joshnichols189 said:
512 GPU doesn't make a difference.. neither really does OC or UC
"Long is the way, and hard, that out of hell leads up to light."
Click to expand...
Click to collapse
I heavily beg to differ. I notice a difference immediately. Everything is smoother when I do oc.
Just tried ocing the gpu in glados kernel and wow, definitely a difference! Now, at 504mhz, does it effect our battery life in a major way?
Sent from my Galaxy Nexus using XDA
Glados with the wheatley gov.
Awesomesauce.
Sent from my Galaxy Nexus using XDA
afive720 said:
Just tried ocing the gpu in glados kernel and wow, definitely a difference! Now, at 504mhz, does it effect our battery life in a major way?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
From what I've heard (not tried), the gain from OC'ing is minimal and battery consumption increase is quite big.
Swyped on my CM9 Galaxy Nexus
why do you even need to overclock? To me battery life is most essential factor and I have yet to come across a kernel that can give me satisfactory results, stock included. The screen on this thing is beautiful but eats battery like no other. I can't wait for Verizon to have a larger Note like device so we can have a larger battery.
The battery life on this phone is amazing for a Verizon LTE phone. Before I activated the phone I played with it around the house for about a week (had to take care of some things before I quit using the iPhone). I went 25 hours with 3 hours of display time. Mind you this was all on WiFi and since it wasn't activated there was no talk time. LTE is the battery destroyer not so much the screen. I have never ran this phone stock, so I have no benchmark to compare it too, but the charging times on the Franco kernel are insane. Went up 65% in 1 hour over a car charger.
I'll have to check out the Gladdos kernel.
what car charger do you have and what apps were you running? I have a 1.2amp usb charger from monoprice and with maps and pandora on it charges for a bit before it gets too hot and switches to "not charging" to not overheat. Then it stays at about the same battery level, give or take a few %
Something similar to this....http://www.newegg.com/Product/Product.aspx?Item=9SIA07Y02A5396. Since it's dual port I'm sure it has a bigger fuse.
M3drvr said:
I heavily beg to differ. I notice a difference immediately. Everything is smoother when I do oc.
Click to expand...
Click to collapse
I suggest reading through the Franco.Kernel thread.. everything above 384 is minimal at best.
"Long is the way, and hard, that out of hell leads up to light."
ashish8 said:
The battery life on this phone is amazing for a Verizon LTE phone. Before I activated the phone I played with it around the house for about a week (had to take care of some things before I quit using the iPhone). I went 25 hours with 3 hours of display time. Mind you this was all on WiFi and since it wasn't activated there was no talk time. LTE is the battery destroyer not so much the screen. I have never ran this phone stock, so I have no benchmark to compare it too, but the charging times on the Franco kernel are insane. Went up 65% in 1 hour over a car charger.
I'll have to check out the Gladdos kernel.
Click to expand...
Click to collapse
which brings me back to the another comment I made in another thread, LTE speeds for a phone is unnecessary. Lose battery life and pay up the wazooo if you don't have unlimited data (soon all of us)? Just a way for the big red to justify charging more. #switchingoffLTE
joshnichols189 said:
I suggest reading through the Franco.Kernel thread.. everything above 384 is minimal at best.
"Long is the way, and hard, that out of hell leads up to light."
Click to expand...
Click to collapse
Then why offer a 512oc if its nothing? Reality is, the phone is noticeably smoother with it. And virtually no hit on battery life. I'm still getting high 3 hours screen on time and 20+ hours battery life. I'll take the much smoother experience for minimal battery life hit.
M3drvr said:
Then why offer a 512oc if its nothing? Reality is, the phone is noticeably smoother with it. And virtually no hit on battery life. I'm still getting high 3 hours screen on time and 20+ hours battery life. I'll take the much smoother experience for minimal battery life hit.
Click to expand...
Click to collapse
Much smoother? Exaggerate much??
And as for battery life, I get 5hrs screen on with 384.
Games run smoothly, UI is smooth, what more do you need.
If you can run 512 then why not but it does not make that much of a difference.
I have used both and I find no difference.
nodstuff said:
Much smoother? Exaggerate much??
And as for battery life, I get 5hrs screen on with 384.
Games run smoothly, UI is smooth, what more do you need.
If you can run 512 then why not but it does not make that much of a difference.
I have used both and I find no difference.
Click to expand...
Click to collapse
Well, for me on my phone, its a major difference between 384 and 512. And I've seen several people comment that it is a difference on their phone too. Web pages scroll is jerky on 384 for me, and with 512 its perfectly smooth. I've never ever gotten 5 hours screen on time with any setting I've ever chosen on my phone so thats not even in the question. Max ever was 4:30 screen on, that was with screen brightness lowest possible, entire time with wifi, which is not even in the question for me on a normal day. Normal for me is high 3's.
Anyways, we all know none of these phones are the same. They react differently to different settings. All I know, is on my phone, 512 is by far smoother than 384. And at a 40% OC of the CPU (1680-1700mhz) the phone is also noticeably faster. And actually, on my old Galaxy S, 1400 was the magic number i needed for things to actually FEEL and LOOK faster, which was 40% more. Anything less than that, I couldn't notice a boost. Thats just my thought on my phone.
Its very easy to see the difference in scrolling smoothness between 512gpu and 384gpu.
All you have to do is go to theverge.com mobile site and just scroll up and down using the stock browser.
The difference is very noticeable.
Glados 1.34 seems to resolve data drop issue, so I've stuck with it for now.
Sent from my Galaxy Nexus
Is there a way to reduce it? My phone slows to the pace of a sloth far too frequently and it seems correlated with temp.
I'm assuming that's the cause because when I look at the CPUs in CPUz the last two go down to 633MHz when things are getting slow. Also seems worse with a case but could be my confirmation bias. This is particularly apparent with the camera, Maps, and when coming out of doze.
Is there a more conclusive way to figure out what is causing my Nexus 5X's occasionally brutal performance?
Sent from my Nexus 5X using Tapatalk
Well, what exactly are you doing with your phone that's causing it to throttle itself? I think with a stock kernel the phone begins to throttle and eventually shut off the Big cluster at 36 or 37 degrees Celsius (someone correct me if I'm wrong). If you flashed a custom kernel, most here have had that limit raised to 46C.
Last weekend I used my phone quite a bit for strenuous tasks including Navigation, Google Maps, lots and lots of pictures and 1080P video. The phone got noticeably warmer, but when I checked my kernel management app, the CPU temperature wasn't even close to the throttle temperature. Unless you're gaming or constantly benchmarking your phone this really shouldn't be a problem. Especially when coming out of Doze. The phone doesn't immediately enter Doze, it waits a while and there are factors that play into its decision to even enter doze in the first place (like laying on a flat surface for X amount of time). So when a phone is exiting Doze because of your input (turning the screen on) the CPU should be quite cool (maybe 22+ degrees). There's no thermal throttling there. The Big cluster shuts off when the screen is off for the sake of battery life, so maybe the lag that you're experiencing stems from the lack of the Big cluster being on for the first second or so when waking the phone back up.
I'll agree that the SD808 isn't a stellar chip; maybe even embarrassing. It's not blisteringly fast, but it certainly isn't slow. There are ways to speed up performance and improve battery life at the same time, which I'm sure you'd appreciate. Unfortunately you have not specified if you're running a custom ROM or kernel, so that's pretty much all the advice and information I can give you right now. But, if you're currently running stock, I'd highly recommend you unlock your bootloader and try out some of the custom (and more lightweight) ROMs that this community has to offer as well as some great kernels. That should make a noticeable difference right off the bat. Then you can dive into the nitty gritty details of tweaking and whatnot if you desire. Check out the links in my signature as a starting point. If you're looking for optimization and speed (like I do) then you'll be impressed.
Thanks for your reply.
I switched to ElementalX about a week ago and it may be a bit better now but it's hard to tell. I've also been using a spigen slim case, maybe that is causing heat to accumulate too.
I don't game. My usage is Maps, Facebook, Snapchat, camera, chrome, hangouts, Spotify, and textra.
I use greenify and amplify as well on xposed. Disabling xposed doesn't seem to make a difference.
Can you confirm that ElementalX throttles at 46C and stock at 36C?
I'm interested in your recommendations. When running geekbench it takes about 9 minutes for things to really slow down.
Sent from my Nexus 5X using Tapatalk
If you search the ElementalX thread you can see that the developer, Flar2, was getting very frustrated with the thermal throttling on this device (others were too, as well). You can read through the progression and, eventually, the decision to apply a "thermal fix" or raise the thermal throttling limit. The threshold is 46C now. Confirmed. The stock thermal throttle threshold is 10 degrees less than that from what I've read. I also remember reading that Franco did a fair amount of research into the throttling issue and found that the CPU was capable of going over 50C with no issues (but aren't recommended), so the limit in place now by the ElementalX kernel is a safe one that shouldn't be exceeded. He probably didn't make it any higher so he wouldn't be found liable by any users if they overheat or damage their phones.
I have no experience with xposed and everytime there's a compatibility issue, hard reboots, etc. it's always because of Xposed. So.. Yeah.
I also do not use any tweaking apps that supposedly save battery or whatever. I let the operating system take care of that. I do use the L-Speed app (again, in my signature) to disable certain things like debug logs and what not to speed things up slightly. Again, I highly recommend trying Ubermallow and Phasma Kernel as those have been my choice, after trying many others, for some time now. Also, I'd look into the interactive governor tweaks after you've settled on a ROM and kernel combination that you like. That's where you can fine tune the way the CPU governor on the phone behaves and can really make a difference in battery life and fluidity of the device.
Lastly, a case can make a difference with cooling but I've never really found it to be an issue. Maybe I'm just not hard on my phone enough.
ryanwalexander said:
Is there a way to reduce it? My phone slows to the pace of a sloth far too frequently and it seems correlated with temp.
I'm assuming that's the cause because when I look at the CPUs in CPUz the last two go down to 633MHz when things are getting slow. Also seems worse with a case but could be my confirmation bias. This is particularly apparent with the camera, Maps, and when coming out of doze.
Is there a more conclusive way to figure out what is causing my Nexus 5X's occasionally brutal performance?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
A member on the 6p forum came up with a hard mod that does this with a special thermal paste better then stock . Requires tearing apart the device though ...so its risky but his results looked promising
Sent from my Nexus 6P using XDA Free mobile app
Google just agreed to take back my device so I only have a few days to try things and make my decision on whether to keep the phone or not.
Thank you for your thoughtful responses and suggestions.
Since I started using the phone outside of the case it actually seems much better.
Regarding the extreme slowness coming out of doze, it only occurs when in doze for a long time. Presumably because the phone tries to catch up on all the sync activity that's been paused for the last 12h or so.
Sent from my Nexus 5X using Tapatalk
I think I'll try your suggestions and remove greenify, amplify, and xposed to see if things improve. I do agree that the system should be managing those things.
Sent from my Nexus 5X using Tapatalk
Yeah, give it a few days. There are many ways to combat the throttling. Got my phone to 41C today while using it out in the sun. The Big cluster is limited to 633MHz at 36C and shut off at 41CC. The 46C built into the kernel is most likely for the LITTLE cluster to start getting throttled. Check the attached pics below.
Thanks. Btw what ROM and app is that?
Sent from my Nexus 5X using Tapatalk
ryanwalexander said:
Thanks. Btw what ROM and app is that?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
ROM and Kernel are in my signature. The app for managing the kernel is Elementalx Kernel Manager and the app to add CPU usage overlays and stuff is called Trepn Profiler.
Sounds like the opposite to me, the phone might be slow because of software on the device not playing nice which causes the SoC to work over time (normal computing + rogue app computing) and can cause the device to over heat and throttle.
There's no reason the device should be slow after a period of doze. That tells me the device is having software caused slowdowns that are not related to thermal throttling.
It takes roughly 12 minutes of 100% sustained load (only synthetic benchmarks) to throttle the 2x A57 cluster, and I've never seen the 4x A53 cluster throttle under any conditions including hours of heavy gaming they stay at 1.4Ghz at all times.
bblzd said:
Sounds like the opposite to me, the phone might be slow because of software on the device not playing nice which causes the SoC to work over time (normal computing + rogue app computing) and can cause the device to over heat and throttle.
There's no reason the device should be slow after a period of doze. That tells me the device is having software caused slowdowns that are not related to thermal throttling.
It takes roughly 12 minutes of 100% sustained load (only synthetic benchmarks) to throttle the 2x A57 cluster, and I've never seen the 4x A53 cluster throttle under any conditions including hours of heavy gaming they stay at 1.4Ghz at all times.
Click to expand...
Click to collapse
Yesterday I was using GPS to drive and Spotify was streaming. The phone got really hot and unresponsive and Spotify began to stutter. Was unable to even launch textra to text someone.
This of course only started maybe 10m into the drive. The phone is fine while cold.
Maybe I have a defective device but my benchmark stress tests give similar results to other people.
Sent from my Nexus 5X using Tapatalk
ryanwalexander said:
Yesterday I was using GPS to drive and Spotify was streaming. The phone got really hot and unresponsive and Spotify began to stutter. Was unable to even launch textra to text someone.
This of course only started maybe 10m into the drive. The phone is fine while cold.
Maybe I have a defective device but my benchmark stress tests give similar results to other people.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
this is consistent with my experience. GPS and spotify (actually almost any app used concurrently with spotify) will cause the phone to have horrible lag.
also, don't text and drive
Interestingly, today when the phone was on battery saver it seemed much faster. Maybe more throttling could help things more than less?
Of course not exactly faster, but more consistent and no unbearable lagging.
Yesterday I flashed the stock firmware files other than user data. Unfortunately I lost root and it seems like I now need to reformat data to get TWRP going again but until then I'm fully stock. Does anyone know a way around that?
I haven't done enough testing to be sure but things seem to be running more smoothly for now than they did with root and ElementalX 1.06. However just writing this i can feel the phone heating up and becoming less responsive. The bottom 2 cores are offline with SoC at 36C and CPU at 56C when I switch to devcheck to check. Other 4 cores at 1440MHz.
ideaman924 said:
I've been having issues with thermal as well. Installed ElementalX along with the governer tweaks GhostPepper profile. When charging (this makes the device really hot) music begins to stutter, coming out of Viper4Android.
When not charging, slow accumulation of heat makes music stutter, same software used. Go figure. Maybe V4A is too demanding on the 808 chip, but I fear if this doesn't cut it, then I'll have to switch phones the next chance I get.
Oddly, this happens when screen is off - the music stutterings. I've thought about Doze and battery saving apps, and have disabled Doze for V4A through the battery optimize pane.
The phone constantly loses battery, around 2~5% an hour, I know thats not too much but my previous phone lost about 1% every three hours. This was a Note 3 Neo by the way. Installing Xposed and Amplify, Greenify and PowerNap should help, but I've had stability issues when using xposed. Maybe later.
Oh, and one last thing. My phone's thermal limit is set to 55 degrees Celsius, but it still feels like it throttles at around 39 or so. Maybe EX Kernel Manager isn't saving the changes, but either way... It throttles too much!
Click to expand...
Click to collapse
That could be because of the custom software and CPU tweaks or your V4A installation. Using those settings always has the potential to cause issues and I would troubleshoot there first.
Minimum CPU performance with stock settings is 4x A53 cores at 1.44Ghz which is still fast. If you've ever use one of the more recent Moto G devices you'd know it doesn't stutter playing music when it's cold and neither does this device when it's hot.
Sent from my Nexus 5X using XDA-Developers mobile app
Setting the throttling temp limit to high will decrease performance, see here for details:
http://forum.xda-developers.com/nexus-5x/general/thermal-throttling-temp-performance-test-t3388559
Alcolawl said:
Yeah, give it a few days. There are many ways to combat the throttling. Got my phone to 41C today while using it out in the sun. The Big cluster is limited to 633MHz at 36C and shut off at 41CC. The 46C built into the kernel is most likely for the LITTLE cluster to start getting throttled. Check the attached pics below.
Click to expand...
Click to collapse
Is this based on battery temperature or cpu temperature?
leo.best1398 said:
Is this based on battery temperature or cpu temperature?
Click to expand...
Click to collapse
CPU temperature but I beleive the phone also has ways of combating high battery temps as well.
Alcolawl said:
CPU temperature but I beleive the phone also has ways of combating high battery temps as well.
Click to expand...
Click to collapse
If its cpu temp then no wonder it's always throttling the cpu is nearly always above 40°c.
What do you mean ''combating''?
Sent from my Nexus 5X using Tapatalk
Hi all!
I have been noticing that the tablet can get fairly hot where the CPU is, and under load it can reach fairly high temperatures - CPU prime got it up to over 90°C for me to the extent that I had to shut it down.
To be honest, it doesn't really impede normal usage, and normally it seems to reach slightly over 70°C under higher workloads. I suppose that's not unheard of for ARM devices and might not actually count as overheating. But after seeing this video on the Teclast X98 Pro and some other info on modding in tablets, I was still wondering if there'd be a way to improve the cooling on the Note 10.1 2014 to get lower average temperatures - potentially, that should also lead to more stable and fluid running under high loads, as there won't be any need for throttling, and it might also be good for the components to keep temps lower.
So I guess my main question is if anyone has undertaken anything of this sort for this or comparable tablets? @thebadwrench has recently posted a very useful guide about swapping the battery with a rare shot of the inside of the tablet: http://forum.xda-developers.com/showpost.php?p=66124495&postcount=13
I was thinking what the most sensible way could be to improve cooling of the CPU, which should be the small shielded unit in the lower centre of the second picture. People seem to have had good results with copper, but it seems fairly crowded in there and it might be hard to get it installed without shortening anything.
Aside of the more practical question, I'd also be interested in the typical temperature that other people's tablet reaches and if you have any better apps than CPU prime to produce high CPU load - possibly one that shows CPU temperature at the same time as well? Currently, I'm having another app running to check CPU temp (CPU prime for some reason only shows the battery temp).
Looking forward to everyone's answers!
PS: @mods Not sure if this is the right section of the forum, feel free to move if you feel it fits better elsewhere.
AFAIK Microsoft intended to fit an innovative kind of heat sink into their Lumia 950 and finally produced a standard design w/o particular cooling devices due to difficulties.
I have no clue how anything could be done. Except replacing the back cover with something thicker, offering room for heatsinks, fans, peltier elements or such.
But the Note should at least have thermal throttling and emergency shutdown features, like all current phones, which will throttle within the first half minute under full load.
franzli said:
Hi all!
I have been noticing that the tablet can get fairly hot where the CPU is, and under load it can reach fairly high temperatures - CPU prime got it up to over 90°C for me to the extent that I had to shut it down.
To be honest, it doesn't really impede normal usage, and normally it seems to reach slightly over 70°C under higher workloads. I suppose that's not unheard of for ARM devices and might not actually count as overheating. But after seeing this video on the Teclast X98 Pro and some other info on modding in tablets, I was still wondering if there'd be a way to improve the cooling on the Note 10.1 2014 to get lower average temperatures - potentially, that should also lead to more stable and fluid running under high loads, as there won't be any need for throttling, and it might also be good for the components to keep temps lower.
So I guess my main question is if anyone has undertaken anything of this sort for this or comparable tablets? @thebadwrench has recently posted a very useful guide about swapping the battery with a rare shot of the inside of the tablet: http://forum.xda-developers.com/showpost.php?p=66124495&postcount=13
I was thinking what the most sensible way could be to improve cooling of the CPU, which should be the small shielded unit in the lower centre of the second picture. People seem to have had good results with copper, but it seems fairly crowded in there and it might be hard to get it installed without shortening anything.
Aside of the more practical question, I'd also be interested in the typical temperature that other people's tablet reaches and if you have any better apps than CPU prime to produce high CPU load - possibly one that shows CPU temperature at the same time as well? Currently, I'm having another app running to check CPU temp (CPU prime for some reason only shows the battery temp).
Looking forward to everyone's answers!
PS: @mods Not sure if this is the right section of the forum, feel free to move if you feel it fits better elsewhere.
Click to expand...
Click to collapse
Similar temperatures are note uncommon in mine. One suggestion is to use a small desktop fan and aim it down at the tablet when your demanding alot from the cpu. I sometimes do that with mine and it actually brings the temperature down about 15 degrees. Its not a mod, but it does work
Thanks for your answers so far!
@lecorbusier yes, I suspect it has throttling, but in the interest of better running it would be nice to avoid throttling when possible. I'm not sure about the effect on battery life - throttling might be good in that a reduced frequency might need less energy, but running hot in the first place is probably bad for battery life.
In fact, part of my problem might stem from either the ROM or some apps I am running - Squid on temasek's CM13. Maybe I just never noticed this before, or didn't use squid so often, but I've noticed that the last couple of days CPU gets up to over 70°C at times with just some writing in squid. Not sure if this is normal, will probably post it in the CM13 thread. But my general idea/wish to improve cooling still stands independently of that.
Similar temperatures are note uncommon in mine. One suggestion is to use a small desktop fan and aim it down at the tablet when your demanding alot from the cpu. I sometimes do that with mine and it actually brings the temperature down about 15 degrees. Its not a mod, but it does work
Click to expand...
Click to collapse
That sounds like an effective method (and I guess in a way one might call it a mod ). I'm thinking about something more portable, and hence passive though.
I will probably try opening up and having a look at the current cooling mechanism to see if adding a copper shim or a better silicone heat sink etc. might help things. Another consideration would be a modded case that contains some metal instead of plastic on the back side. That might help to take away some of the heat even though the plastic back of the device itself probably remains a poor heat conductor. Might be a complicated mod, but I'll see if I can come up with a way to do that. If/when I manage to get something done, or some new thoughts, I will advise here.
Any further input of course still very welcome!
Metal will disturb the various antennas.
A back cover replacement containing one or two fans, adding 1 to 2cms of thickness, and draining the battery with the fans while looking clumsy, thats the "best" solution I could imagine.
Or a back cover replacement containing one or two copper plates, cut and arranged in a way that the antennas aren't too handicapped. Probably you have to remove the various EMI shields to be able to establish direct contact between the chipset and the plates. That is, if the chips don't have contact with the shield plates.
I think this will be something never been done before, but probably after.
Like the battery mod for phones, where you solder one battery together with a second one and cut a hole in the back cover, that the now double-thick battery may fit. That's already been done.
Good point about the antennae, I hadn't thought about that! That also makes sense of the lack of metal cases (facepalm). Might still try modding a case with some metal in some spots at some points, but good to keep in mind how this might impact wifi and bluetooth.
My plan was to see if there'd be a chance to fit some slim copper plates in strategic position on top of the CPU inside the normal case. I'll have to open it up and see how much, if any, space there is - but will probably try this first on a Galaxy Tab S 8.4 that I rely on less for productivity (and that does actually get way to hot, to the point of self-shutdown). Whenever I find the time that is...
Will report when I get around to doing anything on the Note (and might open a topic at the Tab S forum in case I do try a mod there first).
I added a copper shim for cooling to my Galaxy Tab S (will put a more detailed post on that forum when I find some time), which seems to have helped to control temperatures somewhat better. I had two odd crashes, but had some before I did the mod, so am relatively confident that's a problem of the ROM rather than my mod.
Will probably try it on my Note as well soon and report here for anyone who might be interested.
Have modded my Note now, and am planning to post a more detailed description some time (won't have time before next month though). It had clearly improved temperatures and stability of my Tab S, but I'm not sure how much of a difference it made on the Note 10.1 2014 because I didn't measure the baseline temperatures before the mod right (used CPU Prime benchmark which seems to have general stability issues on the temasek ROM I'm using).
Currently, I have idle temperatures of around 30C, under normal use it would get to 40-50C, and under stress (app StabilityTest) it goes up to around 89/90C after 5min and to 92/93C after 10min.
I'd be quite interested in what temperatures other people get on their devices without any modification?
franzli said:
Have modded my Note now, and am planning to post a more detailed description some time (won't have time before next month though). It had clearly improved temperatures and stability of my Tab S, but I'm not sure how much of a difference it made on the Note 10.1 2014 because I didn't measure the baseline temperatures before the mod right (used CPU Prime benchmark which seems to have general stability issues on the temasek ROM I'm using).
Currently, I have idle temperatures of around 30C, under normal use it would get to 40-50C, and under stress (app StabilityTest) it goes up to around 89/90C after 5min and to 92/93C after 10min.
I'd be quite interested in what temperatures other people get on their devices without any modification?
Click to expand...
Click to collapse
Thanks for the update. I did some baseline checks for you, using the same StabilityTest app for consistancy purposes. I am also on temaseks build, cm13 more specifically. I run temaseks 12.1 build just as often as the cm13, so I will run the tests there as well. I revert back to my stock rooted kitkat rom about 1 or 2 days per week so I'll check the temps on that ROM as well.
So, at idle I'm a little warmer than you, hovering between 37C and 40C. Under normal use (like web browsing) I'm between 50C and no higher than 57C. Under stress (again, using same app) I was at 90C at 5 minutes and 91C after 10 minutes. So slightly warmer on low end, nearly identical on the big end. I have the samsung flip cover thats specifically made to fit the 2014 edition on mine, so that could account for my slightly warmer temps. Its worth noting that when gaming on a VERY cpu demanding game, I never reach anything above 78C. Its probably one of the top 10 most cpu demanding games on play store and BY FAR the most I ever demand from my CPU, consuming a whooping 1.5-2Gb of RAM at times.
I'll check the numbers on my other 2 normally used ROMs here in the next few hours and I'll post those results too :good:
On a side note, my galaxy s6 phone (completely stock, near new) averages nearly indentical cpu temps and after researching the matter on it, I found that those temps (on the s6) are what others are getting as well. So it seems that, generally speaking, samsungs might just run with warmer temperatures. I did see somewhere that 100C is kinda the 'YIKES!' point for them and that they start clocking down around that temp to prevent permanent damage
franzli said:
I'd be quite interested in what temperatures other people get on their devices without any modification?
Click to expand...
Click to collapse
Ok, I've done some testing with a few different ROMs and I think you might be as susprised with the results as I am. First of all I need to correct myself in my last post. The initial testing I did was on temaseks unofficial CM12.1 build, not on the CM13 build. I have now tested on temaseks cm 12.1 and cm13 builds, my stock rooted & debloated 4.4.2 ROM and an old nandroid backup I have of hyperdrives 4.4.2 ROM. Heres what I found...
Temaseks CM13 build ran the hottest and was by far the most stressful on the processors and therefore ran the hottest. It consistantly kept the CPU clocked at near max (even when set to "ondemand"), whether needed or not (with no background process running) and would only reduce power when forced via CPU governor or was at the safety threshold for temperature, which I can now comfortably say is about 95C. Tablet was slightly warm to the touch at idle with a temperature of between 50C & 55C. Under moderate load temperature jumped very raidly to the mid 80C range and then would stay there pretty steadily. Under heavy load, CPU temp quickly peaked at 94C where while watching the CPU output, it was obvious the CPUs were going in & out of protection mode as they would drop to 1600MHz, then peak at 1900MHz, 1600MHz, 1900MHz & repeat this. I didnt let this go on for more than about 2 min before shutting down and allowing tablet to cool.
Next, I repeated tests on both touchwiz based kitkat ROMs I have backups for. 1 of them is stock, rooted, debloated and un"tweaked". The other is stock, rooted, debloated and tweaked. Both ran MUCH cooler, peaking at 80C & 82C. These were ocassional spikes and actually averaged around 75C when under heavy load. Now comes the good news...
I have identified a major contributor of excessive CPU temps. When testing on the touchwiz ROMs and observing CPU clocking in relation to CPU temps, I found that the governors are set lower in these touchwiz ROMs. They were a steady 1300MHz with the occasional 1600MHz spike. They averaged 55C to 63C under moderate load and when under heavy load never reached more than 82C.
So, I am now back on my long time daily driver, temaseks cm12. 1 build and I'm ditching the CM13 build entirely. At least for now. I have set my CPU governors down to 1300MHz and with heavy load for nearly 30 minutes (gaming) my CPU peaked at 85C. So my findings were that CM ROM has overclocked the CPUs excessively. They are set to 1900MHz, which has become obvious to me brings them right up to their temperature safety threshold, 95C. It seems Samsung clocked them at 1300MHz and allowed for occasional spikes above this point, keeping them at a maxium & slightly more reasonable 85C a full 10C cooler than their maximum safe operating temp.
I never expected I'd stumble on not only a source, but also that I've been utilizing the solution for months. I should add that governing the CPU lower has had absolutely no effect on performance. I regularly shut down 1 or 2 CPU cores as it is. I found that the tablet will run perfectly under normal use with only 2 cores. This reduces temperature and increases battery life. Sluthing can be so much fun sometimes, it was right in front of my face I just never put 2 & 2 together lol :good:
Thanks for your detailed comparison, that's very helpful indeed! In light of that, I think my mod has indeed given some improvement, as I don't reach over 90°C on CM13 until after 5-10 min, albeit with some throttling to 1700MHz after about 10min.
I've always had the impression that the current CM13 builds are a bit more CPU hungry and run warmer (possibly that triggered my thinking about a cooling mod in the first place), so it's very interesting to see that backed up experimentally! Interestingly, I've had mixed experiences with CM13, almost like two "modes" of running - sometimes, it runs pretty warm, roughly like you describe, but at other times it runs fairly normally around 30-40°C without problems. Haven't really figured out what the problem is and am having occasional instabilities/reboots as well, so I might actually also return to CM12.1 for the moment too.
While the higher CPU clocks (although 1.9GHz is the specified clock speed, but I get what you mean) may explain the heat and slightly better results in Geekbench I've been having with CM13, it's a bit odd that I still get the good result when the ROM is in the cool "mode" (it goes up to high 60s, mid 70s during Geekbench if memory serves well).
How do you set your governors? And have you been able to get the cores to switch on and off automatically as they do on some other devices? Or is this not implemented in the kernel or something?
franzli said:
Thanks for your detailed comparison, that's very helpful indeed! In light of that, I think my mod has indeed given some improvement, as I don't reach over 90°C on CM13 until after 5-10 min, albeit with some throttling to 1700MHz after about 10min.
I've always had the impression that the current CM13 builds are a bit more CPU hungry and run warmer (possibly that triggered my thinking about a cooling mod in the first place), so it's very interesting to see that backed up experimentally! Interestingly, I've had mixed experiences with CM13, almost like two "modes" of running - sometimes, it runs pretty warm, roughly like you describe, but at other times it runs fairly normally around 30-40°C without problems. Haven't really figured out what the problem is and am having occasional instabilities/reboots as well, so I might actually also return to CM12.1 for the moment too.
While the higher CPU clocks (although 1.9GHz is the specified clock speed, but I get what you mean) may explain the heat and slightly better results in Geekbench I've been having with CM13, it's a bit odd that I still get the good result when the ROM is in the cool "mode" (it goes up to high 60s, mid 70s during Geekbench if memory serves well).
How do you set your governors? And have you been able to get the cores to switch on and off automatically as they do on some other devices? Or is this not implemented in the kernel or something?
Click to expand...
Click to collapse
Your welcome. I too noticed that on CM13 at times it seems to run alot cooler than at other times. Although the only time I ever see go as low as 30C is when its been asleep for awhile and then I turn the screen on (CM12 & 13). As soon as it wakes up it'll go to mid-high 40C to mid 50C (on CM12) or it'll go straight to high 50C to low 60C (CM13). CM13 definitely ramped up alot quicker when testing, almost like its either min or max CPU power. I like temaseks CM13 build, but for me there wasnt much improvement over the CM12 build. Plus there is a few minor bugs as well as the slight negative effect on battery life I noticed. Plus I was noticing that there was a bit of a touchy spot in the top right corner of my screen that when swiped from the outside in, it sometimes crashed my tablet. I wasn't sure if it was a fault in my tablets hardware or something software related and I'm still not 100% positive which it may be, but since I began taking notice of when it was happening, its only ever happened on CM13. Thats also part of the reason I think I'm going to hold off on using the CM13 build for awhile. CM12 build is overall just more to my liking I guess... more to my tablets liking as well.
After posting yesterday I looked up some specs on Samsungs website and you are 100% correct about it being 1.9GHz. This is the spec copy/pasted off their website... Exynos® 5 Octa (1.9GHz Quadcore + 1.3 GHz Quadcore). The second part stands out because 1.3GHz is definitely where the stock rom was trying to maintain its CPU frequency when under heavy load. Not once did it exceed 1.6GHz. Whereas both CM builds ramped up to the full 1.9GHz very quickly. So the difference is going to be HOW the processor steps up in frequency as opposed to what the frequency actually is. Thats where my knowledge on that kinda stuff ends. I'm a "let's figure out what failed and why" or "lets figure out how it works" type of person. Thats why I work on cars for a living. I leave the development and detailed technical mumbo jumbo to the devs and engineers. Troubleshooting methods are much the same for just about everything though, hince how I came to my conclusion yesterday. Just for grins I may load up PAC ROMs CM12 build, see how it does. too...
As for how I set my governor, it depends on what I doing at the time. I never fine tune anything, like I said, that's outside my realm of knowledge. What I do set is the governor to either interactive or ondemand. Interactive more for casual use and ondemand more for gaming. I also manually shut down CPU cores depending on my demand from my CPU. Right now, for instance, I'm running stricly on cores 0 & 2 with cores 1 & 3 turned off. My CPU max clocking frequency is set to 1.3GHz but its consistantly hovering at 650MHz, or .65GHz. Thats all I ever mess with and I do so mainly for battery life. It makes a noticeable difference (both charging and discharging) if I adjust those 3 things according to my use. And no, my cores don't ever switch on or off automatically. I do vaguely recall seeing them do that on a different ROM, but I don't remember what ROM that was... it was at least a year ago that I saw that. I'm sure that is something that is kernel related, but I'm just guessing on that one.
What exactly did you mod? Any pictures?
thebadwrench said:
Your welcome. I too noticed that on CM13 at times it seems to run alot cooler than at other times. Although the only time I ever see go as low as 30C is when its been asleep for awhile and then I turn the screen on (CM12 & 13). As soon as it wakes up it'll go to mid-high 40C to mid 50C (on CM12) or it'll go straight to high 50C to low 60C (CM13). CM13 definitely ramped up alot quicker when testing, almost like its either min or max CPU power. I like temaseks CM13 build, but for me there wasnt much improvement over the CM12 build. Plus there is a few minor bugs as well as the slight negative effect on battery life I noticed. Plus I was noticing that there was a bit of a touchy spot in the top right corner of my screen that when swiped from the outside in, it sometimes crashed my tablet. I wasn't sure if it was a fault in my tablets hardware or something software related and I'm still not 100% positive which it may be, but since I began taking notice of when it was happening, its only ever happened on CM13. Thats also part of the reason I think I'm going to hold off on using the CM13 build for awhile. CM12 build is overall just more to my liking I guess... more to my tablets liking as well.
After posting yesterday I looked up some specs on Samsungs website and you are 100% correct about it being 1.9GHz. This is the spec copy/pasted off their website... Exynos® 5 Octa (1.9GHz Quadcore + 1.3 GHz Quadcore). The second part stands out because 1.3GHz is definitely where the stock rom was trying to maintain its CPU frequency when under heavy load. Not once did it exceed 1.6GHz. Whereas both CM builds ramped up to the full 1.9GHz very quickly. So the difference is going to be HOW the processor steps up in frequency as opposed to what the frequency actually is. Thats where my knowledge on that kinda stuff ends. I'm a "let's figure out what failed and why" or "lets figure out how it works" type of person. Thats why I work on cars for a living. I leave the development and detailed technical mumbo jumbo to the devs and engineers. Troubleshooting methods are much the same for just about everything though, hince how I came to my conclusion yesterday. Just for grins I may load up PAC ROMs CM12 build, see how it does. too...
As for how I set my governor, it depends on what I doing at the time. I never fine tune anything, like I said, that's outside my realm of knowledge. What I do set is the governor to either interactive or ondemand. Interactive more for casual use and ondemand more for gaming. I also manually shut down CPU cores depending on my demand from my CPU. Right now, for instance, I'm running stricly on cores 0 & 2 with cores 1 & 3 turned off. My CPU max clocking frequency is set to 1.3GHz but its consistantly hovering at 650MHz, or .65GHz. Thats all I ever mess with and I do so mainly for battery life. It makes a noticeable difference (both charging and discharging) if I adjust those 3 things according to my use. And no, my cores don't ever switch on or off automatically. I do vaguely recall seeing them do that on a different ROM, but I don't remember what ROM that was... it was at least a year ago that I saw that. I'm sure that is something that is kernel related, but I'm just guessing on that one.
What exactly did you mod? Any pictures?
Click to expand...
Click to collapse
Hi thebadwrench,
Which app did you use to do all this modifications on cm13 stock kernel? Especially deactivating cores is very interesting. Can you see all eight cores? I'm using 3C toolbox and it shows it only as quad core and on voltage page I have two cpu cluster.(one clocked till 650mhz and the other till 1900mhz)
Under CM13 the cpu behavior is totally different as on stock Samsung roms because the small cores are more or less unused and clocked at max. only at 650mhz, Lol!
I watch also much more kernel warnings in ksmg and high temperatures for a while now on CM13.
Also battery runtimes are only 3,5-5h unlike 7-8h under cm12.1!
Sometimes the cpu is also locked at max. speed(1,9ghz), mostly after looking youtube videos or other heavy load situations. The only way to get back "normal" behavior is to reboot the device.
I see also only two used cpu states all the time it jumps between 250 and 1900mhz, the most steps in between are unused.
We can only hope a real kernel developer can have a look on this or we can cherry pick some usefull tweaks from another device with the same cpu chipset.
ollimi1 said:
Hi thebadwrench,
Which app did you use to do all this modifications on cm13 stock kernel? Especially deactivating cores is very interesting. Can you see all eight cores? I'm using 3C toolbox and it shows it only as quad core and on voltage page I have two cpu cluster.(one clocked till 650mhz and the other till 1900mhz)
Under CM13 the cpu behavior is totally different as on stock Samsung roms because the small cores are more or less unused and clocked at max. only at 650mhz, Lol!
I watch also much more kernel warnings in ksmg and high temperatures for a while now on CM13.
Also battery runtimes are only 3,5-5h unlike 7-8h under cm12.1!
Sometimes the cpu is also locked at max. speed(1,9ghz), mostly after looking youtube videos or other heavy load situations. The only way to get back "normal" behavior is to reboot the device.
I see also only two used cpu states all the time it jumps between 250 and 1900mhz, the most steps in between are unused.
We can only hope a real kernel developer can have a look on this or we can cherry pick some usefull tweaks from another device with the same cpu chipset.
Click to expand...
Click to collapse
I use kernel adiutor https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor It also shows 4 cores but shutting them down is just a single click. In the attached screenshot you can see that I've manually unchecked cores 1 & 2 and on the CPU display (turned on via developer options) you can see that those cores are indeed shut down and not operating. I like the app's widget, allows you to set up as many different profiles as you want and then change between the different profiles on the widget.
thebadwrench said:
I use kernel adiutor https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor It also shows 4 cores but shutting them down is just a single click. In the attached screenshot you can see that I've manually unchecked cores 1 & 2 and on the CPU display (turned on via developer options) you can see that those cores are indeed shut down and not operating. I like the app's widget, allows you to set up as many different profiles as you want and then change between the different profiles on the widget.
View attachment 3732472
Click to expand...
Click to collapse
Yeah, good news!
I am positive surprised that kernel Adiutor is working, seems we have build-in UCI, which is needed, nice! Using KA on my OP2 since a long time but there is no custom kernel for p600 cm13 roms so I have not tried!
Will try it now!:good:
Thanks!!
thebadwrench said:
What exactly did you mod? Any pictures?
Click to expand...
Click to collapse
I replaced the silicone heat pad on the CPU with a copper shim and thermal compound, added some small silicone pads around other components (all under the heat shields) and added a .5mm silicone heat pad on top of the main heat shield to enhance contact with the back plate. I do have some pictures, but I want to provide a proper write-up and currently don't have much time as I'm moving. Will hopefully find a chance to give a more detailed write-up in May - sorry for the delay, but full report is forthcoming!
As for the CM13 issues, @joshndroid apparently implemented some changes to it in the last build, so I might check that out, although I agree that CM12.1 is probably still the safer bet for a stable daily driver.
franzli said:
Thanks for your detailed comparison, that's very helpful indeed! In light of that, I think my mod has indeed given some improvement, as I don't reach over 90°C on CM13 until after 5-10 min, albeit with some throttling to 1700MHz after about 10min.
I've always had the impression that the current CM13 builds are a bit more CPU hungry and run warmer (possibly that triggered my thinking about a cooling mod in the first place), so it's very interesting to see that backed up experimentally! Interestingly, I've had mixed experiences with CM13, almost like two "modes" of running - sometimes, it runs pretty warm, roughly like you describe, but at other times it runs fairly normally around 30-40°C without problems. Haven't really figured out what the problem is and am having occasional instabilities/reboots as well, so I might actually also return to CM12.1 for the moment too.
While the higher CPU clocks (although 1.9GHz is the specified clock speed, but I get what you mean) may explain the heat and slightly better results in Geekbench I've been having with CM13, it's a bit odd that I still get the good result when the ROM is in the cool "mode" (it goes up to high 60s, mid 70s during Geekbench if memory serves well).
How do you set your governors? And have you been able to get the cores to switch on and off automatically as they do on some other devices? Or is this not implemented in the kernel or something?
Click to expand...
Click to collapse
Hi Franzli,
The kernel seems odd to me!
The small A7 cluster is virtually unused and clocked only to 650MHz @ 1200ma !! Normal is 1.3GHz @ 1200ma for the small A7 cluster on 5420! Also a lot of warnings and errors in ksmg!
No idea whether the A7 ever used or permanently in idle mode, Lol!
Also all 4 big a15 cores are always online, what means no hotplug driver available!
I don't know if we will ever see a good kernel for CM13 because of the missing sources.
Although the kernel is running and mostly stable it is far from "good"!
Power consumption is almost doubled, problems with overheating and sometimes cpu is locked at max. speed and the only way to solve it is a reboot.
I don't remember the cm12.1 kernel but he was definately better in terms of battery runtimes and reliability.
BTW, I'll also mod the device cooling using bigger copper sheets instead of the perforated aluminum sheets, thermal-pads and thermal-grease when I start changing my battery and usb jack, what is definately neccessary in my case!
Maybe I will buy one of the small heatpipes used in S7 or so when I find them somewhere.
It is not difficult to adjust it if needed, so that it can replace the heatspreader.
Mabye it is needed to isolate the heatpipe from the mainboard but nothing what a piece of kapton tape not can do.
franzli said:
Hi all!
[...] But after seeing this video on the Teclast X98 Pro and some other info on modding in tablets, I was still wondering if there'd be a way to improve the cooling on the Note 10.1 2014 to get lower average temperatures [...]
So I guess my main question is if anyone has undertaken anything of this sort for this or comparable tablets? [...]
Click to expand...
Click to collapse
Hallo there
Well I just did the job. I have also made a short manual and would like to share it with you. But first some things about me and my tablet.
I bought a used galaxy note 10.1 2014 edition SM-P600 couple months ago. I was really disappointed about the device performance. Switching from stock android 5.1 to [ROM][7.1.2]Resurrection Remix N for SM-P600 (n1awifi) [5.8.5][UNOFFICIAL][NIGHTLY] did some improvements in performance. But since I am a very heavy web surfer I was still not satisfied with the performance. I have also tried [P600][Touchwiz] Marshmallow Rom 20170622 and went back to RR because I can play around with the CPU governors and all that deathy audiutor stuff. Between very nice work Exynos Team and all the other developers...
Soon I realized that the SM-P600 becomes fairly hot in the backside. I took a look at the ifixit pictures. There was no other way finding good resolution pictures of the inside.
I ended up installing cool tool app. Well is there any other good app for monitoring temps, clock and load in overly?
Well so I added frequency, load, battery temp and cpu temp. You need to add cpu temp manually. I guess it is Label ->
custom label -> enable- Then you have to go fine tuning -> custom label -> path:/sys/class/thermal/thermal_zone0/temp. leace everything as it is. regex is (\d+)\d{3} and add postfix °C and prefix cpu:
.
So I went along and analysed heat and temps in the galaxy 10.1 2014 edition. Especially frequency-temp-ratio. And I can tell you this buddy is everything else than cool. Temps jump up so fast I can't tell you. Even some fast scrolling on ebay, facebook desktop web page in browser treated the Temperature to the hight 80s and soon the high 90s. I have also seen the things franzli mentioned before. Even light work put so much heat to the processor. Watching the frequency and temperature bounce was a pain. I could feel the pain that little Exynos 5420 must suffer of all the time.Throttling is the only ways this little buddy can survive To make it short I decided to do the cooling mod...
So lets see what I found on my journey ... I can tell you that's a big surprise
I opened the case very easily. You can find tons of videos on youtube or use ifixit.
Well I have to mention I am an electronics hardware engineer. So doing this stuff is nothing unique for me. And I have years of professional PCB manufacturing, repair experience.
Opening the case, adding some tape and this is what you get...
As you can see there is a little thermal pad applied to the aluminium shielding. And boooom there you are . Do you see all thet flux solder remains? How come samsung? Seriously?
This is the shielding close up with that thermal pad.
As you can see the FBGA package is covered with flux from soldering. So it is naturally, that the cooling in the galaxy is a pain. There can't bee any good heat flow.
So let's check that thermal pad.
woops that little buddy is kinda to small. I am sad to see this.
Well I cleaned the surface as good as I can with ethanol. After this I applied a new Thermal pad.
After that it looked like this.
Then I closed the shielding case and cleaned it.
So next comes the actual cooling mod. I added a big thermal pad.
I had to cut that little hook in the back plate. So that the 100mmx100mm copper layer will fit in shape.
And this is it done.
So what about the results :laugh:
The back plate fits perfectly. If you know there is a thin layer of copper you can feel it. But it is so less. I had no problem closing the case. Ahh yeah I had to tage it with double sided tape, so it is pressed down to the thermal. The back plate will do the rest pressure.
And really don't worry about the wifi interference. There is no worry. Because the copper layer is located on top of the bettery pack and shielding case. Why should there be any interference? I have tried. Reaching same wifi performance as always. No worries:good:
So what about heating. Well my galaxy note stays pretty cool.
I need to mention this is all mesured with the [ROM][7.1.2]Resurrection Remix N for SM-P600 (n1awifi) [5.8.5][UNOFFICIAL][NIGHTLY] I mentioned before.
I used interactive governor.
I reach in Antutu v6.2.7 about 57000 to 58000
In futuremark work 2.0 I get 4000
Here some pics
I am sorry for that high resolution pics. But I wanted best of (bad) quality. I used my redmi note 4 for taking pictures. If you can't read all in the pics, just open in new window.
There isn't any more throttling at all. It is hard to push to 85°C or above now. Just with synthetic GPU and CPU load on all four cores at once. And it takes a couple of minutes. But in real world you will never get it. With only load on one core my maximum is 69 to 72°C. The tablet fells pretty nice now. The warming in the back plate is reduced to a very large surface. So sometimes it fells as if your hands warm up the case.
Can you suggest me any ROm with a good overclocking potential? I have already tried this ROM. I really don't know why, but it keeps crashing all the time at 2GHz or 2.1 GHz. Even with no load at all. I guess the used kernel is bad.
Do you have any ROM suggestion for me.
If you have any quastions and things you want me to test write me.
Just wanted to share my experience with you. I didn't expect a dirty PCB, BGA and thermal pad like this. So what do you think about this.
Hi all,
So i got a HTC 10 UAE edition from a guy two days before. He was selling it at a reasonable price and i bought it from him.
The battery was draining quite fast and i thought it might be a software issue and i installed venom rom, but problem still existed, so i turned back to stock 2.41.401.41 (Which was very hard though) .
Still the battery is draining so fast. The charger came with the phone( Quick charger ) was also not working and now i'm facing the phone's battery is draining so fast. I'm very confused whether that guy have cheated me or not. If this is a hardware issue i think i have to contact that guy soon.
adb battery stat gave me 2580mah full charge capacity and here, i'm attaching the GSAM battery logs.
Please help me on this
Thanks
Edit: Since the original charger isnt working, im using a oppo 5v- 1A charger, is dat matters on battery drain?
Mine was doing the same as yours, quick charge also stopped working. I changed the cable and it solved it for a few weeks, but the drain started again and quick charge stopped again. Tried ruu etc but no luck. I've sent mine in for repair under warranty and should get it back Monday. My guess is either the charging port is faulty or motherboard but will find out next week.
I was having the exact same problem. I downloaded an app called Lspeed (It's also on the playstore) and did some tweaking in that app as well as used the Enable doze for GMS Magisk Module and now my kernel and android system are on par with each other as far as battery drain goes. Not sure why there are only a handful of people that experience this problem but i'll edit this post with screens of my lspeed config if you want to give that a go!
Edit: Config uploaded. Some of those options are personal preference but take a look around and test it out. What you'll most likely want is to enable the light doze optimization and disable the debugging. That will most likely help in your situation.
Very strange, I'm experiencing this issue too, always receive around 2-3hrs of screen on with very high kernel use during standby. Tried flashing Leedroid, Element X to no avail.
timbohobbs said:
Mine was doing the same as yours, quick charge also stopped working. I changed the cable and it solved it for a few weeks, but the drain started again and quick charge stopped again. Tried ruu etc but no luck. I've sent mine in for repair under warranty and should get it back Monday. My guess is either the charging port is faulty or motherboard but will find out next week.
Click to expand...
Click to collapse
Mine is out of warranty. Dunno what to do now. Tried almost everything.
bilibox said:
I was having the exact same problem. I downloaded an app called Lspeed (It's also on the playstore) and did some tweaking in that app as well as used the Enable doze for GMS Magisk Module and now my kernel and android system are on par with each other as far as battery drain goes. Not sure why there are only a handful of people that experience this problem but i'll edit this post with screens of my lspeed config if you want to give that a go!
Edit: Config uploaded. Some of those options are personal preference but take a look around and test it out. What you'll most likely want is to enable the light doze optimization and disable the debugging. That will most likely help in your situation.
Click to expand...
Click to collapse
I'm currently running on pure stock. Will try this method soon. How was your battery standby before doing the tweak ?
Have you tried wiping cache? Mine drains fast depending on the load, which is usually pretty heavy daily. Plus, I don't dim my screen much. Never knew the advice command for battery. I gotta try that.
Stock Rom
Okay, so I got fed up with the battery life I've been getting and have looked more into it, I've managed to reclaim a lot of the longevity I had before updating to Nougat without hampering UI fluidity. For reference, I'm using Leedroid 3.9 with Element X v1.08 and was getting around 2hrs screen on, android system and kernel had the highest usage under GSam.
bilibox has the right idea, my idle drain was very high, L speed and Greenify both have options to enable a more aggressive Doze which worked pretty well, I lose ~10% battery overnight vs a shocking 20-30% before. I still felt battery drain was too high when active, I combined ivicask's PNP mod (balanced) with some little governor tweaks in EX Kernel manager, basically, I'm using interactive on the little cluster and elementx governor on the big cluster (which tends to be slightly more conservative in my uses). I also set min performance to 0% and downclocked the big cluster to 2Ghz, I'm focusing on these cores since they were draining a lot of power in my case.
It's not a super extensive list of tweaks nor something we haven't seen before, but I manage around 3.5hrs of screen on now which gets me through the day. Before I would have to top up around early afternoon, the phone is also really smooth and I'm happy with how everything is running. I hope this helps some people out!
ryanjsoo said:
Okay, so I got fed up with the battery life I've been getting and have looked more into it, I've managed to reclaim a lot of the longevity I had before updating to Nougat without hampering UI fluidity. For reference, I'm using Leedroid 3.9 with Element X v1.08 and was getting around 2hrs screen on, android system and kernel had the highest usage under GSam.
bilibox has the right idea, my idle drain was very high, L speed and Greenify both have options to enable a more aggressive Doze which worked pretty well, I lose ~10% battery overnight vs a shocking 20-30% before. I still felt battery drain was too high when active, I combined ivicask's PNP mod (balanced) with some little governor tweaks in EX Kernel manager, basically, I'm using interactive on the little cluster and elementx governor on the big cluster (which tends to be slightly more conservative in my uses). I also set min performance to 0% and downclocked the big cluster to 2Ghz, I'm focusing on these cores since they were draining a lot of power in my case.
It's not a super extensive list of tweaks nor something we haven't seen before, but I manage around 3.5hrs of screen on now which gets me through the day. Before I would have to top up around early afternoon, the phone is also really smooth and I'm happy with how everything is running. I hope this helps some people out!
Click to expand...
Click to collapse
Still its bad that a 3000mah battery with a smaller screen compared to other flagships giving a very low battery backup just because of software bug. From reviews, i can see that MM is giving fine SoT as well as standby. One thing i really cant is the standby. I cant even go out for a day trip. The battery will die in just 10-12hrs even on standby.
$tark3 said:
Still its bad that a 3000mah battery with a smaller screen compared to other flagships giving a very low battery backup just because of software bug. From reviews, i can see that MM is giving fine SoT as well as standby. One thing i really cant is the standby. I cant even go out for a day trip. The battery will die in just 10-12hrs even on standby.
Click to expand...
Click to collapse
That's unfortunate to hear, my battery life is pretty much in line with my friend's S7 now, newer devices can get away with larger displays because the 835 is a bit more efficient.
ryanjsoo said:
That's unfortunate to hear, my battery life is pretty much in line with my friend's S7 now, newer devices can get away with larger displays because the 835 is a bit more efficient.
Click to expand...
Click to collapse
Soon i'll have to ditch htc.
$tark3 said:
Soon i'll have to ditch htc.
Click to expand...
Click to collapse
I restore my phone and did all updates again. My battery still seems to drain very quick .in an hour with some navigation, and little screen use It went from 20% to 1 percent.
I've taken excellent care of my HTC. Before this, I had HTC 8 and loved it, until right at the 2-year mark, a small area of the screen stopped working.
This is the second time I` experience this, and sadly there won't be a third., especially after new HTC removed the headphone jack like the iPhone ... RIP HTC
Well to be honest the past couple days were to weird to me usually i get 5 - 6 SOA over 13 hours
now i get 3:30 - 4 SOA over 13 hours, same usage, and i have noticed that google service consume most of the power, i have installed doze program and kept my eye on GSM battery Monitor, after all the google service kept the kernal wake up for a long time, and keep running the hardware on the full abilities
I unistalled Gsam battery monitor and kernel usage is back to normal...
AggelosGR said:
I unistalled Gsam battery monitor and kernel usage is back to normal...
Click to expand...
Click to collapse
I have uninstalled ForceDoze and Gsam Bettery this morning but still feeling that there is something wrong, i might do some battery calibration on my free time, because i charge my phone only for 90% and it did not get lower than 20% i feel like i am losing the battery capacity
Was having the same issue, and had been searching for weeks to try and solve this. Tried rooting, factory resets, ROMs, everything.
For me the issue was Google Sync, in particular Contacts and People syncing. I disabled those and everything is back to normal. There was a program called Google Contacts Sync (Apps > Show System > Google Contacts Sync). I cleared the data on that, and then went into Accounts and Sync and turned everything off. That fixed the battery drain. I have tried turning back on Gmail, Keep and a few others and still have great battery.
I have the same issue and I don't know how to fix it. Please help
I got S22 Snapdragon Variant but the battery still sucks and phone heats up much after I have done the following.
1. Followed [GUIDE] [NO-ROOT] Complete Samsung OneUI Optimization
- Most settings applied
- Phone set up without Smart Switch
- Adaptive Battery disabled
2. Installed [App]Galaxy Max Hz (Refresh Rate Mods, Screen-off Mods, QS Tiles, Tasker Support and More)
- Adaptive Refresh on Power-Saving mode On
- Adaptive Min 10Hz, and Max 120Hz
- Force Lowest Hz on screen-off (10Hz)
2. Installed ®FDE.AI - Ultimate Android Optimizer
- Power-Saving mode
- Force Doze Mode On
- Sensors Off on screen off
- Analyze Apps on screen off
3. S22 Settings
- Sync disabled
- Always-On Display - Tap to show
- NFC, Location, off when not in use
- Power Saving mode 24/7
I am seriously tempted to get a Pixel 5 instead, which I am willing to sacrifice the performance + 120Hz because I'm just another daily user.
Is there a way to underclock Snapdragon 8 Gen 1?
Let us hear your thoughts too. Thanks.
Which s22 model do you have?
Also I felt like I got more battery drain with adaptive battery off so I kept it on but slept all apps except ones i need notifications for
I have the 901e and updated to the Vietnamese firmware avdf running very similar set up to you getting 7 - 9h sot
Try removing that optimiser and using the doze setting in galaxy max hz
Also 96hz works with power saving on
Get galaxy app booster it's with in good guardians (can just download the apks online if you can't find it in the galaxy store) from what I've read it wipes dalvik cache
I'm on S22 SM-910E/DS.
I see... I'll give it a try on your suggestions!
But do you still face quite abit of heat during screen on and using of phone after the tweaks?
Gymcode said:
I'm on S22 SM-910E/DS.
I see... I'll give it a try on your suggestions!
But do you still face quite abit of heat during screen on and using of phone after the tweaks?
Click to expand...
Click to collapse
No heat at all, also in battery powersave settings you can limit the CPU to 70% (in case you didn't know already) from what I can see in adb it's on even when powersaving isnt
Mine is an SM-S9010. I rooted it and did some work on it. I turned off cores, underclocked it, turned off adaptive battery and so on. With all the things I tried, the SOT differs from charge to charge. I stopped even gaming altogether on it. I managed to get 30 more minutes out of it.
So the average SOT for me sits at 4h. I've got the Prime core and the last Middle core turned off, the Little cores underclocked to 1.5GHz and the rest to 1.9. The phone still overheats but the drain is slightly better.
Then there's the idle drain. The main culprit is Google's notorious Play Services crap with its services framework and all the other Google BS. I even installed a module to let it be optimized/dozed. It worked half the time. The other half the drain was even higher than before so it did worse than good. Now I've got Battery Guru installed and this thing monitors everything I need, plus it has a lot of stuff embedded in it, like the Quick Doze mod, power saver and Sensors Off with the screen off, etc. I've got the Powersaver on after the screen turns off and Data saver, and the idle drain sits at ~1%/hour. It goes at 0.7-1%/h, during the night unless the Play Services start spasming again, and they tend to do that a lot. And before having someone suggest a fix, please don't. I tried them all. They're just temporary solving the issue.
So yeah, there's no way in HELL someone can convince me they get 7-9h SOT cause that's just silly and exaggerated lying for a reason I don't understand.
In a 20h time frame the battery will lose 30% while the phone is idling. That includes ~10% which goes to some music listening and calls. I'm then left with 70%. After cutting off the 10-15% at which I plug in the phone, I'm left with ~60% of actual battery for the SOT. That means ~2150mAh. The battery is simply too small to be capable of anything more.
If you watch hours of YouTube, yeah, the SOT will turn out better because you're barely touching the screen once in a while and the CPU does the bare minimum and nothing overheats or goes into seizure mode. And the longer you use it in a smaller time frame, the better the results. When you use it over a longer period of time, go from idle to active use, idle again, and so on, that's when things start to take shape, so to speak. Then the moment you start scrolling and loading and loading things on Reddit or TikTok for example, or you browse the web, switch between apps and so on, things also change. The CPU will jump from a range of frequencies and produce more heat. The battery will share some of that heat and thing will get hot relatively hot soon, especially if it's hot outside. That translates into even poorer battery performance cause the hotter it gets, the worse the active drain is. And also, the lower the percentage, the worse the drain is too, I have noticed since I got this piece of crap phone. But yeah, if outside it's hot AF, the phone will be hot too. Today here where I live it's 30C right now. Using this thing and doing nothing intensive on it still gets it hot. It's too small to dissipate heat properly. Those saying "not heat here" etc, it's not possible unless you live in a slightly colder climate.
Not to forget to mention, I debloated this thing, removing pretty much everything Samsung included and I left only their bare minimum BS. Did it solve anything? Yes and no. It's a small difference but definitely not as big as I was expecting. It mainly reduces the idle drain, but like I said, the difference is extremely minimal.
I used a Pixel 5 last year. It was a great little phone. The battery life was fantastic on that thing. It was basically the first phone I've ever had with such a great battery life. The I moved to an iPhone 13 Pro. The one was even better. I never had to worry about running out of battery. Then after getting bored with iOS, I preordered an S22. Did I even consider the battery life? Absolutely not.
In conclusion, if you keep trying to find a solution to the problem, you won't fix much. Thing might improve today but tomorrow you'll be disappointed again the cycle starts again the next day.
The 8 Gen 1 built on Samsung's 4nm architecture is absolutely rubbish. It's terrible in terms of efficiency and when you pair it with a tiny battery you get a Galaxy S22, the devil child sent on Earth to destroy your mental health.
So don't bother trying much. Just use the phone as is try to use it as is. Just have a power bank with you when you're away and you're fine. Otherwise you won't enjoy the phone one bit. I, for instance, got to a point where I took it out of the case and now I use it with just a screen protector and the rest completely unprotected. If I drop it and it gets smashed into a million pieces, I don't care. Cause this is the worst phone I've ever had In my life. It's hard to like.
dragos281993 said:
Mine is an SM-S9010. I rooted it and did some work on it. I turned off cores, underclocked it, turned off adaptive battery and so on. With all the things I tried, the SOT differs from charge to charge. I stopped even gaming altogether on it. I managed to get 30 more minutes out of it.
So the average SOT for me sits at 4h. I've got the Prime core and the last Middle core turned off, the Little cores underclocked to 1.5GHz and the rest to 1.9. The phone still overheats but the drain is slightly better.
Then there's the idle drain. The main culprit is Google's notorious Play Services crap with its services framework and all the other Google BS. I even installed a module to let it be optimized/dozed. It worked half the time. The other half the drain was even higher than before so it did worse than good. Now I've got Battery Guru installed and this thing monitors everything I need, plus it has a lot of stuff embedded in it, like the Quick Doze mod, power saver and Sensors Off with the screen off, etc. I've got the Powersaver on after the screen turns off and Data saver, and the idle drain sits at ~1%/hour. It goes at 0.7-1%/h, during the night unless the Play Services start spasming again, and they tend to do that a lot. And before having someone suggest a fix, please don't. I tried them all. They're just temporary solving the issue.
So yeah, there's no way in HELL someone can convince me they get 7-9h SOT cause that's just silly and exaggerated lying for a reason I don't understand.
In a 20h time frame the battery will lose 30% while the phone is idling. That includes ~10% which goes to some music listening and calls. I'm then left with 70%. After cutting off the 10-15% at which I plug in the phone, I'm left with ~60% of actual battery for the SOT. That means ~2150mAh. The battery is simply too small to be capable of anything more.
If you watch hours of YouTube, yeah, the SOT will turn out better because you're barely touching the screen once in a while and the CPU does the bare minimum and nothing overheats or goes into seizure mode. And the longer you use it in a smaller time frame, the better the results. When you use it over a longer period of time, go from idle to active use, idle again, and so on, that's when things start to take shape, so to speak. Then the moment you start scrolling and loading and loading things on Reddit or TikTok for example, or you browse the web, switch between apps and so on, things also change. The CPU will jump from a range of frequencies and produce more heat. The battery will share some of that heat and thing will get hot relatively hot soon, especially if it's hot outside. That translates into even poorer battery performance cause the hotter it gets, the worse the active drain is. And also, the lower the percentage, the worse the drain is too, I have noticed since I got this piece of crap phone. But yeah, if outside it's hot AF, the phone will be hot too. Today here where I live it's 30C right now. Using this thing and doing nothing intensive on it still gets it hot. It's too small to dissipate heat properly. Those saying "not heat here" etc, it's not possible unless you live in a slightly colder climate.
Not to forget to mention, I debloated this thing, removing pretty much everything Samsung included and I left only their bare minimum BS. Did it solve anything? Yes and no. It's a small difference but definitely not as big as I was expecting. It mainly reduces the idle drain, but like I said, the difference is extremely minimal.
I used a Pixel 5 last year. It was a great little phone. The battery life was fantastic on that thing. It was basically the first phone I've ever had with such a great battery life. The I moved to an iPhone 13 Pro. The one was even better. I never had to worry about running out of battery. Then after getting bored with iOS, I preordered an S22. Did I even consider the battery life? Absolutely not.
In conclusion, if you keep trying to find a solution to the problem, you won't fix much. Thing might improve today but tomorrow you'll be disappointed again the cycle starts again the next day.
The 8 Gen 1 built on Samsung's 4nm architecture is absolutely rubbish. It's terrible in terms of efficiency and when you pair it with a tiny battery you get a Galaxy S22, the devil child sent on Earth to destroy your mental health.
So don't bother trying much. Just use the phone as is try to use it as is. Just have a power bank with you when you're away and you're fine. Otherwise you won't enjoy the phone one bit. I, for instance, got to a point where I took it out of the case and now I use it with just a screen protector and the rest completely unprotected. If I drop it and it gets smashed into a million pieces, I don't care. Cause this is the worst phone I've ever had In my life. It's hard to like.
Click to expand...
Click to collapse
Sorry to disappoint but I'm not being silly nor lying, I have absolutely no reason too i have nothing to prove or anyone to impress by talking s***, I'd be here doing the same if my battery was rubbish which it was to start with. I don't get any over heating, phone drains roughly 3% over night and barely get any google services wakelocks so you can believe what you want i really dont care what you think I'll chill here happily with a mint running s22 with plenty of sot
skinza said:
Sorry to disappoint but I'm not being silly nor lying, I have absolutely no reason too i have nothing to prove or anyone to impress by talking s***, I'd be here doing the same if my battery was rubbish which it was to start with. I don't get any over heating, phone drains roughly 3% over night and barely get any google services wakelocks so you can believe what you want i really dont care what you think I'll chill here happily with a mint running s22 with plenty of sot
Click to expand...
Click to collapse
It's fine. It's like a described it though. A continuous run of usage with with barely any stops or very short ones, will offer better stats. That's "very light" usage. Anyone complaining about battery life is doing a lot more on their phone just like me, the one who created this thread and the majority of S22 owners, with both variants of the phones.
Sorry if I offended you. You wouldn't be able to get the same SOT with our usage though, not even close, especially of you're 100% on cellular data.
dragos281993 said:
Mine is an SM-S9010. I rooted it and did some work on it. I turned off cores, underclocked it, turned off adaptive battery and so on. With all the things I tried, the SOT differs from charge to charge. I stopped even gaming altogether on it. I managed to get 30 more minutes out of it.
So the average SOT for me sits at 4h. I've got the Prime core and the last Middle core turned off, the Little cores underclocked to 1.5GHz and the rest to 1.9. The phone still overheats but the drain is slightly better.
Then there's the idle drain. The main culprit is Google's notorious Play Services crap with its services framework and all the other Google BS. I even installed a module to let it be optimized/dozed. It worked half the time. The other half the drain was even higher than before so it did worse than good. Now I've got Battery Guru installed and this thing monitors everything I need, plus it has a lot of stuff embedded in it, like the Quick Doze mod, power saver and Sensors Off with the screen off, etc. I've got the Powersaver on after the screen turns off and Data saver, and the idle drain sits at ~1%/hour. It goes at 0.7-1%/h, during the night unless the Play Services start spasming again, and they tend to do that a lot. And before having someone suggest a fix, please don't. I tried them all. They're just temporary solving the issue.
So yeah, there's no way in HELL someone can convince me they get 7-9h SOT cause that's just silly and exaggerated lying for a reason I don't understand.
In a 20h time frame the battery will lose 30% while the phone is idling. That includes ~10% which goes to some music listening and calls. I'm then left with 70%. After cutting off the 10-15% at which I plug in the phone, I'm left with ~60% of actual battery for the SOT. That means ~2150mAh. The battery is simply too small to be capable of anything more.
If you watch hours of YouTube, yeah, the SOT will turn out better because you're barely touching the screen once in a while and the CPU does the bare minimum and nothing overheats or goes into seizure mode. And the longer you use it in a smaller time frame, the better the results. When you use it over a longer period of time, go from idle to active use, idle again, and so on, that's when things start to take shape, so to speak. Then the moment you start scrolling and loading and loading things on Reddit or TikTok for example, or you browse the web, switch between apps and so on, things also change. The CPU will jump from a range of frequencies and produce more heat. The battery will share some of that heat and thing will get hot relatively hot soon, especially if it's hot outside. That translates into even poorer battery performance cause the hotter it gets, the worse the active drain is. And also, the lower the percentage, the worse the drain is too, I have noticed since I got this piece of crap phone. But yeah, if outside it's hot AF, the phone will be hot too. Today here where I live it's 30C right now. Using this thing and doing nothing intensive on it still gets it hot. It's too small to dissipate heat properly. Those saying "not heat here" etc, it's not possible unless you live in a slightly colder climate.
Not to forget to mention, I debloated this thing, removing pretty much everything Samsung included and I left only their bare minimum BS. Did it solve anything? Yes and no. It's a small difference but definitely not as big as I was expecting. It mainly reduces the idle drain, but like I said, the difference is extremely minimal.
I used a Pixel 5 last year. It was a great little phone. The battery life was fantastic on that thing. It was basically the first phone I've ever had with such a great battery life. The I moved to an iPhone 13 Pro. The one was even better. I never had to worry about running out of battery. Then after getting bored with iOS, I preordered an S22. Did I even consider the battery life? Absolutely not.
In conclusion, if you keep trying to find a solution to the problem, you won't fix much. Thing might improve today but tomorrow you'll be disappointed again the cycle starts again the next day.
The 8 Gen 1 built on Samsung's 4nm architecture is absolutely rubbish. It's terrible in terms of efficiency and when you pair it with a tiny battery you get a Galaxy S22, the devil child sent on Earth to destroy your mental health.
So don't bother trying much. Just use the phone as is try to use it as is. Just have a power bank with you when you're away and you're fine. Otherwise you won't enjoy the phone one bit. I, for instance, got to a point where I took it out of the case and now I use it with just a screen protector and the rest completely unprotected. If I drop it and it gets smashed into a million pieces, I don't care. Cause this is the worst phone I've ever had In my life. It's hard to like.
Click to expand...
Click to collapse
Thank you for this. Probably the most honest review about S22's battery. Like you I tried everything under the sun (except the rooting and underclocking). This phone is just disappointing. I could relate to every single line as I read through your post. Weirdly, I'm just happy to know that Im not the only one feeling this way about this "flagship" device.
I'm coming from a very old OnePlus6 which STILL works perfectly fine on a custom Android with close to 4-5 hours of SOT in a full days usage. I charge it only in the night, sometimes it even makes it through the night..
I thought S22 with a higher battery (and NEW) will at least give 6 hours SOT but man was I wrong!!
So initially I used Smart Switch, and I got a terrible SOT of 1-2.
I did factory reset and manually set up the phone and I got about 3 hours of SOT.
I went through the debloating process and now I'm 3-4 hours of SOT.. Still that is so horrible for a flagship!
Its such a let down honestly! I get a flagship and paid so much money and this is such a huge issue! And I hate the font size on the notifications/panel.. it is just not proportional to the overall system font size! And not to forget, the phones takes about 1-1.5 hours to charge. Such a pain when are used to the OnePlus DashCharge which blazes through. Fast Charge on Samsung is such a shame
S22 is seeming to be a mistake. I'm considering swapping this for a Oneplus 10 Pro OR an iPhone 13! You made a similar switch? Looking for advice on fixing this brick of a phone or recommendation on alternate device.
Maybe custom ROMs or Updates in the future will make S22 better?
Edit: I too have a SM-S9010
syedtahir16 said:
Thank you for this. Probably the most honest review about S22's battery. Like you I tried everything under the sun (except the rooting and underclocking). This phone is just disappointing. I could relate to every single line as I read through your post. Weirdly, I'm just happy to know that Im not the only one feeling this way about this "flagship" device.
I'm coming from a very old OnePlus6 which STILL works perfectly fine on a custom Android with close to 4-5 hours of SOT in a full days usage. I charge it only in the night, sometimes it even makes it through the night..
I thought S22 with a higher battery (and NEW) will at least give 6 hours SOT but man was I wrong!!
So initially I used Smart Switch, and I got a terrible SOT of 1-2.
I did factory reset and manually set up the phone and I got about 3 hours of SOT.
I went through the debloating process and now I'm 3-4 hours of SOT.. Still that is so horrible for a flagship!
Its such a let down honestly! I get a flagship and paid so much money and this is such a huge issue! And I hate the font size on the notifications/panel.. it is just not proportional to the overall system font size! And not to forget, the phones takes about 1-1.5 hours to charge. Such a pain when are used to the OnePlus DashCharge which blazes through. Fast Charge on Samsung is such a shame
S22 is seeming to be a mistake. I'm considering swapping this for a Oneplus 10 Pro OR an iPhone 13! You made a similar switch? Looking for advice on fixing this brick of a phone or recommendation on alternate device.
Maybe custom ROMs or Updates in the future will make S22 better?
Edit: I too have a SM-S9010
Click to expand...
Click to collapse
I doubt anything will improve things the way we want. Unless we see a complete revamp of how apps use the CPU, which is a deep optimization process, that should done by Google all the way to a system level, things simply cannot improve in such a drastic way. After doing some math, a 1% idle drain or 15-20% active drain is something relatively decent because it's based on the battery inside the phone. The real capacity of the 3700mAh is actually 3590. So it's even worse than it appears. We've got to accept in the end that Samsung ****ed up this year with the smaller phone, despite the sales numbers.
Anyway, I also had a OP6 which I really liked until the software went completely 180 and disappointed me with that insane redesign which went against everything OP started with.
Anyway, back to the S22. I'm not really bothered by the charging speed. However, considering the terrible battery life, a much quicker charging speed was rudimentary to compensate for the other thing. Samsung doesn't give a **** though. So long as business gets better.
The bottom line is, and I reached to this conclusion the hard way cause I can say that I lost a lot of money in market value in the past 3 years, is that in the Android world, if you want a flagship device with very good battery life, you've got to go big. Otherwise you'll be disappointed. On iOS, you can get that with the smaller phones. Choosing the bigger phone in that situation, will get you the best battery life on the entire phone market. Android needs more mAh to compensate for sudden idle drain, services that have seizures out of the blue and the regular active drain due to poor app optimization. The bigger the battery, the more mAh for those unexpected things to eat and the less you'll have to worry about the battery life, as long as it easily gets you through the day. But if you want to keep using a smaller phone, something that actually fits in your pocket, then I'm afraid only Apple can offer you the best. iOS is in a completely different league in terms of optimization. Not to mention how perfectly smooth everything in every corner is. That is the true definition of buttery smooth no matter the action you do and no matter the app you're using. On Android frame drops/stutters are a regular and no matter the phone I used, they've always been there, despite the claims. I guess I've got more sensitive eyes. Even so, on iOS, those frame drops are so rare, that you really get a truly delightful experience 99% of the times. Not to mention that the 120Hz experience on iOS is actually smoother than the 120Hz on Android, if that makes any sense. All the polish the OS receives is very noticeable on that 120Hz panel. The way the OS works is what you need to get used to, the restrictions and so on. If you can get past that, you're good to go.
So if you want to throw away the S22, thing that I wouldn't blame you for, a 13 Pro is what I'd suggest to you, if you wanna keep using a small phone but if you want the best of the best, go with the Max brick version.
I'm personally waiting for the 14 lineup and I'm most confident I'm gonna get the 14 Pro Max. I want to never worry about battery life. For me it's 2 big compromises I have to accept: iOS and the phone size.
dragos281993 said:
I doubt anything will improve things the way we want. Unless we see a complete revamp of how apps use the CPU, which is a deep optimization process, that should done by Google all the way to a system level, things simply cannot improve in such a drastic way. After doing some math, a 1% idle drain or 15-20% active drain is something relatively decent because it's based on the battery inside the phone. The real capacity of the 3700mAh is actually 3590. So it's even worse than it appears. We've gonna accept in the end that Samsung ****ed up this year with the smaller phone, despite the sales numbers.
Anyway, I also had a OP6 which I really liked until the software went completely 180 and disappointed me with that insane redesign which went against everything OP started with.
Anyway, back to the S22. I'm not really bothered by the charging speed. However, considering the terrible battery life, a much quicker charging speed was rudimentary to compensate for the other thing. Samsung doesn't give a **** though. So long as business gets better.
The bottom line is, and I reached to this conclusion the hard way cause I can say that I lost a lot of money in market value lost in the past 3 years, is that in the Android world, if you want a flagship device with very good battery life, you've got to go big. Otherwise you'll be disappointed. On iOS, you can get that with the smaller phones. Choosing the bigger phone in that situation, will get you the best battery life on the entire phone market. Android needs more mAh to compensate for sudden idle drain, services that have seizures out of the blue and the regular active drain due to poor app optimization. The bigger the battery, the more mAh for those unexpected things to eat and the less you'll have to worry about the battery life as long as it easily gets you through the day. But if you want to keep using a smaller phone, something that actually fits in your pocket, then I'm afraid only Apple can offer you the best. iOS is in a completely different league in terms of optimizations. Not to mention how perfectly smooth everything in every corner is. That is the true definition of buttery smooth no matter the action you do and no matter the app you're using. On Android frame drops/stutters are a regular and no matter the phone I used, they've always been there, despite the claims. I guess I've got more sensitive eyes. Even so, on iOS, those frame drops are so are, that you really get a delightful experience 99% of the times. Not to mention that the 120Hz experience on iOS is actually smoother than 120Hz on Android, if that makes any sense. All the polish the OS receives is very noticeable on that 120Hz panel. The way the OS works is what you need to get used to, the restrictions and so on. If you can get past that, you're good to go.
So if you want to throw away the S22, thing that I wouldn't blame you for, a 13 Pro is what I'd suggest to you, if you wanna keep using a small phone but if you want the best of the best, go with the Max brick version.
I'm personally waiting for the 14 lineup and I'm most confident I'm gonna get the 14 Pro Max. I want to never worry about battery life. For me it's 2 big compromises I have to accept: iOS and the phone size.
Click to expand...
Click to collapse
Well, I guess that's what I'm planning to do too. Wait for the next iPhone. Until then I'll keep charging my S22.. and who knows maybe some miracle update from samsung will fix its battery time!
syedtahir16 said:
Well, I guess that's what I'm planning to do too. Wait for the next iPhone. Until then I'll keep charging my S22.. and who knows maybe some miracle update from samsung will fix its battery time!
Click to expand...
Click to collapse
Ha Ha! I don't believe in miracles. A company that decides to address the issue by creating a mod or something to replace the back glass with something else that fits a bigger battery inside. That is a miracle to me
Thing is, the more you try to optimize this phone, the worse it gets
This is also the case for the adaptive battery that samsung has put on.
Sure you'll get good sot on any phone if you're locked in an app at low brightness for few hours that just scrolls through or plays videos.
But as soon as you start auto killing running apps and do multitasking with them after that, you'll barely get 2-3 hours sot.
Best I got from the exynos version on this was about 4.5 hours SOT with all settings I need enabled and gw4 conected to it.
But the average days (phone outside on higher brightness) are way below that. Using the doze mode when screen off, fingerprint disabled when screen is off, most of the bloatware /junk apps disabled or put in deep sleeping mode. (no root). I keep my phone at 85% and recharge when Im home/office whenever possible
Iphone really naied this down since the by just freezing the active proceeses for the standby adavantage.
The cpu doesnt really have to do anything when you relaunch them.
Im quite surprised android cannot do the same in 2022
Such a shame, this would've been the perfect compact phone if the software was done right on it.
But where is the $$$ for google/samsung for tracking everything you do ?
No matter what settings you try to disable, the phone constantly scans for gps/wifi/bluetooth devices (google's gms even claims this is for covid purposes in their TOS now)
Thank you everyone for the debate above. Understand that battery differs from one another, it seems that most people probably belongs to the side where the battery is insufficient to last through the day, or barely.
I love this phone so so much, and I got the Graphite model.
I hate to say goodbye, but I'll be going back to Pixel 5, and hoping S24, or whatever, will be a more optimized S22, keeping the compact phone size.
I use a snapdragon gen 1 s22. The battery is not terrible but also not great. An SOT of 3hrs for 3 days standby is what i get with max hz app installed, power saving on, debloated, sync on for two mailboxes. I get more SOT with less standyby time( if i watch youtube videos). I think its a nice balance for a compact phone. I had the pixel 6 before this but it was too heavy and big though the battery was slightly better.
Gymcode said:
Thank you everyone for the debate above. Understand that battery differs from one another, it seems that most people probably belongs to the side where the battery is insufficient to last through the day, or barely.
I love this phone so so much, and I got the Graphite model.
I hate to say goodbye, but I'll be going back to Pixel 5, and hoping S24, or whatever, will be a more optimized S22, keeping the compact phone size.
Click to expand...
Click to collapse
You can get a Pixel 5 in mint condition for extremely cheap. I also looked up one cause I'm really considering getting one.
dragos281993 said:
You can get a Pixel 5 in mint condition for extremely cheap. I also looked up one cause I'm really considering getting one.
Click to expand...
Click to collapse
Im a pixel fanboy. But recently with the bugs, poor call quality and the random battery drains i chose to move on. I hate the material you in android 12. Atleast i need an option to switch it off. I cant root as i need to use bank apps in my phone.
Here is a screen shot of my s22's battery usage for the past two days.
dragos281993 said:
You can get a Pixel 5 in mint condition for extremely cheap. I also looked up one cause I'm really considering getting one.
Click to expand...
Click to collapse
Yup I got one myself now. Only downside is the under display firing top speaker which makes the volume thin and muffled. Other than that, I'm very happy with the phone!
And for god-knows-what reason, Pixel 5 rocks a 4080 mAh battery. Wonder why tf S22 weighs heavier and unable to carry a bigger battery. Bells and whistles, but neglected this basic need of a phone
Gymcode said:
Yup I got one myself now. Only downside is the under display firing top speaker which makes the volume thin and muffled. Other than that, I'm very happy with the phone!
And for god-knows-what reason, Pixel 5 rocks a 4080 mAh battery. Wonder why tf S22 weighs heavier and unable to carry a bigger battery. Bells and whistles, but neglected this basic need of a phone
Click to expand...
Click to collapse
If im not wrong the pixel 5 is made of aluminum(sides and back) but the S22 is made of glass(back). Thats the reason for the weight difference.
Sman999 said:
If im not wrong the pixel 5 is made of aluminum(sides and back) but the S22 is made of glass(back). Thats the reason for the weight difference.
Click to expand...
Click to collapse
That is true. But SN8Gen1 is too much to handle for a reduced battery size. I'll go to Samsung shop to see how S22+ feels in the hand, as the battery size is bigger. But for now I'll stick with Pixel 5.