yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] paolocorpo:
Many thanks for your very clear and detailed response !!!!

Yes I think that the issue started with Evie's first installation

I will test as you suggested

Regarding the log file ... I opened it but ... I can't individuate my personal data

For this reason I deleted the attachment

Honestly speaking I am not sure how to remove my personal data

Inviato dal mio Mi A1 utilizzando Tapatalk
[BetterBatteryStats] paolocorpo:
Ok

I tried changing launcher and using the default one (launcher3)

On the boot I had the same issue

Inviato dal mio Mi A1 utilizzando Tapatalk
[BetterBatteryStats] Oswald Boelcke:
Does it re-occur when you completely uninstall BBS and re-install it? Has BBS ever run without issues before on your device?
[BetterBatteryStats] paolocorpo:
For the first question I have to try

For the second question I need to underline that the message is only immediately after the boot

If I open BBS ... No issue !!

Inviato dal mio Mi A1 utilizzando Tapatalk
[BetterBatteryStats] Oswald Boelcke:
I might have overread this information; I apologise. Usually BBS has the permission to "start on boot". Is this granted? Please advise unless you know what I mean, and I provide some screenshots. However, I'm now "out of town" most likely till tomorrow.

And here you'll find my reply regarding logcat.
[BetterBatteryStats] yochananmarqos:
There's no log attached. Did you try clearing BBS's cache and data?
[BetterBatteryStats] paolocorpo:
Thanks la for your reply

I deleted attachment because I would try to clean it of my personal data ... But I am learning about it ;)

For your suggestion ... No I will try

I would like underline that O am able to run BBS

The only issue that I have is immediately after the boot

Inviato dal mio Mi A1 utilizzando Tapatalk
[BetterBatteryStats] paolocorpo:
Yes, the app has the right authorization to start on boot

And thanks ... I will have a look to the link about how clean a log file ;)

Inviato dal mio Mi A1 utilizzando Tapatalk
[BetterBatteryStats] paolocorpo:
Here my log generated by MATLOG and referred to error message that I receive immediately after every new boot
[BetterBatteryStats] yochananmarqos:
Again, did you try clearing BBS cache & data?
[BetterBatteryStats] skivnit:
There seems to be some issue with BBS on android pie beta on s9. I can only see stats since screen on or off. Sometimes I get some api issue error
[BetterBatteryStats] paolocorpo:
Yes I did without success

Inviato dal mio Mi A1 utilizzando Tapatalk
[BetterBatteryStats] TheNico14:
Bluetooth wakelock

Hi, I have a problem with a few wakelocks that keep my phone from sleeping while using bluetooth. I'm using a stock galaxy s9+ on 8.0. When I'm using bluetooth headphones with spotify I have a very high battery drain, initially I thought that spotify was the culprit but after installing BBS I learned that the problem was the bluetooth connection. The constant wakelock is caused by BT_host_wake and other bluetooth related things. I know that bluetooth headphones consume more battery than wired ones, but a constant wakelock like this drains more battery than the screen itself, is there anything I could do?

I can't post links, but if someone wants to help screenshots are on imgur at /HoGQbZh.jpg and /c2fKAxX.jpg

Thanks
[BetterBatteryStats] strongst:
Hi, a dump file will be more helpful than Screenshots like described in op. Also have a look at similar discussion here https://xdaforums.com/showthread.php?t=1179809&p=78206538
[BetterBatteryStats] Oswald Boelcke:
Thanks for providing the logcat. It seems that "something" prevents BBS from launching in the background immediately at boot. Now, my problem: I'm neither familiar with your Android version nor the BBS version you use; I guess it's one of the candidates via Hockey. I'm using BBS v2.4-265 without any issues from the Google Play Store beta programme. Additionally, I'm still on an Nougat ROM and do not intend to go for anything else for different reasons. So, no idea what doesn't grant BBS to start in the background. Did it properly work with a BBS version prior to v2.5.2-274?
[BetterBatteryStats] paolocorpo:
Thanks

Before was all ok

Inviato dal mio Mi A1 utilizzando Tapatalk
[BetterBatteryStats] Oswald Boelcke:
I guess then you've to wait for @chamonix to have a closer look into the release candidate you use. By the way: Do you have debug enabled in the advanced settings of BBS as requested in the OP (partially quotation below)?

If debug was disabled I suggest to enable it and to post another logcat for chamonix here.

Afterwards consider to meanwhile revert to a different version of BBS e.g. the one I use.
[BetterBatteryStats] paolocorpo:
Many thanks for all important suggestions

