yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] chamonix:
oops, I'll remove that one. It saves a "since unplugged" reference. I added it to debug the reference processing as unplugging disconnects the debugger. Just ignore.

Edit: https://github.com/asksven/BetterBatteryStats/issues/240
[BetterBatteryStats] chamonix:
Could you please provide a logcat of the fc?
[BetterBatteryStats] M.A.K:
Here you go...
[BetterBatteryStats] vasilisf7:
Why dont i get any reading on the kernel waekclok since unplug
[BetterBatteryStats] chamonix:
Have you plugged/unplugged since boot?
[BetterBatteryStats] vasilisf7:
Yes
[BetterBatteryStats] chamonix:
Got it: java.lang.UnsupportedOperationException: Attempt to add a sub-menu to a sub-menu.

What Android version are you on? Seems that nested menus are not always supported. I am charging my Desire to test :)
[BetterBatteryStats] M.A.K:
Android V2.3.6.
[BetterBatteryStats] chamonix:
No or unknown signal does not equal drain, it's just a state. I'd suggest that you start reading the how-to in post #3 and proceed systematically
[BetterBatteryStats] chamonix:
Ok, thanks. I will test on 2.2 as I don't have a 2.3 device at hands right now. The problem obviously comes from the reorg I made in the menu (moved "order by" to the "more" menu -> "more" is now nested

https://github.com/asksven/BetterBatteryStats/issues/241
[BetterBatteryStats] chamonix:
In that case please post a dumpfile and logcat
[BetterBatteryStats] vasilisf7:
Omega v13 & Motomoto00 theme
[BetterBatteryStats] chamonix:
That's the ROM, I need a logcat and a dumpfile
[BetterBatteryStats] vasilisf7:
I dont know how....

Omega v13 & Motomoto00 theme
[BetterBatteryStats] flute:
Nobody can help?

Thanks

Inviato dal mio GT-I9100 usando Tapatalk
[BetterBatteryStats] chamonix:
Release 1.10b2

New beta with a few fixes is up.
[BetterBatteryStats] chamonix:
Audio_out is normally related to sounds / haptic feedback. How do you conclude that this is what drains your battery. Please provide more context (a dumpfile)
[BetterBatteryStats] chamonix:
https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNEs6_WKhIMraLzv3eSMFBUSDF1a6Q

Dumpfle: menu - dump to file and attach /sdcard/BetterBatteryStats-<timestamp>
[BetterBatteryStats] Kurre:
IIRC, audio_out is just a some kind of workaround in a cyanogenmod based roms. Earlier versions without this wakelock (which is held if the phone is awake) caused something of problems (maybe audio stutter or something like that?)

Usually user can get rid of this by disabling touch tones from the settings. Then only audio from games/music player will trigger this, but not the system (obviously).

But to make it short, it doesn't affect your batterylife..just like chamonix suspected. It's been awhile since I have read about this issue, so details could be slightly incorrect. :rolleyes:
[BetterBatteryStats] alexinna:
Please read post #1 on how do generate correct dump. Phone needs to be idle.

According to attached file these two processes:

javax.microedition.ims (): Wakeups: 1524
org.gpo.greenpower2 (): Wakeups: 443

and also Facebook, Groupon, map/location services are causing many wakelocks.

You need to review refresh interval and change it. Read post #3 on how to deal with location services.
[BetterBatteryStats] M.A.K:
Beta2 fixes the menu issue so I can now confirm that my dump files are still empty as in 1.9.*.

On starting BBS I get 'fallback to "since boot"' but the reference time is actually since unplugged.

None of the references work for either the 'other' or 'kernel wakelocks' stat's; They all say no ref' since their respective condition.

All references work for 'partial wakelocks' but have the same 'since...' time. Even 'custom' which hasn't been set.
[BetterBatteryStats] vasilisf7:
I have exactly the same problem...

Omega v13 & Motomoto00 theme
[BetterBatteryStats] alexinna:
Testing for 1.10b2

Some of the values are negative and as the result not showing when filtering "0" values:

