yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] dieterdax:
Hi Guys,

I could really need some help with my I19505 running Slimkat 4.4.4. I experience battery draining like hell when "idle" (before Slimkat I was running CM11 with the same battery problems).

I attached an overnight idle-dumpfile of BBS with Root enabled, Sync off and Wifi connected all the time. Google location reporting is disabled, as well as all google services I heard I can safely disable without losing Gmail, Hangouts or Google notes sync.

I read Perseus71 is not a fan of the app Greenify, so I could disable it for my next dump if that's helpful for your analysis.

I really appreciate your help, as I already invested a lot of time to get my phone running without that crazy battery drain (I changed ROM, Kernel, used flight-mode overnight and even bought a new battery, but never got below losing .6 overnight).

Edit: I do use Hangouts and Whatsapp for communication, as well as Gmail (all work related)
[BetterBatteryStats] godlesplay:
[MENTION=1330150]chamonix[/MENTION] I'm using rc5 right now with xposed

do you need any logs?
[BetterBatteryStats] vallyls:
I have flashed Viper 6.2 again without the Elemental Kernel and it seems the ButtonsBlink in gone. It might be something from the Elemental.

I'll flash Elemental tomorrow to see if ButtonsBlink in back to drain my battery.
[BetterBatteryStats] apfelstyle:
Again the "Battery service could not contacted" error message.

Android L preview, nexus 5, BBS installed as system app, rooted

Logcat: https://docs.google.com/file/d/0B8W2Djw1KHN4NlNFcUltTVVNRFU/edit?usp=docslist_api

Text Dumpfile: https://docs.google.com/file/d/0B8W2Djw1KHN4azgzTXBzcmRIMUE/edit?usp=docslist_api
[BetterBatteryStats] u81:
RC5- Alarms show up fine now- No Network info but no error either

[MENTION=1330150]chamonix[/MENTION]

I wish to confirm that on my phone, I can now see the alarms info in RC5. However, no info shows under Network stats but I don't get an error either.

Could either you or [MENTION=3639717]Perseus71[/MENTION] also look at the two sets of logs one with Wifi and sync off and the other one with wifi on , to identify the causes of battery drain.

Thanks once again for the wonderful and tireless effort.
[BetterBatteryStats] Perseus:
Use Rescan Media if you want. Post your findings. Kill App is here.

Turn off SYNC. Post an Idle Log after reboot.
[BetterBatteryStats] lanwarrior:
I went to Settings --> General --> Accounts --> Google and clicked under my Google username. It now shows the following:

I never saw these 3 entries before. I so I unchecked all of them and rebooted. Went back, and it is checked AGAIN! Tried a few other things, and no matter what, Google checked the boxes again.

Do you have these? If yes, how do you disable it?
[BetterBatteryStats] Perseus:
Never seen that. Not any of that stuff with * in front. Sounds weird with your Rom or Gapps. Turn off Google Location Reporting from inside the Google Settings app. If you don't have it or its already turned off then turn off Location / GPS alltogether. Dunno what Push Notifications are. Do you have Google Music/books/keep/games or any of these apps ? If yes , remove.
[BetterBatteryStats] an0n981:
Greemify puts those there. They are hidden sync settings
[BetterBatteryStats] lanwarrior:
Interestingly, this is stock ROM. I didnt make any modification other than root.

Google Location Reporting already disabled, both in Android Settings and Google Settings.

I do use Play Music and Newsstand, but thats it.

Hmmm, just looked at my friend Nexus 5 running stock and it does NOT have these 3 sync things woth asterisk. ****, do I have malware?!

---------- Post added at 09:27 AM ---------- Previous post was at 09:24 AM ----------

That's interesting. But why put it here if I can't do anything about it?
[BetterBatteryStats] an0n981:
That is a question for the Greenify thread
[BetterBatteryStats] greyhd:
I have greenify and I do not have any of those settings. The only reason I see greenify putting those options is if you have GCM push notifications clicked within Greenify.
[BetterBatteryStats] gGabi:
Those appear there because you have "Hidden sync" option checked in the Greenify app.

I saw those as well, but I use this app to disable them completely. Install the app, go to system apps tab and search for Google Play Services, click on it and then click on "show full name" so it'll be easier for you to search those services and to disable them. Reboot when you're done. Hope it works :good:
[BetterBatteryStats] an0n981:
It's better to use something like Android Tuner. Disabling the services without the corresponding receivers may cause horrible wakelocks
[BetterBatteryStats] greyhd:
+1 on this. I can confirm that this will cause a lot of wakelocks.
[BetterBatteryStats] gGabi:
I used this app only to disable location services and few other things I can't remember and I had no wakelocks at all...

