yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] Perseus:
Typically When posting a log here, we prefer that you post a Idle Log as in when phone was not being used. During current log period you were using the phone for at least 15 minutes, this skews the drain pattern and makes it difficult to analyze.

From what I do see, you used the Browser and Facebook for some time and they used internet for some time. This caused a larger drain than expected. This is what in use means.

To answer your question, any Wakelock involving HSIC typically indicates sporadic or bad Signal to the tower. This is cuased by a variety of reasons including but not limited to poor coverage. Most commonly this is resolved by toggling Airplane Mode briefly once you reach home or Work/school.
[BetterBatteryStats] sithjedi333:
Thank you for the feedback. I will try that trick which I haven't seen before and work on an idle log. I really appreciate it.
[BetterBatteryStats] chamonix:
I wanted to wait for the final factory image of nougat for my n6p but as these seem to have been delayed I will have a look at it this week on the preview.
[BetterBatteryStats] samuraix21:
Sorry for the masssive delay but it turned out it was Gasbuddy all along. If you put it in Greenify, it should be fine.
[BetterBatteryStats] chamonix:
Unfortunately the logs did not show the sensor stats that I had added for helping decoding them. I have added some more logging that may help to throw some light into how to interpret (and how not) the value.

Now since we are here let me explain where the stats come from; there is the code for those who like java: http://grepcode.com/file/repository...eryStatsImpl.java#BatteryStatsImpl.Uid.Sensor

The way stats are compiled internally is hierarchical: by UID a timer cumulates the time the UID (decodes to either a userland process or to a package==apk) has been using the sensor. Now this mean that (as for other UID-related stats like partial wakelocks) sensor usage can overlap, leading the total to possibly larger than the total time.

Here is a (decoded, I added that to the current RC2) example from my logcat:

-04 18:43:51.960 14551 20096 I BBS.Sensors: UID=1000, Sensor=GPS (-10000) , time=0 s (65000)
09-04 18:43:51.960 14551 20096 I BBS.Sensors: UID=1000, Sensor=Accelerometer (1) , time=2 s (2716000)
09-04 18:43:51.960 14551 20096 I BBS.Sensors: UID=1000, Sensor=Temperature (7) , time=2 h 11 m 46 s (7906185000)
09-04 18:43:51.960 14551 20096 I BBS.Sensors: UID=1000, Sensor=Relative Humidity (12) , time=32 m 31 s (1951396000)
09-04 18:43:51.960 14551 20096 I BBS.Sensors: UID=1000, Sensor=Unknown (31) , time=2 h 12 m 35 s (7955268000)
09-04 18:43:51.960 14551 20096 I BBS.Sensors: UID=1021, Sensor=Accelerometer (1) , time=19 m 9 s (1149996500)
09-04 18:43:51.961 14551 20096 I BBS.Sensors: UID=1021, Sensor=Unknown (26) , time=19 m 11 s (1151350000)
09-04 18:43:51.961 14551 20096 I BBS.Sensors: UID=10017, Sensor=Accelerometer (1) , time=2 m 13 s (133759500)
09-04 18:43:51.961 14551 20096 I BBS.Sensors: UID=10017, Sensor=Relative Humidity (12) , time=50 m 42 s (3042775000)
09-04 18:43:51.961 14551 20096 I BBS.Sensors: UID=10017, Sensor=Significatnt Motion (17) , time=1 m 15 s (75884000)
09-04 18:43:51.962 14551 20096 I BBS.Sensors: UID=10033, Sensor=Pressure (6) , time=30 s (30733000)
09-04 18:43:51.964 14551 20096 I BBS.Sensors: UID=10155, Sensor=GPS (-10000) , time=1 h 4 m 22 s (3862300000)
09-04 18:43:51.964 14551 20096 I BBS.Sensors: UID=10155, Sensor=Gyroscope (4) , time=2 h 9 m 28 s (7768581000)

Where you can clearly see that e.g. the accelerometer has been used by UID 1000 as well as 1021 and 10017.

Now that leaves me to think that "Summary" is not the right place to put sensor stats: the cumulative figure is not consistent to the total time and even if I provide a popup to see the details (as above) there is still some hackery to be done for the user to find the package that used the sensor.

As a result I will have to revise the approach and add sensors as a stat type (as wakelocks etc.) in order to be able to decode the package names, show the app icons etc.

