yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] chamonix:
can you please provide some screenshots as well info about the launcher used, the screen density and any settings related to widgets (number of columns, padding).

App widgets is kind of a nightmare and requires lots of tests to find the parameters that are the best compromise. Eg 2x2 on my n6 and nova with 5 columns shows a circular large diagram without any legend (as intended).

I also may over obsess in trying to solve all these device dependent things in the code instead of providing controls via the preferences.
[BetterBatteryStats] dasojie:
Hey dev,

any idea what is security.snet.snetservice?

thanks

HTC Desire 601 kitkat 4.4.2 stock rom kofilakernel
[BetterBatteryStats] tcchuin:
having problem with qpnp_fg_memaccess and qpnp_fg_tempupdate, anyone having the same issue?
[BetterBatteryStats] meduza:
[MENTION=1330150]chamonix[/MENTION] ,

I'm using your fantastic app since a long time already on different devices. Now on galaxy s6 with exynos 7420 BBS doesn't show all 8 cores usage, (maximus is 2100MHz but BBS shows max 1500). I guess, it's because of 64 bit CPU or because of 8 cores. So my question is, do you plan to work on this issue in future?

Thank you for this great app and your commitment!

m.
[BetterBatteryStats] code010101:
my HTC One X+ has 1280x720 pixels, standard Sense 5 luncher, with 5x4 (rows X columns) icons on the desktop,

here is a screenshot. As I try to reduce the widget I get a small circle ...
[BetterBatteryStats] UncleMike:
Screen on 100%

I've been having severe battery life on my (not rooted) 2013 Moto X since some time over the summer, but I'm not exactly sure when since I initially attributed the poor battery life to abnormal usage and didn't realize it would be an ongoing issue. Earlier this week while outside before sunrise, I turned my screen off (with the power button) and noticed that the screen flickered several times for 1-2 seconds afterward. Now that I'm conscious of it, I can see this issue seems to come and go randomly, but I have only been able to reproduce it when Active Display is enabled. Anyway, I installed Better Battery Stats and it's telling me that my screen is on 100% of the time, despite the stock battery info telling me it's on much less.

Possibly related: I dropped the phone in a sink with the water running in June, and it's possible that the battery issues started then, but I'm not sure.

After the flickering, the screen appears to be off, but is it possible that the screen is never actually powering off completely, causing battery drain that just not being reported properly in the stock battery info?
[BetterBatteryStats] chamonix:
RC3 is up. I have been working on the widget layout and code and I hope things are getting better in terms of supporting more launchers/screen densities
[BetterBatteryStats] code010101:
much better now! many thanks :)
[BetterBatteryStats] It_ler:
After installing RC3, I checked the responsive widget.

Awake time (Aw) shows another time than on the other (legacy) widget and in the app itself.

Awake time of the legacy widget is the same like in the app. So I assume that the Aw time in the responsive widget is wrong on my phone.

Anybody else?

Signature:

Device:

SGS5 (SM-G900F)

ROM:

AllianceROM v9.1

Kernel:

Stock XXU1BOE6 kernel

Recovery:

TWRP recovery by Ktoonsez

Modem:

XXU1POG1
[BetterBatteryStats] chamonix:
in the new widget awake is indeed calculated as 'awake when screen off' as opposed to the in-app and legacy widget values that are awake as the total awake time, including screen on.

I will fix the widget to be consistent to the rest and make a consistent switch in a future veesion
[BetterBatteryStats] It_ler:
Oh I see [emoji9]

So it's not a wrong value.

And after thinking a while about it ... I like to see the awake time without the screen on time. That's the value I always try to minimize.

Will keep the responsive widget on my homescreen to get more used to it ... from time to time I have to get rid of old habits [emoji69]

Signature:

Device:

SGS5 (SM-G900F)

ROM:

AllianceROM v9.1

Kernel:

Stock XXU1BOE6 kernel

Recovery:

TWRP recovery by Ktoonsez

Modem:

XXU1POG1
[BetterBatteryStats] chamonix:
Well I am hesitant to keep it that way: as you correctly noted using the same term for two concepts is bad from a user point of view.

I was planning to revert the new widget back to 'legacy awake' for the time being and move all occurrences to 'new awake' consistently in 2.2
[BetterBatteryStats] Hedied4me:
I agree. This widget was perfect in RC1 and before.

Sent from my Virgin Mobile HTC Desire 601 zaraCL cdma
[BetterBatteryStats] chamonix:
and what is wrong with it in rc3?
[BetterBatteryStats] Hedied4me:
I havnt tried it yet, will do now. Wasn't trying to be a complainer. I love your product. I just preferred that widget in rc1 vs rc2.

