yashsingh1/xdaforums huggingface dataset:
[Android General] ivy.lally:
Which other mod, Servicely? As only this is new in the system.

And should we allow BetterBatteryStat to convert into system application?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
Guidance was offered; follow it and see what happens. No, don't introduce yet another variable by converting BBS to a system app while trying to solve the first problem.
[Android General] ivy.lally:
And should system battery-optimize BBS or its better to put it on while list?

And I've done what you advised, reinstalled BBS and it works and allows for DeepSleep.

And again zero drain after 2h of idling its what BBS reports:http://cloud.tapatalk.com/s/58fe54ad07fe2/BetterBatteryStats-2017-04-24_212458725.txt

What should I do with the configuration of Greenify and Servicely combined? You've so criticized Servicely however it works, but it seems its more Greenify's job and Servicely just complements it in ungreenified services, like e.g. eWeather.

And maybe is BBS this optimistic

readings affected by the glitch and is wrong? How to check it up?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
Actually, I suggested Servicely as an alternative and don't recall leveling any criticisms of that tool. Must be my evil twin.

Zero idle drain = goodness. Have a beverage of your choosing and enjoy the day. No further optimizations needed.
[Android General] justjr:
Since I'm on Nougat and don't have Xposed, I started using Servicely to block ads and analytics services (mostly on OP), but not sleeping any app with it, and letting it to Greenify. Also trying ForceDoze to see what I'll get from it. If ForceDoze don't give me better results then Greenify on dozing I may get rid of it (may be hard to test that), same with Servicely. At least so far having no problems with functionality.

I also trying GSam Battery since BBS is giving me a lot of results with * around them, and wakelocks are almost all the same with the same execution time, very weird. May try to reinstall BBS like [MENTION=5488402]Davey126[/MENTION] said if I'm not satisfied.

Also, whats your guys prefer, BBS or GSam? I am guessing BBS (I always used BBS).

I might consider going back to marshmallow... I miss Xposed....

edit: sorry to clutter this topic with more offtopic stuff (not much, but it is), but I can't find alarms on GSam, anyone used it and know if it just don't track it, or it's mixed with other stuff in it?
[Android General] DB126:
GSam offers more of an executive overview; it doesn't track wakelocks directly and has no info on alarms, broadcast receivers, etc. Sometimes that perspective is more beneficial as folks often get bogged down trying to sort and manage individual components. That said, once a potential offender is identified in GSam the additional detail offered by BBS, WLD, SDMaid, MyAndroidTools, etc. can be quite helpful.
[Android General] ivy.lally:
As you might suspect it turns out less idealistic if after longer time of idling.

Please note review BetterBatteryStat log:http://cloud.tapatalk.com/s/58fef7f530bcd/BetterBatteryStats-2017-04-25_090445937.txt

It has reported drain of 0.2% (after >8h of idling) and you might say it's ok however it seems the culprit are clearly identified it could curb them (please say how?):

=======================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
ConnectivityService (Android System): 59 s Count:2 0.2%
*alarm* (Android System): 4 s Count:51 0.0%
RILJ (Phone Services): 4 s Count:119 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
PowerManagerService.WakeLocks (): 1 m 37 s Cnt:(c/wc/ec)147/2/0 0.3%
PMS^2265^ConnectivityService (): 60 s Cnt:(c/wc/ec)1/0/0 0.2%
PowerManagerService.Display (): 37 s Cnt:(c/wc/ec)1/0/0 0.1%

PowerManagerService, ConnectivityService, how to tackle then, not Servicely nor Greenify sees them on its list, maybe Amplify?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
Nothing amiss in BBS log:

- ConnectivityService wakelock of 58-59s is common in many kernels/ROMs as device prepares for sleep w/full network isolation; it does not need to be managed

- PowerManagerService typically reflects the accumulated wake time of all apps/services (including above) and also needs no direct management

- 0.2%/hr idle drain is excellent; even while idling you device requires some power; does your heart stop while sleeping?

