yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer General] jrac86:
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.
[Eee Pad Transformer General] The-Nazgul:
Had it with latest asus Update, no root and 40% brightness + wifi sleeps while screen is off. Lockscreen was enabled.

Edit:

Had another one after changing wifi sleep policy. I think it is wifi related.
[Eee Pad Transformer General] spuniun:
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.
[Eee Pad Transformer General] Putzy:
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.
[Eee Pad Transformer General] jcarrz1:
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.
[Eee Pad Transformer General] jrac86:
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
[Eee Pad Transformer General] The-Nazgul:
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!
[Eee Pad Transformer General] Scottland:
I've had 2 so far, both with Hr4 and blob v5. Battery has been at different levels, so I think thats a coincidence.
[Eee Pad Transformer General] Highland3r:
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)
[Eee Pad Transformer General] SiL3nTKiLL:
so far no SOD after a clean tstart
[Eee Pad Transformer General] spuniun:
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
[Eee Pad Transformer General] dfin13:
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.
[Eee Pad Transformer General] madsquabbles:
had my firs SOD today.

running prime 1.2 US. battery at 96%. wifi on.
[Eee Pad Transformer General] spuniun:
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
[Eee Pad Transformer General] LANAtron:
Wow, this is incredible. I'm about to get a Transformer and their is an obvious issue here with the SOD.

What's more amazing is that someone is begging for information so he can try and create a fix and is being completely ignored?

Craziness...
[Eee Pad Transformer General] ogg1e:
It looks like I narrowed it down some more.

I only get the SOD when I have it docked to the keyboard and the keyboard has an SD card in the slot....

I removed the SD card and it's been working fine....
[Eee Pad Transformer General] amix3500:
i have my first sod when using stock firmware on 3.01 (unroot)..

then sod have been continue to happen after root and using prime rom 1.5 with many application and games installed which i don't remember..

but after flashing with only minimal application like flash, root explorer, it didn't have sod anymore (well, for about 3 days).. and here is the curious part, i installed games like spiderman which need ota install, then sod start to happen again.

is it connected to data transfer through wifi?
[Eee Pad Transformer General] player911:
Mine had the SoD until Prime 1.5 and its kernelv2.

It still freaks out when I try to copy large files from the internal to microSD card but that could be just the ape freaking out.

Asus Transformer 3.1 pwnd

www.MiiWiiChat.com

www.SnapSiteAdmins.com
[Eee Pad Transformer General] dreamtheater39:
surprisingly i've never been having SOD ever since the 3.1 update rolled in...never dies on me irrespective of the rom i've used so far
[Eee Pad Transformer General] rj3005:
+1

10char
[Eee Pad Transformer General] shawnathan9:
Have yet to experience this.

Sorry for you guys... Consider different MICROSD...? you never know...
[Eee Pad Transformer General] chrisc627:
I've had sleep of death twice since being on magnus latest release. When using magnus v3 it never happened. It happened several times on prime.
[Eee Pad Transformer General] tahdell:
The times I've had this is when the pad is sleeping and I lose my wi-fi connection. So basically it happens whenever I bring the pad out of my apartment.
[Eee Pad Transformer General] chatch15117:
never had SOD and I've owned mine since June 16
[Eee Pad Transformer General] almaalma74:
situation is same for me too

btw I had sod with total virgin not rooted 3.1 too, without any SD;

well the SOD is not related:

- root

- custom kernel

- custom rom

- SD
[Eee Pad Transformer General] deeren:
This is something related to honeycomb itself and their tetra chips I guess. From what I have seen, and all the latest current tablets experience it.
[Eee Pad Transformer General] EP2008:
No, I've had two froyo tablets that experienced the SOD too. Maybe it's just Android as a whole?
[Eee Pad Transformer General] almaalma74:
On SGS I9000 I had SOD in Eclair and Froyo, but never on Gingerbread. I've tried earlier every rom on SGS.
[Eee Pad Transformer General] Aryantes:
I managed to get two logs with this command.

cat /proc/kmsg > /Removable/MicroSD/asus-fail.txt

Problem I found was, that it doesn't SoD as often when Terminal Emulator is running in the background logging this.

http://www.animesekai.com/downloads/TF101/asus-fail.txt 1.35 megs

http://www.animesekai.com/downloads/TF101/asus-fail2.txt 568k

Hope this helps.

Just installed prime 1.6 and will attempt to get more logs.

I SoD pretty often, without logging it, with mobile battery saving mode on and off, doesn't matter.
[Eee Pad Transformer General] jhanford:
What if you were to issue the command via adb? That would at least remove Terminal Emulator from the equation
[Eee Pad Transformer General] Aryantes:
I'll try this next.

It appears that Terminal Emulator, will (sometimes) not allow the tablet to sleep fully, therefore not getting SoD. The keyboard wake up button often works here when it isn't supposed to.