Deep Sleep (): (-562190 s) Ratio: -49574.7%
Awake (): (-142 s) Ratio: -9.8%
Screen On (): (-188 s) Ratio: -12.9%

I did plug/unplug charger few times but it's not fixing the problem.

Also log shows that reference has been created.
[BetterBatteryStats] M.A.K:
I've found I can create a dumpfile by disabling the 'CPU States' in the dump pref's. It works with everything else enabled just cpu states breaks it.
[BetterBatteryStats] chamonix:
Could you provide a logcat? I can't reproduce on jb

Edit: auto correction sucks :)
[BetterBatteryStats] M.A.K:
Ok, this is a logcat after a failed dump with 'cpu states' enabled. This is what you wanted... right?
[BetterBatteryStats] sweeds:
I am interested in purchasing and utilizing this apps, however many reviews state it constantly requires permissions when running JB. Is this stable to use?

Sent from my CM10 KF w/ Tapatalk
[BetterBatteryStats] alexinna:
Yes it's rock stable. Majority of permission related issues because of a SuperUser 3.2.

Read more here

Give it a shot and like many of us you will soon thank you chamonix for this outstanding app and his excellent support.
[BetterBatteryStats] sewe:
I don't see deepsleep any more

Skickat från min GT-I9300 via Tapatalk 2
[BetterBatteryStats] Ozzie Sandoval:
I have attached my Dump.

I see it has something to do with magazine or maps, still not sure how or why.

If someone would help me I will be sure to buy it off the play store or make a donation to help chamonix.

Thank you.
[BetterBatteryStats] Karpfenhai:
@Sven, new version looks great on my phone, like the new menu button and the root features, great idea!

Can't find an issue, greets from Denmark, where they have working mobile networks!

Tapatalked from my Samsung GT9100

---------- Post added at 11:20 PM ---------- Previous post was at 11:17 PM ----------

Hey there, first, dump is incorrect, read #3 for this.

Second, sign out all location based services, this keeps your phone awake!

Third, tell maps to behave, read the faq how to do so.

Last, good luck!

Tapatalked from my Samsung GT9100

---------- Post added at 11:23 PM ---------- Previous post was at 11:20 PM ----------

Did you plug/unplug your phone after upgrading?

For me a reboot brought deepsleep back.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] :
Try disabling Google Now.

Sent from my MB860 on MROM
[BetterBatteryStats] itsLYNDZ:
How do I do that? Isn't that what the phone runs off

---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------

In don't have google now app.....
[BetterBatteryStats] :
Google Now wants to know your location at all times to display traffic info, weather, flights, etc. It is very power hungry. I believe Google Now app is the Google Search apk, not 100% sure.

Sent from my MB860 on MROM
[BetterBatteryStats] itsLYNDZ:
I don't have that app....
[BetterBatteryStats] :
Sorry, I didn't know your device was not rooted. Disregard what I said...

Sent from my MB860 on MROM
[BetterBatteryStats] itsLYNDZ:
It is rooted... and I can't freeze google search, that's a basic function.. I don't understand, my battery drain was never this bad to the point I have to constantly carry around my charger. Even bad when its just sitting there for hours untouched
[BetterBatteryStats] :
That's my suggestion. I'm sure someone has a better solution to your problem. I am sharing what worked for me.

Sent from my MB860 on MROM
[BetterBatteryStats] alexinna:
You can disable magazines refresh in your google account sync settings but dump file shows only 2 times in 8+h

As explained above location services/map is you biggest enemy for now.

It could be result of Google Now. You can try to disable it.
[BetterBatteryStats] vikasb32:
Kernel wakelocks dosn't show in latest version.
[BetterBatteryStats] Karpfenhai:
Not true! :D

Tapatalked from my Samsung GT9100
[BetterBatteryStats] stuart0001:
I think it's rom dependent. I get them on stock but not on custom roms
[BetterBatteryStats] M.A.K:
I've been thinking...

For me, the app currently reports the 'no reference...' for both 'other' and 'kernel wakelocks' but it does show a 'since <time>' so it is at least seeing a reference timeframe...