- 133 sec wake time over ~9 hours (~32K sec) is outstanding; give it a break
[Android General] J-Hop2o6:
Servicely blocks ads? Can you tell me how? I'm using the Galaxy S8, so no root.
[Android General] ivy.lally:
I must probably return to your concept, if tested with BetterBatteryStats for a longer time, e.g. 8h it turns out solution with Servicely also consumes energy a little bit: 0.4% per hour: http://cloud.tapatalk.com/s/59008a3a863dd/BetterBatteryStats-2017-04-26_103527981.txt

As I can see waking up with Automagic and Amplify together activates even more CPU than Servicely.

What is better? ;)

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] justjr:
I gone back to stock, but I'm sure you can find the services button big on the app, theres no much options there, there's sleep apps and block services only. I don't remember if you need root, I think so, but try it.
[Android General] DB126:
WeatherClock process/widget responsible for nearly 80% of waketime in latest log. This drain have nothing to do with the tools being used.
[Android General] ivy.lally:
And how to improve this stats, does it mean Servicely doesn't stop eWeather despite it has it in its hitlist?

Would Amplify curb the process wakelocks?

I've tested Automagic Amplify idling for four hours, this is the results:http://cloud.tapatalk.com/s/5900ec7442b5c/BetterBatteryStats-2017-04-26_183554750.txt

As you can see it yielded even worse result: 0.9% per hour.

Would you suggest what to set in Amplify plug-in for automated screen-off?

It is what has made the results:

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
Done with this endless cycle of questions. Test, observe, action. Repeat until satisfied. Better yet - get rid of the damn eWeather app/widget that seem to be causing so much distress.
[Android General] J-Hop2o6:
I meant to type Galaxy S8, not S7. And it won't work since this isn't rooted.
[Android General] :
I do not think the two logs are comparable simply because battery drain is not linear.

https://android.stackexchange.com/questions/144760/is-battery-consumption-linear

If you want to compare them objectively then you should at least start from same percentage.

This probably will not help with the battery drain but I would suggest starting all plugins directly from the "screen off" trigger (as in my screen shot). There is no reason to run them one by one like that. Then they will all be executed simultaneously.
[Android General] CounterC:
Anyone knows what these huge wakelocks are?
[Android General] DB126:
Yes - but not going to write a novel explaining what you can find via a search. No need to action any of these unless there is a demonstrable link between excess (operative word) wake time and a specific trigger. Depending on the situation all those nasty wakelocks could simply reflect Android going about its business doing useful things that you know and expect.
[Android General] CounterC:
Thanks, I did an extended search on the job.delay and job.deadline already but found no "solutions", only users reporting their battery logs.

These wakelocks are variable though, one cycle they go until a few hundreds but these cycle they were almost 1000, that's quite excessive...
[Android General] DB126:
Not excessive - just Android functioning as designed. Don't fall into trap of reacting to raw data exposed by various battery/power management tools. Without context raw data is meaningless.
[Android General] pawwaap:
Please, consult this log:

http://cloud.tapatalk.com/s/591b8aac3eb97/BetterBatteryStats-2017-05-17_002200868.txt

It is strange, please look into this:

android (): Wakeups: 38 (5.2 / h)
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 0, Intent: android.content.jobscheduler.JOB_DELAY_EXPIRED
Alarms: 29, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 7, Intent: android.appwidget.action.APPWIDGET_UPDATE
Alarms: 0, Intent: com.android.server.NetworkTimeUpdateService.action.POLL
Alarms: 0, Intent: android.content.jobscheduler.JOB_DEADLINE_EXPIRED
Alarms: 1, Intent: com.android.server.task.controllers.IdleController.ACTION_TRIGGER_IDLE
Alarms: 1, Intent: com.android.server.WifiManager.action.START_SCAN

And the alarm

android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED

is responsible for awakening tablet >5 times per hour, what to do with it?

You may think as much as [0.3%/h] is ok but please consider the tablet's battery volume is 8400mAh so 0.3% constitutes a significant amount of energy.

Chuwi Hi10 plus
[Android General] Wilmerin:
Flashed stock rom, starting over!

Hello!

My phone got bricked, it start draining the battery very fast until it never woke up.

Did the precedure to umbricked following the guide in the sticky section of the forum. Flashed stock rom,

then rooted and then installed CWM.

After a few days testing and limiting, got a good stats on idle battery drain test and apparently the wakelock ste-gps-interface has gone.

However, I would like you to see my new stats and see what can I improve to get a better battery saving.

