yashsingh1/xdaforums huggingface dataset:
[Android General] Jrhotrod:
He just said to not block wakelocks, so there's no need to keep Amplify. I'm not sure of the function of Powernap though, and can't provide any recommendations since o haven't used it myself.

Additionally, there's no need to add multiple question marks to your inquiries... We all know you're asking a question.
[Android General] DB126:
Jetton Amplify. I see no significant benefit to PowerNap on Android 7+; knob/dial turning for the sake of knob/dial turning. I'm sure it makes someone feel better. If it makes you feel better by all means turn that knob/dial.

---------- Post added at 11:10 AM ---------- Previous post was at 10:56 AM ----------

Doze, permissions, Google and user focus on power management (app developers are listening). Modern devices/kernels *designed* for Android 7+ are generally more power efficient all else being equal. Slapping a new ROM/Kernel on an old device generally doesn't not yield the same results.

You visit power management threads with sufficient frequency to know the answer to your other question. If not fond of third party tools like BBS, GSAM, etc. simply use the stock battery tool in Android. Big hitters will quickly bubble to the top. Those who crave a bit more can examine Process Stats under developer options. Common sense prevails; dump the big hitters or seek out 'lite' alternatives. Don't concern yourself with the 'why' or trying to control the behaviors of a crappy app (eg: wakelock/alarm blocking). Doing so simply rewards the developer for careless coding. There are always other options. Enjoy time using your gadget vs managing it.
[Android General] f.a.tonmoy:
I lost 10% battery overnight after uninstalling Amplify and powernap where I used to lose only 1-2%

what kind of steps should I take to prevent that extra drain?
[Android General] mattie_49:
Reinstall amplify. No matter what anyone says. I've been on this wakelock kick. There is absolutely no way to stop Google Play services and unnecessary background apps without it. I'm running latest Oreo sense builds on am HTC 10 . I've tried both ways despite everyone saying amplify isn't needed on Android 6+. Well I have news for you and everyone else here reading. Without amplify and naptime. I get maybe 13 hours off charger and 2.5 to 3 hours on screen. Then I'm charging. With amplify and naptime functioning. I get 1.5 days off charger and 6 and a half hours on screen. Do what you like but the products are proven to work if you have the time and effort to figure out what your blocking and limiting. Hope this helps and I'll use both apps and donate till they no longer are needed. And unless your in some corner of the earth where your running some outdated version of Google Play services. YOU NEED them. Hope this helps my friend.
[Android General] DB126:
You need to identify and address the culprit(s) which is almost always an app running amok in the background abusing its presence on your device. Some claim Google Play Services is the culprit - but it rarely is. Most apps leverage Google services for core functions which makes it appear Google is the bad boy.

Blocking alarms and wakelocks simply addresses the symptoms and not root causes. Amplify and similar tools are well known contributors to bizarre side effects which really aren't that unexpected once one understands what's really happening under the covers. Most devices will happily idle at 0.5-0.8% per hour drain. If your looking to go below that then prepare to loose some functionality (which may or may not matter to you) and deal with side effects which may not be readily apparent.

Pick your poison. If Amplify, Powernap, endless tweaking and the cocktail of other tools and techniques advocated in this thread work for you then have at it. Alternatively, figure out which apps are misbehaving and pick resource friendly options. Bad actors aren't hard to find once you start looking. Social apps are often the biggest offenders.

There will always be the 5% club that advocate for extreme measures. You'll find them in this thread and can be counted on a few hands. The vast majority of Android users, including a much larger pool of Amplify expatriates, suffer no such issues or can quickly address abusers with a few simple adjustments.
[Android General] f.a.tonmoy:
Thanks for the info...
[Android General] lazostat:
I can't find Smart Network app, is there an alternative?​
[Android General] Isley_FR:
Hi, after a couple months here's some feedback.

Eventually I removed amplify altogether, the only battery-extender I have no is Greenify (root version). The good news is I receive all incoming calls on time now. The bad news is, event notifications are still unreliable. When they arrive at all, the arrive late.

