yashsingh1/xdaforums huggingface dataset:
[Android General] pawwaap:
And why enrolling eWeather on Servicely hit list doesn't help, have you any idea how to check if Servicely works at all?

And what is wrong with Automagic, has Edge better stability, less power use?

Assuming want automation application with Amplify then which entries from Amplify are worth to set as 9999999 for Screen OFF, based on the log provided in previous post?

Chuwi Hi10 plus, [ROM][13.12.]-Remix-OS-2.0-(Android-5.1.1)-for-Chuwi-Vi10-Plus,-Hi10-Plus,-Hi10-Pro,-Hibook,-Hibook-Pro-&-Hi12#entry2280114]RemixOS LP
[Android General] :
Llama is the lightest, but also has fewer features and is kind of abandoware. It still works fine for the most part though. As for power use I would say that Llama and Automagic are equal. Automagic is structured to be extremely battery friendly but Llama is just extremely lightweight and thus requires less CPU and RAM to actually do something. On the other hand, I found Tasker to drain more battery than these two.

I would be very careful with limiting like that. I only use 9999999 for the widget alarm.
[Android General] pawwaap:
And what about wakelocks & alarms of Automagic (or other automation application)? If we use it for limiting other apps wakelock & alarms it itself should take care of own ones.

Chuwi Hi10 plus, [ROM][13.12.]-Remix-OS-2.0-(Android-5.1.1)-for-Chuwi-Vi10-Plus,-Hi10-Plus,-Hi10-Pro,-Hibook,-Hibook-Pro-&-Hi12#entry2280114]RemixOS LP
[Android General] Blade2014:
Hello, can anyone please check my BBS dump and guide me?http://cloud.tapatalk.com/s/592125c330da4/BetterBatteryStats-2017-05-21_102816612.txt

Even though the phone was in airplane mode, somehow it lost 0.7% per hour. Kindly guide me.

Regards,

Santhosh.S

Sent from "The element with atomic number one".
[Android General] DB126:
At first glance it appears device was only awake for 64 sec (out of ~3 hours) which would be quite good. However, there are some unexpected entries & reference points that suggests the device was rebooted just prior to starting the BBS log. It appears the device was still going through it's boot activities. That *may* have compromised some of the data recorded.

Observations/thoughts:

- there was no unusual app activity in the submitted log

- device appeared to sleep well during most of the monitoring period

- an immediate drop-off of 1-2% after coming off charge is typical for some devices; there's a logical explanation which I won't detail here

- need a longer BBS sampling window (6-8 hours) for proper analysis

- wait at least 5 min after rebooting to start the BSS log

- can also create a dump starting at a lower charge point (eg: 80%) to avoid distorting stats with large initial drop off

Tip: enabling Watchdog option will create screen off/on reference points. After waking device open BBS and set From/To spinners to "unplugged" and "screen on" and then submit that log.
[Android General] Blade2014:
Thank you so much for such a lengthy writeup... I shall do as you have mentioned and post a dump file soon. Thanks again for your efforts.

Regards,

Santhosh.S

Sent from "The element with atomic number one".
[Android General] pawwaap:
And what is proper procedure to initiate BetterBatteryStats logging? Especially when we want to start logging some time after charging and using a device?

It seems if BBS has started some time after charging complete it includes the state of before logging, i.e. from plug-off a charger to current. And of course it compromises the log, maybe this is the unexplained extra activity from my logs responsible for 0.3% "per hour" (in fact this is an average)?

And are screen off/on reference points visible only after enabling the watchdog option?

After enabling the watchdog option there's still only the "current" reference point.

Is it working in the way logging is starting just after screen off until screen on again (most needed) to read or dump of a log?
[Android General] DB126:
- use screen off/on reference points (watchdog must be enabled)

- BBS does not run in the background unless active monitoring is enabled (settings)

- BBS does not compromise the log integrity in any meaningful way

- likely sources your 0.3% per hour drain have been discussed on multiple occasions

- yes

- screen needs to be off for number of min indicated in settings for off/on reference points to be generated

