yashsingh1/xdaforums huggingface dataset:
[Android General] beforeitwascool:
I tried enabling icing service again, but still I get no sync. So I uninstalled both Disable Services and Amplify to see if was a service related problem, but nothing happened, still no sync.
[Android General] Portgas D. Ace:
Should be available in the Alarm section of Amplify. Search for "analytics" and you should find it.

Does location-related things drain any battery for you? I have flashed a new ROM recently and did not limit any location-related things and don't have any drain (also didn't use My Android Tools to disable any location-related service).
[Android General] djurkash:
Hi, Portgas, anything you see here that I don't? I've greenyfied all, aggressive doze, amplified all alarms, wakelocks etc , and drain is still large...

sent from e6533
[Android General] Portgas D. Ace:
FastDormancyWakeupServer (Android System): 1 m 23 s Count:52 0.4% -> seems that Fast Dormancy is draining some juice, therefore I would suggest you search for "disable fast dormancy" and get yourself familiar with fast dormancy

Alarms: 27, Intent: com.sonyericsson.android.wakeup.FastDormancyWakeupServer -> see above

Alarms: 24, Intent: com.android.bluetooth.btservice.action.ALARM_WAKEUP -> Bluetooth connection during idle time, this will for sure drain battery

So my advice would be to disable Bluetooth connection during idle time (check also "Settings -> Location -> three-dot-menu ->Scanning" and disable Bluetooth scanning if enabled) and to produce another idle log file. Only if the drain hasn't been reduced to less than 0.9% per hour, continue with disabling Fast Dormancy.
[Android General] djurkash:
Location scanning is disabled, both for WiFi and Bluetooth, I'll disable Bt connection and try again, but even if I manage 0.9%/h , this is pretty high, right?

Why are you mentioning 0.9%/h , is it some limit?

Ok, I do have dual sim, but I see phones managing 0.1-0.2 with Wi-Fi on etc...

sent from e6533
[Android General] Portgas D. Ace:
0.9% per hour is just a personal thing, it would mean that Bluetooth was only responsible for 0.3% per hour drain of 1.2% right now, thus leaving Fast Dormancy as the main drainer here. If disabling Bluetooth "fixes" the drain, then there will be no need to disable Fast Dormancy.
[Android General] BatDroid:
reboot to recovery.

wipe cache/dalvik,art

reboot
[Android General] Portgas D. Ace:
Most likely this is because you have limited CheckinService and CheckinHandoff. Unlimit them and reboot your device.

Do you use anything else beside Amplify, for example Greenify and Power Nap?

Which servcies have you disabled by using Disable Services?
[Android General] brunolima01:
help

used the complete original plan of the post, and had problems with google app , google chrome , it closes alone when I open again and it starts and already closes alone again ... message " stopped working " google play services , media, like this to start the device

could you tell me what has aver with these errors for me disable the control and

back on the right

(device xperia z2 lollipop 5.1)

thanks
[Android General] beforeitwascool:
In the end I didn't discover what the problem was. I uninstalled all the battery saver apps, wiped cache/dalvik, but still google sync was broken. So I flashed a previous backup and everything is fine.
[Android General] Portgas D. Ace:
Most likely the "Icing" wakelock is causing the issue. Unlimit it, reboot your device and try again.

Also clear cache of all apps that force close and reboot your device. Check if the issue is still present.

If this doesn't work: disable Amplify, Greenify and Power Nap within Xposed Installer and reboot your device. If those issue still arises, then it is not the fault of one of those apps. If the issue is gone, enable Amplify and reboot again. Check again for issues and then repeat the same for Greenify and Power Nap. This way you will get the module that is causing the issue.

If it is indeed Amplify's falut, unlimit all things from the guide and start to limit them one by one and reboot after you have limited one element. This way you will get to know which alarms/wakelocks cause the issue if limited.

Okay, but now you don't have anything to decrease your idle battery drain. If you are interested, install only Amplify and limit one wakelock/alarm after the other and reboot after limiting one element. If the sync issue arises, then you will know which one causes the issue and you can unlimit it.
[Android General] beforeitwascool:
Yup, that's what I'll do! Thanks!
[Android General] AirwolfUK:
Fast dormancy

