Develop Bugs

Sudden BlueSleep wakelock 100%; how to figure out cause?

Hi folks,
My rooted but otherwise relatively stock G3 D851 suddenly has poor battery life. It turns out it's not sleeping due to a pair of wakelocks ( BlueSleep and msm_serial_hs_dma ) that are 100%. What's the best way to find out which app is pegging them? The only Bluetooth device I use is my car, and this wakelock problem only started in the last couple weeks (not exactly sure... sometime over the holiday).
I don't want to turn off Bluetooth... I like the auto connection to my car, and since it used to work fine without the wakelock issue when not connected, I don't think the phone's core functionality is a problem. I've seen threads on specific apps causing this (Gas buddy was a big one last summer), but I don't have the specific apps that I've seen reported as problematic.
So... what's the best way to figure out which apps are causing the pair of wakelocks I'm observing?
Thanks!
Marc

qpnp_fg_memaccess wakelock

Hello, with the last update of BetterBatteryStats we can see the kernel wakelocks of the LG G4. And i found something weird, a kernel wakelock (qpnp_fg_memaccess) waking the phone even more time than PowerManagerservice.WakeLocks (Sum of all the partial wakelocks/alarms not from kernel). Doing a quick research, i found something in reddit about Nexus 6P having the same wakelock, and that it's maybe related to battery fuel gauge, but memory access for controlling battery? it have no sense for me. Anyone knows what is it and how to stop it? I'm running Android 5.1, V10C build, rooted. Screenshot attached.
Thanks!
edit: i researched a little more and qpnp_FG= Fuel Gauge, so definetively it's something about the battery controller. Still not a clue on how to stop it.

jjhaohao said:
Hello, with the last update of BetterBatteryStats we can see the kernel wakelocks of the LG G4. And i found something weird, a kernel wakelock (qpnp_fg_memaccess) waking the phone even more time than PowerManagerservice.WakeLocks (Sum of all the partial wakelocks/alarms not from kernel). Doing a quick research, i found something in reddit about Nexus 6P having the same wakelock, and that it's maybe related to battery fuel gauge, but memory access for controlling battery? it have no sense for me. Anyone knows what is it and how to stop it? I'm running Android 5.1, V10C build, rooted. Screenshot attached.
Thanks!
edit: i researched a little more and qpnp_FG= Fuel Gauge, so definetively it's something about the battery controller. Still not a clue on how to stop it.
Click to expand...
Click to collapse
Having this same exact issue. Attached is a screenshot of mine. Hopefully someone can chime in on this as it seems to be keeping the phone awake for substantial periods of time. Posted a thread about it too.

the only thing that may work but not on mm xposed modules amplify

Amplify is not for kernel low-level wakelocks like these. Sorry for the double posting i didn't your post. Maybe thermalmod or some kernel tweak (with kernel adiutor maybe?) can mitigate this problem.

bumpity bump bump

I'm seeing them on my Nexus 5X, same percentages too. Fuel gauge might suggest battery monitoring too, but the only way to check seems to be freezing the one app that can tell us whether they're still there...

Some devices such as printers on a network can broadcast packets that can wake your phone up a lot. qpnp_fg_memaccess is related to that. If you are on a home network use static IP, but on a corporate network you have no real control but not use it.

Is there any solution to fix this?
Sent from my Nexus 6P using XDA Labs

Battery drain in Nexus 5X while dozing: GPS is turned on sporadically & RILJ

Hello everyone,
I have a Nexus 5x with android Marshmallow 6.0.1, and for a long time now I'm having problems with Doze feature overnight. On a regular basis when I'm going to sleep - I turn off wifi and mobile data. Some mornings I wake up to see that battery was drain by almost 10% even though doze was active some of the time.
I attached the graphs of "Battery Historian" for last night. Though the battery drain is not horrible in this case, there are two things that I don't understand why they occur:
1. between doze periods, GPS is turned on. On my device "Location" is off and also "WiFi scanning". When I checked which app used GPS during this log, it says "com.waze", which is the domain of the Waze navigation app. However, even if one of its services does come to life between dozes, I don't understand how it is able to turn on GPS location without my active permission. I should say that some night another app will do that, like Tinder.
2. One wakelock that governs the wakelock charts is RILJ, which I understand is connected to location approximation using cellular networks. While the first problem I mentioned happens to me for several months now, this wakelock appears in the logs only recently. I think it relates to an app I recently installed called "Smart Wifi Toggler" which is supposed to automatically turn WiFi on/off depending on approximated location triggers. I uninstalled the app the same day I installed it, however since then RILJ wakelock always appears in the logs.
Last, I wonder if I should upgrade to Nougat. I understand Doze is better utilized with it, but I heard many users desire to downgrade back to marshmallow. In the case I do upgrade, I will perform cache and memory wipe so I don't know what will happen to these bugs. And the researcher in me still wants to know the sources of these errors.
Any help with these matters will be greatly appreciated.

qcom_rx_wakelock on University WiFi Causing Android OS/Kernel Battery Drain

