yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] TNSMANI:
Location seems to be on. Do you require it when the phone sleeps?

There are background downloads upwards of 15 MB in total of which the majority (15MB) is by Ideashower. Perhaps these downloads were the reason for the network_linger_complete alarms in your dump. Are you running a custom ROM or kernel? Whatever it is, the phone was at max CPU speed for more than 5 minutes though it was supposed to be asleep.

I could not find any other issue jumping out. Let the others also see and comment.
[BetterBatteryStats] detpruf:
Regarding location, I use Google location history. However sometimes (rarely) I have only 3% battery drain overnight.

The Ideashower download is from the Pocket app which updates once a day.

I am running the official Android Pie with the latest updates (April 2019 security) with no custom ROM or kernel.

If I disable/enable and clear cache for Google play services app, the overnight drain is under 5% but it goes over 10% after ~3 days. And then the main issue is that overall battery life is bad, not only over night.
[BetterBatteryStats] chamonix:
The reason is that these stats are gained from other sources, not the battery info api. I will hopefully get hands on an S10 tomorrow and be able to do some debugging. More to come once I have some ideas
[BetterBatteryStats] chamonix:
Can you please link to the thread you mention?
[BetterBatteryStats] chamonix:
I will hopefully get hands on an S10 tomorrow. Android studio is already updated so once I have the device I will be able to debug. My fear is that Samsung has tweaked selinux, rendering the device incompatible with the android spec. If I can not work around that by simple means it will potentially require bringing back the stats one by one using alternate sources like dumpsys and lots of heavy maintenance parsing. If anyone has info/intel on any progress from the other devs in the segment I'd be happy to hear and/or engage in a common effort to solve this issue
[BetterBatteryStats] dominicstg2:
Is this normal for leaving the phone alone from 'll.30pm to 5.13am s10 plus exynos
[BetterBatteryStats] akira888:
Coincidentally if you have a look at post#35759 in this thread. I think that is from S10?

Also in this thread:

https://xdaforums.com/galaxy-s10/review/standby-drain-t3888496/page17

Post#169

Thanks!
[BetterBatteryStats] tsiftsism:
Thanks for replying.

The battery i can say it's a new one, i sent the phone at Oneplus service department for its replacement on November.

Now, as for Instagram, Inbox and Adguard wakelocks that you mentioned, I don't know what to do.

What do you suggest?

I guess I'm not the only one using these 3 apps and probably all of us are having the same problem.

What do you people were going to do if these apps were keeping your device awake?

As for the Pocket detection I already disable it.

Thanks in advance for your answers.
[BetterBatteryStats] chamonix:
Call to action: if you own an S10 and whether bbs works or not (if seems to work in certain cases) please make a post and attach a dumpfile. I want to collect the device info etc to get a better picture.

Fingers crossed it won't work on the device I am getting :)

If you could add "dumpfile S10 : working/not working" if would help triaging.
[BetterBatteryStats] chamonix:
Thanks. I have posted my call to action over there as well
[BetterBatteryStats] o_01uk:
Galaxy s10e exynos BBS partially working (alarms and cpu states only)
[BetterBatteryStats] DB126:
Comments:

- Adguard wakelocks are benign and can be ignored

- Mail clients vary in screen off power use; try some others if dissatisfied

- Social apps are, well, social by design and will leverage every opportunity to bring you the latest cat video and pic of Aunt Toenail's bursting bunion; pick your poison

- That said, none of the above were significant contributors to screen off power drain

- Replacement batteries are rarely new; probably been sitting on the shelf for 2-3 years

- Real culprit is age of device (including battery) and suitability/optimization of Android 9 for use on a legacy kernel and platform. Seriously, how much effort do you think OnePlus put into tuning an update to a legacy device that brings in no revenue? Consider returning to Oreo if the 1%/hr idle drain proves bothersome.
[BetterBatteryStats] TNSMANI:
The screenshots say that they are from Charged to Unplugged which could not be more than a few seconds to a few minutes (unless you left it on the charger overnight while taking the dump). This is not the way to take a dump. Read the OP for the correct method and post a .txt dump here. The Dev is interested in analysing dumps from S10 and S10+ since it is reported that BBS does not work on those devices. Read the posts between yours and this.
[BetterBatteryStats] chamonix:
Just a little teaser:

===================
General Information
===================
BetterBatteryStats version: 2.5
Creation Date: 2019-04-27 17:08:32
Statistic Type: Unplugged to Current
Since 1 h 54 m 24 s
Note:
VERSION.RELEASE: 9
BRAND: samsung
DEVICE: beyond1
MANUFACTURER: samsung
MODEL: SM-G973F
OS.VERSION: 4.14.85-15445945
BOOTLOADER: G973FXXU1ASBA
HARDWARE: exynos9820
FINGERPRINT: samsung/beyond1lteeea/beyond1:9/PPR1.180610.011/G973FXXU1ASBA:user/release-keys
ID: PPR1.180610.011
TAGS: release-keys
USER: dpi
PRODUCT: beyond1lteeea
RADIO: G973FXXU1ASBA,G973FXXU1ASBA
Root perms: false
SELinux Policy:
BATTERY_STATS permission granted: true
============
Battery Info
============
Level lost [%]: Bat.: 36%(47% to 83%) [-18,9%/h]
Voltage lost [mV]: (3846-4183) [-177,4%/h]
===========
Other Usage
===========
Deep Sleep (): 44 m 41 s 39,1%
Awake (Screen Off) (): 8 m 1 s 7,0%
Screen On (): 9 m 5 s 7,9%
Wifi On (): 1 h 1 m 46 s 54,0%
Wifi Running (): 1 h 1 m 42 s 53,9%
Doze Interactive Time (): 9 m 1 s 7,9%
Doze Idle Mode Time (): 36 m 37 s 32,0%
No or Unknown Signal (): 1 s 0,0%
Poor Signal (): 37 s 0,5%
Moderate Signal (): 5 m 13 s 4,6%
Good Signal (): 32 m 28,0%
Great Signal (): 23 m 51 s 20,9%
Screen dark (): 1 s 0,0%
Screen dimmed (): 3 m 31 s 3,1%
Screen medium (): 5 m 32 s 4,8%
Screen bright (): 0,0%

Keep the S10 dumpfiles coming though, I had to implement a hack based on specific device values and I want to be sure that all are covered. To be precise this is the filter for the exception, and I want to be sure that the S10+ is covered by that:

if (Build.BRAND.equals("samsung") && Build.VERSION.RELEASE.equals("9") && Build.DEVICE.startsWith("beyond"))

Edit:

changed the logic as this would "fix" S10+ devices as well and I have proof at least some work: beyond2q

I think I have found a better approach:

1. check to get the stats with the right means, depending on the android version

2. if 1. fails fall back and try with the workaround method

This has the advantage of not applying the workaround based on the device family (as some are working) but rather as an exception if the method that is supposed to be used fails.
[BetterBatteryStats] o_01uk:
I have signed up for beta on the play store if you wanted to release the new build and test if it's working on s10e exynos
[BetterBatteryStats] chamonix:
The test version will be made available through the channel described in the first posts first. Based on feedback it will go the gplay beta second.
[BetterBatteryStats] sherlock5545:
I attached mine. For some reason the version from the Play Store kept crashing when trying to share the dumpfile from within even though storage permission was granted. I tried the XDA version and same problem and even though private storage was disabled, it did save the dumpfile there.

Anyway, mine only works with alarm and CPU states. S10+ Exynos.
[BetterBatteryStats] chamonix:
Perfect! that confirms my theory!
[BetterBatteryStats] chamonix:
New release is up! Please report success/failure esp. on S10 models, and report regressions on other devices as well!

Edit: taking a break for the evening now, see you in the morning ;)
[BetterBatteryStats] timbiotic:
dumpfile S10 : working

Posting per request in other thread. No analysis needed but I'm able to see all the options I think. I'm also in developer mode. Not sure if that matters. Paid for app on play store
[BetterBatteryStats] timbiotic:
Play store? Still showing September 2018 last updated. Probably I'm just too early
[BetterBatteryStats] chamonix:
I promised an update on the investigation, based on your feedback (yes, your are great!) and so that other devs struggling with this issue can fix their code (I pushed to github so it's all there) :

- beyond0* are affected and the workaround should fix the problem

- beyond1* same as above

- beyond2 same as above

- beyond2q not affected, battery info works as it should

I will keep updating this post if anything new comes up
[BetterBatteryStats] chamonix:
No, the first ring is xda: updates are always posted here because a) I keep my promises and b) because xda is a vibrant community

Check the first posts of this thread if you want to be on the bleeding edge, gplay beta will follow only when I have received enough feedback from Active testers/reporters
[BetterBatteryStats] sherlock5545:
Here's another dump using the latest test build. Looks like my beyond2 is currently still facing issues. Only alarms and CPU states.
[BetterBatteryStats] lukaszsas12:
adds my may be useful