So, putting aside the problems with selecting the required timeframe, why doesn't the app show the stat's for the timeframe that it does see?
[BetterBatteryStats] itchn2go:
1.10.0b2 does not show any stats.

1.9.2.1shows the stats but very limited. I cannot set a custom reference but since unplugged and charged seem to work fine. Something major changed in 1.10.0b2.

Here is the ROM I am running http://xdaforums.com/showthread.php?t=1780275

If you have a Rezound I highly recommend it. (battery seems great on this ROM - I have only been using it a short time).
[BetterBatteryStats] honest1212:
I am facing wake up issue and the device wake up time is almost double the time of screen on time. I have disabled location service mentioned in the post no 3 and here is the log:

http://pastebin.com/0imBuGMp

I have to enable the location service as Google now does not work without it and here is the log:

http://pastebin.com/eVFt40nv

Please help me to find out what is keeping my phone awake...
[BetterBatteryStats] Stileth:
Guys, what you think about this? Seems in 4 hours while the phone was doing nothing it had never entered deep sleep! I have included screenshots and dump file.

Thx for checking.
[BetterBatteryStats] alexinna:
Both dump files shows the following wakelocks:

"modem_usb_gpio_wake" (): 5 m 15 s (315 s) Cnt:(c/wc/ec)383/14/383 3.2%
"modem_usb_suspend_block" (): 3 m 30 s (210 s) Cnt:(c/wc/ec)418/0/0 2.2%
"musb_autosuspend_wake_lock" (): 51 s (51 s) Cnt:(c/wc/ec)381/247/0 0.5%

It usually happens when you are using Wi-Fi and download something with screen off. But the strange thing I don't see that you are on a Wi-Fi.

Try to find out the source of these and you should be able to improve awake situation.
[BetterBatteryStats] honest1212:
Correct, my wifi is off during the whole time. Can you guide a little bit how to find more about these wakelocks as I didnt find anything material on google.

Does it happen because I have enabled auto update on google play?
[BetterBatteryStats] alexinna:
I would if I know but I don't have personal experience with above locks so google is the only source for me as well.

But if I will be in such situation I would try:

Put phone in a airplane mode and check for these locks.

Re-install stock Rom and check how it works.
[BetterBatteryStats] honest1212:
Will try both above and report back. Anyways there are few users who are having the same problem. Posted there and lets see.

Thanks :)
[BetterBatteryStats] alexinna:
You didn't have any data or Wi-Fi connection and below processes tried to sync your phone:

*backup* (Systém Android): 3 h 49 m 47 s (13787 s) Count:56 93,1%
SugarSync_AndroidApp (com.sharpcast.sugarsync.SugarSync): 16 m (960 s) Count:4 6,5%
com.bluestacks.appsyncer (): Wakeups: 49

You can disable them and try again.

Also location services/maps are waking up your phone. Post #3 explains how to deal with this.
[BetterBatteryStats] chamonix:
https://github.com/asksven/BetterBatteryStats/issues/243
[BetterBatteryStats] chamonix:
I LOLed.

Seriously: http://xdaforums.com/showthread.php?t=1292625
[BetterBatteryStats] chamonix:
Release 1.10b3

is up....
[BetterBatteryStats] chamonix:
I found a possible reason for references to get lost..... in the migration routine pre-1.9 :)

I am cleaning that up and will update b4 soon.
[BetterBatteryStats] chamonix:
Release 1.10b4

Release is up. I need your feedback specifically on:

- does the workaround for SuperUser obsessing work? (and is there no side effects on SuperSU)

- are there still situations where references disapear?

To report about references not being consistent please provide:

- make sure the logging (advances prefs) is on

- provide a logcat

- provide a dumpfile

- tell me what you did, what you expected and what you saw

Without that info I can't do anything as the bug you may experience is not trivial. Reports witout that info will be ignored; not because I don't believe you but because I can't reproduce myself despite 5 devices on different ROMs/Version/Kernels)
[BetterBatteryStats] Karpfenhai:
Btw, gpio was handled in this thread before, unfortunately i can't remember when exactly but it was a post of mine for sure, just search, thx.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] M.A.K:
When I plug/unplug, all references show the 'since <time>' display as the unplugged time except the 'since charged' reference which seems to be appropriate to the time of the last charge.