Most of the time what happens is that I know I have an appointment at like 3pm. By default I should receive a notification A hour before that. At 2:15 still no notification so I 'open' the smartphone, check the event to make there was a reminder for it (there always is) and put it down. A couple minutes later : notification chimes in. It's like the notification system sleeps with the phone.

My calendar is not battery optimized so this shouldn't happen. I use aCalendar but the problem is the same with Google Calendar.
[Android General] strongst:
Acalendar needs for proper functionality google calendar, there's a warning in Acalendar settings when you here's no Google calendar. It's only necessary if you use Google calendar items for correct reminders. Maybe that's the issue.

But I would freeze greenify to double check and test :good:
[Android General] lklaus:
I'm using aCalendar, but not with Google but with davdroid. It's far from the top of battery suckers (FP2, LOS 14.1)

Klaus
[Android General] strongst:
I do use exactly the same combination :svetius: I don't exclude aCalendar or davdroid from battery optimization, notifications are working properly on Android 8.1.
[Android General] Isley_FR:
I freezed Greenify like you suggested, and it seems notification work fine now. I'll do more tests to be sure though. It's weird because neither Google Calender nor aCalendar were greenified. Maybe my settings were wrong somehow.
[Android General] DB126:
Enabling aggressive doze or shallow hibernation can trigger such behaviors. Stick to the defaults.
[Android General] Isley_FR:
I don't think I had aggressive doze on. I did have doze-on-the-go though.
[Android General] DB126:
Doze-on-the-go is generally benign but always best to test w/defaults and then set options one at a time to understand their impact.
[Android General] Fdraco10:
Will be possible UPDATE WAKELOCK and ALARMS TO LIMITS for NOUGAT??
[Android General] DB126:
https://xdaforums.com/android/general/guide-extreme-battery-life-t3095884/post76996896
[Android General] strongst:
What?
[Android General] drozo8o8:
Gsam reports that googe play services is using significant motion detector for quiet some hours every night on idle but it's not draining a lot I think. Any way to block that ? I'm on custom oreo and have amplify.
[Android General] DB126:
Why block it? Just asking for trouble.
[Android General] mattie_49:
Was just giving you props for always answering no amplify needed on Android 6+. I finally stopped using it. Only thing I did to get the same battery life and screen on time was go into each app individually preferably the ones continually running in the background. And tic don't allow to run in the background. Simple as that. It really is a fools game chasing alarms and wakelocks to limit and block. Finally getting all my notifications and calls as well. Big thumbs up. Thanks for helping talk me out of all that craziness. Big waste of time and quite tedious.!! I'm enjoying my device again.
[Android General] DB126:
Hey, glad to hear your device is fully functional again with equivalent battery life. You were a pretty strong proponent of alarm and wakelock management. Unfortunately, your experience mirrors that of most users who come to the conclusion that aggressive management isn't necessary and usually causes far more problems than it solves. Enjoy your liberated device!
[Android General] v7:
[MENTION=4250471]RohinZaraki[/MENTION] I use Delta GAPPS.It is often updated and I'm using it from the start of my custom ROM journey.

Tapped from my furious dogo ;)
[Android General] m0han:
bbs dump with wi-fi + data on (short duration). another with only data on (longer duration) with custom reference. rom is an older build that is thought to be free of the dialer-freeze and other bugs.
[Android General] v7:
[MENTION=4620757]m0han[/MENTION] There's no improvement with this ROM too.Is there any AOSP based ROM available for your device?Most of the Cyanogen based ROMs for your device seems to be buggy in one way or another.

There's no suspicious activity in the dump.A few kernel wakelocks and that's all.I know it's annoying asking you to switch ROMs everytime :o

Tapped from my furious dogo ;)
[Android General] v7:
[MENTION=4250471]RohinZaraki[/MENTION] Post both in-use and idle dump later.
[Android General] m0han:
that's kinda sad. i'm not sure if aosp roms can give me the customisation i love on the present rom (series). if you get time, can you please check here, here and here, or anywhere else, for what could be a better rom for me? :fingers-crossed: thanks. also, is this any good? :D
[Android General] v7:
[MENTION=4620757]m0han[/MENTION] I've looked into the forums.Every other ROMs I've seen have this dialer freeze issue.This is an bug from Cyanogen.You'll have to wait till a fix is implemented.