I can not add

Wysłane z mojego SM-G975F przy użyciu Tapatalka
[BetterBatteryStats] chamonix:
Your dumpfile was taken for 3 minutes so it is hardly representative. Do you still get the toast message that battery info could not be accessed? Do the raw stats get populated or are they empty?
[BetterBatteryStats] lukaszsas12:
where should I download version 2.5.308 ??

Wysłane z mojego SM-G975F przy użyciu Tapatalka
[BetterBatteryStats] sherlock5545:
Haven't seen a toast when opening the app, but when I go to raw stats, it shows "BatteryInfo Service could not be contacted" and it's empty. Currently 45 minutes from unplugged.
[BetterBatteryStats] chamonix:
See the first posts of this thread
[BetterBatteryStats] ianmacd:
One more S10+ dump for good measure. Nothing at all working on my device, although a couple of stats were working at one point. Not sure what made them stop.
[BetterBatteryStats] lukaszsas12:
ok do I have everything okay?

Wysłane z mojego SM-G975F przy użyciu Tapatalka
[BetterBatteryStats] 93ae8074:
beyond2 working here.
[BetterBatteryStats] drezz2:
Goodnight

I am using version 2.3, but I have noticed that from time to time (this time it has been after putting data and activating the location, although I have not used gps applications, if the location history has used it) the case is that I have received notifications of the application that indicates that it is consuming a lot of time in the background, but I do not see any wakelock or process consuming anything, I attach the captures even though the time is not representative, it is only if someone knows what may be due what the application indicates.

a greeting

edit:I think it's because of the GPS, something should not go well with my system, although I removed the location once I turned it on

the txt file is in airplane mode (i know the time is not representative)
[BetterBatteryStats] lukaszsas12:
works on my S10 plus thanks for the work

Wysłane z mojego SM-G975F przy użyciu Tapatalka
[BetterBatteryStats] zjhao:
G975FXXU1ASD6(CSC:BGL)

Summary:Not work

Partial Wakelocks:Not work

Alarms:Work

BBS 2.5-308 version only applicable to G975FXXU1ASD5?

View attachment BetterBatteryStats-2019-04-28_063548721.txt
[BetterBatteryStats] GialanG:
S10+. 2.5-308. Only Alarms and CPU Stats work.
[BetterBatteryStats] sohebq:
I have frozen maps, still, there are maps showing in alarms, Can anyone tell me what is running maps? also how can i decrease gsf wakelocks. Dump and screen capture attached.
[BetterBatteryStats] jeremysherriff:
The GSF count in Alarms isn't enough to be a problem.

Can you take a log for when the phone is idle? Charge, then unplug, leave idle for a few hours, then take the dump file. Make sure you use the view "since unplugged".

Don't freeze maps, or any other Google apps, unless you know what you are doing.

Make sure you sign out of Latitude and GTalk if you use them.

But your problems are likely to be these:

Wakelocks
=========
Managewakelock: partial (UID): 1 h 40 m 23 s (6023 s) Count:795 6.0%
FacebookNotificationService (uk.co.senab.blueNotify.FriendCaster Pro): 27 m 28 s (1648 s) Count:29 1.6%
[BetterBatteryStats] sohebq:
The phone remain idle for around 6-7 hours. If I don't freeze maps, it keeps on running in the running services, I don't need map for anything. I never use LAtitude. However, I do use google talk for a little time. LAstly, I don't understand why facebook notification kept on running for 27 min, because I have unchecked notifications.
[BetterBatteryStats] bergerc:
LocationManagerService is killing my battery

Recently I have noticed the battery life of my Desire HD has diminished significantly. Now the phone struggles to last even one day whereas it used last for 1.5 to 2 days between charges. I'm running 2.3.5 (software number 3.12.405.1) on kernel 2.6.35.10-g931a37e, build number "3.12.405.1 CL199157 release-keys".

I came across this thread and installed Better Battery Stats to try and get an idea of what is going on. What I see is that LocationManagerService is keeping my phone awake over 90% of the time. For example the phone has been idle most of the time since I unplugged it when I woke up this morning (7.5 hours) and BBS (Partial Wakelock since unplugged) shows that LocationManagerService has been active for 7h 7m 53s, count: 6 (96.1%).

The next biggest entry is MyProfiles with 3m 17s, Count: 22, 0.7%.

I've attached the BBS log from yesterday which I took just before going to sleep last night - it exhibits the same issue I describe above.

The only thing I have done recently is install a few application updates from the market - generally I apply updates as and when they become available.