You ask a lot and action little. Plenty of material has been posted for you to work with.
[Android General] Oswald Boelcke:
I really like your patience!:good:
[Android General] :
Automatic itself does not drain battery.

With no conditions defined it will not cause any wakelocks or alarms. Any wakelocks or alarms generated by Automatic will be related to your flows. If you block them, the flows will not work.
[Android General] pawwaap:
Yes, but if you use the trigger/condition ScreenON (what is needed here) then somehow the program must poll if it occurs, needn't it?
[Android General] pawwaap:
Appreciate very much your careful explanations, thank you very much!

And if the "work" is concerned, you know, it needs switching on/off and wait very looong ;)

Please, understand, if in the meanwhile trying to learn why doing it :)
[Android General] pawwaap:
Please, look at this (it has been gathered just now with this watchdog option):http://cloud.tapatalk.com/s/59220f547e3d3/BetterBatteryStats-2017-05-21_235808320.txt

Especially this intrigues:

Wakelocks (requires root / system app on Android 4.4+)
======================================================
*alarm* (com.Elecont.WeatherClock.eWeather HD): 35 m 58 s Count:0 16.7%
android:*alarm* (com.android.systemui.System UI): 35 m 56 s Count:0 16.6%
*alarm* (System): 35 m 56 s Count:13 16.6%
android:*alarm* (System): 35 m 56 s Count:12 16.6%
android:*alarm* (com.Elecont.WeatherClock.eWeather HD): 35 m 56 s Count:0 16.6%
*alarm* (com.franco.servicely.Servicely): 35 m 56 s Count:0 16.6%
android:ConnectivityService (System): 8 s Count:1 0.1%

Please again, explain, what does it mean: Elecont eWeather run for 35min and Count=0 ?

And what is the culprit, one may think from this Servicely prevented from sleeping for 35min, but in fact it looks like the device was awaken for just 1m18s:

=========
Other Usage
===========
Deep Sleep (): 3 h 34 m 33 s 99.4%
Awake (Screen Off) (): 1 m 13 s 0.6%
Screen On (): 3 s 0.0%
Wifi On (): 2 m 3 s 1.0%
Wifi Running (): 2 m 3 s 1.0%
Doze Interactive Time (): 3 s 0.0%
Screen dark (): 3 s 0.0%

Inconsistencies?

You said to freeze Elecont eWeather, i can do it, but:

- it'll destroy its widgets (complex and elaborated),

- want to understand how eWeather contributes to this 0.3%/h, and possibly to tame it with automation for screen OFF spells.

Yes, have just added the action 'kill eWeather' to Automagic "Screen OFF" flow.

Chuwi Hi10 plus, [ROM][13.12.]-Remix-OS-2.0-(Android-5.1.1)-for-Chuwi-Vi10-Plus,-Hi10-Plus,-Hi10-Pro,-Hibook,-Hibook-Pro-&-Hi12#entry2280114]RemixOS LP
[Android General] :
Yes, of course. It is inevitable. If you block it, the corresponding flow will not run.

It does not "poll" though. See https://developer.android.com/guide/components/broadcasts.html.
[Android General] ProudRed:
http://cloud.tapatalk.com/s/5922566fbf07a/logcat-2017-05-22_082311527.txt

http://cloud.tapatalk.com/s/5922565da8aac/BetterBatteryStats-2017-05-22_082258749.txt

New device. Everything normal ?
[Android General] DB126:
Recommend disabling eWeather to see if that makes a meaningful difference. Create a nandroid backup if concerned about side effects. Also recommend disabling Servicely and any other tools used disable, freeze or hibernate apps, block wakelocks or perform other enhanced power management tasks during sleep.

---------- Post added at 04:37 AM ---------- Previous post was at 04:32 AM ----------

Looks good (avg 0.2% drain per hour) with reasonably low wake time during the monitoring period. Enjoy your device!
[Android General] Celestial Fury:
Firstly, does BBS report these wakelocks as causing drain or is it only Amplify which says so? High wakelocks does not mean high battery drain and Amplify does NOT report battery drain. I can't say more without seeing some proper idle stats but I wouldn't limit those wakelocks except maybe RILJ1 but only if it causes drain.
[Android General] beeshyams:
Dear OP