I think that you disable hald of the components that all together turned out to have one purpose, 1 function, yes, it will cause wakelocks. But if you disable all of the components that united are for 1 function/purpose, then why the wakelocks? I don't know, I might be wrong. But again, using this apps for months with no wakelocks at all, but the opposite, this app helped me get rid of huge location and sync wakelocks.
[BetterBatteryStats] an0n981:
Try this: disable both checkin services (there are only 2 related to checkin) in GPlayServices without disabling receivers. Reboot and let your phone sit for say 30 minutes. Then check BBS partial wakelocks. You will have 0% deep sleep time.
[BetterBatteryStats] gGabi:
What does the CheckIn services has to do with the problem of the dude I've responded to?

He had problems with GPS sync and location history sync. You can disable both, as I did, with no wakelocks in the middle.
[BetterBatteryStats] chamonix:
yes, a logcat and a dumpfile. I assume you have granted bbs so rights and are not on the L release, correct?

edit: and BTW alarms do not use Xposed as they are not processed from the api. To test the Xposed module with BBS go the partial wakelocks
[BetterBatteryStats] an0n981:
The quote below is what I responded to. Checkin services was the example I used because it's the first thing AT lists for GPlayServices. Disabling all checkin services without disabling the checkin receivers will cause 100% checkinservices handoff wakelock.
[BetterBatteryStats] godlesplay:
logs in attachments, I'm on cm11 4.4.4
[BetterBatteryStats] Perseus:
+2

Same would apply to Google Services Framework.

Disabling Services within an app can have devstating impact on the operation of the App as well as how Android communicates with the app. Results could be anywhere from Bootloop to complete misbehavior from the said app. It is best to turn off Receivers instead as that takes away the ability of the app to Poll the Android TICKer and thereby cause Partial wakelock.

An analogy to this would be like taking away the Radiator of a Car but keep the Gas tank intact. The car will still run but will fail down soon. However if you take out say ABS or Lane Assist System, the car will still run fine.
[BetterBatteryStats] lanwarrior:
Dude... I think you just identified the root cause of my problem! I do use "Disable Service" app and in Google Service Framework, I disabled:

- CheckinService

- EventLogService

- SystemUpdateService.

I will enable this, reboot and see what happen...
[BetterBatteryStats] chamonix:
Your issue is definitely not related to the Xposed module: the stats retrieved from the API that is access by either the system app or the xposed module is retrieved properly.

Still there is a problem with alarms (related to parsing dumpsys): in order for me to check on that I would need:

- a logcat with BBS advanced debug logging settings turned on

- a file containing the result of 'dumpsys alarm' (no copy paste, I need the file) in order to be able to debug the parser
[BetterBatteryStats] chamonix:
I just wanted to give an update about RC6. I have a possible fix for the system app install on certain devices but am still fighting with the chronus / deskclock integration. I have installed chronus as I didn't get timely feedback and was able to reproduce and track the problem down to the event receiver / filter. The problem seems to be related to the fact that BBS xdaedition has a difference package name (apk).

I still have trouble getting my head around what is wrong but I have the feeling that the problem is related to ADT and the way the package renaming affects the manifest (or not in the current case). I give myself this evening to see if I find a fix that could go into RC6. If I am not able to fix in that timebox I will release RC6 as it is right now.

:)

OK
I/ActivityManager( 777): START u0 {cmp=com.asksven.betterbatterystats/.DashClockSettingsActivity (has extras)} from pid 27989
I/ActivityManager( 777): Displayed com.asksven.betterbatterystats/.DashClockSettingsActivity: +83ms

NOK
I/ActivityManager( 777): START u0 {cmp=com.asksven.betterbatterystats_xdaedition/.DashClockSettingsActivity (has extras)} from pid 27989
[BetterBatteryStats] lanwarrior:
Hmm, I spoke too soon. The 3 services are still shown as "unchecked" after reboot, so it looks like it is disabled by Android, not me. Probably because I do not use Google Now.

I looked for other services in "Disable" service and I did NOT disable any other Google related service. However, BBS still show that "Android" is using 44% of the battery, with 1.1% PER MINUTE! (!?). I am at loss now...
[BetterBatteryStats] Perseus:
You didn't read what I said #24322 above your last post did you ?
[BetterBatteryStats] lanwarrior:
I did, but what I meant is that I THOUGHT I was the one who disabled those service. Turns out it was not me, it was Android itself.

