yashsingh1/xdaforums huggingface dataset:
[Android General] TNSMANI:
I have no idea except for what I can see from its name "barometer".

Limit it and see whether it affects any critical function. If you face any issue, unlimit it and reboot.
[Android General] Celestial Fury:
The point was the methodology and not the viability of the methodology. That is, screen on time can certainly be used to measure battery drain but screen off time will be a safer way without stressing your display. It wasn't that long ago that screen technology had problems such as burn-through and dead pixels. Also, the display has the biggest drain on battery and by eliminating it you eliminate the biggest variable.

Not Found

Error 404

I think you should test your phone's baselines first. See Post #3.

The way it works, by limiting it it will read the barometer less frequently.
[Android General] roman313:
Something i know

Something
[Android General] DB126:
Why? Do you have measurable drain associated with any of the alarms/wakelocks? Just because it shows up doesn't mean it's bad. Excessive/random/irresponsible limiting is a recipe for unpleasant outcomes.
[Android General] eshipp31:
dump

Can someone take a look at my dump file
[Android General] DB126:
Crosspost: http://xdaforums.com/android/general/guide-extreme-battery-life-t3095884/post70392883
[Android General] knpk13:
Oh yeah about this, why do we have 2 identical threads for battery life using the same tools?

PS: you're kinda cross posting too, haha.
[Android General] DB126:
On a macro level they may seem identical. Dig deeper and you'll find they focus on different objectives and often (albeit not always) utilize different tools and techniques.
[Android General] roman313:
I know and test only this

I know only this
[Android General] knpk13:
Huh that's interesting. I'll dig deeper then. With my new OP3T however, the battery life so much better than my OP2 that I don't really have much of an incentive to dig deeper. :laugh:

But if they are different, then shouldn't it be okay to crosspost in both threads?
[Android General] DB126:
Many of the same members service both threads. XDA guidelines encourage posting similar/identical questions in a single thread. If the response is less than satisfactory try another.
[Android General] inchvbeam:
which rom are u using for ur 3T
[Android General] knpk13:
Wrong thread, don't continue the conversation here.

But I'm using multirom. Primary OOS 4.0, secondary Lineage, many other secondaries for testing that I don't particularly like. I did like sultan's CM13 but made the move to Lineage 14.1.
[Android General] wongfeihung1984:
Hi everyone and happy new year!

I would like post my bbs dumpfile for the first time. I hope the more experienced of you will be able to help me make my phone better :)

You all have a great day.
[Android General] TNSMANI:
Start using Amplify and go through the OP (first post) of this thread and limit those that are recommended. Then update BBS to RC3 from its thread in XDA and post a fresh dump. Simultaneously take and attach a screenshot of the battery history details page in Settings.
[Android General] wongfeihung1984:
Thanks for your help...but I've already limited almost all the partial wakelocks/alarms I could with Amplify: a few I didn't so I wouldn't break notifications.

But what do you mean by "Then update BBS to RC3 from its thread" ? RC3?
[Android General] DB126:
"RC" refers to Release Candidate - a test version not yet available to the general public.
[Android General] wongfeihung1984:
Thanks for the tip. I've already asked to be part of the beta tester community. I'm waiting to download it and I'll get back to you.
[Android General] TNSMANI:
You still have a lot that can be limited. Check again. If you are not able to find them, I will help you after you post a fresh dump with updated BBS.

BBS has now gone upto version 2.2.2.0, so RC3 (Release Candidate) is not available. Update to 2.2.2.0.
[Android General] misterhong:
is it safe to limit this wakelock? *job*/com.google.android.apps.maps/com.google.android.apps.gmm.offline.OfflineAutoUpdateJobService

because suddenly it active for 10minutes showed on wakelockDetector.
[Android General] mrmcshagbag:
Best guide ever!! Has helped my battery draining so much! Didn't know battery life could get better until I tried this guide! Absolutely does not make my phone dumb either. Can still use it as normally would with no problems whats so ever! Thank you sooo much I appreciate your work!
[Android General] MasterChief2:
My phone is Letv Le 1 Pro US version.

I have huge battery drain and Android OS is on top when i go to Battery Statistic. I installed BBS, and my device was awake for 2-3 hours. When i go to Kernel Wakelocks in top 3 are qpnp_fg_memaccess, qpnp_fg_update_temp and qpnp_fg_update_sram. What are this services, can I delete them and how? Here are screenshots of BBS:

https://postimg.cc/image/b7yk7ghn1/