Thanks for your tips. Have been able to come close to the target and get darn good battery life. 8+ hours SOT with 36 hours of usage

[ROM DISCONTINUED] >> DEEP IMPACT ROM … - Pg. 38 | Samsung Galaxy Note II GT-N7100, N7105 | XDA Forums http://xdaforums.com/showthread.php?t=2733262&page=38
[Android General] cornelito:
TBH you don't need all that hassle to achieve 0/0% battery drain. I only use Greenify without Xposed and constantly having 0% drain for 8hrs period. My phone is not even put onto Flight Mode etc.
[Android General] Celestial Fury:
That's because your WiFi is hardly running (< 1 min) so you don't get push notifications. That's one step above flight mode.
[Android General] Celestial Fury:
Back again. After getting the phone back from repairs and getting it down to 0% [0.0%/h], Google Play Services updated twice since then and I've been suffering like everyone else from crazy drains, some ghost drains meaning the drain can't be pinpointed. Some of the solutions suggested like disabling location or keep awake for Google Play Services in App Ops messes with BBS getting data and removing the GPS view from Battery Stats.

What I did was to disable Amplify within Xposed and let the phone run whatever it wanted to. Then re-enabled Amplify and the drain is now a manageable [0.4%/h]. Firstly, to be clear and since surprisingly no one ever asked, I do not and have never gotten [0.0%/h]

every

time. Certain times, depending on the duration of the limitations, alarms and wakelocks will run when their interval comes up and also drain from Google Play Services is hard to pinpoint.

One big change with Google Play Services is that it seems to have taken a leaf out of WeChat and now has unkillable ALARM_WAKEUPxxxxx where xxxxx is a random 5 digit number that gets recreated every time it's blocked. I hope Google didn't get any ideas from WeChat.

Post #2 now greatly expanded mostly with GPS (global positioning) alarms/wakelocks limited at 12h (I like a unified limited category). Also, a number of alarms/wakelocks have "(currently not limited)" meaning I no longer limit them because they seem to be playing nice now, I'm avoiding limiting anything related to synching and synching also seems to be playing nice and I don't use any widgets any more. Ad/Privacy related alarms that can't be blocked are limited to the max.
[Android General] aukhan:
Good to hear back and see the thread updated. What happen to your device recently it was back from servuce and now again ?? Whats wrong ??? which device are you using by looking the OP it has stamina i assume its a song brand??
[Android General] Celestial Fury:
Back from service just that one time then the Google Play Services update hit twice. It's a Sony Xperia Z1. While it was under repair I did use an Xperia Tx running JellyBean so some of the alarms/wakelocks in the guide might only be related to that phone/android version.
[Android General] dirty_smurf45:
Got Android 5.1 and Xposed doesn't work yet. Any alternative for Amplify? I miss the 0.0% battery decrease. Also, does BBS need Xposed (I forgot)?

Tapatalked with Boost Mobile Moto G (xt1031). Running Android 5.1 on CM12 by Meticulus.??the smoothness
[Android General] Celestial Fury:
[MENTION=5939247]dirty_smurf45[/MENTION], you should have posted those 0% [0.0%/h] screenshots.

I don't know of anything comparable to Amplify. BBS doesn't need XPosed but it needs root. Greenify can work without root though.
[Android General] v7:
Xposed for 5.1 http://xdaforums.com/showthread.php?p=59901239

Tapped from my furious ZR ;)
[Android General] ARGD:
Thanks.

Great guide.:good:
[Android General] 3473:
Something new I've noticed on the new Google Play Services is high 'lockbox' service and alarm... can these be limited?
[Android General] dirty_smurf45:
Amplify bootloops according to reports. I'll just wait for stable release. Thanks for sharing. Now I can be even more updated!!!?