Can anyone suggest what the cause of this issue might be and how to resolve it?
[BetterBatteryStats] Karpfenhai:
From what i can see, the location service is your culprit, try to get rid of it and use altitude instead! Maybe cleaning the application cache will help too.

JD is not good too, freeze it for a test.
[BetterBatteryStats] jeremysherriff:
A service running isn't necessarily doing anything - it's just alive. You can see from the stats its not using CPU time.

The phone remaining idle isn't my point - my point is that you took the log during your working day, so we can't easily tell what was keeping your phone awake, vs what you were activily doing with it.

Lastly: It's not the Facebook app itself that is awake, it's FriendCaster Pro. Remove your Facebook profile from FriendCaster Pro if you don't want/need it notifying you.
[BetterBatteryStats] chamonix:
You are right, location manager is the problem. But with this behavior there must be something else: the count is low but the wakelock is held for a really long time, suggesting that whatever happens while the wakelock is applied does not run properly. As there is no code to look at it's only speculations but it could be that the caching actions performed by maps are not working as planned. I can not imagine that this is network related but rather i/o related. I also see that your phone runs for a few days so it would be interesting to see if that behavior stops after a reboot. If it persists a logcat and a radio logcat may help finding out what happens during those long times
[BetterBatteryStats] glennkaonang:
Could someone take a look at my dump file here.

I want to know what makes my phone awake for quite a long time besides me listening to music with it.

I listened to music for around under an hour.

The rest I did some messaging here and there.

As you could see, the screen on time is only around 1 hour.

From what I saw, it's this Google Services wakelocks that keep driving me crazy.

I'm sure that I have turned off auto sync & auto backup.

I uninstalled Maps, News & Weather, Talk, Wallet since I don't need them.

I do use Google Talk but via Beejive because I have accounts from other IM as well.
[BetterBatteryStats] jeremysherriff:
Maybe, but you also seem to have a kernel issue:

Kernel Wakelocks
================
"modem_ip_rx" (): 1 h 56 m 2 s (6962 s) Cnt:(c/wc/ec)2138/883/2137 10.7%

You may have made things worse by uninstalling the Google apps, especially GTalk and Maps. Maybe, maybe not.

Whatsapp is a known drainer, remove it if you can.

You should turn off the keypress sonds for softkeys too:

Wakelocks
=========
<snip>
AudioOut_1 (1013): 50 m 35 s (3035 s) Count:100 4.7%

Can you post a dump file that only covers idle time (charge before bed, dump the file when you get up with "since unplugged" view) so we can see what is background processes please?

Edit: @glennkaonang you have posted about these same issues a couple of times now I think? Especially about uninstalling/freezing parts of the Google apps & framework. Are you trying different ROM's all the time? Coz it seems to be the same stuff in the logs: http://xdaforums.com/showpost.php?p=22640933&postcount=3359
[BetterBatteryStats] glennkaonang:
So what does "modem_ip_rx" mean?

Could you explain?

What about Google Wallet?

Is it okay for me to uninstall it since I really have no intention of using it.

If I didn't uninstall it, it's showing in the running apps.

Or perhaps disabling it via manage apps is enough?

Regarding the audiout, it's when I played music actually.

I did turn off the keypress sounds.
[BetterBatteryStats] jeremysherriff:
Hmm. It means your modem (data connection on your phone) is receiving data packets. I would normally expect this to be WIFI_ not modem_ so it's hard to say what the problem is. It *might* be WhatsApp, or one of the other apps you have in push mode. You might need to disable all push mode apps for a bit, and enable them one-by-one to see which one is a problem.

It is more likely that your kernel or modem firmware has a problem, is changing the modem code a possibility?

Wallet is OK to uninstall, it does not actively sync AFAIK. I think it just syncs when you open it.

OK, I'll take your word on that. Other people with AudioOut_1 report the wakelock reducing or disappearing when disabling key sounds. A music app should register the wakelock under its own name I think, not a system component, so maybe it's notification and ringtone noises?

This is why we need to see a log for idle time, when you have not been using the phone.
[BetterBatteryStats] glennkaonang:
You mean flashing other baseband?

Ah I see now, yes it's notification ringtones.

Well I'll try to get my phone idle.

How long do you think it's enough to see the log?
[BetterBatteryStats] jeremysherriff:
Two hours is sufficient usually..

Any problems show up pretty quick because the wakelock length or count is so high.

Hmm, maybe another baseband, different phones have different terminologies. The SGS2 people often mention their "modem version", but I'm not sure if that is the same as their baseband. Probably a question in the Q&A section of your device. Also, maybe a question for the kernel developer?

