Related
Hello everyone,
Would like to raise a matter about the battery life.
I have updated tostock 4.2.2 recently, I have noticed recently that the battery life is being awkward the least. The device can hold up to 4 days ideal but when I start using it the battery percentage dives rapidely it can go down in 20% if the screen is on for 10 minutes. Did anyone experience this and know how to go around it? Im really troubled as it wasnt like this in 4.1.2 it could hold up to 5 hours of screen now it can barely keep with 2-3 hours!
Sent from my GT-N5100 using Tapatalk
modesty1 said:
Hello everyone,
Would like to raise a matter about the battery life.
I have updated tostock 4.2.2 recently, I have noticed recently that the battery life is being awkward the least. The device can hold up to 4 days ideal but when I start using it the battery percentage dives rapidely it can go down in 20% if the screen is on for 10 minutes. Did anyone experience this and know how to go around it? Im really troubled as it wasnt like this in 4.1.2 it could hold up to 5 hours of screen now it can barely keep with 2-3 hours!
Sent from my GT-N5100 using Tapatalk
Click to expand...
Click to collapse
My charge and battery drain thread is here somewhere...
You can look in settings, battery... let us know what is tops on the list.
Also look at settings, data... let us know what is tops as well.
Note: Most of the time the trouble is with google music player, this years update sux with 4.2.2. If you have 4.1.1 it is no problem.
4.2.2 also does not like media files with odd names and characters. I had to rename all my music files to 2 digit numbers, for the media to stop indexing. Folders don't seem to be the issue, just the files. I get 3% per 12 hours discharge with wifi on while sleeping disconnected from charger, and about 10% per hour under a mix use. Thus able to have 8 hours before charging. I can possibly get a week out of the tablet having sync off, power saver enabled, and Wifi off when disconnected from battery in sleep.
modesty1 said:
Hello everyone,
Would like to raise a matter about the battery life.
I have updated tostock 4.2.2 recently, I have noticed recently that the battery life is being awkward the least. The device can hold up to 4 days ideal but when I start using it the battery percentage dives rapidely it can go down in 20% if the screen is on for 10 minutes. Did anyone experience this and know how to go around it? Im really troubled as it wasnt like this in 4.1.2 it could hold up to 5 hours of screen now it can barely keep with 2-3 hours!
Sent from my GT-N5100 using Tapatalk
Click to expand...
Click to collapse
use power saving mode, and download Advanced task killer. Kill all apps running in the background whenever u are done or not using the tablet. and clear your "Recent applications". that should increase the battery life significantly
Same here on videos
gooberdude said:
My charge and battery drain thread is here somewhere...
You can look in settings, battery... let us know what is tops on the list.
Also look at settings, data... let us know what is tops as well.
Note: Most of the time the trouble is with google music player, this years update sux with 4.2.2. If you have 4.1.1 it is no problem.
4.2.2 also does not like media files with odd names and characters. I had to rename all my music files to 2 digit numbers, for the media to stop indexing. Folders don't seem to be the issue, just the files. I get 3% per 12 hours discharge with wifi on while sleeping disconnected from charger, and about 10% per hour under a mix use. Thus able to have 8 hours before charging. I can possibly get a week out of the tablet having sync off, power saver enabled, and Wifi off when disconnected from battery in sleep.
Click to expand...
Click to collapse
Hi guys,
I will search your thread cause I have this huge battery drain problem too.
I'm on 4.2.2 for long now but for 1 or 2 months now, my battery drains very rapidly when I'm watching movies or series ... I can use the samsung player or MX player it's just the same ...
When I'm 100%, i loose more than 10 % in 15 minutes of watching ... in fact my train travel in the morning is 30 minutes, and If i'm watching a movie, during the trip I loose nearly 30 % !!!
The thing is when I'm playing games or do something else, there is no such drain ... and as you I get only approx 3% or 4% per 12 hours discharge with wifi on while sleeping ...
This drives me crazy ...
At 56% at 3:00 pm today (I'm french), since a discharge at 6:00 am, my batteries info from parameters are :
Screen : 39 %
Network / Radio function : 33% (what is this ?)
MX player : 16 %
Sleep mode : 3 %
And the rest is under 2 or 3 % ...
For example, I watch a movie for only 30minutes today and played Zombie Tsunami for approx 20 minutes wich only drains 2% on the battery monitor ...
golgoth57 said:
Hi guys,
I will search your thread cause I have this huge battery drain problem too.
I'm on 4.2.2 for long now but for 1 or 2 months now, my battery drains very rapidly when I'm watching movies or series ... I can use the samsung player or MX player it's just the same ...
When I'm 100%, i loose more than 10 % in 15 minutes of watching ... in fact my train travel in the morning is 30 minutes, and If i'm watching a movie, during the trip I loose nearly 30 % !!!
The thing is when I'm playing games or do something else, there is no such drain ... and as you I get only approx 3% or 4% per 12 hours discharge with wifi on while sleeping ...
This drives me crazy ...
At 56% at 3:00 pm today (I'm french), since a discharge at 6:00 am, my batteries info from parameters are :
Screen : 39 %
Network / Radio function : 33% (what is this ?)
MX player : 16 %
Sleep mode : 3 %
And the rest is under 2 or 3 % ...
For example, I watch a movie for only 30minutes today and played Zombie Tsunami for approx 20 minutes wich only drains 2% on the battery monitor ...
Click to expand...
Click to collapse
I wonder if your using data connection instead of Wifi...Data would draw more power when used, that is probably why you see Network/Radio about as high as screen. I have MX player pro as well so it is not an issue with MX player.
When I watch Netflix I get about 12% an hour drain with Miracast activated. As for playing video files on SD, it can be a lot lower to a lot higher depending on size and bit rate. Remember media playback has a number of things going on, speaker / earphones, video quality, and screen brightness will draw power at higher levels. I suggest doing a test with BBC iplayer for streaming when at home since your in France. Watch about 30 minutes with power saver enabled. You should get about 5% drain at most for the 30 minute test. If you are doing that, I would think the Data connection would be your primary issue with power drain. A way you can boost battery while watching video when traveling, you can purchase an external rechargeable battery. Both Data and GPS will suck the power right out of your device much faster than WIFI and there are a few battery calibration apps that use GPS to quick discharge for faster calibration.
Hope this helps in understanding.
I've got a similar issue.
I've seen a change recently, because the battery lasts much shorter now than only a few weeks ago. I suspect it could have to do with having run the battery too low (below 20%) a couple of times, specially with my kid playing games or watching Youtube on it. 49% of consumption is the screen, 27% is Android OS, Skype 11%. I haven't installed any new apps in that tim, although I updated Skype to a well functioning version (4.6.0.42007), but with it consuming 11% of total energy, I doubt that being the culprit. I haven't change the energy conservation setting (it's turned off), so it's not that either. On the other hand I turned on Playstore apps updating recently, and that might have something to do with it.
Today the Note even went dead, I didn't notice any battery alert. Is there a way to turn a SOUND on for this. Can't seem to find it. However, the Samsung UI keeps making little ringing noises with every received mail, right up to the device shutting off (sound on message alert is turned off). Any way to turn that off?
Gadgety said:
I've got a similar issue.
I've seen a change recently, because the battery lasts much shorter now than only a few weeks ago. I suspect it could have to do with having run the battery too low (below 20%) a couple of times, specially with my kid playing games or watching Youtube on it. 49% of consumption is the screen, 27% is Android OS, Skype 11%. I haven't installed any new apps in that tim, although I updated Skype to a well functioning version (4.6.0.42007), but with it consuming 11% of total energy, I doubt that being the culprit. I haven't change the energy conservation setting (it's turned off), so it's not that either. On the other hand I turned on Playstore apps updating recently, and that might have something to do with it.
Today the Note even went dead, I didn't notice any battery alert. Is there a way to turn a SOUND on for this. Can't seem to find it. However, the Samsung UI keeps making little ringing noises with every received mail, right up to the device shutting off (sound on message alert is turned off). Any way to turn that off?
Click to expand...
Click to collapse
Ah, wow! I always have my screen much higher than any app with battery consumption. I use Dolphin browser for Youtube video while browsing with flash enabled and flash.apk installed as well. I prefer the youtube app for links to youtube from emails.
As for sound, it depends on the app that sends notifications. I just block the device most of the time. Though google has options to use default notifications sometimes it can get confused when you set your devices notifications to silent. Then you must change googles notification to silent as well. I think you do that in language and input in one of the google settings for TTS or Voice. It is really a pain but then again that is why I just block and leave things be. Block is in the Notification panel. you can open the complete switch panel by choosing the squares in the upper right.
When your device hit 100%, unplug your device, turn it off and put it into the power socket. Does it say the charge is 100% or does it take another half an hour before it say 100%?
If that's the case you have a battery calibration problem. The software thinks it's fully charged when the battery is only half charged.
Sent from my GT-N5110 using Tapatalk
deviant_cryptic said:
When your device hit 100%, unplug your device, turn it off and put it into the power socket. Does it say the charge is 100% or does it take another half an hour before it say 100%?
If that's the case you have a battery calibration problem. The software thinks it's fully charged when the battery is only half charged.
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
k
I am sorry to say this... but I have had my own issues with power, and that is why I made a thread about such issues.
What you describe is almost what all OEM Note 8.0 devices do. It will show charging again once you have reconnected power after charging.
It has nothing to do with calibration needed to the battery. I have done this many times with Stock and Civato's ROM. If you do not want the issue with Touchwiz DVFS, download an app to disable it. Then you will not see that sort of issue any more. I do not recommend using tools of any sort to circumvent normal operation, but many have disabled DVFS without ill effects so they have a more accurate view of charge capacity.
Nobody here, including me can tell you what is going on directly with your battery without seeing critical information. If anything post the top battery eaters before you charge. This way we can see what is happening. For the most part media seems to be the issue. As google music player will run in background as Media Server no matter how many times you reboot it will try to re index media files over and over. I froze my Google Music player so the issue is non-existent
Another issue is USB charging cables. Samsung cables are not that good. I moved on to Sony / Nokia cables as they are superior cables and a wee longer to boot.
gooberdude said:
Ah, wow! I always have my screen much higher than any app with battery consumption. I use Dolphin browser for Youtube video while browsing with flash enabled and flash.apk installed as well. I prefer the youtube app for links to youtube from emails.
As for sound, it depends on the app that sends notifications. I just block the device most of the time. Though google has options to use default notifications sometimes it can get confused when you set your devices notifications to silent. Then you must change googles notification to silent as well. I think you do that in language and input in one of the google settings for TTS or Voice. It is really a pain but then again that is why I just block and leave things be. Block is in the Notification panel. you can open the complete switch panel by choosing the squares in the upper right.
Click to expand...
Click to collapse
Thank you for the reply. Regarding sound, I thought it was Samsung's @mail inbox app, but it was Microsoft's Exchange. So that is now on silent. Didn't have any effect (!). Under Settings --> Personal --> Google, sound is also set to silent (!!).
Under Language I found Language, Keyboard, Speech and Mouse pointer, and sound for key press could be disabled (it already was).
The Unit's system sounds for ringing and messages have been on silent the whole time (!!!). Still not getting rid of it.
The low energy alert, I don't know whether that is Google or Samsung's Touchwiz. I have sound (I would like to get an auditory warning)? If so, where would that be? It seems I've been through all the settings, but since I haven't been able to turn off the sound alert for incoming mail, or turn off the auditory alarm for low energy, there probably are other settings I've missed.
Come to think of it, this subject would probably would go better under a different thread.
Thank you for your assistance.
gooberdude said:
k
I am sorry to say this... but I have had my own issues with power, and that is why I made a thread about such issues.
What you describe is almost what all OEM Note 8.0 devices do. It will show charging again once you have reconnected power after charging.
It has nothing to do with calibration needed to the battery. I have done this many times with Stock and Civato's ROM. If you do not want the issue with Touchwiz DVFS, download an app to disable it. Then you will not see that sort of issue any more. I do not recommend using tools of any sort to circumvent normal operation, but many have disabled DVFS without ill effects so they have a more accurate view of charge capacity.
Nobody here, including me can tell you what is going on directly with your battery without seeing critical information. If anything post the top battery eaters before you charge. This way we can see what is happening. For the most part media seems to be the issue. As google music player will run in background as Media Server no matter how many times you reboot it will try to re index media files over and over. I froze my Google Music player so the issue is non-existent
Another issue is USB charging cables. Samsung cables are not that good. I moved on to Sony / Nokia cables as they are superior cables and a wee longer to boot.
Click to expand...
Click to collapse
Which app can disable the Samsung dvfs?
Sent from my GT-N5110 using Tapatalk
deviant_cryptic said:
Which app can disable the Samsung dvfs?
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Just search on google play for DVFS... you will need to be rooted.... I like saferoot.zip, and to install xposed framework. Most gamers prefer to disable, but it does wonders for true battery reading and charging.
Hello,
Lately, my note 8 started to feel warm while I'm using it...
So I decided to watch CPU temperature using System Tuner:
https://play.google.com/store/apps/details?id=ccc71.pmw
First, temperature of the atmosphere here nowadays is about 35c to 40c...
for my note 8:
In idle mode, temp is about 40c, while normal using (wifi off, bluetooth off) like watch videos, using apps,
CPU temp is about 50c and battery is ~38c to 40c
sometimes while gaming, CPU temp could reach ~60c
The tab from the back left side is feeling warm
Is these temps normal??
What's your readings?
Note: I'm rooted on stock 4.2.2, and I didn't modify anything..
I just set the max freq at 1GHZ after overheating
AhmadLight said:
Hello,
Lately, my note 8 started to feel warm while I'm using it...
So I decided to watch CPU temperature using System Tuner:
https://play.google.com/store/apps/details?id=ccc71.pmw
First, temperature of the atmosphere here nowadays is about 35c to 40c...
for my note 8:
In idle mode, temp is about 40c, while normal using (wifi off, bluetooth off) like watch videos, using apps,
CPU temp is about 50c and battery is ~38c to 40c
sometimes while gaming, CPU temp could reach ~60c
The tab from the back left side is feeling warm
Is these temps normal??
What's your readings?
Note: I'm rooted on stock 4.2.2, and I didn't modify anything..
I just set the max freq at 1GHZ after overheating
Click to expand...
Click to collapse
Removing, disabling, or freezing Google Play Music will fix battery drain and temperature issues. Though there are thousands of apps that are buggy, since everyone has different tastes there is no real way to point out exactly what app outside of Googles Play Music that is causing drain without going into system and looking at battery. The top two items listed are the cause of your battery drain. Display should always be on top unless using GPS, Games, or Media without power adapter. Google's Play Music will cause Media Adapter to index in back ground. Depending on media type and media name, Media Adapter will run for 30 minutes to hours on end draining battery as well. 4.2.2 has a bug with media names, So using Windows or Apple's media management to create folder and names can be your issue as well. Search for any media with "_" in the name or folder.
gooberdude said:
Removing, disabling, or freezing Google Play Music will fix battery drain and temperature issues. Though there are thousands of apps that are buggy, since everyone has different tastes there is no real way to point out exactly what app outside of Googles Play Music that is causing drain without going into system and looking at battery. The top two items listed are the cause of your battery drain. Display should always be on top unless using GPS, Games, or Media without power adapter. Google's Play Music will cause Media Adapter to index in back ground. Depending on media type and media name, Media Adapter will run for 30 minutes to hours on end draining battery as well. 4.2.2 has a bug with media names, So using Windows or Apple's media management to create folder and names can be your issue as well. Search for any media with "_" in the name or folder.
Click to expand...
Click to collapse
Google play music is disabled long time ago.
I'm also aware of the media storage drain issue...
That's why I wished to upgrade to 4.4.2 to end the media drain issue.. but kitkat seems buggy too as many users confirmed that.
Also, I've no battry drain problem, it's just overheating!
My battery can last for about 8 hours without charing
ONLY OVERHEATING
AhmadLight said:
Google play music is disabled long time ago.
I'm also aware of the media storage drain issue...
That's why I wished to upgrade to 4.4.2 to end the media drain issue.. but kitkat seems buggy too as many users confirmed that.
Also, I've no battry drain problem, it's just overheating!
My battery can last for about 8 hours without charing
ONLY OVERHEATING
Click to expand...
Click to collapse
Sounds like a hardware issue... if still under warrenty on the Date of registration, I would do a factory reset and call it in.
gooberdude said:
Sounds like a hardware issue... if still under warrenty on the Date of registration, I would do a factory reset and call it in.
Click to expand...
Click to collapse
No, my warranty is void...
I downloaded 2 different apps to check the sensors in note 8.0
it doesn't have temperature sensor at all!
How system tuner could give me CPU temp?? or it's just fake?!
I have perpetually experienced overheating issues while using 4.4-based ROMs; typically while using Navigation as part of Google Maps and while docked in the Galaxy Nexus Car Dock.
My frustration lead to inquiring with some skilled members of the Galaxy Nexus community, including @Ziyan, @freshgiammi, and @aosp. They have indicated that 4.4-based ROMs seem to be afflicted with this problem, but that it might also be tied to the kernel being used.
I have two phones; one running stock 4.3 (Sprint) and another running CM11 M8 (also Sprint).
Testing Setup:
I have Google Maps (and all other software, including Google Play and Play Services) completely updated. The screen brightness is set to auto. I've tested using Navigation initiated by WiFi, and then disabling the cellular radio (to ensure that the overheating is not being caused by radio activity.) I checked OS Monitor by switching through recent apps mid-testing; this gave me a snapshot of system temperatures and a glimpse of CPU usage.
Stock - Worked perfectly. Navigation, at any time of day, seems to work wonderfully. I do notice that the phone does get warm, and using OS Monitor, can confirm that it reaches 47 degrees C (and holds), never exceeding it. The phone continues to charge without issue. OS Monitor cited CPU usage of 29% at the highest (note that this does not indicate that Maps never used more than 29%, just that 29% was the most I witnessed while checking 15-20 times over the course of 10 miles.)
CM11 - Phone overheats within minutes of starting Navigation, reaching temperatures of 53 degrees C--and as high as 58 degrees C. The phone stops charging as soon as the system registers an "overheated" state. OS Monitor's highest CPU usage was 52%, which is almost double as high as I saw under the stock firmware.
IMGUR link of screenshots while Navigating, idle temperature, overheating, etc.
So far, it appears when my phone has been asleep or idle, it's operating at 29-35 degrees C; so it's nearly doubling it's temperature when Navigating. Additionally, this behavior occurs at night, when the sun (and warmer temperatures) are no longer a factor, which seems to rule out the idea that the environment is a major contributor.
I have a good friend who also as a Sprint Galaxy Nexus running CM11; he is a Waze user, and is experiencing the same issue.
Is this a known issue/problem with 4.4-based ROMs? This has been speculated in other threads, but perhaps a more definite answer/explanation is warranted?
Might this be related to the kernel in use, and the thermal throttling limits? What would be the best method of testing such?
What tests or other steps should I take to gather more information or test more factors?
EDIT 1: At @aosp 's recommendation, I'm looking for thermal throttling capabilities via the Kernel Tuner (2014 beta) application. The "Thermal" button is available, but grayed out. Is it safe to assume that means the kernel I'm using has no thermal throttling capabilities, which would (probably) explain how the Galaxy Nexus seems to be able to work itself into an overheated state?
Shidell said:
I have perpetually experienced overheating issues while using 4.4-based ROMs; typically while using Navigation as part of Google Maps and while docked in the Galaxy Nexus Car Dock.
My frustration lead to inquiring with some skilled members of the Galaxy Nexus community, including @Ziyan, @freshgiammi, and @aosp. They have indicated that 4.4-based ROMs seem to be afflicted with this problem, but that it might also be tied to the kernel being used.
I have two phones; one running stock 4.3 (Sprint) and another running CM11 M9 (also Sprint).
Testing Setup:
I have Google Maps (and all other software, including Google Play and Play Services) completely updated. The screen brightness is set to auto. I've tested using Navigation initiated by WiFi, and then disabling the cellular radio (to ensure that the overheating is not being caused by radio activity.) I checked OS Monitor by switching through recent apps mid-testing; this gave me a snapshot of system temperatures and a glimpse of CPU usage.
Stock - Worked perfectly. Navigation, at any time of day, seems to work wonderfully. I do notice that the phone does get warm, and using OS Monitor, can confirm that it reaches 47 degrees C (and holds), never exceeding it. The phone continues to charge without issue. OS Monitor cited CPU usage of 29% at the highest (note that this does not indicate that Maps never used more than 29%, just that 29% was the most I witnessed while checking 15-20 times over the course of 10 miles.)
CM11 - Phone overheats within minutes of starting Navigation, reaching temperatures of 53 degrees C--and as high as 58 degrees C. The phone stops charging as soon as the system registers an "overheated" state. OS Monitor's highest CPU usage was 52%, which is almost double as high as I saw under the stock firmware.
IMGUR link of screenshots while Navigating, idle temperature, overheating, etc.
So far, it appears when my phone has been asleep or idle, it's operating at 29-35 degrees C; so it's nearly doubling it's temperature when Navigating. Additionally, this behavior occurs at night, when the sun (and warmer temperatures) are no longer a factor, which seems to rule out the idea that the environment is a major contributor.
I have a good friend who also as a Sprint Galaxy Nexus running CM11; he is a Waze user, and is experiencing the same issue.
Is this a known issue/problem with 4.4-based ROMs? This has been speculated in other threads, but perhaps a more definite answer/explanation is warranted?
Might this be related to the kernel in use, and the thermal throttling limits? What would be the best method of testing such?
What tests or other steps should I take to gather more information or test more factors?
EDIT 1: At @aosp 's recommendation, I'm looking for thermal throttling capabilities via the Kernel Tuner (2014 beta) application. The "Thermal" button is available, but grayed out. Is it safe to assume that means the kernel I'm using has no thermal throttling capabilities, which would (probably) explain how the Galaxy Nexus seems to be able to work itself into an overheated state?
Click to expand...
Click to collapse
IMHO, handling of thermal throttling in 4.4 should be secondary thing to investigate about.
Shouldn't we first think of why for the same application, CPU is hogging this much?
Is it that CPU is not offloading its tasks to GPU which is supposed to happen, and happening with 4.3?
Good thing is that you have two tuna phones available to test out various scenarios.
If you use a ROM's stock kernel, thermal throttling is enabled correctly.
Give Omni and Trickster Mod a try. Omni is more stable & bug-free than CM, and Trickster will show you your CPU temps, as you only posted your battery temps - which are way too high! How the hell did you reach it? Even if I do some antutu, mine never reaches more than 40 °C. 58 °C is either a sensor misbehaving, or you put your phone in a jacket, lol, as it's far enough from the CPU to not heat up.
Post some Omni & Trickster temps with it's stock kernel something must be wrong, as I didn't notice anything like this on my maguro.
Ziyan said:
If you use a ROM's stock kernel, thermal throttling is enabled correctly.
Give Omni and Trickster Mod a try. Omni is more stable & bug-free than CM, and Trickster will show you your CPU temps, as you only posted your battery temps - which are way too high! How the hell did you reach it? Even if I do some antutu, mine never reaches more than 40 °C. 58 °C is either a sensor misbehaving, or you put your phone in a jacket, lol, as it's far enough from the CPU to not heat up.
Post some Omni & Trickster temps with it's stock kernel something must be wrong, as I didn't notice anything like this on my maguro.
Click to expand...
Click to collapse
My battery goes to about 44 degrees C when watching Netflix and charging and about the same during navigation and charging. Only time it's gotten hotter than that is due to environmental issues (such as very hot car interior before ac cools down). I run cm11 and faux123 kernel. Looks like OP is having some kind of hardware issues.
Shidell said:
I have Google Maps (and all other software, including Google Play and Play Services) completely updated. The screen brightness is set to auto. I've tested using Navigation initiated by WiFi, and then disabling the cellular radio (to ensure that the overheating is not being caused by radio activity.) I checked OS Monitor by switching through recent apps mid-testing; this gave me a snapshot of system temperatures and a glimpse of CPU usage.
Stock - Worked perfectly. Navigation, at any time of day, seems to work wonderfully. I do notice that the phone does get warm, and using OS Monitor, can confirm that it reaches 47 degrees C (and holds), never exceeding it. The phone continues to charge without issue. OS Monitor cited CPU usage of 29% at the highest (note that this does not indicate that Maps never used more than 29%, just that 29% was the most I witnessed while checking 15-20 times over the course of 10 miles.)
CM11 - Phone overheats within minutes of starting Navigation, reaching temperatures of 53 degrees C--and as high as 58 degrees C. The phone stops charging as soon as the system registers an "overheated" state. OS Monitor's highest CPU usage was 52%, which is almost double as high as I saw under the stock firmware.
Click to expand...
Click to collapse
I think it would be helpful to try to narrow down where the heat is coming from. Some possibilities:
1. Mobile data or LTE - a likely suspect, but you've already eliminated this one.
2. GPS - set Google Maps aside for a bit, get an app like GPS Status and Toolbox, set it to keep the screen on, and see if this still causes the heating issues.
3. GPU (or lack of proper use of GPU) - If Google Maps overheats the phone but GPS Status does not, it could be how CM is handling the display for Google Maps.
I got a chance to do some testing yesterday afternoon while driving. Toroplus on Page Plus, OmniROM 8-31 nightly, NukedTrinity kernel (was running it to test something else, will test stock kernel today but I fully expect results to be the same). Mobile data off as always. Started GPS right after a 15 minute phone call, battery was at 40 C. Hooked up the charger and ran GPS Status for 5 minutes, battery temp went up to 44 C. Ran Google Maps for 15 minutes (had previously downloaded offline maps for the area), still charging. Battery temp had gone back down to 40 C.
Sdobron said:
My battery goes to about 44 degrees C when watching Netflix and charging and about the same during navigation and charging. Only time it's gotten hotter than that is due to environmental issues (such as very hot car interior before ac cools down). I run cm11 and faux123 kernel. Looks like OP is having some kind of hardware issues.
Click to expand...
Click to collapse
Can you provide me with a link to the exact kernel you're using? I'd like to test it as well. Thanks!
Shidell said:
Can you provide me with a link to the exact kernel you're using? I'd like to test it as well. Thanks!
Click to expand...
Click to collapse
http://faux.romhost.me/tuna/kk44/tuna-kk-kernel-039m-sr.zip
Thank you. I'll test with this shortly as well.
@Ziyan
I agree that these temperatures are way too high; as you'll see below, though, my phone is reaching 46 degrees C simply by using GPS Status! I don't know what to make of that.
@musical_chairs
Thank you for testing as well. I agree that your hypothesis about separate testing is sound, and so I've been testing using GPS Status. I've tried @bsmitty83 's kernel, FancyKernel v56, and Laux123's kernels--all provide slightly different results, but to varying degrees of bizarre behavior using GPS Status.
Stock 4.3 works very well; it determines a bearing indoors without GPS fix and maintains it, with almost no change over a 10 minute period of time. Also, 4.3 warms up, but it never exceeded 44 degrees C.
CM11 w/ Laux123, Fancy Kernel and bsmitty83's all exhibit strange heading behavior. If you'll watch this youtube clip I uploaded (2:45), you'll notice that the phone is laying flat on a wooden table, and yet the Heading will change by 15 or more degrees on it's own. Later in the clip, I move the phone manually to force it to readjust, and you'll see that finds a new bearing from the beginning.
Laying both phones down next to one-another, stock 4.3 indicated the bearing was approximately 219 degrees. In this video clip (FancyKernel r56), my phone believes the bearing is 285 degrees (to begin with) and 260 degrees at the end.
Might GPS be the problem? I suppose I should flash Stock 4.3 to my phone, to make sure it does not continue to behave this way and rule out hardware problems/failure, right?
This just seems really bizarre. Especially that using a GPS fix application can ramp up the temperature so quickly, and so dramatically. Perhaps is the driver/kernel making too many callbacks, causing an escalation in CPU use and heat?
Finally, where can one find the CM11 M8 kernel (indivdually)? I'd like to re-flash it and compare it as well.
Thanks for the continued help in troubleshooting what's happening, everyone.
YouTube CM11 FancyKernel r56
@Shidell just download cm11 m8 and pull out the boot.img so you can fastboot flash it
I managed to gain -5°C on my maguro.
Basically just lowered the thermal throttle to stock values, and now it feels cooler. However still hotter than 4.3 so we're now sure that's not the culprit. Just FYI.
freshgiammi said:
I managed to gain -5°C on my maguro.
Basically just lowered the thermal throttle to stock values, and now it feels cooler. However still hotter than 4.3 so we're now sure that's not the culprit. Just FYI.
Click to expand...
Click to collapse
That's really interesting--5 degrees makes a pretty big difference.
I think I'm going to put stock back on my phone soon, in order to make sure it isn't some sort of hardware failure (maybe the chips in the GNex start to fail if they overheat too high/much? I've heard of that type of failure causing strange issues.)
I'm not sure what to chalk up as the culprit yet, but something is amiss.
If anyone else is reading this thread with a Galaxy Nexus and can comment on their experiences, that information would be useful.
@Ziyan A stock 4.2 or 4.3 kernel should work with any ROM, such as CM10.2 or CM11, is that correct?
I've tried pushing boot.img via fastboot, against both, but neither wants to boot. Am I doing something incorrectly?
Shidell said:
@Ziyan A stock 4.2 or 4.3 kernel should work with any ROM, such as CM10.2 or CM11, is that correct?
I've tried pushing boot.img via fastboot, against both, but neither wants to boot. Am I doing something incorrectly?
Click to expand...
Click to collapse
Yep, but you should only flash the zImage, as flashing the full boot.img flashes the 4.2/3 ramdisk too, which won't work.
BTW, it would be much easier to just flash the latest Omni to your phone. It uses a kernel close to stock, and it's close to AOSP... unlike CM
Ziyan said:
Yep, but you should only flash the zImage, as flashing the full boot.img flashes the 4.2/3 ramdisk too, which won't work.
BTW, it would be much easier to just flash the latest Omni to your phone. It uses a kernel close to stock, and it's close to AOSP... unlike CM
Click to expand...
Click to collapse
I plan on testing Omni today. The reason I ask about the kernel is because I'd also like to test various other ROMs using one of the stock 4.2 or 4.3 kernels.
Can I extract the zImage from the boot.img to ensure I'm only flashing the kernel?
Shidell said:
I plan on testing Omni today. The reason I ask about the kernel is because I'd also like to test various other ROMs using one of the stock 4.2 or 4.3 kernels.
Can I extract the zImage from the boot.img to ensure I'm only flashing the kernel?
Click to expand...
Click to collapse
Yes Connect the gnex via usb and "fastboot flash zimage zImage"
Thanks @freshgiammi I've done some extensive testing, so I hope that this helps us determine where the problem is. @Ziyan, @aosp, @musical_chairs, @poo706, @rkpeterson, @MWisBest, @BigBrother1984, @something15525 I'm hoping you might be able to lend a hand as well.
I created this thread based on the Galaxy Nexus tending to overheat when Navigating. However, I've found another discrepancy--live wallpaper performance with the Google Now Launcher. When using the GNL with the Phase Beam wallpaper, sometimes the GNex can draw it just fine; it's smooth, no (or few) dropped frames--it looks and works great. However, with other ROMs, it's very janky, stuttering and performing poorly.
(Note that GNL with a static picture works fine.)
I suspect that there might be a GPU driver issue, or perhaps a configuration issue, in some ROMs that's causing this behavior. Perhaps a certain GPU driver is used in some ROMs, and not others, causing the problem? Perhaps there is a config file with GPU settings where one has specific features enabled, others do not, and it results in poor performance in certain rendering cases?
I wonder if it might be related to overheating on the Galaxy Nexus when Navigating, watching video, playing games--items that tax the GPU. If it is such an issue, though, it might also mean extra work is being performed to compensate, and that would mean extra heat and battery use.
Here are two YouTube links displaying the behavior in question. First is Factory Stock 4.3--I wasn't able to directly record the screen (as that feature wasn't introduced with ADB until 4.4), but hopefully it's clear enough to see that it's smooth. (There is one hiccup when the cards are loading, but that's it.) The second video shows the same test, but running on CM11 M8--it's very choppy and lags behind input, and it's extremely noticeable in person.
I tried to capture video from OmniROM, but received this error while using ADB:
Code:
D:\Android\sdk\platform-tools>adb shell screenrecord /sdcard/omni44.mp4
WARN: Unable to set device connection state for audio submix IN
WARN: Unable to set device connection state for audio submix OUT
Unable to instantiate audio source (error -1)!
Factory 4.3
CM11 M8
I've conducted some tests on a spare Galaxy Nexus, and wiped my own personal model, to be sure that the behavior is the same on both devices--to ensure I don't have a damaged GPU or some other weird hardware issue that might be responsible.
Results:
Factory 4.2.1 - OK
Factory 4.3 - OK
LiquidSmooth LS-KK-v3.2-2014-09-03 - OK
Paranoid Android 4.6 Beta 1 - OK
OmniROM 4.4.4 - 20140905 Nightly - FAIL
CM10.2 RC 1 - FAIL
CM11 M8 - FAIL
Further, I extracted the kernel zImage from Factory 4.2.1 and 4.3, and flashed it into CM11 M8 just to see if the kernel alone made any difference. The 4.2.1 kernel wouldn't boot; 4.3 booted up properly, but the lag/choppiness persisted, which seems to indicate that the problem is not kernel related.
What should I investigate next? Clearly LiquidSmooth and ParanoidAndroid are getting smooth GPU performance, which I expect is also what's causing Navigation to cause my phone to overheat (but I can't prove that, unless we can solve this issue and then I can test with a fix and determine if it's the cause or not.)
Could a config file be at fault? A difference in drivers being used?
I'm having a huge lag with the latest version of Chrome which updated with material design. I'm afraid will we be having these gpu related bugs with Android L as well.
Will these gpu drivers issues be fixed with 3.4 kernel?
sagara.sandaru said:
I'm having a huge lag with the latest version of Chrome which updated with material design. I'm afraid will we be having these gpu related bugs with Android L as well.
Will these gpu drivers issues be fixed with 3.4 kernel?
Click to expand...
Click to collapse
Hm, I'm not sure I can answer that without more information.
What ROM and Kernel are you using? What type Galaxy Nexus? If you are using 4.4, can you do a screencap of what you're experiencing and upload it to YouTube as I have?
Shidell said:
Thanks @freshgiammi I've done some extensive testing, so I hope that this helps us determine where the problem is. @Ziyan, @aosp, @musical_chairs, @poo706, @rkpeterson, @MWisBest, @BigBrother1984, @something15525 I'm hoping you might be able to lend a hand as well.
I created this thread based on the Galaxy Nexus tending to overheat when Navigating. However, I've found another discrepancy--live wallpaper performance with the Google Now Launcher. When using the GNL with the Phase Beam wallpaper, sometimes the GNex can draw it just fine; it's smooth, no (or few) dropped frames--it looks and works great. However, with other ROMs, it's very janky, stuttering and performing poorly.
(Note that GNL with a static picture works fine.)
I suspect that there might be a GPU driver issue, or perhaps a configuration issue, in some ROMs that's causing this behavior. Perhaps a certain GPU driver is used in some ROMs, and not others, causing the problem? Perhaps there is a config file with GPU settings where one has specific features enabled, others do not, and it results in poor performance in certain rendering cases?
I wonder if it might be related to overheating on the Galaxy Nexus when Navigating, watching video, playing games--items that tax the GPU. If it is such an issue, though, it might also mean extra work is being performed to compensate, and that would mean extra heat and battery use.
Here are two YouTube links displaying the behavior in question. First is Factory Stock 4.3--I wasn't able to directly record the screen (as that feature wasn't introduced with ADB until 4.4), but hopefully it's clear enough to see that it's smooth. (There is one hiccup when the cards are loading, but that's it.) The second video shows the same test, but running on CM11 M8--it's very choppy and lags behind input, and it's extremely noticeable in person.
I tried to capture video from OmniROM, but received this error while using ADB:
Code:
D:\Android\sdk\platform-tools>adb shell screenrecord /sdcard/omni44.mp4
WARN: Unable to set device connection state for audio submix IN
WARN: Unable to set device connection state for audio submix OUT
Unable to instantiate audio source (error -1)!
Factory 4.3
CM11 M8
I've conducted some tests on a spare Galaxy Nexus, and wiped my own personal model, to be sure that the behavior is the same on both devices--to ensure I don't have a damaged GPU or some other weird hardware issue that might be responsible.
Results:
Factory 4.2.1 - OK
Factory 4.3 - OK
LiquidSmooth LS-KK-v3.2-2014-09-03 - OK
Paranoid Android 4.6 Beta 1 - OK
OmniROM 4.4.4 - 20140905 Nightly - FAIL
CM10.2 RC 1 - FAIL
CM11 M8 - FAIL
Further, I extracted the kernel zImage from Factory 4.2.1 and 4.3, and flashed it into CM11 M8 just to see if the kernel alone made any difference. The 4.2.1 kernel wouldn't boot; 4.3 booted up properly, but the lag/choppiness persisted, which seems to indicate that the problem is not kernel related.
What should I investigate next? Clearly LiquidSmooth and ParanoidAndroid are getting smooth GPU performance, which I expect is also what's causing Navigation to cause my phone to overheat (but I can't prove that, unless we can solve this issue and then I can test with a fix and determine if it's the cause or not.)
Could a config file be at fault? A difference in drivers being used?
Click to expand...
Click to collapse
Could you give FML a try? In particular the latest beta build...
not sure if you're on a maguro or a toro, so I'll link them both:
omni-4.4.4-20140825-maguro-FML.zip (159.56 MB)
omni-4.4.4-20140824-toro-FML.zip (159.41 MB)
With FML being based on OmniROM, if there's an issue with OmniROM but not FML or vice-versa it can help narrow down what might be the difference that causes the issue.
I'm also interested if screen record via adb works with that build for ya as well, so if you could test that it'd be much appreciated.
sagara.sandaru said:
I'm having a huge lag with the latest version of Chrome which updated with material design. I'm afraid will we be having these gpu related bugs with Android L as well.
Will these gpu drivers issues be fixed with 3.4 kernel?
Click to expand...
Click to collapse
The 3.4 kernel isn't looking to be the smoking gun we were hoping for, however if we can get Ducati (hardware video encode/decode and camera stuff) working with the updated GPU drivers in the 3.0 kernel that would definitely be helpful. The newer GPU drivers have better power management by a landslide.
I've recently upgraded old Nexus 7 to Nexus 7 2013 in my car semi-permanent setup.
This use case strongly reduces the selection of custom ROM/kernel combinations to support OTG with charging. I finally sticked to the special build of Glitch kernel (https://forum.xda-developers.com/showpost.php?p=72214133&postcount=2876) together with LineageOS 14 (https://forum.xda-developers.com/ne...rom-lineageos-14-1-nexus-7-2013-5-12-t3931482).
So far everything works like a charm with one very annoying exclusion: USB audio streaming runs into virtually continuous buffer underruns, which result in horrible glitching/cracking. Without a workaround described later it's unusable.
Somewhere I learned this is caused by CPU hotplugging implementaction of default mpdecision driver. Here is my investigation (questions are bold):
In Glitch kernel mpdecision is disabled by default, msm_hotplug is used instead. But still no help here. No other hotplug driver is included. Glitch development is dead.
I tried some tweaks of msm_hotplug in Kernel Adiutor. Strangely, switching it off leads to single core operation. So I kept if on and set min_cpus_online to 4, which effectively disables hotplugging (all cores are online all the time). This makes the glitches less frequent but is not a solution.
The only step which makes USB streaming usable is a workaround - running another CPU heavy app in foreground. This helps a lot (like 90% glitches are gone) and in car it is surprisingly easily achievable (e.g. a navigation app does the trick). Still, I would love to make it more robust:
I've tried alternative USB audio driver, namely the app USB Audio Player app. It works perfect. But only covers local files playback and music streaming services which I don't use (no Spotify, which is critical). I could not find any standalone driver. Is there any?
I was not successful trying other tweaks of msm_hotplug. Are there any settings proven to help USB streaming, which I overlooked?
I haven't successfully flashed any other ROM/kernel combination. There is effectively only ElementalX kernel v 5.16 (which in theory should be useable with LineageOS 13/Stock ROM) and old Timur services integrated in LineageOS (https://forum.xda-developers.com/nexus-7-2013/development/rom-usb-host-based-rr-timur-s-t3659332). There were problems which prevented me from setting up these ROMs. Is there any hope it could help?
nalott said:
I've recently upgraded old Nexus 7 to Nexus 7 2013 in my car semi-permanent setup.
This use case strongly reduces the selection of custom ROM/kernel combinations to support OTG with charging. I finally sticked to the special build of Glitch kernel...
Click to expand...
Click to collapse
With "no battery mod" you wouldn't be restricted to a special kernel/old ROM, nor worry about replacing the battery ever again.
Thanks. Interesting idea. But I need to keep my Nexus removable and usable outside the dash.
I did some more experiments. My assumption is that the USB buffer underruns are caused by CPU frequency scaling and/or hotplugging. So I tried to set the CPU governor to 'performance' and min_cpus_online=4. The cores were really all plugged all the time. For some reason they didn't maintain the full frequency (1728 in my setup), but still the available CPU performance was constantly overkill for what was needed. Still no help, audio glitches were roughly the same as in my standard configuration (CPU governor 'interactive', min_cpus_online=1).
The only workable workaround seems to be running a sufficiently CPU-greedy app in the foreground. Problem is that not all apps (which one wants to be running in the foreground) are sufficiently CPU-greedy. Thats why I'm trying to find a real solution.
I am having a very frustrating issue after moving to the S22 from my S9.
In direct sunlight, the screen is nice and bright and readable.
However, after a few minutes in the sun when the phone gets warm, it is automatically dimming the screen meaningfully - to the point where its really not readable.
I have tried both with Adaptive Brightness enabled and disabled. From what I have read it seems to be something the phone does automatically when warm to preserve battery or regulate the heat.
However it makes the phone unusable in the sun on a warm day once it warms up. Has anyone figured out a way to manage/disable this?
Use in direct sunlight should be measured in seconds not minutes if at all, not recommended.
You can severely damage the phone like this if it overheats especially if the ambient air temperature is high!
More than likely the phone isn't optimized and has a lot of junk running in the background contributing to high battery consumption and excessive heat. Tone it down...
thanks for the quick reply.
the phone is very new so shouldnt be that cluttered, and its having this issue that the S9 never had. Its not even 70 degrees today (although its direct sunlight) so its not like I am at the beach.
Would definitely welcome any suggestions on how to "tone it down" though as I would like to make sure I am having it run efficiently...
It seems strange that a brand new phone with better processor, etc should be having this issue in moderate temperature compared to the older phone I had for years...
Toss any social media apps; they should never be installed or activated if preinstalled like FB.
Try temporarily disabling Google play Services; gmail needs it(use manual sync) and Playstore needs it (enable/reboot for Playstore). Paid for apps that need Playstore; activate them, then use Karma Firewall to block Playstore so they continue to work. Firewall block those apps as well if they don't require a internet connection.
Samsung and Google cloud don't help matters, disable if you don't use them. Google Backup Transport* is a prime offender.
Set brightness to manual and keep at 50% or preferably less... don't burn your eyes out.
Clear system cache, don't use SmartSwitch to transfer from old phone... it can cause issues.
Don't use any of the Device Care battery optimization options as they cause erratic behavior and even increased battery usage. Only fast charging should be toggled on if you want it.
Instead find the power hogs and deal with each on a case by case basis. Set display to medium resolution ie the optimized setting and leave it there. If you run at 60hz that will also save power.
Disable carrier, Google, Google Firebase, Samsung and app feedback. Not sure if Package Disabler works with Android 12 yet, that's an easy way to clean up bloatware and easily toggle apps on/off if needed. Stay with the stock launcher as it's efficient and powerful.
Lol, it's a long list and some depends on your own desires/usage. Once optimized block system updates as they can undo everything... be careful before doing them, wait and see if and what issues they may introduce.
Play with it and explore... it's almost impossible to crash a stock Android
Be careful what you install though, you are what you load. One poorly coded app can cost you a factory reset if you can't undo its damage. Rarely, they can alter hidden user settings and this remains even if you uninstall the app! Repairing this can be time consuming and a pain.
*since you don't have an SD card slot to use as a data drive work out a good backup plan for all critical data or you will lose it eventually. A OTG 5tb flashstick can be used for frequent "dirty" backups.
In addition use at least 2 hdds that are physically and electronically isolated from each other and the PC to redundantly backup critical data!!!
Copy/paste folders/files only, Do Not use SmartSwitch to backup any critical data!!!
Like it's predecessor Kies, it can fail you miserably. Verify folder count and data size after a backup, spot check that the data is readable.
Once lost, data can rarely be recovered... plan ahead to avoid this sad fate.
thanks this is thorough and I will examine these things.
I guess my takeaway based on your response is - there is no way to disable whatever is causing the phone to autodim when it gets warm?
because I think its related to the phone itself physically getting warm from sitting in the sun (although I understand these things can exacerbate it).
I am not having any overheating issues other than when its warm out and the phone is in the sun and it then toggles down the brightness
lirong said:
thanks this is thorough and I will examine these things.
I guess my takeaway based on your response is - there is no way to disable whatever is causing the phone to autodim when it gets warm?
because I think its related to the phone itself physically getting warm from sitting in the sun (although I understand these things can exacerbate it).
I am not having any overheating issues other than when its warm out and the phone is in the sun and it then toggles down the brightness
Click to expand...
Click to collapse
Auto dimming is a last ditch effort to protect the phone. The display acts as a heatsink for the mobo as well as producing a lot of heat of it's own. The sunlight has a high infrared component to it.
Thermal stress is best kept as low as possible for OLEDs. The increased temperature causes expansion of the components; that could cause a failure by itself. The OLEDs are made of extremely thin layers (microns thick) so they could potentially overheat unpredictable fast as there's very little mass to them.
Best not to tickle the dragon's tail...
Hi there, just got hands on a S22 myself and observing this dimming issue. Obviously it's all about apps using GPS. I notice that the screen goes dim to about 40% max brightness when I'm in Google Maps or Locus Map. And this doesn't matter if Adaptive Brightness is on or off. Going back to any other app, the screen comes back to max brightness.
That's a no go as I'd buy the phone for my outdoor experience with Locus Map.