yashsingh1/xdaforums huggingface dataset:
[Android General] DB126:
Also own a 2nd gen Moto X (mini variant); great device.

To test your hypothesis simply disable Amplify and Greenify in Xposed, reboot and see what happens. You can go further by uninstalling Greenify and any other power management tools. Leave Amplify installed but disabled so you don't loose your settings (benign if disabled in Xposed). If things start working again layer on tools and settings until you identify the culprit. Better yet, see how you device behaves without the power management cocktail. Results may be surprising.

If a regular reader of this thread you likely know I'm no fan of Amplify. While it can (and certainly does) help in special situations the side effects of wakelock blocking/limiting can be subtle and difficult to track down. Power savings are often minimal as wake locks themselves do not drain; people get all whacked out over big numbers reported in Amplify (GSAM, WLD, etc) that are typically meaningless when taken out of context. Really shouldn't need aggressive wakelock management a contemporary​ Moto device if running stock ROM.

Good luck.
[Android General] ProudRed:
I can confirm, disabling amplify allowing me to access location on map.
[Android General] Celestial Fury:
Location alarms are in blue in Post #2.
[Android General] Asiier:
Hey guys!

Have been a while since my last post here, anyways, I have some questions for you guys.

I know that this stats are not done with minimal SOT and all that things.

Over night my phone sleeps pretty well, taking into consideration that I'm on 7.1.1, which means niether Xposed or amplify are available.

The problem is over the day.

I use Bluetooth a lot, I have a Huawei Watch and a Bluetooth earbus.

The first problem comes here, Bluetooth_timer wakelock is huge, and behaves really weird, while my screen is on the wakelock is continuing or at least when I'm looking at it via BBS, sounds weird but it's like that.

If I don't connect my earbuds in all day the wakelock stays pretty tamed but If I do it gets wild and can keep my device awake for hours. I have tried several ROMs, Kernels and method to kind of stop it but no luck.

I wanted to know If anybody knew something about it and could help me out.

Second thing, my partial Wakelock, they are really messed up.

As you can see on the picture most of them are *alarms* and *launch*. I do know it's a necessiry wakelock but either is not getting detected properly or something is ****ed up.

I have never gotten such huge *alarms* and *launch* wakelock and I said it might not be detecting properly because some apps that are shown there have been opened in all day or they are straight up Freezed!

Don't mind my alarms, I'm not sure what happened with BBS​ that the alarms looks like that, but they are normal anyways taking into consideration I don't have Amplify installed.

In summary, what the hell I can do about Bluetooth_timer wakelock and my hours long *alarms* and *launch* partial wakelocks.

Thanks you for your time :D
[Android General] DB126:
- screen-on wakelocks are irrelevant; ignore them

- most devices/ROMs must remain awake (screen off) in a low power state while actively supporting a bluetooth device

- device should doze if BT buds are plugged in but not being used (nothing playing); failure to fall asleep could be a kernel or ROM issue

- this thread is dedicated to minimizing idle (screen off) drain; may want to post elsewhere if having screen-on issues
[Android General] Asiier:
- I know that they are irrelevant, I just found funny that they worked like and If it was any sort of explanation. And does it counts as Awake and not as Screen On (on BBS)?

- I see, that explains with my earbuds can keep my device awake all the time. Plus if I have my earbuds connected I'm most likely playing music.

- Is there anyway I can measure that wakelock only when the screen is off (all over the day), I mean, BBS is reading it even when the screen is on and I want to see how big of a problem it can be when the screen is off.

- So all those alarms* and *launch* are normal?

- Yeah, I know that and I just want to improve my off screen drain, I'm happy with my screen on drain. In fact, I have a thread about that for the OP3/T

And thanks you for your reply :)
[Android General] ivy.lally:
Please take a look into this:http://cloud.tapatalk.com/s/592c42a0263ef/BetterBatteryStats-2017-05-29_121552332.txt

after 12h of idling with 0.3%/h, and this is Xperia Aqua with small battery (2600mAh) and this is why would like to minimize draining at least in idle sleep. In this test Automagic is used intensively and please advice what else to add to it's flow to exclude alarms and wakelocks?