You could try the YUPHORIA OS from the YU forums.I'm not sure about the bugs/freeze issues.

The app you mentioned won't do any good.

Tapped from my furious dogo ;)
[Android General] Portgas D. Ace:
In case the SystemUpdate wakelock is still present and you are running Tasker, you could try this solution:

1. Create a Tasker profile "terminate SystemUpdate", which is triggered on device's boot (Event -> System)

2. Create a task "terminate SystemUpdate", which includes two shell commands:

pm enable com.google.android.gms/.update.SystemUpdateService​

pm disable com.google.android.gms/.update.SystemUpdateService​

This will first enable the SystemUpdateServcie and then disable it again. This way the SystemUpdateService wakelock was no longer an issue for me ;)
[Android General] m0han:
i meant you to suggest an

aosp rom

from among the ones you saw, and i could try their earlier build.

btw, did you mean, yuphoria os ported to yureka (my device)? could you give me the link you found?

incidentally, the build of carbon rom that i'm running now

does not

seem to have the dialer-freeze bug.
[Android General] v7:
The only AOSP ROM I found for your device is PAC-ROM.Seems to have a few bugs though.

You could also try changing Kernel of your current ROM.There's a bunch of Kernels for your device
[Android General] iall5tar:
Hiho!

Well here is the idle dumpfile... But seems that everything is OK?

https://www.dropbox.com/s/7z1eawcl63ke21m/BetterBatteryStats-2015-06-26_085450464.txt?dl=0
[Android General] Mogten:
I couldn't find the text app, something must be amiss. Thanks.

Just did. It doesn't happen often, just twice and yesterday only. Thanks for the tip!
[Android General] beeshyams:
[MENTION=5867207]vaisakh7[/MENTION]

Thanks a lot for this thread and your active participation in helping others out. Much appreciate

Couple of general questions that have always bothered me

1. Why does one insist on charging to 100% before starting test. Only reason I can think of is that it is a clear starting point and can eliminate 1% error. But I see a problem here. Since discharge rates are rapid for any battery comparatively speaking from 100% by design, the actual discharge rate may be different than shown

2. This is something I noticed with all my batteries. If you switch off power soon after reaching 100% say within 7 minutes, the discharge is rapid in test condition. Whereas if you keep power on for a long period say 25 minutes after reaching 100% and then carry out test, the battery holds to 100% state much much longer, even 6 hours. This is true with a new or less used battery also. So the result depend on how long you kept power on after full charging. So how does one start testing

In any case, since one can start BBS from reference, why not start test at some point where the discharge is more linear? Anywhere between 90 to 50%?

This has been bugging me so requesting clarification. Only for my understanding and not to question your methods. Please don't misunderstand this

Thanks again
[Android General] v7:
[MENTION=3890097]iall5tar[/MENTION] This is an in-use dump mate.Read the FAQ in post #5 and post the dump.

Tapped from my furious dogo ;)
[Android General] v7:
[MENTION=6285129]beeshyams[/MENTION]

1.Your views are right.The discharge rates are higher at 100-90%.But even 0.0% drain is possible at 100%.Anything <0.5%/hr is considered good.While in the 75-50%,the battery shows it's strength.At this period, anything <0.3%/hr is considered good.As you said,100% is set as a clear starting point.You can also set a Custom Reference and post the dump.Interpretation of the battery life is different then.

2.First of all,thanks for the question.:).While charging to 100%,most of the batteries show 100% even before reaching its full capacity.It is recommended to leave atleast 10-15 minutes at 100% before unplugging.You can use apps like Ampere to read the capacity while charging.

Tapped from my furious dogo ;)
[Android General] v7:
[MENTION=4250471]RohinZaraki[/MENTION] Victory!!The wakelock is gone for good.Now post a dump of longer idle time mate.

Tapped from my furious dogo ;)
[Android General] beeshyams:
[MENTION=5867207]vaisakh7[/MENTION]