Really appreciate

Where may I download the version of BBS that you are using with success ?

Ciao

Paolo

Inviato dal mio Mi A1 utilizzando Tapatalk
[BetterBatteryStats] Farkat:
Same problem with beta fm HocceyApp on LOS 15.1 Xiaomi mi6. Rolled back to version fm PMartet, all fine, excluding state of net. All shows as WiFi, fact 50/50 wifi/cell
[BetterBatteryStats] dingsaller:
same here with 2.5.2.274, reverted to BBS 2.4.262. and the stop error after reboot has gone ....weird :confused:

OP3 LOS15.1+Magisk 17.3+Caesium kernel
[BetterBatteryStats] tsiftsism:
Hello.

I attach the files showing the battery consumption after the 1st charging of my device's new battery.

The device was fully wiped, so this is a fresh setup.

Can you please tell me if everything is working ok, or am i having draining issues?

I came back home from the office having consumed 19% without heavy use of the phone.

Thanks in advance for your answers.
[BetterBatteryStats] strongst:
We cannot answer your question cause analyzing a usage dump contains too many factors(external) not recorded by bbs. You can also refer to first post instructions.

Bad mobile signal for hours, roaming between cell phone towers etc. is one of high drainers while on move.

You can ask others screen on time of the the same device/setup within the device forum for example to get a feeling if something is wrong. ;)
[BetterBatteryStats] TheNico14:
Today I did the same during my commute and I tried with both spotify offline and soundcloud with the same 100% wakelock during playback so I would assume that is a bluetooth playback or connection issue and not a spotify one.

I'm still unable to attach files so i posted my dump on https://pastebin.com/vL7w4viT.
[BetterBatteryStats] strongst:
Your dump file is not recording 6+h and screen on time should be only some seconds, please have a look at the instructions in first post ;)
[BetterBatteryStats] TheNico14:
Sorry maybe I wasn't very clear, I know it's not a standby drain problem because doze works without problems in normal condition. The problem that I'm facing is that my battery drains like crazy when listening to the music with my bluetooth headphones, and with BBS I found that BT_host_wake keeps my phone from entering doze and I'm not sure if that's normal, I didn't find anything on internet about this problem. Shouldn't the phone be able to sleep while playing local music?
[BetterBatteryStats] TNSMANI:
Playing music will consume battery. How much is the question. That is why strongst suggested to you to post an idle dump so that it can be analysed to see what your drain is in sleep, whether it drains too much even during sleep, if so, what is the reason etc. So please post an idle dump.
[BetterBatteryStats] TheNico14:
Okay I'm going to do an idle dump tonight, I'll update you after that. Thanks
[BetterBatteryStats] Oswald Boelcke:
Despite the always available XDA-editions, I purchased BBS on Google Play Store a long time ago (refer to screenshot) mainly to show chamonix my sincere appreciation and to support the further development of BBS. Meanwhile I've joined the BBS beta programme on Play Store in accordance to the instructions on post #2 that I partially quote below. The BBS version I currently use is the latest available within the beta programme. Remark: I actually don't know if it's possible to join the beta programme without a purchase of BBS on Play Store; somehow I doubt.
[BetterBatteryStats] lukaszsas12:
hello, what is the surfaceflinger process ??

Wysłane z mojego BLA-L29 przy użyciu Tapatalka
[BetterBatteryStats] Jpas1:
I've been having some pretty significant drain and I'm not quite sure what's causing it. Android system is consistently the highest usage when I look at my battery usage. For example, after about 15 minutes of use (5 of which on YouTube) this morning, I dropped to 91%, which seems abnormal. Any help is appreciated!

Dump File
[BetterBatteryStats] DiamondJohn:
If by use, you are talking about Screen On Time, then projecting that out, you are looking at around 2hrs 45min of SOT. Is that bad for your device? And in your case, it wasn't just SOT but also video processing, network activity etc. ie your phone was performing battery draining things on top of lighting up the screen.
[BetterBatteryStats] Jpas1:
Sorry I didn't explain that better. Yes, I'm referring to SOT. 2:45 would be very poor for my device, as many get double that on the Note 9. I posted the dump file so that I can get insight as to what might be causing this.
[BetterBatteryStats] lklaus:
Just as follow up: i made a tasker profile switching off location services when switching off the display and not in WLAN (and when dropping off WLAN while display is off). Now the system sleeps well when in motion
[BetterBatteryStats] TNSMANI:
Instagram, Messages, wifi were draining battery. Control the sync of the first two. As far as the wifi router is concerned, reset it by switching it off for atleast 10 seconds. Also check whether there were other devices using the wifi. If so, disconnect them from the router and check. Mobile signal was also a reason. Choose a better place to rest the phone where the signal is better.

