yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] M7mdA7md7sein:
Thank you soo much for such detailed answer and great effort.

I will try to do my best in the following days and generate another dump, before I go for the factory reset pathway :(
[BetterBatteryStats] Unreal-Forever:
Hi!

For almost a year I went to the support site for my phone and today they have even been able to answer my problem, a few months after having acquired this mobile I began to notice that "SO_Android" began to drain my battery , but I can't identify the cause.

It does not always happen but in most of the times the mobile continues to consume the battery almost as if it were using it, even just before going to sleep having fully charged the mobile and the next day when I get up I see that the battery charge has dropped from quickly (92-90%) without using it, without having mobile data or wi-fi activated, I have even done the test of setting 2G as the preferred network so that the signal coverage is very strong, but this continues going.

I made the log and the screenshots where you can check what happened during the almost 9 hours after being fully loaded and without having used it until after these hours.

I hope this has a solution.

Apparently I still can't attach image files or the log
[BetterBatteryStats] Oswald Boelcke:
Analysis without an idle dump is nearly impossible even if screenshots are attached. I suggest to upload your idle dump (taken in accordance with the guidance in OP; 6 hours minimum with less than 1 minute screen-on time, starting with battery at 95% or less) and to upload the dump to e.g. https://filebin.net/, https://hastebin.com/about.md or https://paste.imirhil.fr/.

Please provide the link here, omitting the leading https://
[BetterBatteryStats] pjadec:
Need dump file

But

EINT wakelock

Et360 wakelock

are culprits but I don't why
[BetterBatteryStats] Unreal-Forever:
Thanks for the suggestion, I see that so if I can put the link :)

drive.google.com/drive/folders/1r-oKyxFWqUIcStbBgfRZsGeegYoRQorU?usp=sharing
[BetterBatteryStats] pjadec:
Your phone kernel have some problems. Phone still go no deep sleep.

Still same culprits and I don't know how to fix it.

You can try change kernel or something or flashing rom
[BetterBatteryStats] TNSMANI:
It is a kernel issue. et360 wakelock seems to be connected to finger print. I don't know about EINT wakelock. If your phone has another kernel, try that. If not, try a custom ROM.

The dump is not complete. Things are missing. Uninstall BBS, reboot and reinstall. Let us see.
[BetterBatteryStats] matushsvk:
nvm
[BetterBatteryStats] Unreal-Forever:
The phone goes into deep sleep when it wants, it doesn't always, but it's not like it always fails when trying to get into deep sleep.

For example, this is what happened after I went to sleep, that last horizontal line at the end is that it managed to go into deep sleep, but this does not always happen:

I have never done to change the kernel, nor to give it root permissions, I have not wanted to lose the support or guarantee of this.

I also took screenshots and logs in case you can see a difference.

Something that may be useful to you, generally when I go to sleep I end up forcing the closure of most of the apps that are not vital to me while I sleep, I do this with the Hibernator app, I force the closing of both the apps that I have installed as several of the system to avoid that these can generate some consumption, sometimes I have thought that I could be closing an app of the system that could be controlling the doze system, but I have noticed that not, since I have done the test of starting the Phone in safe mode where it does not allow the app that I have installed to start, in this mode I have not done to close any app on the system either, but the same thing continues to happen, the battery ends up being drained by the system while I sleep.

En el mismo enlace que yo había dejado en el anterior comentario agregué una nueva carpeta (v2 2020-09-01) donde tengo las nuevas capturas y logs.

drive.google.com/drive/folders/1r-oKyxFWqUIcStbBgfRZsGeegYoRQorU?usp=sharing

---------- Post added at 03:39 PM ---------- Previous post was at 02:52 PM ----------

I have never done to change the kernel and this did not happen in its first months, this phone while working correctly the battery charge could last me up to a week (and I am not exaggerating)

Could something else be controlling finger print?

Updated:

I already did the steps that you asked me, I had to retype the 3 adb command lines after it installed.

in the same link I created a folder "v3 2020-09-02"

drive.google.com/drive/folders/1r-oKyxFWqUIcStbBgfRZsGeegYoRQorU?usp=sharing

Observations:

In the trial period they are an alarm for me to get up (at that moment I observed that there was no time at all while deep sleep) and a moment before doing the logs I had to make a call in which no one answered.
[BetterBatteryStats] M7mdA7md7sein:
Good morning,

If you can check this log for me, I will be thankful.