Will try adb soon.
[Eee Pad Transformer General] almaalma74:
I have new experience with SOD, please try it somebody.

I have SOD of course, but if I set Screen TimeOut for 15 secs then SOD is gone, if I set it for 30 secs or 1 min then SOD comes. I know this is strange but works.

I got zero SOD with 15 secs Screen Time Out, for now.

(Wifi always on, Revolver 1.1.2 w/ Netformer 1.5)
[Eee Pad Transformer General] Aryantes:
Very interesting. I will try this today. My screen timeout is always set to 2 minutes or 1 minute.

~~

On another note. when I am logging via ADB, I can't get SoD to happen reliably. Same as running Terminal.

As soon as I stop logging, SoD instantly. So the act of piping these logs to another file is preventing the tablet from sleeping.

Any other ideas for retrieving logs?
[Eee Pad Transformer General] EP2008:
Damn, just had my second SOD in two days - there were the first since the 3.1 update, but they are happening under very different circumstances.

I almost always have my tablet docked, but these last two SOD incidents, I was using the tablet and then docked it and the next time it was turned on, the unit was off. I use a system monitor and it looks like the tablet turned off about an hour after it was docked - there's nothing else to explain it :(
[Eee Pad Transformer General] pitfuze:
My SODs had subsided for a few days since removing Wizz. Nothing running as a widget that updates from remote left. However I just got another after playing with web/IP camera programs.

(btw, more SODs, like every couple hours, when I was using ADW Launcher.)

Would your logging trouble indicate that using the logcat live wallpaper would keep SOD away? And if not, then where does that wallpaper store the log while displaying? Might there be any quantity of log remaining? If the SOD still occurs with it running, would the last image of the wallpaper show anything useful?
[Eee Pad Transformer General] Aryantes:
If you can prevent the thing from going into sleep mode, it will never SoD. This sleep mode is the one where pressing the keyboard dock unlock button doesn't wake it anymore. Different from screen timeout.

Since I have a running process that is actively writing to disk, its likely that this is preventing it from sleeping, until there is some period of inactivity in the log.

I guess it would be a workaround, run something in a terminal that just does something forever.

The log files are already written to disk, but we're just writing it to another location as well.

If I recall, some of these logs are deleted upon bootup. (could be totally wrong here) so it might be necessary to constantly copy before crashing.

Got one more log.

http://pastebin.com/jsy9Zvup
[Eee Pad Transformer General] EP2008:
Got another two... both happening shortly after I connect the tablet to the dock. So I either use the tablet in full dock mode or throw away my keyboard... neither option is looking good.
[Eee Pad Transformer General] chrisjm00:
I've had one already, and only had this TF since Wednesday. Mine did it when fully charged, still on the charger. I went to wake it up and it had shut itself down. Only Widgets I have are beautiful Widgets, one screen with maybe a dozen icons. Has anyone found a common factor to all of this? Rooted, unrooted, what apps people are using and so on? What are the charge levels when this happens? Oh yeah, I don't have the keyboard dock and still got it.
[Eee Pad Transformer General] Aryantes:
I've not tested on an unrooted device.

I do get the sleep of death on a fresh install of a prime rom, or any other rom.

In other words, install rom, leave every single setting at default, get SoD soon thereafter. Then I try playing around with settings to see if they make a difference but it seems to always happen.

Now testing the lower screen timeout.

If you get this problem often, then try grabbing a few log files from the instructions posted a few pages back. Hopefully glitterballs is still around.
[Eee Pad Transformer General] david_ag:
I was getting Sleep of Death issues after rooting, and overclocking my TF. I had overcloked it to 1.6 Ghz. I scaled that back to 1.4 Ghz, and I've had zero SOD issues anymore.

Hope it helps!
[Eee Pad Transformer General] Aryantes:
I upgraded to HC 3.2 using Prime 1.7 alpha and had no more sleep of death issues for a few days.

Now, I am using Prime 1.7 beta and still have no SoD.

I hope this is a cure!
[Eee Pad Transformer General] gee one:
I did some unsavory flashes with nvflash and I get the SOD every single time!

I think it goes into APX mode too, but have to wait until I get home again to verify.

Is there anything I should check to add another data point before I try reflashing with something more normal?

This was on "stock" unrooted rom that I rooted. I think it had SOD with the "stock" version. Stock was a mkodded 8656 OTA flashed through a modded CWM and probably a low battery.

sent from my cyanogen(mod) vision
[Eee Pad Transformer General] Disket:
Been getting SOD since I got my TF on 3.1. Still getting it after updating to stock 3.2 and also after rooting it. One thing I noticed is that it never gets SOD when docked and charging. Other times, it's random. Mostly when undocked, at least for me.
[Eee Pad Transformer General] gee one:
I ran fix permissions in CWM, which seemed to help. Before, it was SOD after every screen timeout.