Thanks for the reply. I am struggling to find the culprit in my cell...will post my logs soon..tomorrow...request your help in cracking it :)
[Android General] v7:
[MENTION=6285129]beeshyams[/MENTION] My pleasure :)
[Android General] iall5tar:
This is a custom ref from tonight... It's not in use dump... Am I missing something? Or you really need an idle dump from 100%??? Is it a must? Even with a ref cust?
[Android General] v7:
[MENTION=3890097]iall5tar[/MENTION] You made a small mistake while taking the dump.While taking dump with Custom Ref., you should select "Custom" option from the drop down menu and then use the share button to save the dump.Otherwise the stats won't be of the Custom Ref.like the one you've posted.
[Android General] iall5tar:
Damn! my bad! this happens to make it fast xD

ill report later then...hope the third try goes well...
[Android General] drozo8o8:
Yea that's true but why is it using a sensor for 8 hrs+ when it's idling while I sleep ?

I just read about some of your previous posts and I see your point. I've been using amplify and aggressive doze/hibernating since forever (kitkat) but i'll give it a try without any of those tools after a clean flash.

It would be hilarious if its really just like some kind of placebo effect here.
[Android General] DB126:
Visibility does not equate to mandatory action. Just because you can see it doesn't mean it needs to be managed. Classic exercise in determining what's important.
[Android General] Zander_Sig:
Nice!

Hey, Thanks for posting these settings. How goog does this save the battery compared to a CPU Control Profile like setCPU - Screen off profile?

BTW, it's going to take a bit to enter all these changes for Amplify but I couldn't find this entry...

"Alarms(Allow every 1800 seconds)

com.oasisfeng.greenify.CLEAN_NOW" I guess it's because I don't have Greenify installed huh? If they don't show up should I add the setting as "New"?

What are the main entries that really saves the battery the most? Is there a way to make a shorter list for those changes or could you maybe please give me your preference file for Amplify? Would that work if I got your preference file and then I put it on my phone? That would save me a great deal of time. If you don't mind that is. :) Hehehe. ?

Thanks man!
[Android General] DB126:
Suggest you read the last dozen or so posts (plenty more before that) and reconsider. Alternatively, spend uncounted hours configuring/reconfiguring, chasing bizarre side effects, posting questions/observations that have no answer before eventually coming to the same conclusion. Pick your poison wisely.
[Android General] strongst:
Perfect answer:)

[MENTION=4602375]Zander_Sig[/MENTION] :

A lot of people have those heavily tweaking to best battery life in mind of former Android times where it was sometimes necessary and you really gained some mA out of your battery(I did it too on froyo etc.).

But, as already countless explained, since Google implement lots of battery saving features in the last couple of Android versions you can just chill instead of spent hours of tweaking.

All others are app related like badly programmed ones.
[Android General] Zander_Sig:
Thanks

OK, I will do that. Thanks man!

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

I am still on a Nexus 5 running OS 4.4.4 and my battery dies fast! I even put a brand new battery in it back in March of this year and that didn't help me.

To me it seems that the new versions of Google services, Google apps, etc is killing my battery.
[Android General] strongst:
That's a true observation many are aware of this and I do also use less Google apps than years before. Alternatives are mostly around and it's only a convenience problem to head over ;) that helped me solving a lot of battery drain problems(and privacy issues too ;)) and you support 3rd party developers by donating :D

About new batteries you'll find enough. Not every new battery is new.

Google play services are a service you can't get rid fully off these days when using gapps or apps that using this service, but MicroG can be an alternative you should have a look at it.
[Android General] DB126:
I have two 4-5 year old devices on KitKat (4.4); neither suffers from 'excessive' drain either in use or while sleeping. In fact, one has the lowest idle draw of all my assorted devices. All have Google services and selection of Google apps installed. Your issue is likely due to an old/worn battery, personal app portfolio not optimized for Android 4 or layers of cruft that has build up over the years. Reflashing a well tuned ROM can make a huge difference. Good luck.
[Android General] ngohoainam:
i used to use Nexus 5 so i understand what you feel! i can confirm with you nexus 5 had bad battery usage. bad battery usage is the main reason i sold it and buy new phone to use. Now i'm using Xiaomi Mi A1 ( Android One - pure and no boatware). => moving to a new device which has better battery and Chipset ( Xiaomi Mi A1 uses Snapdragon 625) is a solution to have a better experience! :)
[Android General] maybeme2:
What features are you giving up when you move to android one? What are the downsides? I believe it has problems with LTE in the US. Are you rooted?
[Android General] vaggosgr:
I don't know which one (amplify or powernap) is causing a bug on my phone. When i receive a call or when an alarm goes off the screen stays off and i cannot turn it on or answer call/turn off alarm. I can only wait till they stop ringing and then my device restarts itself. Has anyone faced the same issue? If yes please help cuz i wanna use those apps to improve my battery life :(
[Android General] speedy56:
Is this wificonnectivity manager alarm normal or not?