I use "Disable Service" app to disable service from installed apps, not System Apps. I just happen to look under System Apps and noticed those 3 in relation to what you and others have posted.
[BetterBatteryStats] Perseus:
Its unlikely Android is going to do anything like this. As others said Greenify may have done it.
[BetterBatteryStats] lanwarrior:
I didn't Greenified any Google related stuff, like Google Play, Google Music, etc.

I just uninstalled Greenify. Will see if this issue still persist. Will report back.

EDIT: Even after Greenify is uninstalled from Xpose, those 3 services are still disabled.
[BetterBatteryStats] chamonix:
RC6 is up (I love time boxing!). If you had problems previously with installing as a system app please retest. Same is valid for settings from chronus not being accessible.

Please provide logs if a test was negative
[BetterBatteryStats] chamonix:
If nothing bad happens RC6 is the golden release
[BetterBatteryStats] chamonix:
Still no feedback from the gplay beta testers.... I must say I am pretty dissapointed.
[BetterBatteryStats] tuniel:
Extension settings in Chronus is now working properly. Thanks!
[BetterBatteryStats] Perseus:
Apologies I missed this one.

Settings >Wireless >Advanced turn off Scanning always available. Also set "Keep Wireless On During Sleep" to Never. Look for my post Linking to [MENTION=4355376]Karpfenhai[/MENTION]'s Mod and steps on how to apply it in this thread. Do so.

Downloading Now. I don't expect any issues. If I do find any will post otherwise All's well.
[BetterBatteryStats] guido_glx:
Yessss! Settings working fine now in DashClock extension

Enviado desde mi GT-I9100 mediante Tapatalk
[BetterBatteryStats] ttabbal:
Haven't had any problems with it. Anything particular you want to have tested? I've just been using it and randomly poking things..
[BetterBatteryStats] gGabi:
I have a simple suggestion before releasing the stable version :)

If possible, please, can you make the the stats text a bit bigger? :D

For example, the awake time, or wakeups # in Alarms section, etc...

Using the graph bars it makes it a bit bolder, but the pie gauge looks much better, but sadly with a smaller text.