Thanks
[Android General] DB126:
Usage pattern (wake vs doze/sleep) time looks typical; actually quite favorable for Lollipop. An alarm 'firing' does not mean the device actually woke; depends what the receiver does. 5-10 alarms per hour is relatively low.

Appears the media scanner service was the top consumer and likely the driver behind a 60s sprint at max CPU frequency. Suspect you may have a largish stash of music stored on the device.

Battery drain does not always occur linearly with relatively small percentage drops not being representative of overall battery health or power actually consumed. In your case (50->48% over 7+ hours) the reported hourly fall off rate would be significantly impacted by a 1% change in either direction.

Also note battery temperature can have an impact on reported charge level. A 30F difference in battery temp can easily yield a 1-2% difference in charge level. Battery temp is usually somewhat higher when the device enters sleep than when it wakes.

---------- Post added at 03:40 AM ---------- Previous post was at 03:35 AM ----------

0.1% fall off per hour is excellent by any measure, especially for KitKat. Not going to dig any deeper. Enjoy your device.
[Android General] pawwaap:
And where can you see this data please? It seems there are just two references in the log to MediaScannerService, line 46:

======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
MediaScannerService (Media): 9 s Count:3 0.0%
*alarm* (Android System): 3 s Count:45 0.0%

and line 794:

"partialWakelockStats": [
{
"count": 3,
"duration_ms": 9902,
"name": "MediaScannerService",
"wake_type": 0,
"total": 26258242000,
"uid": 10006,
"uid_info": {
"m_uid": 10006,
"m_uidName": "Media",
"m_uidNamePackage": "",
"m_uidUniqueName": false
}

And how to improve it, is blocking, freezing MediaScannerService your advice, or Servicely, or maybe Amplify with Automagic?

At all, is MediaScanning in background essential for anything?

Chuwi Hi10 plus
[Android General] james.iha:
Im quite happy with my m4c battery drain after following this guide.

I've been using mi4c for 1,5 years, and for the previous 3 months i can only get 1h sot (auto brightness and always using celluler data, mainly for browsing, social media, whatsapp and no gaming) and my phone always turns off before it can reach to 50% in batt indicator (i think my battery is broken and i have tried to calibrate the battery without any success).

And now i can get 3h of sot, my phone doesn't turn off when it reaches 50%, and idle battery drain is very good. Not to the point of 0%/h drain but considering my battery is broken im very satisfied with the improvement.

Sorry, my english is poor. I want to post screenshot but always failed
[Android General] DB126:
Look under processes heading, third line.

No specific guidance other than avoid blocking wakelocks as it simply masks symptoms of core problem. Lots of info on the web about dealing with media related issues on Android. I have not experienced them personally (except on an old JellyBean device) and have limited experience in this area.
[Android General] pawwaap:
And as in articles found from Google the most frequent is advice to simple disable the media scanning service,

Question: need anybody scanning service and what for?
[Android General] DB126:
Scanning service indexes content using various meta data for rapid retrieval and organization. Generally not needed unless you have a huge library.
[Android General] pawwaap:
Please look here again, another log, the same Chuwi Hi10plus but different ROM: RemixOS LP:

http://cloud.tapatalk.com/s/591d85c89cb0d/BetterBatteryStats-2017-05-18_131636877.txt

And again, althouth it drains "just" 0.3% per h, since it has big battery 8400mAh this 0.3% constitutes big portion of energy.
[Android General] DB126:
Same general observations as before except no media related drain. Might take a look at deskclock/weatherclock (eWeather HD) as it showed a fair amount of activity during the monitoring window.

Your device is behaving normally with low wake time (3½ min) over 14 hours; quite typical for Android 5.x. Switching ROMs isn't going to lower that number significantly. Regardless of stated battery capacity your device is acting like a typical phone/tablet with a stock pack. You'll need to invest in a inexpensive USB charge meter (example) to determine true/current capacity. Also suggest recalibrating if not done recently.
[Android General] pawwaap:
And what is it you saying about: recalibrating and how to make it?

Yet about battery volume and percentage. You may think well about its predicting shown in battery stats however I also have Huawei MediaPad-T1 and with just LBE tweaks it keeps battery ready for over one month idling (It's battery capacity is half of this Chuwi Hi10plus).
[Android General] DB126:
Soft recalibration can be done from most ROMs from battery panel (look under gear and/or overflow menu). Some devices also support recalibration via firmware or vendor specific app.

Rated and actual battery capacity can be different due to design, age or defect. Your device was awake for 3½ min (much of it at the CPUs lowest frequency) and reportedly consumed 4% of packs capacity or ~1% per min of activity. At that rate your battery would last only 60 min while in use! Guessing that is not the case. Data speaks for itself. Either the pack holds significantly less than claimed, discharges in a non-linear fashion or there is a zombie consumer that BBS does not see. Take a deep breath and stop worrying about such a minor loss of charge. Is what it is.
[Android General] pawwaap:
Indeed, there is something weird with these readings as on average use battery keeps for 3 days without seeing charger. And it is intriguing as well, what could it be? ;)

You repeat this kind of advice very often to people in this forum, actually you act as psychologist counsellor here, don't you? ;)

And about eWeather as BetterBatteryStats reported, I use Servicely and eWeather is on its list of applications to switch off during sleep, it looks this Servicely doesn't work. And which Servicely version do you recommend, I used to use the two:

pro 2.0 and (presently) pro 4.0.6,

and have an impression the older one (2.0) had better reliability and completely different philosophy, would you recommend to revert back to version 2.0?
[Android General] DB126:
- no opinion on Servicely; suggest temporarily disabling eWeather to see if has a meaningful impact on wake time and/or battery drain

- average 0.2-04%/hr idle drain on three very different run-of-the-mill devices using stock ROMs with minimal tweaks

- so yea, "psychologist counsellor" comes out; no appetite for micro managing productivity gizmos; 80/20 (preferably 95/5) rule for me

Good luck.
[Android General] pawwaap:
And yet please counsel about this option in permissions: "prevent tablet from sleep" It is for every application set on and it seems the rationale is not disturbing in tablet sleeping, would you advise to switch off this permissions for almost every application though?
[Android General] DB126:
Temporarily keeps device awake during specific operations such as downloading/installing app updates from the Play Store. I generally find toggling that option 'off' has minimal impact on wakes or wake duration. Others make different claims. Likely app specific. BBS will normally expose offenders.
[Android General] Celestial Fury:
I see these which are in Post #2:

Alarms: 56, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED

Alarms: 17, Intent: android.appwidget.action.APPWIDGET_UPDATE

Follow the guide and you'll have minimum micro-management.
[Android General] pawwaap:
Amplify and Automagic combined are better for taming this kind alarms, don't you think?
[Android General] pawwaap:
Anybody knows why Amplify can't start in this RemixOS? And other Xposed modules work well, Amplify has been installed, activated as module, but after a boot when clicked its ui blinks for split second and stops, again the same.
[Android General] pawwaap:
It looks like it needs Google to launch, and it seems strange because on my Xperia with MarshMallow it didn't. Any clue why?

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] BorrowedTime:
A friend suggested to dowload Amplify but I have no idea what to do. I use a Note 3 with MagmaNX rom. Is there a guide on how the app works
[Android General] DB126:
Possibly different GAaps and/or Google Play Framework/Services builds as Amplify is known to run on Android 4.4.x to 6.x. See here for a sample of different builds from one provider.
[Android General] pawwaap:
And do you confirm Amplify needs Google to run? In another phone, Xperia Aqua MarshMallow, I run Amplify with every Google component frozen. Amplify can see it as if the whole Google was uninstalled, can't it? And here, in LP RemixOS it needs an Google account been logged in and running! It is strange.
[Android General] gh0stzk:
On cm 12, lineage 13, i run amplify without google services, but u need to install a version before latest version, i dont remember but last version is 3.3.7, u need to install 3.3.6
[Android General] DB126:
Believe Google account is needed for license validation, at least on the final (terminal) build. Note Amplify is effectively abandonware; 3.37 was the last release.
[Android General] pawwaap:
Even v3.37 if installed from Xposed installer (instead of Play) it launches, works, and says what it needs a propos donations :)

It needs Xposed installing method (why is in Play so?)

---------- Post added at 02:03 PM ---------- Previous post was at 01:53 PM ----------