Always On Display set off one alarm per minute. Disable it and check. Location was on and had contributed to the drain. Do you require Location to be on even during sleep? Widget updates also contributed to the drain. Control them.

Smart Watch was connected? BT, Samsung Push both contributed to the drain. Disconnect it and check. CPU was at peak for about 13.5 minutes.

Controlling the above may result in a drain of about 0.7% per hour as against 1.7% now.
[BetterBatteryStats] iakoboss7:
hello, yesterday i installed in my phone (RR 8.1 redmi note 4 snapdragon) the last DEV version, all worked perfect.

today i got an email with a new update, installed it over the above and this keeps showing in my notifications screen.

what is it?

https://xdaforums.com/attachment.php?attachmentid=4651572&stc=1&d=1543165583
[BetterBatteryStats] tsiftsism:
Last week no one could understand from the files i attached if there was any battery drain in my device.

Today, since 10 in the morning that i unplugged the phone, i didn't touch it at all. But i have lost 2.6% per hour and it seems that the problem is something called rmt_storage.

Could you please read/see the files/photos i attached and tell me if possible what is causing the drain?

Thanks in advance for your answers.

https://i.postimg.cc/qv6Drm4T/1.jpg

https://i.postimg.cc/hP6M29x3/2.jpg

https://i.postimg.cc/CKV7gScG/3.jpg

https://i.postimg.cc/W46npCyQ/4.jpg

https://i.postimg.cc/nhm2gCGV/5.jpg

https://i.postimg.cc/5N6n5PHC/6.jpg
[BetterBatteryStats] Waiting4MyAndroid:
After the latest XDA edition update (2.5-283) I am getting the same persistent notification. SM-930T unrooted, but permissions granted through ADB.
[BetterBatteryStats] Nimueh:
Same here, very annoying - and I haven't found anything in settings to turn it off.

Honor View 10, RR Oreo, rooted w. Magisk.

Please tell us how to get rid of it [MENTION=1330150]chamonix[/MENTION] :crying:
[BetterBatteryStats] chamonix:
Latest bbs version ist compiled against SDK26 as Google has defined that as min SDK for gplay. Now in SDK26 all background processes are forced to show a notification icon when running in the background. BBS does this to handle events like boot - thus the crashed on previous beta - and devs are forced to go down that road now.

I am working on a workaround to provide a notification channel that can be ignored to get rid of another non-telling notification but until then we can only thank Google for this move
[BetterBatteryStats] shaggyskunk:
I'm using Tasker's AutoNotification to hide the notification from the Status Bar - Works perfectly ? [MENTION=1330150]chamonix[/MENTION]
[BetterBatteryStats] paolocorpo:
That's good idea !

Inviato dal mio Mi A1 utilizzando Tapatalk
[BetterBatteryStats] Nimueh:
Tasker is a paid app and I'm not going to buy it just to get rid of 1 notification lol.

I've forbidden BBS from showing notifications now ... not perfect but it'll have to do ;)
[BetterBatteryStats] chamonix:
On Pie (at least) when you go to settings - apps - bbs and notofication the settings will show you the notification channels and you can either turn the notifications off completely or diable a channel. The channel the 'event processing' notification is sitting in is called BBS so if you turn this one off it will only suppress the persistent one that has no real function
[BetterBatteryStats] Nimueh:
Oreo isn't that specific lol - this is what it looks like for me and it removed that persistent one ... no idea if that killed anything else though :laugh:

Thank you for all you do btw :) :good:
[BetterBatteryStats] shaggyskunk:
I believe that you can use the AutoNotification app for free by agreeing to watch ads or something - You don't need the full Tasker app (I'm using it for other things as well) & as [MENTION=1330150]chamonix[/MENTION] says in Pie Google has done away with such foolishness ?
[BetterBatteryStats] Nimueh:
Ah ok, but I'll just stick to blocking it through the system.

Thanks though :)
[BetterBatteryStats] chamonix:
The UI may be different but the category 'BBS' (I will change the name) is the channel that is used only for the event processing notification. Expect the category / channel to have a more speaking name in next build
[BetterBatteryStats] Nimueh:
Ah ok cool - thank you :good: :)
[BetterBatteryStats] TNSMANI:
This is not an idle dump. Phone was used for 7+ minutes before the dump was saved.

