yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) General] chris23445:
It honestly seemed to happen every day or two. It was so often I couldn't stand it. But I restored Power Nap from Titanium Backup and I did have Moto and Moto Display and all that whitelisted. But I added some new stuff to the Whitelist. "Moto Display System Process", " Motorola Services" and "Motorola Services Main". I also added a few more. I basically added most Motorola apps just to be safe. I'll report back if I don't have the issue at all this week.

I wanted to let you know I followed your guide, I didn't block as much of Google Services in Amplify cause I'm actually a fan of Google showing my location map and all that. But my battery life is much much better already. Both on screen and off. Also, I found out through AppOps a ton of apps were using my location when it was on. I navigated for 30 minutes yesterday and barely lost 10% battery, maybe even less. Before, I would have easily lost at least 20%. Thanks again for everything!!
[X Style (Pure) General] abupxavier:
Fjjd
[X Style (Pure) General] dlepp22:
What are your battery stats with this setup?
[X Style (Pure) General] chris23445:
Click the button in his post, the "click to show content" button. It literally shows all of his battery stats.
[X Style (Pure) General] timde9:
Okay so I am having an issue after following this guide. Keep in mind I was actually already using amplify first before I read this based on the same threat you reference so I just essentially added powernap into the equation and apops exposed. Everything is great except smart lock location no longer functions and I can seem to figure what it is that's causing it. Smart lock on body detection and Bluetooth detection work fine so its specifically to do with location bit I cant seem to figure it out. Any idea?
[X Style (Pure) General] rehpyc:
Sorry for the late response.. final holiday projects at work keeping me busy :( I'll try using smart lock myself and see if I have any issues.

For those that may not have received their invite to the Power Nap test group yet, it seems you may be waiting quite a while. I updated the info in the OP of how to still obtain the app.

If you aren't happy with the battery stats you're getting after these changes, I'll soon be adding stuff to post #2 to help assist you on your way in determining the app(s) sucking up your battery. I've also recently flashed AICP ROM, so I'll be able to do some testing of how things go on a non-stock build.
[X Style (Pure) General] bslow1:
Is Greenify even necessary if you're already using Power Nap and Amplify?

As far as I can tell, any app that you would hibernate with Greenify is automatically blacklisted by Power Nap as long as you don't actively "whitelist" it. Is that accurate, or am I missing something?
[X Style (Pure) General] knince:
how is the battery life after MM update?
[X Style (Pure) General] bslow1:
For some reason, my Moto Display will stop working after a reboot when Power Nap is active. (After every full recharge, the phone is programmed to reboot itself so it starts fresh). Many times when the phone reboots, everything is fine, but occasionally, Moto Display will stop functioning and, even though it's checked off in the Moto settings, I need to toggle it off/on and reboot the phone again to get it to activate.

Does anyone else experience an issue like this? Is there something else that needs to be whitelisted to ensure that Moto Display keeps working with Power Nap?
[X Style (Pure) General] chris23445:
I had this issue before, and I disabled every single application that remotely had Motorola in the title, and it still froze. Power Nap really helps with battery when the phone is not in use, but I can't deal with Moto Display freezing. It literally freezes my entire phone and I have to force a reboot. Hopefully someone can help us figure out how to solve it.
[X Style (Pure) General] BigTrimma:
I had the same issue with moto display freezing. For me, whitelisting the moto apps and a reboot worked.
[X Style (Pure) General] chris23445:
That's what I did. After a few days it will start freezing again. I gave up and disabled it again.
[X Style (Pure) General] rehpyc:
Updated the first 3 posts, since the thread was initially created for Lollipop. Will be trying out Orion OS and AICP to compare to the results I typically get on TruPure w/ Frankenclark.

If you typically get 5hrs+ of SOT w/ at least 24hrs+ of charge, share what ROM/kernel you use for others to try out.
[X Style (Pure) General] rowlers:
Stock MM, xposed, greenify and amplify. Easy 5 SOT...
[X Style (Pure) General] Sheetzie03:
Been seeing A lot of people who run xposed on stock saying its a major player in battery drain, So while in your specific situation, you may be getting nice SOT, I wouldnt say by any means its 'easy' ..a big part is the difference in apps from one user to another,I'm sure u know this.. I wish a user can run this, this, and this, and that will equal a certain amount of battery life...

Thing I don't get is how can 1 person say they run xposed and its not causing and drain but another person says that it does . Now I know different apps people use play a major part and how people use their phone, but there is no explanation behind 1 saying xposed causes drain and the other gets 5hr sot while running it.

One last thing, some have the opinion that greenify isn't needed in Marshmallow. I don't know enough about it to say whether its true or not.
[X Style (Pure) General] gpz1100:
Are you using your device for any google services? How would google voice/gmail notifications work with the settings in the OP? What about imap email? I'd think the high values used for various alarms would affect this.

Mainly I use mine for imap/2 accts with 1 folder in each using aqua mail. I also need phone/SMS to work and google voice (texts).
[X Style (Pure) General] rehpyc:
No problems with sms/Gmail. Any app that you want to update automatically, just make sure to whitelist it with PowerNap. I use to use GV, so no issue there.
[X Style (Pure) General] Makalicious:
Based on observations from ROMs other than stock, are they even an option for you personally? I feel like while they are all snappier and some even more fluid than stock, none even come close in battery life. I don't charge overnight and first thing I noticed with all the customs is 25+% drain overnight vs 5% stock.
[X Style (Pure) General] rehpyc:
Honestly, no ROM should drain 25+% overnight, especially with MM introducing Doze. There's gotta be something that would keep waking your phone up, though weird that it wouldn't happen the same on stock. I've yet to have a custom ROM use more than .5%/hr overnight. The ROM and kernel combo has had each range anywhere between .1-.5%/hr. If you ever get a chance, fully charge your phone before you sleep, and then unplug it right before you go to bed. When you wake up, open Better Battery Stats (linked above) and create a log dumb (share button). Feel free to PM me that file.

The best I could get with AICP was 5 1/2 hrs of SOT over a 2 day period. I'm not one to care how much SOT I can get in a day, since I never care to be on my phone that much, so I always gauge things over a 2 day charge. It seems I'm going to get about the same with Orion, though I haven't done much tweaking to its kernel yet. Orion is definitely the smoothest ROM I've tried thus far, but TruPure w/ Frankenclark kernel has by far given the best SOT/endurance. Part is due to how optimized and the variety of governors available for Frankenclark compared to the kernels that some of these ROMs come with.
[X Style (Pure) General] gpz1100:
If anyone is looking for powernap, finding it appears to be challenging, especially the all elusive 0.7a version.

See pics/md5 in this post to confirm attachments: http://xdaforums.com/showpost.php?p=63294720&postcount=1213

https://plus.google.com/100850530627319687588/posts/VTcVMxb1nFU
[X Style (Pure) General] rehpyc:
Gave OrionOS a shot, and while it feels fluid and didn't have any issues really, the battery life just isn't there. The kernel doesn't seem very optimized for standby, and I wish it could clock lower.
[X Style (Pure) General] somecro:
Guys I have a question about battery life.

I have a Moto X Style on Stock Android 6.0 + Frankenclark v0.8 + SuperSU 2.62-3. I'm also using Wakelock Detector and Greenify to Hibernate certain apps. The problem I'm having is that Cell Standby takes about 10% of my battery life and because this is my first Android phone, I have no idead if that's a bad thing or just normal? Also the problem I'm facing is that I'm getting sudden steep spikes in my battery life. Will post a screenshot of my battery stats and my Wakelock Detector after I empty out my battery.
[X Style (Pure) General] gpz1100:
To the OP,

Can you post the file below.

/data/data/com.ryansteckler.nlpunbounce/shared_prefs/com.ryansteckler.nlpunbounc_preferences.xml

I've been fighting with amplify/google to try to get wakelocks/alarms down but seem to be getting nowhere. Either it sleeps good and google services don't work (specifically google voice texts/notifications), or not and things work as they should.

It's a relatively small file and contains no personal info, just the entries you have disabled/blocked/adjusted through amplify.

Thanks
[X Style (Pure) General] dkeepitabuck:
Is this really necessary if you are on a custom rom with a modified kernel such as TruPureXMM?
[X Style (Pure) General] gpz1100:
I don't believe a kernel has any control on what apps/services are running in the background. A custom rom has less background services than stock. Unless you're not using anything google related, there's still a bunch of google services consuming resources present.
[X Style (Pure) General] rehpyc:
^ This.

A modified ROM will have a lot of bloat removed, which helps keep that stuff from running in the background. It's why you don't have to disable a lot of apps/services in the OP, cause they have already been removed in a custom ROM.

A custom kernel will have various governor, speed, and memory tweaks made, which will help affect the performance and standby battery use.

gpz, I'll pm you that file tonight. Charge your battery to 100% before bed then unplug it. In the morning save a BBS log and send it. Don't keep WiFi on overnight for this.

P. S. Just noticed I never updated Amplify since Lollipop lol, so I'll update more stuff in the OP tonight as well. I only lose about 0.2% overnight.
[X Style (Pure) General] gpz1100:
Thanks.

As an experiment I've unchecked google play services and framework in powernap. I white listed google voice (which I use for texts) and my email app (k-@ mail). About to head out to dinner, will take my other phone with and leave the moto to idle.

About the only other app I use occasionally which needs to have sync capability is hangouts (for inbound voip calls). I'll add that to the white list later if the above tests out good.

Prior to the above experiment, i'm getting ~8-9% battery loss over night, with the phone in airplane mode, wifi on, email client in sleep mode (imap disabled for night time hours). This is not acceptable. My old s4 on GPE with amplify literally sips battery when idle or in use. If I can't get these WL/alarms under control, downgrading to 5.1.1 will be a consideration. Really, for what I do with the phone, 6.xx doesn't over much improvement over 5. Hell, 5 might even run faster.
[X Style (Pure) General] rehpyc:
Will help you try to get this battery performance!
[X Style (Pure) General] chris23445:
Can I ask you a noob question? I used to have BBS working great, but I can't figure it out anymore. I open it and it tells me to install it as a system app. I click the button in the app to install it as system, and then it says to reboot. I reboot, open the new app icon, and it never works. Am I doing something wrong?

Also, that screenshot you posted is insane. I'd love to see how it goes with you getting gpz to get better battery life. I lose about 8-9% overnight too. Phone isn't on airplane, but mobile data and WiFI are off.
[X Style (Pure) General] jmark13:
Are your doze settings in seconds or milliseconds?
[X Style (Pure) General] gpz1100:
I'd say seconds. 900 ms is barely a second. Wouldn't make sense.
[X Style (Pure) General] rehpyc:
[MENTION=7332704]somecro[/MENTION] Depends if you are constantly in an area with bad reception and how long your phone is up for. In pictures attached to this post with my most recent results, 22% of my battery was consumed by cell standby. You'll see I frequent areas with some pretty crappy reception, which will heavily drain any phone's battery, and also was off a charge for over 2 days (so inherently will have standby drain).

[MENTION=2179192]gpz1100[/MENTION] File you requested is attached.

[MENTION=4977878]jmark13[/MENTION] Doze settings are set to seconds.

Attached are my latest results with some additional tweaks in Amplify (will update OP tonight/tomorrow) on Frankenclark 0.8 kernel. Was a few updates behind with Amplify it seems lol. One thing to note, notice how my phone is primarily only awake when the screen is on, and otherwise it's not really awake too much else. In the BBS screenshot, you can see out of 2d 7h 54m without a charge (impressive alone), the phone was only awake 52m 50s when the screen was off. THIS is what you should hope to achieve, unless you heavily depend on push updates from many apps.

Results: 6h 46m 55s SOT w/ 2d 7h 54m 38s off a charge. (Btw, to those who argue that a turbocharge won't last as long as a normal one, the charge was off a turbocharge)

If you guys want my help in finding culprits to your battery drain, you need to charge your phone to 100% before going to bed and then unplugging your phone. Leave WiFi off. When you wake up, immediately open BBS and save a log file (share icon, then save). Upload this file and I'll help review it. You should only lose .2-.5%/hr overnight. DO NOT send a log from a period in which you've been actively using your phone.
[X Style (Pure) General] gpz1100:
Thanks for posting. I've gone ahead and implemented your settings and added Google Play Services, and Google Services Framework to the powernap whitelist. I did see a high wlan wakelock in the kernel stats of bbs. Going to try a static ip instead of dhcp. If that doesn't work i'll assign the phone to the guest wifi network.

Note; to keep from having to charge the phone up to 100% each time for testing, BBS has a custom reference option. I set that, clear amplify & powernap history before each test.

I keep the phone in airplane mode with just wifi on to eliminate cell reception potentially affecting battery drain. Signal here is ok but not great (amber color in battery stats).
[X Style (Pure) General] rehpyc:
Wlan wakelock can be attributed to either a weak signal, poor router output, or dhcp. Typically it's the latter, so setting a static IP should help clear that up. While BBS does have a custom reference point, and admittedly I will sometimes do the same, you should at the least wait and set the reference point immediately after the battery drops a percentage. Else the resulting stats can be skewed, albeit not by a large margin. Lastly, the main reason why I want you to keep WiFi off is that some apps like to sync/download in the background on their own, which will keep the phone awake. Amber color typically will drain my battery ~5-7% over a 10 hour period.
[X Style (Pure) General] gpz1100:
Did another test this morning. Charged it up, then let it sit all day (~7hrs). Saw the same .3%/hr draw. Went from 97% to 94% by the time I returned. You're right about possible skewed data. Still, this is much better than what I was seeing before. Tonight i'll test with wifi off over night. I really expect it to maybe lose a percent, if any at all.

Of course, keeping wifi off defeats the purpose of a smartphone. Controlling these syncs while wifi is *on* is the trick. I think the static wifi assignment helped. That is, static assignment in the phone itself, not static dhcp on the router.

If it all goes well, tomorrow i'll make another twrp image then re-introduce double tap 2 wake. On my previous tests, that caused significant battery drain. In fact, I think that was one of the key contributors before. Other users in the thread claim not to see such an impact, so we'll see.

I think the key to all this is one step at a time without introducing too many variables all at once.
[X Style (Pure) General] dkeepitabuck:
Does everyone use these settings on top of having battery saving mode enabled?
[X Style (Pure) General] DrunkUncas:
Implemented most of the things listed in your guide last night before bed, and my phone slept like a stone. .3% per hour. Outfrigginstanding!

The one issue I'm hoping you can help me track down is that my Moto Display works, but won't unlock the device. The unlock toggle moves down, or up, if I've got notifications, and freezes. Device still unlocks just fine with the power button.

I installed Amplify, but didn't set it up- nothing was populated yet. Everything else was done to your specifications, more or less.

Thanks

ETA: Fixed. Added Moto Display to power nap. Didn't need to add the associated services.
[X Style (Pure) General] ban.codrut:
Now is part of Xposed Repository(added v0.7 on ~15/04). Plus the dev said it will resume development sometime next this months

Inviato dal mio XT1575 utilizzando Tapatalk
[X Style (Pure) General] Corduroy-21:
I've been having wakelock problems the past days. The phone is awake all the time in the GSam stats. Although battery life has not deteriorated that much, it's annoying to see the phone being always awake. Is there any way to find the culprit with no root?

GSam has no further info as what causes the wakelocks.
[X Style (Pure) General] rehpyc:
I prefer using Better Battery Stats (BBS) vs. GSam - Download it HERE. Check the partial wakelocks and alarms that keep waking up your phone. I've been able to get my phone down to 1-1.5hrs of awake time over a 2 day span, which obviously bodes very well for battery life.

P.S... Gonna be updating this thread in the coming days
[X Style (Pure) General] Corduroy-21:
Thanks, but I thought BBS needs root to show this info. Am I wrong?
[X Style (Pure) General] ban.codrut:
The lates update uses a walkaround the permission request using some sort of API (if I remember it right) to get battery stats. It depends on device's os but it should work without root right now. Otherwise, in case it doesn't work, there is an option buried deep in the setting menu to revert to traditional root method to get the battery stats.

---------- Post added at 02:08 AM ---------- Previous post was at 02:02 AM ----------

I can't understand if you have already updated the post or not... so you made the changes already :) ?

(I'm not trying to be pushy in any ways!)
[X Style (Pure) General] ban.codrut:
There isn't a list anymore ...
[X Style (Pure) General] rehpyc:
No update yet (I'll make sure update the OP to begin having a changelog lol). Been busy working on some kernel tweaks for the Frankenclark kernel, so check those out even if you use a diff kernel. I aim to have a big update on Monday.

AppOpsXposed pretty much became useless with us being able to control app permissions in MM Apps settings. I'll be cleaning things up in the OP Monday tho.
[X Style (Pure) General] rehpyc:
OP updated. Let me know if you guys run into any issues.

The BEST way to have me help you out would be to provide BBS logs along with some of your battery drain issues.
[X Style (Pure) General] zohar_ml:
Should I post the logs here?

I keep getting 2%hr while the phone in doze mode :(

Can you post the most up to date

/data/data/com.ryansteckler.nlpunbounce/shared_prefs/com.ryansteckler.nlpunbounc_preferences.xml?

Best if you can add it to the first post.

Zohar
[X Style (Pure) General] rehpyc:
Can link your BBS log to a post or PM me.. wouldn't put the entire log in a post lol.

I'll create a zip file to flash the xml file to make it easy :)
[X Style (Pure) General] zohar_ml:
I'm attaching my BBS log.

Having a 1.5%h with 96.8% deep sleep :p

In the past I did hade nights in witch battery went very low, and I don't know when it changed.

I even tried some other roms with no change.

In previous test I had 100% sensor time, have no clue why tonight it went to 0.5%

Currently using TruPureXMM 2.8.2+ frankenclark-0.12 test3, 300hz, s2w, redhawk, rehpyc_misc

Copied your amplify xml file.

Thanks,

Zohar
[X Style (Pure) General] rehpyc:
With using Frankenclark, do you have the wlan wakelock blocked? Check Kernel Adiutor for that, since I'm seeing:

wlan_wow_wl (): 7 m 18 s

What kind of tasker profiles are you running, cause Tasker seems to be keeping your phone awake quite a bit:

net.dinglisch.android.taskerm (): Wakeups: 51 (8.2 / h)

Alarms: 26, Intent: net.dinglisch.android.tasker.ALARUM

Alarms: 25, Intent: net.dinglisch.android.tasker.ANOFFCHECKORUM

The last thing I'd suggest is turning bluetooth off, unless you need it at night:

com.android.bluetooth (): Wakeups: 25 (4.0 / h)

Alarms: 25, Intent: com.android.bluetooth.btservice.action.ALARM_WAKEUP
[X Style (Pure) General] zohar_ml:
Didn't used Kernel Adiutor since i've installed this current rom (last week and from scratch)

In Kernel Adiutor, Misc Control, I have all three wakelock on. should I turn some off?

I use tasker to:

a) turn wifi on/off according when the bluetooth connects to my car.

b) make longer screen time out when reading news/internet.

c) change phone volume at night and turn it on before the alarm goes on.

d) and some more.

I may try to turn off tasker/bluetooth and make a short test.

-----

Did a short 1hr test: freezed tasker, turned off bluetooth, reboot, waitad abit and did the test. still -1% /h (still better then the -1.5% overnight)
[X Style (Pure) General] rehpyc:
Unfortunately 1hr isn't a good test.. typically want 6-8, since the phone doesn't doze immediately. WiFi wakelocks still are keeping your phone active, though. Try turning WiFi off and test. That wakelock can often be remedied with hardcoding the IP to use rather than using DHCP.
[X Style (Pure) General] zohar_ml:
5.5hr test with -1.4%/h. tasker + bluetooth off. I also changed to Frankenclark 12 with both of your scripts- gov_rehpyc + rehpyc_misc.

I will try to turn off the wifi tonight.

If i set a static IP wont I have problem to connect to public wifi networks?

In the past you had settings for doze editor. why did you take it off? (I do have one of the short presets on)

Zohar
[X Style (Pure) General] rehpyc:
Did you apply this limit in Amplify? com.google.android.gms/.checkin.EventLogService$Receiver (86400)

Does your chomp text app have advertisements? Could be safe to limit this to 99999: com.p1.chompsms/.adverts.AppAdvertsConfigDelegate

If you don't need automatic updates with News Plus, limit com.noinnion.android.newsplus/.reader.service.SyncService and com.noinnion.android.newsplus/.reader.service.CleanService to 86400

I did have settings for Doze Editor before, namely due to Greenify at the time not fully working well with ignoring motion in order to kick the phone into Doze. The custom settings with Doze Editor allowed for this, but now Greenify works sufficiently enough that it's not needed.
[X Style (Pure) General] mahdif62:
Can Amplify settings be somehow imported? Is someone kind enough to send me their settings?
[X Style (Pure) General] zohar_ml:
Yep, see this http://xdaforums.com/showpost.php?p=65900555&postcount=44

The file is from: /data/data/com.ryansteckler.nlpunbounce/shared_prefs/com.ryansteckler.nlpunbounc_preferences.xml

I had some hard time with copying the new file.

At the end, I've killed Amplify, opened the existing xml file with text editor, deleted all it's content, and paste the content of rehpyc file then saved the file.

I think I even rebooted after this.

Zohar
[X Style (Pure) General] mahdif62:
Thanks a million.