When I got my OP3 I noticed that my battery wasn't quite as good as some had been reporting and that there was a lot of drain going on while the phone was off. After a while I started to notice that I was having bad wakelocks only when I was on any WiFi network on campus. When I went home for Thanksgiving, this battery drain was completely eliminated and I was easily getting 6+ hours of SOT which is almost double what I was getting. Once I came back to school, the battery drain came back. I did some research and everything seemed to point to the qcom_rx_wakelock which seems to be an issue on many school/work networks. I ran Wakelock Detector while on WiFi and this confirmed that qcom_rx_wakelock is the cause of the drain.
I am on version 3.2.8 and completely stock and I would like to keep it that way. This wakelock is an issue on the network's end and from the sound of things there aren't really any software fixes that I could do. I've read that most battery saving fixes such as using Amplify or flashing a different kernel don't help anyways. Does anyone have any ideas on how I could stop this? Are there any changes to the network that the school could make to alleviate this issue? I doubt they would listen but it's worth a try. Or are there any other things I could try?
Also, I should mention that I tried the simple fix of turning off the setting "Keep WiFi on During Sleep" which prevented me from reconnecting to the WiFi even when I turned the phone back on. The only way I could reconnect to the network was rebooting my device.

same with me.
i open qq in background. if i connect to the college wifi, screen off wake time is up to 50%;if i connect to my router,it's about 12%.. BTW,i use betterbatterystates to see my wake time.

Flash Franco Kernal, it has this WiFi wake lock fix.

cstrock said:
When I got my OP3 I noticed that my battery wasn't quite as good as some had been reporting and that there was a lot of drain going on while the phone was off. After a while I started to notice that I was having bad wakelocks only when I was on any WiFi network on campus. When I went home for Thanksgiving, this battery drain was completely eliminated and I was easily getting 6+ hours of SOT which is almost double what I was getting. Once I came back to school, the battery drain came back. I did some research and everything seemed to point to the qcom_rx_wakelock which seems to be an issue on many school/work networks. I ran Wakelock Detector while on WiFi and this confirmed that qcom_rx_wakelock is the cause of the drain.
I am on version 3.2.8 and completely stock and I would like to keep it that way. This wakelock is an issue on the network's end and from the sound of things there aren't really any software fixes that I could do. I've read that most battery saving fixes such as using Amplify or flashing a different kernel don't help anyways. Does anyone have any ideas on how I could stop this? Are there any changes to the network that the school could make to alleviate this issue? I doubt they would listen but it's worth a try. Or are there any other things I could try?
Also, I should mention that I tried the simple fix of turning off the setting "Keep WiFi on During Sleep" which prevented me from reconnecting to the WiFi even when I turned the phone back on. The only way I could reconnect to the network was rebooting my device.
Click to expand...
Click to collapse
I was on stock... switched to FreedomOS 1.7 (3.2.8) with ElementalX kernel. No WiFi darins.

cstrock said:
When I got my OP3 I noticed that my battery wasn't quite as good as some had been reporting and that there was a lot of drain going on while the phone was off. After a while I started to notice that I was having bad wakelocks only when I was on any WiFi network on campus. When I went home for Thanksgiving, this battery drain was completely eliminated and I was easily getting 6+ hours of SOT which is almost double what I was getting. Once I came back to school, the battery drain came back. I did some research and everything seemed to point to the qcom_rx_wakelock which seems to be an issue on many school/work networks. I ran Wakelock Detector while on WiFi and this confirmed that qcom_rx_wakelock is the cause of the drain.
I am on version 3.2.8 and completely stock and I would like to keep it that way. This wakelock is an issue on the network's end and from the sound of things there aren't really any software fixes that I could do. I've read that most battery saving fixes such as using Amplify or flashing a different kernel don't help anyways. Does anyone have any ideas on how I could stop this? Are there any changes to the network that the school could make to alleviate this issue? I doubt they would listen but it's worth a try. Or are there any other things I could try?
Also, I should mention that I tried the simple fix of turning off the setting "Keep WiFi on During Sleep" which prevented me from reconnecting to the WiFi even when I turned the phone back on. The only way I could reconnect to the network was rebooting my device.
Click to expand...
Click to collapse
I'm having the same problem but what's new for me is that I'm connecting to the same router from last week I'm facing this issue on any ROM but IDK how can this happen bc my router are same as before it used to work fine before.
I guess it a hardware fault?

Battery Drain due to qcom_rx_wakelock

Anyone knows what this qcom_rx_wakelock is?
Im currently on CB8 clean flashed it.
Battery drain too high due to this particular wakelock.
Anyone knows how to get rid of it?

It's a wakelock that often happens when you are connected to a large secured network like a university or company. The network itself is waking your phone up and keeping it in an active state even when you are not using your phone. I'm in the same situation as you on 3.2.8 and I have heard that the only way to stop it is by flashing elementalx which apparently is capable of blocking the wakelock. I think there are probably some fixes that whoever controls the internet network in your building could make but I have no clue how to go about that.
I made a post recently about this here but there isn't anything too helpful in it
http://forum.xda-developers.com/oneplus-3/help/qcomrxwakelock-university-wifi-causing-t3514414