yashsingh1/xdaforums huggingface dataset:
[Android General] Celestial Fury:
HEBF optimizer

Disable it and see what's the difference. Note: A single log with and without it disabled isn't conclusive. More logs increases likelihood.

sec-battery-monitor

Does enabling the WiFi setting turn wifi off when asleep reduces it? Note: Check if this impacts your push notifications. Mostly Samsung phones seem to have issues with sec-battery-monitor.
[Android General] Celestial Fury:
Wasn't the question. Log says otherwise. Log says otherwise.

Terminology: Phone ON. Screen ON.
[Android General] anon1135:
anyone using setcpu to help save battery during screen off? I don't see it in any guides and I think latest version doesn't work on nougat. wanted to know if it's really useful
[Android General] anon1135:
I tried it on mm and it doesn't seem bad but if max cpu is set too low then recieving calls will be delayed or too laggy to accept. things like Bluetooth audio could also sound choppy at times. for me around 700 was fine. I'm not sure how people can be fine with it set to as low as 300. some were doing that in guides when I checked but they're a bit outdated since it's an old app. I was thinking maybe some roms can already clock that low by default without any user changes during screen off possibly making this app unnecessary

edit - sorry didn't mean to double post I thought I clicked the edit instead of quote button
[Android General] xt7xda:
Hi,

While travelling, I listen to music a lot, for 3-4 hrs daily. I'm using Moto X Play with Lineage OS 14.1 20171109/Magisk/Xposed/Amplify/ForceDoze.

Can android doze while playing music (Poweramp) with screen off, facedown and motion sensor off? Is it possible?

Thanks...
[Android General] Amanbaid99:
Noob question - will this guide work for nougat?
[Android General] Taracair:
Everything depends on the ROM you're using. You will have slightly different wakelocks and alarms. Just check which one drains your battery and search at xda if it is safe to limit it.
[Android General] smallKING81:
I got the problem with whatsapp when I limited alarm com.google.android.gms.common.receiver.LOG_CORE_ANALYTICS up to 9999999 seconds.

I do not receive notification of an incoming message until I enter to whatsapp. With the disabled restriction, notifications arrive excellent.
[Android General] Celestial Fury:
Android version?

How many copies of WhatsApp on the phone?

If yes, which has a problem - first or second?

Have you checked that none of the push notification alarms (red cloud icon) have been limited?

Is WhatsApp greenified/dozed/in stamina mode?

Doe it happen every time - reproducible?
[Android General] smallKING81:
Ohh, I found my mistake...I limited alarm com.google.android.intent.action.GCM_RECONNECT

Now everything is OK. Thank you!
[Android General] patrickdrd:
big big no, NEVER EVER touch that one if you want notifications!

limit everything else, everything you want except this!
[Android General] sohebq:
It doesn't matter how many times I limit facebook Orca. It will generate a new similar service. I am tired of this. The faceook alternate suggested was not that good.
[Android General] mrjuniork:
Why don't you skip amplify and use greenify for the apps instead? Ever tried?
[Android General] sohebq:
Already using man. Facebook is greenified but not much effect. This crappy app doesn't work well in greenify
[Android General] DB126:
Greenify will quiet any app if properly configured on a rooted device. That said, the official Facebook is a steaming pile for numerous reasons. Lite alternatives exist which have proven satisfactory to most. Can also use tools like Hermit to improve the experience using the web interface. Your choice.
[Android General] Revontheus:
I have to admit, the title sounded like click bait at a first glance but after carefully following which services and wakelocks to limit along side the Ultimate Battery Guide on XDA. It really does work.! I left my second phone (Samsung S5) at home before school with around 79% battery, 3G on and everything and came back (after 8 hours) to see the same amount.

Kudos to [MENTION=5401012]Celestial Fury[/MENTION]! for making such an awesome guide.

Protip: to anyone who uses this guide, it works super well alongside Greenify + PowerNap.
[Android General] drbabusaha:
how to share specific post????
[Android General] Celestial Fury:
Clickbait is a first. ;) However, take note that ADB BBS on non-rooted can also show 0% drain even though BBS records and shows a drop - but that's a bug.

[MENTION=6814688]drbabusaha[/MENTION] - click on reply for a particular post to "quote" it unless by share you mean something else.
[Android General] Craz Basics:
I think he meant like, how do you send a link with the specific post. I.e. if you click a link it will take you to this thread post 18.