I also noticed, before I fixed permissions, whenever I would click on a link in an email (gmail and stock asus/android) the screen would get dim. I don't have a default browser set, so I would expect it to pop up a dialogue box. After fixing permissions, it worked as expected.
[Eee Pad Transformer General] Disket:
How long have you gone without SOD since fixing permissions?
[Eee Pad Transformer General] techbeck:
Never had sleep issues myself. On Prime 1.6 and working great. I didnt root using the PURE method since CWM never EVER would install. In fact, when I ran the CWM bat file, it said it installed but messed up the ROM and stock recovery. So I had to ODIN back to stock.

I ended up installing Prime 1.4 which rooted my phone and installed CWM. Then I updated to Prime 1.6.
[Eee Pad Transformer General] republicano:
i was happy about my tf101 Till i read this post, i didnt know SOD happend, i have all those background data services off except the one required for the market,disabled automatic updates for my widgets, have it in auto brightness and i use wifi alot, done this since i got this (1 week) and no issues so far, not rooted on 3.2.screen timeout 30 secs, and auto rotate disabled.

i have system panel on to record my data for abnormal signs,no issue so far
[Eee Pad Transformer General] gee one:
I spoke too soon, it's still SOD'ing.
[Eee Pad Transformer General] fonze73:
No SOD after RMA

I sent mine in for RMA because of the SOD issue, started doing it while I was on a business trip. They replaced a "daughter board" (and the LCD due to a stuck pixel). I have not had any problem since. Running stock 3.2. I have a B4O unit.

Henry
[Eee Pad Transformer General] EP2008:
I'd be curious to know how that fixed the SOD issue, since it's common with every Android tablet running all versions of the Android OS.

If it is a hardware issue, this will be the last ASUS product I'll be getting - with light bleed, dock battery drain (apparently a hardware issue), speaker problems and now SOD (apparently a hardware issue), it's not worth the money for "dollar store" quality.
[Eee Pad Transformer General] Jedi223:
For the people interested. (and what this thread was intended for before people spammed all over :D )

