Mysterious kernel wakelocks on lollipop? - Nexus 5 Q&A, Help & Troubleshooting

Hello everyone. I've flashed the factory image of lollipop and wiped everything in the process. Last night I went to bed around 2 am, and as you can see my phone has been awake a lot after that. I installed gsam, which atm seems the only compatible battery app, and this is what I discovered: 25 min of kernel wakelocks in the time of wakelocks tab, but when i open the kernel wakelocks tab, it shows basically nothing even remotely that lenghty....
Do you have a similar situation?
Thanks,
TD

After a few battery cycles the situation hasn't changed, lengthy kernel wakelocks, but none in the kernel wakelock tab....

Related

[Q] Help the charge sleep!

Hello all,
I'm running Tweaked 2.1 with the 5/24 PBJ kernel. Everything works great, except that I've found my phone won't deep sleep after I've charged it for the night. The only fix I've found is to reboot.
So, to be really clear.
I turn it on - deep sleep happens.
Use it all day, deep sleep happens.
Charge it overnight,
Disconnect and no more deep sleeping happens, it just stays at 100MHz and the battery drains that much faster.
So, my clever cell-phone-friends, any ideas?
Go this thread: http://forum.xda-developers.com/showthread.php?t=1179809
Download Better Battery Stats from the bottom of the second post. Install it, and then wait for the problem to happen again. When you see that it's happened, run BBS and select the options to view partial wakelocks since unplugged. That will show you what is holding wakelocks (preventing the phone from sleeping).
stats
Okay, so, here are the wakelocks after last night's charging.
Partial:
* ImapFolderPusher.....
k-9
12s
* RILJ
Dailer
7s
Kernel:
* "RXNET_MSL_LISTENER_WAKELOCK"
48 m 2 s
* "vbus_present"
2 m 21 s
And it records 51 minutes since unplugged.
I've looked for anything about RXNET... before, and found nothing. Is it maybe something realted to wifi? RXNET sounds like some sort of network receiving thing. I don't suppose anyone else has this problem?
I've also read about turning on the screen while unplugging and other hacky fixes, but nothing has worked for me. Those were for other phones, so I didn't really expect it to work.
In any event -- an further ideas? Thanks for helping.
You definitely don't have an issue with partial wakelocks, but kernel wakelocks seem to be a big problem. 48m of wakelock out of 51m is bad for battery life. I did a quick search and couldn't find anything specifically on that wakelock either. I'll keep looking and see what I can find.
Imnuts is the person to ask about this one.
Sent from my SCH-I510 using xda premium
Fixed!
So, apparently, freezing the Rx Networks PGPS downloader app causes that wakelock. Unfreezing it has let my phone sleep again. Odd that it waited until after charging to be a problem.

Is anyone else's battery stats all wonky with 4.4.2 ROMs?

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.

[Q] No deep sleep but no wakelocks huh?

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.

LineageOS is here!!! [ROM MM]