Yes but is it worth to use Automagic combined with Amplify plug-in to set problematic wakelocks and alarms as 999999 when screen OFF,

and to return them to normal when screen ON?

And maybe the Amplify itself, with settings from post #2, does its job perfectly and introducing additional application for such automation is exaggeration, and it adds new self wakelocks too?
[Android General] Oswald Boelcke:
There are several threads on XDA available talking about Amplify; just use the really powerful XDA search.

And in every thread you have the first post (normally also called OP) that is most often describing details regarding the subject application, ROM, kernel etc. Just give it a try with the first post of this thread.

Great you followed your friends advice; however, did he/she tells you that your device must be rooted and running the correct version of Xposed for Amplify to work? If you're rooted on a Nougat ROM, Amplify won't work as no Xposed for Nougat is available (yet?).
[Android General] Wilmerin:
New stats! Thanks for your advice.

Awake (Screen Off) (): 1 h 16 m 24 s 18,3%...

"cw1200_wlan" (): 50 m 59 s Cnt:(c/wc/ec)1812/0/1812 12,2%

200 MHz (): 1 h 4 m 6 s 15,3%

What can I do to reduce awake time?

Thanks
[Android General] DB126:
Old device w/JellyBean ROM; many modern tools won't run on that platform. Thoughts:

- power consumed admirably low given high wake time including 11 min at max CPU frequency

- did not notice any 'out of control' user apps keeping device awake

- largish download from Sony app/service "dispositivos" (??)

- well known network wakelock is present for this generation of hardware

- try disabling WiFi while sleeping

- if the above doesn't help consider disabling mobile radio or use airplane mode while sleeping

- some claim older routers are at fault; personally wary of this explaination
[Android General] Celestial Fury:
Take an idle battery test but turn on and off the screen every hour. Then read the log.

First link in Google search. Router problem apparently. And your data was on as well.
[Android General] pawwaap:
I see your point but in case of tablet with big screen it is hard to predict how often the screen will be ON & OFF. It will be irregular, longer spells of inactivity interrupted with whimsy hysterias of longer activity ;) (activity spells with many screen ON/OFF interruptions)
[Android General] pawwaap:
Please, take a look now into the present log just after applying rules from post #2 with Amplify: http://cloud.tapatalk.com/s/591f69bf75523/BetterBatteryStats-2017-05-19_234127184.txt

As you can see little has changed, there's still 0.3%, and what intrigues is this Elecont eWeather records:

=========================================
Wakelocks (requires root / system app on Android 4.4+)
=========================================
android:*alarm* (System): 2 h 20 m 43 s Count:22 37.4%
*alarm* (com.android.deskclock.Clock): 2 h 20 m 43 s Count:1 37.4%
*alarm* (com.Elecont.WeatherClock.eWeather HD): 44 m 11 s Count:1 11.8%
android:SyncManagerHandleSyncAlarm (System): 8 s Count:23 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
...
=========================================
Processes (requires root / system app on Android 4.4+)
=========================================
system (System): Uid: 1000 Sys: 1 h 19 m 35 s Us: 2 h 22 m 12 s Starts: 0
*wakelock* (com.android.deskclock.Clock): Uid: 10037 Sys: 45 m 11 s Us: 1 h 13 m 47 s Starts: 0
*wakelock* (com.Elecont.WeatherClock.eWeather HD): Uid: 10098 Sys: 12 m 46 s Us: 19 m 12 s Starts: 0

Please, explain how2 interpret this data?

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] :
I would say say, especially for the widget wakelock. It does not have to be Automagic though as any automation app will likely suffice. There are lighter alternatives (eg. Llama) if this is going to be your only use for the app.
[Android General] pawwaap:
You know, if introducing such an infrastructure (automation) it tempts to use also for other things, sky is the limit ;)

And Llama is lighter in sense of wakelocks and power use?
[Android General] DB126:
Macrodroid and Edge (Xposed module) are other alternatives that remain in active development. Tasker is unquestionably the most powerful tool but has a step learning curve for those lacking technical/programming background.

---------- Post added at 02:10 PM ---------- Previous post was at 02:06 PM ----------

Data speaks for itself. Dump (freeze/uninstall) eWeather and (arguably) deskclock; see what happens.