Here are a bunch of crashdumps from my (badly SOD'ing) transformer.

All completely random and all mentioned 'fixes' have no effect whatsoever.
[Eee Pad Transformer General] EP2008:
Hey Guys, looks like Toshiba has fixed the SOD issue on their tablet - what's wrong with ASUS?

http://www.androidcentral.com/updat...mpaign=Feed:+androidcentral+(Android+Central)
[Eee Pad Transformer General] gee one:
OK, I reflashed to a sane image and the SOD is gone completely. I never had them before I flashed the franken-file, so I think it was either a bad flash because of a low battery or just incompatible bits and pieces rammed together with nvflash.
[Eee Pad Transformer General] Disket:
What do you mean by 'sane image' and 'franken-file'?
[Eee Pad Transformer General] gee one:
The franken-file was bits and pieces of the update blobs and other pieces of system images. I was trying to get a 8656 boot/recovery with an 3.2 system image. These all match in theory, but the system image came from a different nvflash batch.

The sane version is where the boot/recovery/bootloader all came from the same blob and I flashed the system via CWM.

There is something odd about the 3.2 OTA. I flashed back to stock 8239, but I couldn't flash the OTA, after sequentially upgrading. I think the fingerprint is off and the OTA hangs on the file checks.

I think my SOD's were caused by bad flashes, but that doesn't explain the SODs on stock systems.
[Eee Pad Transformer General] msticninja:
I had a few SODs a month ago. On the stock 7/11 FW, it seemed to be the "wifi scanning in nomadic situations" bug, same as my Archos. After a few of them in rapid succession, it seemed to go away.

On Prime 1.6, I had a couple SODs when I was using CIFS, and I set the CIFS mountpoint to /sdcard/Network. This meant that the stock Gallery indexer was trying to index all my network content. Once I moved the mountpoint to /Network, it stopped indexing, deleted about 500,000 media file entries, and never SODed again.
[Eee Pad Transformer General] Sememmon:
Has any progress been made on this? I am still having issues with random SoD's and am currently in discussion with Asus tech support about the issue.

-s
[Eee Pad Transformer General] fonix232:
Had this problem only once, with stock ROM, since nvflashing Prime 1.8, it never ever happened!
[Eee Pad Transformer General] The-Nazgul:
My SODs got better after each Asus Update. Since I upgraded to Prime or Revolver I never had one again..
[Eee Pad Transformer General] Popsiclestand:
I get sleep of death every single time my tablet goes to sleep while it is connected to the dock. Without fail it will power off. Rooted or unrooted. Stock or other ROM. Battery saver checked or unchecked. It is really annoying because now I can't really use my dock with my tablet because each time I close it or accidentally let it fall to sleep it will power down.

After calling Asus over 6 times, I finally convinced them to send me a FedEx label as I had already RMA'd the tablet once and the dock once for other issues.

Beyond the fact that they seem to break something everytime you send it in for repair, the tablet works great!
[Eee Pad Transformer General] Gwartan:
I'm having the exact same problem. out of the dock the tablet works fine, goes to sleep, wakes up. Once I attach the dock and let it fall asleep I have to hard power it down to use it again. Dam thing will even power itself back on when I know I turned it off before closing it and putting it in my bag.
[Eee Pad Transformer General] Popsiclestand:
I don't know if you've been able to solve your problem yet, but after trying many many different kernels I installed Blades 8-24-11 kernel and it seems my problems are solved. I am also running the latest version of revolver. Been using my tablet all day with the dock. Put it to sleep countless times, closed the lid and it sprang back to life each time. The dock is now completely discharged and I am only using it for the keyboard function and still no problems (before I had noticed that if the dock got down to about 20% I would start to have very frequent shutdowns even while I was using the tablet).

It looks like my problems solved. Hope this combination can work for you too.
[Eee Pad Transformer General] kino13:
Does anyone have a method to wake up from the SOD?

My tablet just keeps hanging up and going into SOD and I have no idea how to start it up again.

I have done everything in no specific order:

hold power button

hold power button+volume down

insert card

connect power

connect docking

repeat and rinse

It always ends up starting up, but I have no idea how...

The tabled had this problem since day 1, before AND after rooting, so I do not know what to think about it. I am seriously thinking in return it to the shop.

When it works is just perfect, but most of the time is just SOD.
[Eee Pad Transformer General] Danzano:
Did you o/c i found mine got in boot loop then sod then boot loop when o/c was to high so reflashed kernel and its fine now

Also had a wierd one where the light sensor was constantly re adjusting untill it crashed it wasn't noticeable untill i looked at ram dump hasn't happened since
[Eee Pad Transformer General] kino13:
Didn't overclock or anything.

The thing is, the tablet is now in front of me, dead. What do you guys do in this case? the power button for 10 seconds, wait, and then the start up does nothing in my case, do you always just wake it up that way? Because if that's the case, mine goes to RMA faster than light...
[Eee Pad Transformer General] Danzano:
You stated you had rooted it so a rma just yet probably would not be a good idea

Have you tried the same thing while plugged into adb to see if its just the screen?

If you can get the pc to read it and it is the screen you can blind flash it back to stock then rma it.
[Eee Pad Transformer General] kino13:
Thanks for the answers, but I finally decided to return the unit.

I "nvflashed" the original rom in one of the times I got it to start up (took me five hours! to start, 10 minutes to flash), made sure all my data was deleted (twice!), and returned the unit.

Next day I got a call from the shop to go take a new one, they could not even pass the point of setting up an account.

On that question, yes, I tried to log on ADB whne it was blacked out without success, but the unit was faulty, it was not normal at all that level of inestability.

I got a new unit, I rooted it the moment I arrived home, put the latest prime, installed Klemsin kernel, and finally installed setcpu and LOCKED it to 1000Mh, yes, NOT overclocked (didn't overclocked the previous unit either).

I have had NOT A SINGLE hang up of the unit. NOT ONE.

So, what have I learned from this? **** happens.

If you have an stock rom unit doing the idiot, maybe it's not you, you just got unlucky.

Thanks to everyone
[Eee Pad Transformer General] vittogn:
I hope it is an HW problem

I had a very frustrating SOD (in my case it was more a "SOR(eeboot)").

My 3.2.1 unrooted and recently formatted B6OKA unit in whatever condition (dock or not, wifi or not, lock screen enabled or not) was randomly reebooting also 5 times in one hour. The most of time it was wile in standby.

I lost the mood for fighting and trying alternative ROMS and/or kernels. :(

I've just opened the ticket for RMA and I'll update you about my experience with the new unit, that really can not be worse than my first days in the Android Tablet world!!
[Eee Pad Transformer General] matthian:
Im runnning Prime 2.1 on my TF and now stucked in the SOD as well. Sadly enough, pressing buttons in any combination does not wake the TF. But I'm connected to the TF via USB and can open a shell.

It there any command on the shell prompt to wake the TF?

Thanks in advanced for your help.
[Eee Pad Transformer General] the.joeba:
I'm getting some really really hard to wake from SODs. I've been able to get out of them eventually by just waiting a few hours then holding power and Vol Down and releasing Vol Down after about 5 seconds (I have no idea if that's even a thing).

I just got this off ebay, and may have to return it. It freezes up after a few minutes off use, and then goes into what appears to be the dreaded SOD.