Idk how to do that though haha.
[Android General] Celestial Fury:
Hover over the Post number: #3499. The balloon will say: Permalink to Post #3499. Click on it to open a new tab. Copy that URL and paste it in the Insert Link icon in your REPLY message editor.

https://xdaforums.com/showpost.php?p=75496532&postcount=3499
[Android General] TheAnswerIs3:
Hello, can anyone check up my battery stats? I've got 1.8% drain during idle for the past 4 hours ?. Couldn't leave my phone idle longer as i need it for work
[Android General] :
There are some other issues too, but the main culprit is

================
Kernel Wakelocks !!! wakeup_sources !!!
================
sensor_ind (): 3 h 32 m Cnt:(c/wc/ec)30/3/0 80.8%

I have not experienced this problem myself but check https://reddit.com/r/nexus6/comments/2ttg4d/****ing_sensor_ind_wakelock. You should basically either try to enable or disable your ambient display (depending on its current state) and see if there are any changes.
[Android General] TheAnswerIs3:
Will do! Thanks for the reply! ?
[Android General] TheAnswerIs3:
I cant seem to find the WifiConnectivity manager in Amply. Is there like something that i have to type in myself?

Sorry for the dumb question
[Android General] Celestial Fury:
When it triggers it should appear in Amplify. There's also a search function in Amplify. Limit it and you'll likely have problems with WiFi connection.
[Android General] Amanbaid99:
Hey guys i wanted to know if amplify is effective on oreo and if it is can i refer to this thread for settings(blocking wakelocks and alarms)
[Android General] DB126:
Please don't cross post; answered here but best asked here.
[Android General] leAndroid91:
Hi guys,

please take a look at my BBS.

I have already optimized some alarms and wakelocks according to previous posts.

But i still have 28 alarms / h over night from android

Alarms: 33, Intent: *job.delay*

Alarms: 41, Intent: WriteBufferAlarm

Alarms: 16, Intent: DeviceIdleController.light

Alarms: 37, Intent: NETWORK_LINGER_COMPLETE.200

Alarms: 12, Intent: *job.deadline*

Alarms: 37, Intent: WificondScannerImplPno Monitor

and some high numbers from com.google.android.gms

Alarms: 17, Intent: com.google.android.gms.gcm.HEARTBEAT_ALARM

Alarms: 14, Intent: com.google.android.location.ALARM_WAKEUP_LOCATOR

Unfortunately i couldn't find any useful information by googleling those alarms.

Can i limit those alarms without having any issues like missing notifications?

What limit should i choose? 3600 seconds?

Do you see any other potential to optimize my battery drain?

Thanks for your help!
[Android General] Celestial Fury:
Notification-related alarms/wakelocks have a red cloud icon in Post #2. You have an active network connection [see network section in your log] from your many active apps leading to a high CPU usage while idle.
[Android General] leAndroid91:
Thanks for your feedback but how do i solve this issue?

I added another BBS file from last night with wifi turned off but i lost the same amount of battery over night.

According to my understanding there shouldn't be that much wakelocks and alarms.

On Marshmallow i had a battery drain of 1% in 8h so i don't get whats different now :confused:
[Android General] DB126:
Seen this movie before. Older device runs fine on Android 6/7 then suffers high idle drain with Oreo with no obvious culprits exposed by BBS and similar tools (as is the case with in your dump). Likely kernel has not been optimized for Android 8.x ROMs and is failing to put one or more hardware components into a power efficient state. Roll back to whatever worked before and profit.
[Android General] Celestial Fury:
You can test it systematically by first establishing baselines as in Post #3.
[Android General] T@z90:
Hello, I followed the guide to reduce my battery drain. And thanks to that finally my battery lasts again enough! I use MIUI 9 on my Xiaomi MI5, and I noticed that whenever I limit *net_scheduler* I don't get notifications from WhatsApp anymore unless I open the app. It is an issue because the wakelock is the reason my battery was draining fast.

I tried removing from amplify anything else, and is just the *net_scheduler* if i set a limit higher than 5 minutes the issue which disables my WhatsApp notifications. Did anyone else also encounter this problem?
[Android General] Celestial Fury:
Android version? IIRC, KitKat relies on it for push notifications but can be safely limited on Lolipop and above as later versions do not (if still) wholly rely on it but use other means.
[Android General] T@z90:
My phone has Android 7. I limited it to 10 min, and it is a good balance between notifications and battery drain. Anyway, the problem only occurs with WhatsApp, all other apps are working properly!
[Android General] leAndroid91:
Sorry for the late reply.