I have changed and disabled some options in the developer settings and enabled the battery saving.

I would like to understand if the same problems are still there or not! Or shall I head to factory reset!

Thank you so much ?
[BetterBatteryStats] TNSMANI:
Oh, my fingers ache scrolling through all those wakelock etc :(

Such a lot of activity! I have never seen so much activity in a phone which is supposedly asleep.

Anyhow, you have managed a drain of 0.7% per hour. But all the previous observations are still relevant and have not been addressed.

If you are going in for a factory reset, after resetting, take another idle dump before installing your apps. That will give an idea how the apps affect the phone.
[BetterBatteryStats] TNSMANI:
Now your drain is 0.7% per hour but the phone was awake for nearly 4 hrs and 45 mts.

Your mobile signal was poor to moderate, never good or very good.

ET360 and EINT are there for almost the full wake time.

There is no point in further analysing the dump. The earlier observations stand.
[BetterBatteryStats] beatschubser:
I recently bought a new phone (Huawei P30 Pro New Edition) and noticed that it stays awake most of the time when it should be idling. The battery drain isn't too high and the mobile signal is weak, but the battery life could be much better without the time awake.

Here's the log: https://0bin.net/paste/BDtrafKN#UJocP1VE6xcgfIiq2QS2jmVK2u24Aup52BzHgbAmvj3

I hope you can find the culprit.
[BetterBatteryStats] M7mdA7md7sein:
That's bad!

Thank you so much for your help ?

I may wait for a big Android update and then update, factory reset and then do what you have mentioned ?
[BetterBatteryStats] Unreal-Forever:
Thank you for your answer, although I do not think that is the problem, in the event that this time it gave me a bad signal it was because I had 4G as the preferred network, and that is why it never usually gives me a good signal at least while I'm on 4G, but Although I select 2G as the preferred network where the signal is always good, I still have the same problem

Another thing is that if I do the test with since I finish charging the phone 100% it tends to last much longer than it should, it is as if the full charge was actually 105% but it does not show the values ​​higher than 100%, that is why it is always shown that the line begins horizontally even though it has never been through deep sleep.

This time I did the test with just over 5 hours, being the preferred 2G network where I always had a great signal and even so it was only in deep sleep for less than 7 minutes, draining 8% of the battery.

Something is causing the CPU to be on high frequencies.

drive.google.com/drive/folders/1r-oKyxFWqUIcStbBgfRZsGeegYoRQorU?usp=sharing

folder "v4 2020-09-03"

This mobile when it goes into deep sleep, although the signal is very poor, the impact on the battery drain is barely noticeable, and the battery consumption line remains completely horizontal as I showed in the previous message.
[BetterBatteryStats] M7mdA7md7sein:
Would you kindly check these apps for me?

Cause I am suspecting it just might be one of them that is keeping the phone awake!

My eyes on Avast anti theft and Notisaver (Notification log saver to be retrieved afterwards), I have attached the screenshots of special access they do have as it might give you some impression. If they are not related to the issue, I won't waste my time with them.

Thank you.
[BetterBatteryStats] TNSMANI:
I simply made an observation about the quality of the signal. Your issue is not that.

Though the drain remains at 0.7% per hour, the deep sleep time is less than 7 minutes. Phone was awake for the balance time.

Kernel wakelocks as already mentioned continue and they are your issue. Look for a change of kernel or a custom ROM.
[BetterBatteryStats] beatschubser:
Anyone?
[BetterBatteryStats] TNSMANI:
You are wasting your time by doing the whole thing backwards. The proper and easier way to check for misbehaving apps is to clean flash the ROM, take an idle dump and keep it as a reference point. Then add a couple of apps, take another dump and compare the dumps. If the drain rate is not much different, those apps are ok. Then add another couple and compare dumps. And go on till you identify the app/s. Though time consuming, it is the surest way of identifying the app/s.

You are not going to identify the app/s by checking their permissions, unless it is by fluke.
[BetterBatteryStats] TNSMANI:
Please don't jump the gun. You are not supposed to bump your post within 24 hrs of posting it. Any way, I was coming to your post after dealing with the other posts.

Your dump is supposed to be for 6+ hrs not 5+ hrs.

Your drain is slightly higher at 0.9% per hour. Deep sleep was only for 3 hrs and 31 mts. The balance time your phone was awake.

As you yourself observed, mobile signal is an issue and it usually drains a lot.

BT was on causing a lot of wakelock and alarms. Disable it for the next dump.

Something called bfg_wake_lock_etc which is shown in kernel wakelock kept your phone awake for more than an hour. I have no information on it nor does Google.

You have some Location related alarms. You can disable Location and also wifi/BT scanning and take another dump.

I don't know what is com.hisi.mapcon which is also causing some alarms. If you disable Location and scanning, this may go down.

If you have AOD on, it is also causing some alarms.

And some background downloads, which are inevitable but not alarming.

Your major issues are mobile signal. Location and scanning.

If possible, locate the phone at a place where the signal is better, disable Location and scanning and take a fresh dump for 6+ hrs. After seeing that we will start worrying about the other unknowns. And wait atleast 24 hrs for an answer.
[BetterBatteryStats] beatschubser:
Thanks a lot for the detailed response, and sorry for being impatient with my last post. Will do as suggested and post the results.

com.hisi.mapcon seems to be related to WiFi Calling, which I have enabled.

AOD is disabled.

WiFi and Bluetooth-scanning are disabled, but I'm using a Withings Watch that is connected via Bluetooth 24/7. My phone reports the "Health Mate"-app (Withings) for constantly scanning for Bluetooth-devices. I will disable Bluetooth completely for the next test.
[BetterBatteryStats] beatschubser:
Here's the new dump: https://0bin.net/paste/AXOwos4+#eVrUWxs4fxe87H29fI8181THUAwPbR+kjDiJF1kOsqO

I couldn't do much about the signal quality, but Bluetooth and Location were disabled this time. It's better now, but still 10,7% awake time.
[BetterBatteryStats] TNSMANI:
Forget about the wake time. Drain is only 0.6% per hr.

Now the kernel wakelock is gone.

Do you have any settings enabled either in the ROM or in any app to delay the wifi going to sleep? Some such thing shows up in kernel wakelocks delaying wifi sleep by over 20 mts.

How long is it from the time you last cleared Dalvik and cache? Do it now, that will have some effect if deleted apps and such things were not cleared completely.

Widgets have some alarms. Can you reduce their number or frequency?

AOD and com.hisi.mapcon alarms are still there.

All other wakelocks and alarms are mostly related to your poor mobile signal. If you can manage a better signal, your drain may come down by 0.2 to 0.3%.

Rectify whatever you can from the above and take another dump. That will be your final drain rate unless you get a better signal.
[BetterBatteryStats] beatschubser:
There was a firmware update before the latest test, I guess that cleared the cache - after the reboot it said "Optimizing apps". EMUI doesn't have any setting to send WiFi to sleep, so I guess it is always on. (btw, what are "20 mts"?)

AOD is still disabled - could it be the in-display fingerprint-reader?

I will see if I can optimize some of the settings and post a final dump.
[BetterBatteryStats] TNSMANI:
'20 mts.' is nothing but 20 minutes.:p

It is possible that the in-display fingerprint reader is the cause of the AOD alarms.
[BetterBatteryStats] RANJITH THRISSUR:
Recently found that I'm loosing as high as 7 % charge overnight. Looks like whatsapp is the culprit. It was not the case before.. drain used to be 2%. I'm on nolimits 11.7, weeb kernel, eagle debloat.

Is it some new additional back ground checking done by whatsapp?

How can I get back the old level of battery idle drain?

One plus 7 pro is the device. My idle drain was as low as 0.2 to 0.4 in the past
[BetterBatteryStats] Nastrahl:
What I noticed since doze mode was introduced, is that to compensate and to avoid delays and being killed by the system, it uses the sensors like the accelerometer to keep itself alive all the time. It may use different tricks with sensors when the phone is still.
[BetterBatteryStats] Unreal-Forever:
Hi!

Finally I found the cause of the battery drain, thanks to the data provided by BBS I was able to draw the most accurate conclusion and clue.

The cause is shown by BBS as (com.google.android.gms), belonging to Google Play Services, in this there was a declared permission and they are the body sensors, once deactivated everything returned to normal, since Saturday that was when I deactivated that permission, I am checking and since then whenever the mobile turns off the screen it goes into deep sleep, I always leave BBS in the foreground showing the behavior from when I turned off the screen until I turn it on again and it always reports more than 90% of time in deep sleep.

I have been reading that this permission makes the mobile know when we are moving, I know that it is not the same in all, but in my case this permission is useless, so from now on it remains deactivated.

Thank you very much for the help you have given me in this community.

Greetings: David.
[BetterBatteryStats] Oswald Boelcke:
For a few days now, microG supports the official German Corona-Warn-App (and also others from other countries). Since then I've installed the updated µG version and the app (not battery optimised, running in background) i.e. Bluetooth, which was usually disabled on my device unless I used a head-set, is now enabled 24/7.

Just like to share my in my opinion very satisfying idle dump of still 0.4% / hour drainage.
[BetterBatteryStats] ijo7:
It's my first post on the forum so I wanted to say hello .

I recently bought Xiaomi Mi 10 and saw that I lost 10% during night (8hours). I've heard that people have trouble receiving their notification, but it looks like this time it's the other way around. When I check my battery stats I can see that the phone is always awake and never or almost never (1%of the time tops) in deep sleep mode. I've installed BBS and will provide some screenshots.

Edit:

Sorry I couldn't find any other way to post those screenshots, so I had to find some kind of workaround. First link contains all the screenshots. I'd be very grateful for your help. Thanks in advance.

The fun part is that I don't see any apps that would stop the phone from going into deep sleep apart from "android" alarms or "PowerManagerService.WakeLocks" at Kernel Wakelock.

https://drive.google.com/folderview?id=1-sgdDOAX0fNQpS3fqcWPTWAmToeBlOJG
https://imgur.com/y1Ny0u7
https://imgur.com/VouE6cp
https://imgur.com/lLL9MJJ
https://imgur.com/cSZDYqm
https://imgur.com/lmwluy9
https://imgur.com/y2Vh1L9
https://imgur.com/hrnWkTi
https://imgur.com/2226pbh
https://imgur.com/RRqkN6D
https://imgur.com/C9AqRlT
https://imgur.com/QtQYuDy
[BetterBatteryStats] mrjuniork:
First off, welcome to XDA, great having you here :highfive:

As a new member you need to reach a certain amount of post count in order to upload screenshots. That being said, screenshots are not at all helpful for finding any kind of culprits you might be dealing with.

Besides, you haven't separated those links with a space, so it's basically one long link that has to be separated manually ;)