Aqua E2303, MM modded, SkyMelon
[Android General] DB126:
See here for detail on creating an idle log (screen off->screen on). Alternatively, see post #3 in this thread.
[Android General] Asiier:
As I said before, my device sleeps okay over night the problem is during the day.

Where I use it, then I leave and repeat.
[Android General] DB126:
Procedure can be used for any screen off operations; not confined to 6+ hour "no touchy" window. Longer durations are better but even a brief period may yield some insights. In this scenario it may be best to set watch dog service option to 'unlock' vs 'screen on'.
[Android General] prosnz:
Hey I'm really new to this topic. Sry if I'm in the wrong place.

But if I am at work my battery drains really bad in screen off.

Can someone be so kind and give me some advice?

Thanks
[Android General] DB126:
Read the first three posts in this tread then create an idle log for analysis. Just because you are new to a topic doesn't absolve you of the responsibility for doing preliminary homework. As it appears you are also new to XDA keep in mind it is always best to consult the "OP" (Original [first] Post in a thread) before asking for help. Often the answer is right there for the taking.
[Android General] :
Have you actually tested if all those in fact drain battery?

Even if they do, limiting data and WiFi alarms and wakelocks like that is extreme. You may as well just disable mobile data and WiFi all together and gain even more battery life... because they won't work properly with those limitations anyway.
[Android General] prosnz:
Sry something went wrong uploading the log.
[Android General] DB126:
This log can't be used as it contains 2+ hours of 'screen on' time. Suggest enabling Watchdog processing in BBS (procedure) to simplify idle log creation.
[Android General] pawwaap:
And another problem: Antivir Kaspersky, need its alarms and wakelocks limiting in DeepSleep?
[Android General] TheKaptan23:
I need help. Something is consuming the battery and I can't find.
[Android General] peterlee928:
fyi

if u havent already

post ur bbs log

in the thread below as well

https://xdaforums.com/showthread.php?t=1179809&page=3219

cheers
[Android General] TheKaptan23:
Bro I don't know good English. So I don't understand a lot of you said. Please, you will should speak basic English. What should I do step by step? Could you tell me?

SM-A9000 cihazımdan Tapatalk kullanılarak gönderildi
[Android General] peterlee928:
post your better battery stats log

to this link also

https://xdaforums.com/showthread.php?t=1179809&page=3219
[Android General] Oswald Boelcke:
Your dump file is not usable as it started at boot and not when you unplugged your device from the charger. Additionally, it only contains 47 minutes and 28 seconds, of which the screen was on for 10 minutes and 29 seconds.

Why did you decide to post in this thread? Are you running XPosed and Amplify as required by post #2 of this thread?

Like peterlee928, I also suggest to use the thread "[APP][2.1+][7 jan. - V2.2.2] BetterBatteryStats" and read its OP (the OP is always the first, opening post in a thread).

If available enable WiFi and enable mobile network. Charge your device till it's (nearly) full and unplug. Now, leave your device alone and at rest for about six hours. Don't touch it, don't use it, don't turn the screen on. Screen on time must be less than one minute.

After the six hours take a dump with the settings "since unplugged" until "current".

Post the so called idle dump in the above mentioned BBS thread and wait for support.

As far as I remember double posting is not well noted on XDA.
[Android General] DB126:
Actually, don't. Pick one forum/thread and post there. If responses prove unhelpful try a different forum/thread. Double posting is frowned upon.
[Android General] Oswald Boelcke:
@Davey126: I know you had it explained much better and more precisely than me here. Just tried to be as easy as possible.
[Android General] DB126:
Well defined. Only suggestion is enabling BBS watchdog service which simplifies capture and permits mid-charge analysis which can be more accurate that starting immediately after unplug (typically 100% charge).

https://xdaforums.com/showthread.php?t=1179809&p=72467976
[Android General] Oswald Boelcke:
Oh, I've bookmarked that great post already. Due to the possible language barrier I just intended to initiate a first start in the hopefully correct thread, hoping to continue with further support and guidance afterwards. Please don't mind but I know that your wordings do really suit that intention, too.
[Android General] TheKaptan23:
Thanks man. I will try than send post:good:
[Android General] peterlee928:
ah thx for that note

given he posted a bbs log