Battery only drain after 8h is 1%.

I assume the actual battery only drain is 0% and the phone lost 1% during boot.

Airplane mode battery drain is 3% after 7h.

Please see BBS file and screenshots attached.

Does that help?
[Android General] Celestial Fury:
If limiting it causes WhatsApp not to receive messages then you shouldn't limit it at all. If others report the same I'll put up a note in Post #2. However, whether your drain is due to *net_scheduler* or not can only be determined (to a certain extent) with a BBS log.
[Android General] Celestial Fury:
You haven't limited (see Post #2):

CONTEXT_MANAGER_ALARM_WAKEUP

analytics

Location alarms

If you don't need continuous instant FB updates, greenify it or experiment with limiting FB alarms. Non-system apps can be safely limited without affecting phone stability.

Widgets drain much more than their respective alarms would indicate.

NETWORK_LINGER_COMPLETE in the amount triggered in your log is not normal so I check to see if you're using a custom ROM and sure enough you are.

==========

CPU States

==========

1.25 GHz (): 4 m 25 s

CPU running at top speed for minutes in idle. I usually search for a near-corresponding time elsewhere in the log and find PowerManagerService.WakeLocks (): 4 m 9 s which BBS claims to be the sum of the partial wakelocks but a quick check in your Wakelocks section shows a total of exactly 2 m. So, either that's not the case or BBS calculations are wrong or there's a hidden wakelock not shown by BBS but calculated all the same.
[Android General] leAndroid91:
Thanks for your reply!

I limited CONTEXT_MANAGER_ALARM_WAKEUP, analytics, Location alarms as posted in #2.

I would like to keep instant push messages since my goal isn't to achive 0%, i would be fine with 1-5% over 7-8h.

But I'm not using a custom rom.

I'm using the factory image of google with TWRP, SU, XPosed and ElementalX kernel.

I will take a look how the battery drain will develop with the latest settings.
[Android General] leAndroid91:
Unfortunately the drain didn't got any better.

Is there anything else i can try :confused:
[Android General] DB126:
Quick look suggests connectivity issues (possible weak signal) and larger than expected network activity for apps/services that should be dozing. Also some symptoms suggesting kernel incompatibility but may be a red herring given everything else that's going on. Might consider rolling back to Nougat to see if problem persists.
[Android General] leAndroid91:
Since you mentioned a potential kernel issue i rolled back to google standard kernel and again got 3% battery lost in airplane mode over night. Same result as the ElementalX kernel.

Will do another BBS analysis tonight with the google kernel without airplane mode.
[Android General] DB126:
3% overnight loss over 6-8 hours on your device (considering age, ROM and app portfolio) is not unreasonable even in airplane mode. If you are chasing "0.0%/h Idle Battery Drain" that ain't gonna happen short of powering down.
[Android General] leAndroid91:
I'm not chasing 0% drain, since i didn't hat that on M either.

But i would like to get back to 1-2% over night instead of currently 2-3% / h.
[Android General] DB126:
2-3% per hour (vs "over night") is ridiculous and almost certainly related to one of the sources already identified. If overall endurance is also taking a hit verify the battery is not failing.
[Android General] sgtslaughter64:
I followed the guide, but now I am having issues with SMS having significant delays in sending...can anyone help?
[Android General] DB126:
Wakelock limiting/blocking has side effects which you are now experiencing. Make sure alarms/wakelocks from your messaging app are not being limited. Better yet step away from Amplify which offers little benefit over native power management when properly implemented on Android 6 and above.
[Android General] Egyptiandroid:
Thanks
[Android General] Celestial Fury:
A kernel is part of a ROM and the log doesn't differentiate it. How well does mixing and matching ROM parts work? Point is, only see such issues in custom ROMs.

Nothing in the guide messes with SMS. Disable Amplify in XPosed. If problem doesn't occur, then something else you limited is the cause.

In general, Amplify is a tool and XDA is all about the mods. If you want to let Android handle everything then XDA is not for you. The guide has been compiled through numerous testings and feedback. They are meant to limit alarms/wakelocks/services that:

misbehave (Facebook, WeChat, etc.)

unneeded by the user (analytics, ads)

unneeded by the user unless actively used (Location alarms)

trigger often but can be safely limited (CONTEXT_MANAGER_ALARM_WAKEUP)