I kindly refer you to this post in order for you to read about how to proceed, so we can get a better look at what might be the issue in your specific case.

Looking forward to seeing what you come back with.

Cheers :good:
[BetterBatteryStats] peterlee928:
hi all. sorry to bug yall with this, but i just couldnt find a solution after a search. i know my idle dump doesnt meet the requirements, but its pretty clear which kernel wakelock is the bad guy (first one in the "kernel wakelocks" section). any thoughts as to what could be causing this? much thanks in advance :)

idle dump here: https://drive.google.com/file/d/1-_wlsSrcCj759VInpXd9v7RnkAMAhBRX/view?usp=drivesdk
[BetterBatteryStats] ijo7:
I've managed to find out what's causing the issue. The phone stops going to deep sleep mode everytime I charge it. To prevent this I have to reboot my phone, but it's really annoying to do so every time. Do you know what might be causing the issue or how to prevent it permanently? From what I see the main thing keeping the phone awake after the charging is PowerManagerService.WakeLocks kernel wakelock(70% usage at this time) - so I guess it's not coming from any app, because all apps in "partial wakelocks" seem to be under 4% usage.
[BetterBatteryStats] mrjuniork:
What ROM are you on and did you flash a custom kernel?

Surely the usage time is way to high, but that's difficult to figure out without knowing more about the OS you are on and any other modifications you have made recently.