Sorry ignore

Meant to search and not reply :(
[Android General] brunolima01:
problems caused by amplify, however did not have a chance to disable icing, all restored before obtaining answer ... I will follow the beginning of the program again without amplifying icing, and see if the problem is solved ... anyway, google chrome and google app were hibernated besides wakelocks and alarms, it causes some kind of conflict or has to be done it that way? limit and hibernate? (I'm not using poweramp)
[Android General] Portgas D. Ace:
Limiting alarms/wakelocks of a hibernated app will not cause any issue as long as the limited element itself will not cause issues.
[Android General] vogiasf:
Hi, can someone check this log?

It was Awake (Screen Off) (): 9 m 30 s 3.0%

in total 5 hours, with these 2 processes most active

system (Sistema Android): Uid: 1000 Sys: 10 m 59 s Us: 7 m 26 s Starts: 0

com.google.android.gms:snet (Servicios de Google): Uid: 10012 Sys: 4 m 58 s Us: 11 m 37 s Starts: 0

Can I improve anything?

Thanks! :)
[Android General] Portgas D. Ace:
Screen On (): 1 m 52 s 0.6% -> try to minimize the screen on time to less than a minute, save the log file right after you turned on your screen

The rest is fine, 0.2% per hour is great :good:
[Android General] vogiasf:
:o

ok! The 0.2% isn't true though because 100% to 99% is like five times longer than a normal 1%...

and when I use the phone with 10% Screen On the Screen Off (active) climbs to 13%

is that normal?:confused:
[Android General] Portgas D. Ace:
Yes, but we are looking at the idle drain and numbers such as 0.2% per hour (means you lost 1% in 5 hours) are normal here.

Yes, that's quite normal. It always depend on the individual usage.
[Android General] timeshiftt:
Now I lost 13% on standby lol

I updated BBS to 2.2.0.0B6
[Android General] brunolima01:
restored the amplifys and redid the beginning this time not merely "icing" and everything returned to work properly ... I am Brazilian and time of translation of the page did not realize that "icing" it was freezing some apps ... thanks bro

---------- Post added at 08:57 PM ---------- Previous post was at 08:55 PM ----------
[Android General] NoyNoying:
Latest battery stats.... from 0.8% per hour to 0.4%

any amplify tricks to share? Because my goal is 0.2% or 0.0% per hour :D

I'm using a 4 years old samsung s3 and 1 year old battery
[Android General] lu_peng2:
jep, me too!! after not limiting "Icing" all error disappear,

funny i used all of the tips from this page (greenify, amplify) on my previous HTC ONE M8 in LP times and now i'm back with a M9 and MM and it save my day again!!

Also the tip with not limiting "Icing" is maybe worth to mention in the first page as warning! I'm lucky it was mention the last page otherwise i would read trough 945 pages to find the reason for the Chrom and google service errors ect!
[Android General] Portgas D. Ace:
Awake (Screen Off) (): 1 h 2 m 23 s 12,1% -> way too much awake time

*sync*/com.google.android.gm.email.provider/com.google.android.gm.legacyimap/eM_ADDR (com.google.android.gm.Gmail): 1 m 12 s Count:9 0,2% -> Gmail sync was running during idle time

bcm4773_wake_lock (): 31 m 40 s Cnt:(c/wc/ec)3841/8/3841 6,1%

NETLINK (): 12 m 38 s Cnt:(c/wc/ec)15451/1004/0 2,5%

ssp_wake_lock (): 5 m 4 s Cnt:(c/wc/ec)245/27/87 1,0%

wlan_rx_wake (): 4 m 32 s Cnt:(c/wc/ec)261/478/261 0,9%

wlan_oob_irq_wake (): 3 m 42 s Cnt:(c/wc/ec)3582/63/2 0,7%

GPSD (): 3 m 32 s Cnt:(c/wc/ec)40/8/0 0,7%

PowerManagerService.WakeLocks (): 3 m 16 s Cnt:(c/wc/ec)294/32/0 0,6%

lli_pm_wlock (): 3 m 7 s Cnt:(c/wc/ec)277/14/0 0,6%

ssp_sensorhub_wake_lock (): 1 m 57 s Cnt:(c/wc/ec)37/1/37 0,4%

umts_ipc0 (): 1 m 42 s Cnt:(c/wc/ec)207/9/207 0,3%

rtc-sec (): 1 m 9 s Cnt:(c/wc/ec)140/28/140 0,2%

PowerManagerService.Display (): 1 m 8 s Cnt:(c/wc/ec)5/0/0 0,2%

13930000.decon_fb (): 1 m 8 s Cnt:(c/wc/ec)5/0/0 0,2%

alarmtimer (): 1 m 1 s Cnt:(c/wc/ec)31/31/31 0,2% -> your kernel is producing a lot of wakelocks, maybe flash a different custom kernel

Your "Alarm" stats are corrupted, please ensure that you haven't enabled the "Use API to get alarms" within BBS settings (Settings -> Advanced)

Alarms: 3, Intent: com.google.android.gms.analytics.ANALYTICS_DISPATCH -> limit this one to 9999999

By the way, did you turn off all data connections during idle time? Can't see any reference for mobile data or WiFi. Could you upload an idle log file with WiFi enabled and connected to your home WiFi?

Will be done upon @v7's return.
[Android General] timeshiftt:
I have no idea why these wakelocks started to appear, I wasn't having more than 1 minute of awake (screen off) time before. Now I disabled this "Use API to get alarms" on BBS, it came activated by default.
[Android General] StuPot01:
Can someone take a look at this please?

It isn't ideal because the battery wasn't quite 100% but you should be able to still get some good info from it.

I've not limited all the things suggested in the first post, only the ones that showed up in BBS.
[Android General] NoyNoying:
Should I charge my phone to 100% charge while wifi is on and idle only? I'll upload it tomorrow. Thank you for helping me... ☺
[Android General] neonkat:
anyway,doesn't matter.
[Android General] Portgas D. Ace:
Statistic Type: Custom to Current -> change it to "Unplugged to Current", otherwise you will end up with something like this:

Level lost [%]: Bat.: 1%(76% to 77%) [-0.1%/h]

This way we are not able to properly identify all the things we want to optimize. And don't enter airplane mode or turn off mobile data or WiFi. Apps tend to be more active while connected to the internet.

Turn WiFi on, charge your device to 100%, unplug your device from charger and leave it idle with WiFi on (and connected). That's it. This way we can see which apps are active because they are able to access the internet. This is the main purpose of this guide: to minimize battery drain while having your default usage pattern enabled (for example WiFi on, Bluetooth connected and so on).
[Android General] djurkash:
Hi, Portgas, I've disabled all connections, and turned airplane mode on, and the best I've got it's still pretty high: 0.8%/h

Both awake time (2mins) and SOT (<1min) were ok

What I see strange is PowerManagerService.Display which should show how long screen was on, is showing 10mins !?

qpnp-smbcharger-ffffffc0c0097400 is probably related to Qi charging case (I charge my phone wirelessly) but this is first time I see this wakelock that high

qpnp_fg_memaccess and wlan_rx_wake are pretty low now, so no issues there

Regarding processes I only see com.sonymobile.xperiaweather.Weather a troublesome, is this too high?

Alarms are on the minimum as expected, as no data connection was available from any source, so even HEARTBEAT is ok....

And, this takes us to CPU states:

CPU States

==========

1.56 GHz (): 2 m 18 s 0.6%

1.48 GHz (): 13 s 0.1%

1.34 GHz (): 27 s 0.1%

1.25 GHz (): 39 s 0.2%

960 MHz (): 1 m 47 s 0.5%

864 MHz (): 13 s 0.1%

768 MHz (): 13 s 0.1%

672 MHz (): 8 s 0.0%

600 MHz (): 13 s 0.1%

460.8 MHz (): 10 s 0.0%

384 MHz (): 9 m 53 s 2.6%

Deep Sleep (): 6 h 1 m 42 s 95.7%

Pretty high SOC usage to me, especially at max frequency, also this 10mins at minimum frequency correlates with SOT, so, really strange to me...

And, again 0.8%/h , I think is too much, seeing what others manage...

Any ideas? Thanks...

sent from e6533
[Android General] Portgas D. Ace:
0.8% per hour without data connection or Bluetooth enabled is too high, should be around 0.3% per hour at a maximum. The only thing that I can suggest is to flash a custom kernel or maybe even a custom ROM.
[Android General] NoyNoying:
Ok, I'll post it tomorrow... ☺ thank you! Is this safe to amplify com.google.android.gms.gcm.heartbeat_alarm ? according to bbs it's cosuming my battery by 28.0 per hour
[Android General] drstereos:
can I amplify com.google.android.gms high drain on battery thanks...
[Android General] davebugyi:
For me Amplifying "ICING" causes Goggle Play services and Google App to FC every minute or so (since version 9 of those apps), so had to remove it from the list.

---------- Post added at 12:30 PM ---------- Previous post was at 12:29 PM ----------

That is the whole package name for the Google Play Services. If you do not want to use Google apps at all, you can.
[Android General] Docek70:
Dangerous wakelock

Icing - DO NOT LIMIT / DENY

(reported to force close Google Play services, etc.)
[Android General] tet-bundy:
Well. 0.0%/h is pretty easy to achieve. Power down the device.

It should be logical that an electrical device which is actually running simply can not use no energy. #perpetuummobile

Gesendet von meinem unknown mit Tapatalk
[Android General] TNSMANI:
As a sarcastic comment, it may be ok. But 0.0% per hour in this thread's context does not mean that no power is consumed. Power will be consumed but it will be less than 1% per 10 hours as per the measurement matrix used here (because the consumption percentage does not go beyond the first decimal).
[Android General] aidy.lucas:
Link to my post with the new working regex blocking for latest play services CONTEXT_MANAGER_ALARM_WAKEUP_XXXXXX alarms

http://xdaforums.com/showthread.php?p=66986424

D2303 5.1 deodexed z2 port+z5+X apps+themes, be,xr,sv,ad,XZRt2urecovery,xposed,z5 cam2.0,xLOUD,S-Force,viperaudio+more
[Android General] Danbarizer:
Hello !

This is my logs for my HTC One M8 running Marshmallow with the official ROM.

So I think the battery consumption is fine but if there are ways to enhance my autonomy, I'm not against :D
[Android General] Portgas D. Ace:
HSP_Weather_60 (com.htc.sense.hsp.Service Pack HTC): 1 m 55 s Count:3 0,4% -> HTC Weather being active

Alarms: 6, Intent: CONTEXT_MANAGER_ALARM_WAKEUP_151325817 -> use Amplify's regex blocking function to eliminate this one. The regex: CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]+ with an interval of 9999999

Alarms: 18, Intent: com.google.android.gms.location.fused.SEND_LOCATION_IN_SMD_MODE -> limit this one to 86400

Beside this, lots of location-related alarms that are part of the OP. Ensure you have limited all of them.

Rest looks good :good:
[Android General] tet-bundy:
well actually, assuming BBS rounds to the first decimal u would actually have to achieve a drain <0.05%/h to have it displayed as 0.0%/h. That would match around an entire day running idle with a drain of ~1%.

i didn't intend to offend anyone here, but i afraid, i actually doubt that can be realized...

Gesendet von meinem unknown mit Tapatalk
[Android General] TNSMANI:
No offence.

But who said BBS is rounding off? I for one, don't know whether it rounds off or stops with reading the first decimal.

But the fact is that 0.0% drain is possible. I had achieved it back when I was on Lollipop and I had posted the BBS dump as proof. Check this: http://xdaforums.com/showpost.php?p=62209472&postcount=2723

Not only me, a few others had also achieved it.

The fact also remains, I am yet to come across someone who has achieved the same result in MM, including me.
[Android General] lepa71:
Can somebody look at mine? I have been having lots drain lately.

https://drive.google.com/open?id=0B6Q3mX4-UYRgSDBWUHdJRDllV0k
[Android General] tet-bundy:
Okay thats in fact interesting. Did the battery drain faster when u start using ur phone again? Because i mentioned for example battery drains relatively faster after it was in flight mode for a while and then started using it again. Because if this is the case, i think the low drain does simply not match reality similar to the "fast drain from 100% after unplug" which is mentioned in op.

Regards

Gesendet von meinem unknown mit Tapatalk
[Android General] TNSMANI:
When I was on Lollipop, the drain after achieving such 0.0% and then unlocking the screen, would be slightly higher but not comparable to the drop from 100% mentioned in the OP. But it didn't happen every time. Most of the times, the drain after screen on would be normal.
[Android General] xda26:
content://com.google.android.apps.docs.storage.legacy/enc%3DGuWQxr1AO2dLCNZLiK6yW9Fhs2M0wQT-_Efv1CnOhG4EskXW%0A
[Android General] rdoane:
Does anybody have experience with limiting the alarm titled com.google.android.gms/.vision.DependencyBroadcastReceiverProxy?
[Android General] lepa71:
Anybody can look at mine?

I think Google Play services 9.0.82 causing lots of battery drain.

Thanks
[Android General] nickoArd:
Hi [MENTION=5867207]v7[/MENTION] .

Im testing a android N rom (obviously, xposed is not available but greenify in root mode yes).

Do you recommend activate the shallow hibernation and agressive doze?

Doze is "agressive" by default in android N i think...

what do you think???

Thanks.
[Android General] Snowby123:
wlan_rx_wakelock is your biggest drainer. The next big one is mmc1_detect. The third is sec-battery-monitor. I know there is another thread that explains how to control the first one. Your second one I have not seen and Cannot explain. Stopping the last wake lock is simple... Just keep wifi off while the device is turned off
[Android General] arunkafley:
Can you please provide me with a regex for limiting android.net.netmon.lingerExpired_xxx_xxxxxxxxx. I got the regex when both are positive but I dont know how to configure when the second numerical part is negative e.g android.net.netmon.lingerExpired_112_-2112734287
[Android General] 4uvak91:
bump, anyone? very annoying issue.
[Android General] steve97ta:
try removing them from your battery saver setting like you said
[Android General] 4uvak91:
I will, thx. What about BetterBatteryStats dump, anything special there to tweak?
[Android General] steve97ta:
Looks to me like your deep sleep is good, you lost 6% in how many hours? and you are using the device.
[Android General] 4uvak91:
Deep Sleep (): 8 h 4 m 25 s 91,1%
================================================== ====
Wakelocks (requires root / system app on Android 4.4+)
================================================== ====
AudioMix (1013): 1 m 14 s Count:46 0,2%

Just noticed now... why audiomix waking so much time? There are other audiomix wake ups too...
[Android General] rm83855:
Please remove the "Icing" service/wakelock from this guide, i have routinely experienced crashes with the Google app and google services with this restricted. I have unrestricted it again and all is good. Others have reported the same situation. Thanks for the great battery tutorial btw :)
[Android General] stopa10:
Yes, I can confirm that limiting Icing gives FCs of the latest Play Services. Unfortunately is not the only problem. Casting to Google Cast also has issues, I am still investigating what wakelocks are involved...
[Android General] Revontheus:
Hi Guys! Since you block Messenger/FB Service in Amplify and limit their wakelocks does that also go for twitter and other social media applications?

