sorry, ive been looking around and I see in the Liquid Rom thread that it has a SOD problem. I looked around for a bit and i couldn't manage to find what it stands for. I think i might have it because sometimes when i turn my screen on, the touch response doesn't respond. I have to turn off my screen and turn it on again to make it work. I'm unsure if its a aosp problem cause i don't remember getting this problem in Sense
It stands for sleep of death, so it is a deep sleep problem.
Its not an AOSP problem, Ive never had it on Dark Jelly CM10 at least.
SOD stands for Sleep Of Death like the above poster said, and can result in a number of things.
The TF101 was plauged by SOD, and on that device sometimes the screen wouldnt turn on after a deep sleep. It also did random reboots during deep sleep and hanged at the boot sequence - draining the battery in no time at all. That was very frustrating.
A workaround for the TF was to use an app that woke the device up every now and then, so it didnt deep sleep for long periods of time. It drained the battery a bit faster, but it was quite ok.
Personally I worked around it by never letting wifi turn off - even during deep sleep, then set up some task that used wifi such as weather updates every 30min, msn, rss feeds etc.
Basically, SOD is commonly used when you wake a device up and it doesnt act as it should and forces you to reboot/remove battery/wait for battery to drain/etc
Related
Okay, I've been trying to diagnose a somewhat annoying issue. I've been using a fairly simple set of conditions in the Llama utility to automatically disable Wifi when the screen turns off in CM7 to prevent a wakelock condition and reduce battery drain.
So I activate wifi, I reset the log in CPU Spy, and I lock the phone disabling the screen. When I reactivate the phone and check CPU Spy, wifi was definately off but the phone was never in Deep Sleep, so something was holding the wakelock I guess. I repeat the experiment with no changes and Llama still running, but this time I manually disable wifi before locking the screen. This time the phone immediately goes into Deep Sleep according to CPU Spy-- it works perfectly.
So what is the difference between Llama autodisabling and manually disabling wifi that leaves a wakelock active? I've repeated this experiment like ten times last night, and it isn't making much sense to me.
Thanks,
Gnat
I would love an answer to this as well. I can add that with juice defender ultimate the same thing happens. It will disable the wifi but the wakelock stays active. I have tried several settings and reboots and tests and the only thing that would get my phone to deep sleep was disabling JD.
mikel81 said:
I would love an answer to this as well. I can add that with juice defender ultimate the same thing happens. It will disable the wifi but the wakelock stays active. I have tried several settings and reboots and tests and the only thing that would get my phone to deep sleep was disabling JD.
Click to expand...
Click to collapse
I can't tell whether this is the exact same, because you make it sound like JD has the wakelock. In my case, Llama is running in both tests, the only difference is whether Llama turns off Wifi or I manually toggle it-- manual toggling puts it into deep sleep even with Llama running.
On the general battery issues on Triumph, one of the more helpful discussions I've seen is this one here-- http://androidforums.com/triumph-all-things-root/456795-cm7-triumph-battery-life-improvement.html. In it a quote from Tickerguy blesses the JuiceDefender approach to throttling data use for battery savings, but I don't think he had done any analysis regarding wakelocks. BTW, I reverted to stock today, and I am finding the exact same problems as CM7-- wifi imposes a wakelock, and Llama can't shut down wifi automatically without the wakelock persisting. I have to manually toggle wifi off before screen off before the wakelock is gone.
Regards,
Gnat
gnatd said:
I can't tell whether this is the exact same, because you make it sound like JD has the wakelock. In my case, Llama is running in both tests, the only difference is whether Llama turns off Wifi or I manually toggle it-- manual toggling puts it into deep sleep even with Llama running.
Click to expand...
Click to collapse
Sorry; the wakelock is WLAN. It is almost always active if JD is toggling wifi. I hadn't tried disabling wifi manually but leaving JD active yet. I just tested that and got deep sleep immediately. So it must have something to do with how it disables wifi isn't releasing the wakelock.
You know, after switching back to stock from CM7 I'm really not sure I'm not happier. With CM7 I was getting worse battery performance, which led me to start obsessing about wakelocks and deep sleep. Now that I am back on stock, I do the same analysis and see that I have the same problems with wakelocks and deep sleep-- but the battery performance is better so it's not that big a deal. I'm sure that there are things I could do to make CM7 have better battery performance-- but I wasn't enjoying the process and wasn't finding answers, so why bother?
It's like power management programs. I ran Green Power for a long time, and had some glitchy problems with being unable to get wifi to turn on even though it wasn't supposed to be managed while the screen was on. Then I disabled it, and you know what... my battery life was good enough to get me through the day. Froyo is good enough to get me through the day.
The wakelock was put in there on purpose to prevent the phone from hanging when WiFi was on and the phone went to sleep. I use my power widget to turn off WiFi before I turned off the screen unless I'm actually using it.
You could try and build it to see if removing the wakelock is still necessary. If you need help on that side, just post and I'll help. It's not hard, really.
I use awesome off to turn my pad on and off so I don't have to use the power switch all the time. I always do this so I don't have to go through the whole boot up process when I want to use it. I noticed that when I wake up in the morning the pad is dead or almost dead. Is there a better way to put this to sleep at night? There is always so much stuff running that kills the battery. I read on here somewhere that someone was not even losing 1% by putting it in some deep sleep. Is there a mode for long time sleep that does not use battery or run any processes? But without shutting it down all the way.
Sent from my Toasted Marshmallow using xda app-developers app
Toasted Marshmellow?
Can't you just set the tablet to sleep in 5 or so minutes after being inactive?
You can have the tab cut wifi off in sleep also.
I don't do the wifi off in sleep tho...sometimes it doesn't reconnect after a wake up.
I don't know what awesome off is...I'll have to check that out.
My tab just goes into sleep after 10 minutes when I set it down.
The problem is awesome off. It won't let the pad sleep and is constantly checking for movement, light levels etc. Dump it and use the power button to turn it off and on.
Battery dies
dpshptl said:
I use awesome off to turn my pad on and off so I don't have to use the power switch all the time. I always do this so I don't have to go through the whole boot up process when I want to use it. I noticed that when I wake up in the morning the pad is dead or almost dead. Is there a better way to put this to sleep at night? There is always so much stuff running that kills the battery. I read on here somewhere that someone was not even losing 1% by putting it in some deep sleep. Is there a mode for long time sleep that does not use battery or run any processes? But without shutting it down all the way.
Sent from my Toasted Marshmallow using xda app-developers app
Click to expand...
Click to collapse
I have Nook color power button donate that I got when I had my old rooted Nook color with flaky on off switch. It was in my google apps when I was loading apps on my infinity so I figured try it and see what happens lol It works remarkably well on my tab and does put it into deep sleep . See attached. I have not used my tablet much in last day but you can see that it does put it to sleep and turns wifi on and off and also reboots. Also BTW I then tried it on my rooted ICS leak Bionic and it gives reboot function instead of the long drawn out shut down then turn on process. It does not speed up any of these functions as far as rebooting.
Could be the "wifi location drain"-bug with google maps. From reading the forums it seems quite a few people have it without knowing it. You can of course disable wifi while sleeping, but this will not cure the main issue.
Turn the location settings on in google maps, then make sure that unneeded check boxes are disabled under location settings menu and you should be fine after that. The interesting part here is that google maps will drain the wifi even when the settings are not enabled, perhaps because you can't access the underlying menu without first enabling it. So only after you first enable this setting in maps will it work correctly.
Hopefully this helps, it did for me ..
Yoop,
I watched the awesome off YT video and it didn't look as though the tablet was being sent into full sleep.
I guess with it just grinding away essentially not shut down into a battery save mode it would die.
Doesn't the Tegra3 have a 5th core for minimum power processing or fast wake up?
Disclaimer: I searched the forums but couldn't find anything relevant.
Am I the only one whose tf700 acts really sluggish after it wakes up for a minute or two?
Is there any solution to this? It kills my main use case of the tablet (pick it up when I want to look at something in a pinch, and put it away when I'm done).
I'm on official ROM, rooter but not unlocked. This has been happening with the previous firmware versions as well.
I had the same problem for a while... most of the time I woke the tablet from sleep it'd be very sluggish.
I noticed that this happens when the wifi disconnected during sleep... it would have to reconnect and therefore all the services that required wifi would all start at the same time, throttling the system.
Turns out its the special setting in ASUS Customized Settings, "Disconnects network during sleep" that was causing this. It does exactly what it says, suspends network-related tasks when the screen goes off and resumes on screen on.
I initially turned this on because i was worried network tasks would drain my battery on sleep, but there doesn't really seem to be much of a performance difference with it on or off. So I'm leaving it off for now.
originalnabisco said:
I had the same problem for a while... most of the time I woke the tablet from sleep it'd be very sluggish.
I noticed that this happens when the wifi disconnected during sleep... it would have to reconnect and therefore all the services that required wifi would all start at the same time, throttling the system.
Turns out its the special setting in ASUS Customized Settings, "Disconnects network during sleep" that was causing this. It does exactly what it says, suspends network-related tasks when the screen goes off and resumes on screen on.
I initially turned this on because i was worried network tasks would drain my battery on sleep, but there doesn't really seem to be much of a performance difference with it on or off. So I'm leaving it off for now.
Click to expand...
Click to collapse
Hmm, I disabled that with the same battery concerns, but I'll give it a shot, thanks!
fincan said:
Hmm, I disabled that with the same battery concerns, but I'll give it a shot, thanks!
Click to expand...
Click to collapse
Also try a clean boot.
Hold down the volume down and power button when you power it on from cold. Let it go through the next screen without touching and it will clear cache automatically.
This does help as well anyway.
It's probably still quicker than most of us after we wake up..... Have you tried coffee?
Try turning off all bloatware. Mine used to be incredibly sluggish when waking up, and when I checked it turned on about 25-ish apps everytime i woke it up. Rubbish like Google Now, Talk, Gallery, etc. This slows the poor thing down to an insane level. Turned off all the random crap I would never use anyway, did a coldboot (sbdags describes the process up one post ^) and now it's instantly awake.
This topic has been up a couple of times before, perhaps most interestingly discussed in this thread.
It appears the problem still exists (asusdec_wake kernel wake), and I'm experiencing extreme battery drain during sleep with the dock attached. Currently running Cromi-X 5.4, and I have tried hunds 3.4.4, and _that 8 and 9 kernels.
It appears to behave as following: The tablet enters deep sleep with low battery drain (0.3% per hr with wifi off), and after a while (have seen it happen after a range of 1 - 5 hours) it starts draining quickly as asusdec_wake wakes the tablet up. It only occurs when the tablet is docked, it can occur at both high charge levels and when the dock is empty (mine always drains to 0%). It does not seem to matter whether wifi is on or off. I monitor the battery with better battery stats.
It's a real pity, since I have to turn the tablet off whenever I want to keep the dock attached.
Is anyone else experiencing this drain? Any suggestions for fixes?
Also: obligatory first post thanks-for-making-my-tablet-great to @sbdags, @_that and all the other contributors to Cromi :good:
rkha said:
It appears to behave as following: The tablet enters deep sleep with low battery drain (0.3% per hr with wifi off), and after a while (have seen it happen after a range of 1 - 5 hours) it starts draining quickly as asusdec_wake wakes the tablet up.
Click to expand...
Click to collapse
How do you know that it first enters deep sleep and that it's woken up later?
asusdec_wake is a wake lock which only keeps the tablet awake, so the question is what causes the wake up and keeps the wake lock?
_that said:
How do you know that it first enters deep sleep and that it's woken up later?
Click to expand...
Click to collapse
It might be a strong assumption, but it's based on the battery drain patterns I've seen. I've tried to monitor this a bit the last few days. Usually the battery drain is as expected during sleep for a while (whenever I check during this period, the asusdec_wake has not been active and the entire period the tablet has been in deep sleep), before it increases and stays high. I attach some screen shots where this can be seen. The change in slope in the battery graph is after about 7 hours. In those screen shots the deep sleep time reported by bbs was 6h24m. I'm not sure the reason for suspend_backoff, but I assume something is forcing the tablet to stay out of deep sleep. If I disconnected the tablet, there are no issues with suspend_backoff (and naturally not with asusdec_wake either).
_that said:
asusdec_wake is a wake lock which only keeps the tablet awake, so the question is what causes the wake up and keeps the wake lock?
Click to expand...
Click to collapse
Good point. Any tips on how this can be diagnosed?
rkha said:
It might be a strong assumption, but it's based on the battery drain patterns I've seen. I've tried to monitor this a bit the last few days. Usually the battery drain is as expected during sleep for a while (whenever I check during this period, the asusdec_wake has not been active and the entire period the tablet has been in deep sleep), before it increases and stays high. I attach some screen shots where this can be seen. The change in slope in the battery graph is after about 7 hours. In those screen shots the deep sleep time reported by bbs was 6h24m. I'm not sure the reason for suspend_backoff, but I assume something is forcing the tablet to stay out of deep sleep. If I disconnected the tablet, there are no issues with suspend_backoff (and naturally not with asusdec_wake either).
Good point. Any tips on how this can be diagnosed?
Click to expand...
Click to collapse
Try turning location services off completely for me in settings.
Does that help? Give it a reboot as well.
sbdags said:
Try turning location services off completely for me in settings.
Does that help? Give it a reboot as well.
Click to expand...
Click to collapse
Yes it did, thank you! 21 hours, only 3% down and asusdec_wake inactive. I will report back if things change.
Will add always turning this off when tablet screen is off to Tasker. Interesting that it caused this huge battery drain, given that gps and wifi was off anyways. Wakeups from com.google.android.gms decreased from many to nearly none when turning off location access, perhaps it is sufficient to turn of google apps location access in settings.
Thanks again!
rkha said:
Yes it did, thank you! 21 hours, only 3% down and asusdec_wake inactive. I will report back if things change.
Will add always turning this off when tablet screen is off to Tasker. Interesting that it caused this huge battery drain, given that gps and wifi was off anyways. Wakeups from com.google.android.gms decreased from many to nearly none when turning off location access, perhaps it is sufficient to turn of google apps location access in settings.
Thanks again!
Click to expand...
Click to collapse
It's Google now constantly polling for your location as far as I can tell.
I'm trying to help my mother revive her TF300T. She was running the stock 4.2.1 ROM and it was borderline unusable. Task switching was horrible and upon waking from sleep, when that worked, it would be several minutes before it would work smoothly - it definitely wouldn't work when background sync was going on. More often, once it went to into deep sleep, it would have to be manually rebooted since it would not wake. She also had an issue where the volume turns itself up.
I installed CM11 on there and much of the usability problems have been taken care of. It is much, much speedier. However, it appears it still will not wake from deep sleep, at least sometimes. The volume issue persists as well. The latter is probably a hardware issue. I'm wondering if the inability to wake is also a hardware problem. Any ideas?