https://postimg.cc/image/cqd6pea9l/

https://postimg.cc/image/bcnt1jv0z/

https://postimg.cc/image/npirwpi49/

https://postimg.cc/image/nciywiuw7/
[Android General] mrmcshagbag:
I have no idea sir. I just followed the guide and used what was recommended. I'm not sure what those wakelocks are unfortunately. I hope someone else can help clear this up for you.
[Android General] lepa71:
Can somebody look at my newest dump? https://drive.google.com/open?id=0Bwga8b5AaM9EVlJLRjBUOXRIY3M

Also. What is MPL accel in GooglePlayServices? I think it keeps my phone on.

Thanks
[Android General] TNSMANI:
Your problems are here:

Your mail was syncing in the background. In addition,

Alarms: 44, Intent: com.android.server.LightsService.action.UPDATE_SVC_LED

Alarms: 17, Intent: android.appwidget.action.APPWIDGET_UPDATE cmp={com.sec.android.widgetapp.favoriteswidget/com.sec.android.widgetapp.favoriteswidget.SeniorFavoriteWidgetProviderSmall}

Alarms: 11, Intent: android.content.syncmanager.SYNC_ALARM

com.android.exchange (): Wakeups: 44 (5.1 / h)

Alarms: 38, Intent: {com.android.exchange/com.android.exchange.MailboxAlarmReceiver}

Alarms: 6, Intent: {com.android.exchange/com.android.exchange.EmailSyncAlarmReceiver}

Alarms: 8, Intent: {com.droid27.transparentclockweather/com.droid27.transparentclockweather.receivers.WeatherUpdateReceiver}

Decide what is important for you. Do you require all these syncing to take place while the phone (and probably you) is sleeping? If not turn off automatic sync.

There was a download of about 1 MB by Play Services. Were you on mobile data? I don't find the info regarding your WiFi and mobile data in the stats.
[Android General] lepa71:
I do need exchange sync for work. It is set to 15 min during off hours. I don't use wifi as it drains battery like crazy.
[Android General] TNSMANI:
Ok, if you can't, you can't.

But if you find that WiFi is draining more than mobile data, I would suggest that you examine that because for most people, it is mobile data which drains more.

If you can elaborate on that, I will try to help you since otherwise you can't do anything more to reduce your drain.
[Android General] danecr7:
Hello guys, some weird alarms from facebook started to show up in amplify recently(Xd.ACTION_ALARM.com.facebook.orca. and X.06K.ACTION_BACKUP_ALARM.Mqttlite.com.facebook.ka tana and a lot more) and whenever I try to block one, facebook create a new one with a different number in it and in my amplify app they are more than 20 actually so I try to find a way to limit them all using a regex and I thought it might be helpful to others in xda battery life threads.

Here is the REGEX is found matching all the alarms:

X.([0-9]|[A-Z]|[a-z])([0-9]|[A-Z]|[a-z])([0-9]|[A-Z]|[a-z]).*
[Android General] lepa71:
I believe it is a combo of my old TW 4.3 drivers and my work wifi setup. I can try to charge phone at work and let it idle with wifi enabled to show what I get. There was suggestions to assign static ip to resolve those issue, but I can't do this at work. At home I get really good signal and may be this is why it drains battery less on data vs wifi.

Thanks
[Android General] jututt:
You need _ (underscore) between Wakeup and [0-9]

CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]{4,}

Otherwise it will not work, every time you reboot final numbers change
[Android General] MihaiSG:
Try this regex to block all CONTEXT_MANAGER_ALARM_WAKEUP alarms:

CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]+
[Android General] lepa71:
I'm posting 2 dumps.

1. This is overnight idle with wifi on. https://drive.google.com/open?id=0Bwga8b5AaM9EOWlKNnp5M3I1WGM

2. This one is during the day not exactly just idle, but it shows wifi keeps phone up. https://drive.google.com/open?id=0Bwga8b5AaM9ER18xV3lvbUdSNVk

Any other suggestions would be appreciated?
[Android General] TNSMANI:
Your WiFi connection has issues and that is why it drains more. If you own the router and connection or if you can persuade the owner, set up a static IP for your phone. It may solve this issue. If not, at least try resetting the router.

Apart from that, as already indicated, (from your idle dump), it is your mail, AppWidget Update, Weather and Google Apps, LightsService, Heartbeat Alarm and 1 MB of background download by Play Services which played spoilsport with your battery. See whether you can do something about any of these.

This is the best I can give under the circumstances.

