Related
Anyone have any views on which of all roms and official releases have best battery?
i think best gingerbread rom is iceandfire
As far as battery life is concerned, my oppinion, nothing beats a clean stock Eclair (official), followed closely by a clean stock Froyo (official). All mods are great, but battery life is better in the official ROMs in my own experience.
HinotoriBR said:
As far as battery life is concerned, my oppinion, nothing beats a clean stock Eclair (official), followed closely by a clean stock Froyo (official). All mods are great, but battery life is better in the official ROMs in my own experience.
Click to expand...
Click to collapse
Are you serious?
iceandfire v2.1 is the best ROM I've found so far in terms of battery life. Don't know why, but it just lasts SO long!
I use ice and fire loads its good but I wish it could be a lot better, testing froyomod now, am considering buying a new phone mainly for battery life as the milestones is sooo bad!
Sent from my Milestone using XDA Premium App
mcdevtingz said:
Anyone have any views on which of all roms and official releases have best battery?
i think best gingerbread rom is iceandfire
Click to expand...
Click to collapse
As mentioned, nothing beats Eclair. And if we talk about Eclair, nothing beats Telus Lite.
I have CM7 installed.
Your battery mileage may vary depending on your usage habits... But I'm typically a pretty heavy user. Lots of Angry Birds/other games, surfing, Pandora, etc. I go to sleep at around 11pm with my phone unplugged at a full charge (100%), and I can use my phone until the next day mid to late afternoon - that's about 15-18 hours. Granted, a lot of it is when I'm asleep (until about 7am) and during my working hours, but it's still pretty decent considering how I use the phone. ESPECIALLY with all I've heard about CM7 having terrible battery life.
I DO have several apps and tweaks to try to lengthen my battery life though...
Some things you can do:
- install "Network Switcher" from the market. You can set conditions between certain hours and the screen off to turn off WiFi and 3G. I have mine set turn off all data between 11:15pm and 7:15am when the screen is off.
- install the "Toggle 2G" app. This automatically switches the phone to 2G mode when the screen is off. 2G typically sucks less juice than 3G. (get it here: http://forum.xda-developers.com/showthread.php?t=739530)
- tweak your /system/build.prop file so your wifi scan interval is a higher number. I have mine set to 360 seconds (that's 6 minutes). I don't know about you, but I don't need my wifi scanning every 15 seconds for an open or known signal.
- also in the build.prop file; change your ro.telephony.default_network setting from 3 to 0. 3 means GSM/WCDMA mode; 0 means WCDMA preferred. From everything I've read, WCMDA preferred tends to switch signal types less often, which benefits your battery.
Heck, even if you DON'T have a Milestone w/CM7 installed, these tweaks can help immensely with your battery life.
Froyo should beat out Gingerbread... They're roughly equal for me, but the memory issues of GB make me have to keep my phone on longer to wait for tasks to complete, thus draining more battery overall.
pippocannelunghe said:
Are you serious?
Click to expand...
Click to collapse
Yep, I've tried pretty much any Froyo and/or Ginger Bread mods (and I've specially liked CM7 / ShadowMOD, but all other ROMs are great as well), no one is close to the stock Froyo as far as battery life is concerned. But, I have to say, it is not absolutely stock, but, with exactly the same VSEL/CLOCK settings I've tried in other roms (which save some battery since it uses lower vsel).
HinotoriBR said:
Yep, I've tried pretty much any Froyo and/or Ginger Bread mods (and I've specially liked CM7 / ShadowMOD, but all other ROMs are great as well), no one is close to the stock Froyo as far as battery life is concerned. But, I have to say, it is not absolutely stock, but, with exactly the same VSEL/CLOCK settings I've tried in other roms (which save some battery since it uses lower vsel).
Click to expand...
Click to collapse
Have u tried the ROM that is banned from XDA yet?
dmo580 said:
Froyo should beat out Gingerbread... They're roughly equal for me, but the memory issues of GB make me have to keep my phone on longer to wait for tasks to complete, thus draining more battery overall.
Click to expand...
Click to collapse
Have u tried AutoKiller Memory Optimizer with my recommended settings (see video below)?
http://youtu.be/z1vBcNsDkn0
mcdevtingz said:
I use ice and fire loads its good but I wish it could be a lot better, testing froyomod now, am considering buying a new phone mainly for battery life as the milestones is sooo bad!
Sent from my Milestone using XDA Premium App
Click to expand...
Click to collapse
Get either an extra battery or extended battery if u are a heavy user.
pcphobic said:
Have u tried AutoKiller Memory Optimizer with my recommended settings (see video below)?
http://youtu.be/z1vBcNsDkn0
Click to expand...
Click to collapse
That doesn't come remotely close to the V6 SuperCharger script.
The minfree levels is only one aspect of it.
AKMO doesn't fix groupings or priorities.
With those settings, all your apps are getting killed at 28 mb - because of the screwy groupings they are in the 5th slot while slot 3 are 4 are basically empty holes.
And that whole "banned rom" spiel is getting pretty annoying.
I'd bet money that HONO's SuperCharged CM7 kicks Cronos' ass with those AKMO settings.
zeppelinrox, have I offended u in anyway?
I have even introduced your method to calibrate battery to other people.
Why do u need to reply in such an arrogant and nasty tone towards me?
I agree with zeppelinrox, running his V6 supercharge scripts work wonders.
And no matter what ROM I use, i always use SetCPU to auto-adjust the processor speed based on certain scenarios. For example, I'm using CM7 right now, which auto overclocks to 1000mhz. That's great for performance but crappy on the battery. However, with SetCPU I can force the CPU to run between 250mhz and 400mhz when the screen is turned off. There's simply no need to let it go up to 1000mhz if I'm not even using the thing! Calls still come through fine, as do emails and messages. But it really extends your battery life. You can go as low as 125mhz, but then things do start messing up. As soon as the screen turns on, the phone is automatically allowed to run at 1000mhz again.
It's also useful for when your phone gets really hot, as a precaution. If my phone reaches 42*C it automatically underclocks as well. I picked that number out of a hat though. It's just a number I felt was too hot based on my own experience with the phone.
SetCPU:
https://market.android.com/details?id=com.mhuang.overclocking&feature=search_result
pcphobic said:
zeppelinrox, have I offended u in anyway?
I have even introduced your method to calibrate battery to other people.
Why do u need to reply in such an arrogant and nasty tone towards me?
Click to expand...
Click to collapse
I think you're reading too much into it. I didn't think he was being arrogant/nasty. He was just being straight forward.
Just my 2 cents though
No not offended.
Everybody knows that gingerbread memory management is screwed up and fiddling with minfree levels alone ain't fixing anything.
AKMO alone does nothing to fix memory management it doesn't even tell you what apps are where.
One set of settings on one rom has a totally different effect on another rom.
The groupings in CM6 and froyo mod are nothing like CM7 and Cronos.
So those settings would make froyo roms dog slow but are kind of aggressive in CM7 and Cronos and of course do nothing to make the launcher more responsive in both cases.
The only way to know what kind of effect minfree levels would have is if you know where the apps are.
And the only way to be certain of where they are is to tell android where to put them.
Which is why the SuperCharger script works on all roms the same way... it puts apps in their place so that the OS will run in a predetermined and predictable fashion and therefore the lowmemorykiller settings will have the exact effect that the user expects.
So no, I'm not offended.
But kind of annoyed that I spent quite a number of weeks perfecting it and somebody who knows this is fiddling around with AKMO settings while they really truly can have a phone with fixed memory management.
btw, if you check the memory groupings with AMM, you will see that AKMO is annoyingly in memory way too often. Which is ridiculous.
zeppelinrox said:
No not offended.
Everybody knows that gingerbread memory management is screwed up and fiddling with minfree levels alone ain't fixing anything.
AKMO alone does nothing to fix memory management it doesn't even tell you what apps are where.
One set of settings on one rom has a totally different effect on another rom.
The groupings in CM6 and froyo mod are nothing like CM7 and Cronos.
So those settings would make froyo roms dog slow but are kind of aggressive in CM7 and Cronos and of course do nothing to make the launcher more responsive in both cases.
The only way to know what kind of effect minfree levels would have is if you know where the apps are.
And the only way to be certain of where they are is to tell android where to put them.
Which is why the SuperCharger script works on all roms the same way... it puts apps in their place so that the OS will run in a predetermined and predictable fashion and therefore the lowmemorykiller settings will have the exact effect that the user expects.
So no, I'm not offended.
But kind of annoyed that I spent quite a number of weeks perfecting it and somebody who knows this is fiddling around with AKMO settings while they really truly can have a phone with fixed memory management.
btw, if you check the memory groupings with AMM, you will see that AKMO is annoyingly in memory way too often. Which is ridiculous.
Click to expand...
Click to collapse
Ah yes, now your tone of voice is much better... more professional and more matured as compared to when u said wrote b4.
Thank you for clearing this up.
Hope to see you back in Cronos forum as I recalled how much u were impressed with Cronos Ginger.
Best Battery -> Official 2.1-update1. Simple as that.
pcphobic said:
Hope to see you back in Cronos forum as I recalled how much u were impressed with Cronos Ginger.
Click to expand...
Click to collapse
I check it out time to time.
Cronos is good and feeyo is cool but lack of updates, v1.2 had issues plus I needed to test other roms.
Btw the memory managent on cm7 and cronos mimics my strategy from v5 anyway - which was to give the laubcher its own OOM grouping/slot but everything else is just weirdly placed far down the list so still not as good as v5.
Tthen V6 simply out does v5 hands down.
Sent from my Milestone using Tapatalk
I've been using the note for a few days now, i've noticed that it heats up quite a lot. Under charging it is understandable... But even when the screen is on for is say 10-15 mins straight... Does anyone elses phone heat up too?
Sent from my GT-N7000 using XDA App
yep, every smartphone I have used does that (GS1,GS2, Note, Tab 7" tab 10.1) and some feature phones do it (iPhone, HTC wildfire etc).
Think about it, dual core 1400mhz running, and batteries always heat up with heavy drain and charging.
Mine has normal temperature under regular use (IE a browser etc. - not really causing higher load), gets quite warm if playing a game for example (higher load, not sure how high).
How long does your battery last? (heat = energy)
I used to have over heat issues but eversince i use franco's kernel 6 the issue has gone away.
i use sfock LA4 with root, bloatware removed and franco's kernel. all good and no heatind issues even when charging.
There is an app called "Elixir" that can monitor the temp of the various sensors within the phone. I've used it on every device I put a custom kernel on. Setup a homescreen widget so you can see the temp at all times. If it tops 45c then you panic a little and let it cool down
which rom and kernel did u use?
Mine heats up only when I charge. I don't mind, I like warm stuff.
Mine gets pretty warm too, especially at extensive use and charging at the same time.
yeah mine gets warm too, especially when browsing using Dolphin browser. The highest temp it touch is 51 degrees. Other than that it quite ok. Usually temp between 28-31 degrees.
When I was on stock rom and connected to gps +charging at the same time, my note used to heat up to extreme temperatures. enough to make me want to shut it off to avoid any hardware damage to internal circuit. It used to become burning hot at the top part of the phone. Now I have LA4 rooted stock rom with bloatware removed and using franco's kernel #6. Now my phone barely gets warm when I am charging and using gps at the same time.
aftabbabar said:
When I was on stock rom and connected to gps +charging at the same time, my note used to heat up to extreme temperatures. enough to make me want to shut it off to avoid any hardware damage to internal circuit. It used to become burning hot at the top part of the phone. Now I have LA4 rooted stock rom with bloatware removed and using franco's kernel #6. Now my phone barely gets warm when I am charging and using gps at the same time.
Click to expand...
Click to collapse
I am on rooted la4.
Exactly what is safe to remove in terms of "bloatware"?
Did you just flash franco kernal 6 with mobile odin over the rooted la4?
Yes, my phone used to heat to levels you couldn't even hold it or touch the screen or your finger would burn. That happened with GPS or PocketCloud. After putting up Franco's kernel, heating is totally gone.
Sent from my NotePhone
flash francos kernel in recovery from cwm. I deleted all samsung apps and all the apps i wll never use. the list is long. there are threads where people list the apps that can be safely removed.
I'm in the boat as gent0r mine will get fairly warm when used under heavy work and charging. But its alarming at this point. Not like sarius where he thought it was melting his case!
Sent from my Xoom using XDA App
mine always with <50c still acceptable for me
I used Franco's latest kernel and my Note's temperature suddenly went up.. it raised the heat more...
I reflash back to Abyss Note and the temperature is back to Normal again..
Usually heating issues are caused
1.) when your using Data Connection thru Carrier (surfing, auto-syncing emails, news feeds, twitter, facebook and etc.)
2.) when your playing graphic extensive games
3.) and lastly when your Note's display is always ON, all the time (like watching movies all the time.)
mine doesnt really heat up, except one time when using titanium backup. the process just stopped and the phone got extremely hot.
it never does that in normal usage though
we must remember we are taking battery temperature as an indication to CPU temperature. In reality your CPU could be getting fried at 50 degrees battery temp depending on circumstances. We news to access the CPU temp sensor if there is one. Does the phone shut off when overheating? Like a failsafe? Or is it just the hardware failing?
Edit - the reason I say this is I remember on the n900 forums a guy dismantled his overclocked phone which was dependent on battery temperature (safe temperatures were established and overclock was dependent on battery temp) and when he saw the state of the main board and scorching around the CPU he was very shocked.
Sent from my GT-N7000 using XDA App
letters_to_cleo said:
I used Franco's latest kernel and my Note's temperature suddenly went up.. it raised the heat more...
I reflash back to Abyss Note and the temperature is back to Normal again..
Usually heating issues are caused
1.) when your using Data Connection thru Carrier (surfing, auto-syncing emails, news feeds, twitter, facebook and etc.)
2.) when your playing graphic extensive games
3.) and lastly when your Note's display is always ON, all the time (like watching movies all the time.)
Click to expand...
Click to collapse
Its always best to reboot 2 or 3 times after flashing a new rom or kernel. Also wiping cache n dalvik helps.
While flashing new kernel, always use kernel cleaning script. I have been using battery indicator pro till now, will try the mentioned sw 'elixir' n see the difference.
Franco v2, speedmod v1 are better kernels imo.
Moved To Q&A
Please post all questions in the Q&A section
My Moto X randomly started lagging heavily. It's unbearable.
It's not just a little bit here and there, the entire system is EXTREMELY LAGGY. It takes 30 seconds for the device to register a touch or perform an action.
I have root + stock ROM + gravitybox + very minimal third-party apps.
What the hell is going on?
Download an app that keeps track of CPU and RAM usage for each app. One of your apps may be keeping one or both of those at close to 100% usage and slowing it way down.
Sent from my XT1049 using Tapatalk
DonDizzurp said:
My Moto X randomly started lagging heavily. It's unbearable.
It's not just a little bit here and there, the entire system is EXTREMELY LAGGY. It takes 30 seconds for the device to register a touch or perform an action.
I have root + stock ROM + gravitybox + very minimal third-party apps.
What the hell is going on?
Click to expand...
Click to collapse
Many things could cause it. Backgrounded app crashing over and over (loop), malware (very unlikely), weird software conflicts, perhaps you froze an app that the system is trying to wake non stop, etc. Might be faster just to backup, RSDlite and restore. Titanium Backup and Ultimate Backup make it very easy with batch backups/restore. 2 key inputs backs up all your apps and 2 restores them lol. It's ridiculously easy
Also make sure you're not running battery saving mode, I imagine that caps your max clock speed to a lower value although it shouldn't cause THAT big of a performance hit.
Apps like BetterBattery stats or GSAM can also show you what's hammering your battery in the background and occupying your CPU cycles. I would take a quick peak at those tools first before I decide how to approach the situation.
What's happening is some app or software conflict is polling (sending commands to) your CPU non stop so when you interact with your phone each key press/swipe/action is put into what is now a long queue for the CPU to process it. Kind of like a lineup at a coffee shop in the morning, you wanna get in and out fast but they gotta serve the people in front of you first.
scorpion667 said:
Many things could cause it. Backgrounded app crashing over and over (loop), malware (very unlikely), weird software conflicts, perhaps you froze an app that the system is trying to wake non stop, etc. Might be faster just to backup, RSDlite and restore. Titanium Backup and Ultimate Backup make it very easy with batch backups/restore. 2 key inputs backs up all your apps and 2 restores them lol. It's ridiculously easy
Also make sure you're not running battery saving mode, I imagine that caps your max clock speed to a lower value although it shouldn't cause THAT big of a performance hit.
Apps like BetterBattery stats or GSAM can also show you what's hammering your battery in the background and occupying your CPU cycles. I would take a quick peak at those tools first before I decide how to approach the situation.
What's happening is some app or software conflict is polling (sending commands to) your CPU non stop so when you interact with your phone each key press/swipe/action is put into what is now a long queue for the CPU to process it. Kind of like a lineup at a coffee shop in the morning, you wanna get in and out fast but they gotta serve the people in front of you first.
Click to expand...
Click to collapse
I've frozen a bunch of apps and it's been fine for months.
I also turned on CPU updates from developer options to see if anything is bogging it down. I don't see anything in battery stats either.
I wiped cache and dalvik cache and now it's fine. I've never had something like cache build-up cause this much of a problem before. Weird.
I tired the init script or the kernel switches - they both do the same thing really, write 'disabled' into qcom,bcl.39/mode file.
Which does nothing. I still get throttled down to 1958mhz with only two cores running. thermal-engine-shamu.conf has been fixed ages ago (and really that file by default has very mild throttling)
As you can imagine this lags the hell out of the phone and it's very annoying.
Running latest 6.0.1 stock image with all kinds of different kernels, including stock, making no difference. Even kernels that claim to disable or allow disable of BCL (like benzoCore) I get nothing. I am sometimes able to restore the clock speed cap, but not turn the cores on. Plugging into the charger sometimes restores cores and clock speeds instantly, sometimes doesn't. Charging to above 40% AND rebooting always restores them. Using zen hotplug to simplify things.
I'm pretty much ready to chuck this and get a 6P unless someone knows how to solve this?
I don't know if it is useful or even what you are looking for. There's a zip here on nexus forum called disable throttle. I flashed that and it resolved some issues.
Sent from my Nexus 6 using XDA-Developers mobile app
Edit. Here is what I use. Again not sure if this is what you are looking for. But thought I'd share in case it's something useful for you.
http://forum.xda-developers.com/nexus-6/development/mod-disable-throttling-battery-low-t3440814
Thank you. That first line from the OP is not really accurate unless older versions of Android throttled below 40% with the default thermal-engine.conf file. On 6.0.1, the thermal engine throttling kicks in at 25% and only for the GPU. The CPU isn't throttled at all until either at 15% or 10% (don't remember which). And I already have that zip flashed.
I'm pretty certain the 40% throttle, which is the problem I'm struggling with, is the BCL driver that cannot be turned off by just writing "disabled" into the mode file.
Frankly not sure why everyone isn't up in arms about this, because it makes the phone pretty damn unusable. I suspect there are a number of inputs which make a difference, so the majority people are not experiencing this. Maybe I have too high of a constant CPU load, so the throttle affects me more than others? Maybe BCL is being triggered by inputs from my failing battery (mine has about 85% of its original capacity left)? Some ROM versions don't do this? Who knows.. It seems a waste to upgrade when a non-throttled 6 would cover 95% of my use cases except for the lousy camera. I'll be replacing the battery soon so maybe that'll fix it.. fingers crossed.
*double post*
I'd it were me I'd buy a new battery. Also for camera. I know it's a hardware limitation your talking about but. But I use camera nx1. Modified Google camera I snagged from the apps and themes section here
Anyways. Not sure what I can mention to help. Other then that sucks. N6 is a great phone and it seems like some users just phonws with issues that others are not experiencing. Wish there was a solution for you. Sorry man.
Sent from my Nexus 6 using XDA-Developers mobile app
I bought my first Samsung phone in over 10 years, the Samsung S20 FE 4G with the Snapdragon chipset.
To my surprise the device is heating up very quickly while in use:
With light use, like messaging apps the CPU stays around 37 to 49°C,
While gaming it stays around 47 to 50°C+ (I believe the 60°C was the biggest temperature spike).
I've heard people saying that transferring data from your older phone via Smart Switch may cause this heating issue, but I don't think that should be a issue.
Lastly, I have no clue on how weather affects the phone's temperature.
Despite being winter, we're having temperatures around 40°C where I live, but even when the night comes and the temperature drops to around 20°C (right now it's 26°C and the CPU temperature is around 40°C, while I'm listening to music via Bluetooth and (re)writing this post) my phone still heats up (just not as much as in the rest of the day).
I think it's worth mentioning that the CPU temperature is also changing quickly, I don't know if that's normal or not but for instance, when I switch from one app to another, if the app I'm using to measure the device temperature (CPU Monitor) is to be believed, the temperature jumps some 2 to 5°C. It usually comes back down again, but I really don't know if that's normal.
I went to the Samsung store today, they checked, did some tests, and said that the temperature was at normal range, but they said that the temperature while switching between apps was a little strange.
They also said that their system detected a temperature spike caused by Fine Lock on the day that I bought the phone, which I find weird since it's only a launcher to the Good Lock apps, but nevertheless they advised me to uninstall it and keep monitoring the temperature for a few more days, and that if the device gets too hot (over 60°C), that I should go back again and ask for a replacement.
Anyway, should I give some time, should I worry about it, should I take it back to the store?
I have the same model as you and I haven't experienced any of the symptoms you are talking about. If I were you I'd return it and get another one. At least then you can be sure if it is normal or a defective device.
SmartSwitch isn't that smart especially between different OS's/devices.
I think you better start from the beginning...
Backup your contacts etc to the PC using cut/copy plus at least one other hdd.
Factory reset. Reload from scratch. Run factory loaded versions; do not update any at first.
Avoid enabling any power management at least at first.
See what you got and go from there.
It's likely not hardware at all but a bad configuration. Common with Samsungs and correctable.
Orcam said:
I have the same model as you and I haven't experienced any of the symptoms you are talking about. If I were you I'd return it and get another one. At least then you can be sure if it is normal or a defective device.
Click to expand...
Click to collapse
Thank you. I'm thinking about doing it. I've talked to some S20 FE owners who live in my country (which is a very hot country) and they said that the device temperatures are basically the same as theirs, but at the same time I'm still worried about it's long term effects since I plan to keep this phone for at least two years.
blackhawk said:
SmartSwitch isn't that smart especially between different OS's/devices.
I think you better start from the beginning...
Backup your contacts etc to the PC using cut/copy plus at least one other hdd.
Factory reset. Reload from scratch. Run factory loaded versions; do not update any at first.
Avoid enabling any power management at least at first.
See what you got and go from there.
It's likely not hardware at all but a bad configuration. Common with Samsungs and correctable.
Click to expand...
Click to collapse
Thank you, I did what you told me (except for flashing the factory stock ROM since I couldn't find it), I've only restored the apps using the Google backup, but didn't restore my settings. I've also did a mild debloat of the phone (removed Bixby and the Facebook apps) and while using the phone to browse through social media doesn't heat the phone as much as it used to, it still heats up more or less the same during gaming, so I'm guessing that might be normal.
Depending on how CPU cycle intensive the game is, it could normally use a fair amount of power.
Running background apps can make it noticeable worse though.
Try temporarily disabling Google play Services and see if that helps.
blackhawk said:
Depending on how CPU cycle intensive the game is, it could normally use a fair amount of power.
Running background apps can make it noticeable worse though.
Try temporarily disabling Google play Services and see if that helps.
Click to expand...
Click to collapse
It's Honking Impact 3rd, it's not intensive like PUBG or something like that, but can be intensive depending on the game mode. It runs at 53°C max. I found out that one of the apps that I was using to measure the temperature apparently only shows the temperature of the hottest CPU core, that's why the temperature sometimes shoot up to 60°C whenever I took a screenshot for example, and then came back down to around 50°C.
But I'll try disabling Play Services and playing again.
Do you know if those temperatures are safe btw? Around 50°C while I'm gaming.
The battery's temperature doesn't go past 40°C, in fact I don't even think I've ever seen it getting to 40°C.
Anyway, thank you very much.
You're welcome. The Farenheit is scaled better for real world use.
140F is well within tolerance for the CPU/mobo as long as the battery doesn't get hotter than that. I don't let my battery go beyond 103F.
The CPU/mobo can handle up to probably 165F but it's best never to push it that hot as auto thermal shutdown doesn't always work in time to save the components that are running hot and have a sudden additional power usage spike.
Really the phone shouldn't feel hot... it's killing the battery too. Track them down.
If it feels warm when using the browser, something(s) are running in the background driving it up.
Any cloud apps, including Google backup Transport, Framework and Google Firebase.
Ditch any trashware apps like WhatsApp, Twitter, Instagram etc.
I'm using my 10+ in a case at a 75F ambient air temp browsing with a CPU temp of 89F right now. It is stock but heavily optimized.
blackhawk said:
You're welcome. The Farenheit is scaled better for real world use.
140F is well within tolerance for the CPU/mobo as long as the battery doesn't get hotter than that. I don't let my battery go beyond 103F.
The CPU/mobo can handle up to probably 165F but it's best never to push it that hot as auto thermal shutdown doesn't always work in time to save the components that are running hot and have a sudden additional power usage spike.
Really the phone shouldn't feel hot... it's killing the battery too. Track them down.
If it feels warm when using the browser, something(s) are running in the background driving it up.
Any cloud apps, including Google backup Transport, Framework and Google Firebase.
Ditch any trashware apps like WhatsApp, Twitter, Instagram etc.
I'm using my 10+ in a case at a 75F ambient air temp browsing with a CPU temp of 89F right now. It is stock but heavily optimized.
Click to expand...
Click to collapse
The phone doesn't feel hot, unless I'm playing a game, depending on the game it gets somewhat hot.
It's been colder in my city these past two days, but tomorrow we'll have a temperature that's closer to normal. If the phone manages to stay in an acceptable temperature range I'll keep it, if not, I'll return it to the store and see what I can get done.
My old phone didn't have a plastic back, so feeling the phone warm is a new thing for me.
Most Google apps are disabled, I only use WhatsApp to talk to my family, I have Instagram installed but I don't even remember when it was the last time I've used it (I put it on deep sleep also).
Thank you very much once again.
Using power management can cause erratic behavior and sometimes increased power usage especially if set globally.
Developer options>standby apps, all buckets should show as active otherwise power management is running.
blackhawk said:
Using power management can cause erratic behavior and sometimes increased power usage especially if set globally.
Developer options>standby apps, all buckets should show as active otherwise power management is running.
Click to expand...
Click to collapse
With Power Management you mean the Background Usage Limits from the Device Care app?
furquim97 said:
With Power Management you mean the Background Usage Limits from the Device Care app?
Click to expand...
Click to collapse
Yeap. I have a 10+ running on Pie.
Your may get different results but it's a known source of instability and trouble.
This is how mine is configured.
blackhawk said:
Yeap. I have a 10+ running on Pie.
Your may get different results but it's a known source of instability and trouble.
This is how mine is configured.
Click to expand...
Click to collapse
I'll try it. Thank you once again.
blackhawk said:
Yeap. I have a 10+ running on Pie.
Your may get different results but it's a known source of instability and trouble.
This is how mine is configured.
Click to expand...
Click to collapse
I did it but now all my apps under Standby Apps are set as "Active" and I can't change it. Won't this consume more battery?
furquim97 said:
I'll try it. Thank you once again.
Click to expand...
Click to collapse
Once you do that you need to track down the trouble makers and deal with each on a case by case basis. Sometimes simply cleaning the system memory in Device Care can work wonders. Keep open apps to a minimum.
Here's the old version of Device Care. It uses 360° which cleans very well but is CCP junk.
To safely use it use Karma Firewall* to block its internet access. It will still run normally.
Before uninstalling your current version use Apk Export** to make a installable copy, just in case.
*freeware, uses almost no battery
**freeware that is very useful to backup all your apps and updates for future use... ditch Playstore for reloads
blackhawk said:
Once you do that you need to track down the trouble makers and deal with each on a case by case basis. Sometimes simply cleaning the system memory in Device Care can work wonders. Keep open apps to a minimum.
Here's the old version of Device Care. It uses 360° which cleans very well but is CCP junk.
To safely use it use Karma Firewall* to block its internet access. It will still run normally.
Before uninstalling your current version use Apk Export** to make a installable copy, just in case.
*freeware, uses almost no battery
**freeware that is very useful to backup all your apps and updates for future use... ditch Playstore for reloads
Click to expand...
Click to collapse
Thanks. But I can't uninstall the current Device Care app. Is it safe to do it via adb?
furquim97 said:
I did it but now all my apps under Standby Apps are set as "Active" and I can't change it. Won't this consume more battery?
Click to expand...
Click to collapse
This is normal. Just because their bucket state is marked as active doesn't mean they are running. It simple means Android is no longer managing them by assigning a bucket state to them and so on. Google it... it sounds like a great idea but it never worked well for me in practice. Android still manages the apps with it off less the added resource burden of this system.
furquim97 said:
Thanks. But I can't uninstall the current Device Care app. Is it safe to do it via adb?
Click to expand...
Click to collapse
Sorry. You are correct.
I got rid of the updated version by doing a factory reset. You can try loading the older version by first force stopping the loaded version. It may worked... try this first.
I guess a adb edit would allow you to disable the current one. If the older one will load is another question.
blackhawk said:
This is normal. Just because their bucket state is marked as active doesn't mean they are running. It simple means Android is no longer managing them by assigning a bucket state to them and so on. Google it... it sounds like a great idea but it never worked well for me in practice. Android still manages the apps with it off less the added resource burden of this system.
Click to expand...
Click to collapse
Oh, I get it. Thanks.
blackhawk said:
Sorry. You are correct.
I got rid of the updated version by doing a factory reset. You can try loading the older version by first force stopping the loaded version. It may worked... try this first.
I guess a adb edit would allow you to disable the current one. If the older one will load is another question.
Click to expand...
Click to collapse
I'll see what I can do.
I'll also test the phone again tomorrow when the weather in my city will return to normal. If everything goes well I'll keep the phone, if not I'll have to take it to the store and see what they offer me, a replacement, another device, I really don't know how it works in this particular store that I bought.
Anyway, thank you very much, you've been very helpful!
My 10+ was a battery guzzling hot running hog before I optimized it. It took some time and effort
Today you never guess it is that same phone.
If there's any doubts get a refund. It could be hardware, even a heat sink or pipe issue.
That said this is a commonly seen problem that has nothing to do with hardware in Samsungs.
Do some Google searches for that device and hot running issues. See what you find.
blackhawk said:
My 10+ was a battery guzzling hot running hog before I optimized it. It took some time and effort
Today you never guess it is that same phone.
If there's any doubts get a refund. It could be hardware, even a heat sink or pipe issue.
That said this is a commonly seen problem that has nothing to do with hardware in Samsungs.
Do some Google searches for that device and hot running issues. See what you find.
Click to expand...
Click to collapse
I can relate. I had a Xiaomi before this one, and the stock ROM was plagued with app killing and battery drain. I'm glad you managed to work it out, all I had to do was switch to a custom ROM.
I've tested the same game again today since the temperature has gone back to normal where I live, and while the CPU temperatures are in acceptable range, the battery temperature got to 40°C/104°F.
I did some research regarding overheating on this phone and it's always the same thing, some have it like I do, while others say the phone doesn't even warm up the palm of their hands. So I don't know if its a configuration issue or if there are a lot of defective devices out there.