That apart, mobile signal is the worst offender. Your signal strength was bad and it drained battery.

rmt_storage seems to be related to kernel and modem. There is not much info about it on the net. So may be a change of kernel, if available, may cure it, though there is some info that it is related to qualcomm, in which case even a change of kernel may not help.

I am not in a position to comment on the other drainers since the stats of the phone being on, corrupts the idle dump. So please post an idle dump as per OP.
[BetterBatteryStats] Jpas1:
I appreciate the response. A lot of those are simple fixes, which is good to hear. As far as location and widget updates during sleep, is there a way to automate those things to turn off when the device isn't in use? I'd like to keep them enabled during usage and manually toggling all the time seems like a hassle.

Lastly, I do not own a smart watch, so that's very strange to see. Do you know what I should disable or what would cause that CPU usage?
[BetterBatteryStats] RainGater:
Created a widget in the home screen and in Settings - Widget, I set the stat type to "Since Screen Off". The widget doesn't refresh automatically. When I turn on the screen, the widget is static and have to refresh it. Is it by design?

Btw, awesome app.
[BetterBatteryStats] TNSMANI:
As for Location, I previously used LeanDroid from the PlayStore. Now I simply disable Location since I use it for navigation alone and manually enable it when required. But for widgets, I have no idea (except for may be using Tasker or a similar app but I don't know whether it is possible). You can think of reducing the number of widgets atleast.

Disable BlueTooth atleast during the night even if you require it to be on during daytime. Once again, LeanDroid helped me before for BT too.
[BetterBatteryStats] chamonix:
No, this is a bug left by the transition to the new background processing. I am working on it
[BetterBatteryStats] chamonix:
New build is up with translations updated and a new language: dutch was provided by github user matthias-vdE.

I also changed the name of the notification channel to be more speaking and hopefully the widget updates should be fixed as well.
[BetterBatteryStats] RainGater:
Yes, the refresh works and thank you so much for providing quick updates. Awesome!

Btw, when you turn on the screen, it takes few seconds (maybe 3 - 4 seconds) to refresh but that's okay I guess. Also, after the phone is turned on, refresh is not automatic or is there a setting? That's not a big issue, just wondering...
[BetterBatteryStats] Ysalamiri:
Ha, that's me! But I'm not very active on the XDA forums at all.

I'll double check the translations in the app itself to make sure they make sense in their context.
[BetterBatteryStats] :
[MENTION=1330150]chamonix[/MENTION] Thx for your extra ordinary support and continuing maintenance for this great app.

Quick question: have you killed "legacy widgets"? Would be a pity (at least for me ;)).
[BetterBatteryStats] deitrich:
Hello! I have a fundamental question. why the latest edition is not officially published?

Wysłane z mojego RNE-L21 przy użyciu Tapatalka
[BetterBatteryStats] RUPESHBW:
Do i need to make BBS to system app in android pie custom rom
[BetterBatteryStats] chamonix:
The delay on screen on is doe to the fact doze mode schedules jobs. I could reduce the delay but this may cause doze to take restrictive actions.

While the phone is on refreshes get scheduled every 5 minutes with a grace period of one minute. If this feels to low to you I could try to increase the frequency. Unfortunately the job api is not flexible enough to allow things like "schedule only while user is active" so I need to make trade-offs.
[BetterBatteryStats] chamonix:
Nope, system app got deprecated
[BetterBatteryStats] chamonix:
What do you mean with officially published? My policy has always been to put xda users first so there is always a delay between version I publish for xda users (using hockey-app) and betas on gplay. The means of distribution are not important to be, getting feedback from an engaged community it at the center of my release policy
[BetterBatteryStats] RUPESHBW:
Thank you, just bought the app few hrs ago:)
[BetterBatteryStats] chamonix:
Yes I did because stats showed a low usage. If they are important to you and now that I have fixed the refresh issue for the new one I can replicate that.

Are they that important to you? If yes, what are you missing in the new widget?

This is not a question to trick you, I am genuinely interested in understanding what brings you to prefer to use the legacy ones
[BetterBatteryStats] chamonix:
Then proper credits due to you! If you want me to add credits to your xda user, or Twitter, or anything else just let me know
[BetterBatteryStats] deitrich:
[MENTION=1330150]chamonix[/MENTION] I get e-mails with the latest version, but I thought that gp is also updated. Ok. thanks for the answer