EDIT: Maybe in the future you can add an option for the user to configure the size of the text :)
[BetterBatteryStats] Endlessgamestudio.com:
hmm gonna try this app then see, my device only work for 3-4 hours if 3G on :(
[BetterBatteryStats] greyhd:
How can we enable the option to "since unplugged"? I only have "boot" as the option. Also how do you uninstall it? It doesn't have that option.
[BetterBatteryStats] chamonix:
The update process and the install of the new system app are the things I'd be the most interested in as those steps have proven to be different from sideload
[BetterBatteryStats] chamonix:
I won't risk any change in the layout at this stage but you are kindly invited to give your input on UI/UX for the upcoming 2.0 iterations
[BetterBatteryStats] gGabi:
RC5 wouldn't install as sytem app on my 4.4.4 GPe HTC One M7, would FC right away.

RC6 installed without issues and working fine.

---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------

I wish I had any coding knoweledge. Unfortunately I'm totally in parallel with coding :(
[BetterBatteryStats] godlesplay:
what do you mean by this "a file containing the result of 'dumpsys alarm' (no copy paste, I need the file) in order to be able to debug the parser" how can I get this file?
[BetterBatteryStats] HaTrED_:
Dash/Chronus extension seems not to be working, at least with me... just gives me the Awake Time but battery drain is always 0% /h! :(
[BetterBatteryStats] tuniel:
Form me it's working with chronus, the only thing is that the extension doesn't seem to fallback to "since boot", even if it is selected in the extension settings. Once I reboot I always get 0%/h
[BetterBatteryStats] RobertusITA:
Sorry, how can i delete BBS if is installed like a system app?
[BetterBatteryStats] guido_glx:
That happens to me every time the device is rebooted. Plugging & unplugging fixes it.

Enviado desde mi GT-I9100 mediante Tapatalk
[BetterBatteryStats] chamonix:
open terminal or adb shell

su

dumpsys alarm > /sdcard/Alarms.txt

attach Alarms.txt
[BetterBatteryStats] chamonix:
please provide a logcat with BBS advanced settings set to debug
[BetterBatteryStats] chamonix:
by going the same way as when you installed it:

settings - advanced

there chose uninstall to uninstall the system app part
[BetterBatteryStats] chamonix:
my original question was about the beta available on gplay. As rc6 is not on gplay you have obviously tested under other conditions.

when you encounter an FC please save a logcat: without that I have no way of finding out what happened.

No need for you to have coding knowledge. My answer was about commenting on the UI during the next cycle. Layouts are tricky because of the multitude of resolutions and screen densities and I am not ready to take the risk of breaking something on specific devices at this late stage. RCs are only for Bugfixes, I implement feature requests only prior to and during beta
[BetterBatteryStats] GabrielSousa:
[MENTION=1330150]chamonix[/MENTION]

same problem on RC6 :(

I/SystemAppInstaller(31937): Checking if com.asksven.betterbatterystats_xdaedition.apk is a system app

I/SystemAppInstaller(31937): Command returned ls: /system/priv-app/com.asksven.betterbatterystats_xdaedition.apk: No such file or directory

I/SystemAppInstaller(31937): Checking if system is mounted rw

I/SystemAppInstaller(31937): Remount system rw

I/SystemAppInstaller(31937): Checking if system is mounted rw

I/SystemAppInstaller(31937): Checking if system is mounted rw

I/SystemAppInstaller(31937): Status: An error occured mounting system rw. Aborted

I/SystemAppInstaller(31937): Checking if com.asksven.betterbatterystats_xdaedition.apk is a system app

I/SystemAppInstaller(31937): Command returned ls: /system/priv-app/com.asksven.betterbatterystats_xdaedition.apk: No such file or directory

E/BetteryInfoTest.MainActivity(31937): History: An error occured mounting system rw. Aborted

I/SystemAppInstaller(31937): Checking if com.asksven.betterbatterystats_xdaedition.apk is a system app

I/SystemAppInstaller(31937): Command returned ls: /system/priv-app/com.asksven.betterbatterystats_xdaedition.apk: No such file or directory

E/TemperatureHumiditySensor( 680): mCompEngine is NULL
[BetterBatteryStats] godlesplay:
here it is
[BetterBatteryStats] HaTrED_:
QFT! :good:
[BetterBatteryStats] tuniel:
Here you go. I plugged and unplugged. I have run something and made sure that the extension was sowing stats, then rebooted, run something again and the extension is showing 0%/h.

Let me know if this is what you need

https://mega.co.nz/#!8lcXUQoJ!XI-KlQojQG7KD1HNaqDPIXnFd4fR5qB9LDPUuCI9xDI
[BetterBatteryStats] chrisaw:
The situation on this is - in the real world people are busy and don't have time to arse around trailing through a billion page XDA developers thread to update each app they want to beta test. There is already a system for that in Play Store - it's called Google+ Groups and a beta attached to that. Personally, I would rather run RCs/betas than run an app which hasn't been updated in months on my phone.

Can we get this sorted out? Nobody wants to screw around pushing APK files around and having absolutely no notification for when there is a newer version released - especially when app store can keep you on the latest build automatically. Believe me - get a Google+ group and I will be the first to contribute as much feedback on bugs as I possibly can.
[BetterBatteryStats] :
I'm sure someone else has a better answer, but i hope this will help you understand Chamonix's decision :)

What you said is exactly the reason why Chamonix doesn't want to do the beta testing using the service offered by google. ;)

He mentioned it more than once already, that beta testing on play store only offers the means to notify beta testers about new beta updates that needs testing. The means they offer to let users provide the developers valuable feedback is very lacking, at least when compared to the direct, personal feedback that Chamonix gets here in XDA from enthusiastic users.
[BetterBatteryStats] ttabbal:
App info shows me on RC4. Play doesn't show an update. Should there be one?
[BetterBatteryStats] eluspo:
Is this already compatible with android L?
[BetterBatteryStats] mdamaged:
Yes.
[BetterBatteryStats] lanwarrior:
This is the continuation from post 24326, with discussion on 24328 and 24330.

RECAP: I uninstalled Greenify, let the phone overnight without connecting to power, and here's the result in the morning:

As you can see, there are 2 hours of "Awake", with KWL + PWL = 1.5 hours. The battery goes down from 98% to 92% in 8 hours. Looking at "Alarms", it shows the following:

So com.sec.ims.android and com.google.android.gms are the biggest culprit. The first one, it is caused by com.samsung.rcs.framework.alarms.action.registerrefresh..

The graph shows the phone Awake randomly and throughout the night:

Key things about my phone:

- NO Google Now

- NO Facebook, Twitter, even weather

- 4 GMail accounts

- I DISABLED (frozen with TitaniumBackup or Turn Off from Settings) most Samsung stuff - Samsung Hub, Samsung Accounts, etc.

- Keep Wi-Fi on during sleep set to "Always". I read it's better for battery life to do this - correct me if I am wrong.

So I am curious what is this samsung.rcs.framework stuff?

As usual, all logs are attached.
[BetterBatteryStats] chamonix:
I ran the file through my unit tests and the parser runs fine. On the other hand the alarm list is pretty short. Would you mind checking the raw stat alarms to see if there is something displayed there?
[BetterBatteryStats] chamonix:
I am really sorry but you seem to have a pretty special version of the mount binary. For those cases I have created a CWM package that you can apply from recovery to install the system app
[BetterBatteryStats] chamonix:
The extension showing 0%/h after a reboot is perfectly correct: at reboot all counters are reset. What matters is that after a reboot and after some time the value should change to something > 0%/h.

If this does not happen please make sure that you have checked the "debug" setting (advanced settings) so that we can check if the dashclock service was called and what values were retrieved from the fallback reference.
[BetterBatteryStats] godlesplay:
I launched BBS straight after reboot and still same: "This stat requires root"
[BetterBatteryStats] tuniel:
That's what I mean. Even after a while it always stays at 0%/h. Before I took the log I sent you I had run a game and BBS was showing something like 50%/h, but the extension stays at 0
[BetterBatteryStats] chamonix:
Wow, quoting a post from last april as your first post in this thread. Troll alarm? ;)

Just FYI there IS a beta on gplay for chosen testers and selected release candiates. You will read that when you reach the end of june.

No need for a g+ community for that either, google groups work as well.

On the other hand those are just tools and a tool has never solved a problem. Testing is about the process and the feedback and I prefer to stick to a process/workflow for testing that has proven it works (look at the number of posts and view of this thread). Testing is a lot of work (I don't talk about reporting that an app fails): you need to collect logs, describe error situations, give feedback on fixes, retest, etc.

Finally a remark about notification: the name of the thread telly you the current release and date so there is no need to scan threads as this is kind of an established convension on xda. And if you don't have time to scan the updated thread in your control panel you can follow me on twitter and get the updates delivered to you.

An finally if sideloading is too much of an effort then don't. You can also lean back and get the version that have been tested by dedicated users of this thread delivered to you by google play.
[BetterBatteryStats] chamonix:
Then please repeat with debug options and attache a dumpfile and the logcat.
[BetterBatteryStats] chamonix:
After a boot this would be normal as the stats are reset. Leave your phone alone one hour and then check the raw alarms. If something shows there recheck the stats. The error message may be a little misleading as it also shows when alarms are empty
[BetterBatteryStats] chamonix:
Time to start compacting the change log, take new screenshots and build the final packages for release....
[BetterBatteryStats] GabrielSousa:
no need ;) i can do it manual ;)
[BetterBatteryStats] godlesplay:
What do you mean by raw alarms?
[BetterBatteryStats] chamonix:
Menu - More - Raw Stats and select alarms from the spinner
[BetterBatteryStats] chamonix:
1.16 is up. No changes from RC6 except the change log. Google Play roll-out (staged) is started.