Edit: RC3 widget looks nice. My only preference about Rc1 was that the text would show up when resized to a smaller widget. 2 and 3 the text only shows up when the widget is slightly larger. Ill just learn to deal with it. No biggie. Great product bud.

Sent from my Virgin Mobile HTC Desire 601 zaraCL cdma
[BetterBatteryStats] chamonix:
Thinking it through and looking at the code and at the paradigm of the new widget I think I will go the hard way and make everything consistent to the new paradigm that is "awake + screen off + deep sleep = 100% of the time". I took this approach because I felt it is more natural and it represents well on a pie/ring chart where the full circle is 100%.

Going away from this in the new widget breaks the representation (overlapping values) and I feel that the new paradigm is more natural.

There are more changes to do but I will take that step as there is nothing else to be prepared for Marshmallow.
[BetterBatteryStats] chamonix:
RC4 is up with a paradigm shift in the semantic of "awake". Previously that value included screen on time, now it does not anymore. Please test consistency.

Note: as the calculation/sematics changes all references needs to be re-created in order to get correct results
[BetterBatteryStats] meduza:
Thanks!

But what about full galaxy s6 support: http://xdaforums.com/showpost.php?p=63113969&postcount=29465 ?

m.
[BetterBatteryStats] Skar3:
Hi,

for me BBS after the first reboot the option "since unplugged" disappear, why? The app have root permissions and it's installed as System app, I have a Xiaomi mi4 with official CM 12.1

Thank you
[BetterBatteryStats] draxema:
Hi, I have an issue with my zopo zp999, my phone cannot go to sleep. Here's a bbs log file http://pastebin.com/0GKQcFjW

