Today I noticed my phone has been awake when screen is off and I had no apps running as I use greenify on pretty much all apps. I tried googling what is UID wakelock but no dice. There are many kernel wakelocks too, maybe thats keeping my phone awake? I have attached screenshots. I really hope someone can help. Im using OxygenOs and ak kernel.
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.
So im a flashaholic, and ill usually flash new builds every couple weeks if they've included performance or features improvements. Ive always had good battery life .5 to 1.5% an hour. Well lately its sucked, at around 3%/hr idle. I always use the same stuff, Xylon Rom, and francos kernel. Ive tried just about everything to try and figure out why its happening, even trying different roms and kernels. One thing i will say is i believe when i had the best battery life was before the latest system update. When i was using baseband .33. So im thinking that might be my next test, to try to flash the older .33 radio.
Here are all the constants as far as applications i install that people might think be causing problems, even though BetterBatteryStats really shows no problematic wakelocks to my knowledge, which ill post screenshots of later for you guys to analyze
Facebook
Messenger
DashClock
Ez Weather Widget
Mightytext SMS
Franco Kernel App
What ive tried so far
1. Restored my phone stock 4.2.2 image from google developers. Flashing all the img files via fastboot trying to start from a clean phone. Right after that i flashed latest Xylon rom and franco milestone 2 kernel. After that i install all my apps, customize my phone and such. I charged it last night pulled it off and let it idle through the night and it dropped from 100% to 85% ~3%/hr. This is what ive been getting for the past 2 months so im guessing the stock flashing didnt help do anything. Unfortunately i didnt save the screen shots of betterbatterystats for you guys before i decided to proceed to step 2 this morning.
2. Trying a different kernel this morning and also upgraded my .48 baseband to the .54 one. I flashed Faux kernel this time, and also his Faux123 App. I kept all the default settings just like i do with Francos kernel. Im currently charging my phone to 100% right now, going to drain it throughout the day, and then charge it up again, clear the battery information and let it idle overnight. Ill report back after that, including the BetterBatteryStats information. Hopefully you guys can help me get this sorted out.
The problem is not coming from the kernels or the baseband. Most likely the trouble is coming from your apps. Install "wake lock detector" to find the cause of issue. Optional: download "Greenify" and hibernate apps so they won't drain power and wake up constantly.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
The problem is not coming from the kernels or the baseband. Most likely the trouble is coming from your apps. Install "wake lock detector" to find the cause of issue. Optional: download "Greenify" and hibernate apps so they won't drain power and wake up constantly.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, ill install that app and include Wakelock detectors findings as well.
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
Hey, I am testing stock EU 6.0 battery life, for now not so good, DOZE doesn't do anything for me, same %/h as on lollipop, but questions is another. On Amplify I noticed "ICING" wakelock. It stands for Google Play Services and have some business with SMS. I cant find what causes to start this wakelock, but on stock 5.1.1 this wakelock had smaller wakeup time. Maybe someone can explain me? Why does this shows up?
BooBzi said:
Hey, I am testing stock EU 6.0 battery life, for now not so good, DOZE doesn't do anything for me, same %/h as on lollipop, but questions is another. On Amplify I noticed "ICING" wakelock. It stands for Google Play Services and have some business with SMS. I cant find what causes to start this wakelock, but on stock 5.1.1 this wakelock had smaller wakeup time. Maybe someone can explain me? Why does this shows up?
Click to expand...
Click to collapse
I always wondered this also. Amplify shows a lot of wakelocks but don't know enough about how to use app properly other than limiting the safe to limit wakelocks maybe change default 240 seconds to a greater number. Wonder what ill effects this has. I know I tried screwing with the alarms wakelocks and had issues.
jmileti said:
I always wondered this also. Amplify shows a lot of wakelocks but don't know enough about how to use app properly other than limiting the safe to limit wakelocks maybe change default 240 seconds to a greater number. Wonder what ill effects this has. I know I tried screwing with the alarms wakelocks and had issues.
Click to expand...
Click to collapse
You can limit icing wakelock (I did) I set like 14240 seconds
I could never do anything to stop com.android.gms wakelocks but I finally managed too. I had over 800 wakelocks on full battery today I had 11
Don't worry about it. Icing barely effects battery.
slicetwo said:
Don't worry about it. Icing barely effects battery.
Click to expand...
Click to collapse
I am not sure, but will agree with you, but I cant figure out what does this wakelock to appear, why on lollipop I havent this issue?