Please share some more details. When and what did you flash.

And if you haven't flashed anything, meaning having a complete stock android device, then you could try to factory reset the device and to start fresh.
[BetterBatteryStats] ijo7:
Yeah, I'm having a stock device. I wonder if I should flash xiaomi.eu maybe it'll help. What do you think about that?
[BetterBatteryStats] Vordx:
Now that this app is basically dead in development, are there other apps that shows wake locks/calls ? Or an all in all an alternative to this app?
[BetterBatteryStats] IronTechmonkey:
The speed of updates may not be to your liking but AFAIK there has been no indication that development has ceased. A look at GitHub shows the most recent work seeming to have occurred only 11 months ago which is not that long, especially considering that life has been far from normal for billions of people for the last 6 months. Even apart from that, it seems disrespectful in a development thread to ask for alternatives rather than bug test in the interest of development of the app that is the topic here. :|
[BetterBatteryStats] mrjuniork:
What exactly do you mean by flashing xiaomi.eu?

Flashing your stock ROM?

Have you tried to factory reset your device? When was the last time you did that, if you did that?
[BetterBatteryStats] ijo7:
I mean installing new custom rom called xiaomi.eu. I've never tried to factory reset my device, because it's fairly new. Bought it about 2 weeks ago.
[BetterBatteryStats] DB126:
Gotta love value assessments based on the speed/frequency of introducing potentially unstable changes to a mature app. :rolleyes:
[BetterBatteryStats] R1kki:
dump