From what I see, it's the xhci kernel wake lock (which is related with the usb kernel driver I think?) and eint wakelock. I fixed the eint wakelock, it was Google play services. Although, I don't know how to fix the xhci wakelock, please note that I need to shut down my phone so it can charge, if I don't, it doesn't detect the power source. And one time, the xhci wakelock was not present (I do no know why.) and my phone was charging proprely. So how can I fix this? I re-flashed with sp flash tool but it didn't help. If any dev or anyone knows anything. Please help me. it's been a pain in the ass. If you need anymore info, I will be more than happy to provide it.
[BetterBatteryStats] chamonix:
because all references that were previously stored get deleted at boot. Please also see the FAQ in post #3
[BetterBatteryStats] chamonix:
The link does not work
[BetterBatteryStats] chamonix:
If you refer to the cpu stuff there is unfortunately not much I can do: BBS reads the frequency info from what the kernel stores (see cpustates.java in the androidcommon project on github. If samsung does not follow the Linux standards the only thing that would help is to get a hint from a kernel dev on how samsung documents the cpu time in state info
[BetterBatteryStats] meduza:
Yes, the cpu stuff. Thanks for the explanation!

m.
[BetterBatteryStats] code010101:
I like the new "paradigm" :good:

did you changed "strings.xml" accordingly?

Ste
[BetterBatteryStats] qwerty22:
What about Samsung Galaxy S5 (with Lollipop) support? Wakeups without Alarms (added debug info to logcat):

View attachment BetterBatteryStats-Wakeups_without_Alarms_3_Unplugged_to_Current.zip

View attachment BetterBatteryStats-Wakeups_without_Alarms_3_Boot_to_Current.zip

Dump from patched version (Wakeups with Alarms, added debug info to logcat):

View attachment BetterBatteryStats-Wakeups_with_Alarms_3.zip
[BetterBatteryStats] chamonix:
Yes but as I said, I count on you to test and report any inconsistency / required changes that I may have missed
[BetterBatteryStats] draxema:
Sorry, here's a pastebin link http://pastebin.com/0GKQcFjW
[BetterBatteryStats] chamonix:
a source to start: https://groups.google.com/forum/m/#!msg/android-x86/jmDsPzmamFU/VQO2x9_lRl4J

even if not related to android that seems like a kernel topic to me. Now I noticed that your reading was not idle (screen on time) so I would recommend to proceed by elimination:

- wifi was active

- you were active

- as always lots of wakeups caused by gms

I suggest to proceed by eliminating wifi from the equation by leaving it off to see if that wakelock is still triggered.
[BetterBatteryStats] efrainmartinez:
That's one of the best app to know wakelocks... And with that Knowles you can control draining battery and have a faster and fluid smartphone.
[BetterBatteryStats] code010101:
I find some difficulties in understand how to exactly get a particular configuration of the widget,

the philosophy seems to be: "just keep resizing until you get something you like" :D

but apart from that, sometimes all the info don't fit correctly into the widget itself (PWL, see attach)

from the graphical point of view, I love the pie graph, looks nice and it's easy to read,

it gives prompt and complete info about the power consumption.

Personally, the percentages are the only information I would in case add to the pie,

I found the hh:mm:ss digits useless, they mess up a little the widget readability, imho

if I need more details I just open the app ... but that a mater of taste, of course

Ste
[BetterBatteryStats] chamonix:
That IS indeed helpful. I was able to reproduce on Marshmallow final on my N5 with the stock launcher.

The logic for the auto-layout is:

(see also here: https://github.com/asksven/BetterBa...atterystats/services/UpdateWidgetService.java)

(height and width are expressed in cells)

if ((height <= 2) && (width <= 2))

show the widget without legend

else if (height < width)

show the widget with legend on the right

else

show the widget with legend below

Now it seems that the cell-sizes (the pixel to size ratio in non-linear, see here for more details) is either slightly different between launchers or has changed on M. I will leave my N6 on 5.1.1 and N5 on Marshmallow and do some testing now that we have a way to reproduce. At the same time I will look at either offering different font sizes for the legend or do some calculation to make sure it does not get cut off in the normal 2x3 or 3x2 situations.
[BetterBatteryStats] code010101:
I get the pie only, with 1x1 and 2x1 cells,

with 1x2, I get a very partial legend, below the pie

with 4x2, the pie is so big that the legend doesn't fit (likely because of showing both time + %)
[BetterBatteryStats] It_ler:
Now the awake time is nearly the same like in the legacy widget and inside the app itself:

Signature:

Device:

SGS5 (SM-G900F)

ROM:

AllianceROM v9.1

Kernel:

Stock XXU1BOE6 kernel

Recovery:

TWRP recovery by Ktoonsez

Modem:

XXU1POG1
[BetterBatteryStats] chamonix:
RC5 is up with more widget tuning.

[MENTION=4563466]gaich[/MENTION], [MENTION=5543250]mag01[/MENTION], [MENTION=4789833]vldesco[/MENTION], [MENTION=1026905]code010101[/MENTION], [MENTION=6126058]seky2205[/MENTION], [MENTION=3388754]xavihernandez[/MENTION], [MENTION=5735890]Minty123[/MENTION] : the changelog is already compacted and ready for release. Please update your translations. I am planing a release for a staged rollout in two days.
[BetterBatteryStats] :
Thanks for your great work and this fantastic app.

/deleted
[BetterBatteryStats] vldesco:
I will update spanish this night (I am GMT-5)
[BetterBatteryStats] It_ler:
I like the 2x2 sized widget (right widget) ... but in RC5 it's without the text on my phone:

If I resize it to 2x3 (left widget) the text is visible again ... but less space on my homescreen for other widgets.

I would prefer the 2x2 widget with the text like it was in RC4 on my phone ... just my 2 cents.

Signature:

Device:

SGS5 (SM-G900F)

ROM:

AllianceROM v9.1

Kernel:

Stock XXU1BOE6 kernel

Recovery:

TWRP recovery by Ktoonsez

Modem:

XXU1POG1
[BetterBatteryStats] IronTechmonkey:
Interesting, and thanks for the incidental comparison (out of official TYs today). Considering that I have a relatively low screen resolution of 540x960 and use maximum native font size of 130% I should count my blessings. Here are some doctored screen grabs that show the resize borders for comparison (so space occupied by the widget is not seen as free space on the screen). These are comparisons between default and the best resizing I can get - which still truncated certain items when the reported values are graphically longer (ie 100%) in the resized one that is longer vertically.

{EDIT} This /\ is in RC3. Repeating in RC5 Which requires the widget to be significantly larger to show text. Pics coming.

RC5 - To get text to display in "vertical" I must increase horizontal and vertical widget size each one notch (Nova Launcher - older version) compared to RC3 and RC4. There is not enough room on display to get text to appear in "horizontal" in RC5 on my device.

Now in RC4 where the widget sizing is the same as in RC3 (which is the only one that works well at my screen resolution and font size) an exceedingly minor additional note: Widget pie graph slightly off center to the left (as indicated by Pink Floyd and the CM clock). Like I said - exceedingly minor :). The ability to see text in the smallest graphic footprint is certainly more useful than absolutely perfect centering.

BTW [MENTION=1330150]chamonix[/MENTION] You are moving incredibly fast this week - wow!
[BetterBatteryStats] code010101:
I've updated both changelog and strings (revised) right now ;)
[BetterBatteryStats] chamonix:
Well, I am off from my day job this week so I can spend more time having fun :)

