Develop Bugs

[Q] High battery drain because of Android-System

Hello,
I have a high battery drain because of "Android System". I lose about 3-5% per hour of my battery in idle state. I turn screen off and didn't use it.
I'm using Slim ICS ROM with franco kernel #174.
Badass Battery shows me that following included processes are in Android-System:
Code:
com.android.systemui
system
android:ui
com.tmobile.themechooser
surfaceflinger
com.android.settings
servicemanager
So anybody know what's the problem here?
I'm already disabled Google Photo Sync, NFC and GPS because I didn't need that. Also googling for the problem doesn't help.
Hope you can help, thanks!

You hit the "Yes this is a question" box
Guess where this thread belongs?
Thread Moved
Friendly neighborhood Moderator

you must install your rom again
this is based on your luck

luckydude said:
you must install your rom again
this is based on your luck
Click to expand...
Click to collapse
Again, I've mentioned this twice today: Bullsh**, I don't mean to be disshonouring, or anything, but please, give proper answers,. It's all good, that you want to help, but only with proper and correct answers.
Right, back to topic;
Go into your dev. settings, and uncheck everything that doesn't need to be checked (Stay Awake, Strict mode, etc.) Undervolt the CPU, that should save a ton of battery charge, and underclock to 900-920 MHz, that is definitly enough, on a dual-core

