This post should actually show up in the respective development thread, but I am not entitled to post there (http://forum.xda-developers.com/showthread.php?t=1700904).
I recognized that my I9000 did not enter deep sleep anymore after I had upgraded my kernel from 0.79 to 0.98.2. I tried all kinds of things, but nothing changed. When 0.98.3 came out, I upgraded to that, but still no deep sleep. BetterBatteryStats indicated that "suspend_backoff" was part of the problem. I re-flashed several times, froze many apps, and tried to track down the problem with no success.
I ended up going back to 0.79 and from that moment, deep sleep was working again. Consequently, I suppose that kernel version Devil3_0.98 might have a problem with deep sleep.
Did anybody here see similar problems with 0.98? This might be an example: http://forum.xda-developers.com/showpost.php?p=28280095&postcount=1330
(ROM: AOKP b40)
I just flashed 0.98.3 again, and now deep sleep works there also. This leaves me puzzled...
Quote:
Originally Posted by Kurre
Use BetterBatteryStats to investigate what app is keeping your phone awake. You'll find free XDA version from chamonix's thread here in XDA
Sent from my GT-I9000 using Tapatalk 2
done that, did not see anything useful.
heres a screenshot from now, if anyone can help out with this.
Thanks
ATTACHED THUMBNAILS
Click to expand...
Click to collapse
(cited from thread http://forum.xda-developers.com/showthread.php?p=28364531#post28364531)
Hi, I am pretty sure that you have the same issue that I have (I respond here because I am not allowed to post in dev forum). I bet BetterBatteryStats shows the kernel wakelock "suspend_backoff" as topmost entry, right?
I have new insights about this. I can reproduce the problem with kernels Devil3_0.98.3 and Devil3_0.79 (the only one I tried). So, it is not caused by the current kernel version. Steps to reproduce the no deep sleep problem:
flash kernel --> deep sleep works, but no deep idle
enable "Toggle Deep Idle" in Devil Kernel Config
reboot --> deep idle works but only with TOP=on, deep sleep still works
enable "Bluetooth kill" in "Devil Kernel Config"
save init.d file in "Devil Kernel Config"
reboot --> no more deep sleep, BetterBatteryStats shows kernel wakelock "suspend_backoff", deep idle works with TOP=off
So, this seems to be kernel related, and Bluetooth kill seems to play a role. At the moment, we can either have deep sleep or deep idle with TOP=off working, but not both at the same time. Any ideas?
Segner said:
(cited from thread http://forum.xda-developers.com/showthread.php?p=28364531#post28364531)
Hi, I am pretty sure that you have the same issue that I have (I respond here because I am not allowed to post in dev forum). I bet BetterBatteryStats shows the kernel wakelock "suspend_backoff" as topmost entry, right?
I have new insights about this. I can reproduce the problem with kernels Devil3_0.98.3 and Devil3_0.79 (the only one I tried). So, it is not caused by the current kernel version. Steps to reproduce the no deep sleep problem:
flash kernel --> deep sleep works, but no deep idle
enable "Toggle Deep Idle" in Devil Kernel Config
reboot --> deep idle works but only with TOP=on, deep sleep still works
enable "Bluetooth kill" in "Devil Kernel Config"
save init.d file in "Devil Kernel Config"
reboot --> no more deep sleep, BetterBatteryStats shows kernel wakelock "suspend_backoff", deep idle works with TOP=off
So, this seems to be kernel related, and Bluetooth kill seems to play a role. At the moment, we can either have deep sleep or deep idle with TOP=off working, but not both at the same time. Any ideas?
Click to expand...
Click to collapse
suspend_backoff means that phone is trying to go to sleep but some process is "blocking" it from doing this. Bluetooth kill is known to cause this kind of problems..but I saw this same behavior without Bluetooth kill..and I couldn't find out the cause for this. Only thing I changed, was CPU governor, from ondemand to smartassV2. But I don't think that it would be the culprit.
Sent from my GT-I9000 using Tapatalk 2
Thanks for the info! Please let me know when you find a solution.
For the time being, I don't use deep idle. I have read that deep idle with TOP=on doesn't save any battery...
I am about to give up on this.
Do I really have to accept that Deep Sleep and Deep Idle with TOP=off don't work at the same time?
BTW, the same problem occurs with the recent Semaphore kernel as well as with the newest Devil3. So the thread title is misleading. I can't change it...
A kernel cleaning script did not help either. AOKP m6 also did not change anything.
Immediately after I kill Bluetooth, Deep Sleep stops working (while Deep Idle with TOP=off starts working)
flash JV* fw through odin.
flash AOKP M6.
let it boot.
flash devil kernel.
let it boot.
go to recovery - wipe\reset factory + dalvik + cache.
enjoy rom.
thats what i did when i had rom\kernel problems that didnt wanna go away.
as for Top=on - vibrator is on \ bt is on.
never checked what happens if i turn vibrator off.
Thanks everb00b, now I rebuilt everything from scratch: Back to stock, root, AOKP m6, gapps, and the most recent Devil3 kernel (0.99). Still, strange things happen, when I use btkill. Seems that it only happens when Wifi is off while I perform btkill.
Have you seen? In the Devil3 kernel thread, somebody showed up who seems to have similar problems like myself: http://forum.xda-developers.com/showpost.php?p=28503076&postcount=1556.
I will continue here to report my insights about this (still some postings missing until I can post in dev forum).
BTW, most of my apps were not restored although I had checked "automatic restore" in "backup&restore" settings. It's really cumbersome to restore everything manually. Anyway, this way, I can rule out that my problems had to do with my particular setup. So, thanks for your help. I will continue searching...
Related
I'm using CF's rooted kernel and nothing else on my KLA4 Note. No other alternative kernels, just the stock one. And yet I keep seeing strange issues with the kernel. Is anyone getting any of these two?
1) gps causing a wakelock in betterbatterystats in kernel section
2) fuelgauge also causing a wakelock in betterybattery states in kernel section
It doesn't happen often, but it has happened out of the blue. And before you ask, no, GPS was never enabled, no apps I have in my phone are using GPS too. Happened over the weekend with no other activity on the phone other than some calls. A reboot fixed it.
As for the fuelgauge thing, I have no idea either. It happened after removing my phone from a charger, and noticed that the battery was draining fast. Sure enough looking at BBS, I see fuelgauge wakelocking in kernel, whatever that is. A reboot fixed it.
Anyone else facing these strange issues?
If it helps to know, I have it too. I seem to be able to trigger the GPS wakelock issue when the Browser attempts to fix my location but is somehow unable to. But not always.
Fuel gauge. Seems random, but it might be related to the battery being too stressed and the level "rising" a bit when relaxed.
I've tried the stock android kernel and now am CFRoot kernel with Checkrom v5. If anything the gps issue has increased.
I had a high Android OS usage with CF kernel and LA4. I switched to Abyss Kernel and the OS usage is next to none now. No wakelocks except those for sync. Phone has deep sleep now and the battery life is outstanding.
Blue1k said:
I had a high Android OS usage with CF kernel and LA4. I switched to Abyss Kernel and the OS usage is next to none now
Click to expand...
Click to collapse
I had the same with stock kernel. On low-use days my kernel was using 40% of the battery!
It finally forced me to flash a kernel, and I chose Abyss. Kernel is now less than 5% pretty much all the time. Deep sleep is also most of the time, although I did not check well before that.
My phone randomly reboots. This happened over a few weeks ago, I wiped cache and monitored it, it fixed it.
Today, it just rebooted.
I think its more a software problem rather than hardware.
Any suggestions.
P.S. Not to threadjack, but I am also on LA4 CF Root with CheckROM
There's a separate thread in the Q&A section about the GPS Wakelock problem.
http://forum.xda-developers.com/showthread.php?t=1419087
Some ideas to try and avoid it, but unfortunately nothing definitive yet.
Just as an aside, personally I've been using the 'wake up lag' characteristic of the exynos when coming out of Deep Sleep as a clue to these wakelocks. If the screen comes on immediately, I suspect a wakelock of some sort and check BetterBatteryStats and CPUSpy.
Yesterday I got the ICS update via Kies.
Saw that my CPU was not going into deep sleep.
BetterBatteryStats showed the problem
fuel_alerted is forcing a kernel wakelock.
I tried searching the forums, and there are some fixes in some custom kernels.
However, I could not find out what exactly is fuel_alerted, why does this happen, and does it happen on all phones?
I believe taking out battery and putting it back in should fix the problem. Right?
Will it come again?
Whats the root cause of this problem?
I powered off, removed battery, and then put it in, powered up the phone. Now phone is going into deep sleep.
But I still cant figure out what is fuel_alerted, and whats the issue, why does it come?
i dont have this issue. i flash DDLP8 india yesterday.
tsk1979 said:
I powered off, removed battery, and then put it in, powered up the phone. Now phone is going into deep sleep.
But I still cant figure out what is fuel_alerted, and whats the issue, why does it come?
Click to expand...
Click to collapse
I had this on LPY, Did same as u did and its gone. Now yesterday i flashed LP8, its not yet there. Let us know if it comes again.
weng_cas said:
i dont have this issue. i flash DDLP8 india yesterday.
Click to expand...
Click to collapse
All ICS roms have this issue. You just have not hit it. Its a bug in the kernel. Somebody has fixed it in an open source code. I googled quite a bit, and also found the offending function
https://github.com/CyanogenMod/samsung-kernel-c1/commit/5f6d8422629002c530dcf30891c241fe3ee2e0ab
katyarevishal said:
I had this on LPY, Did same as u did and its gone. Now yesterday i flashed LP8, its not yet there. Let us know if it comes again.
Click to expand...
Click to collapse
Will do
Here is what the bug report says
"However, when the SOC starts rising, the wakelock was only destroyed"
Now what is SOC referring to? System on Chip? Does not make any sense. Can somebody look at the github page?
Try disabling the power saving mode and restarting.
Don't use power saving mode. I've only seen this Wakelock after I've checked the powersaving option.
Ironic. But true.
Sent from my GT-N7000 using XDA Premium HD app
SoC = State of Charge in this case.
It's another classic case of Samsung failing to fix well documented and fixed bugs. Not as severe as the eMMC brick bug (documented since before November by Google during Galaxy Nexus development), but still - documented and fixed by the community for many months.
I fixed this in I777 Gingerbread kernels back in October, I9100 kernel developers pulled in the fix fairly quickly. Despite the bug being documented and fixed by the community for months, it is still present in all of Samsung's ICS kernels.
It has been fixed in the CM9 kernel since the day I9100 Update4 sources were released.
It's also fixed in DAFUQ. (However a lot of other stuff is currently broken in DAFUQ.)
No need to pull the battery when you encounter it, just reboot. Rebooting is the only fix without flashing a kernel that has the bug fixed.
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
tsk1979 said:
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
Click to expand...
Click to collapse
I just noticed this param, I am not sure it was there before (I am on LPY)
Rebooting and it's still there!
Doing Power off now..
tsk1979 said:
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
Click to expand...
Click to collapse
No - FM is a userspace issue, as is MHL.
For CM9, the only things the source release affects are:
1) Speakerphone (already fixed)
2) Possibly a more reliable wifi driver (although CM9 may just kangbang pawitp's great work on the Aries kernels)
3) Backporting some performance features such as improved busfreq control
Entropy512 said:
SoC = State of Charge in this case.
It's another classic case of Samsung failing to fix well documented and fixed bugs. Not as severe as the eMMC brick bug (documented since before November by Google during Galaxy Nexus development), but still - documented and fixed by the community for many months...
...No need to pull the battery when you encounter it, just reboot. Rebooting is the only fix without flashing a kernel that has the bug fixed.
Click to expand...
Click to collapse
Found this thread after seeing this causing wakelocks in my i9100 S2. Thanks for the explanation.
However, rebooting - as well as powering off and switching on again still did not eradicate the fuel_alert problem and CPU Spy was showing my phone couldn't enter deep sleep.
Only after pulling out battery (and waiting for 1 minute for good measure) and powering up again did the bug go. CPU spy then reported my phone had entered deep sleep and the fuel_alerted entry was no longer showing in BetterBatteryStats.
Remove the battery and wait for 1 minute and reboot the phone , it will fix the problem.
To avoid it from happening again , remember to wake and unlock the phone every time before removing the phone from charging(Data cable & charger both).
I never unlock the phone before plugging and unplugging, and inspite of that problem is not reappearing.
So it may be completely random. I looked at the github code, but somehow could not figure out any relation to lock/unlock while charging.
It happened to me once and i removed the battery for 15 mins and it disappeared. But today it happened again. I do have power saving mode enabled but i dont want to again and again remove the battery to fix it. I charge my phone by turning it off and once its charged i remove the charger, let the display go off and then only turn on the phone. Do i need to turn on the phone before i remove the charger?
I think the power save mode has something to do with it. I didn't check the battery history before turning it on though but after a few days the Note didn't last 12 hours with only 1 hour of usage. The processor was awake even when the screen was off.
As suggested here I removed the battery for a few mins. I reinstalled the battery and charged it while the phone was still off. After a few hours of charging I turned the phone on and date/time defaulted to base time as expected. I observed battery behavior for a few days and the processor is now sleeping when the display is off and only wakes up every once in a while maybe to sync. BTW I only have Gmail sync on everything else is set to manual. And I haven't touched the power save option since
is there a list of known apps that cause the sleep of death?
i'm using the 7/30/12 mirage kang. the fresh install doesn't have SOD problems but after i restore my apps, if i let the screen go dark for ten minutes while wifi is running, i'm pretty much guaranteed SOD.
jeff.p said:
... if i let the screen go dark for ten minutes while wifi is running, i'm pretty much guaranteed SOD.
Click to expand...
Click to collapse
That *is* the SOD. It's not caused by an app so much as meeting those conditions. For a quick fix set wifi to turn off when the screen turns off. Search is your friend for more info/fixes.
jeff.p said:
is there a list of known apps that cause the sleep of death?
i'm using the 7/30/12 mirage kang. the fresh install doesn't have SOD problems but after i restore my apps, if i let the screen go dark for ten minutes while wifi is running, i'm pretty much guaranteed SOD.
Click to expand...
Click to collapse
Like MISRy said, it is not a specific app causing it. It is the fact that you leave wifi on with the screen off. And not just specifically screen off, but in deep sleep. But it is not consistent and not everyone gets it. Some of the devs could never make it happen. Usually it is when wifi is on with screen off and an app is using it that is the problem. So if wifi is on and being used, and at the moment you try to turn it on it is in deep sleep, bingo SOD. As I said in the other thread, look at my tips.
leapinlar said:
Like MISRy said, it is not a specific app causing it. It is the fact that you leave wifi on with the screen off. And not just specifically screen off, but in deep sleep. But it is not consistent and not everyone gets it. Some of the devs could never make it happen. Usually it is when wifi is on with screen off and an app is using it that is the problem. So if wifi is on and being used, and at the moment you try to turn it on it is in deep sleep, bingo SOD. As I said in the other thread, look at my tips.
Click to expand...
Click to collapse
i thought the fixed wifi module was included with all recent kernels
jeff.p said:
i thought the fixed wifi module was included with all recent kernels
Click to expand...
Click to collapse
No, the kernel and wifi kernel module are two different things. The wifi kernel module has to be matched to the kernel (it is a kernel module), but is a separate piece of software. It is in /system/lib/modules/twlan_drv.ko. No SOD patches have been used in any stock CM7 kernels or modules. I think Mrg666 uses a patched kernel for his Mirage build and sometimes it is enough, but SOD does not really stop until the patched module is used.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
leapinlar said:
No, the kernel and wifi kernel module are two different things. The wifi kernel module has to be matched to the kernel (it is a kernel module), but is a separate piece of software. It is in /system/lib/modules/twlan_drv.ko. No SOD patches have been used in any stock CM7 kernels or modules. I think Mr666 uses a patched kernel for his Mirage build and sometimes it is enough, but SOD does not really stop until the patched module is used.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
Click to expand...
Click to collapse
ok. thanks for the info. i'll try the module at http://d01.megashares.com/?d01=8VPCE7N and report back
jeff.p said:
ok. thanks for the info. i'll try the module at http://d01.megashares.com/?d01=8VPCE7N and report back
Click to expand...
Click to collapse
no SOD yet. awesome!
Can u set wifi to go off in settings somewhere or do u need an app like green power? I only ask because that was what I did but after awhile, it won't let the wifi come on at all until I remove the app and reboot
Sent from my NookColor using xda premium
purpleurkle said:
Can u set wifi to go off in settings somewhere or do u need an app like green power? I only ask because that was what I did but after awhile, it won't let the wifi come on at all until I remove the app and reboot
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Yes there is a setting. Go to wifi networks and select menu and advanced. There should be a wifi sleep policy setting.
I think there is no specific app which causes SOD
Dear all my friends who facing the SOD Sleep of Death issue with their Android devices...
i found that it is totally related to Wifi Sleep policy related... i just changed the setting last night n now after 8 hours it is running absolutely without SOD... i will also be inform u later if i will get my device out of SOD issue... all of u just have to do one thing.
Go to settings>wifi settings>
from the options go to advanced settings
there is one option: Keep wi-fi on during sleep (go to this option)
there is 3 options: 1. Always, 2. Only when plugged in, 3. Never (increases data usage)
u just have to change ur option from 1 to 2 or 3, then i hope u will find that u will get ur device out of SOD issue...
Regards,
Nauman
(sorry for the poor english)
nauman_waheed said:
Dear all my friends who facing the SOD Sleep of Death issue with their Android devices...
i found that it is totally related to Wifi Sleep policy related... i just changed the setting last night n now after 8 hours it is running absolutely without SOD... i will also be inform u later if i will get my device out of SOD issue... all of u just have to do one thing.
Go to settings>wifi settings>
from the options go to advanced settings
there is one option: Keep wi-fi on during sleep (go to this option)
there is 3 options: 1. Always, 2. Only when plugged in, 3. Never (increases data usage)
u just have to change ur option from 1 to 2 or 3, then i hope u will find that u will get ur device out of SOD issue...
Regards,
Nauman
(sorry for the poor english)
Click to expand...
Click to collapse
it's not working on my s6 sprint
Sprint network having any problems here
Sent from my QMobile i12 using Tapatalk
i'm chasing a battery drain issue.
i can leave my phone at idle even after a reboot and still even after hours of idle it never goes to deep sleep and shows 8 hours in the 384 mhz.
i have deleted apps, factory reset, flashed stock kernel, flashed factory image, NOT loaded the apps from google restore and still it comes up.
i have tried using better battery stats and all it shows is SUSPEND BACK OFF WIFI..
what gives? how do people use BBB when it is never specific with what is causing things, its so vague and generic.
my device SHOULD go into deep sleep if i reboot and leave it at idle right?
nothing?
I just want to know how so many people swear by BBB when all it ever does for me is show generic wake locks and not which specific apps are contributing to those wake locks.
Hi! I just wanted to tell you that this has been haunting me as well during the last 5 days.
Before, I had tremendously good deep sleep. But now I have the same problem. I have tried different kernels, reinstall CM. It must be app related.
Sent from my Nexus 4 using xda premium
nextelbuddy said:
nothing?
I just want to know how so many people swear by BBB when all it ever does for me is show generic wake locks and not which specific apps are contributing to those wake locks.
Click to expand...
Click to collapse
There are 2 fields there. Kernel wakelocks and partial wakelocks.
Kernel ones are those that are held by the OS. Partial are the ones that are held by apps. You can find out which apps are consuming battery by looking into it.
wifi wakelock is held by the OS and not an app. So you'll see it mentioned under kernel wakelocks. Most likely your wifi router isn't allowing your phone to sleep. Try disabling wifi and see if you still get wakelocks.
Sent from my Nexus 4
thanks guys
i tracked it down manually to the app called ULTIMATE ROTATION and ULTIMATE ROTATION LICENSE
as soon as i removed those apps no more wake locks and i can now deep sleep properly.
posted a message on the play store but no response yet
i have the same problem after i reflashed my rom! i didnt have this issue b4! im using the exact same rom with the exact same apps, i just restored my backup... im not sure wat is causing the problem... i tried everything with no luck :S
Hi, I have installed Quarx's awesome 4.4.2 kitkat build and I am very impressed with its performance so far. I read up on the recent comments saying that the build from 6-11 is pretty stable and I believe it's true. I'm also running the 2.6 kernel along with the aerokernel app by blechd0se.
as you can see from the attached screen shot, my defy isn't entering deep sleep... I've frozen a lot of unnecessary apps and turned airplane mode on while leaving the defy alone for some time but it's still draining really fast. there is no deep sleep happening.
does anybody know how I can improve this phone?
thanks!
UPDATE: It seems I fixed my own issue by looking into every running app that looked like they were trying to collect data or keep the defy awake. from there I stopped/unchecked the services and then rebooted into recovery to wipe dalvic/cache, fixed permissions
only until then did it start deep sleep! hope this helps others as well