Thanks for the helpful feedback. I will experiment with margins for an accurate centering and will do some more work on trying to maximize the use of real estate. Expect yet another attempt today.
[BetterBatteryStats] jswclw:
I also spent some time messing around with resizing the responsive widget. It seems to work real well when it senses an horizontal layout is in order. However, when a vertical layout is sensed, it seems to reserve too much vertical space for the textual information. Consequently, the text doesn't even show until the vertical size is well past what is necessary to accommodate it. Then when the text is painted right under the graph, lots of empty space remains below the text.
[BetterBatteryStats] chamonix:
I have done some major changes regarding the layout and tested on N5 with Marshmallow:

- image is no centered

- refresh icon does not consume space anymore as overlayed on top of the round pie/ring chart

- better text length management for vertical layout

What is left is limiting the pie/ring chart to always grow to the whole width/height: better to leave space for text in e.g. 3x3. And some testing on different sizes and version/launchers: I have my N6 and Nexus S ready for testing later today.
[BetterBatteryStats] Reiteration:
Could you please analyse my log?

Could you please analyse my log? I'm seeing really high battery drain.

Dropbox[dot][com]: /s/s0732cbh3xj8web/BetterBatteryStats-2015-10-07_191857448.txt?dl=0
[BetterBatteryStats] chamonix:
RC6 is up with merged translations and some more trickery on the widget layout part. I tested on a Nexus S with 4.1.2, Nexus 6 with 5.1 and Nexus 5 with 6.0 and this is the best I can come up to that satisfies all specific densities:

- refresh icon overlaps with pie/rings to optimize margins and maximize real estate

- percentages get removed when space is too narrow to avoid "..."

- the pie/ring has a min. and max. size to avoid it to be too small / too large, to let enough space for text <-- there are some trickery with magic numbers here but it is still the best compromise

Hope you like the new optimizations!
[BetterBatteryStats] qwerty22:
Optimizations except Samsung Galaxy :(
[BetterBatteryStats] It_ler:
Here we go:

The responsive widget sized 1x3 looks good on my device (Samsung Galaxy ... S5 - still TouchWiz Android 5.0).

But the Aw time seems to be different to the Awake time of the lagacy widget and the app itself.

Can provide the dumpfile if needed.

Signature:

Device:

SGS5 (SM-G900F)

ROM:

AllianceROM v9.1

Kernel:

Stock XXU1BOE6 kernel

Recovery:

TWRP recovery by Ktoonsez

Modem:

XXU1POG1
[BetterBatteryStats] qwerty22:
Do you use custom or rooted offical firmware?

Upd.

Sorry for the question, in signing see that custom - Alliance ROM v9.1. My problem with Wakeups is present on the official firmware.
[BetterBatteryStats] IronTechmonkey:
This "still TouchWiz Android 5.0" might be an indication of stock although the status bar elements in the screen grabs do not look stock..
[BetterBatteryStats] IronTechmonkey:
Looks like a good compromise.across screen densities without compromising quality. On my 540x960 screen with max 130% font size; vertical now requires a taller footprint than before, fitting into grid 2 wide x 3.5 tall (rather than 2x3 for the previous version) but horizontal now crunches down to 2.5 wide x 1 tall (rather than 3x2 in the previous version one) which is quite nice on this device. Note: Older (good version;)) of Nova launcher allows widget resizing and half steps in resizing and item placement. A combo pic from RC6...
[BetterBatteryStats] FernBch:
I have a question for anyone who can help me identify a solution. I have the SCH-I545 and am currently running the JDC optimized CM12.1. Currently my device will not enter deep sleep and as a result battery life is not what it should be. There is a PowerManagerService.Wakelock on top of the list at 100%.

Here's a Logcat:

https://www.dropbox.com/s/xfncwfp0les7eem/Log_2015-10-06_18-07-06.txt?dl=0

And a BBS text dump:

https://www.dropbox.com/s/26a4fo5xs4e70fy/BetterBatteryStats-2015-10-06_180210196.txt?dl=0

Thanks in Advance.
[BetterBatteryStats] chamonix:
As you can see in the wakelock chapter here is what keeps your device awake:

com.avast.android.at_play (com.avast.android.at_play.Avast Anti-Theft): 9 h 8 m 8 s Count:0 75.6%
[BetterBatteryStats] Blade2014:
Respected Sir,