Edit: you could just flash another kernel, see what happens... :D
[BetterBatteryStats] glennkaonang:
Alright, I'll try flashing another kernel, charge my phone, unplug it and have it idle for some hours.

I'll post back here later to see further help.

Thanks a lot.

And yes I'm sorry for posting the same issue.

Before now I was trying almost all ROMs available to get my problems fixed.

But now I'm sticking to one because I really like this one.

But yeah, the issue still persists and I really have no idea what to do than posting my problem here.

So, sorry for this.
[BetterBatteryStats] jeremysherriff:
No problems dude! I'm was unsure, because depending if this was different ROMs/kernels or the same, might be a clue as to the problems!
[BetterBatteryStats] bemymonkey:
So lots of WiFi_RX is normal? Because that's always at the top of my kernel wakelock list... I've been wondering this a few days now, mainly because someone mentioned to me that current kernels use too much power for WiFi on the Galaxy Nexus - possible?
[BetterBatteryStats] jeremysherriff:
No man, not normal, just more common!

Try setting a static IP instead of using dhcp for your wifi settings.

Also try changing your wifi router's channel (might be interference from other access points), other stuff. There's a whole bunch of suggestions in this thread somewhere, search on the exact wakelock name.

Edit: Hmm wifi power is not likely IMHO, but possible. There's an app in the market for reducing transmit power, not sure if it will work for your device tho. Keep in mind most wifi devices conform to the standards, which say wifi transmit distance is like 90ft or more. Your router is probably only 20' from you I'm guessing, so you might be able to reduce it with no effect. But then what happens with public wifi? Might be too low then.
[BetterBatteryStats] Szczepanik:
You might want to look at WiFi Timeout from Android Market

https://market.android.com/details?id=com.lastmile.wifitimeout

Cheers

Tom
[BetterBatteryStats] bemymonkey:
WiFi turning off at any time is the last thing I want :p
[BetterBatteryStats] aashgaur:
hey again ... heres my full dump file !! :)
[BetterBatteryStats] chamonix:
Please attach a dumpfile
[BetterBatteryStats] GialanG:
Update: After charging my phone to 93% and unplugged, BBS started working normally like a charm. Now everything is shown ?
[BetterBatteryStats] dr4go:
Same thing happened to me... I guess the voltage references were borked in the beginning. Since today morning everything is perfect, thanks a lot! :)
[BetterBatteryStats] chamonix:
No the workaround is not specific to a model but it seems that Samsung has done things differently depending on the model, causing different errors on different models. I am working on adding more diag logging as I am blind since the workaround works on my s10
[BetterBatteryStats] sherlock5545:
Hey, just a quick update. Yesterday it didn't work for the whole day. Then before going to bed I thought I'd reboot the device and leave on charge overnight. I can confirm this morning everything is working just fine.
[BetterBatteryStats] ianmacd:
It's working fine on my S10+ (G975F) also.

Many, many thanks. The device felt incomplete without BBS.

I hope your work inspires the GSAM developer to update his app, too.
[BetterBatteryStats] giovag7:
I would like to try bbs on my S9+ not rooted. I bought bbs on playstore in the past... Can i use that version or another one?
[BetterBatteryStats] Richy19:
Is there anyway to have BBS remember stats over a reboot? My phone is draining over night when battery saver is on but because it turns off it forgets all data and I can't pinpoint what's causing it
[BetterBatteryStats] strongst:
No, that's not possible, but just do your test when you're awake to save the dump file before the battery is empty.
[BetterBatteryStats] chamonix:
New build is on its way, with a few tweaks in regards to the S10 workaround:

- Less calls to the battery service: for the S10 we use the legacy mode and too many calls to the API causes the battery service to crash

- App Permissions as well as dumpfile shows the state of the battery info calls (i.e. "fallback" for the S10) as well as the last error returned by userland if the service failed

During my tests today I have noticed that some times the service fails, due to BBS calling it in legacy mode. If this happens there is no alternative than rebooting the phone. This is unfortunate but this can not be avoided until I find a way to avoid the workaround (legacy call).

The root cause is the S10's SELinux policy, preventing BBS from reading the parcel. Samsung may have a different opinion on that but in my eyes it is a bug in their android implementation.

I am exploring one other option to get it to work but don't have much hope. I will leave the current build for feedback a few days and decide to go to gplay beta based on your feedback.

Edit: this option was a deadend so atm so clean solution for the S10, but a somewhat stable workaround at my end