Database Info

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.

Google play services wakelock after update 6.1.74

After updating to latest version of Google Play Services I have started to notice some sort of partial wakelocks. After 6hrs use I've got 44mins wakelock by google play services. Has anyone else noticed such behaviour? I have tried Purity Rom, Cm and Carbon just incase if there's difference, but I've encountered the same wakelock always. Here's what wakelock detector shows

http://forum.xda-developers.com/showthread.php?t=2785128

Lethargy said:
http://forum.xda-developers.com/showthread.php?t=2785128
Click to expand...
Click to collapse
Edit:thanks!

wakelocks are how your phone works, they are supposed to be. an occasional incident might happen, and a process will get "stuck", which could keep a wakelock active. tell me, your wakelock, is it draining battery faster than usual? a reboot will usually fix these kinds of incidences. but you say you flashed roms since, and still the same.. so my next question is which apps are you using that is using this wakelock?

simms22 said:
wakelocks are how your phone works, they are supposed to be. an occasional incident might happen, and a process will get "stuck", which could keep a wakelock active. tell me, your wakelock, is it draining battery faster than usual? a reboot will usually fix these kinds of incidences. but you say you flashed roms since, and still the same.. so my next question is which apps are you using that is using this wakelock?
Click to expand...
Click to collapse
Afaik I don't use any apps that trigger these wakelocks I've experienced. The only solution I've found so far is to disable services called "Configfetchservice" and "userpresenceservice". I've got these wakelocks no matter what ROM or even if I had disabled all Google stuff (sync, location, device manager and so on). Always after a day I have about an hour of Google play services wakelocks by userpresenceservice and configfetchservice. Never had this before. I'm sure it has something to do with latest google play services versions. I know wakelocks are very important part in smartphones but these kind of wakelocks are everything else but wanted.

rockknee said:
Afaik I don't use any apps that trigger these wakelocks I've experienced. The only solution I've found so far is to disable services called "Configfetchservice" and "userpresenceservice". I've got these wakelocks no matter what ROM or even if I had disabled all Google stuff (sync, location, device manager and so on). Always after a day I have about an hour of Google play services wakelocks by userpresenceservice and configfetchservice. Never had this before. I'm sure it has something to do with latest google play services versions. I know wakelocks are very important part in smartphones but these kind of wakelocks are everything else but wanted.
Click to expand...
Click to collapse
so you are saying that these wakelocks exist for you.. one very important question to an answer you havent mentioned at all, are these wakelocks causing battery drain?

simms22 said:
so you are saying that these wakelocks exist for you.. one very important question to an answer you havent mentioned at all, are these wakelocks causing battery drain?
Click to expand...
Click to collapse
Not really shocking drain but noticable it is, which is nothing exceptional. It does these wakes during deepsleep every now and then. And of course when device is not used much and there is google play services on top 3 consuming elements at settings-> battery that's not the way it should be. Now I'm going to enable those services again and look for the logcat if I could find out to which app it is related to.

rockknee said:
Not really shocking drain but noticable it is, which is nothing exceptional. It does these wakes during deepsleep every now and then. And of course when device is not used much and there is google play services on top 3 consuming elements at settings-> battery that's not the way it should be. Now I'm going to enable those services again and look for the logcat if I could find out to which app it is related to.
Click to expand...
Click to collapse
if its draining some battery, but nothing in large amounts, i wouldnt really worry about it. as sometimes these wakelocks appear, then disappear a week or two later.

simms22 said:
if its draining some battery, but nothing in large amounts, i wouldnt really worry about it. as sometimes these wakelocks appear, then disappear a week or two later.
Click to expand...
Click to collapse
I guess you're right. I'll just keep those services enabled for a week or so and see wheter it goes away or gets nasty and drains my battery in couple hours.

rockknee said:
I guess you're right. I'll just keep those services enabled for a week or so and see wheter it goes away or gets nasty and drains my battery in couple hours.
Click to expand...
Click to collapse
a while back, these kinds of things drove me crazy. then one day i just decided not to think about them anymore, and have been better off since. sure, every once in a while(rare, usually location oriented) a wakelock will appear that will drain lots of battery, but ill just use the disable services app to kill that wakelock for a week or two, then ill switch it back and all will be normal.

Anyone else having lots of wakelocks after flashing new kernels?

Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks

KodRoute said:
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
Click to expand...
Click to collapse
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.

Lethargy said:
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Click to expand...
Click to collapse
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?

KodRoute said:
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
Click to expand...
Click to collapse
The CPU throttles at 65C by default (some kernels change this or give you an option to change it), and shuts down at 105C. 47C is hardly anything.

