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
Related
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.
Hey guys,
I had the issue with the 40% battery burn overnight again. According to WLD, the CPU was awake for 96% of the ~11 hours since it was charged (which explains it). I want to make sure I'm reading these right, so I've posted screens of wakeup triggers and CPU wakelocks.
I've got Google Now turned on, the "OK Google" keyword detection turned off, location reporting on, location history on, and location services set to high accuracy (I use navigation and what not and would prefer to not have to toggle it constantly). Please see the attached screenshots.
Some googling of my own told me it's location reporting keeping it awake, which I'm afraid is the case, as I didn't have this issue for a while when it was off (it's also been on for several days and I haven't had this issue).
So, I have two questions in total. Is it Google Now's location usage that's draining my battery and keeping my phone awake? Also, since this isn't an every night issue, do you have any suggestions or recommendations to solve it without losing Gnow functionality?
I am running Carbon (July 1st nightly) and the Franco Kernel r55. Thank you very much in advance, this issue has alluded me and annoyed me for months.
Update: upon further research, I'm seeing that blocking wakelocks from Google Search / Google Now related location services will eliminate the problem without affecting Gnow functionality - is there any truth to this? I've also seen people claim to have disabled location reporting without loosing their weather, nearby events, etc. I worry that disabling the wakelock will impede functionality because I don't have the screen on often while traveling. I just can't seem to get a straight answer!
Update 2: after a phone call to Google (yes, they actually gave me a good answer), I was told that Location Reporting *only* tracks where you've been to give you travel time and similar things. Turning it off doesn't disable weather, nearby events, parking location, and so on, so it's looking like just disabling it is a good place to start.
turbofandude said:
Hey guys,
I had the issue with the 40% battery burn overnight again. According to WLD, the CPU was awake for 96% of the ~11 hours since it was charged (which explains it). I want to make sure I'm reading these right, so I've posted screens of wakeup triggers and CPU wakelocks.
I've got Google Now turned on, the "OK Google" keyword detection turned off, location reporting on, location history on, and location services set to high accuracy (I use navigation and what not and would prefer to not have to toggle it constantly). Please see the attached screenshots.
Some googling of my own told me it's location reporting keeping it awake, which I'm afraid is the case, as I didn't have this issue for a while when it was off (it's also been on for several days and I haven't had this issue).
So, I have two questions in total. Is it Google Now's location usage that's draining my battery and keeping my phone awake? Also, since this isn't an every night issue, do you have any suggestions or recommendations to solve it without losing Gnow functionality?
I am running Carbon (July 1st nightly) and the Franco Kernel r55. Thank you very much in advance, this issue has alluded me and annoyed me for months.
Update: upon further research, I'm seeing that blocking wakelocks from Google Search / Google Now related location services will eliminate the problem without affecting Gnow functionality - is there any truth to this? I've also seen people claim to have disabled location reporting without loosing their weather, nearby events, etc. I worry that disabling the wakelock will impede functionality because I don't have the screen on often while traveling. I just can't seem to get a straight answer!
Update 2: after a phone call to Google (yes, they actually gave me a good answer), I was told that Location Reporting *only* tracks where you've been to give you travel time and similar things. Turning it off doesn't disable weather, nearby events, parking location, and so on, so it's looking like just disabling it is a good place to start.
Click to expand...
Click to collapse
The data we need to see isn't shown in your screenshots. This is why I prefer BBS. You can just post a log and nothing will be missing.
Aerowinder said:
The data we need to see isn't shown in your screenshots. This is why I prefer BBS. You can just post a log and nothing will be missing.
Click to expand...
Click to collapse
Ugh, I knew I should have left it. I've got it installed now and will post a screenshot if it happens again. I've got Location Reporting turned off. I want to see if it will still give me the features I want, and if the battery drain issue stops, yippee. I will leave BBS there, however, in case it happens again.
turbofandude said:
Ugh, I knew I should have left it. I've got it installed now and will post a screenshot if it happens again. I've got Location Reporting turned off. I want to see if it will still give me the features I want, and if the battery drain issue stops, yippee. I will leave BBS there, however, in case it happens again.
Click to expand...
Click to collapse
All of the wakelocks that start with Nlp are due to location. Switching the location mode to Device only will stop them. Anything that relies on GPS still works fine. This should be the default setting.
I did a factory restore of the phone, latest Gapps, Carbon rom (07/07 nightly + 07/06 firmware), latest ElementalX Kernel now (so far, better temp/performance + equal or better battery). I know it's only an hour's worth of use, but a problem is pretty apparent.
Location reporting/history is off, Gnow is enabled, keyword detection is off. WiFi is on, and location services are in high accuracy mode. Why is a wakelock created by never released and how do I avoid that?
Is there any reliable setting I can use to avoid a random software issue eating up my battery? This inconsistency is driving me insane.
Hello all, I recently noticed that my OPO was not going into deep sleep. So I installed wakelock detector and to my surprise, nothing out of the ordinary was going on. I proceeded to wipe the dalvik and cache, still nothing, won't deep sleep. Last night I flashed franco kernel in the hopes that it would solve the problem, guess what, nothing, still won't deep sleep. The phone just drops to 300mhz and stays there for the minimum frequency.
I'm running liquid smooth 3.2 (4.4.4) with the recently flashed franco kernel.
Do you guys have any other suggestions on what to do?, I was just about to flash an entirely new rom and keep it barebones till the end of the week when cm 12s and oxygen os are released.
I'm experiencing exactly the same issue..
amd-dude said:
Hello all, I recently noticed that my OPO was not going into deep sleep. So I installed wakelock detector and to my surprise, nothing out of the ordinary was going on. I proceeded to wipe the dalvik and cache, still nothing, won't deep sleep. Last night I flashed franco kernel in the hopes that it would solve the problem, guess what, nothing, still won't deep sleep. The phone just drops to 300mhz and stays there for the minimum frequency.
I'm running liquid smooth 3.2 (4.4.4) with the recently flashed franco kernel.
Do you guys have any other suggestions on what to do?, I was just about to flash an entirely new rom and keep it barebones till the end of the week when cm 12s and oxygen os are released.
Click to expand...
Click to collapse
Maybe the PlayServices are the Problem somewhere here is a guid to prevent them to keep your phone awake
Actually play services did not come up in the battery stats to indicate it was indeed active. I ran through anything, there is nothing causing unnecessary wakelocks. So that's why I'm confused.
amd-dude said:
Actually play services did not come up in the battery stats to indicate it was indeed active. I ran through anything, there is nothing causing unnecessary wakelocks. So that's why I'm confused.
Click to expand...
Click to collapse
Play Services doesn't always show up as Play Services in the battery stats page in your settings menu, it quite often will show up as Android OS.
Transmitted via Bacon
timmaaa said:
Play Services doesn't always show up as Play Services in the battery stats page in your settings menu, it quite often will show up as Android OS.
Transmitted via Bacon
Click to expand...
Click to collapse
Not even that, as I said there was nothing android related nor was there any app in wakelock detector that was showing signs of a wakelock. For good measure I did follow the many guides on stopping google services etc. and none of them worked. Phone still won't go into deep sleep. Strangely enough it was wasn't affecting my battery life that much, was still getting about 6hrs on screen time with 14% battery left.
amd-dude said:
Not even that, as I said there was nothing android related nor was there any app in wakelock detector that was showing signs of a wakelock. For good measure I did follow the many guides on stopping google services etc. and none of them worked. Phone still won't go into deep sleep. Strangely enough it was wasn't affecting my battery life that much, was still getting about 6hrs on screen time with 14% battery left.
Click to expand...
Click to collapse
Sounds to me like your battery stats might just be screwy.
Transmitted via Bacon
So now I'm wondering, as well. What would an example of good/excellent deep sleep look like? % drop over time?
My battery stats show cell standby at 1%, phone idle at 1%, and over over eight hours go from 100% to about 86%. Would that drain be considered deep sleep, or good deep sleep?
I had a similar issue and able troubleshoot successfully.
Device:
- POCO F1
- MIUI 12.0.3.0, Android 10
- Magisk 21
What tried but didn't help
- There is no wake-locks active
- Tried Battery Saver and Ultra Battery Saver
- Tried Airplane mode
- Tried rebooting
- There is no significant battery drain (only 1.6% per hour)
- Tried disabling Proximity sensor
- Tried wiping dalvik-cache
I have followed the guide by Intel at https://software.intel.com/content/...-no-sleep-issues-in-android-applications.html
As I mentioned earlier, there is no active wakelock, that is why the troubleshooting was much difficult.
I have digged into `/sys/kernel/debug/wakeup_sources` and sorted processes based on the column `prevent_suspend_time`. The process `qtidataservice` was on the top. Not sure what it is, but it's probably from Qualcomm and running under the `radio` user.
The `strace` was showing nothing. I have simply killed that process. It's eventually re-created with a new PID. Interestingly the device began to go Deep-sleep while in idle.
A few months ago my phone's battery started draining twice as fast as it used to. At first I replaced my 3 year old battery, but that didn't help. So I rooted the phone and installed the recommended apps, which marked smdcntl1 and radio-interface as the culprits. I then s-offed the thing and tried a few combinations of ROMs: stock, Liberty 6th element and CM12.1; and radios: 1.15, 1.20 and 1.35a.
Once I moved from the stock configuration, the results are the same - the phone is awake 100% of the time, and now RILJ is reported as the villain (this might have been the case before the rooting too - don't remember, and I might have used less capable tools).
I have the location services off and so is the GPS, wifi and bluetooth; I don't use any social network (cr)apps; and I'm a very light user in general. My reception is ok, but the drain continues even during the night. I tried to block wakeups using Amplify and force deep sleep using Deep Sleep Battery Saver - neither made any difference. The only thing that lets the phone deep sleep is flight mode.
I'm now out of ideas. How can the insomnia persist over different roms and radios? What else can I try?
Greetings, I have a problem with constant wakelocks on my MI11i phone since the day I bought it. Those wakelocks drain battery by 30% overnight, but also cause increased drain during the day in standby too since they instantly kick in as soon as the phone is locked, overall resulting in poor battery life. Even thou I am not an advanced user and has no need of it, I went so far that I completely factory reset the phone(this was the 2nd time), then reflashed new recovery and new official ROM to see will that sort the issue, then for a good measure I also rooted it with TWRP and Magisk. I tried underclocking the cpu to the lowest but it makes no difference while in standby since obviously that isn't the case. I tried using icebox but there were no processes that had SNS or RMNET in their names, so I just froze some analytics apps. Both wakelocks are gone as soon as I turn on the airplane mode or switch to wifi. Any app that can help me freeze those or edit something in kernel?
I found a rom that fixes the wakelock, listed here https://miuiflash.com/roms/miui-csx/alioth/miui-csx-v13-0-8-0-stable-alioth
But i couldn't find a way to contact the author for more info can i fix the kernel myself