yashsingh1/xdaforums huggingface dataset:
[Android General] LeppeRMessiaH:
This is my first post on XDA and I would like to thank you for this thread. I've recently rooted my Xperia M Jelly Bean and you helped me save quite a bit of power. It was difficult but I managed to stay off my phone for about 16h, the log and screenshots below include some airplane mode too. I know the screen draws power like crazy when it's on but I would appreciate if you would take a look at my data and maybe provide some additional power saving tips. I can't seem to get rid of ALARM_WAKEUP##### of com.google.android.gms and no matter what I do, it's never %0.0.

My config:

Widgets: HD widgets (weather and clock), DigiCal (calendar and agenda), RSS widget

Wifi: Keep wifi on during sleep-always, Scanning always available-no, wifi-optimization-on

Power: stamina and low battery modes only kick in at about 35%, location based wifi-no

Location: GPS and Google location on (I'm doing some testing with the second one disabled)

Email: Sync every one hour between 9-23

Animations: off

Google play auto update: no

Greenify is only active for apps that I don't use constantly

SetCPU is configured to reduce frequency when screen is off

Disabled Media Scanner with "Rescan Media Root"

I also have KakaoTalk always running in the background

Disabled 23 Google Play Services, mostly related to Fitness and Wear:

-ActivityRecognitionService

-AnalyticsIntentService

-AnalyticsService

-CollectSensorService

-ConfigFetchService

-DispatchingService

-Fit****

-GmsWearableListenerService

-StoreMaintenanceService

-UserPresenceService

-Wearable****

-WorkAccountAuthenticatorService

P.S.-I know BBS reports 100% No or unknown signal but that's not true. It's been like that since I installed it.
[Android General] Celestial Fury:
Your alarms and partial wakelocks are ok. Like you said, it's your secril_fd-interface kernel wakelock that's draining. Unfortunately, Amplify can't limit kernel wakelocks. In my opinion, 0.6%/h on data Sorry, saw the wrong number. 10.3%/h is of course high. Mobile data on idle should be below 1.0%/h.
[Android General] Celestial Fury:
Yes, location alarms should be limited at 86400 secs / once per day for Google to update their database. Otherwise, they should only trigger when I'm actually using something that uses location.

So, far Lolipop seems to be all right. Wakelocks and alarms still work the same and are limited the same. I only have one new analytics alarm by Sony to limit.
[Android General] Celestial Fury:
Sure (to disable services only) but first can you edit your post and remove your quoting of the entire 1st post?
[Android General] Celestial Fury:
The 1st four attachments are invalid. Mega makes you jump through the hoops just to download a small text file. Did you try opening them from Mega? They're still jumbled. Only need the first BBS file in .txt format. After saving it, just attach it here.
[Android General] Celestial Fury:
Everything's low. When the alarms and wakelocks are not causing the drain, then it's either the network signal or the battery. In your next post, besides the BBS dump, also post:

In BBS - graphs - history

(does the number go down evenly or jump a few steps?)

In Power Management - Battery usage (to see network signal)

How old is the battery? Any funny drain like skipping a few steps? Shutting down on its own? Sudden unexpected drain?
[Android General] Celestial Fury:
[MENTION=6724606]LeppeRMessiaH[/MENTION]

[0.1%/h] is almost there. While some minor tweaks could be made, the biggest drain is ALARM_WAKEUP#####. So, let's just fix this.

AppOps

Under Hacks - tick FIX OP_WAKE_LOCK

Servicely

Select:

Screen off only

Aggressive process termination (may or may not be needed)

Add:

Google Play Services (only)

NOTE: If you use Google Apps, Google Play Services is an important component and needs to run (backup, etc.) from time to time. So, let it run during screen on. Killing it may also have unintended side affects. Make sure you have a backup where you have not killed Google Play Services that you can restore.
[Android General] vctrrl:
Actually this dump was taken overnight in flight mode. So no network issues, right? My phone is about two years now, so that's the battery age. Yes, sometimes it drops a few steps. Shutting down on its own never happened. Sudden drains happens as I mentioned, by a few steps.
[Android General] HH6:
Hi all,

New screenshots attached.

My idle is very good now. But I feel that the using the phone it drains quicker than before. I don't know if this is only in my mind or actually happening.

Anyway to test this or compare with others in this forum?

FYI, I unplugged immediately after my batt tuned 100%, if I would have left it longer I probably would have had less drain.
[Android General] Portgas D. Ace:
You should let your device connected to your charger for about 10 - 15 minutes after the battery level has reached 100%, as the real value is actually lower than 100% and thus will drop faster. This is quite normal behaviour of batteries.

For your thoughts about faster battery drain: in my opinion there is no real comparison possible, but you might try using some kind of daily routine (use Facebook for 10 minutes, then use other apps for some amount of time,...) to check whether this is true or not for different setups. Nevertheless, the best way to compare battery drain is to leave your phone idle for the same amount of time with different setups.
[Android General] @punto:
wanted to know one thing:

if i follow the settings from the post, do i get gmail notification as soon as i receive a mail? or does it delays the notification? when say in a deep sleep mode.

i an using amplify as well as greenify
[Android General] Portgas D. Ace:
Notifications should work as intended, but you can easily confirm it by yourself. Follow this guide and send yourself an email.
[Android General] @punto:
jst did but gmail not syncing automatically
[Android General] Portgas D. Ace:
Try unlimiting the com.android.vending/com.google.android.finsky.services.ContentSyncService
[Android General] LeppeRMessiaH:
Unfortunately FIX OP_WAKE_LOCK is greyed out in AppOps :(
[Android General] Celestial Fury:
I meant cell network coverage/connection. Let's see how severe the drain steps together with the dump. If you have a removable battery, you can try with another battery.
[Android General] Celestial Fury:
The drain that I see now comes from Maps and Cyanogen lock clock with weather update. Maps shouldn't be active in idle. Clear recent apps before unplugging. Weather updates will drain some battery.
[Android General] Celestial Fury:
Don't limit anything with push notifications or has sync in it and don't greenify the app in question.
[Android General] Celestial Fury:
It's available for me in version 1.28. You'll have to ask there why it's greyed out for you.
[Android General] vctrrl:
Battery is non-removable. I have a Sony Z1. I'll create another dump ASAP.
[Android General] J4M1L_4HMED:
Can you check this dump. My battery seem to good on Idle drain.
[Android General] Celestial Fury:
[2.0%/h] isn't good. You've used it for 9 m 36 s which will affect idle drain. In BBS Settings - Advanced - UNcheck Alarms using API (it's less accurate). Then take another idle dump.
[Android General] The Lord Vader:
Thanks for a really great thread and great advices, one of the best threads on XDA!

I followed your advices, so deep sleep is pretty ok now.

Can you take a look at my BBS dump to see if there's anything to improve?

Thanks!

https://www.dropbox.com/s/73xax2wcbfsm8iq/BetterBatteryStats-2015-07-01_062539440.txt?dl=0
[Android General] Portgas D. Ace:
0.2% per hour is quite good. Nevertheless you coud try to limit the alarm android.appwidget.action.APPWIDGET_UPDATE, as it keeps running approximately every 6 minutes. If you don't need this widget to be updated this frequently, you can limit this alarm to 3600s (1 hour), so it will only update once per hour. The rest seems okay for me.
[Android General] The Lord Vader:
Thanks for your reply! Only thing that concerns me a little bit is that my gmail doesn't sync as rapid as before? I guess that it's something I've changed in amplify...
[Android General] Portgas D. Ace:
Check the OP for alarms/wakelocks with the GCM symbol (blue cloud). Limiting those affects push notifications and thus should be used with caution if you rely onto them. You could try to unlimit one by one and check if this will affect your Gmail push notifications. Also check for alarms with keyword "sync" in it, as those are related to synchronizing, maybe those affect Gmail sync. I am of no further help here, as I do not use any Google-related apps on my device. [MENTION=5401012]Celestial Fury[/MENTION] might help you even more.
[Android General] Hopie:
can i limit this 3?

location, sync, wakeful?
[Android General] Portgas D. Ace:
Do they drain battery for you according to Better Battery Stats? If not, don't limit them. High number in Amplify does not neccessaryly mean high battery drain.
[Android General] @punto:
thnxx a ton sir...... will come here if i face any other problem.....
[Android General] Celestial Fury:
Yes, to what [MENTION=5901790]orville87[/MENTION] says.

I also see this:

Alarms: 14, Intent: com.cabooze.buzzoff2/.AlarmReceiver

Alarms: 8, Intent: com.google.android.location.reporting.ACTION_UPDATE_WORLD

I think Lolipop may have some functions for Silence Premium Do Not Disturb and ACTION_UPDATE_WORLD is in the guide.
[Android General] pikachukaki:
Great guide....i add as alarms i could found the biggest problem is Google play services and facebook messenger...i will keep looking at BBS and for help i could ask someone here!!!
[Android General] garthybarthy:
Hello,

Please can someone take a look at the dump attached from bbs, phone idle overnight.

Thanks.
[Android General] Portgas D. Ace:
According to your stats, you charged your phone during idle period.

Battery Info

============

Level lost [%]: Bat.: 5%(89% to 94%) [-0.5%/h]

Please charge your device to 100%, unplug it and leave it idle for about 6 hours (over night) with WiFi turned on, if possible.
[Android General] garthybarthy:
No I charged it and unplugged overnight, wasn't charging at all. WiFi was off though.

Edit: its took the log from boot rather than unplugged, my fault. So have to start over again tonight, it did go from 100%-94% tho overnight.
[Android General] easwar007:
wakelocks :(

i did as in post #2

other than that i have these wakelocks and alarms which are draining my battery

what to do!?

View attachment 3388228

View attachment 3388229
[Android General] Celestial Fury:
Use BBS to show drain not Amplify. See Post #3.
[Android General] easwar007:
Wakelocks :(

Ok here it is.

Is it the wifi causing all this!?
[Android General] Celestial Fury:
You've already used the phone for 30 mins. It's no longer idle. Charge it to full then leave it alone for 7 hours or so. Then attach BBS text dump before you use the phone.
[Android General] easwar007:
Ok thanks! I will try do so.
[Android General] vctrrl:
Here goes. Overnight, not in airplane mode.

No drain while powered off. Almost 1% per hour, even using amplify, even while on airplane mode as the last dump shows.

Cannot determine if the battery is faulty or if there's something I'm missing.
[Android General] Celestial Fury:
Your signal seems ok. How do you get negative alarm?: Alarms: -7, Intent: com.oasisfeng.greenify.CLEAN_NOW I see the drain now. It is here: too many wakelocks. It should be mostly clear. Your BetterBatteryStats version: 2.0.0.0. I think that was before Lolipop was out. There are some changes since then that could be relevant like:

2.0.0.0B2 #506: alarm details missing in dumpfile

2.0.0.0B4 #528: Partial wakelocks show wrong values

2.0.0.0B6 #550: missing strings

2.0.0.0RC4 #618: add info to dumpfile is alarms/kernel wakelocks are from API.

I can't see where the wakelocks/alarms could come from in the dump. Try again with the latest 2.1.0.0_B5.
[Android General] Xpid3r:
Here is my Dump file..

it drains alot and Google play is showing Fc when i set your recomendations
[Android General] Celestial Fury:
FCs - did you Greenify Google Play Services or use any other app on it? If you say it's Amplify then a simple test is to disable Amplify, reboot and see if it still FCs.

Your Screen On (): 9 m 47 s. Not possible to take the dump in less than a minute?

These are all in the guide. You've limited them accordingly? They shouldn't occur so high but your using of the phone will not give an accurate reading.

Alarms: 18, Intent: ALARM_WAKEUP706349 (the fix for this is in Post #2 under Not Recommended)

Alarms: 12, Intent: com.google.android.intent.action.GCM_RECONNECT

Alarms: 6, Intent: com.google.android.gms.gcm.ACTION_CHECK_QUEUE

Your antivirus. Can't tell if it's triggering during idle or during use.

Alarms: 5, Intent: com.textra/com.mplus.lib.xn

How did you get a negative alarm? Use the latest BBS version.

Alarms: -1, Intent: ACTION_TRIGGER_IDLE
[Android General] Celestial Fury:
Firstly, is it idle time, that is you did not use your phone for 7 hours or so? See Post #3. Posting screenshots of Other, Partial Wakelocks, & Alarms (+ details of top 3 alarms) will help.

If you didn't use Whatsapp during the idle period and its alarm is high then limit it. If you were using it then its alarm will naturally be high. Need to see the details of google.android.gms in idle mode. High use in Amplify doesn't necessarily equal to battery drain in BBS. Use BBS to diagnose the problem. Use Amplify to fix it. Anything that doesn't cause drain, leave it alone (unless it's for ads or privacy).
[Android General] amarbunty:
thanks it works :)
[Android General] E66666666:
com.google.android.gms seems to be quite active. I just disabled Google Now, would that help? Here's the screenshot of those details.
[Android General] Celestial Fury:
That's actually a collection of individual Google alarms. Firstly, ensure that they are alarms active during idle time and not when you have used the phone. MCS_HEARTBEAT apparently has no affect on being limited as reported by the Dev himself if the name is any hint. Unbouncing com.google.android.intent.action.MCS_HEARTBEAT has no effect For GCM_RECONNECT, GCM is probably Google Cloud Messaging.

From your screenshot, 12.6/h is definitely not idle time so any recommendation won't be accurate. So you need to get screenshots of idle time. See Post #3.
[Android General] Phoenix232:
These are my stats after limited the alarms and wakelocks. And I limited GCM_RECONNECT for about an hour.
[Android General] Celestial Fury:
Partial wakelocks seem fine. There's 8 mins of awake time to find though. What details under Android (Alarm)? Under com.google.android.gms, only 3 stand out:

checkin.EventLogService$Receiver

location.reporting.service.Dispatching.Service

ALARM_WAKEUP_BURST_COLLECTOR

Try limiting these - be sure to check GPS & maps functionality and any reboots.
[Android General] E66666666:
And here's mine, after an entire night of not touching it. Google Search really seems to be the culprit.
[Android General] Celestial Fury:
You've got the idea already. :good: Google quicksearch can surely be limited (more). Try limiting the eventlogservice$receiver as well. See if MCS heartbeat (affects sync) can be limited as well even though the Dev said there's no effect. Don't forget to check for functionality and any reboot.
[Android General] Cj Marquez:
After all night no touching my phone

Hello all, any comments would be appreciated. Attached my screenshots
[Android General] Celestial Fury:
Net Scheduler, Google quicksearch, facebook orca. Also deny the services in Post #2. Your last 3 screenshots, it's clear that it's not idle time - the difference with the first 3 screenshots is too large.
[Android General] Cj Marquez:
Thank you, I'll do the exercise again tonight and will post again.
[Android General] Cerberus_tm:
Hey [MENTION=5401012]Celestial Fury[/MENTION], thanks for this very useful thread! I am sorry to hear about your loss. I hope your phone will get well. So you denied the GPS permission to Google Services: what programme did you use to do that? Xprivacy?

I'm still not sure how having the GPS on for hours would damage your hardware! When you navigate in the car, GPS can be on for hours too...and how can the GPS' being overtaxed cause the cellular radio to break down?

A question about Amplify: is it true that Amplify does not affect anything that happens when the screen is on? For example, updating the location when you're using Google Maps?

When my phone is off, I would want almost all things to be off. I don't need my phone to update my location at all when it's off. The only thing I want it to do is keep receiving push messages, my alarm clock going off, and receiving reminders from the calendar application. I presume that will all still happen?

Now suppose I amplify some alarm resulting in my calendar not being synchronized immediately when the screen is off. That is what will happen, isn't it? Will my calendar then synchronize immediately as I turn on the screen?
[Android General] Celestial Fury:
I used XPrivacy to block location completely for Play Services (which shared an ID with other things like Backup , etc. Only 2 or 3 items that had "cell" in them was not blocked. The thing to note is I did not link the loss of signal with blocking this permission immediately. It was only the next day that I realised this was the only significant thing I had done. Unless it's a coincidence and the signal and GPS was already on its way to oblivion. I've had the GPS on for hours before in the car.

The phone was hot when I checked it 6 hours later and stock battery graph showed the GPS active throughout that time. Unfortunately, I did not check BBS or Amplify to see what was using the GPS. What I'm suspecting is something fried and perhaps the cellular connection is located near the GPS connection on the motherboard. Maybe someone can confirm this. Xperia Z1 disassembly guide.

I think Amplify should also be limiting alarms/wakelocks when the screen is on. It's easy to check that they are being blocked because the number of block alarms/wakelocks will rise even while using the phone. I'm sure I've noticed this.

0.0%/h idle drain was gotten before updates to Play Services caused the limited Backup wakelock to initiate a reboot. I had to reset all the alarms and wakelocks but as I remember I did not have to limit WhatsApp so push notification was instant. I think WhatsApp may also have other ways to sync besides Google's sync alarms. Unfortunately, I cannot remember if I limited sync alarms at that time.

Depending on how often you add events to your calendar, it should be enough for it to update twice a day and not cause drain. I don't think I've seen the calendar alarm starting up in BBS after I turn the screen on. The time limitations placed on them should work regardless of screen on or off. However, I shall keep an eye on this.

Nonetheless, whatever limitations you impose, you need to recheck for functionality according to how you want things to work.
[Android General] wahuka:
Hi all.

I'm new with Amplify.

Forgive my ignorance.

I see many wakelocks and Alarms first post did not appear in my OnePlus.

I understand that Facebook did not have to appear if I have not installed, but is that the list only shows me 5 or 6 between wakelocks and alarms.

I must wait longer to collect more information BBS?

sorry for my English.

Thank You
[Android General] androidTitan:
Please kindly impelement copy nd paste.Thanks :o
[Android General] Celestial Fury:
Alarms/Wakelocks won't appear in Amplify until they actually run. If they don't run since Amplify was reset, they don't show. In BBS, if they don't cause drain, they don't show either.
[Android General] Celestial Fury:
I didn't create the app. I'm also waiting for copy+paste. See Post #2 for Amplify forum link.
[Android General] E66666666:
At this point I should mention this IS a 2+ year old Galaxy Nexus (got it a year after release), so drain MIGHT be inevitable. Though, Google still seems to claim 23 minutes keep-awake. Those wakeup triggers for Google Search don't seem to have influenced drain percentage at all.
[Android General] Alexsk8.93:
Titanium backup

Hello Guys,

And Thanks OP for this post, it's really useful! :)

Can someone make a titanium backup of the custom amplify settings? I think this is the only way to export settings :D
[Android General] thegios:
When you say "xxxx seconds every yy hours" what do you mean? In the settings i see no "every yy hours" but only "every xxxx seconds"

Also, I am posting some screenshots from BBS and my Amplify settings: is there any improvement I can do?
[Android General] vctrrl:
Another dump. Again, negative wakelocks from Greenify :confused:

Can't trace where's the drain is coming. Feels like Amplify is doing nothing but hide alarms and wakelocks from BBS as the drain remains.
[Android General] ar2o:
Hey Celestial Fury

I have been following your guide which is very well done and I appreciate the time you spent not only to post and update the guide but for answering everyone's individual questions regularly! Gratitude to you sir!

I attached 2 screenshots, one shows my exchange account and the other shows my calendar. My exchange account is for my work, so it syncs every hour Monday to Friday from 9am-5pm, and from 5pm-9am on weekdays and all day on weekends it syncs every 4 hours. My calendar has my work meetings and events scheduled. Do you think if I lit these starting at 7200 seconds my email and calendar sync will be delayed? I have a Gmail account syncing every 4 hr daily but that doesn't show any drain in BBS. Any advice is much appreciated.

Sent from my PopRocks V6X Xparent Skyblue Tapatalk 2
[Android General] Celestial Fury:
Amplify can't hide anything. BBS gets its info independently. I've mistakenly saw your graphs screenshot as the one from battery details. BBS shows more wakelocks compared to battery details. I think this is normal as battery details gives a less detailed representation of wakelocks. Still, we need to find the cause.

In BBS graphs, select save and attach the file here. It should be in the internal root SD. This is to search for the drain skipping I mentioned initially.

For next dump, also reset Amplify stats and after idle period, attach screenshots of alarms and wakelocks from Amplify. Let's see what Amplify reports as being triggered that BBS doesn't seem to show.

Since Greenify is showing negative alarms, disable it for this idle period. With draining wakelocks and alarms limited in Amplify, there shouldn't be anything left for Greenify to put to sleep anyway.

Attached the log with the negative alarm and report to BBS thread. Negative alarm seems like a bug.
[Android General] Celestial Fury:
[MENTION=6388973]ar2o[/MENTION]

Are you using a stock calendar? If so, if you limit it then its calendar alarm will not alert you properly and its synching is probably affected. In short, stock calendar triggers too often for no good reason. You can try the alternate calendar app in Post #2 that doesn't need to be limited at all.

I don't use Exchange but you can test yourself easily. If you want it to sync every hour then limit its two alarms to 3600 secs. But after every hour manually open the app yourself to see if it syncs. Opening the app will force a sync.
[Android General] HH6:
Hey guys!

Could you help me squeeze out any more performance of my phone in idle mode?

I'm very happy the way it is at the moment, but if possible to do more, I want to do more! :)

Cheers again for this awesome thread!
[Android General] Celestial Fury:
[MENTION=6782998]HH6[/MENTION]

This. It shouldn't be active in idle. And com.facebook.orca. Your mobile data was on during idle? Huawei seems to be managing drain better than other phones.
[Android General] HH6:
OK, I will try to limit both of them :)

Yes, mobile data on all the time.

Recently used apps; you've asked me to clear them before. What's the reason?

I do clear them as a routine once in a while as well, but sometimes I don't want to..

Thanks