LineageOS is here!!!
The title is enough, I think,
I haven't tested it yet but.... the first LineageOS ROM for our beloved Photon appeared !
https://download.lineageos.org/xt897
I've been 2 days using this rom on my xt926 so far is good and fast
Thanks, do we have to 'clean-install' this?
clean install was safe.
You'll get a broken notification status bar eventually and you'll need this:
https://forum.xda-developers.com/showpost.php?p=67444950&postcount=721
I spent half-a-day
palmwangja said:
clean install was safe.
You'll get a broken notification status bar eventually and you'll need this:
https://forum.xda-developers.com/showpost.php?p=67444950&postcount=721
I spent half-a-day
Click to expand...
Click to collapse
gapps package which removes CyanogenSetupWizard/LineageSetupWizard is broken and shouldn't be used.
There's no such issue with opengapps nano package which I use.
you can avoid wiping if you "hack" a bit.
I had only to defeat the check (adding the key to htmlviewer in the package.xml (or something like that)) and do a "pm grant com.android.systemui android.permission.READ_CONTACTS" via adb (to enable the logon screen).
Additionally, I did something like
for i in /data/app/*; do
pm install -r $i/base.apk
done
(could have small errors, is two weaks sine then ) to fix the other permissions problem (most with network status access)
It works apparently
Upgrade done almost flawlessly from LL resurrection remix to Lineage OS 13
Few apps had permission problems, i fixed it just restoring the app (app only, no data) using titanium backup.
Anyway I went back to RR given I like it more, and I can't see any real improvement on MM over LL
I am experiencing huge battery drain. Battery in idle last for about 8 hours. Even when phone was in airplane mode during night it fall from 100% to 75% during about 8 hours. Previously with Cyanogen I've lost maybe 3% during the night tops.
Battery stats does not shows any apps that goes wild. I've installed GSam Battery Monitor and it shows that battery is used mainly by kernel (~40%) and LineageOS (20-30%), but it was running only about half an hour. I will check tomorrow morning after airplain mode night, maybe something came out.
sc0ty said:
I am experiencing huge battery drain. Battery in idle last for about 8 hours. Even when phone was in airplane mode during night it fall from 100% to 75% during about 8 hours. Previously with Cyanogen I've lost maybe 3% during the night tops.
Battery stats does not shows any apps that goes wild. I've installed GSam Battery Monitor and it shows that battery is used mainly by kernel (~40%) and LineageOS (20-30%), but it was running only about half an hour. I will check tomorrow morning after airplain mode night, maybe something came out.
Click to expand...
Click to collapse
Have you checked if the CPU is entering deep sleep? My phone usually manages > 80% time in deep sleep. Of course that would depend on usage. Previous ROMs (nearly all) virtually never entered deep sleep. This one wallows in it.
If I leave it over night (clearing stats at the beginning) it gets very close to 100% I personally use CPU Spy, but there are many apps that would show you if you dont already have one.
I've installed CPU Spy, will see the stats after the night. I've also installed Greenify and I think battery consumption is better now, so I suspect one of my apps was preventing my phone from going to deep sleep.
According to CPU Spy my phone never goes to deep sleep when in airplane mode. I've checked this also with clean rom installed, without gapps or any other apps, just CPU Spy. I'm gonna open ticket in LineageOS JIRA.
sc0ty said:
According to CPU Spy my phone never goes to deep sleep when in airplane mode.
Click to expand...
Click to collapse
so, when its not in airplane mode, it does go to sleep?
I just tested mine, and even with a ton of apps, Xposed, Viper, Magisk etc etc it still went to sleep quickly. This ROM for me wallows in deep sleep. Previous ROMs hardly visited deep sleep if at all.
DiamondJohn said:
so, when its not in airplane mode, it does go to sleep?
Click to expand...
Click to collapse
Yes, the problem with battery drain when not in airplane mode seams to be fixed. It goes to deep sleep ~80% of the time when idle. I'm not sure what was the fix since there was update to LineageOS in between, and I was reflashing two times in the meantime, cleaning caches and restoring backup from recovery, so hard to say.
sc0ty said:
Yes, the problem with battery drain when not in airplane mode seams to be fixed. It goes to deep sleep ~80% of the time when idle. I'm not sure what was the fix since there was update to LineageOS in between, and I was reflashing two times in the meantime, cleaning caches and restoring backup from recovery, so hard to say.
Click to expand...
Click to collapse
Sorry, reading my post I guess was not clear. My phone DOES go to deep sleep when in airplane mode. XT905
============ edit
oh, and almost forgot. I am using Pico Gapps, and turn off auto updates and notifications on play store updates.
Hello, it looks like I'm experiencing the same problem. Battery drain on my photo Q running the last lineage os 14.1 (android 7.1.2).
When on airplane mode the battery drain disappears (even if I can't consider this phone a battery beast).
It seems curious to me, I was imagining that in all these months the problem was corrected.
Do you guys have a suggestion? Many thanks in advance
The thing is that my phone seems to suffer from battery draining (when not on airplane mode) even when running sailfish OS (flashed over cyanogenmod 11).
Could then be possible that it has some kind of hardware problem connected to the gsm/radio part? Except for the battery consumption It works fine tough.

SNS_SMD and RMNET_DFC wakelocks

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

Categories

Resources