Tapatalked with Boost Mobile Moto G (xt1031). Running Android 5.1 on CM12 by Meticulus.??the smoothness
[Android General] aukhan:
Me too now running on Android Lollipop and the sad part is lack of xposed Modules I wish rovo fixes it soon

Powered by ET!
[Android General] Celestial Fury:
There are a bunch of new Google Play Services alarms but if they don't show up in BBS (and lockbox doesn't for me) then don't amplify them. High count in Amplify doesn't necessarily equate to drain.
[Android General] Maddyraj:
Need help pls

I have followed the steps.. The following screenshot was my battery drain when my phone was in idle state so.. please suggest me , Which is safe to limit and best sec for these wakelocks to limit?
[Android General] v7:
Why would you care?? [MENTION=5401012]Celestial Fury[/MENTION] has already said about the drain.Everytime you won't be able to attain 0.0% drain.Never expect that to happen.As far as I know you've least idle drain.You should be happy about this.Better don't play around with the GP alarms or wakelocks.

Don't be so greedy.Be a nice guy ;):D

Tapped from my furious ZR ;)
[Android General] Celestial Fury:
You've got [0.1%/h] drain but that's with WiFi

off

during idle. You can limit these (also in Post #2):

- com.google.android.sidekick.shared.a.a.UPDATE_CALE NDAR_ACTION

But you should use alternative calendar here or your stock calendar may not trigger on event.

This also:

- com.google.android.apps.sidekick.SCHEDULED_REFRESH (I haven't seen any side effect yet but make no guarantees)

- com.google.android.gms/.checkin.EventLogService$Receiver

You have 2 more alarms with >20+ alarm triggers but I don't have those so you'll have to test those yourself. No need to worry about those with only 1 or 2 alarm triggers.

[MENTION=5867207]vaisakh7[/MENTION], this is a 0% [0.0%/h] guide after all and so far I'm the only one who's posted [0.0%/h] drain with WiFi always on and GPS on high accuracy while maintaining push notifications. I'm just waiting for someone who can get the same.
[Android General] Maddyraj:
Bro i'm not greedy i'm trying to learn how to use amplify effectively ..

---------- Post added at 05:13 AM ---------- Previous post was at 05:10 AM ----------

Next time i'll test using wifi on and gps on.. will get back to u soon
[Android General] netyang:
Great job. Really works. Only one thing for me is Google fit cannot wok.
[Android General] pawwaap:
Yes, put your advise in place, frozen eWeather, Servicely and the log just after 3h looks like this:

http://cloud.tapatalk.com/s/5922dd6a9b11a/BetterBatteryStats-2017-05-22_143331159.txt

It seems now Automagic poses a problem, doesn't it?

Processes (requires root / system app on Android 4.4+) ===================================
system (System): Uid: 1000 Sys: 33 m 9 s Us: 1 h 16 m 43 s Starts: 0 *wakelock* (ch.gridvision.ppam.androidautomagic.Automagic Premium): Uid: 10128 Sys: 11 m 56 s Us: 27 m 8 s Starts: 0

Chuwi Hi10 plus, [ROM][13.12.]-Remix-OS-2.0-(Android-5.1.1)-for-Chuwi-Vi10-Plus,-Hi10-Plus,-Hi10-Pro,-Hibook,-Hibook-Pro-&-Hi12#entry2280114]RemixOS LP
[Android General] DB126:
- device was awake for just 11s (!!) during 2½ hour sampling window

- WiFi radio on for ~15 min; possible source of drain

- if concerned about automatic disable it; not a drainer IMO
[Android General] pawwaap:
If so what is it:

Processes (requires root / system app on Android 4.4+) ===================================
system (System): Uid: 1000 Sys: 33 m 9 s Us: 1 h 16 m 43 s Starts: 0
*wakelock* (ch.gridvision.ppam.androidautomagic.Automagic Premium): Uid: 10128 [B]Sys: 11 m 56 s Us: 27 m[/B] 8 s Starts: 0

And what does this "Sys: 11 m 56 s Us: 27 m" stand for?

---------- Post added at 06:40 PM ---------- Previous post was at 06:00 PM ----------

And here is log emerged right now, without Automagic, Servicely nor eWeather (just Amplify and Greenify):http://cloud.tapatalk.com/s/5923311450758/BetterBatteryStats-2017-05-22_203113354.txt

It's just bit better, 0.2%/h, but there is still:

system (System): Uid: 1000 Sys: 1 h 41 m 53 s Us: 3 h 53 m 23 s Starts: 0

What is it?

And I need eWeather, need help how to tame it?

Chuwi Hi10 plus, [ROM][13.12.]-Remix-OS-2.0-(Android-5.1.1)-for-Chuwi-Vi10-Plus,-Hi10-Plus,-Hi10-Pro,-Hibook,-Hibook-Pro-&-Hi12#entry2280114]RemixOS LP
[Android General] DB126:
Not certain in this context; ticked up counters but did not contribute to drain in a meaningful manner. Disable/uninstall and reaccess if concerned.
[Android General] pawwaap:
And can't uninstall System :)
[Android General] DB126:
Quickest way to 0% idle (and active) drain. :)
[Android General] pawwaap:
And I need eWeather ;)
[Android General] DB126:
"Want" would be a better descriptor. As eWeather has been shown to be a modest (albeit not excessive) drainer and you scored near zero screen-off wake time you can now return to some of the earliest explanations for the remaining drop off during sleep. Enjoy.
[Android General] pawwaap:
Please, help with eWeather, as you can see from particular logs the situation only changed after freezing Automagic too, and only by merely 0.1%/h (from 0.3% to 0.2%) and it might fall into an error margin.