Thanks for your answer =)
I think my phone is already undervolted through Smartreflex in francos app and I also tried underclocking by setting max cpu to 1036 Mhz (instead of 1200 Mhz).
The problem disappeared after 1-2 charges (don't ask me why..).
And now after flashing Slim ICS 3.9, battery time seems to be ok (for me at least).
Per hour in idle state the phone consumes ca. 2-3%.
I ask myself how do others get 1% drain over night. Is that even possible? Tried very much kernels (franco, trinity, glados and leankernel) and didn't even get near that.
Any tips?

OP Im glad you mentioned the issues went away after a few charges. this has been an issue for some who do not believe that a few charge cycles does anything. well im with you as i always see things sort of "settle down" after a few days of flashing a new rom.

I have the same problem on my Nexus S.
The process consuming battery is surfaceflinger. I can see it on battery screen before the name change to Android System.

Pik3no said:
I have the same problem on my Nexus S.
The process consuming battery is surfaceflinger. I can see it on battery screen before the name change to Android System.
Click to expand...
Click to collapse
I doubt you will find much help here for the Nexus S.

adrynalyne said:
I doubt you will find much help here for the Nexus S.
Click to expand...
Click to collapse
I guess this is an Android problem. Not related to any device.

Android
Yes, i think your prob comes to every Android phone after flashing New rom.
Just wipe Battery stets after flashing. It needs few complete chargings to calibrate the battery.
There are also many apps in the market for this

konsolen said:
Yes, i think your prob comes to every Android phone after flashing New rom.
Just wipe Battery stets after flashing. It needs few complete chargings to calibrate the battery.
There are also many apps in the market for this
Click to expand...
Click to collapse
You need to read this. Also you, OP.

General Crespin said:
You need to read this. Also you, OP.
Click to expand...
Click to collapse
This. People, just give it 2,3 days for the rom to settle after flash. Same for a kernel.

konsolen said:
Yes, i think your prob comes to every Android phone after flashing New rom.
Just wipe Battery stets after flashing. It needs few complete chargings to calibrate the battery.
There are also many apps in the market for this
Click to expand...
Click to collapse
I don't know if was the new kernel I flashed or was the battery stats wipe I did, but seems now my phone have no more RILD/RILJ wakeclocks.

GNexor said:
I ask myself how do others get 1% drain over night. Is that even possible? Tried very much kernels (franco, trinity, glados and leankernel) and didn't even get near that.
Any tips?
Click to expand...
Click to collapse
Yes, it is possible. I get 1 or 2% drain overnight with wifi and mobile data disabled, and up to 5 to 6% if mobile data is enabled overnight.
My record with it is 1 day and 20 hours from 100% to 3%.
I had a LG Optimus Black before and didn't last a day. I'm loving this Galaxy Nexus.
Nuno

One Power Guard can help the system into a deep sleep,Reduce battery drain
downloaded from http://forum.xda-developers.com/showthread.php?t=1889740

Nuno_PT said:
Yes, it is possible. I get 1 or 2% drain overnight with wifi and mobile data disabled, and up to 5 to 6% if mobile data is enabled overnight.
My record with it is 1 day and 20 hours from 100% to 3%.
I had a LG Optimus Black before and didn't last a day. I'm loving this Galaxy Nexus.
Nuno
Click to expand...
Click to collapse
I would like to achieve battery drain like that, seems like what it should be.
I am running AOKP Build 2 and I feel like my battery life is ok but not great. I let my phone sit overnight last night with sync off, but LTE on and it drained roughly 4% an hour. I actually turned off LTE in the middle of the night to see if there would be a difference, and no, it drained at the same speed on 3G as well. I live in an area with pretty good reception actually, GSam says I spend the vast majority of my time with a signal strength of 4/5.
GSam reported that roughly 34% of my battery drain overnight was due to Phone Radio. Another 52% was due to app usage. Drilling into that it tells me that over 40% of the battery drain from apps came from "Android System", "Phone" and "Kernel". Under Android System, which was by far the greatest drain of the apps, it only kept the phone awake 1m18s overnight so that doesn't seem excessive. However, I'm confused as to why, with a good signal/connection my battery would drain at nearly 4% an hour whether connected to LTE or CDMA. Unless the radios in this device are poor, I have a hard time believing there isn't a way to fix this without using something like Juice Defender.
I can't recall because it's been so long, but I don't really remember any ICS ROMs draining this fast. I'm on a clean install of AOKP B2 and I've tried a few different kernels with the same results. Any ideas anyone?

So I wanted to let you all know that after trying a few different ROM/Kernel combinations all with similar idle battery drain, I installed the latest (9/21) CM10 nightly and I only lost about 10-12% overnight last night connected to LTE. That is a much better drain than the 30% or so I was seeing previously. Not sure why but my phone just hasn't been handling the latest AOKP builds very well. I am afraid to try a different kernel right now as I'm leaving town tomorrow for most of the week so I'll leave it as is until I get home next weekend, and see if I get this good of battery life with the latest Leankernel.

Surfaceflinger
The same happens to me, this app appear in BetterBattery stats, Surfaceflinger appear as the culprit of my 45%+ battery consumption caused by Android Sys
When I first rooted my phone (xperia S) I noticed an 31%+ energy consumption by Android Sys, I reflashed and re-rooted and stoped for 2 weeks or so, now 2 days ago I woke up to find that 81% of the battery is being drained by Android Sys, then it lowered to 31-43%. I noticed that when I refreshed the stock "Battery" app ,"Surfaceflinger appear for a moment, I seem that I confirmed with the BetterBatteryStats, Surfacaflinger appears at the top.
Why is this happening? Can something be done about it?
PS: I cannot change kernel, bootloader is locked...

Surfaceflinger and android.process.acore are top battery drainer. I mean how to make them not sucking on battery?

Cell Standby Battery Life

Hi,
I'm sure this type of question has been posted here before - I've seen a lot of the posts. However, I'm having lots of trouble finding a good answer for my problem.
I'm using a Verizon Galaxy Nexus with a custom JB ROM and the latest radios. My problem seems to be that Cell Standby takes up a ton of my battery. This problem existed in ICS (stock and custom roms/kernels) and with JB (several custom roms/kernels). I've noticed if my WiFi is left on, the problem is immensely better. It's 3:20PM and I'm sitting at 87%. I'm on about 6 hours standby and that's all on WiFi, no use. If I'm on WiFi, that'll be about 60%.
It varies of course depending on what I'm doing. I've noticed that phone calls use a ton of juice and the screen obviously uses a bunch, too.
Also, it doesn't make too much of a difference if I'm running on 3G or 4G. I prefer 4G as it seems a lot more consistent in staying connected, but I've opted for 3G to keep my battery at a decent level.
OH! And the only thing I have running on my phone right now is an Exchange account, Gmail and Google Voice. Google Now is turned off.
Has anybody experienced this sort of thing? I just can't understand how the iPhone can sit idle for days and my phone can't make it past 24 hours unless it's on WiFi.
Thanks,
Jack

[Q] Questions about battery life and comparisons

I have a Nexus 7 32gb LTE, and I have a few questions about it's battery life compared to the other N7 devices.
I used to have a 16GB WiFi, and the battery life is MUCH better than the LTE's, is it because of the radio and/or storage size? If so, is there a way to make it so it'll have the same life? As stupid as that sounds. Could disabling the radio help? As when I tried with the 4636v2 app, there wasn't much change. I run the newest CM (deb) nightly every day, and I'm about to flash 12-30-13.
Thanks in advance,
Tony Sesek

You should have similar battery life if you are running WiFi when you are in your house. 4G LTE consumes more battery than WiFi. So picture myself running a 4G LTE variant Nexus 7 2013 and keeping my data plan on constantly, obviously I will consume more battery than my WiFi tablet.
You could try to find a kernel that supports your ROM but I personally don't think there is much you can do at this point.

codemonkey98 said:
You should have similar battery life if you are running WiFi when you are in your house. 4G LTE consumes more battery than WiFi. So picture myself running a 4G LTE variant Nexus 7 2013 and keeping my data plan on constantly, obviously I will consume more battery than my WiFi tablet.
You could try to find a kernel that supports your ROM but I personally don't think there is much you can do at this point.
Click to expand...
Click to collapse
I would use ElementalX, but CM just flops over onto its back begging to be killed when you try it now.
If you could recommend me a good, energy-saving, kernal like ElementalX for CM11, I'd highly appreciate it.
Also a way to conserve more energy, as I don't even HAVE a data plan, I just keep the SIM in so I don't lose it. If I take it out, could that help? Maybe a combo of disabling the radio and taking out the chip.

Tony556 said:
I would use ElementalX, but CM just flops over onto its back begging to be killed when you try it now.
If you could recommend me a good, energy-saving, kernal like ElementalX for CM11, I'd highly appreciate it.
Also a way to conserve more energy, as I don't even HAVE a data plan, I just keep the SIM in so I don't lose it. If I take it out, could that help? Maybe a combo of disabling the radio and taking out the chip.
Click to expand...
Click to collapse
I wouldn't know any kernels for your device. I have a Nexus 7 2013 but I do not actually have it rooted. I know, what a shame, but I do like to have a stock tablet around. Especially one that is running vanilla Android.
The SIM shouldn't have any issues. It isn't doing anything, as it isn't activated. You could try disabling the LTE radio by using airplane mode and seeing if that helps. With the LTE radio off, there shouldn't be a difference in power consumption between a WiFi Nexus 7 2013 and a LTE one. You also could try disabling bluetooth and all sorts of miscellaneous options you do not use.

codemonkey98 said:
I wouldn't know any kernels for your device. I have a Nexus 7 2013 but I do not actually have it rooted. I know, what a shame, but I do like to have a stock tablet around. Especially one that is running vanilla Android.
The SIM shouldn't have any issues. It isn't doing anything, as it isn't activated. You could try disabling the LTE radio by using airplane mode and seeing if that helps. With the LTE radio off, there shouldn't be a difference in power consumption between a WiFi Nexus 7 2013 and a LTE one. You also could try disabling bluetooth and all sorts of miscellaneous options you do not use.
Click to expand...
Click to collapse
I have the same stuff activated as I did on my WiFi, WiFi, NFC, Location, and that's about it. The 4626 or whatever it was app seems to help, slightly. But now, another problem arises. It's charging unusually fast, my tablet. IDK if USB Fastcharge is somehow enabled or what, but it's suffering from what my phone has. As my Verizon Galaxy Nexus charges and drains quickly. Haven't disconnected the tablet from power yet to see if it really is draining even quicker. Updates soon.

Tony556 said:
I have the same stuff activated as I did on my WiFi, WiFi, NFC, Location, and that's about it. The 4626 or whatever it was app seems to help, slightly. But now, another problem arises. It's charging unusually fast, my tablet. IDK if USB Fastcharge is somehow enabled or what, but it's suffering from what my phone has. As my Verizon Galaxy Nexus charges and drains quickly. Haven't disconnected the tablet from power yet to see if it really is draining even quicker. Updates soon.
Click to expand...
Click to collapse
I have heard of the Nexus 7 draining faster than charging, but I have not heard about it charging as fast as it is draining. Have you tried doing this by any chance?

Tony556 said:
I have the same stuff activated as I did on my WiFi, WiFi, NFC, Location, and that's about it. The 4626 or whatever it was app seems to help, slightly. But now, another problem arises. It's charging unusually fast, my tablet. IDK if USB Fastcharge is somehow enabled or what, but it's suffering from what my phone has. As my Verizon Galaxy Nexus charges and drains quickly. Haven't disconnected the tablet from power yet to see if it really is draining even quicker. Updates soon.
Click to expand...
Click to collapse
I'm not sure how much rooting & installing a custom rom on my N7 has affected battery life, as I did that immediately after getting the device (therefore no frame of reference).
Using Sinless 3.2.0 rom together with ElementalX kernel (CPU 1728, GPU 477, UV 850, DT2W) and my N7 has been pretty much completely in standby for 17 hours (at work and therefore no time to play ) with only 10% battery used (90% left). This is with Wifi, Sync, GPS always on.
Normal usage will use up approx 2% per hour of battery. Still pretty awesome in my book!
This custom rom :
http://forum.xda-developers.com/showpost.php?p=46897944&postcount=1

daffie said:
I'm not sure how much rooting & installing a custom rom on my N7 has affected battery life, as I did that immediately after getting the device (therefore no frame of reference).
Using Sinless 3.2.0 rom together with ElementalX kernel (CPU 1728, GPU 477, UV 850, DT2W) and my N7 has been pretty much completely in standby for 17 hours (at work and therefore no time to play ) with only 10% battery used (90% left). This is with Wifi, Sync, GPS always on.
Normal usage will use up approx 2% per hour of battery. Still pretty awesome in my book!
This custom rom :
http://forum.xda-developers.com/showpost.php?p=46897944&postcount=1
Click to expand...
Click to collapse
I would use that, but it's not for LTE (deb).
-----------------
For the last 2 days, I rarely used my tablet. But I binged it for up to an hour multiple times,Y and the battery drained wayyyy too fast. Screenshot of battery life soon

As I don't even USE the radio, should I just get some of my money back and buy a 32GB WiFi? Is it thinner than the LTE? Can I flash flo roms onto a deb? Disable the radio entirely? And don't say use airplane mode, I hate that stupid icon, and I think that disables GPS.
EDIT: Can I just: "fastboot erase radio"? Or format. Sounds SOMEWHAT logical.

Cell Standby/Phone Radio after Android M Upgrade

I have read numerous posts about the Android L cell standby bug on the One M8 and used that to make as many changes as possible before posting here. I haven't seen many posts where the HTC One M9 was affected by the MM update in this way.
I have had my Verizon One M9 since March 2015 (preorderd it), and it worked great on Lollipop. My cell standby was consistently under 5%. Then, I upgraded to 6.0 around March 2016 and have been noticing consistent battery drain from what I think is the Phone Radio (Gsam) or Cell Standby (stock battery app). It is >40% with the screen on and >30% with the screen off. Airplane mode appears to help with the cell standby percentage (down to 5% after 12 hours, battery down by ~15%). I am also having more issues with the phone heating up; 114 Fahrenheit was the highest I noticed before it stopped functioning from the heat.
What I've tried:
-Verizon's Repair Assistant/Software Upgrade Tool
-Factory Reset
-Wipe Cache Partition
-Clear Network Settings
-Turn off Advanced Calling (seemed to help the most)
-Switch from Global to LTE/CDMA
-Keeping WiFi off unless I'm downloading something (helps the WiFi battery drain issue)
-Location off
What I have NOT tried:
-Booting into safe mode (my apps don't seem to be misbehaving per Gsam or the stock monitor)
-Unlocking the bootloader and flashing a custom ROM. (I'm S-On with a Locked Bootloader.)
In all fairness, I get good battery life (2 days) if I don't use my phone (<1 hour SOT in a day). If I use my phone, it dies in like 6 hours. I lose over 10% per hour of active use (Chrome, texting, Gmail). I don't have Facebook, Twitter, or G+, but I use Hangouts.
Reason I'm concerned: People I live with, same contract have a 1% cell standby (Samsung Galaxy S5 on 6.0.1). Why is my phone's cell standby so high even though this issue was supposedly fixed for MM?
Thoughts?

Hi, I agree, its pretty bad. You are getting better battery life than I am...
I've been on a stock rooted/S-Off for only three weeks or so, but am considering going back to my M8 because the battery life is so poor. (and I actually would use FM radio , which I can not on the M9 Verizon)
I run no social networking apps, have uninstalled everything I don't actually use.
GSAM tells me Google Play services is a culprit, so just today I've removed my Google acct, location turned off unless I need it, and will test over the next day or so .
I'm waiting for a custom rom probably HTC 10 port to get rave reviews and will likely give that a go .

mikeataol said:
Hi, I agree, its pretty bad. You are getting better battery life than I am...
I've been on a stock rooted/S-Off for only three weeks or so, but am considering going back to my M8 because the battery life is so poor. (and I actually would use FM radio , which I can not on the M9 Verizon)
I run no social networking apps, have uninstalled everything I don't actually use.
GSAM tells me Google Play services is a culprit, so just today I've removed my Google acct, location turned off unless I need it, and will test over the next day or so .
I'm waiting for a custom rom probably HTC 10 port to get rave reviews and will likely give that a go .
Click to expand...
Click to collapse
I'm not rooted yet. I noticed high Google Play Services usage (don't remember the exact percentage and didn't screenshot it) a few days of upgrading to Android M. It seemed to help to backup my data, factory reset the phone, run Verizon's Repair Assistant/Software Upgrade tool, and turn off Advanced Calling. Now Google Play Services is calculated at using 10% of my battery since last full charge (4.9% per GSam App Sucker). The cell standby issue was probably there all along, but I just didn't notice it until I tamed the Google Play Services drain. Maybe doing what I did will help you. I can't post outside links yet, but if you Google "Verizon's Repair Assistant - Software Upgrade (HTC)," it will be the first result that comes up.

Edit
I suspect my phone's issue is a reporting bug, as some other posts have suggested. I feel bad complaining since I get great battery life if I don't use my phone. Comparing phone radio usage with airplane mode on for 12 hours to not using my phone for 12 hours (airplane mode off), the only difference was in reporting. It was 5% with airplane mode on and like 35% with it off. Same amount of battery was used. Perhaps the screen is really what's draining my battery. All I know is that I used to get double the screen-on-hours while running way more apps when I had Lollipop.

Winnie-the-Pooh said:
I have read numerous posts about the Android L cell standby bug on the One M8 and used that to make as many changes as possible before posting here. I haven't seen many posts where the HTC One M9 was affected by the MM update in this way.
I have had my Verizon One M9 since March 2015 (preorderd it), and it worked great on Lollipop. My cell standby was consistently under 5%. Then, I upgraded to 6.0 around March 2016 and have been noticing consistent battery drain from what I think is the Phone Radio (Gsam) or Cell Standby (stock battery app). It is >40% with the screen on and >30% with the screen off. Airplane mode appears to help with the cell standby percentage (down to 5% after 12 hours, battery down by ~15%). I am also having more issues with the phone heating up; 114 Fahrenheit was the highest I noticed before it stopped functioning from the heat.
What I've tried:
-Verizon's Repair Assistant/Software Upgrade Tool
-Factory Reset
-Wipe Cache Partition
-Clear Network Settings
-Turn off Advanced Calling (seemed to help the most)
-Switch from Global to LTE/CDMA
-Keeping WiFi off unless I'm downloading something (helps the WiFi battery drain issue)
-Location off
What I have NOT tried:
-Booting into safe mode (my apps don't seem to be misbehaving per Gsam or the stock monitor)
-Unlocking the bootloader and flashing a custom ROM. (I'm S-On with a Locked Bootloader.)
In all fairness, I get good battery life (2 days) if I don't use my phone (<1 hour SOT in a day). If I use my phone, it dies in like 6 hours. I lose over 10% per hour of active use (Chrome, texting, Gmail). I don't have Facebook, Twitter, or G+, but I use Hangouts.
Reason I'm concerned: People I live with, same contract have a 1% cell standby (Samsung Galaxy S5 on 6.0.1). Why is my phone's cell standby so high even though this issue was supposedly fixed for MM?
Thoughts?
Click to expand...
Click to collapse
I'm quite sure I have this same problem. I've only had my M9 a week, and am seeing some strange and inconsistent battery drain. The majority of time if I'm doing a simple task like texting or checking e-mail, the phone gets warm (warmer than anything I've used). Battery seems to deplete quickly too, mainly with some from of google services being the culprit. However, I've also noticed high mobile radio usage. I can see that the mobile radio is active pretty much the same amount of time phone radio is, even when on wifi....I've never experienced this before. It is as if the mobile radio is constantly locked on (which I noticed there is a check box for this in dev options). I know the Moto X 2013 had this same issue when updating to L, and was never patched. I came from a Droid Maxx, so maybe I was spoiled with battery, but I can almost sit and watch my battery drain on this M9 (and thaw my hands if necessary). I also have rooted every android I have owned, and decided I don't want to root the M9 and take a break from all that. Immediately a bit annoyed with the heat and abysmal battery life. That said, build quality is great, and the user experience is quite good and fluid (aside from ridiculously pointless pinned notifications like when boomsound is active or when you connect to wifi and it reminds you you're connected....both mind bogglingly stupid and take up way too much of the notification panel).
If I have to disable a bunch of features to get it to not heat up and/or use less mobile radio, most likely will sell it. Unless rooting and romming helps? Though initially I'm not seeing much development on this M9. I want to like this phone so badly but these problems that shouldn't be problems make it a bit hard to do so.

Battery problems?

I know, our device has really great battery life and I don't have anything to complain about that, but a friend of mine just got himself a new phone and his values make me a bit jealous and most of all: surprised and stunned.
He got himself a Xiaomi Redmi Note 4 (SD 625 variant, MKT variant really sucks), it has the same processor, same display and not even 700 mAh more (4100 mAh) and he got with some "dev rom" (made by Xiaomi, seems to just be the beta of that ugly MIUI 9, based on Andorid 7.0) 6h of SOT, doze seems to haven't really kicked in in that time. in their forum in the SOT thread I see people getting normally about 8-10 with up to over 12 h of SOT, most of them on stock ROM without any additions. And I'm quite irritated about that huge of a difference with not that much more battery. And he seems quite convinced that it's not on the cost of performance, you should notice that quickly on such a heavily skinned ROM.
Now my question is: how in hell is that even possible? I mean our devices seem quite comparablewith just a slight bump in battery but near-stock AOSP Android against pretty much an iOS clone. Does anyone have any idea what could cause that big of a difference? And if it's software based could that be done on our device? Because my experience and from different posts our device lasts about 5-6 h normally.
I mean I'm already lucky about my 2 days of usage with up to about 2.5 days on some weekends where I have a lot of stuff to do. But I wouldn't mind a bit of extra. But my biggest problem with that is as simple as: how? I could really use some explaination right now...

I don't have issues with device.. stock 7.1.1 with dec.patch, unlocked bootloader, with latest magisk. Also installed greenify.

Then you are one of very rare cases. My experience is about half of that.
And I also meant on stock ROM, without any modifications. So I don't know which apps you greenified, but that was not the point. I use Greenify too but more for apps that aren't supposed to run constantly in background when I only use it very seldomly.

The norm for this phone is 8+ hours SOT. Sometimes I get 10 and a few have had up to 12. Unless you're gaming 8 should be easy. 5 hours means something is wrong with your phone hardware, you have a rogue battery eating app or you're gaming. I rarely charge my phone over the weekend even when I use it a lot.

Well, neither of that is the case and I rarely see people claiming more than 6h of SOT

So the answer to your question is, it's the wrong question. The question should be, why does my battery not last very long and what apps or usage causes me to have such poor battery life? Compared to the Redmi Note 4 the Z Play is exactly where it should be.
Here's a link to the SOT thread: https://forum.xda-developers.com/moto-z-play/review/screen-time-t3643959
gsmarena battery life test 100h endurance rating: https://www.gsmarena.com/battery-test.php3?idPhone=8310#show
Here's an app to help diagnose battery condition (Accubattery): https://play.google.com/store/apps/details?id=com.digibites.accubattery&hl=en
also betterbatterystats is really helpful.
I sincerely hope you get it sorted out!

Well, gsam isn't detecting any app that's off even with root so I don't think there is any. I installed that AccuBattery app, let's see what it has to say

Removed because of ****ty q&a system...

Oh, and another thing I noticed: I get very randomly reboots, and every time the battery percentage drops massively. Just had a 30% drop. And after the reboot the battery percentage seems like frozen. Now I rebooted and plugged in the cable and got 44% again... No fast charging. Do that detection seems very off
Motorola forum isn't helpful at all. Clearing cache and dalvik didn't change anything and running around for a week in secure mode (that's how random they mostly are) or even doing a factory reset without restoring apps is out of question for obvious reasons.

That's pretty weird. Did you try a factory reset and after restore your apps? There's not a lot you can do if you're not rooted, but you shouldn't need to do much anyway on stock rom.
Only other option is full RSD lite OS restore as a last resort.

I am rooted for long, that's why I use Greenify. I know it also works without but then it's a joke. As RSD lite is, it just refuses for everyone to detect anything on Windows 10.
Factory reset is out of question for the moment, it takes way too long to do it properly (with titanium and NANDroid backup first) and I won't have that much time probably for the whole of this month. Otherwise I would most likely already have went off to the next best custom ROM since Motorola just can't get their **** together and still work on 8.0 in test for 2.5 month with searching testers for another one.
I think the next thing I'll do is to try the good old battery calibration, just have to find the file storing the statistics. I know many say that won't work but that's rubbish, it worked for me already a few times

Update: no, no change. Don't know if that funky battery percentage bug on random reboots still happen since I haven't had any again yet, but they come too random and unpredictable.
And that AccuBattery just proves to be worthless. It tries to estimate the rest capacity, but then it even fails to detect original capacity by 500 mAh. The battery sucker stats are also unrealistic. It puts chrome first with 10%, while GSam with root puts it 5th at 4.6% after kernel, Spotify, Android system and fight services. Android itself even puts it 9th with screen, phone idle, cell standby, Android OS and Bluetooth in-between.
So let's see what happens first. Motorola releasing 8.0, which I will flash through the .xml.zip, this time using flashfile.xml which should force a factory reset... Or me finding the time to switch to a custom ROM
Edit: so I got another one, bit this time no crazy battery drop. But the other times I killed of the soft reboot sequence because Magisk can have some problems with that. This time I didn't

Yesterday I was finally able to do the factory reset since those darn random reboots became too annoying and Moto's support is had just the most ridiculous ideas... In the worst way.
Either way, now OTA looks better, let's see how it will turn out in the next days