And all that triggers unnecessarily for the user causes drain. If Amplify is no longer needed and the main Amplify thread gets closed down, I'll ask for this to close as well.
[Android General] sgtslaughter64:
It was actually a network problem that just happened to occur after I made the mods. Working like a champ now.
[Android General] DB126:
This is crap. XDA is many things including learning, developing, sharing and yes, "mods" when mods are beneficial. Sometimes status quo is the best answer. Change for the sake of change is a fool's errand.

Certainly not advocating for the thread to be shut down as there is much to be learned from the shared experiences of others - especially when supported by objective data which is increasingly rare. Those who measure (vs. just reacting to the presence of alarms and wakelocks) usually find little difference in battery endurance or favorable device performance on Android 6 and above. There are exceptions and outliers which this thread continues to serve.
[Android General] the_scotsman:
Closed on request of OP.
[Android General] Celestial Fury:
Google Play Services just got updated and it will now stop unexpectedly every now and then. Had to reenable everything Google Play Services again. Then I'll see how the drain is. But I'll keep this in mind.

Yes, I'd definitely like to see stats with WiFi on.
[Android General] umbian:
Hi. This is my first post here.

I followed the guide for 0.0%. What do you think about my battery life?

Thanks.

Device: Htc One M7

Rom: Viperone 8.0.0

Kernel: xceed
[Android General] goutham.veeru:
I am not sure why, but using amplify heats my phone up trumendously.

Uninstalled it and all ok now
[Android General] Celestial Fury:
You didn't quite follow the guide. It's an idle battery drain guide which is to reduce drain when

not

using the phone but you've used it for nearly 5 hours. You can't get 0.0% drain while using the phone for 5 hours, right? See Post #3 on how to test: Leave phone idle for 7 hours or more.
[Android General] v7:
Here's my stats with Mobile Data On.I use Greenify+Amplify+Stamina Mode.
[Android General] Celestial Fury:
Looks like your data connection gets turned off or blocked after 20 mins or so. Basically, you have no connection and internet connection is a big cause of drain. Needing to turn on the screen for push notifications renders push notifications pointless. You may have some app which regulates connectivity or amplified push notifications apps. I also have stamina mode and have WhatsApp, Hangouts excluded in Stamina mode and greenified but Greenify is not excluded in Stamina mode.
[Android General] Celestial Fury:
I'm not sure why, but you could have used BBS to show if Amplify was indeed using the battery more than other apps instead of making sweeping assumptions.

Ignore assumptions and all will also be OK.
[Android General] OrangeFever:
I have wakelocks such as com.google.android.gms.nlp.ALARM_WAKEUP_LOCATOR and ALARM_WAKEUP_LOCATOR. Same with com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVITY_DETECTION and ALARM_WAKEUP_ACTIVITY_DETECTION.

Do I block both, or just the first with the com.google.android.gms.nlp. prefix?
[Android General] Celestial Fury:
[MENTION=4264204]OrangeFever[/MENTION], both. The package name is still Google Play Services. I'll update the guide.
[Android General] Mudahuda:
http://www.xda-developers.com/keep-those-services-in-check-xda-app-review/ Have you seen this?
[Android General] wxfreak:
Help with the nitty gritty

Is there any way a can improve on this? Battery drain was 0.8%/h now is over 1%/hr.

I have disabled my widgets

Thanks!
[Android General] Celestial Fury:
Limit/increase limit of

com.google.android.intent.action.MCS_HEARTBEAT

com.google.android.gms.gcm.ACTION_CHECK_QUEUE

com.facebook.push.mqtt.keepalive.KeepaliveManager. ACTION_INEXACT_ALARM.com.facebook.katana

(unless you need to be connected to FB all the time)