I've also attached my L speed settingsView attachment 4557759
[Android General] DB126:
Don't drink the lemonade; you don't need either of those apps to score good battery endurance on Android 6+. Just look back through recent posts - and many more prior to that. However, if you enjoy hours of configuration and bizarre side effects without any corresponding benefit belly up to the bar and pour yourself another glass.

---------- Post added at 03:06 AM ---------- Previous post was at 03:04 AM ----------

Disable WiFi scanning and leave everything else stock.
[Android General] tullian:
Thanks @v7, [MENTION=5488402]Davey126[/MENTION], [MENTION=613506]strongst[/MENTION] and everybody else for sharing your knowledge and experience!

Could anybody be bothered to take a look at my log file? I've had ~6%/hr in idle drain, which, to me, seems a lot.

After a restart, only wifi on and without having started a bunch of apps. Greenify was on but with standard settings (no aggressive or shallow doze, no greenified apps).

I've read the first few and last 50 or 60 pages but don't quite know where to start. Running RR 8.1 on a Note 4 (910F). CPU is limited to 1958 MHz, govenor is smartmax.

Any help would be greatly appreciated!
[Android General] DB126:
Log was short (<6 hrs) and contained 6+ min of screen on time compromising usability. Still, unfavorable sleep/wake ratio and elevated cpu activity suggests something is amiss. Thoughts:

- weak/unstable wifi signal seems likely; try moving to a different location

- make sure WiFi scanning is disabled/off

- mobile signal wasn't great either but not a major player in wake time

- aging battery also a contributor...but not the primary culprit

- no apps stood out; there's room for optimization but a proper idle log is needed for further analysis; again, not a major player at this stage

- no benefit to capping max CPU speed in the absence of excessive heat or thermal throttling; snapdragon 805 is capable of handling its own affairs without 'helpful' (cough) intervention.

- make sure fingerprint sensor is clean and free of edge gunk

Me thinks the smoking gun is a kernel/rom cocktail not optimized for a 2014 vintage device. See this a lot with Oreo ROMs brewed in someone's kitchen. Might consider rolling back to stock kernel and a well regarded Nougat (7.1) based ROM. Good luck.
[Android General] tullian:
Thanks for the quick response, [MENTION=5488402]Davey126[/MENTION]!

I agree that the screen-on time isn't helping but unfortunately, in BBS from/to I can only choose to 'current' or 'custom'.

On your thoughts:

- Wifi signal was stable at -54dB, 2m from the router. It won't get better than that.

- Wifi scanning was off.

- Mobile signal is what I get here. I'm 1km from the tower.

- Battery is new and (supposedly, hopefully) original.

- I'm capping CPU freq since I've had the 910F's infamous eMMC failure, which, as far as I know is heat-related. Some apps (like BBC News, inexplicably and unnecessarily) take all the juice they can get. Otherwise, my usage hardly ever maxes the CPU, capped or not.

- Don't know if it makes a difference but I've never used the fingerprint sensor. It's clean, though.

I think RR can be considered a well-regarded ROM. It's been around for many years and in many Android versions. Like its Lineage base, it has been focussed on the 910F since that is a capable and (still) popular model.

Please don't consider my comments dismissive. I'm trying to understand these things by discussing them.

What's most interesting to me (right now) is that this level of idle drain only occurs as long as wifi is on. I usually switch it off overnight which results in 0.1~0.2 %/h.

I'd be willing to do more thorough testing but I hope I can get more promising pointers in order to make RR 8.1 work for me before I go back to 7.1 or one of the original Lineage versions. And I'd be very reluctant to go back to stock...