Thanks! :)
[Android General] Shark5060:
Well I can only say I've limited every Social Media App including Twitter, WhatsApp, Tumblr, Skype, Discord and Instagram.

Since I don't use most of them THAT often (1-2 times a day) I can't really tell if they don't work properly (since I have deactivated notifications on most of them anyways).

I'd say - try it out and see if you're getting delayed notifications or otherwise broken features.

EDIT: FB and FB Messenger are very important since they usually spam alerts and wakelocks like mad.
[Android General] Tinchoska:
Have you tried this app? https://play.google.com/store/apps/details?id=com.franco.servicely

Enviado desde mi XT1097 mediante Tapatalk
[Android General] Revontheus:
Sometimes Greenify Can't greenify Google Services because of SSBService, anyone else experienced this? I force stop google services and it gets greenified. Strange
[Android General] knpk13:
System(adsprpcd) draining battery when device is idle. What is adsprpcd?

[MENTION=5901790]Portgas D. Ace[/MENTION]

@v7
[Android General] Portgas D. Ace:
Could you tell us what alarms/wakelocks you have limited by using Amplify?

Will be done as soon as [MENTION=5867207]v7[/MENTION] is back from exams.

Statistic Type: Boot to Current -> Set it to "Unplugged to Current", otherwise the stats are useless.
[Android General] 4uvak91:
https://drive.google.com/open?id=0B4Yp0UNFwvNjSFN6UkU4dEp3dzg