I'd also put all the location alarms like: com.google.android.gms.nlp.ALARM_WAKEUP_PASSIVE_CO LLECTOR at 43200 secs (see Post #2).
[Android General] Celestial Fury:
Regrettably, ALARM_WAKEUP(#####) has reappeared and Google Backup stops responding.

Thanks to [MENTION=4401674]Mudahuda[/MENTION]'s suggestion of using App ops to turn off BOTH Google Play Services AND Google Services Framework, [B]ALARM_WAKEUP(#####)[/B] by Google Play Services no longer appears.

Using [URL="http://xdaforums.com/xposed/modules/xposed-appopsxposed-appops-4-3-t2564865"]App ops[/URL]:
[LIST]
[*][SIZE="1"]Google Services Framework - turn off [B]EVERYTHING[/B] [/SIZE]
[*][SIZE="1"]Google Play Services - turn off [B]EVERYTHING[/B] [I]except[/I] Location[/SIZE]
[/LIST][I](needed or Maps won't show your exact location anymore)[/I].

I also used [URL="http://xdaforums.com/showthread.php?t=1013063"]SD Maid[/URL] to:
Disable the following autostart components:
[SIZE="1"]Google Services Framework - [B]EVERYTHING[/B]
Google Play Services:[/SIZE]
[LIST][*][SIZE="1"]com.google.android.gms.ads.jams.SystemEventReceiver (Google Mobile Ads?)[/SIZE]
[*][SIZE="1"]com.google.android.gms.common.analytics.CoreAnalyticsReceiver(privacy)[/SIZE]
[/LIST]
Post #1 and Post #2 updated.
[Android General] Mudahuda:
Services framework can also be greenified, but you also receive notifications later (not never, but some minutes later)
[Android General] Celestial Fury:
I actually missed the "Show All" option in Greenify. Here's some 0% [0.0%/h] screenshots after the ALARM_WAKEUP(#####) fix. It's not on a full charge and I have a nagging suspicion that it's harder to get 0% [0.0%/h] on a full charge because the phone is more active on a full charge (by design?)
[Android General] Mudahuda:
Or by charger, some faulty chargers leave a wakelock (at least on Samsung) in kernel wakelocks called "charger soft-reg"

A reboot after unplugging charger should solve this problems

Also i suggest using adaway rather than adblock plus
[Android General] pratik_193:
the apps ops wont work on Samsung Lollipop rom's right ? as there is no xposed module yet...

Can you share some tips for better battery on samsung tw Lollipop Roms ?
[Android General] Celestial Fury:
[MENTION=1686671]pratik_193[/MENTION], Greenify and Servicely work without Xposed.
[Android General] pratik_193:
i am using Greenify(with pro version) & servicely. but i get a lot of wakeups from google play services, which is greenified & disabled by servicely...

i will share my sleep stats in a few hours from now..
[Android General] Portgas D. Ace:
Could you explain what this ALARM_WAKEUP is used for? I didn't find a good explanation yet.
[Android General] Celestial Fury:
I can't find one either. All I can say is it didn't exist before the recent Google Play Services updates, and not having it around now doesn't seem to effect anything as far as I can tell.
[Android General] Portgas D. Ace:
Ah, cool. Thanks, Google, for bringing unneccessary stuff to my phone again :p
[Android General] Khairin:
Thanks man!

Thanks alot for this thread [MENTION=5401012]Celestial Fury[/MENTION] !! Because of this thread i started to rethink the way i use my phone. Im that kind of guy that disables many things and not enjoy full functionality except for those basic ones just for battery life. Because of this, I flashed a new rom, enabled everything google has to offer, recovered my data for titanium and start to use the phone the way it was made. i started benchamrking with only amplify (didnt greenify anything, no app ops tweaking) and battery was quite decent! and got full functionality with your guide!!. But hey, lets tweak it further!. I benchmarked it yeterday. Note that my wifi signal is only 2 bars in my room. Im getting alot of this *Alarm* wakelock(see attachment) which is annoying. Your advice?
[Android General] Celestial Fury:
[MENTION=6133119]Khairin[/MENTION], what kind of phone is this?

Your 'alarms' are running for nearly 2 hours but you only have [0.6%/h] drain over a period of 6 hours? I don't see how this is possible, not in my experience.

You need to click on the items in question to show further details of the individual items that can be limited.
[Android General] vesparados150:
[MENTION=5401012]Celestial Fury[/MENTION] sorry for the different nick, xcidently logged in w g+. Anyways, It's a Oneplus One. I have no idea how that was possible. However, Battery on my status bar was consistent. See attached screenshot for more alarms info. Note that the attached screenshot was taken a few secs ago where i had used the phone for quite some time. In my last post, the screenshots were taken in the morning before getting ready for work. it might however give you some idea of the alarms im facing.
[Android General] v7:
I got these kind of unknown alarms on one of the ROMs I used.I couldn't figure out what caused the issue.But had no battery drain.The stats were same as these of [MENTION=6133119]Khairin[/MENTION]

Tapped from my furious Dogo ;)
[Android General] vesparados150:
[MENTION=1071347]vaisakh[/MENTION] just for the record im on vanir exodus lollipop (OneplusOne) with the stock kernel came with the rom. did you somehow manage to fix it?..