I will release RC2 once I'm done :cool:
[BetterBatteryStats] chamonix:
RC2 is up with more comprehensive sensor stats (see my previous post for the why and how)
[BetterBatteryStats] chamonix:
I am planning to provide public beta for selected (if not all RCs) on google play. This goes back to my thoughts of working towards becoming more agile again, in the way I deliver BBS for a substantial number of 200K+ users on gplay and 100K+ on xda (those figures blow me away!).

Of course I stick to my word and will not stop providing all betas and RCs on xda as well so I'd be interested in how you guys see it:

1. would you rather prefer to join the public beta and avoid actively looking for updates here?

2. should I announce RCs going to google play here or separate that (stay with the way I announce version here and use twitter for "public" stuff?

3. should I drive the traffic for feedback from google play back here or do you prefer to me taking care of traffic/questions from google play by mail?

4. does a separate xda version still make sense or would you prefer me to use a closed alpha channel and a public beta channel from google play to distribute all binaries.

4. would assume you guys have all bought the version from google play anyway and would prefer to get notified of updates instead of coming here to look for new bits. I am really hesitant on making this change as:

- BBS is and will stay free on xda

- I don't want to force anyone to buy the app if he doesn't like it

- I am happy and proud of having such a vibrant community and don't want to fix something that doesn't need fixing.

Please let me know what you guys think as I one the one side don't want to stick to old habbits just because it's the way I always did things, but on the other hand I don't want to make your life more difficult/cumbersome.

In other words: I don't want to change a working model but am always happy to improve and make your life easier ;)
[BetterBatteryStats] kmarc33:
1) I know less than zip about it but the new XDA app keeps talking about distributing apps through XDA. Have you looked at that?

2) I use both Play and XDA, I'll see it eventually

3) whatever is easier for you but mail is generally bad for this since the community here in the forum is a strength.

4) whatever is easier for you. If you're doubling your admin workload to take care of parallel versions then that's time away from support/code.

IMO <shrug>

thanks for asking. That's what keeps us here... ;)
[BetterBatteryStats] swallowingled:
The XDA Labs app works really well for updating apps. I bought the play store version some time ago but follow this thread and use the XDA version. Downloading from this thread works as well.
[BetterBatteryStats] guhvanoh:
1. I come here to XDA everyday so I vote here.

2. I would go for a third option and say both here and Twitter. Some folks here may want to know about those releases even though they get their release here. Plus you'd be spreading the knowledge...

3. Tough one. The real question is what suits you best and enables you to do your thing effectively. It is possible that forum members can help with support questions, however bear in mind that we are sometimes harsh in our answers.

4. I would prefer coming here for updates. That way I don't get nagged by Play.
[BetterBatteryStats] Haldi4803:
This Sensor Tab, does it need any Special Love to Show anything?

On my HTC 10 it Looks empty.

I already had Problems showing Kernel Waklocks, but this helped here....

mntP=$(grep /sys/kernel/debug /proc/mounts | awk '{print $2}')
if [[ "${mntP}" != "/sys/kernel/debug" ]]
then
mount -t debugfs none /sys/kernel/debug
fi

http://cloud.tapatalk.com/s/57cd46f9c8ec7/BetterBatteryStats-2016-09-05_121933260.txt

http://cloud.tapatalk.com/s/57cd4706a9f87/dmesg-2016-09-05_121933710.txt

http://cloud.tapatalk.com/s/57cd470cb8718/logcat-2016-09-05_121933571.txt

P.S does that work for logs?

Advanced log activated in Settings.

In case of nope, heres a full system log:

http://cloud.tapatalk.com/s/57cd473694313/2016-09-05_12.18.zip
[BetterBatteryStats] Javi22:
For me it shows 3h of sensor: relative humidity

Is that normal??

Enviado desde mi Nexus 5X mediante Tapatalk
[BetterBatteryStats] chamonix:
The source reference needs to get populated with sensor data so make sure to plug/unplug your device after installing 2.2. You can also check raw sensor stats as those will always show data if there are any sensor stats that have been collected by android
[BetterBatteryStats] mmm286:
Hi,

I have a Chinese tablet (Chuwi Brand) and I see a lot of consumption when the tablet is locked:

11.46 am -> 80%

00.16 pm -> 63%

It seems that system process is consuming a lot. Could you help me please?

Thanks and sorry for my English!
[BetterBatteryStats] Portgas D. Ace:
You have some kernel wakelocks. Check this thread for a possible solution.

Furthermore:

Alarms: 305, Intent: com.quoord.tapatalkpro.activity/com.cuebiq.cuebiqsdk.model.Collector -> Tapatalk is quite active