I didn't block the services, audiomix causing huge wakelocks and zero.boost I removed. I have SDMaid now.
[Android General] Epsil:
It's ok with this ?

Thanks for your help

http://cloud.tapatalk.com/s/57495ef265a73/BetterBatteryStats-2016-05-28_110256013.txt

Envoyé de mon LG-H815 en utilisant Tapatalk
[Android General] Portgas D. Ace:
BetterBatteryStats version: 2.1.0.0 -> Update BBS to v2.2.0.0B6 (can be found in the BBS thread here on XDA) as "alarm" stats are corrupted

android.content.syncmanager.SYNC_ALARM

SyncLoopWakeLock

Those two might be responsinble for the delayed push notifications. Unlimit them, reboot and check if you still receive delayed push notifications.

Statistic Type: Boot to Current -> set the statistic type within BBS to "Unplugged to Current", otherwise the log file is useless

No idea about it.
[Android General] ElementRn:
https://youtu.be/GOVrMV_0Cz0

Have a great day?
[Android General] Epsil:
I don't have choice.

Envoyé de mon LG-H815 en utilisant Tapatalk
[Android General] MostaphaHida:
for those who r facing problems like google play services stopped or downloading something from play store and stops while ur in background dont limit : Icing

also if ur using AOSP roms GearCM or something else dont limit :NetworkStats

