Database Users

[Info][WIP] LET's FIGURE OUT the sleep of Death!!!! [NOT A ROM]

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

Any fix for the sleep of death?

I have had mine for about 9 days now, and it has dose the sleep of death thing twice already... i am running Prime 1.5 it seems that peoples screens dont work after some sleeps of death... just wondering on it.

Optimus-Prime said:
I have had mine for about 9 days now, and it has dose the sleep of death thing twice already... i am running Prime 1.5 it seems that peoples screens dont work after some sleeps of death... just wondering on it.
Click to expand...
Click to collapse
I know that when I installed Prime 1.5, I get "Sleep of Death" every hour... I went back to stock and "Sleep of Death" went away... I'm not sure if this issue was fixed yet. I was told last week that it might be kernel related issue. But in the meantime, you can also try a different kernel and see if that fixes the problem... If not, try a different rom or even use Prime 1.4. Worst case is to go back to stock 3.1.
I'm still using stock rom right now and plan on using it for a while...

ill have to give stock a test drive. i did see that when i changed roms i did get sleep of death.
we can just flash a CWM stock rom right?

I had this problem for the first time today. I'm on Prime 1.5.
I also had no sound when I got it back on. Had to reboot to get the sound back.
Any similar sound/sleep of death issues?
Any new information on a permanent fix for this?
Thanks.

ASUS is working on a fix for this. It has something to do with 'power management.'
Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.

I had it nearly every time I left the tablet on for more than an hour without touching it. Upgraded to stock 3.1 and it hasn't happened since... (I manually flashed it; didn't wait for the OTA if that matters..)

My first TF suffered a SOD but I think it was a screen of death not sleep of death. I could never get it back so I replaced it at TigerDirect. My current solution? I pushed the TF off to the side of my desk and bought a Xoom...

zephiK said:
ASUS is working on a fix for this. It has something to do with 'power management.'
Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.
Click to expand...
Click to collapse
I read Asus saying they were fixing hte dock draining issue, nothing about the sleep of death. I have never had this happen, though I'm on stock, and form the looks of it the peeps that are on custom roms have this issue so doubt they'd fix a non-stock problem.

zephiK said:
ASUS is working on a fix for this. It has something to do with 'power management.'
Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.
Click to expand...
Click to collapse
I also only saw reference to the dock issue being fixed in an OTA. If you have a link to any information about the fix they are working on, it would be most appreciated.
Thanks.

So i replaced everything with stock, and no sleep of death yet to happen. but i have been using it alot lately so ill let it chill for about the next 2 hours and see what happens.

Optimus-Prime said:
So i replaced everything with stock, and no sleep of death yet to happen. but i have been using it alot lately so ill let it chill for about the next 2 hours and see what happens.
Click to expand...
Click to collapse
Thanks... let me know if it works for you.

Bought my TF a week ago, with 3.01, NEVER has seen SOD; today -finally- OTA upgrade to 3.1 in the Netherlands; since upgrade SOD every time TF goes in sleep mode..
Great upgrade, thanks ASUS! Any solution (except downgrading) around, plz?

Last nights OTA update fixed my deep sleep problems. This update apparently included a power management fix.

I've had my transformer for 2 months now. I had it stock, always updated OTA, until the NVflash/APX mode rooting method appeared and then I flashed PRIME! v1.4 and never had any SOD until recently when I upgraded to PRIME! v1.5. However, I did two other things around the time of the v1.5 upgrade that could equally have started the problem, namely; I started using a 16GB SDHC card in the keyboard dock and I also connected HDMI to my TV for the first time using a C-to-A adapter (this also does not work properly - uinstable image - intermittent digital interference flickers along the bottom of the screen).
I have since re-flashed PRIME! v1.5 using the APX/NVflash method and have stopped using the 16GB SDHC card in the dock and now the SOD has stopped happening..... HDMI is still an issue but that could be the cable and/or adapter.

Deep sleep , could it be tegra 2 issue?
the Folio 100, the toshiba thrive and Asus TF has this problem. all of them have Tegra 2. if i set the folio 100 to 30 minutes before sleep i can use it as long as i don't let it go over 30 min before i wake up the screen. if i close the screen (via the button) i don't get deep sleep problem before 30 min has gone. so there is some problem related to the CPU and memory going to deep sleep and can not get interupts from the button anymore

My SOD seems to only happen when it's attached to the keyboard dock. If I leave it undocked, it never get's the SOD. I'm on a replacement dock, and the original dock I had never gave me the SOD either.
I have the latest firmware installed and that didn't make a difference.

No dock. But had my first SOD with Prime 1.6 + Netformer and IO fix OC'd to 1.5