As you can see there is still something strange what makes these 0.2-0.3%/h and taking into consideration the battery volume (8.4Ah) this is remarkable amount of energy.

And the Servicely program should do its job, like it does on other phones, why is here the opposite?
[Android General] DB126:
- a batteries advertised capacity often differs significantly from actual capacity due to age, quality of components, misrepresentation and other factors

- an inexpensive USB 'charge meter' will reveal batteries true uptake capability

- devices can consume power at levels that are not detectable by BBS or other similar tools; similarly battery packs can 'leak' power as they age

- the older ROM and kernel on your device are not known for power efficiency

- I have little interest in optimizing the use of a specific application (eWeather)

- further efforts to optimize your otherwise well behaved device offer little community learnings/value IMHO
[Android General] pawwaap:
- an inexpensive USB 'charge meter' will reveal batteries true uptake capability

Have true uptake capability anything to do with drain rate measured by BBS (especially when measuring from a middle percentage point)?

- devices can consume power at levels that are not detectable by BBS or other similar tools; similarly battery packs can 'leak' power as they age

And the tablet is brand new ;)

And ok, will measure discharge rate when tablet is off.

- the older ROM and kernel on your device are not known for power efficiency

I have also Huawei T1 with KittyKat and after some tweaks it can last over one month without charging (idling).

And ok, have also LineageOS MarshMallow ROM for this Chuwi tablet, just flashed it and begin to measure with BBS, let's see.

Is it possible these entries in logs like:

system (System): Uid: 1000 Sys: 1 h 41 m 53 s Us: 3 h 53 m 23 s Starts: 0

have come from e.g. kernel inefficiency?

- I have little interest in optimizing the use of a specific application (eWeather)

- further efforts to optimize your otherwise well behaved device offer little community learnings/value IMHO

You know, there are some people using and experimenting with Chuwi Hi series, they would like to see the results :)
[Android General] cristixperia:
My stats from the last two days.

Using grennify + force doze + L speed, no amplify this time.

Expected to have more SOT :( but I think the main drainer is "cell standby" (weak signal).

Brightness was most time over 50%. [MENTION=5488402]Davey126[/MENTION] can you take a look on bbs log? Please :)
[Android General] DB126:
- no need for screen shots; everything is in the log

- nothing useful can be derived from log as it spans 38+ hours and numerous device states

- ideal idle power consumption study is 6+ hours of inactive time with <1 min screen on (see recent posts regarding BBS Watchdog processing)