Every thing else is working well and superb battery life thanks to OP.
[Android General] mestizo19:
Anyone knows what is the Alarm below? And i can't find the regex alarm. I made the procedure but i can't find ALARM_WAKEUPxxxxx
[Android General] neonkat:
check the screenshots given in op's post.

go to alarm-*page* icon on top-tap the + icon-add as given.
[Android General] Portgas D. Ace:
CONTEXT_MANAGER_ALARM_WAKEUP is the new ALARM_WAKEUP. Just add a new regex function

CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]+

and limit it to 9999999
[Android General] criz.89:
What should i amplify to optimize Google play service battery drain?
[Android General] soosoolhastam:
That's the million dollar question
[Android General] tet-bundy:
Delete

Gesendet von meinem ONE E1003 mit Tapatalk
[Android General] 4uvak91:
Above is my new data, anything special in there?
[Android General] Portgas D. Ace:
Web Client (com.whatsapp.WhatsApp): 2 m 27 s Count:51 0,7% -> WhatsApp Web connection has been active

Alarms: 20, Intent: com.facebook.rti.mqtt.e.f.ACTION_INEXACT_ALARM.Mqt tLite.com.facebook.orca -> FB Messenger is active, you can limit this one to 1800 and check if you are okay with this as it might delay push notifications

Alarms: 3, Intent: com.facebook.analytics.service.a.ACTION_ALARM -> limit this one to 9999999

Alarms: 11, Intent: com.whatsapp.messaging.MessageService.LOGOUT_ACTION -> limit this one to 43200

The rest looks okay, 0.4% per hour is good. But you also have some kernel wakelocks, maybe flash a custom kernel.
[Android General] 4uvak91:
Thx, there is no custom kernel for xiaomi mi5 yet.... The source is no published.
[Android General] darkwolf_99:
In Android 6.x, Power Nap cannot work very well, I think, because it cannot save juice as in 5.x