i thought it was more pertinent

for him to post there

in any event

duly noted

:)
[Android General] TheKaptan23:
This time, Is it correct ?
[Android General] Oswald Boelcke:
Yes, looks to me fine and pretty decent with a drainage of only 0.7% per hour. However, I think the Awake (Screen off) time is still slightly high.

Did you take the log while being in Airplane mode? I guess you should take another one but with WiFi enabled (if you have WiFi) and mobile data enabled.

Further, I suggest to follow this procedure by @Davey126 who is a real expert in limiting battery drainage and to post the new log in this thread only.

Additionally, please inform if you are using tools like Greenify, Amplify, AppOpsXposed etc.
[Android General] DB126:
Undeserved recognition; XDA is a community where various members share their time, talents and experiences to assist others.

Fully concur with [MENTION=7408621]noc.jfcbs[/MENTION] observations. Also wonder if the Greenify option "Doze on the Go" is enabled (requires Xposed framework) which is critical​ to limiting wake time while the device is in motion and permitting the device to enter doze mode more rapidly during screen-off operations on Marshmallow.
[Android General] TheKaptan23:
Thank you very much. Yeah, I'm using Greenify, Ampfily, AppOpsXposed and PowerNap. For CPU, I use Synapse.
[Android General] SSEmonBD:
Great help

It was really useful.Now I guess I can use my battery life more efficiently.
[Android General] ivy.lally:
Please take a look into this log http://cloud.tapatalk.com/s/593e75798fab7/BetterBatteryStats-2017-06-12_125609561.txt

of 11h idling

And what's weird is this Doze Idle Mode Time (): 4 h 26

==========
Deep Sleep (): 11 h 49 m 40 s 99.8%
Awake (Screen Off) (): 39 s 0.1%
Screen On (): 38 s 0.1%
Wifi On (): 1 m 34 s 0.2%
Wifi Running (): 1 m 34 s 0.2%
Doze Interactive Time (): 38 s 0.1%
Doze Idle Mode Time (): 4 h 26 m 47 s 37.5%
Doze Idling Time (): 4 h 26 m 47 s 37.5%

Aqua E2303, MM modded, SkyMelon
[Android General] DB126:
Err...device was awake for a whopping 38 sec over the course of nearly 12 hours with a total loss of 2% (~0.2%/hr) the majority of which was likely used to maintain the SOC, memory, radios, etc in a minimal power state. Nothing to look at. Various reported doze states are irrelevant.
[Android General] ivy.lally:
And what about application for playing music, e.g. Xperia's Music? After applying the tweaks from this guide and Greenify Music stifles after screen turns off now.

Aqua E2303, MM modded, SkyMelon
[Android General] Celestial Fury:
Music works fine for me with screen off. See Post #3 How to find problems with limited alarms/wakelocks.
[Android General] ivy.lally:
Please forgive me, it is about CPU underclocking and governor tuning. If very low minimal frequency and power saving interactive governor parameters are applied then Music stifles on screen OFF. It is still interesting when screen is ON it plays correctly with the same settings.

(Also it plays normally on screen OFF with bigger parameters.)

Anybody knows why?

Aqua E2303, MM modded, SkyMelon
[Android General] DB126:
Seems obvious. Analogy: I press the accelerator peddle down 5% but my auto won't climb the hill. Solution: give it a little more gas. Good chance device is going into deep sleep (doze) after a period of screen-off time at low frequencies.
[Android General] ProudRed:
Safe to limit any of these alarms ? Too much drain in idle state. http://cloud.tapatalk.com/s/594527cc5b6fe/Screenshot_20170617-153245.png?
[Android General] Celestial Fury:
Post #3 Last line in red.
[Android General] ProudRed:
I am following both and have merged together. Thats why.

Let me know if you can help me with a suggestion.
[Android General] Celestial Fury:
You cannot merge threads. I suggest you follow XDA's rule number 5. It's the only rule I've explicitly stated for posting in my thread.
[Android General] DB126:
Just don't. Suggestion posted in other thread. Will look at your idle log should you decide to post it (in one thread...your choice).
[Android General] ProudRed:
If you are saying that I cannot follow both the threads to configure my amplify then I must tell you that couple of weeks back someone told me in this thread of the other thread that I can merge both, I will try to quote that post if I can find it.