EDIT: You can also try a different kernel which can block the wakelocks due to WiFi.
[Android General] lepa71:
I can do static ip at home, but not at work and this is where the drain mostly happens. As for a different kernel, this phone does not have that many active kernels.

I guess that is max I can do.

Thanks for help.

ps. I may try 7.1 when I get a chance.
[Android General] sas_sas:
Hi all,

My xiaomi mi5 /64gb with several (MM and N) miui and custom Roms has 3-4% per hour drain while device power off as well as while airplane mode.

I experienced the same result with two different battery.

Those batteries do not loose any charge at all when they are disconnected from the phone.

Where is the culprit?

Do you think Amplifiy can be useful for any cure under those circumstances?
[Android General] SirRhor:
First you have to identify the cause of the drain. Use the following to find that out, and only then use Amplify:

https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats
[Android General] sas_sas:
Thanks [MENTION=4310653]SirRhor[/MENTION] for your concern.

Pls see the screenshots of BBStats app info after more than 8 hours standby period..

Can you and all other persons here comment what sucks the battery?

Hardware or software?

İf it is hardware no need to bother much..

Keeping in mind that phone is 98% in deepsleep and and 78% doze mode.

It seems to me the only remainig battery consumer is

"com.google.android.gms" alarm.

I wonder if this alarm can suck such a battery (almost 4% per hour)?

Sorry attaching pics instead Dump file. Though I tried to get dump file but its file always appears blank..
[Android General] Oswald Boelcke:
If I correctly understand you get a drain of 3-4% / hour even with the device switched off.

Please allow me to quote this post
[Android General] DB126:
While there are small drains that might be improved I would say the biggest issue is the device battery (likely old/failing). 34% drop over 6+ hours is not consistent with awake/sleep ratio and modest CPU activity during those 4-5 minutes of wake time.
[Android General] sas_sas:
Thanks for your valuable comments..

The below are results;

Battery OUT (removed) drain = zero/ per hour,

Battery ONLY drain = app. 4% /per hour,

Airplane mode drain = app. 4% / per hour,

Idle battery drain (only wifi is on) = app. 4%/ per hour

Standard phone usage battery drain = app. 6% /per hour..

BBStat is taken after 4 an half hour. Pls keep in your mind that this situation is almost same with two different new batteries meaning batteries are quite healty.

No extra apps are installed but a few battery and kernel tuning apps..

This situ is almost the same with many stock miui and custom roms too.

Probably a faulty hardware sucks it, I want to know what that is..

Dump file attached here;
[Android General] DB126:
Nothing jumps out as a smoking gun. Yes - there are the expected suite of idle wakelocks/activity that can be trimmed through various methods discussed in this thread and others like it. But no 'big hitters' unless I missed the obvious.

Might want to invest in a USB meter that tracks cumulative charge (can find them on Amazon for ~$10 USD). Bring the battery down to near zero then see how much juice the battery accepts on a full charge. Possible your packs do not live up to their rated capacity. Not uncommon, especially aftermarket.