- be sure to configure device as desired (eg: radios) before initiating study

- SoT is a highly subjective and largely non-reproducible​ metric that serves little purpose in this thread
[Android General] pawwaap:
Please, look at newest 10h log but this time taken on MarshMallow LineageOS:

http://cloud.tapatalk.com/s/5926c959e630d/BetterBatteryStats-2017-05-25_133840195.txt

As you can see the idle drain is still the same 0.3% in spite of carefully set up Automagic, Amplify, (and Greenify too).

In this situation it is better to return to system without Automagic & Amplify, would you confirm?

Chuwi Hi10 plus, [ROM][8.5.]-LineageOS-13-(Android-6.0.1)-for-Chuwi-Vi10-Plus,-Hi10-Plus,-Hi10-Pro,-Hibook,-Hibook-Pro-&-Hi12#entry2279219]LineageOS MM
[Android General] DB126:
Device was awake just 65 sec during 10+ hour monitoring window which is excellent. You are not going to improve that with software tweaks. Accept your device may be 'leaking' a small amount of power that BBS does not see. Other explainations (offered numerous times) include battery temperature between start/stop points, normal tolerances that yield small variances in reported battery level and/or a battery pack that holds less than advertised capacity. Get over the measly 0.3% loss per hour.
[Android General] pawwaap:
And Automagic and Amplify do you advise to freeze/uninstall?

Chuwi Hi10 plus, [ROM][8.5.]-LineageOS-13-(Android-6.0.1)-for-Chuwi-Vi10-Plus,-Hi10-Plus,-Hi10-Pro,-Hibook,-Hibook-Pro-&-Hi12#entry2279219]LineageOS MM
[Android General] DB126:
Personal choice. I don't use either but both are useful in specific situations. Last results were excellent (didn't read past first page of log) - why change anything¿?
[Android General] pawwaap:
Automagic introduces some overhead since waking up costs energy, but Amplify costs nothing, so maybe it is nice to use it?

And maybe to tame somehow with Amplify yet these alarms from the log:

android (): Wakeups: 5 (0.5 / h)
Alarms: 2, Intent: ScheduleConditionProvider.EVALUATE
Alarms: 1, Intent: com.android.server.WifiManager.action.DEVICE_IDLE
Alarms: 1, Intent: android.net.dhcp.DhcpClient.wlan0.RENEW
Alarms: 1, Intent: com.android.server.task.controllers.IdleController.ACTION_TRIGGER_IDLE

and with what frequency to limit them?

Chuwi Hi10 plus, [ROM][8.5.]-LineageOS-13-(Android-6.0.1)-for-Chuwi-Vi10-Plus,-Hi10-Plus,-Hi10-Pro,-Hibook,-Hibook-Pro-&-Hi12#entry2279219]LineageOS MM
[Android General] DB126:
Amplify also introduces overhead (minimal); more concerning are potential side effects which do not always manifest immediatlely or in the expected manner. Do not ask what they are; do your own research in this and Amplify threads to your draw own conclusions.

Not going to offer recommendations/suggestions for trivial items on a well behaved device.
[Android General] ProudRed:
In my motorola MOTO E when I am trying to determine my location on the map, it cannot locate it without me turning on wifi scanning. But on my other phones, It can locate easily.
[Android General] DB126:
Recent generation Moto E/G devices often exhibit this characteristic although first I have heard of the wifi scanning requirement. Common workaround is to enable Google Location Services even when not needed. You should continue this discussion in your device forum as it is not related to managing idle drain.

As an aside, I own a 4th gen Moto G (nice device given price point); hardware GPS performance is disappointing. Usually have to break out another device in congested areas with marginal satellite reception. Other Motos are fine. Likely cost saving components in the E/G series. Common complaint.
[Android General] ProudRed:
This is definitely due to limiting something as previously it was working fine. Thats why I put it up.

There is an issue with my OP3T, it cannot determine location from Facebook. But on Google map it can.

I have Moto X play as well.. all I can say is it is still a beast of a device.