Wysłane z mojego RNE-L21 przy użyciu Tapatalka
[BetterBatteryStats] :
Thanks for your fast response.

Yes I'm using legacy widget on all my devices "for ages" and would be very happy if you can reintroduce it. I'm using it 'cause it deliver a lean and clean status/overview about battery stats. I've attached a screenshot to visualize.
[BetterBatteryStats] chamonix:
Gplay will be in time but the prime time will always be for xda until we have reached a certain stability of code as well as in features. One good example is the conversation we are just having in regards to legacy widgets: based on the feedback I will probably re-instate legacy or merge them into the new widget. Such a change on gplay would just cause bad ratings but gplay does offer a space for having a conversation. This is why I do things as explained.
[BetterBatteryStats] chamonix:
I get your point and will provide that view back. I don' t want to remove any features that have value but rather reduce the code base I have to maintain. Expect the view to be re-instate, either ported to the modern widget or re-enabled: I will have to look into the best approach.
[BetterBatteryStats] RUPESHBW:
Is there any historical data available in BBS to see how many time charged . When and how much battery drain in week or month like that ? Or it just detect apps and processes which drains battery not history of battery
[BetterBatteryStats] strongst:
There's no history cause of Android itself. Maybe on this page you'll find a workaround and/or answers too: https://xdaforums.com/showthread.php?t=1179809&p=78153558
[BetterBatteryStats] Ysalamiri:
That's OK. As I said, I'm not active on these forums at all. I added my Github handle in the credits, if that's OK.
[BetterBatteryStats] Banayat:
Graphs view shows up bluetooth being enabled randomly on s7 edge (Android Nougat) . I've checked Permissions for all apps and haven't been able to find out what is causing these RANDOM bluetooth activations on my device. I seem to be blind finding any respective app producing this wakelock. I need some help :confused:
[BetterBatteryStats] Oswald Boelcke:
Is "Bluetooth Scanning" disabled in ROM settings => Location (please refer to here)?

Remark: Please be aware that users of XDA Labs aren't able to see the title of a post i.e. repeat any useful information in the title also in the post.
[BetterBatteryStats] Banayat:
Yes, it's disabled. I also found a bluetooth related option within Developer Options called "Bluetooth HCI Snoop Log" which is disabled, too.

Sorry, really didn't know that. Thanks :good:
[BetterBatteryStats] Fif_:
I've been having problems with screen on/off references when the watchdog option is active. I'm using the play store current version 2.4-265, and I'm seeing this on multiple devices, all running some variants of Nougat (OOS 4.5.15/Nougat 7.1 on a OnePlus 5, LineageOS 14.1 on a Nexus 5).

Some times the screen off an on references are saved correctly, and other times it looks like both references are saved when the device wakes up: while the device had been idle for a while, turning the screen on and unlocking shows that both references have been saved mere seconds apart when the device woke up. This makes the monitor report crazy awake times, with an awake percentage over 100%.

I've tried toggling "Watchdog on unlock" on or off but it didn't make a difference.

It almost looks like BBS is forgetting to put a wakelock when saving the screen off reference ;)

How can I help troubleshoot the issue?

Edit: I've added two pictures showing the problem. When I unlocked the device and clicked on the BBS notification shown, the device had been idle for over 20 minutes.
[BetterBatteryStats] Oswald Boelcke:
If interested to dig into it further I suggest to provide an idle dump iaw. the OP. Maybe - but maybe not - it helps to identify the culprit.

You might also want to consider to take a "long time" logcat and analyse it by use of some BT related keywords.

Absolutely concur, that's weird. However, I can't confirm the issue. Using BBS 2.4-265 with enabled Watchdog (default warning settings at 30% and 10 mins.) on two devices, a Samsung SM-G901F and a Samsung GT-i9305, both on RR-Nougat-v5.8.5. None of them shows the behaviour as described by you. Occasionally but very rarely the notification (as in your first screenshot) pops up but with reasonable values. I'm interested if others experience the issue, too, and if we are hopefully able to track down the reason.
[BetterBatteryStats] TNSMANI:
I can confirm the screen off and on stats issue. It is occasional and I did not dig deeper into it. I am also running the BBS PlayStore version but on my OP3 running SkyDragon Pie ROM. In addition, after a full charge today, the only reference shown is screen off to current. No "from boot", "custom ref", "charged" "unplugged", "screen on" etc. I have cleared the cache and data of the app and now the default "from" "to" references are shown. Hopefully the issue is resolved.