[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.

Having bad battery life on Nougat? Check this.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​What I have right now out of Doze are "Bluetooth MIDI Service", "Bluetooth Share", the "Clock" app and two other Clock apps.
I am not sure how effective is the method listed below after the last update. Stay tuned.​​
Also I think the current version of Facebook Messenger is draining too much battery.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​Hello everyone,
when I bought my Zenfone 3 ZE520KL, I was amazed by it's battery life. I could easily get around 8 hours of SOT in a single charge with moderate usage. My device was running Android Marshmallow 6.0 out of the box, but performance wasn't as good. On Nougat, performance is much better and faster, also I used to get some lags and frozen screen, the capacitive keys also sometimes froze when I was charging my phone, but now I don't get issues like that as often as before. Interface is so much more appealing and I love it.
But what about battery life? I started getting around 5 hours of SOT.. which is still good, but not really close to 8 hours. I thought a lot about these 3 hours that were missing so I decided to start investigating. I wanted to share my findings with you so maybe you would know something that could help.
It's been two weeks since I have been testing out different things. The apps I used to do my research are:
Carat. What I love about this app is the process list. It shows exactly which apps and system processes are running in the background, so I can control them very easily.
Greenify. Thanks to the Carat app, I can see which apps continue running in the background, so I can use Greenify to hibernate them after I'm done using them. (Examples: Youtube, Snapchat etc.). Also I bought the Donation Package, and unlocked the other modes using adb commands (my device is not rooted).
BetterBatteryStats. This app is usually used to detect wakelocks. I limited the Google Calendar App from syncing so it doesn't use too much battery in the background. This app is paid in Google Play but you can get it for free from here.
What I did to get better battery life:
I excluded the services, that were always running in the process list from the Carat App from Doze. Apparently, the new Doze in Nougat gives us permission to optimize more system processes and services than before, which can backfire - Doze starts trying to kill processes that can't be killed, and this results in consuming more battery juice than saving it.
How to enter Doze settings and make the following changes:
Go to "Settings" > Select "Battery" > Tap on the three dots at the upper-right corner > Select "Battery Optimization" > Select "All Apps" > Find and tap on the Apps/Services/Processes I have listed below > Select "Do not optimize". The other apps and services should stay optimized.
The apps, processes and services that I removed from Doze are:
Android Services Library
Android System
ASUS Calling Screen
Bluetooth MIDI Service
Bluetooth Share
Camera
Clock
com.android.smspush
com.asus.keyboard
com.asus.shim
com.qti.qualcomm.datastatusnotification
com.qualcomm.qti.tetherservice
org.codeaurora.bluetooth
org.codeaurora.ims
com.qualcomm.qcrilsgtunnel
ICESound Service
Mobile Manager
MobileManagerService
System UI
Telecom Service
Telephony Service
ZenUI Keyboard
ZenUI Launcher
Some other apps that I'm using: Do It Later, Greenify, Messages, Nova Launcher, Timely, Weather.
Please do a full charge to 100% afterwards and check if the battery still drains as quickly as before. Your feedback will be greatly appreciated.
I am already starting to see improvement in my battery life. I was losing around 2% on Stand By and battery was draining fast when I was using the phone, but now I lost 0% on Stand By overnight and 10% for 1 hour of SOT (before this I was losing 10% for 30 min. of SOT). I am still trying to figure out which services exactly are causing the drain, when they are being optimized. Maybe the services, included in the Android System? (Check them from Settings > Battery > Android System > Included Packages). I deleted Facebook and Twitter apps and started using them from Chrome (almost the same thing, I quickly got used to that). Please check the updates below for more info and share your opinion or advice in the comments so we can all reach a better experience with this amazing smartphone.
Thank you for reading!
Update1: 6h30min SOT with 30% left (917mAh, 35%), but I will have to charge now. I have been messing with Doze a lot, maybe I'll get more clean results later. Progress has been made though, at least with my device.
Update2: Something interesting - my J-Score with the Carat app before and after starting this experiment: http://i.imgur.com/Q8u6HBD.jpg
Update3: There is a battery drain when making voice calls - 226mAh (7%) were lost because of 43 minutes long talk time.
Results were worse after testing with the second list removed, although there wasn't much draining with the screen on: SOT - 5h20min for 70% of battery (752mAh, 20%).
Update4: com.android.phone appears as a wakelock at BBS (Wakeups:8). Also 2h30 SOT for 30% used battery (100-70%~408 mAh). I'm updating the list and trying again.
Please note that my phone is updated to the latest firmware WW_Phone-14.2020.1703.28-20170410.
Update5: com.android.phone is still an active wakelock (Wakeups:14), but SOT is 2h34min for 30% used battery (100-70%~343mAh). At 30% battery left, SOT is almost 6hrs(28%~787mAh), Device Idle is at 10% (291mAh). The MobileManagerService is causing way too many wakelocks and is probably the reason for the high Device Idle battery usage.
Update6: MobileManagerService is no longer showing as a frequent wakelock. com.android.phone (Telephony Service - Wakeups:9) and com.google.android.apps.messaging are the most persistent wakelocks, other than that battery life is amazing at the moment. SOT is 2h45min for 30% used battery (100-70%~366mAh). I also had 27 min of talk time (4%~145mAh). At 30% left, I have 6h33min of SOT (32%~912mAh). Device Idle is again at 10% (292mAh). We are ready for the final test.
Update7: The results are quite interesting. After removing com.qti.qualcomm.telephonyservice from Doze, com.android.phone stopped appearing as a frequent wakelock at first, but now, at 70% it has 16 wakeups. SOT is 2h22min (100-70%~318mAh), so it's not better. I'm going to try a few more changes.
Update 8: I posted it as a reply here.
Update 9: I shouldn't have put Task Manager out of Doze, I get so much better battery life now. The update is ready, check it here.

Good post, thank you for investigating this, please let us know if you find more stuff or what exactly is responsible for it and an easy way of fixing.

1noob said:
Good post, thank you for investigating this, please let us know if you find more stuff or what exactly is responsible for it and an easy way of fixing.
Click to expand...
Click to collapse
Hello! Thank you for your reply. I'm so happy I could help others and myself with this thread, but I also need to know if you are also seeing any difference. Please check here regularly!
Also, I'm guessing that when you put your system processes and services in Doze, you also decrease their performance, which causes battery draining, as they try to run normally and do their work. Doze is trying to prevent them from doing that. This is my conclusion, but only results will show if I'm correct. If you own yourself a Zenfone 3, please feel free to report if you experience any changes using my method.
Thank you and have a nice day!

Hi, thank you for the post. I have a zenfone 3 here and will try your method.

I'm trying it on ze520kl with marschmallow, it seems working fine. :highfive:

Do you remove the first and second list from doze ? or ate testing with only the second list now?
Nice findings btw

pedromms86 said:
Do you remove the first and second list from doze ? or ate testing with only the second list now?
Nice findings btw
Click to expand...
Click to collapse
I have removed everything from both of the lists. It's still early to say but no major battery drain is noticed for now. Thanks!

bibbomio said:
I'm trying it on ze520kl with marschmallow, it seems working fine. :highfive:
Click to expand...
Click to collapse
Awesome! :good:

Thank you so much for this article. Well written as well. I have applied the changes and so far no issues (it has been 6 h is). Will report once I have more history

I remove the apps from doze, and can say it really improve battery (test for one day)
thanks !

@Blackrose110 any news improvements after update3 ?

New update is released via OTA (~500MB).

pedromms86 said:
@Blackrose110 any news improvements after update3 ?
Click to expand...
Click to collapse
Too early to say, also I got a weird wakelock, and lost 2% overnight. I lost the results (100-90%) after a restart. Now I'm going to update my phone and start again.
I had 8% used up on 43 minutes of SOT, and 2% lost on voice calls (100 and something mAh). I went to bed with 92%, I guess the other 2% were lost on that wakelock and the clock wakelock. These 2% were lost on equal intervals.
It's going to take a while, I'm just using my device normally. I don't have time to be on my phone all the time, also the battery is harder to drain now. At this point, I'm just trying to get better results.
Cheers!

pedromms86 said:
@Blackrose110 any news improvements after update3 ?
Click to expand...
Click to collapse
Check again tomorrow!

RobinRo said:
New update is released via OTA (~500MB).
Click to expand...
Click to collapse
Updating...

I don't think it is a good ideea to change Doze settings for system services like com.qualcomm.* or telephony*.
In theory, these services should be compatible with operating system and they should work as designed. I would focus on third-party apps who doesn't work well on Nougat.
Anyway, is just an opinion and i'm looking forward for updates

ci6i said:
I don't think it is a good ideea to change Doze settings for system services like com.qualcomm.* or telephony*.
In theory, these services should be compatible with operating system and they should work as designed. I would focus on third-party apps who doesn't work well on Nougat.
Anyway, is just an opinion and i'm looking forward for updates
Click to expand...
Click to collapse
Hello ci6i, I also agree with you, and that's why I excluded all of them from Doze when I first tried this out. At the moment, I removed only those system services, that run in the background all the time. My goal is to find the least amount of system services and processes, that are causing battery drain when the phone is in use.
I am not saying that you should do exactly what I did. It's best if you try out yourself on your own device what works and what doesn't.
I also have only excluded from Doze apps that I use daily. But everyone is using different apps and it depends only on the developers to update them.
You can download Carat for free from Google Play and check the process list, it's very useful. The app itself doesn't use any battery.
Good luck!

Blackrose110 said:
...
I am not saying that you should do exactly what I did. It's best if you try out yourself on your own device what works and what doesn't.
I also have only excluded from Doze apps that I use daily. But everyone is using different apps and it depends only on the developers to update them.
...
Click to expand...
Click to collapse
I agree with you and i really appreciate your work Yesterday I've installed Carat after i read your first post and today i did new OTA update and cleared cache partition. Let's see how it works in the next few days.

What should I do next, guys? Remove other com.qualcomm/com.android/com.asus services or remove just MobileManagerService from Doze? I'm thinking about the second one, I'm curious to see if ti makes any difference. I think the results from the first test were the best, and the MobileManagerService was out of Doze as far as I remember. Might as well try and see what happens.
It's a bit hard to drain the battery these days, so updates might not be fast. Patience is key!

Yeahh final test!! Looking forward to the result