Also possible there is a hardware drain that BBS and similar tools do not see. Rare but happens (eg: 'stuck' LED flash won't directly register in BBS).
[Android General] aryan531:
i am on cm 14 based on nougat 7.1 .... soo its clear that theres no xposed for it soo what can i do ??

any solution to limit wakelocks any alternative to amplify ?? or something

p.s : i am using greenify
[Android General] sniickers:
Yeah I get a lot of emails due to multi camera security system that emails me every motion. My neighborhood has very active people 24/7. My Bluetooth is always on connected to my Gear S. Mainly shooting email alerts and notifications from apps. And yes, no usage. As soon as I turned the screen on after 10 hours I took these screen shots.
[Android General] Celestial Fury:
With such activity, [1.3%/h] seems reasonable as your phone isn't exactly idle. Those 3 items I mentioned take up the most drain so reducing others won't really be significant.

But if you like, I think NLP wakelock can be further limited if it isn't already and whatever else under Google and Android alarms (the details weren't shown in the screenshots). Just use Post #2 as a reference.
[Android General] YudmudTR:
Is it safe to limit wakelocks/alarms which is in Safe to Limit section on Amplify?
[Android General] Celestial Fury:
Safe here means it shouldn't cause bootloops or cause a function to completely stop working. However, it may cause functions to work less well for some people. For instance, Sony storage alarm is listed as safe but I will occasionally get "SD card not available" in third party apps while others don't (or they don't notice it). Use BBS) as a guide on deciding what to limit and use Amplify as the tool to limit and not the other way around.
[Android General] dirty_smurf45:
DS Battery Saver is in my list and I want to limit it, BUT, the I don't know if setting the alarms for 7200 seconds (2 hours) will affect the actual deep sleep. Here are the alarms:

com.rootuninstaller.bartsaver.action.DEEPSLEEP_ON

com.rootuninstaller.bartsaver.action.DEEPSLEEP_START

What should I do?

Also, would the com.android.systemui alarm, com.android.internal.policy.impl.PhoneWIndowManager.DELAYED_KEYGUARD, affect the lock screen if limited?
[Android General] Celestial Fury:
Sounds like they both would but only you can test to confirm as I don't use it and the key guard doesn't drain for me. The battery saver I know will cause some drain (ironic) but I'll be surprised if the key guard does as well.
[Android General] Ok_Kaleidoscope5109:
I like the idea of baselining. I highly recommend this. However, I recommend baselining for both WiFi and 3G/LTE.

For devices like the Nexus 4, it performs pretty well on WiFi in terms of battery. However, on 3G, it performs like total crap. The modem is not part of the SoC and instead is on a separate chip that is connected via the USB bus. It tends to not do so well in releasing the USB wakelock and therefore you get massive msm_hsic_wakelock events. So a typical N4 use for me with standard location updates gave me 4-5% drain per hour. My N5 on the other hand with the exact same setup gave me 1% or so drain per hour. That's a HUGE difference.

In general, 3G/LTE should be more prone to battery drain not only because of the radio using more power to transmit, but because you run into typical issues like congestion, reception, etc. Under WiFi, you typically don't have any of those issues.

---------- Post added at 09:50 PM ---------- Previous post was at 09:44 PM ----------

Some additional comments. Extrapolating 0% drain is hard over such little time. I'd recommend measuring the actual drain over a longer period of time. I have seen it before where my phone takes 8-10 hours to drop 1% (down to 99%) but the next 9% are very fast.

It's hard to make a conclusion about a battery or drain by using only a small portion of the battery meter.
[Android General] Celestial Fury:
As you said, 3G/LTE would usually drain more than WiFi so setting a WiFi baseline is certainly useful if you're focusing on testing 3G/LTE drain (interesting info on your phone).

Definitely, the longer the period for testing the better. Fast drain upon turning on the screen can sometimes be attributed to alarms / wakelocks going off. It can clearly be seen in BBS a few minutes after using the phone. It all depends on hit the phone has been set up.

Also, some really draining alarms / wakelocks that are limited can manage to run in a longer test period such as stock backup which I've limited to run once a day but each time it runs it runs for 10 to 20 minutes or more.

Basically, I'm happy if I turn on the screen in the morning and still see a full charge.
[Android General] dirty_smurf45:
What battery saver do you use? Also, is there a way to get results like these but during phone use? I'm guessing I would need a task manager for this.
[Android General] Celestial Fury:
Amplify, Greenify, Xprivacy, App OPS, Sony stamina mode. Use phone without drain? Not possible.
[Android General] dirty_smurf45:
I didn't mean "without" drain I meant "less" drain but I don't really have apps running in background anymore so I guess I should just deal with it? Thanks
[Android General] Celestial Fury:
That's the next step, actually. Once work on idle drain is done, the next step is to work on active drain.
[Android General] dirty_smurf45:
Nice. Is it on here right now or are you still working on it? I'll be very happy once it's up ☺ Thanks for this guide btw?
[Android General] Celestial Fury:
Whatever's in the guide should also reduce drain while active. Any more than that will be up to the user as active drain varies even more than idle drain.
[Android General] dirty_smurf45:
Ok I got the point. Thanks
[Android General] aukhan:
[MENTION=5401012]Celestial Fury[/MENTION] please add date on the title thread as when was last OP update uve made so it would be easy to track if any changes like if you've added some more w,S, A.

Powered by ET !
[Android General] Celestial Fury:
Every time a post is edited there is a last edit date at the bottom of the post.

Post #1

Last edited by Celestial Fury; 11th January 2015 at 09:49 PM. Reason: Amplify can't limit kernel wakelocks.

Post #2

Last edited by Celestial Fury; 13th March 2015 at 10:07 PM. Reason: Added ad related services and alarms.

Post #3

Last edited by Celestial Fury; 12th March 2015 at 10:05 PM. Reason: Added link to post with newer screenshots.
[Android General] aukhan:
Agreed just thought it would be easier did it's a thread title [emoji14] no worries I can manage this way also. I am just a bit lazy to open the thread and check [emoji14]

Powered by ET !
[Android General] pratik_193:
[MENTION=5401012]Celestial Fury[/MENTION] -

i get too many wake locks from

RILJ1

Alarm Receiver

ActivityManager-Launch

Checkin Handoff

Checkin Service

MediaPlayerService

ScheduleNextAlarmWakeLock

can you help me if these are safe to limit ?
[Android General] aukhan:
Pratik follow the methods mentioned in post 2 and you shall see the progress. This guide needs a lot of patience.

Powered by ET !
[Android General] DB126:
Greenify and disabling rogue broadcast receivers and/or services are the best tools at present. That said, I find little need to overtly manage wakelocks on Nougat. Yes, they occur but don't significantly (operative word) impact battery life. Enjoy your device.
[Android General] jlb1959.01:
I have a context manager alarm wakeup 488194 that reads every night 4,5 times . what is this alarm?? .I have followed this posts directions to a tee,I've notice this alarm every night tho..
[Android General] Portgas D. Ace:
The CONTEXT_MANAGER_ALARM_WAKEUP has been known as a battery drainer for quite some time now. You can set up a custom regex with Amplify to limit such kind of alarms.

Use

CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]{4,}

