Related
Sup all! I love my Hero. I use it as my primary music player on the go.
As most of us have encountered though, it happens sometimes that music starts stuttering after half a day of usage. The problem arises when the music stutters for about a tenth of a second on wakeup, and could start stuttering really badly and intermittently while the phone is asleep. It's frustrating when I can't listen to a complete song without interruption!
I figured, if the phone is silky smooth soon after boot, but starts degrading after a while, it's certainly a software bug that's causing the hiccups. Looking at logcat didn't yield much else than AudioFlinger warnings, but after connecting through SSH and looking at top, I noticed the process /system/bin/mediaserver was using up to 17% of the CPU all the time. I killed it, and the music stopped, but then the process restarted, and the music started again, though from the beginning of a different track.
But the music was smooth again, and the CPU usage of /system/bin/mediaserver dropped drastically.
That's all I have so far. Anyone have a clue why mediaserver would start eating CPU cycles like that? Could it be fixed in future custom ROM releases?
I'm hoping for the best.
YES!
This has pretty much been my biggest concern since I got the phone, but haven't looked into it at all.
I am glad someone else brought this up, I'd like to see some discussion on it, and once I get some free time AND get the IM.apk working, I would like to help in figuring this out.
Just briefly I took a look at the Android OS source, and mediaserver doesn't seem to be in there, so I'm going to make a guess and say that mediaserver is an HTC-specific service. (It's 2:30 in the morning here, I really won't have time until at least Sunday to put this theory to the test. )
If it IS HTC-specific, well, there are pros and cons. A pro is that this would mean that simply using a different music app could instantly fix the problem. Cons: The HTC apps are not open source, and we'd probably have to rely on HTC fixing the code, hopefully in the 2.1 update... and, I really like the HTC Music app, so I'd rather not switch to something else if I don't have to.
If it's NOT HTC-specific, then we'll probably have the same problem with every Music app... HOWEVER, this also means that the community has a better chance of fixing it without HTC's help.
One potential solution I've been thinking of is to use Linux's nice function to give mediaserver a higher priority. This means that other processes will run slower when music is playing, but the mediaserver process should constantly get all the CPU cycles it needs. If I'm listening to music on my phone, I'm more than willing to accept a bit of slow-down in everything else.
Sidenote: After disabling compcache and applying this (http://forum.xda-developers.com/showthread.php?t=622666) fix, the issue is much less noticeable, but it's still there. If I were to venture a guess, I would say that disabling compcache is where this improvement came from, since compcache uses some CPU power to compress the memory.
mediaserver is part of the AOSP. It's inside platform/frameworks/base.git, in /media/mediaserver/.
I'll try looking into it but I doubt I'll find anything. =\
In some cases a better SD card helped
ROM based
I seem to recall this being a ROM based issue. I think I had it for a couple of the early versions of Paul's MoDaCo, but in the newer versions it was fixed, and its never been an issue on any of the AOSP 2.1 ROMs i've been running.
I would guess its probably something from the original HTC release that was badly implemented, or un-optimised.
[I think it may have been sorted for MoDaCo when teknologist released his custom kernal?]
I have a Transcend Class 6 8GB, which I think is a well respected card around here. Besides, it doesn't explain why the process starts choking up after a few hours.
By the way, I run on MoDaCo 3.2 beta 5, with the OOM killer tweaked. It's definitely a software bug where the mediaserver gets stuck in a a strange processor-intensive mode.
as for me A-Data micro sdhc turbo class 6 run smooth/faster on music playback/transfer or backup/apply file in recovery.
I have BT audio in the car, what I have found is that when a new track starts the begining seems slower than normal but speeds up, but this doesn't happen when I listen through the phones speaker or headphones? I run on MoDaCo 3.1 and my micro sdhc is a Kingston 4gb.
Could it be it takes a while for the "waves" from the new track to be caught by the stereo, so it takes a while to catch up? (lol!)
Hopefully when andriod 2.1 comes out it will be sorted?
Don't know how it happened, sorry
as i know when u on wifi or BT it will consume more power eat up cpu & phone will surely laggy. if u using normal cable earphone it doesnt consume more power then BT & wifi & dont eat much cpu. BT is eat lot of battery & cpu if im not wrong.
i get this same problem. Its been there since the stock firmware, and is still apparent in MoDaCo 3.1. Even with a class 6 8gb SD card, its still there.
Now Im running a 2.1 variant, its gone, so it would suggest its a rom problem for sure
alexperkins said:
i get this same problem. Its been there since the stock firmware, and is still apparent in MoDaCo 3.1. Even with a class 6 8gb SD card, its still there.
Now Im running a 2.1 variant, its gone, so it would suggest its a rom problem for sure
Click to expand...
Click to collapse
are you sure u using bluetooth audio without lag?
Hey guys,
i got stable hung ups in 3D intense games (asphalt5, dungeon hunter 3D, crusade of destiny)
some 3-10 mins of play and bang! you got complete stall - have to plug out the battery to reboot.
all other games (2D arcades, tetrises, arcanoids, pacmans) are working quite stable.
i've already tried almost all available ROMS (except stock non rooted one, btw - i dont want to update HBOOT to 0.8, full reset with wiping all the caches inc. dalvik and ext3 part before each ROM.)
pays ROM (several vers)
MCR r2-r3.1 (with richard's kernel either with OCUV or with OC only or without any UVOC and with original MCK 1.1 kernel)
amer_mod des final
all are behaving the same....
what the heck? My phone is generic and certified for Russia (PCT) and it's from white shipment.
the only idea i have is slow SD, cause i use the one which was with the phone - 4GB class2 SD.
please ideas? i wanna play some time not only tetris!
just noticed one moment. it happenes not only in 3D games, it also happenes when using the phone intensively, i.e. now I got stable instant reboot when using internal browser (even with pictures and flash turned off) and opera beta for android. the most interesting part is that just before reboot the back bottom part of the phone becomes noticeable warmer, let's say about 40°c and then instant reboot. (just as it is in 3d games) I use Richards OC only (no UV) kernel v14 with Max freq. set to 998 and MCR r3.1 (everything was wiped upon flash)
Re: Stable HangUPs in 3D CPU intense games on all ROMs
Maybe its some kind of thermal protection of the cpu?
-------------------------------------
Sent via the XDA Tapatalk App
i thought so too...
does any one knows some king of CPU thermal monitoring tool with logs for android?
Happens to me as well. The phone heats up like crazy particularly on badly coded games like the ones gameloft released. For example polarbit's armaggedon squadron runs perfectly well for any amount of time but realfootball for example causes the phone to overheat.
They really botched their ports.
just did a thermal monitoring with tempmonitor lite - but on Desite it only monitors BATTERY temp - it's about 32-33 degrees - so far i found no CPU temp mon which works. and still phone reboots during hard flash playing in about 10 mins with battery temp about 32-33 degrees. i also noticed an infinite boot loop when turning on the phone with AC plugged in. (it starting to load sense and just after SD card preparing notification STABLE instant reboot, though it may not be related)
will try to use stock ROM today (i still have the very first nandroid backup)
Try to uv without oc...should get the temps down.
Any of you guys still experiencing these problems? Have an untouched desire (sim free) that hasnt been unlocked or rooted and sometimes (although rarely) the phone just restarts itself.
Prema999 said:
Try to uv without oc...should get the temps down.
Click to expand...
Click to collapse
UV only kernel reported to have some stability probs....
when u use OC only kernel and, as in my case, set up max. freq to 998 it literally means that you just dont user any OC. so overclocking is not the issue...
jaymit said:
Any of you guys still experiencing these problems? Have an untouched desire (sim free) that hasnt been unlocked or rooted and sometimes (although rarely) the phone just restarts itself.
Click to expand...
Click to collapse
My phone reboots when I'm playing robo wars, when the battery is LOWish and Im charging the phone at the same time. No battery warning, just reboots. If I have a good charge on the phone, and am charging then it seems fine. This is NOT a lock up, like the original thread starter, but a straight old reboot... Annoying, but I dont play robowars when there is low charge from now on!
gunja99 said:
This is NOT a lock up, like the original thread starter, but a straight old reboot... Annoying, but I dont play robowars when there is low charge from now on!
Click to expand...
Click to collapse
i got complete lock ups with only one game (heard rumors about it's bad coding style) the rest issues just reboots the phone. also i noticed that it reboots more frequent when using the phone and it's connected to charger simultaneously.
!!!UPDATE!!! 27.06.10
got back my Desire from the service after 10 days. They've changed motherboard (IMEI also changed) and no more overheating problems!!! HOORAAAY!!!!!!
It's working now even under high load!!!!
I've tried several builds and am quite happy with each (getting better and better as I learn more and more). I've gotten newer and newer kernels and builds and am currently using Thoughlesskyle's not so super froyo and am really liking it.
The one deal-breaker issue that's keeping me from using this phone full time is something I'm calling a phone coma. The phone periodically refuses to wake up from sleep. I may have a flashing notification light that makes it look like the phone is sleeping but I am not receiving emails or phone calls when it's in this state. To wake it up, I have to press the reset button.
I think this may be related to battery (http://forum.xda-developers.com/showpost.php?p=9360324&postcount=7) and I'm going to try to debug this a bit but I was wondering if anyone else is seeing this. I don't think it's specifically related to any one build as I've seen this with DZO and Thoughlesskyle.
Just for completeness, I'm running a Kaiser with a 1 year old 1600mAh battery, a 2.6.25 kernel and, currently, both Sys and Data are on NAND.
Anyone experiencing anything like this?
Sorry, read too quickly your post.
usually is a radio problem that hang the kernel. try with different radio firmware.
I seem to get one of those about 1 or 2 hours after every kernel flash (that may just be a cooincidence though), and maybe once or twice a week as well.
I haven't been able to identify any app or other thing that might have caused it, as they usually happen when I haven't been using the phone for a while.
Info:
Kaiser 130, 23-11-10 l1q1d kernel, Fat Free Froyo RLS5
I thought it might be something to do with the screen turning on (ie wrong panel type), as when it "freezes", the keyboard lights still go on and off when you open the keyboard. I've never been sure if my Kaiser is panel 2 or 3, but it's happened to me on both panel 2 and panel 3 nbhs, so maybe it's unrelated.
That is a known issue with the .25 kernel did it give you backwards text too? What's weird is its only froyo that has that issue these freezes are also why dzo started porting the new one
Sent from my HERO200 using XDA App
I've never seen the backward text. I'll look at rebuilding with the .32 kernel. Interestingly, it doesn't seem to happen when plugged in (so far). It's only happened once today so I may let it roll for a few days and see what it's like.
I observed it too
Adomatic said:
I've tried several builds and am quite happy with each (getting better and better as I learn more and more). I've gotten newer and newer kernels and builds and am currently using Thoughlesskyle's not so super froyo and am really liking it.
The one deal-breaker issue that's keeping me from using this phone full time is something I'm calling a phone coma. The phone periodically refuses to wake up from sleep. I may have a flashing notification light that makes it look like the phone is sleeping but I am not receiving emails or phone calls when it's in this state. To wake it up, I have to press the reset button.
I think this may be related to battery (http://forum.xda-developers.com/showpost.php?p=9360324&postcount=7) and I'm going to try to debug this a bit but I was wondering if anyone else is seeing this. I don't think it's specifically related to any one build as I've seen this with DZO and Thoughlesskyle.
Just for completeness, I'm running a Kaiser with a 1 year old 1600mAh battery, a 2.6.25 kernel and, currently, both Sys and Data are on NAND.
Anyone experiencing anything like this?
Click to expand...
Click to collapse
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
doghead said:
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
Click to expand...
Click to collapse
have some patience guys, kernel .25 has this issues, and devs are working hard on kernel .32 to solve this problems, this is a linux kernel and has to mount the file system to read it and then unmount it on shutdown, but recently there have been some issues with the unmounting part on the shutdown (like when u just unplug the power cord on a PC and windows restart with the "blue screen") until devs find a solution, its wise to always keep on hand a recent /data backup. Another word of advice: read! i dont want to sound rude, but all this is commented extensively over the forum.... like l1qu1d would wisely suggest: use the search tool!
doghead said:
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
Click to expand...
Click to collapse
the old kernel only does this with froyo if you still want to use android use n eclair build or donut its not the latest and greatest but they are very stable though
Thanks, I may give it a shot (or I may just buy a samsung captivate ). Your build is very good. Doesn't seem to be as quick as some of the others I've tried but yours has been really stable. I've been running it for about a week. The others
This problem doesn't seem to happen when plugged in - it's only when on battery. I've had some app freeze-ups but, in general, the phone has been really nice.
Adomatic said:
Thanks, I may give it a shot (or I may just buy a samsung captivate ). Your build is very good. Doesn't seem to be as quick as some of the others I've tried but yours has been really stable. I've been running it for about a week. The others
This problem doesn't seem to happen when plugged in - it's only when on battery. I've had some app freeze-ups but, in general, the phone has been really nice.
Click to expand...
Click to collapse
yea not so super is a little bloated if you dont mind a little work fat free is very snappy i just has a blue theme
First off, I am on AOKP build 19 with Franco #13.1 undervolted to 1275/1075/975/860/840. I recently bought Osmos HD after playing the demo which is an incredibly fun little game. I was playing it for about 20 minutes just fine, not particularly hot in my hand (especially not compared to how hot my old Moto Droid used to get) and it freezes up and goes into a reboot.
I figure no big deal, probably just showing me some instability in my undervolt that stress testing (with StabilityTest app) didn't find. Well, when it gets to lockscreen after booting, it proceeds to freeze and reboot again.. And it does so again after another reboot. I let it sit and cool off for a while, assuming that is the problem and finally it boots up. Well now, I take a look around and all my widgets are gone from my home screens. Not only that, signal bars stay gray, implying I am not connected to Google services anymore. A few reboots fixed the gray signal bars, but widgets remain MIA.
Not a terribly big deal as far as widgets go (though the gray bars would have required a nandroid which is inconvenient), but to me it seems very peculiar and makes me a little concerned. Is this typical when phones freeze up from excessive undervolting or is my phone possessed? Maybe some strange bug with Osmos HD?
The whole thing worries me a little, so I think I will try stock voltages for a while and play some more to see if I can replicate it like that.
I don't think the App could have done anything like that. I am pretty sure it had something to do with the undervolting. This is why I tend to stay away from overclocking until tested stable by others. If you wanna be one of those people to make a $650 paperweight, go ahead, just get insurance.
And is it really true that blue icons = connected to google services?? I thought it meant able to send/receive data.
I honestly skimmed that pretty hard but I undervolted too much myself and had basically the same thing happen... Just be cautious hitting set on boot.
Sent from my Galaxy Nexus using XDA App
App couldn't do that kind of things(maybe system memory management apps which has su access; normal app just terminate app if they cannot handle correctly errors). It's likely caused by excessive undervolting or extremely overlocking: in the first case you obtain system freeze caused by lacking of power requested, in the secondo one you get 'hot' reboot (which prevents the phone become an useless oven, not because it' become an oven which is necessary, but because it's a phone)
Samzebian said:
I don't think the App could have done anything like that. I am pretty sure it had something to do with the undervolting. This is why I tend to stay away from overclocking until tested stable by others. If you wanna be one of those people to make a $650 paperweight, go ahead, just get insurance.
And is it really true that blue icons = connected to google services?? I thought it meant able to send/receive data.
Click to expand...
Click to collapse
Yes Blue means connected to Google Services. Had the same with CM7 on my old SGS (feature of CM7 i think).
Herman76 said:
Yes Blue means connected to Google Services. Had the same with CM7 on my old SGS (feature of CM7 i think).
Click to expand...
Click to collapse
This only seems to work in most ROMs...in the CM9 Kang, it's never blue. (1/19 version, haven't tried the latest due to lack of root)
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.