My first post so I'm locked out of development forum with the relevant thread
http://forum.xda-developers.com/showthread.php?t=1070343&highlight=waking+sleepsleep+of+death
Anyway, had my TF for only a couple of days, goes to SOD two-three times a day already. I didn't play around with 3.0 much before doing OTA to 3.1 but 3.1 and now 3.2 still put it to this unnatural sleep.
Actually, it didn't wake up after updating to 3.2 itself.
From reading that thread the best probable cause appears to be the voltage issue when CPU clock speed changes - when waking form sleep clock speed goes up but voltage doesn't or something like that, and if some processes are left running, like logging to a file, the system never really goes to sleep so no problem with waking but a problem with catching the culprit.
Someone also said that in 3.2, by design, there should be even more sudden clock speed increases so SOD problem might become even more frequent.
One more possible argument for the voltage theory - SOD doesn't happen when TF is charging, meaning that CPU management is not that strict. Someone reported that Juice Defender, the app to minimize power consumption/CPU load, actually caused SOD on his TF.
The actual cause of SOD is a failure to get the correct value for blacklight on waking so looking at the display closely with a flashlight one still can see it running, allegedly, and can even unlock it. If that happens and the system is otherwise responsive maybe there's a way to force the backlight on, maybe some widget that toggles autobrightness on something. I'm waiting for my next SOD to test this theory, sometimes the screen doesn't look black, simply not light enough.
Maybe all I've said is nonsense but I'm an unrooted noob, I'm allowed.

Safe Mode

Is there any way at all to disable the Fascinate from ever loading into safe mode again? It's really annoying when it happens because I have to reset all my widgets.
I've flashed my phone several times and it happens with every rom that I've had on it so is it part of the baseband kernel?

Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.

johnnyplaid said:
Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.
Click to expand...
Click to collapse
X2
List off the steps you used when flashing these last few roms (and what rom specifically) that you say are making you boot into safe mode...I've only seen it once on my phone and 1 reboot fixed it and I never seen it again, but that was months ago and I just chalked it up to me missing a step?! I have flashed many roms since and never see safe mode again.
Sent from my SCH-I500 using XDA App

Im starting to think that it's more a problem with my Fascinate than anything else. It usually happens when I have to pull the battery due to it locking up. Sometimes pulling the battery out a second time still doesn't get me out of safe mode and I have to continuously do it until it does.
For the past few months I've been using CM7 and updating with nightlies. On Monday I updated to the stable GLITCH kernel and so far it seems to be running much better. It's always had a problem with randomly bringing up my keyboard and backing out of apps and I have not had that problem yet since putting the GLITCH kernel on it.
Figured I'd also note in here that the GLITCH kernel is not currently working with the newest Cyanogen nightlies. It bootloops and I found that out the hard way.
For now im running GLITCH v11.1ML and CM7 Nightly 35 and it's been great so far.

so glad I havent run into safe mode

[Q] iconia a500 touchscreen doing it's own thing

first off here is what my iconia is running and it's clock settings:
thor_rom_v14.2 @ min:456 max:816
okay so my iconia tab has gone crazy from the second i got it meaning i don't even have to touch it and it will click "back" out of an app out back in the browser or so on and it constantly does it even on the homescreen and at times it's so bad it's un-usable especially when playing a game i.e nfs shift can someone help me fix this with out me having to take it back as i really like this tab and do not want to do that. thank you

i'manoob said:
first off here is what my iconia is running and it's clock settings:
thor_rom_v14.2 @ min:456 max:816
okay so my iconia tab has gone crazy from the second i got it meaning i don't even have to touch it and it will click "back" out of an app out back in the browser or so on and it constantly does it even on the homescreen and at times it's so bad it's un-usable especially when playing a game i.e nfs shift can someone help me fix this with out me having to take it back as i really like this tab and do not want to do that. thank you
Click to expand...
Click to collapse
You're running a custom ROM with a custom kernel, having problems, and you're asking if you need to take back the tab?
Yes please take it back and get one of these here!

no I do NOT want to take it back, I refuse to get an Ipad never will I get one. I want to get this issue resolved without taking it back

i'manoob said:
first off here is what my iconia is running and it's clock settings:
thor_rom_v14.2 @ min:456 max:816
okay so my iconia tab has gone crazy from the second i got it meaning i don't even have to touch it and it will click "back" out of an app out back in the browser or so on and it constantly does it even on the homescreen and at times it's so bad it's un-usable especially when playing a game i.e nfs shift can someone help me fix this with out me having to take it back as i really like this tab and do not want to do that. thank you
Click to expand...
Click to collapse
Ok, let's see if I understand this.
You bought a tab, that has these issues immediately when you bought it?
Then you rooted and flashed a custom rom? Because I never would have attempted it knowing the display exhibited strange uncontrolled behavior.
Strange. I would have returned it before flashing.
Or did you buy it that way (pre flashed)? Or did it happen after flashing?
My advice, first, I would adjust the screen sensitivity settings. If that doesn't work, I would boot to recovery, do the 3 mandatory wipes, then reflash the rom. Do a nice check on things, BEFORE loading it with apps, and even then, I would load only what is necessary making sure things function before going to the next.
And stay away from apps like display adjusters and such.
If that doesn't work, try a different rom. Maybe one a little less cooked, like Harkon.
If not, and you don't want an iPad, then I may suggest an HP Touchpad. Hear rumors MS may use them to forray into the tablet business, and load windows7

