So I have the past few days I have been getting constant SOD's. I notice it happens more if I hit the button to put the phone to sleep and then within a few seconds turn it back on. But I can't get it to constantly do this.
Attached are the dmesg and kmesg
Edit: Looking at the logs my self it looks to be an issue with the modem keeps disconnecting which I reported with the new kernels from franco and AK. I am going to try flashing the Find7 radio and monitor it.
Related
Had read a few suggestions for fixing this "sleep of death" issue on the G tabs... doesn't seem anyone has posted this
I've tried multiple ROMS, multiple apps like Regpon Wifi stay awake etc. and multiple GTabs...
The only thing that repeatedly seems to completely fix the not waking after sleep issue is an app called "Captivate Keep Alive"
Instead of tying wake to WiFi or CPU, it lets you tie it to battery %.
Try it, let me know if it works on your ROM.
Tested working 100% for Vegan 5.1.1 and CM 7 Harmony.
Tablet used to require boot after leaving it, now it will always wake up, after 1 hour, 20 hours, etc. Plugged in or not.
Completly agree. I tried all ROMs, and Kernals(up to .40). Nothing helps, but Captivate Keep Alive.
I had a similar, but not same issue. My WiFi would turn off completely when teh screen went blank. I could not ping it. Turns out that I had to update my kernel to pershoot's 2.something.39. That fixed it. I do find it every now and then totally unresponsive but pressing the power button patiently 3-4 times wakes it up. I'm running CM7.
App works
So glad I found this thread. I was having this same issue using TNT Lite and installed Captivate Keep Alive. I have been able to turn on from sleep without the reboot.
My rule for wifi is to turn off when screen if off. I notice that my mail is still coming thru when the screen is off.
I'm getting a lot of battery drain. Anyone know what I can do to solve this issue?
What do you guys use for the rule of wifi to reduce battery?
what rom/kernel are you using (you should always mention thse when asking a question like this fyi). revolver just fixed this problem yesterday, try updting your rom/kernel....
I'm using the latest stock rom..I think 3.2?
How do you update the stock rom or solve this issue?
Root and flash a custom rom. Revolver 3.2.1 fixed this issue i think...
Sent from my TBolt using my f***king thumbs...
I am on stock 3.2 and no problems. Have you checked the battery info. That is the best time to check how much time the TF has been on and how much time wifi has been on.
It's true that wifi doesn't disconnect as soon as screen goes off. It maybe takes some minutes for wifi to actually go off. Also, if I am using any app that uses wifi (like radio streaming), wifi won't turn off.
Anywy, most of the time wifi will go out just a couple of minutes after screen goes off. Check settings, running apps and battery stats.
Regards.
The stock rom is set to time out 10 minutes after the screen is turned off I believe. The revolver rom now has an option in revolver parts to set how long till the wifi is disabled.
There are several apps that keep wireless and/or GPS alive after screen is off. This is due to the way the OS handles apps after you stop using them. Try turning off TF then restart and without running any apps, let is sleep. Then check to see if wireless went off.
same issue
Hey, I'm having a similar issue.
I'm on a B70 running revolver 3.11 and a stock kernel and I've noticed my wifi intermittently toggles the disconnect policy to "never" instead of "when screen is turned off".
I thought it was part of the custom wifi timeout from revolver parts but according to battery usage in settings (and massive battery drain) the wifi isn't actually being switched off when the device isn't in use (tablet idle rarely shows top of the list).
I've tried flashing new roms and kernels but haven't been able to work out the specific cause of the problem or how to fix it. I would have posted in the revolver discussion to find out how the wifi timeout is managed as this might have given a clue but alas I am a noob
Waffles
Honeycomb is not good at keeping wifi off with the screen when other apps request a connection
Grab "Auto Airplane Mode - by Don" from the market free and it does exactly that, screen off = radios off, screen on = radios on
Well my TF wifi off with screen off work except it work too good.
It work but after it goes to deep sleep it does not want to turn back on ( would need a reboot of TF for it to work again) so I set Wifi sleep policy to never and use Auto Airplane Mode.
Prime 2.1.1 w/ Prime OC kernel
*Detection* said:
Honeycomb is not good at keeping wifi off with the screen when other apps request a connection
Grab "Auto Airplane Mode - by Don" from the market free and it does exactly that, screen off = radios off, screen on = radios on
Click to expand...
Click to collapse
Downloaded this app and it works a treat. I'm a bit anal so I'll keep trying to investigate why the system isn't doing what it should but its nice to have something to save the battery in the meantime.
Hey all. My Skyrocket seems to be turning the screen on by itself at random intervals. Sometimes it will turn itself off by the screen timeout set at 30 seconds but sometimes I will have to manually turn the screen off. Sometimes after turning the screen off when I go to bed I wake up in the morning to see my phones screen on. I believe an app is causing this to happen but I am trying to figure out which one it is. Instead of wiping clean and never finding the culprit I want to spend some time digging. I caught the phone in the act just recently and grabbed the logs. It happened right around 1:30am. Please see attachment for log.
I looked over the log but did not see anything obvious. Maybe someone with more knowledge can take a peek at the log and find something of value.
Thanks!
I guess I should also mention my Skyrocket is rooted with stock rom and kernel running 2.3.5.
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
Hi!
Recently, my oneplus one has been misbehaving or acting weird. I'm running the latest CM13 (has been like this for the past 5 builds or so) and the latest boeffla kernel (also tried a couple of versions) here are the things it does:
Randomly freezes and turns off and won't automatically reboot (sometimes takes about 30 minutes before I can even hard reboot it sometimes the red LED is on and lots of unreadable partitions show up on my pc when plugging it in) and it will also enter some super battery drain mode where it can kill it's entire battery in less than an hour
the WI-FI randomly dies and won't reconnect until rebooted
Top part of the touch screen not really workig? Like the adress bars in browsers don't work but when I try to interact with the notification shade in that area it works fine...
Battery drain: not really an issue, just started happening today with nova launcher sucking the battery dry
And overall it's really slow...
I'm not sure if it's boeffla kernel or CM13 or the phone is just dead...
I tried to reflash a dozen times so not sure
Can anyone help me with this?
Same here but i have everything stock... Except Root and bootloader unlocked
Flash stock rom, make no changes don't even restore Google data just set it up as a clean device, and see if it's still misbehaving. If it is its hardware.