So I have searched through all the forums for this problem without a solution. If anyone running this kernel (ie Quickwiz or TPC) could please get betterbatterystats from this forum and check for partial wakelocks? I'm getting decent time, but if I could find a fix to this wakelock it would increase. I think its kernel related though
fixed by installing juicedefender, probably can be chalked up yo some rouge app
Related
I've noticed that periodically I'd get a very long lasting wakelock. It doesn't seem to cause horrendous battery usage, per se, but it does seem to keep the phone up for a long time, and so I'd notice that battery performs slightly worse than usual.
BBS shows a wakelock caused by EntriesRefresh_wakelock, and under Running App, I'd see an entry for Google Search (EntriesRefreshIntentService).
Running - Omni Rom (latest)
Faux Kernel ( No custom settings)
noobismyname said:
I've noticed that periodically I'd get a very long lasting wakelock. It doesn't seem to cause horrendous battery usage, per se, but it does seem to keep the phone up for a long time, and so I'd notice that battery performs slightly worse than usual.
BBS shows a wakelock caused by EntriesRefresh_wakelock, and under Running App, I'd see an entry for Google Search (EntriesRefreshIntentService).
Running - Omni Rom (latest)
Faux Kernel ( No custom settings)
Click to expand...
Click to collapse
Might be worth your while posting in the better battery stats thread. They are good at diagnosing wakelocks
Here's a link: http://forum.xda-developers.com/showthread.php?t=1179809
BuT_TeR said:
I've noticed that periodically I'd get a very long lasting wakelock. It doesn't seem to cause horrendous battery usage, per se, but it does seem to keep the phone up for a long time, and so I'd notice that battery performs slightly worse than usual.
BBS shows a wakelock caused by EntriesRefresh_wakelock, and under Running App, I'd see an entry for Google Search (EntriesRefreshIntentService).
Running - Omni Rom (latest)
Faux Kernel ( No custom settings)
Click to expand...
Click to collapse
I had the same issue, so disabling Google now (opening Google now, settings, toggle it off) has stopped this wakelock for me!
Sucks a bit to turn it off, but I'd rather not have the wakelock than have good now info, I'll just wait for an update/fix.
YoHoJo said:
I had the same issue, so disabling Google now (opening Google now, settings, toggle it off) has stopped this wakelock for me!
Sucks a bit to turn it off, but I'd rather not have the wakelock than have good now info, I'll just wait for an update/fix.
Click to expand...
Click to collapse
Hopefully this works, what kinda **** is this google..
I've been playing around with some 4.4.2 nightlies (Slim, PA, CM, Gummy, OSE, etc) and I've noticed that all of them have some battery stat issues.... the stock battery app is registering the phone as awake 100% of the time (verified with other apps as not accurate)... and secondary battery apps like GSAM, BBS, WLD, all show odd information. GSAM (companion installed as system app) shows the correct totals for a module's total "held awake" time, but the actual wakelocks all have the same count and time (which all add up to the overall total... it's guessing). WLD also shows (totals are OK, but individual stats are junk). BBS isn't/can't filter out the zero'd stats and some of those stats are shown in such a way that it looks like it lacks some specific information and is trying to fill in the gaps.
I know Google messed with battery stats a bit to lock them down... I've installed the GSAM companion as well as the Xposed module to open them back up again. But this doesn't explain the STOCK battery app's problem in getting accurate results.
Anyone else see this? I've been trying to track down a wlan_ctrl_wakelock problem when I load 4.4.2 ROMs, but without the granular power stats, I really can't see anything of use (and what IS there, I can't really trust).
Is this just a case of things being too new with KK?
I'm on cm11 12/21 and ever since the battery stuff was changed back around the 12/16 nightly things have been weird. My stock battery app shows zero awake time, but GSam and BBS show the correct wake times (also have GSam companion and Xposed module for KK battery stats).
The problem appears in those apps when I try to see partial wakelocks - they're all ridiculously low, like 15 seconds with a 20 hour uptime. BBS says all the wakelocks are kernel wakelocks, buy when you check those it's all just PowerManager wakelocks, which are all the partials lumped together
For a wlan_ctrl_wakelock you can try the app Network Log - if you're getting those wakelocks, you'll see a lot of packets bouncing around from your phone to your router, or other traffic on the router (specifically if the kernel is sending/receiving a bunch of packets)
Sent from my SCH-I535 using XDA Premium 4 mobile app
scorchedsky said:
I'm on cm11 12/21 and ever since the battery stuff was changed back around the 12/16 nightly things have been weird.
Click to expand...
Click to collapse
Pretty much. I just loaded a nightly from last night... battery stats got fixed in the base code from the looks of it.
Thanks on the logging app... going to give it a look.... might just be a simple adjustment in my network, I hope.
There is more drain than 4.3 roms, but I'd venture to say it's related to coding of the device to the framework and it will improve as the roms advance. Wakelocks are the main culprit so get Better Battery Stats and see what's keeping the device awake.
For wlan, turn off wifi scanning in advanced wifi options.
Hi guys,
I got a really annoying issue with my 1+1, got my phone for 2/3 months.
I did already a lot to fix this issue but couldn't find a fix.
Battery status: battery savings..
Pics:
http ://imgur.com/a/dMmVb
Does anyone know a trick to fix the android system draining bug?
Your screenshots show absolutely no information. You need root and one of the following apps,
- BetteryBatteryStats
- GSam
- Wakelock Detector
Root required. From that point on, you'll know what app is causing your battery to drain via partial wakelocks and alarms.
Have you tried a fresh stock install of 38 r? Ota seems to result in poorer performance. Assuming your using 11s?
Disable "wake lock" and "stay awake" in Privacy guard to Google play services.
I'm running N5 with latest Xtra Smooth Odex Rom w/ default ELX 6.04 kernel. I noticed battery life was abysmal. I installed BBS and found wakelock problems with BlueSleep and several other BT-related items preventing device from ever entering deep sleep. After scouring interwebs, it seems GasBuddy was culprit. I uninstalled GB, cleared data/cache for BT services, rebooted, and am now enjoying greatly improved battery life, i.e., device entering Deep Sleep, Doze working as it should, etc.
And I think I may have posted in wrong thread.
Moderators please move to appropriate sub-forum
I am running into a Wakelock issue and I am completely stumped. For some reason, my phone refuses to go into deep sleep for hours on end. Better Battery Stats shows that the phone spends the majority of its time with the CPU at its lowest frequency, but refuses to go into deep sleep. The issue started when I clean flashed LinageOS back when I tried 14.1. Since 15.1 has recently released, I tried to have another go, yet the problem remains. I am using a Oneplus 5.
The very weird thing about these Wakelocks is, is that they are completely invisible. Wakelock Detector isn't showing any specific wakelocks (Advanced mode enabled), but does show that the phone isn't entering the deep sleep state. Not even for a single second. Better Battery Stats shows the same thing, with zero seconds spent in Screen off (deep sleep) and all the time spent in Screen off (Awake). No application is listed anywhere that's causing these wakelocks. They aren't visible under partial wakelocks nor kernel wakelocks.
Now this is where things get bizarre. I tried removing all my applications and reinstalling them one by one to find out if it was an app that was causing the issues. Each time I installed an app, I would check whether the phone would go into deep sleep when I wasn't using it. It turns out that the phone stopped going into deep as soon as Whatsapp was installed. Yet Whatsapp would never register more than a few seconds of wakelocks each passing hour.
I'm not sure where to even begin to try and solve this issue. Has anyone else ever experienced these kind of invisible / hidden wakelocks, and if so, how did you manage to fix these issues? Thank you very much in advance for helping me out
Nobody with a similar problem to mine? It's really killing battery life for me
Mushoz said:
Nobody with a similar problem to mine? It's really killing battery life for me
Click to expand...
Click to collapse
I think I may have something similar happening with WhatsApp. My stats show lots of time spent with CPU on and screen off. Wakelock detector shows WhatsApp at the top of the list. But I don't really understand how to solve it other than deleting WhatsApp, which I don't want to do. Did you get anywhere with it?
Ian
IanHodgson said:
I think I may have something similar happening with WhatsApp. My stats show lots of time spent with CPU on and screen off. Wakelock detector shows WhatsApp at the top of the list. But I don't really understand how to solve it other than deleting WhatsApp, which I don't want to do. Did you get anywhere with it?
Ian
Click to expand...
Click to collapse
No, I still have the same issue unfortunately. Though my issue seems to be slightly different than yours in the sense that Whatsapp is very low in the list. The total minutes of Wakelock is far below the total minutes of awake (screen off). But uninstalling Whatsapp instantly solves the wakelock issue. Out of interest, what phone are you using and what rom?
Mushoz said:
Out of interest, what phone are you using and what rom?
Click to expand...
Click to collapse
Redmi Note 4, Pixel Experience Oreo 8.1
I got here through a google search. I am not sure it's whatsapp causing this (haven't removed it yet) but on a Moto G3 with LOS 15.1 unofficial by Rahul I have the same symptoms.