Once again this has been a challenging journey from the B1 until RC6. The planning was well aligned with Google I/O and I feel that a 2 major release strategy per year (for I/O and at the end of the year for the new devices) is a good plan.

Thanks to all dedicated testers for your valuable support and for your tireless dedication to making BBS such a great tool.
[BetterBatteryStats] tuniel:
I thought I had already. I'll come back to you tomorrow
[BetterBatteryStats] chrisaw:
Quoting a post from so long ago to highlight the stupidity of the whole structure of the way you are testing this app and the COMPLETE lack of forward thinking happening on this project. End of.
[BetterBatteryStats] brice83:
Hi guys, is it normal after 10 hours and 50% off battery last that all the progression bar on the application are white.see image in attachement.
[BetterBatteryStats] Lownita:
Yes of course, here we go! http://dl.dropbox.com/u/37488657/BetterBatteryStats.txt

Tried to switch modem, but didn't help!

Thanks!
[BetterBatteryStats] ponicpool:
Kindly have a look for kernel waterlocks. Here is the link

https://dl.dropbox.com/0/view/czkw5q60ihdvidy/BetterBatteryStats-2012-01-01_153107533.txt
[BetterBatteryStats] yani2000:
Some suggest Maps, some Google+.

For you it was the Google backup service.

For me it was tracked down to an app called Locale Gtalk Plug-in Free (I think it's malicious).

I restored it thru Titanium from a previous ROM and guess it wasn't restored correctly so I had to re-apply all my Tasker tasks that use this app.

And because I have ROOT access I additionally deactivated some permissions thru Permissions app, just to be on the safe side.