and limit it to 9999999.

See this post for reference.
[Android General] jlb1959.01:
thank you very much......
[Android General] atzsmm:
Woo, thats looks great. Ill try it later. But Im wondering, is there any way to do it without xposed?
[Android General] DB126:
If referring to wakelock limiting (specifically CONTEXT_MANAGER_ALARM_WAKEUP) Xposed Framework and Amplify are required. Keep in mind this wakelock is not a huge drainer with a small number if hits. Unfortunately, you won't be able to assess the impact without measuring, limiting and then measuring again.
[Android General] papsr6:
Sorry for the stupid question but know someone a easy quide to setup my lg G4 because are to many setups ?

I try to search the first page setups but search not work and is very difficult to find all this wake locks and alarms.

Thank you
[Android General] danecr7:
Wakelocks need some days to populate, and you won't find all the wakelocks and alarms described on OP as you probably have different ROMS and devices.
[Android General] papsr6:
Thank you for the answer...
[Android General] bearthing:
thanks for the tips
[Android General] jackson_c:
Can anyone guide me with which Google Play Services alarms I can block?
[Android General] Bewildered Wolf:
Check the OP. You'll get what to block ?
[Android General] Oswald Boelcke:
When I replied to you here yesterday, I didn't suggest to double-post but to check and read the OPs of the two linked threads. You'll certainly find answers to your request.
[Android General] jlb1959.01:
I have a question,might not be the smartest but it has my curiosity..what exactly does context manager alarm wakeup do,for instance when you set the alarms etc what would happen if you didn't apply the context alarm.dumb question as its in the set up but I was just wondering..sorry for my ignorance.
[Android General] lepa71:
I have *net_scheduler* running 49 minutes but with only 3776 wakelock count. I tried to limit it with recommended 7200, but it does not seem to help.

Any ideas?
[Android General] Celestial Fury:
1) It used to be called just ALARM_WAKEUP####

2) Sorry, don't know much about it.

It doesn't affect the alarm clock but it may have an affect on android related alarms triggering.

Post an idle log according to Post #3 with *net_scheduler* limited at 7200 then we can see if it does or if it does not.
[Android General] jlb1959.01:
thank you,appreciate your help...
[Android General] eng3:
Do you have any tips for low phone reception?

Normally, I'll have 0.4%/hr idle drain

At my office with poor reception, it is more like 1.4%/hr. Basically, I'll see no signal at all most of the time but sometimes an email or txt gets thorugh. Phones calls can often get through too

I could ofcourse just put the phone in airplane mode but I often forget or forget to turn it back on
[Android General] DB126:
If your device supports it try 3G (or even 2G) which sometimes yields a stronger connection than LTE depending on location. Both are fine for voice and basic SMS. If that works there are a number of apps that can auto toggle between modes using various criteria.
[Android General] Oswald Boelcke:
I used to work in a high-security environment where no cell phones (or other electronic devices) were allowed at all. Prior to passing the security checkpoint, I locked the phone into one of the provided container and developed the automatic behaviour in this way to set the device to airplane mode. Alternatively, I simply left the phone in the car. But I know my experiences don't help you.

Maybe you want to try a tool like Llama or something similar?