My Nexus 10 is exhibiting sleep of death issues when I leave it overnight. Are there troubleshooting steps to help me determine what the cause of the issue is?
apastuszak said:
My Nexus 10 is exhibiting sleep of death issues when I leave it overnight. Are there troubleshooting steps to help me determine what the cause of the issue is?
Click to expand...
Click to collapse
When you leave it on over night, do you have it charging or not charging? If not charging, what is the battery level before and in the morning?
ROM? Rooted? Mods?
SmokinCharger said:
When you leave it on over night, do you have it charging or not charging? If not charging, what is the battery level before and in the morning?
ROM? Rooted? Mods?
Click to expand...
Click to collapse
Stock 4.3. Rooted with SuperSU 1.65. ClockworkMod Touch installed.
I had Sleep of Death overnight, and I was not plugged in.
Yesterday morning it was dead. I plugged it in via pogo cable and factory charger to charge and by 8:00 PM it was only at 37%. Switched to USB cable and got it to 90% in a couple of hours. Went to bed at Midnight. Charge was 80%. After I rebooted the device this morning after the SOD, it was at 60%.
A little history.
I was on rooted 4.3, but had connectivity issues to my Verizon Wireless JetPack.
So I decided to roll back to 4.2.2. I installed CyanogenMod 10.1.3 RC2 and lo and behold, I could one again use my JetPack for Internet access.
But then I started to have Sleep of Death issues. I used CM for over a week and and had 4 SOD problems.
I then found out about Wifi Fixer in the Play Store. Went back to stock 4.3 and installed Wifi fixer and all my JetPack problems went away.
But now I am getting SOD issues. I have been on 4.3 since Saturday night, and have had 4 SOD incidents.
I did a data, cache, and dalvik wipe in between each ROM install.
I'm contemplating doing a full factory reset and re-rooting, but I really don't want to backup all my data and reinstall it, unless I really have to.
Are you running an app like Crossbreeder? It has been known to cause random reboot issues and sleep of death.
If you started getting SoD on a CM based ROM running 4.2.2, and it continued after switching to stock 4.3, perhaps it is an app you installed at some point recently. or an app that was updated and the new version is causing problems.
EniGmA1987 said:
Are you running an app like Crossbreeder? It has been known to cause random reboot issues and sleep of death.
If you started getting SoD on a CM based ROM running 4.2.2, and it continued after switching to stock 4.3, perhaps it is an app you installed at some point recently. or an app that was updated and the new version is causing problems.
Click to expand...
Click to collapse
I had installed the Cyanogen cLock widget, because I really liked it. So, I thought that might be it. I deleted the widget, but I still had the issue with the SOD.
And now I am not sure why the pogo cable charging is so crappy. It used to be much faster than microUSB.
I am not running Crossbreeder.
apastuszak said:
I had installed the Cyanogen cLock widget, because I really liked it. So, I thought that might be it. I deleted the widget, but I still had the issue with the SOD.
And now I am not sure why the pogo cable charging is so crappy. It used to be much faster than microUSB.
I am not running Crossbreeder.
Click to expand...
Click to collapse
With all the changes back and forth, I recommend, as you suggested, doing a full reset, data wipe, etc. I was flipping between 4.2 and 4.3 AOKP ROMs and was seeing strange issues as well. I believe my problem was related to corrupted files, partition, etc for the /SDCARD or TIBU because I was flashing a lot of mods and playing around with programs. I finally did a full wipe of everything (backing up TIBU to dropbox first especially the apps that were not in Play Store) and did a clean, fresh install including the apps from Play Store - not TIBU. It was a pain of course having to reset it all back up, but it is working much better now.
If you can, backup via OTG so you have it.
OK, did a factory wipe and used Fastboot to push the stock ROM and stock bootloader onto the device. No Sleep of Death issues, battery life has doubled. Haven't tested the pogo cable yet. But overall it's good to be in a stable place.
Now trying to decide if I want to root again. I really didn't do all that much with root. I think I will leave it this way for a while to get a baseline and then tinker.
Whether you root or not it would probably be a good idea to make a Nandroid backup of everything so that if you have an issue again you have a completely stable and known good configuration to come back to.
Related
Does anyone have a logcat from their dead transformer, during/around the time when it died?
Has anyone noticed any trends in when it happens? I saw something about 82% battery but I think that's just a coincidence.
Please post here so we can get to the bottom of this.
Jcarrz1
I think this is dev, unless it's a hardware issue. But hopefully we'll be able to discern that.
I have had multiple sleep of death issues after rooting. When I flashed back to the stock Blob, they stopped. Every time I root to Blob V5 (I am on the most recent firmware), they come back. I tried MoDaCo's Rom - they still occurred. Trying Prime's Rom now - so far it's working without any sleep of deaths.
I was on MoDaCo's Hr4 for a few days and never had a sleep of death. Since installing Prime 1.2 I've had 3 or 4.
Since we've had completely opposite experiences I think we can safely rule out that this issue is ROM related.
I've used both those roms and never had a sleep of death. But I also used the root method without the v5 blob, just the standard GingerbreakBB.
I've had one sleep of death incident, using unrooted stock Transformer configuration.
mine case: downgrade back to 8.2.2.6 using SD method (EP101_SDUPDATE.zip) then Gigerbreakbb then the BLOBV5 => lots of SOD issue.
May be we must update to the latest 8.2.3.9 before break using gingerbreakbb and install BLOBV5?
BR
Blob 5 is made to work with 8.2.3.9... It will most definitely have issues with the old firmware.
I am beginning to think the issue is with one of my apps and its settings. When I am rooted, I use Titanium Backup to restore my data and maybe the reason for the SOD is because something in an application isn't playing nice with Honeycomb... Obviously when I am not rooted, I cannot restore the settings and thus no SOD.
I just flashed back to root with Blob V5. Going to see if there are any SOD issues before installing apps... Will probably install one by one to try to see if I can find the problem - A PITA, but I really want the SOD to stop.
Had it with latest asus Update, no root and 40% brightness + wifi sleeps while screen is off. Lockscreen was enabled.
Sent from my Nexus One using Tapatalk
Edit:
Had another one after changing wifi sleep policy. I think it is wifi related.
The-Nazgul said:
Had it with latest asus Update, no root and 40% brightness + wifi sleeps while screen is off. Lockscreen was enabled.
Sent from my Nexus One using Tapatalk
Edit:
Had another one after changing wifi sleep policy. I think it is wifi related.
Click to expand...
Click to collapse
Other threads are pointing to the WiFi scanning be enabled. I have flashed back to MoDaCo Hr4 (because it was more stable for me than Prime 1.2) and also disabled WiFi notifications and will report back if/when I get a SOD.
Unrooted, getting about one or two of these a day depending...... seems to happen more if I've left it sleeping for an hour or more.
Putzy said:
Unrooted, getting about one or two of these a day depending...... seems to happen more if I've left it sleeping for an hour or more.
Click to expand...
Click to collapse
this could relate to wifi scanning as well. were you connected, and what are your current settings?
Thanks for participating everyone, so far there isn't a conclusive answer.
However, could someone install log collector from the market, and leave it there until the BlackSOD happens, and then upload the file? that would be super awesome. preferably someone who gets them all the time. if the last thing in the logcat is consistently wifi-related, then we're on to something.
is there any firmware version on which NOBODY has EVER had a BlackSOD? This could be worth looking in to as well.
Well, I rerooted and have installed about 80% of my apps. So far no SOD. I have a few more apps to install and I usually freeze some of the unwanted apps. Will post an update later. Also, I read on other forums that fancy widget caused issues like this on other tablets. I had been using beautiful widgets I wonder if the way that tries to access wifi causes issues.
The apps I have yet to install are:
Watchdog lite, beautiful widgets, adfree android
Sent from my Transformer TF101 using Tapatalk
Just had one while wifi was disabled! I guess that makes it less likely that wifi causes the problem.
Next time I will upload a logfile!
Sent from my Nexus One using Tapatalk
I've had 2 so far, both with Hr4 and blob v5. Battery has been at different levels, so I think thats a coincidence.
Has anyone tested on a 100% Factory reset device (either with a custom or stock ROM?) That should help rule out any apps which may cause the problem.
FWIW, never had this issue (have run Stock, HR1 -> HR4 & Prime V1.2)
so far no SOD after a clean tstart
Had a SOD this morning on Hr4 so I will run Log Collector today and hope to catch another. I'm assuming that Log Collector is continually writing to my Gmail draft so it should be there after the full reboot? Doesn't seem like it will let me mirror logcat to a file on sdcard...
sent from a device using an app
I realize this isn't the least bit helpful, but after having several SoD issues, and trying all the fixes (and then undoing them), I haven't had the issue for a week now. Mine would do it sporadically -- it would happen once in a day, and then 3 times in a day -- and the only thing I've left changed is disabling the lock screen, but I think that's just coincidence. This will be a hard one for Asus to nail down.
Hopefully someone produces a helpful log for Asus, I'm sure some non-XDA people may think they have a dead tablet rather than one they have to force power down and reboot.
had my firs SOD today.
running prime 1.2 US. battery at 96%. wifi on.
spuniun said:
Had a SOD this morning on Hr4 so I will run Log Collector today and hope to catch another. I'm assuming that Log Collector is continually writing to my Gmail draft so it should be there after the full reboot? Doesn't seem like it will let me mirror logcat to a file on sdcard
Click to expand...
Click to collapse
So it does not seem that this app will work because it only collects logs in real-time, does not store them for later analyzing. What else can I use other than leaving adb logcat running?
sent from a device using an app
so i've noticed multiple times today (just got it yesterday, rooted) that the charging indicator flashes on and off. this keeps bringing it out of standby. although sometimes the screen turns on without it saying charging but that seems to be a known issue.
but whats up with the charging flashing
full reset and its still doing it
actually i think it has to do something with rooting
i used this http://androidflip.com/how-to-root-acer-iconia-a500-with-stock-honeycomb-3-1/
but i unrooted and uninstalled and its not doing it now....
any other root method for 3.1?
Strange
Never had this issue on my a500 - but have the exact same issue on my Samsung Intercept with a slightly damaged charging port - after unplugging the system will still show as charging and offer to mount as an external storage device - even though it's not plugged into anything.
Had the random screen on when I was still on a 3.0 based rom - have you registered your tablet with Acer and upgraded ota to 3.1? Can also manually flash 3.1 update.
best of luck!
i just updated my last post,
but yeah im on the latest ota 3.1 in the US and registered
lbhocky19 said:
full reset and its still doing it
actually i think it has to do something with rooting
i used this http://androidflip.com/how-to-root-acer-iconia-a500-with-stock-honeycomb-3-1/
but i unrooted and uninstalled and its not doing it now....
any other root method for 3.1?
Click to expand...
Click to collapse
Yes! Easy as hell too.
Check this out, and good luck!
(How to root a500 3.1 stock)
http://forum.xda-developers.com/showthread.php?t=1138228
(Edit: the method you linked to looks like the same method described here at XDA. May not solve your problem)
well cancel my happiness. did a reboot and now it fully thinks its charging. no flickering.
even plugged it in and unplugged and still says charging.
this time i plugged it in and rebooted. at least the notification went away
edit: and its back.
really strange....
May want to just return it and snag a new one if that is easy/possible.
After your full reset did you do any Modding/install any apps? May be possible something you are running is causing the issue, but I am really stumped on this one.
Could always get cwm running and reset the battery cache, but I am pretty doubtful that is gonna do anything.
same problem for me here.though I did not root my device yet.it shows charging with no charger plugged in.also recognized that my battery indicator sometimes remains on a certain percentage and hangs.after a restart it shows the actual battery level.I am on stock rom 3.0.1...maybe I send it back tomorrow.because this is really enoying...
yup. mine just started doing the hanging at one percentage til reboot
don´t know if it´s software or even hardware related
the fact that we have identical problems makes me think software
When placing phone call my device crashes with purple led flash.
cell signal normal, text messages work, cell data works
I'm not sure if problem lies in hardware or software(bad flash, radio, ect)
I replaced the digitizer
Currently running Kang ICS RC0-9.0 | faux123-v025
Had same problem with Neutrino 2.1
Any ideas or test suggestions?
PROBLEM SOLVED, WHERE DID MY FRIDAY NIGHT GO THOUGH?
*deleted post incorrect information
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
dac1227 said:
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
are you already on 2.3.4.91 ?
chamoy said:
are you already on 2.3.4.91 ?
Click to expand...
Click to collapse
No, I couldn't get the zip for 4.91 to flash for some reason so I did Neutrino 2.5 after sever data formats.
update: on on GB 4.5, same problem persists
SOLVED
How did you solve the issue?
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Well the issue was less solved but minimized in the end.
After many fastboot formats and CWM flashes, I ended up fruitcaking back to 2.3.4, that's when the problem started to be less of a hassle; meaning the screen would come back on and buttons/soft-keys were again responsive and a battery pull wasn't needed.
I re-installed Turls ICS and the problem is still present, but it doesn't hinder making or receiving calls, I just hold my breath with each.
I'm suspecting that when flashing either the kernels or roms, things are not getting cleaned and formatted as well as they ought to be. I know there is a universal CWM zip floating around somewhere (seen it in the skyrocket forum). We've had similar issues in the skyrocket forum where remnants of previous flashes were being persistent, or resistant to format attempts.
I messed with it for hours trying to fix so I cannot say for sure what I did to make it a non-immediate issue, but if others describe like problems I try and help.
xscottishx27 said:
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Click to expand...
Click to collapse
I was having the issue with Neutrino 2.1, 2.5; Turl ICS, and stock 2.3.4. The latter seemed to be the most effective method I employed to fix, without bricking.
any of you guys experience it? just long press the power button wouldn't help. I had to plug it to the charger and long pass the power button to reboot it. this is getting pretty frustrating... btw my n4 is 100% stock
jakkix said:
any of you guys experience it? just long press the power button wouldn't help. I had to plug it to the charger and long pass the power button to reboot it. this is getting pretty frustrating... btw my n4 is 100% stock
Click to expand...
Click to collapse
It has to be an app that`s causing that....
jakkix said:
any of you guys experience it? just long press the power button wouldn't help. I had to plug it to the charger and long pass the power button to reboot it. this is getting pretty frustrating... btw my n4 is 100% stock
Click to expand...
Click to collapse
Happens to me almost every time I connect it to my cars Bluetooth to listen to Pandora, and i'm on the latest CM 10.1 nightly.
SOD
I also happened yesterday and today, yesterday had cm 10.1 and in the evening I returned to stock 4.2.2 and happened again this morning. any suggestion?
My wife and I are both having this problem with our N4s. It's been happening on and off since about 2 weeks after we got them on January 7. I'm still debating whether or not to try an exchange under warranty. I'm not yet convinced that it would help, but it seems like it's only affecting a handful of us, so maybe it is hardware related?
Hmm hppnd with me too. Yst n today almost at same time. After playing with some apps or games.. Phone was hot..
Sent from my Nexus 4 using xda app-developers app
What rom/kernel if any are you guys on? I recently got the SOD. I am on the PA 3.1 and bundled kernel. Not sure what's causing it. My initial assumption was the themes in cm10. Now I think it's the launcher in question or lockscreen.
I am using Nova Launcher with slide/stock lockscreen. Nothing really has changed that I can tell within the last week. I uninstalled all my themes this morning to see if it was that causing the SOD.
Got the SOD this morning at work. Had to long press the power button a few times to boot it up. This time I uninstalled the Nova Launcher completely and reinstalled. Restored my widgets and seeing what that does later.
Happened twice. Once with unrooted stock, once with cm10.1. So i think this is an hw problem.
my battery screen looks exactly like this after SOD: https://code.google.com/p/android/issues/detail?id=35139
in my case long pressing to power button boots the device. no need to charger or button combo.
Forgot I posted here. I forgot to follow up. It turned out for me, there was a bad browser commit in the PA build in early March. I since reverted to a working nandroid and flashed the most recent rom. For others,I suggest to backup your apps and do a wipe. If that doesn't work, then maybe a factory reset?
i realized my SOD's occur at ~13:30 (1:30pm). Uninstalled a few apps(dash clock, rotation widget) and SOD's stopped. But today installed Onavo compression app than, bam!, SOD again(at 13:30 of course).
kpjimmy said:
Forgot I posted here. I forgot to follow up. It turned out for me, there was a bad browser commit in the PA build in early March. I since reverted to a working nandroid and flashed the most recent rom. For others,I suggest to backup your apps and do a wipe. If that doesn't work, then maybe a factory reset?
Click to expand...
Click to collapse
What do you mean bad browser commit?
Linsanity said:
What do you mean bad browser commit?
Click to expand...
Click to collapse
Basically the stock stuff was crashing the rom and causing the sleep of death. Have been fine ever since I reverted back to a working nandroid and dirty flashed the updated ones.
I am currently using the new version of pacman and it happened to me two nights ago.I reflashed and downloaded sleep of death fix app for charging. But I want to be 100% sure it won't happen again because I depend heavily on my nexus 4 for alarm. How can I be sure?
Sent from my Nexus 4 using xda premium
I just posted in the Android issue tracker this fix for nexus 4 SOD that worked for me :
It looks like there are different types of Nexus 4 freezing behaviour, all being lumped under the description: SOD.
My device (reliably) SODs after extendeded USB charging the very first time it sleeps; never happens while actually charging, just immediately upon disconnection; and it never happens in other circumstances.
However, I believe I now have a fix. If I only charge with a QI wireless charger OR if charging via USB, immediately sync with a QI charger upon disconnection, I never (it's been over a week now vs. every morning before) get a SOD.
Try this if you have the exact same problem I had. QI chargers are now available on eBay for less than £4 shipped.
NOTE: if you have a different sort of SOD issue, this may not work for you.
I have done countless searches and tried everything I possibly could to find a solution to my problem and nothing has worked.
When running any 4.4 rom, and I have tried pretty much all of them, I have this wifi issue. The problem is that if I have wifi turned on the phone starts randomly rebooting approximately every 15-20 minutes when the screen is off. I have tried every setting, upgraded and reset my router(dd-wrt) with different settings and a static ip, and tried different apps that are supposed to help with wifi issues.
This does not happen on stock roms and I have zero issues with any other devices on my network. The very limited amount of info any where that I have found with a similar problem all lead to dead ends. This happens regardless of being a fresh install with no apps installed besides gapps. I really just can not think of anything else to try. Please help me with my G2, I really want to like this phone. :crying:
From the complete lack of info I am able to find on this it would seem to be quite a rare problem. But if anyone has any suggestions for me I would really appreciate it.
No suggestions at all?
Mine is doing this too, however not as frequently. Are you using a proxy app? And do you have auto-wifi disconnect on?
It has nothing to do with the router. I'm 99.9% sure it's either a rogue app or a bad install.
greydelta38 said:
Mine is doing this too, however not as frequently. Are you using a proxy app? And do you have auto-wifi disconnect on?
It has nothing to do with the router. I'm 99.9% sure it's either a rogue app or a bad install.
Click to expand...
Click to collapse
No I'm not using any proxy apps or disconnect. It's not an app or bad install as far as I know. Like I have said this has happened with every install of any 4.4 rom that I have tried. Including, PA, CM and Mahdi. When installing any rom I always do a full wipe, cache, data, dalvik and system. Even without out installing anything besides gapps it happens. So I think I can rule out a rogue app or a bad install.
I have reinstalled countless times and it always pops up. On occasion there has been instances where the problem does not start for several hours after a fresh install but invariably the issue does come up and the reboots start again every 15-20 minutes when the screen is off.
I mentioned the router because, although rare, they can cause issues with connecting devices. Most of the problems that I have read about is usually the other way around though. The router crashing with certain devices connecting to them. But I have had zero issues with my router and any other devices but still thinking it could be possible.
I have a 4.2 rom(Energy) installed currently with no issues whatsoever. It is only KItKat that seems to be a problem. I just have no idea what it could be.
What model is your g2 and kernel? The only thing I can think of is you are changing sleep tweaks on the kernel and causing it to sod when in deep sleep. Are you undervolting?
greydelta38 said:
What model is your g2 and kernel? The only thing I can think of is you are changing sleep tweaks on the kernel and causing it to sod when in deep sleep. Are you undervolting?
Click to expand...
Click to collapse
It's the d801. Every kernel on every rom. I have tried using kernels as is or using Trickster to undervolt, overvolt, you name it, I've tried it.
Any other suggestions?
Project X-Ray said:
Any other suggestions?
Click to expand...
Click to collapse
Make a backup and wipe everything, and boot up into a totally clean rom WITHOUT installing Gapps for it. Then see if it keeps happening. I'm searching around and not really finding anything on this issue. Mine hasn't been doing it since I flashed the new AOSB build
greydelta38 said:
Make a backup and wipe everything, and boot up into a totally clean rom WITHOUT installing Gapps for it. Then see if it keeps happening. I'm searching around and not really finding anything on this issue. Mine hasn't been doing it since I flashed the new AOSB build
Click to expand...
Click to collapse
Well I took your advice. I wiped everything and did a fresh install, latest PA without gapps.The only thing that I have done is connected it to my wifi. I let it go for about 3 hours and had no reboots. So I installed Banks Core gapps. Again, I let it sit for 3 hours. No reboots. All the while it has been plugged in and charging. As I write this, I just unplugged it from the charger and within 2 minutes had my first reboot. We'll see if they continue.
So now, I wiped and reinstalled PA without gapps. I did not install anything else at all. Turned on wifi and started getting at least 2 reboots per hour without even using the phone at all. When I turned off the wifi it has been running for 10 hours now without any reboots at all. I am at a complete loss as to what could be the problem. Is there anything I can do?
Project X-Ray said:
So now, I wiped and reinstalled PA without gapps. I did not install anything else at all. Turned on wifi and started getting at least 2 reboots per hour without even using the phone at all. When I turned off the wifi it has been running for 10 hours now without any reboots at all. I am at a complete loss as to what could be the problem. Is there anything I can do?
Click to expand...
Click to collapse
I hate to say it, but I'm at a loss too. Best course of action I can see is for you to return to stock, email LG, and ask for a replacement for a defective device.