Related
Hello,
I need a simple app to help with an overheat problem on my EVO.
Let me recap the problem simply, when the phone gets too warm it will shut down and vibrate five times and then blink the green LED. The phone then cannot be turned back on until the battery has cooled down.
I have found a half solution, if my phone is in Airplane mode then it will not shut down even when it is warm. So, to avoid shutdown, I need a simple widget. The widget should be 2x1. On the left side, a simple battery temp monitor. On the right side, an airplane icon to let me know if the phone is in airplane mode or not.
What I need the app to do is to automatically switch the phone to airplane mode if the the phone gets above a user designated temperature. The only exception to the automatic airplane mode should be if the phone is in a current call. Seems like the phone will let me finish a call before shutting down due to heat. Hopefully the app can throw the phone into airplane mode immediately when the call ends. But if that exception is too difficult, the primary functionality would still be worth it.
This is my first app request, so I don't know if I'm being specific enough. I also know that other people can use this app. Hopefully someone out there can help us all out.
Thanks
There is an app called tasker that should be able to do that for you. At least untill someone can build an app for you.
Sent from my PC36100 using XDA App
Not sure what your doing to over heat the phone, but I would try to fix the problem instead of usong a work around. It sounds like you have an inefficient kernel or its too far ovrrclocked. I'm thinking continual use in this overheated state will cause unrepairable damage to your phone.
Just looked at Tasker, from what I can tell it does not have Temperature as an event.
And the problem cause is not my kernel, from what I can tell. I've tried a few different kernels on a couple different mods. I've tried underclocking and under volting. Nothing seems to help. From what I've read, I might have a faulty sensor.
I had a hell of a time with cm7 and the jit compiler. Poor battery life and running warm even when browsing the web. Not sure what your running but it may be as easy as tapping a checkbox.
siris420 said:
Not sure what your doing to over heat the phone, but I would try to fix the problem instead of usong a work around. It sounds like you have an inefficient kernel or its too far ovrrclocked. I'm thinking continual use in this overheated state will cause unrepairable damage to your phone.
Click to expand...
Click to collapse
It's a hardware cpu sensor calibration issue, according to Sprint tech Lokifish Mars. Search for my thread in Evo General.
I avoid shutdowns by keeping battery temp < 39°C.
mine overheated when i was charging and using hotspot/tether, somehow after i wiped my sd card and everything else and installed the rom again it never overheated again.
somehow the more apps get installed the more the chanse some of them be are gonna be running in the backgroung, who knows...
omenovi said:
mine overheated when i was charging and using hotspot/tether, somehow after i wiped my sd card and everything else and installed the rom again it never overheated again.
somehow the more apps get installed the more the chanse some of them be are gonna be running in the backgroung, who knows...
Click to expand...
Click to collapse
Some phones overheat and shutdown regardless of installed apps, rom, or kernel. My Evo consistently shutsdown at 39°C, even when running bare aosp w/zero apps installed.
It's only an issue for me when playing games, using the phone in high ambient temps, and flashing mods. Keeping the battery & cpu cool with a fan or ac vent is the only way I can flash mods or roms.
Elixir is a free app on the market, you can make customizable widgets (1x1 up to 4x1), one for temp, the other to toggle airplane mode.
I use it to monitor temp, battery, cpu freq, and cpu %, and to keep an eye on ram.
Works well.
So I was streaming music from MOG and all was working well until my screen went off (idle). Music started to pause/buffer and kept doing so every 10 seconds. When I turn the screen back on and stare at it, it won't do it at all and I can see it load full on the seek bar. Only happens when screen goes off and phone goes idle. I'm guessing its something with the CPU throttling maybe? Is there any way I can fix this? I'm connected on WiFi 5G and I have "keep WiFi on during sleep - Always".
This seems to be a pretty common issue (I have it myself, when connecting via WiFi with adb I need to keep my display on) and I've seen two issues on file here and here. I've yet to see a fix for it yet though
Aww crap. Well that sucks. Does it happen on custom roms/kernels?
reyes.jr said:
Aww crap. Well that sucks. Does it happen on custom roms/kernels?
Click to expand...
Click to collapse
I'm running CM9 nightly with leankernel now. Although it's happened since I've gotten the phone, and I've ran probably half a dozen different ROMs and 3 different kernels, including stock. I vaguely remember reading some posts where people either said there was a fix or they were working on it, though I'm honestly not real sure.
K thanks for the info bro.
reyes.jr said:
So I was streaming music from MOG and all was working well until my screen went off (idle). Music started to pause/buffer and kept doing so every 10 seconds. When I turn the screen back on and stare at it, it won't do it at all and I can see it load full on the seek bar. Only happens when screen goes off and phone goes idle. I'm guessing its something with the CPU throttling maybe? Is there any way I can fix this? I'm connected on WiFi 5G and I have "keep WiFi on during sleep - Always".
Click to expand...
Click to collapse
I am also facing the same issue. Yesterday, I was downloading ARHD 3.0 directly on phone through wi-fi. Surprisingly the progress was 1% completion per minute in screen-off mode. But the moment, I would turn on the screen, the rate became 3-4 times faster. i.e. 3-4% completion per minute.
Deviating from topic, I have seen similar behaviour quite some time back in iPad1.
kizuki.buy said:
I am also facing the same issue. Yesterday, I was downloading ARHD 3.0 directly on phone through wi-fi. Surprisingly the progress was 1% completion per minute in screen-off mode. But the moment, I would turn on the screen, the rate became 3-4 times faster. i.e. 3-4% completion per minute.
Deviating from topic, I have seen similar behaviour quite some time back in iPad1.
Click to expand...
Click to collapse
Well glad to know I'm not in the same boat. Have any of u tried android 4.0.4?
reyes.jr said:
Well glad to know I'm not in the same boat. Have any of u tried android 4.0.4?
Click to expand...
Click to collapse
Yeah, I'm on Liquid 1.25 (4.0.4 based ROM) and it still does it. If I run a speed test and turn the screen off, let it finish and check it; it will never go much over 5 Mbit/s. When I run the test with the screen on, I will get 10-20 Mbit/s. This was of course testing on my home WiFi network.
This is pretty annoying because I download anime torrents every week and it's enough of a battery killer already just to download the thing, but now I have to leave the screen on in order for it to even finish in a reasonable amount of time. I've also tried setting the minimum clock speed to 1200 MHz in SetCPU just to see if it was a CPU throttling/bottleneck issue when the screen turns off. But it made no difference . This can't be a hard fix for Google/Devs.
At least with popcorn and franco kernels you can do
echo 1 > /sys/module/bcmdhd/parameters/wifi_pm
to put wifi on high performance mode with screen off. They say this can enable high throughput.
reyes.jr said:
Well glad to know I'm not in the same boat. Have any of u tried android 4.0.4?
Click to expand...
Click to collapse
Yes, I am using ARHD 3.0 which is based on 4.0.4
There seem to be definite improvements and it was worth the effort to update.
As far as I know, wifi goes into a low power state with screen off to conserve power/battery life.
My command put it in normal power mode, but kernel must support it
KiNG OMaR said:
As far as I know, wifi goes into a low power state with screen off to conserve power/battery life.
Click to expand...
Click to collapse
oooo, so only on WiFi does this occur? On 4g it doesn't?
This also happen to me.. Happened in 4.0.1 4.0.2 4.0.4 so far I managed to bypass the issue with wifi keep alive its a free app from play store.. You could try and comment if that works for you
Sent from my Galaxy Nexus using xda premium
Threre is no need for any custom kernel module. Im on Stock ICS 4.04 and found an easy workaround. Actually this issue is not an android bug, but an issue of streaming apps that aren't proberly coded for honeycomb and ICS.
Leaving my OP in place, but I have rewritten the description with much more detail and pics here
http://forum.xda-developers.com/showthread.php?p=25401417#post25401417
I suggest skipping to there.
I am looking for general tips here. E.g., not asking you to diagnose my specific problem so much as give me ideas of what else to check or try.
Lately I have had unexplained (to me) battery drain. Yesterday I lost about 25 percent in an hour while the phone idled. It is not a constant thing, though. I can go an hour and loose 1 percent then loose massive amounts in the next hour.
Now, i have searched, but I have not found anything that applies to me.
I have:
Tried a different radio
Tried a different kernel
Reflashed my rom
Phone is entering deep sleep according to cpu spy
There are no unusual or excessive wake locks according to better battery stats
No apps are using a lot of battery.
I am in a low signal area at work, but putting the phone in airplane mode and dissabling background syn does not stop the drain.
Ideas?
might be your phone is loosing signal? i would check the battery stats in the settings menu to see if you have a poor mobile signal.
Zepius said:
might be your phone is loosing signal? i would check the battery stats in the settings menu to see if you have a poor mobile signal.
Click to expand...
Click to collapse
beren28 said:
I am in a low signal area at work, but putting the phone in airplane mode and dissabling background syn does not stop the drain.
Click to expand...
Click to collapse
So I don't think I can blame it on that.
Do you have any exchange sync on your phone?
Sent from my Galaxy Nexus using Tapatalk 2
can you give us screen shots of battery stats?
Herman76 said:
Do you have any exchange sync on your phone?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I do, and on reflection it is a possible culprit since I added it recently.
Didn't occur to me since it was producing no wakelocks and the battery stats did not showing as using much battery.
I shall turn it off for a bit and see if that helps. (unless there is some other way to test if it is the problem first.) I am off to the search button!
Zepius said:
can you give us screen shots of battery stats?
Click to expand...
Click to collapse
This is from yesterday when i set it down unused for about 90 minutes. The amount of wakes seems liek a lot, but it is similar to what i see when i have far far less drain, so I don't think that is the problem. I didn't get the app list screen, but out should screen as the only major drain with about 2 minutes.
I know it is shows poor signal strength, so immediately after that shot I put it in airplane mode, turned of sync, and rebooted. The battery continued to drain and graph had the exact same slope under those conditions. (Forget to get a pic though.)
Sent from my jitterbug using tapatalk.
System panel paid version with monitoring enabled is the best for tracking apps using CPU.
OK, still working on this.
To recap:
When the screen is off, and no apps are running I sometimes get inexplicable battery drain. This is occurring under conditions when I should be experiencing little or no drain at all. I say this becuase:
The screen is of and no bakground apps are running
the phone is NOT awake and IS entering deep sleep (as confirmed by cpuspy)
there are no unusual kernel or partial wake locks
there are no apps listed as using unexpected ammounts of battery
This is not a universal problem. The phone *often* behaves as expected. I can leave the phone off for an hour and see a 1% or 2% drain, and I am happy with that. However, sometimes, randomly, it goes nuts on my.
This graph from a few weeks ago shows what I mean. Look in the green box. The phone is sleeping, and the screen is off. The graph starts as a flatline, then, all of a sudden, it begins to drop precipitously.
Here is a graph that shows the battery dropping at the same rate whether the phone is awake or sleeping:
I have gone the following to try and narrow the problem down:
Done a completely fresh install of my Rom including a system wipe.
Tried two kernels (the aokp default and several relases of Franco's
Tried a different radio
Activated and installed a new sim card
I have come to suspect that the problem is network related. When the problem starts, sometimes going into airplane mode and back and/or toggling 2g only temporarily fixes the problem.
I suspect that something is happening with my connection to T-Mobile that keeps the network running and draining power. This is pure speculation, but it is all I can think of.
I installed juice defender (which I had not been previously running) and noticed the that, sometimes, it didn't turn of data when it should have. I also noticed the following two things happen:
I do not believe it is a rom problem, since if so, someone else would be reporting this. It might be an app problem, but if so the app is draining battery without a wake lock and while the phone is in deep sleep.
It is not exchange (as was suggested in this thread) since it continues when I ev my exchange account.
I have no idea what else to do or try.
Since it happens at random and takes a while to identify, uninstalling one app at a time to test for that could easily take months to narrow down a misbehaving app.
I know it is not a hardware issue since last month I got this:
That was with AOKP and Franco (earlier versions obviously)
I have google searched till my fingers bleed.
I am a long way form being an expert, and I suspect I may have overlooked something obvious.
Please, any thoughts??
Damn you definitely have a major issue and I don't know what it could be. But when my phone sleeps itstays dead flat with no awake bars, and drops 1% every 3 hours.
1. Calibrate battery
2. If you really wanna find the problem, install the rom with no mods or apps and run it and see if it still happens. Then add back each mod/app one at a time
derekwilkinson said:
1. Calibrate battery
2. If you really wanna find the problem, install the rom with no mods or apps and run it and see if it still happens. Then add back each mod/app one at a time
Click to expand...
Click to collapse
While I appreciate your effort, this is remarkable unhelpful for the following reasons:
1. "calibrating" the battery is a myth and doesn't actually do something. Even if it did, it would not explain the symptoms I have described. I have been around xda long enough to know it is the knee-jerk reaction to any battery question, but it is not relevant here.
2. Since the problem occurs at random, and sometimes takes hours to show up, (For instance, last night I charged to full and tried to catch it happening. For 4 hours nothing happened, it behaved perfectly. Then I went to bed and it immediately started to fall and was dead by morning) and since I have over 100 apps, your suggestion could easily take *over a year* to follow. Believe me, I have thought about it, but I started this thread hoping for ideas that would allow me to avoid it.
Here is that chart for last night.
I had about 1 hour and 30 minutes screen on time with 65% left when I went to bed. When I woke up, phone was dead.
RogerPodacter said:
Damn you definitely have a major issue and I don't know what it could be. But when my phone sleeps itstays dead flat with no awake bars, and drops 1% every 3 hours.
Click to expand...
Click to collapse
Mine often does that. But sometimes it doesn't. It is the fact that it happens seemingly at random that makes it so annoying and hard to track down.
I would replace the battery
One thing you haven't rulled out is that the battery itself is bad.
Have a friend you could swap with for a day, or at least long enough to see if the problem follows? If your battery drops on their phone that is also a good indication.
arw01 said:
One thing you haven't rulled out is that the battery itself is bad.
Have a friend you could swap with for a day, or at least long enough to see if the problem follows? If your battery drops on their phone that is also a good indication.
Click to expand...
Click to collapse
The thought has occurred to me, but unfortunately, no, I don't have a friend I can swap with. And really, since I have had the phone less than 3 months, the battery *shouldn't* be bad, but yeah, defective products happen.
If I cannot find any other cause I will likely order a new battery and see if that fixes it.
beren28 said:
While I appreciate your effort, this is remarkable unhelpful for the following reasons:
1. "calibrating" the battery is a myth and doesn't actually do something. Even if it did, it would not explain the symptoms I have described. I have been around xda long enough to know it is the knee-jerk reaction to any battery question, but it is not relevant here.
2. Since the problem occurs at random, and sometimes takes hours to show up, (For instance, last night I charged to full and tried to catch it happening. For 4 hours nothing happened, it behaved perfectly. Then I went to bed and it immediately started to fall and was dead by morning) and since I have over 100 apps, your suggestion could easily take *over a year* to follow. Believe me, I have thought about it, but I started this thread hoping for ideas that would allow me to avoid it.
Click to expand...
Click to collapse
1. yes battery calibration does make a difference.
2. ok, so an app can't run a process at random? especially when you have "over 100 apps"? Run the rom stock and see if it still happens, or even run the stock rom/kernel. if you don't want to try this then why are you asking for suggestions? christ
derekwilkinson said:
1. yes battery calibration does make a difference.
Click to expand...
Click to collapse
You are incorrect. But, in any case, I DID calibrate the battery just to cover bases in the case that I was wrong.
2. ok, so an app can't run a process at random? especially when you have "over 100 apps"?
Click to expand...
Click to collapse
We'll of course it can. That is kinda my point. If I go one app at a time waiting for it to "run a process at random" I am talking literally MONTHS of testing. I would have to wait many hours, if not days after installing or uninstalling an app to be sure whether or not it made a difference, then move on the the next. This is simply not an option. I started this thread in hopes that a realistic and doable solution might exist that I was unaware of.
Run the rom stock and see if it still happens, or even run the stock rom/kernel. if you don't want to try this then why are you asking for suggestions? christ
Click to expand...
Click to collapse
I am asking because there may be a solution that I am unaware of that doesn't require me to put my entire life on hold for months. It is possible that there is no such solution, but I asked in case there was one.
Sorry to have put you out so much.
You mentioned you recently installed exchange sync. Did turning off sync remedy this or have you not tried disabling all sync features?
One other thing to check is the background data usage of your apps. You'd find this under 'data usage' and make sure you enable the wifi tab so you can see data usage on wifi.
skadebo said:
You mentioned you recently installed exchange sync. Did turning off sync remedy this or have you not tried disabling all sync features?
when i did a complete quote and re flash i did not setup the exchange account, but the issue continued.
One other thing to check is the background data usage of your apps. You'd find this under 'data usage' and make sure you enable the wifi tab so you can see data usage on wifi.
Click to expand...
Click to collapse
I'll check that out. Thanks.
Sent from my jitterbug using tapatalk.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
My battery also drains at a rate similar to yours however I'm on the CDMA version. Hopefully you can figure out what's going on with yours.
Hello,
I’m looking for help with a rather strange problem. I’m getting a lot of awake time in Android OS. I installed BetterBatteryStats and noticed it was the service BTLowPower that was doing a lot of kernel wakelocks.
I turned bluetooth off a couple of days (and have rebooted in the meantime even) but still the top service in kernel wakelocks is BTLowPower by a very large margin ... how can this be if bluetooth is turned off ?
Stats are in BetterBatteryStats Kernel Wakelocks
Unplugged 12h47min.
BTLowPower 9h33min, 74.7%
I've attached a screenshot
I have a Galaxy Nexus which is running stock Jellybean.
Thanks in advance for any advice !
Same here.
Please help.
My battery drains out because of this in 12h and 1.5h of screentime
Sent from my Galaxy Nexus
bat0nas said:
Same here.
Please help.
My battery drains out because of this in 12h and 1.5h of screentime
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Do you guys have other Bluetooth devices around? I have a Motorola S805 headset as well as a cheapo BT2.0 dongle from DealExtreme.
I typically don't have the headset turned on unless it's connected to the computer, but what I'm finding is that if I just leave my phone with the dongle turned off and the headset turned off then I don't get the BTLowPower battery drain.
If I turn the dongle on, and turn on the headset then I typically get the BTLowPower battery drain in my GNex. I have to reboot the phone for it to go away. I'm not really sure the exact sequence of events to cause the drain to occur, but I feel like it's definitely related to turning on and off my S805 headset or being around the dongle.
There might be other bluetooth devices around (such as phones of a colleague or something), however the bluetooth on my phone is turned OFF and I still keep getting the BTLowPower in kernel wakelocks Today for example it kept my phone awake for over 10 hours
Anyone ? I keep having this problem ...
Same problem here. BTLowPower keeps draining my battery.
I have bluetooth and Jabra headset off...
It usually happends when I unplug my GNex from charging.
Please help....
-----------
sorry for my bad english.
Same issue
I'm running a Toro Gnex with the Vanir AOSP ROM. It's buttery smooth, and I've had no problems at all, other than this specific kernel wakelock. Same scenario as the OP.
If anyone finds out more about it, I would be grateful!
Airplane Mode
NicholasFarseer said:
I'm running a Toro Gnex with the Vanir AOSP ROM. It's buttery smooth, and I've had no problems at all, other than this specific kernel wakelock. Same scenario as the OP.
If anyone finds out more about it, I would be grateful!
Click to expand...
Click to collapse
I've been reading about this all morning. I run Automateit Pro and have it go into airplane mode at night. After losing 25% battery overnight, the investigation began. BTlowpower was keeping the phone awake. It looks like airplane mode can be the culprit, possibly in combination with Wifi set to always on. I am set up to turn Bluetooth off a couple of minutes after going into airplane model tonight, I'll follow up with my findings over the weekend.
bigknowz said:
I've been reading about this all morning. I run Automateit Pro and have it go into airplane mode at night. After losing 25% battery overnight, the investigation began. BTlowpower was keeping the phone awake. It looks like airplane mode can be the culprit, possibly in combination with Wifi set to always on. I am set up to turn Bluetooth off a couple of minutes after going into airplane model tonight, I'll follow up with my findings over the weekend.
Click to expand...
Click to collapse
Great, keep us posted. I also turn airplane mode on at night, but my Bluetooth is always off.
Did anyone try to hard reset their phone ? I called Samsung but I got the standard reply to hard reset my phone, I haven't tried it yet because I doubt it would work and I have a lot of authenticators on it and it's a bit of a hassle. But if any of you guys already tried it I would love to hear if it worked ! Thanks !
BTlowpower solved
Darthy1980 said:
Great, keep us posted. I also turn airplane mode on at night, but my Bluetooth is always off.
Did anyone try to hard reset their phone ? I called Samsung but I got the standard reply to hard reset my phone, I haven't tried it yet because I doubt it would work and I have a lot of authenticators on it and it's a bit of a hassle. But if any of you guys already tried it I would love to hear if it worked ! Thanks !
Click to expand...
Click to collapse
BTlowpower issue solved by turning Bluetooth on and then off again after Airplane mode activated. However, that caused another issue - modem_usb_gpio_wake to crush my battery. Doing more testing today to resolve that one - will post again when that one is solved.
BTlowpower and modem_usb_gpio_wake resolution
bigknowz said:
BTlowpower issue solved by turning Bluetooth on and then off again after Airplane mode activated. However, that caused another issue - modem usb gpio wake to crush my battery. Doing more testing today to resolve that one - will post again when that one is solved.
Click to expand...
Click to collapse
After testing different configurations this weekend, it looks like turning off sync causes these 2 kernel wakelocks. I tested 2 states: Airplane mode + no Wi-fi, and no data (no Wi-fi + no Wireless data, voice signal on). In either instance, the wakelock occurs with sync off. Leaving sync on finally achieved the low overnight battery drain (< 5%) I've been looking for. Regardless, to avoid battery drain after shutting data off:
Turn Bluetooth On and then Off again. If you are using airplane mode (this may be overkill), also turn Wireless Data On and then Off again.
Let me know if this helps.
bigknowz said:
After testing different configurations this weekend, it looks like turning off sync causes these 2 kernel wakelocks. I tested 2 states: Airplane mode + no Wi-fi, and no data (no Wi-fi + no Wireless data, voice signal on). In either instance, the wakelock occurs with sync off. Leaving sync on finally achieved the low overnight battery drain (< 5%) I've been looking for. Regardless, to avoid battery drain after shutting data off:
Turn Bluetooth On and then Off again. If you are using airplane mode (this may be overkill), also turn Wireless Data On and then Off again.
Let me know if this helps.
Click to expand...
Click to collapse
Hi thanks for posting !
Just to make sure I understand, you say the solution is to turn bluetooth on and off again after turning off airplane mode ?
Just for completeness sake, this is my situation: overnight I turn on airplane mode and I sometimes have the wakelock draining my battery during the day (but not always). Draining doesn't occur during the night as while it's on airplane mode I'm also charging it.
I will try every morning when I turn airplane mode off to turn bluetooth on and off again afterwards for a few days and see if that helps. Let me know if I misunderstood.
Thanks,
Jorn
Just found a kind of workaround at another thread, this might be helpful (if it works ).
It doesn't, the drain still occurs >_<
gwindlord said:
Just found a kind of workaround at another thread, this might be helpful (if it works ).
It doesn't, the drain still occurs >_<
Click to expand...
Click to collapse
I actually have a workaround that works for me. During the night I turn off my phone instead of using airplane mode. I no longer have BTLowPower and I also am able to successfully connect every time very quickly with bluetooth to my carkit, which previously was very flaky. It's definitely a standard issue though with the galaxy nexus, I can reproduce it on 2 other galaxy nexi as well.
I just installed BetterBatteryStats two days ago, and I'm seeing the exact same results. I can't help but wonder if the issue is at all related to the kernel I'm using (LeanKernel v4.7), or if perhaps a resolution to the problem could be solved by a modification within the kernel code. The ROM I'm running is BAMF Paradigm v2.4, which is based on AOSP v4.1.2. Like the rest of you, I'd really like to get this fixed.
trestevenson said:
I just installed BetterBatteryStats two days ago, and I'm seeing the exact same results. I can't help but wonder if the issue is at all related to the kernel I'm using (LeanKernel v4.7), or if perhaps a resolution to the problem could be solved by a modification within the kernel code. The ROM I'm running is BAMF Paradigm v2.4, which is based on AOSP v4.1.2. Like the rest of you, I'd really like to get this fixed.
Click to expand...
Click to collapse
Anyone have any updates on this? My GNex just started doing this randomly after being stable for a long time.
the7thson said:
Anyone have any updates on this? My GNex just started doing this randomly after being stable for a long time.
Click to expand...
Click to collapse
After three days or so, the issue seemed to go away on its own. I didn't make any changes to any of the apps I was running, nor did I update the kernel. I really have no clue what took care of it for me, but I haven't seen it since.
trestevenson said:
After three days or so, the issue seemed to go away on its own. I didn't make any changes to any of the apps I was running, nor did I update the kernel. I really have no clue what took care of it for me, but I haven't seen it since.
Click to expand...
Click to collapse
Weird, mine went away as well after toggling BT a couple times. Guess we'll file this one under unsolved mysteries
My Galaxy Nexus is running CM11 since day one and before that I was running PlayfulGod's Unnofficial port.
Every couple of days the phone simply crashes/hangs. It happened at night few hours after I last touched it, it happened during the day while simply laying at sleep in the desk and even while using it. The phone simply stops responding.
If it crashes while sleeping the phone appears to be dead, while active, the screen will remain frozen until the battery is dead (guessing... didn't really wait until the battery ran out).
Removing the battery and re-inserting and the phone will work, typically showing a big hit on the battery level.
I assume there's some CPU activity going on because I can feel the area near the camera warmer (not hot) than the rest.
I opened this topic to follow the issue raised on this post:
VuDuCuRSe said:
I just had the same problem! (I'm using the official Jan05)
It happened a few times on the last days. The phone seems to be off, but in complete dark I can see a bit of back light. Once happened during sleep and it even registered screen on activity (weird).
Never really tried connecting it to the computer, always removed the battery right away. =(
Click to expand...
Click to collapse
At least amrs seems to be having this issue.
amrs said:
My phone had a hang yesterday and again today. Running 0104 nightly. Just a black screen with a faint backlight, no reaction to buttons or anything.
Today I managed to get some info finally as to what happens. Turns out the phone didn't crash, I was able to get in via adb, so dmesg and logcat attached. Also I noticed from the process list system_server was a zombie. As I understand it, system_server is a fairly major part of Android so that's probably a problem...
Click to expand...
Click to collapse
Maybe with more reports we may understand what is causing this crashes.
VuDuCuRSe said:
My Galaxy Nexus is running CM11 since day one and before that I was running PlayfulGod's Unnofficial port.
At least amrs seems to be having this issue.
Click to expand...
Click to collapse
I didn't have any problems for a few days, after installing 0112 nightly. Turns out I didn't have any deep sleep either according to Better Battery Stats. A reboot fixed that but then I got a crash quickly again. I realized weather info was odd in the lock screen so locked and tried to unlock and nothing. Couldn't even get in with adb shell this time.
So I guess deep sleep has something to do with this. I've been using the hotplug CPU governor most recently but I think this happened with interactive too.
I'm all stock... kernel, CPU/GPU settings and so on... so I guess that it shouldn't be related to that.
Do you know of any good debugging app to eventually save some sort of evidence of the crash?
I tried plugging the USB cable on the last crash but the computer/adb didn't detect the phone.