Alarms: 151, Intent: nextapp.systempanel.action.MONITOR_UPDATE -> SystemPanel Task Manager is also quite active (I don't know why people use stuff like this on Android at all, it's not required and drains a lot of battery)

Alarms: 17, Intent: CONTEXT_MANAGER_ALARM_WAKEUP_120262 -> you can use Amplify and especially its regex blocking function to limit this

Beside this, some apps like Gmail are downloading some data (around 1MB).

I would suggest to head over to one of the two battery threads, you might get help in reducing your battery drain there.

http://xdaforums.com/android/general/guide-0-0-hour-idle-battery-drain-stock-t2973588

http://xdaforums.com/android/general/guide-extreme-battery-life-t3095884
[BetterBatteryStats] mmm286:
Many thanks!

I see a lot use of system progress. That's normal? Is possible to identify why?

Thanks and sorry for my English

Enviado desde mi SM-G930F mediante Tapatalk
[BetterBatteryStats] Portgas D. Ace:
It is okay that Android System is active during idle time. I would suggest to start according to one of the above linked threads and limit everything according to the recommendations. Afterwards, produce another idle log file and post it in one of the two threads (which one is up to you). If Android System is still active, ask for help there.
[BetterBatteryStats] chamonix:
Big news guys:

1. I found a bug in the way the sensor names were decoded. It took some hackery but now the names are correct.