Moscow Desire said:
Ok, let's see if I understand this.
You bought a tab, that has these issues immediately when you bought it?
Then you rooted and flashed a custom rom? Because I never would have attempted it knowing the display exhibited strange uncontrolled behavior.
Strange. I would have returned it before flashing.
Or did you buy it that way (pre flashed)? Or did it happen after flashing?
My advice, first, I would adjust the screen sensitivity settings. If that doesn't work, I would boot to recovery, do the 3 mandatory wipes, then reflash the rom. Do a nice check on things, BEFORE loading it with apps, and even then, I would load only what is necessary making sure things function before going to the next.
And stay away from apps like display adjusters and such.
If that doesn't work, try a different rom. Maybe one a little less cooked, like Harkon.
If not, and you don't want an iPad, then I may suggest an HP Touchpad. Hear rumors MS may use them to forray into the tablet business, and load windows7
Click to expand...
Click to collapse
Yes it had the problem when I bought it and before root and pre-flash but I figured it would go away concede I flashed a custom rom but I was wrong

i'manoob said:
Yes it had the problem when I bought it and before root and pre-flash but I figured it would go away concede I flashed a custom rom but I was wrong
Click to expand...
Click to collapse
And I tried like 4 different roms none have solved it same with the screen sensitivity adjustment

Should have returned it for replacement when you first noticed the problem.
Now, you'll have to return it to stock and return for a replacement.
Bad display from the factory.

had a same problem on stock 3.0.1. with some asus widgets but it desapired on stock 3.2. Then I installed Thor v14.2 the problem came back.Think it has to do with the base of his rom(Asus).
The thing with returning tab was that on stock rom its running normal.
Now I'm on honneylicious and everything works great.
Be sure to wipe everything before flashing.

Could be a brick, Could be hardware...

A Little History: :silly:
I have been running i9220ZCLP1...known bad kernel since whenever it was first available, April I think. Anyways, acquired that through flashing Rocketrom v5, according to the instructions provided at the time. Everything worked fine, other than contacts crashing and the wlan some times not enabling until reboot...common issues, as far as I've seen on these forums. One thing to note, is that unless the instructions at the time asked for a full wipe after flashing 5 (I'm almost certain they did not), then there has not been a full wipe performed while in this kernel.
The current issue:
The other day my phone froze on me...months after flashing and having used this kernel, waiting for something more solid to come out. After it froze...holding the power button turned it off, but the phone would not boot afterwards...to ics, to recovery, to download mode, nothing.
After some fiddling, I realized that it will charge and once it buzzes and the screen comes on showing a full battery, I can turn the phone on and it will boot...then freeze after getting past unlock screen. Or freeze and go black in download mode...didn't try recovery, wasn't interested in it at the time, but I'd imagine the same.
After removing the battery for a few days, then plugging it in til full charge notification, I was able to get it to boot again, where it froze at the boot screen, but went dark. After one more full charge...oddly, like a minute later, it booted to ICS fine and worked for 24 hours or so.
Now:
With a mind to flashing away from the bad kernel, I restarted the phone tonight from the menu in ics... it booted fine, so I left it plugged in to get a full charge and came back to a phone, screen still on, that shows same battery % as when I left it. And I'm back to where I started with this problem, powered off after holding power button a few seconds and now nothing.
Waiting for a full charge again, to see what happens...I'm guessing/hoping I'll be able to get it to boot again, with some more fiddling...
My question is whether this sounds like it's hardware (battery etc) or software (bad kernel etc) that is causing the problem.
If I can get it into download mode...plugged in, obviously, should I try OdinPC to a safe kernel?
Thoughts would be awesome. :fingers-crossed:

How about flashing stock GB via pc odin first and getting safe?

apurvapatel said:
How about flashing stock GB via pc odin first and getting safe?
Click to expand...
Click to collapse
+1 I've read a few people on ICS having charging/battery related issues over time. Worth seeing if it still happens on a gb kernel.
Sent from my GT-N7000 using xda premium

apurvapatel said:
How about flashing stock GB via pc odin first and getting safe?
Click to expand...
Click to collapse
OK, that's one vote for flash if I can get it running again. Thx, glad you read my post.

SpyderTracks said:
+1 I've read a few people on ICS having charging/battery related issues over time. Worth seeing if it still happens on a gb kernel.
Click to expand...
Click to collapse
Hmm, but how to get there...GB and all.
So now the vote is software. Any idea why this would happen much much later? No battery issues at all, just suddenly.
Maybe I'll buy a battery.

nebreprah said:
Hmm, but how to get there...GB and all.
Click to expand...
Click to collapse
A little searching would show you DrKentan's guide @ http://forum.xda-developers.com/showthread.php?t=1424997