So shall I use only one thread to configure my amplify ?
[Android General] Celestial Fury:
You can follow as many as you like but you can't merge threads (unless you are a forum moderator). You can't post the same thing more than once. If you don't get an answer or one that you're satisfied with in other threads then you can ask here.
[Android General] ProudRed:
By merging threads I meant, I merged the inputs from both the threads into my amplify. There is no harm in doing that right ? Thats the reason made post on both the threads as it had input from both.
[Android General] FaustTN:
I don't know why but I seem to have 10 alarms fired and 99 blocked, and Amplify does not list any alarms.

Is anyone having the same problem?
[Android General] DB126:
Reset Amplify stats from home page then wait a few hours for data to accumulate. Better yet consider whether Amplify is really helping to reduce battery drain. It can in some specialized situations; most of time the savings are minor relative to side-effects, potential loss of functionality and the time/effort involved in setting-up and subsequently monitoring for aberrations. If unsure submit a BBS idle dump for analysis.
[Android General] Celestial Fury:
I'd disagree. Amplify may no longer be in development but AFAIK it's the only one of its kind and it does the job. The wheel is also the only one of its kind and there are only so many ways it can be developed further. Here are some of the myriad ways Amplify helps you:

Location alarms

(Post #2 in blue)

Nav apps don't use them. Mainly Google for their 'collection'. Fancy having your GPS activated when you're not using it? This is the way to go.

CONTEXT_MANAGER_ALARM_WAKEUP

This is a relatively new addition with repeating newly created random numbers which is impossible to restrict without regex blocking code added to Amplify.

Analytics

I count 5 alarms, 1 wakelock, 5 services from Android LP alone.

Certainly there are side-effects. That's why there's a guide which has been updated whenever a side-effect has been found by me or other readers of this thread. It has been a long time since one has been found so I'd say the guide has been pretty stable for some time. XDA is also all about tinkering and Amplify as an Xposed module is a lot safer as nothing is permanently changed.
[Android General] DB126:
First and foremost a sincere tip-of-the-hat for the tremendous work you have put into this thread and especially the first few posts (guides). Regardless of what follows you have earned a spot in the XDA hall of fame for your selfless contributions.

Amplify is a good tool (despite the lack of recent development) and certainly can help those looking to squeeze the last drop of power from their devices.

That said, the wakeups referenced typically do not cause excessive drain on modern hardware. Yes, some trigger actual wakeups (or delay deep sleep) but the impact on battery life is minimal on most devices/ROMs. Yes, there are exceptions (especially older devices/ROMs) not to mention those that loath the power consumed - even if small.

In some cases there are alternative methods that are arguably easier and/or do not impose side effects. For example, I permanently disable FireBase analytics at the service/broadcast receiver level and enforce those settings with MyAndroidTools Xposed.

As for location services, using "device only" eliminates most wakelocks associated with Google's enhanced location services; the latter can be switched on as needed (eg: indoors). Most ROMs and modern devices only enable the hardware GPS when needed; gone are the days of power hungry GPS receivers decimating battery reserves when not in use.

Finally, Amplify takes time and effort to initially configure and work through various issues that can arise - even using your excellent guide. In most cases battery life is only marginally improved. Sometimes drain actually increases. The challenge to readers is deciding whether the potential benefits outweigh the time investment - especially on newer devices and Android builds.

I think we can agree that XDA is all about development and "tinkering". Your guide and the collective experiences of those who have contributed to this thread allow members to make intelligent decisions on how they choose to manage their devices.
[Android General] Celestial Fury:
The location alarms mentioned (as well as many others) most certainly still drain on LP. I can't speak for MM since I'm still on LP. GPS on device only renders Google Now/Google Maps less usable. While purists would advocate going Google-less, those apps and the Play Store are important to many.

I do consider disabling receivers to be less safe as can be seen in Post #1 because uninstalling the disabling program does not restore the receivers and if problems arise in a future update you might not remember what you had disabled. I doubt if Firebase is the only Google analytic or there wouldn't be multiple Google analytic alarms and services. Amplify like any tool is just a tool and different tools seem to catch different things.

The thing is, asking readers to consider whether Amplify is really helping to reduce battery drain in an Amplify-related thread seems akin to an anathema.
[Android General] DB126:
Yes, I see your points although don't necessarily agree with all. I'll refrain from a point/counter-point discussion for the benefit of readers who probably don't care for that level of engagement in a public forum.

You and countless others are are obviously comfortable with Amplify and the way it fits into your workflows. I have no doubt the benefits (by whatever measure) are real, reproducible and significant.

I used Amplify for nearly 10 months on several KK and LP ROMs. Over time I realized that while alarms, wakelocks and actual wake time were often reduced the impact on battery life was insignificant relative to other strategies. I also experienced several undesirable (and not immediately noticable) side effects despite very conservative settings. Eventually I abandoned Amplify and have not looked back. Idle performance rivals the best that are reported in this thread and elsewhere. Others have had a similar experience. However, not everyone. Some returned to Amplify after observing a negative impact after disabling or uninstalling. Not many - at least among the community that report back.

I have tried to use words like "consider", "check", and "verify" when suggesting Amplify may not be the best solution. However, in the haste of engaging dozens of posts each day (and still have a life outside XDA) my tone sometimes becomes abrupt. I'll try to be more careful going forward. That said, abstaining from a candid discussion of Amplify along with other solutions would be disingenuous to the members who come here with battery life concerns.
[Android General] :
I think that the real problem with Amplify is that it requires Xposed. Unless there is any progress regarding Xposed for Nougat or a new tool with similar functionality is released, Amplify will likely become obsolete very quickly. At the moment I would not give it more than 2-3 years. This is also one of the reasons why I think it is beneficial to look for alternative methods to tame down wakelocks, the sooner the better.
[Android General] :
App named "Wakeblock" by the author "Giovanni Bozzano" available on playstore appears to be an interesting find. The app currently in its alpha stages of testing. It claims to act without the need for Xposed. Has anyone actually tried it out?
[Android General] Oswald Boelcke:
I'm very grateful that I was privileged to follow this real interesting discussion. While I was on Marshmellow I used to use Xposed and Amplify; a habit that obviously had to change since I moved to Nougat.

Please allow me to share my point of view after quite some time with and without Amplify. I believe Amplify (but only in conjunction with this thread and its OP as well as the others few threads covering Amplify) is a great tool and has been an invention like aspirin more than 100 years ago. I think I liked Amplify so much as I hadn't too intensively think about the processes in my devices; together with the great recommendations in the mentioned OPs I got a pretty straight forward tool to use - and I'm convinced this applies to other users, too.

Meanwhile being on Nougat, I had to change my strategy, was forced to look deeper into my system and to try to understand what is why going on. Now, after more than six months without Amplify I can clearly state that I was able to even more decrease my battery drainage than before with Amplify.

Bottom line: Amplify did its job - like aspirin for me that reduces fever and removes the headache while I must accept a possible gastric ulcer or other adverse effects. If Xposed were available for Nougat I'd most likely going to continue utilisation of Amplify. But without Xposed and in turn without Amplify, I was forced to look for the causes of the fever, headache and high value of leucocytes. And I think it was pretty effective to treat the cause instead of minimising the effect.
[Android General] tanago:
Hey, do you mind helping me out. I'm running Nougat too and I get 2-5% battery drain overnight. What tools should I look in to minimize this drainage? My device is rooted.
[Android General] DB126:
Fair assessment of Amplify and alarm/wakelock blocking in general. The last statement captures my views and the strategy I choose to pursue: addressing the problem (ideally root cause) vs masking symptoms. There is significant misunderstanding over how wakelocks work and the true impact on actual wake time. Big numbers don't always equate to big drain. I'm also comfortable accepting a modest increase in wake time in exchange for 'passive management' as most modern devices/kernels/radios/sensors/roms/etc idle efficiently when properly configured. Idle battery drain on my varied devices hovers in the 0.2-0.4% per hour range with few restrictions. Not "extreme" by any means but perfectly acceptable given personal objectives. Boils down to active vs passive (lite touch) management style which often mirrors the preferences of the device owner vs being driven by necessity. As always, different strokes for different folks. :)