However, when viewing a working stat such as 'partial wakelocks', only the since unplugged timeframe is used even if I select 'since charged'.

It would seem that BBS is writing the time reference ok but looking elsewhere for references as it finds the 'since <time>' timeframes without fail.
[BetterBatteryStats] sewe:
This isn´t my phone but can you explain this?

The problem is that he´s loosing battery fast

https://www.dropbox.com/s/9css3ch9w2q2538/BetterBatteryStats-2012-08-19_093708155.txt

Level lost [%]: 70Voltage lost [mV]: 528

Deep Sleep (): 10 h 43 m 51 s (38631 s) Ratio: 98,9%

Awake (): 7 m 20 s (440 s) Ratio: 1,1%

Screen On (): 4 m 3 s (243 s) Ratio: 0,6%
[BetterBatteryStats] Karpfenhai:
Bad dump (no root) but this seems to be the famous s3 battery plummet :mad:

Search there are many others with this issue!

I recommend to reboot if the drop happens or disable lte if possible.

Afaik there is an upgrade (modem) to get rid of it.

Its a shot in the dark..

Tapatalked from my Samsung GT9100

---------- Post added at 11:51 PM ---------- Previous post was at 11:37 PM ----------

found it, good luck! :D

Tapatalked from my Samsung GT9100
[BetterBatteryStats] sewe:
I cant´t ask him to root because of this

What favourite plummet, are you talkting about cell standby wrong value 34mA instead of 3.4, if so that´s not the case, he´s loosing battery and the bug is just reporting it wrong
[BetterBatteryStats] Karpfenhai:
Have a closer look here:

http://xdaforums.com/showthread.php?t=1811182

Tapatalked from my Samsung GT9100
[BetterBatteryStats] akapaul26:
Do you see anything wrong with my log? I have been losing battery faster than normal IMO while using the device mostly. I have followed the steps in post three to stop the auto maps. The log was created with performance governor, I usually use ondemand. I am using sense4 senseless with apex launcher and faux kernel. Thanks in advance for looking.

Paul
[BetterBatteryStats] sewe:
I didn't have to read the whole thread, that's not his problem,op in that thread says that the only thing that stops it is flightmode but in this case it doesn't,

It drains like hell even in flightmode

As you can see, it´s avake to much and what i don´t understand is why bbs says it deepsleeps like a baby

https://www.dropbox.com/s/zm1iqiegrw06rt6/Screenshot_2012-08-19-19-47-00.png

Here´s another one

Flightmode all the time

Level lost is backwards, he lost 38%

https://www.dropbox.com/s/5h1ifc01mnm1isf/BetterBatteryStats-2012-08-19_18 flygläge3337751.txt

Skickat från min GT-I9300 via Tapatalk 2
[BetterBatteryStats] Karpfenhai:
Looks not to bad but i would strongly recommend to not use performance governor as it tends to run on high CPU only (visible in your dump)!

Ondemand is just fine! Remember you are here to save battery, not to burn, so its am oxymoron then :p

Maps its still misbehaving, did you actually use it during your measuring period?

Tapatalked from my Samsung GT9100
[BetterBatteryStats] akapaul26:
I know about the governor, I had it on performance for benchmarking... forgot to set it back before I ran the BBS!!! Back to ondemand now...I did not use maps at all infact I did not touch the phone during the test...I thi9nk it may be the updated maps version as it is causing random reboots for some users of the elegancia rom. reverting back to the previous maps may clear this issue that appears to be a google issue with the maps.

I did another test drive and now it looks like maps is ok but calendar is going crazy....This is with CPU on ondemand.
[BetterBatteryStats] alexinna:
I would also suggest to look at

*sync*_com.htc.sync.provider.weather_Account: 9 s (9 s) Count:8 0.2%

Do yopu really need weather to refresh 8 times in 1.5h? Plus it could use location services. Also I see that Wi-Fi is On and running all the time. It causing below wakelocks:

"wlan_rx_wake" (): 5 m 15 s (315 s) Cnt:(c/wc/ec)175/0/175 5.8%
"wlan_wake" (): 2 s (2 s) Cnt:(c/wc/ec)1259/159/0 0.0%
[BetterBatteryStats] akapaul26:
I am old school when it comes to wifi....I keep it on while at home and when im on the road data turns on. otherwise I am always between 2g and 4g. Will look at weather, thanks not sure why its doing this.
[BetterBatteryStats] Emir5kurt:
Can you look at my log as well? I'm seeing some drain overnight. Thanks.

There are some stuff at alarms that I couldn't understand what they are.
[BetterBatteryStats] alexinna:
Beta testing: 1.10b4

I'm still having an issue with Deep Sleep. Application is not displaying it correctly

Deep Sleep (): (-655311 s) Ratio: -4257.5%

I did plug/unplug charger after installing new beta but never reboot my phone. Do I need to reboot for BBS to work correctly?
[BetterBatteryStats] alexinna:
Please read post #1 on how to generate correct idle dump file with Kernel Wakelocks.

Based on the attached file I can see the following:

Android system backup is still running very often

*backup* (Android System): 1 m 23 s (83 s) Count:1055 0.2%

even when you have TB installed. I would recommend to use only TB and backup on DropBox for example or other cloud services ones a day.

Google "quick search box" creates lots of wakelocks and probably using location services as well. Post #3 describes how to deal with that. Also it will be a good idea to review Google+ and Beautiful Widgets to check if you need to refresh them so often.
[BetterBatteryStats] chamonix:
You are absolutely right. 'since' comes from another source (the batteryinfo) service and I will move that to taking the references as source.

Edit: #245
[BetterBatteryStats] Stileth:
Thx a lot! Turned off google sync, uninstalled SugarSync and BlueStacks, turned off google location services and phone is now deep sleeping like a well fed baby :D

Managed to cut down consumption to 3-7 mA! :victory:
[BetterBatteryStats] M.A.K:
I'm not sure I understand. Do you plan to:

1. Replace the 'since...' data with the elusive references that haven't worked for me since 1.9.*.

or:

2. Replace the source of the failing references with the batteryinfo data that seems to be working.
[BetterBatteryStats] chamonix:
Without working references there is no data so there is no sense either to show 'since'. My goal is to make things consistent and get all the info from the references. Of course this also means fixing the references where those are not working properly
[BetterBatteryStats] Salty Wagyu:
I froze the Facebook app two days ago in ROM Toolbox Pro, but the number of wakeups from com.facebook.katana is still gradually increasing. I've been into Settings > Apps and checking for Facebook in running process and cached processes but no sign of Facebook. :confused:

Attached the log, anything else looks unusual?
[BetterBatteryStats] alexinna:
Attached dump shows: Since Unplugged Since 3 d 17 h 15 m 10 s. is it correct?

Not sure yet why Alarms shows so many FB wakelocks but after 3+d with Wi-Fi on you lost only 73%. This is not usual I would say.

And this is on top of Android backup, location/map services and other stuff that is running.

Please confirm you can use device for such a long time.
[BetterBatteryStats] Salty Wagyu:
Yes I can confirm it is 3+ days :)
[BetterBatteryStats] alexinna:
In this case I wouldn't even worry about wakelocks on BBS dump and enjoyed my device :)

But if you do want to get one more day take a look on backups, location/map services and maybe Go launcher.

Still can't connect dots for FB behavior. Maybe you can remove FB to debug this issue.

Good luck!
[BetterBatteryStats] chamonix:
Release 1.10b5

New beta is up.

I have invested a lot of energy in reproducing a situation where I could get no "other" stats anymore and starting from this I have refactored the error handling to make those errors visible to the user. At the same time I found that one API call was making the most trouble on my setup so I started cleaning up unneeded API calls.

Even with a monkey test on all stats I was not able to reproduce any data loss and I hope this will work for you too!

As always, see changelog for details.

Happy testing!
[BetterBatteryStats] chamonix:
Feedback missing

I need some feedback on following fixes:

- superuser not obcessing anymore

- tasker plugin delivering complete dumpfiles

- stats on froyo

- "deleted:" kwl on siyah kernel being processed correctly
[BetterBatteryStats] chamonix:
Now that IS intersting:

08-19 23:24:37.179 D/StatsProvider(27859): Added Deep sleep:7 d 21 h 33 m 44 s (682424 s) Ratio: 4049.6%
08-19 23:24:37.179 D/Misc (27859):[B] Substracting Deep Sleep[/B] 7 d 17 h 47 m 47 s (668867 s) Ratio: 90546.0% from Deep Sleep 7 d 21 h 33 m 44 s (682424 s) Ratio: 4049.6%
<snip>
08-19 23:24:37.179 D/StatsProvider(27859): Substracting [Misc [m_name=Deep Sleep, m_timeOn=13556447, m_timeRunning=16113069], Misc [m_name=Awake, m_timeOn=3295327, m_timeRunning=16851774], Misc [m_name=Screen On, m_timeOn=3022498, m_timeRunning=16851774]]
08-19 23:24:37.179 D/StatsProvider(27859): from [Misc [m_name=Deep Sleep, m_timeOn=668867598, m_timeRunning=738705], Misc [m_name=Awake, m_timeOn=275746, m_timeRunning=738705], Misc [m_name=Screen On, m_timeOn=261514, m_timeRunning=738705]]
08-19 23:24:37.179 D/StatsProvider(27859): Current value: Deep Sleep 3 h 45 m 56 s (13556 s) Ratio: 84.1%
08-19 23:24:37.179 D/KeyguardViewMediator( 543): setHidden false
08-19 23:24:37.189 D/Misc (27859): [B]Substracting Deep Sleep[/B] 7 d 17 h 47 m 47 s (668867 s) Ratio: 90546.0% from Deep Sleep 3 h 45 m 56 s (13556 s) Ratio: 84.1%
08-19 23:24:37.189 E/Misc (27859): substractFromRef generated negative values (Misc [m_name=Deep Sleep, m_timeOn=-655311151, m_timeRunning=15374364] - Misc [m_name=Deep Sleep, m_timeOn=668867598, m_timeRunning=738705])
08-19 23:24:37.189 D/StatsProvider(27859): Result value: Deep Sleep (-655311 s) Ratio: -4262.4%

Looking at that log it seems something happens twice.... and yes, looking at the code confirms that. Testing a little and I'll add an issue together with the fix

Edit: confirmed and fixed for b6: #247
[BetterBatteryStats] chamonix:
You are right, your phone didn't sleep, and the winner is:

*backup* (Systém Android): 3 h 49 m 47 s (13787 s) Count:56 93,1%

Google could backup. That's the cost of cloud when it doesn't work....

If you have an offline backup like titanium I'd recommend turning off google's could backup and using the offline backup instread. Please note that you will have to reboot to make sure the cloud backup stops as it tends to continue running if something is ongoing
[BetterBatteryStats] chamonix:
Release 1.10b6

Wow, I managed to push b6 before anyone downloaded b5 :D

Happy testing!
[BetterBatteryStats] Karpfenhai:
gotcha, have b5 installed..

Dl b6 now

Tapatalked from my Samsung GT9100
[BetterBatteryStats] chamonix:
Pfffff :P

Internet's too fast in Denmark ;)
[BetterBatteryStats] cukierkas:
Hello dear dev, how are you?

Thanks for the wonderful app.

I've got one issue, app doesn't show CPU states properly. Screen shot included.

App version is latest, tryed to reinstall, cleared cache, dalvic cache, fixed permissions.

Galaxy scl I9003, xwlf2, xda bam kernel v14, rooted. Smartass governor, sio scheduler.

Thanks for the answer.
[BetterBatteryStats] chamonix:
I'm pretty good, thank you! and thanks for the flowers.

Could you provide a logcat after refreshing the stats? There are multiple reasons that could cause that and we need to refine a bit with the logs.
[BetterBatteryStats] Stileth:
This was happening to me too when I installed the app. Restart of phone sorted it.