I am using Moto g 2014 XT1068 , SOKP ROM with AK kernel. In BBS I find this "starting dock service" partial wakelock and I am not able to identify the particular app. Also in kernel wakelock i find the "power management service". I These are keeping the phone awake during idle time. I have attached the screen shot and I request anyone to help me resolve this issue.

Thanks s regards

Santhosh. S
[BetterBatteryStats] j1gga84:
Since a few days I have a problem on my tablet (Android 5.0.2 Stock).

It does not go to deep sleep because of a wakelock of Android System called 'TimaService' as you can see in attached screenshot.

What can I do here to kill this wakelock? :confused:

Many thanks and regards
[BetterBatteryStats] FernBch:
Never even thought of that. Thanks!! I'll freeze it with TiBu for a day and see what happens. If it is actually my issue I'll contact them with a report. I have used that app for a long time and this has only showed up recently.
[BetterBatteryStats] mondohow:
If I remember correctly TimaService has to do with Samsung KNOX. It's been a while since I've seen it mentioned but I think there was some build.prop editing that stopped this wakelock. Not much but hopefully this points you in the right direction.
[BetterBatteryStats] boshuter:
I apologize if this has been answered, I tried searching the thread but didn't find what I needed.

I installed the app (downloaded from first post), installed it and got the "battery service could not be contacted" toast. I then downloaded the system app and flashed it in recovery, rebooted and reinstalled the .apk and still have the "battery service could not be contacted. I'm using a Galaxy S5, rooted, and running resurection remix rom, android 5.1.1

Any help getting this to work is appreciated :confused:
[BetterBatteryStats] adm1jtg:
I am getting same issue after trying to re-install it on cm 12.1 latest snapshot aka with the new google security fixes. I even bought it fro playstore and still no luck.
[BetterBatteryStats] shaggyskunk:
I'm not having any issues with RC6 - I initially installed the previous RC versions by copying to System Priv-App and fix Permissions - Subsequent RC versions I just installed the apk - Granted Root - Done

AOSP 5.1.1

Sent From my SM-N910W8 Running SlimRemix V5.1
[BetterBatteryStats] IronTechmonkey:
Those new fixes should be in my next ROM test of CM12.1 10/8 or 10/9 nightly (no snapshot for my device). Will check this out in a couple of days.BTW In another forum I saw conversation about whether or not those fixes actually made it into the snapshot, although the notes at CM's blog imply such. Typically CM folds into the snapshot important commits that were created after the snapshot features were frozen but before it is released and this gap seems to have shrunk this year but do you have any confirmation that those patches are in the snapshot?
[BetterBatteryStats] adm1jtg:
I cannot make it install no matter what and have been using the program for years. I am pretty sure the new google updates for security broke something and the dev will have to update.

---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------

Was told in the cm irc channel that the snapshop was MOSTLY these new security updates and that was the only reason they released a snapshot. Have not looked in gerrit or whatever to comfirm and i think the patches were introduced into the nightlies om the 5th or 6th
[BetterBatteryStats] Jake2kOne:
This helped a lot! Thank you.

-> LG G3 32GB @ CM12.1
[BetterBatteryStats] chamonix:
What fixes are you talking about and how do they affect the security model, ie bbs.

Does bbs get the required permissions granted? you can check this from the advanced settings under system app.
[BetterBatteryStats] IronTechmonkey:
It think it is google's monthly security patches being folded into CM; in a more organized and transparent workflow than was used in the past. Mentioned here at the CM blog http://www.cyanogenmod.org/blog which has a link to details of the update which are here: https://groups.google.com/forum/#!topic/android-security-updates/iv1BF0f0XY4. I do see some elevated privilege issues to fundamental components but don't understand their ramifications. As to testing; a significant power management commit (http://review.cyanogenmod.org/#/c/110704/) was added to my device just after the 10/8 nightly containing the google security patches so I'm going to wait until that one is also in before testing. Assuming the CM buildbots keep chugging I should be able to do so within 24-48 hours. Presently in RC6 in a week old CM12.1 nightly BBS has been granted both BATTERY_STATS and DUMP with SElinux set to enforcing (although post boot I often use a command to set SElinux to permissive to keep LMT Pie happy).

EDIT - LOL Usually I migrate completely to a new nightly each week but I'm already getting antsy to know about this potential issue and might test later tonight in a throwaway ROM install. No promises though. :)

---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------

Sounds similar to what I read, and looks like they made it into the 10/8/15 nightly for my device.