2. A goodie for all of you with API >= 21: sensors stats now contain info about whether the sensor is causing wakeups (https://developer.android.com/reference/android/hardware/Sensor.html#isWakeUpSensor()) -> this is important info in order to fully interpret sensor stats

3. 2.2RC3 is up with all these enhancements

4. 2.2RC3 is also in the beta ring on google play (public beta). Here's the link: https://play.google.com/apps/testing/com.asksven.betterbatterystats

Please note that the link was not made public yet and that the support URL on gplay points to this thread. If the thread is disrupted by taking this more public approach I may change that. For the sakes of keeping the possible negative side effect to a minimum I kindly ask you not to share the public beta URL yet.

Enjoy!

[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]

I have compacted the changelog in preparation for the final release so please start updating your resource files
[BetterBatteryStats] TNSMANI:
Thank you for this.

Does BBS now report sensor data in the Sensor tab? In RC2, the sensor data is available only in the Raw Stats and not in the Sensor tab which is blank.

Additionally, I am not getting the Doze times except Doze Interactive Time in RC2. In my ROM which is Nougat for N4 by Zaclimon, the Doze flag was not enabled initially but now in V5, it is enabled. Greenify notification now reports Doze times but BBS doesn't, not even in Raw Stats. Is there something that I can do to address the issues?

Selinux is enforcing, if that is of any relevance.
[BetterBatteryStats] killerm:
In my case, RC3 perfectly shows sensor data in sensor tab and "doze idling" and "doze idle mode" times (apparently identical?), but still on S6/MM.
[BetterBatteryStats] TNSMANI:
Thank you. In RC3 also, I have the same issues. I have tried selinux permissive also but no change.
[BetterBatteryStats] mag01:
[MENTION=1330150]chamonix[/MENTION]

While updating the translations I noticed that as the TXT & JSON dump files were merged, these strings (strings.xml) should be perhaps merged as well - or not?

<string name="message_hint_savestat">Save a Text Dumpfile</string>
<string name="message_hint_savestatjson">Save a JSON Dumpfile</string>
[BetterBatteryStats] Plonkplonk:
RC3 does not work properly for me (while RC1 does). Instead of the summary it shows "There weren't any statistics collected yet." I rebooted after installing BBS and let my alone the whole night.

(Using a rooted FirePhone with CM11)

Thomas
[BetterBatteryStats] gvp9000:
Same here with RC3 "There weren't any statistics collected yet." Note 3 android 4.3 no root. RC1 works fine.
[BetterBatteryStats] TNSMANI:
After a couple of reboots in RC3, sensor data is displayed properly under the Sensor tab.

But Doze times are still not reported. I have tried a data and cache wipe for the app, still no dice.
[BetterBatteryStats] raptorddd:
what should i hibernate.?? screenshots here.? http://xdaforums.com/showpost.php?p=68605870&postcount=6

whats best purify-greenify or servicely.?
[BetterBatteryStats] :
[MENTION=1330150]chamonix[/MENTION]

Just wanted to thank you because your app and Google search helped me hunting down the worst battery hogs and as an addition helped me to identify an app that caused a serious performance Impact.

Thanks again for providing free XDA Edition. Bought ProVersion right now.
[BetterBatteryStats] fire2blade:
Tnx

Send from my Redmi Note 3 - kenzo
[BetterBatteryStats] onolox:
Delete.
[BetterBatteryStats] chamonix:
This is not a bug report. Please consult post #1
[BetterBatteryStats] jr67:
Using RC3 whenever I pull a dumpfile following the Reference Overview section I always get something that looks like this:

------ human readable part end here

*/

{

"alarmStats": [

{

"details": "",

"items": [

{

"number": 4,

"intent": "com.google.android.location.ALARM_WAKEUP_LOCATOR"

},

{

"number": 0,

"intent": "com.google.android.gms.location.fused.SEND_LOCATION_IN_SMD_MODE"

This raw code actually makes up most of the dumpfile which makes for very large dumpfiles.

Please let me know if there is anything else you need from me.
[BetterBatteryStats] code010101:
[MENTION=1330150]chamonix[/MENTION]

I'm sorry, I'll be back from holidays the next Sunday (18 Sept). On Monday, I'll manage to do my job(!)

Ste
[BetterBatteryStats] chamonix:
This is in fact a feature introduced to make any dumpfile human readable (first part) as well as machine readable. It the size really a concern?
[BetterBatteryStats] jr67:
Thanks for the reply. No it's not really a problem. It's just that I have a Tasker Task that I use to save then pull some information from a dumpfile and display it on my live wallpaper and I was wondering why the task was failing especially if the dumpfile covered a long period of time. Instead of reading the entire dumpfile into a variable I'll just have to go back to selectively reading only certain lines into the variable.
[BetterBatteryStats] chhapil:
Enabling Non-root mode

Hi, I'm just reporting what i did to make sure non-root mode working on my Xiaomi Mi5.

I followed the guide in post #4 to grant the permission to read "android.permission.BATTERY_STATS" to bbs, waited for an hour at least to get the stats working but it didn't work for me.

So I went ahead and found all the permissions bbs needs

adb shell dumpsys package com.asksven.betterbatterystats_xdaedition

and granted all of them via adb except superuser, granting su access would anyways fail.

adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.BATTERY_STATS
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.DUMP
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.WRITE_EXTERNAL_STORAGE
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.ACCESS_WIFI_STATE
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.ACCESS_NETWORK_STATE
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.RECEIVE_BOOT_COMPLETED
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.READ_PHONE_STATE
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.DEVICE_POWER
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.GET_TASKS
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.BLUETOOTH
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.WAKE_LOCK
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.READ_LOGS
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.READ_EXTERNAL_STORAGE

Viola! BBS is showing all the stats now.

Thanks very much for the guide
[BetterBatteryStats] chamonix:
I added the link to the public beta in post #2 as well as on twitter. Please let me know if these announcements cause any disruption to our thread.
[BetterBatteryStats] gvp9000:
v2.2.0.0RC3 "no stats have been collected yet!" message.

Any stat combination of summary, kernel and sensors gives the same message.

I uninstalled and reinstalled the app .... same result.

At raw stats I have the error "An unknown error occurred while retrieving stats. Please check your logcat"

Samsung Galaxy Note3, NoRoot, android 4.3.

Attached the logcat with debug enabled.

-------------------------------------------------------------

-------------------------------------------------------------

-------------------------------------------------------------
[BetterBatteryStats] M@31:
Im trying to figure out if I need to worry about anything with my phone....

Deep sleep percentage - 94%

Time the phone was sitting - 10 hours 38 minutes

Percentage battery drained - 14%

It seems to drain fairly fast, but Im not too sure.

I want to post the wakelocks, but I really do not know how.

I was on wifi and autosync is set for Google gmail only......

I dont know why my phone would need to drain 14% of the battery if it was in deep sleep for 94%.......

Any help or tips on how to get the wakelock dump (if needed) up would be greatly appreciated

I have BBS, but I am trying to figure out how to get/post my wakelock data....

Im trying to figure out this ADB thing, but it is proving to be difficult.

Is there any easier way to get my wakelock data?

I just wanted to post the .zip files here so someone could give them a looksy.

I have been trying to get the adb working, and thought I had it, but when I open the .txt file for the wakelock, it says

/proc/wakelocks: permission denied

Thanks so much for the reply!

EDIT - since I have been trying to get adb working, I have had my phone plugged in and such, so not really a good reading.

I will have to test again tonight possibly, to get a good reading. clear my cpu spy times and get a full charge maybe....

Thanks in advance of course!
[BetterBatteryStats] longfeng:
10 hrs for 14%, it is quite good for routine use.

nothing to rant about. some cannot even last for 8 hrs.
[BetterBatteryStats] Steven6489:
Hi all,

Interested to know why my alarm manager count so high..I believe this is the problem why my battery drain so fast..
[BetterBatteryStats] longfeng:
simple, just check which apps are using the alarm. they are the ones.
[BetterBatteryStats] M@31:
Not routine use.

I was sleeping and the screen was off the whole time......
[BetterBatteryStats] Steven6489:
Thanks for your reply..however, how can I check which apps is using it?
[BetterBatteryStats] kishancito:
Hi all, i have a similar problem, eith alarm manager and activitymanager-sleep, can you give some advice please?

Thank you very much in advance!
[BetterBatteryStats] chamonix:
How about you post a dump together with your thoughts after studying it?
[BetterBatteryStats] chamonix:
From bbs go to the 'more' menu, create a dump and retrieve it from /sdcard. If you want to use adb for that: adb pull /sdcard/BetterBatteryStats<timestamp>
[BetterBatteryStats] chamonix:
If you are rooted use the alarm view from the 'more' menu
[BetterBatteryStats] M@31:
Finally!

Thanks Chamonix,

I feel stupid, but I tried to find the the file form my sdcard.....

I created the dump but still cant seem to find where it saved too....

Im sorry dude

EDIT - think if found it!!!!
[BetterBatteryStats] M@31:
Deep Sleep - 93%

Resting time - 8 hours 8 minutes

Percentage Drained - 11%

Of course, it is not as bad as some are seeing, but there are times when my phone wakes up during the night and just want to find out what it is.....

Even while I slept, it says that my phone went up to the 1300mhz level for 3 or 4 minutes.....

Thank you soooo much!

EDIT - I am not too sure what there is vbus_present wake there....when I check kernel wakelocks/since custom.....it shows 20 mins, but the phone hasn't been plugged in since I set the custom ref.
[BetterBatteryStats] ManUtd07:
I think I am still having trouble getting a complete dump. I have BBS to start on "since unplugged" and "partial wakelocks" when I open it up. After starting BBS, I let it sit for a minute to make sure that it populates and lists out all the activities before I create the dump. Am I doing something wrong as I am noticing that nothing is under "wakelocks" in the dump file?
[BetterBatteryStats] longfeng:
You are in deep sleep but are your phone in deep sleep?

Sent from my GT-I9003
[BetterBatteryStats] longfeng:
Do you have the graphs?

Sent from my GT-I9003
[BetterBatteryStats] longfeng:
You get nothing after you plug out from the charger. Just wait.

Sent from my GT-I9003
[BetterBatteryStats] M@31:
Longfeng,

Who are you replying to?
[BetterBatteryStats] longfeng:
To you. :)

Sent from my GT-I9003
[BetterBatteryStats] M@31:
So,

I charged the phone to full. I unplugged it, rebooted, and reset the CPU spy timers.

Left it over night while I slept (over 8 hours).

In those 8 hours, my phone was just sitting there.

It is only in deep sleep for 94% (not bad, but Ive heard better).

My phone was running at 1.3ghz for 3-4 mins while it wasn't being used. That shouldn't happen.

Also, the vbus_present shouldn't show 20 minutes, but it does....the phone was unplugged the hole time and if I read correctly, vbus_present is for when the phone is being charged, which it wasnt.

I do not understand what you mean "You get nothing after you plug out from the charger" sorry.

Where can I get the graphs from?
[BetterBatteryStats] longfeng:
Touch or Press the 21 hrs (top) 2nd chart.
[BetterBatteryStats] rdobbert:
I'm having the same issue.

Samsung Note7, NoRoot, Android 6.0.1
[BetterBatteryStats] a1exus:
I barely used my phone today, yet 2/3 of battery is gone and it's only 3pm..

any suggestions?
[BetterBatteryStats] chamonix:
Have you followed the instructions from post #4 for unrooted phones?
[BetterBatteryStats] rdobbert:
Yes, sir.

"adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.BATTERY_STATS".

It's worked up until the latest RC. I'm back on 2.1.0.0 and it's working again for other and partial wakelocks, but not alarms.
[BetterBatteryStats] chamonix:
well that does not help at all. why do you report without the possibility to provide logs?
[BetterBatteryStats] gvp9000:
[MENTION=1330150]chamonix[/MENTION]

My log helped you at all?

Thanks for all your effords.