hey.

want to ask you help.

miui 12, Xiaomi Mi 9 lite.

since June 2020, I have battery drain at night about 10%.

dump is in attachments.

could you help me to read the dump and understand what is the reason of the battery drain?

thanks
[BetterBatteryStats] TNSMANI:
Your mobile signal quality is poor and it normally is a huge drainer.

The next time you take a dump, do not start from 'unplugged' because there are kernel wakelocks related to charging which should be released sometime after charging is completed. But in your case, it took nearly 9 minutes. So start the dump when the battery is at 90% or even less.

The watch app set off alarms at the rate of almost 11 per hour. If you can control it, ok. Otherwise, disable it for the next dump.

Location also had a high number of alarms. Set Location to off and also wifi and BT scanning to off.

The SAR detector sensor was awake for more than 8 hrs. I don't know why. If there is a way to control it, do it.

Set AOD to off. Its sensor also had wake time of nearly 20 mts.

Network stats are not recorded. But I suspect that a lot of background downloads happened. That is normal if it is within limits. And it should not happen every day. But in the absence of stats, I have no way of checking it.

Take another dump after rectifying whatever you can from the above. Let us see.
[BetterBatteryStats] R1kki:
Great analysis!

Thanks a lot.

Will do and post again
[BetterBatteryStats] kzhkr:
hi,

would like to check if anyone encountered the stats not being reset after full charge 100%?

---------- Post added at 01:29 PM ---------- Previous post was at 01:29 PM ----------

hi,

would like to check if anyone encountered the stats not being reset after full charge 100%?
[BetterBatteryStats] amn1987:
Could anyone please take a look at the attached BBS dump?

I am trying to find the cause of unnecessarily high idle drain in an old Redmi 3s. About 5 months ago it was running LOS 15 by e/foundation with microG built-in. In combination with a custom kernel idle drain was excellent, 0.1-0.2%/h consistently. But after switching to Android 9 and later idle drain has been a mess. Currently on Havoc Pie. Daytime ~0.8%/h, overnight 1-1.3%/h. Idle drain was equally bad with no GApps and microG that had to be installed separately. So I flashed BitGApps. It has support for GMS Doze but it stopped working after sometime. Flashed Universal GMS Doze module and its again working unreliably. Freezing Google Play Services reduced idle drain for a while but after sometime it worsened to 1.6%/h. So I unfreezed it again before taking the dump. Also GMS Doze was working. Despite being in deep sleep for 99% or even 100% idle drain isn't as expected. 2G only, mobile data off,Sync off, GPS, Wifi, BT off. Ambient Display, Pocket mode off AFAICT. The ROM has built-in in support for blocking Wakelocks, Alarms etc so recently blocked a bunch of them.

Idle drain at this time at 0.53%/h is actually much better than what is had been for a really long time now.

Thanks.
[BetterBatteryStats] pjadec:
There are no problems in this dump. It seems to be normal drain (0,4-0,7%/h)
[BetterBatteryStats] amn1987:
Ah. OK. Will post another dump if the drain worsens. Thanks.
[BetterBatteryStats] TNSMANI:
This is your base drain. Since everything is off, you can't reduce the drain further (unless you are in aeroplane mode). As and when you start enabling wifi, data, BT, Location etc., the drain will get worse.

Next time you take an idle dump, leave the phone in the normal state in which you usually keep it, like wifi, data etc.

BTW how old is the battery?
[BetterBatteryStats] olidie:
One of the first things that I disabled when setting up the phone was sync. Contacts, calendar and K-9 are synced manually.
[BetterBatteryStats] Karpfenhai:
FYI, e-plus does not support fast dormancy, ergo you should turn it off!

*#9900# is the right code..

Swyped from my GT-I9100 using XDA App.
[BetterBatteryStats] noke955:
I already posted it, but I read elsewhere Nexus S doesn't support the code, so he is not able to turn it off (if it is on?)