yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] magnamentis:
there will never be a build that solves the drain issue because there is no build that is causing that issue. it's you(r) setup that causes it. if you read a bit through XDA it should be obvious the drain is either user space or due to a dirty install, 99.9% with very few exceptions and this build is none of those exceptions. if a drain is caused by a rom bug everyone or at least a vast majority will have it which is not the case.

the earlier you learn to troubleshoot battery drain the better for you (and for us readers) but then you have to admit first that it's on your side.

follow the below linked procedure step by step, by the letter and it will either be gone or you will know what it was.

a little hint, dont' be lazy (not sayin' you are, just a recommendation) give the steps in between time to test your battery consumption, make small steps and always make a nandroid backup after each step that was running without drain.

and be aware that directly after flashing there are background tasks that use a lot of juice, media scanner will be running and each app and component will have to settle first. that said, here is you tutorial how to troubleshoot and before you start it is recommended to use a "sophisticated" monitoring app that will provide max information as to the possible culprits.

last but not least, reported issues without logs did not happen, why didn't you provide a catlog for the dev so he and others can look into it

and perhaps tell after a minute where your issue lays? first comes proper analyzes, then reading and searching for troubleshooting solutions and then perform a clean install like or similar to the linked procedure.

http://xdaforums.com/showpost.php?p=62192068&postcount=4059

EDIT: and to make sure it's clear, my battery with xposed and 200 apps and 8 email accounts synced lasts almost 8h and sips 2% in 7-8h overnight.
[ONE Android Development] KeyperOS:
It appears it was YOU who didn't read well enough my post.

It WAS a clean install and I am not even going to dignify with an answer whether I followed the correct procedure, suffice to say I have been doing this for the better part of 7 years and across 5 devices. In my early days I also was a beta tester for an HTC ROM which meant flashing a new test build about every 3 to 4 days.

The restored apps were the exact same ones I've installed for 2-3 years now and in the exact same way. In fact I even cut down the list to the bare essentials (about 50 from 80 or so) to minimize the chance of an app screwing things up.

The settings I set up again were identical to the ones I've set up in the previous 10 or so RR builds I've installed.

The battery drain IS an issue with these builds, varund7726 himself said so, it simply isn't his mess to fix, it's CyanogenMod's.

As for the post you've linked, it is nothing but a noob guide to flashing and honestly, I am offended you even considered providing it in relation to my issue.

Now, if you have a specific advice about something that would help with the drain - others have suggested freezing the CyanogenMod System, clearing the data from the Contacts app, switching the location setting from High Accuracy to either Device Only or Battery Saving (I chose the latter) and even wiping and rebuilding the Dalvik cache and battery stats - please do post it here. As for me I tried all of the above with no success.

In any other case, I would kindly request that you stop needlessly filling up this thread with repeating generic, noob-oriented advices as well as veiled insults to members clearly more experienced than you.
[ONE Android Development] mmurphmsu:
I just want to say a big thank you to [MENTION=4841620]Timmmmaaahh[/MENTION]. A few weeks ago I posted about a microphone issue. You linked me to a YouTube video to change the mic part in the phone. I switched it out with a new part and it is working again. I really appreciate it.
[ONE Android Development] r25txe:
This is probably a really stupid/obvious question, but here goes ... If I want to reset the settings of the whole ROM to the way they would be as if I were after flashing RR for the first time can I just wipe data of the apps: Settings and CyanogenMod Settings and Advanced Settings? Or is there some other way of achieving it that does not involve a clean flash?
[ONE Android Development] magnamentis:
so you have a problem, i gave you the solution and you tell me that you know it all, no problem, so keep the problem which i don't have.

clean install is NOT enough as stated above. you have to follow the troubleshooting procedure to find the culprit if you want to get rid of it and that IS the solution for issues that are unaccounted for. you prefer to blame the rom, but it's not, it's YOUR setup and only YOU can fix it. spoon feeding doesn't work for most battery drain issues. there is no ONE single possibility that one can simply name. in each case and setup the culprit may differ.

but as you like i use 7 devices with 13 roms and have nowhere ever a drain for longer than 2-3 days until i perform what i recommended and it's found and gone. only for those who are ready to learn, even after 7 years. perhaps years are not the criteria, perhaps i could mention several hundred rom, kernel device combos with all kinds of mods incl. exposes, many on a nightly basis, all togther that makes thousands of setups and flash events. just sayin' since you brought it up. over an out, do as you like but dont' ask for help if you're not ready to try it out.
[ONE Android Development] suaverc118:
You could turn off location services. Have you always had it even on earlier builds that had better battery life? You have gone into privacy and turned all the apps to keep away and start at boot to off?
[ONE Android Development] KeyperOS:
Yes, I've always set it to on and "Battery Saving", basically it means it uses WiFi and Cellular to get a coarse location. GPS is off.

I've set all my own apps to not keep awake and not start at boot but I did not touch the ROM's defaults.

Right now I let the phone's battery die so that I can charge it to 100% while off, just in case it is a matter of wrong battery indicator.

Tomorrow I'll make a nandroid and start freezing things and shutting down keep awake and start at boot, maybe I'll get lucky but I am afraid I might have to turn location services completely off...
[ONE Android Development] r25txe:
I do not believe that the Android ID that Titanium manages is the same as the randomly generated device identifier that is created on a clean flash by Google.
[ONE Android Development] KeyperOS:
I do believe that it is though. Not 100% sure however so don't quote me on that :D
[ONE Android Development] Timmmmaaahh!:
Happy to see your surgery performance on your device worked out fine. Always nice to read a success story, thanks for reporting back.
[ONE Android Development] KeyperOS:
Yeah, turning location services completely off also completely stopped the drain, in 4 hours 49 minutes of inactivity, the phone remained in deep sleep for 4 hours and 45 minutes with just a mere 4 minutes 45 seconds total of screen off activity.

I'd like someone to insist that it was my setup that was at fault now...
[ONE Android Development] dharmil007:
My phone has trouble charging.

I dont know if its software issue or Hardware.

When I charge it through wall chargers, the phone does not charge neither does it drain the battery. It stays at the same level.

Tried many chargers those chargers work well with other phones.

I can only charge my phone via my PowerBank, through which it charges perfectly.

Any solutions, please ?
[ONE Android Development] Truble187:
Hey,

yesterday I installed the lastest release. Now I habe Provlems with the Facebook and Amazon Video app. I can´t start them.

Anybody an Idea?
[ONE Android Development] maxed4901:
See when you post a question without a proper log etc, no body will respond except for a hopeless like me.. here goes!'

Latest release means 20516? bcz m on 24.5.16 build (which is not there any more) due to changes and battery drain reported by some users. Do a clean install because this is not reported by others meaning high chance that its something with your device.

First go apps> facebook> wipe data and cache for app and do same for amazon. Now without opening either apps, reboot recovery and wipe cache and dalvik.. now try.
[ONE Android Development] magnamentis:
does not matter what one believes it's exactly that ID which is what counts, instead of posting believes better read up facts, this back and forth leads nowhere and in the future you don't have to quote images, you could use the hide function, but only if you believe it works and makes sense
[ONE Android Development] Truble187:
I tried you solution, but no change :(

The installation was clear (factory reset), but I have restored my apps with titanium backup.
[ONE Android Development] track909:
[MENTION=4817632]varund7726[/MENTION]

What do you think about this commit?

Is this a solution for battery drain?
[ONE Android Development] thecoolkid:
I flashed back to 20160513 to stop the drain. Also because it's the last build that the 50 mpx mod works (in CameraNextMod and also ColorOs Camera). Somehow CM broke it once again and nobody can find a fix yet (propably flashing the old library like the last fix). CM of course is not interested in fixing it, "couse it's not what the phone comes with" so I think I'm gonna stay with 20160513. I need my 50 Mpx camera for traveling on holidays. I find that it really does look better and you can zoom in more so it's always nice.

I hope [MENTION=4817632]varund7726[/MENTION] would revert those commits that broke it, but I guess he's not interested. Too bad, because this ROM was always about features :(

BTW why can't we record video in 4K DCI anymore, just regular UHD?
[ONE Android Development] iPusak Gaoq™:
Make sure you're using stable version of facebook not the beta version....i'm using stable v77.0.0.20.66 and i don't have any problem with it....
[ONE Android Development] r25txe:
Why is the Android ID stored in a database file that's not in GSF data folder?
[ONE Android Development] stranac79:
I can see that battery drain is not only my problem so will wait for solution like others, but do u have problems with overheating? I dont know what's happening but when I use my phone it become so hot in area around back camera.
[ONE Android Development] SGBE:
Has anyone been successful getting the new Android Pay to work with their OPO using this or the Stock ROM? I think my issue may be the root flag and/or some missing system keys.

Scott-
[ONE Android Development] magnamentis:
if you're not alone with a problem that does not mean it's a rom issue, this rom has no battery drain problem built in.

it can as well mean that you use the same app or a similar or the same setup or mod like others who have the same issue.

follow the following procedure to find out when the drain starts and narrow it down, it's on your side.

what is much more important than whether you're the only one or not with that issue is how many users have that issue and it are very few

no matter 5, 10, 15, it's a vast minority and the huge rest is quietly enjoying good to perfect battery life. currently my devices sips 2-3% in 8-10h overnight and is running 7-8 hours in use. (SOT)

if there were a rom based issue that would simply not be possible.

BTW i feel like repeating this message on a daily basis in on of the many threads i follow an for years, really curious when people stop blaming

anything and anyone else than themselves for any kind of bad battery life with an exception rate of less than 1%.
[ONE Android Development] KURDKiNG:
I heard if you install systemless root itl worl, or if you have supersu and xposed, do systemlesss supersu, and a unnofficial systemless xposed just got released if you wanna try
[ONE Android Development] SGBE:
Thanks. I will try it.

S-
[ONE Android Development] maxed4901:
Thats the problem.. Do not restore backups.. its happening with all custom roms.
[ONE Android Development] track909:
Yes, I have problems with overheating too....

Best build is 20160522
[ONE Android Development] mukesh22584:
Where is 20160522 build I can't find, Basketbuild shows latest is 20160520...

Only ANGLER........
[ONE Android Development] hellcat50:
He removed some oft the builds because of this issue.
[ONE Android Development] deoliveiranv:
Hi, What is the best kernel for this ROM right now???????????
[ONE Android Development] Timmmmaaahh!:
THE ONE IT COMES WITH!!!!!!!!!!!!!!!! Seriously, one question mark does suffice.

---------- Post added at 11:14 AM ---------- Previous post was at 10:48 AM ----------

Chances are very slim. http://www.xda-developers.com/android-pay-no-longer-working-with-systemless-root/

According to the article most Marshmallow ROMs are currently rooted systemless.. I'm sure there's a really smart person around here that can tell us which method is used for our beloved RR M ROM. Anyone?
[ONE Android Development] rolarocka:
Is basketbuild down?

Oneplus One
[ONE Android Development] magnamentis:
it's the slowest website of the century, horrible indeed and and offense to all users, have to download via PC to avoid errors, doze kicking in and a lot of heat while downloading "almost nothing per minute" so it's possible that you just have to give it time and as an additional annoyance we can't even tell whether it's down or just terribly slow, that's how slow it is. i have 300Mbps line here but the throttle is on their side.
[ONE Android Development] rolarocka:
Ok Ty mate!

Oneplus One
[ONE Android Development] Anubhav1996:
Maybe 5.7.0 is coming
[ONE Android Development] pinto83:
Use FDM, works well for me.
[ONE Android Development] KeyperOS:
I will ask you one last time to stop repeating false information.

This and every other CM-based build HAVE problems with battery drain that are caused by CM screwing up a commit concerning Device Location.

This is not in dispute.

Everyone knows this, varund7726 knows this and like I confirmed earlier, turning the location service OFF with no other change whatsoever results in exceptional battery life, much much better than any build before it which is why I remained with this build instead of reverting to the 20th.

So, turning off the location service is indeed a workaround for the battery issue and thusly, if you have it on OFF that would explain why you're not experiencing the issue.

I also read but have not yet confirmed that the issue also does not present itself when the location option is left at its' default setting which is "Device Only" i.e. GPS only which is why if someone doesn't change the location setting from the default then they won't experience this issue.

However not everyone can afford to keep location services off and GPS doesn't work indoors, hence why varund7726 himself pulled all the builds that include the aforementioned commit and only has up to the 20th build for download.

Now, for the last time, PLEASE stop spreading false information, otherwise the ones responsible for fixing what is broken (CyanogenMod) will not be as inclined to.
[ONE Android Development] suaverc118:
[MENTION=3715094]KeyperOS[/MENTION], is their a reason why you had location set to on all of the time? I think 90% of the time since I've had this phone its been set to off and I only turned it on when needed. I'm must curious and not attacking at all. I never understood why something needed to be on when its not needed. What is the benefit? So to me, battery life has always been good since I only used location for maps if I needed directions. What was battery life like on the previous good builds for you vs now? Thanks for your jnfo
[ONE Android Development] KeyperOS:
No worries friend :)

I keep GPS off but I do allow the phone to get a coarse location using WiFi and Cellular location (that's what the Battery Saving option stands for) for things like weather to work or for location-sensitive apps like those bank apps that also tell you the closest ATM.

Before now it didn't consume nearly any battery at all since the radios it used were on anyway, however CM screwed sth up with this one (according to R.C. kalpik it was due to CM switching to the Qualcomm location stack. Apparently they'd tried that once before too with the results also being the same i.e. huge battery drain).

With location service on, after checking better battery stats I saw that it's keeping the phone from going to deep sleep (sth to the effect of 2 hours on while sleeping in a period of 6 hours). Obviously it's also messing with Doze from kicking in.

With location service off however the phone gets a 99.9% deep sleep, only waking up occasionally to refresh content and run coalesced tasks.
[ONE Android Development] Timmmmaaahh!:
I personally use location history as memory support. I won't go into the boring details but basically I have a few spreadsheets that require me to keep track of certain locations I've visited. Thanks to this history, which needs location services to be on (duh), I don't need to frantically update these files constantly but can limit the work to once a week.

Google Now needs this as well if the user wants location aware updates (I've used this for digital tickets in the past).

Another application I sometimes use it for is in Google Keep, location based reminders. Just saying "OK Google, remind me to feed my gerbil when I get home" can literally be a lifesaver :P
[ONE Android Development] magnamentis:
FDM ?

Sorry for my ignorance, once in a while something new pops up and i will gladly take your advice if you tell me what FDM stands for :)

as usual for those who know it seem probably self-evident but i never had to use it or just missed the term (abbreviation)

thanks
[ONE Android Development] KeyperOS:
FDM: http://www.freedownloadmanager.org/
[ONE Android Development] Warsonex:
After today's update Facebook, the application to crash, what is the reason?

Rom version 5.6.9.
[ONE Android Development] iPusak Gaoq™:
i'm using updated facebook v79.0.0.18.71 and so far it doesn't crash....make sure you're using the stable version not the beta version....
[ONE Android Development] Warsonex:
Today I went to the stable version 5.6.4 is currently at the latest, because stable also the same crash ... I thought that wine firmware and so was updating to the latest.

Which version do you consider the most stable?
[ONE Android Development] iPusak Gaoq™:
Are you asking about RR rom or facebook apps? If you're asking about RR rom then v5.6.9 (build 20th) is currenty the most stable as i'm using it...if you're asking about facebook apps then the version i have mention before is the stable version...
[ONE Android Development] Warsonex:
I ask for a stable rom, I have exactly the same, so I do not know why me in this new and old crash Facebook
[ONE Android Development] iPusak Gaoq™:
There a lot of possibilities why facebook is crashing on you phone....

1. Themes = if you use other themes then probably it got to do with the themes not properly coded on facebook apps....

2. Kernel = there a slight changes custom kernel can cause apps crashing....

3. Kernel tweak = if your happen to tweak your kernel using kernel adiutor, try restoring it to default setup...best setup for me would be underclock it at 1958mHz (max) 300mHz (min) with Smartmax governor, zen I/O, 2048kb read-ahead....
[ONE Android Development] Warsonex:
omg seriously?? ... i doesn't repair this..
[ONE Android Development] sco-mito:
I think that those amplify configurations can solve partially the battery drain problem
[ONE Android Development] pijas82:
Powernap yes , amplified not

For me no drain
[ONE Android Development] magnamentis:
this rom is stable, facebook is a known trouble maker, the story goes back for years, possible reasons are manifold, best provide proper LOGs as it's mentioned in almost any OP on XDA ;)
[ONE Android Development] KeyperOS:
Although you are right, Amplify COULD solve the draining problem, you're listing the wrong things to limit.

I let my phone die twice from the drain and then analyzed the battery data, confirming what everyone has been saying.

The drain occurs because of a wakelock of the magnitude of HOURS from the LocationManagerService.

In my case the battery history says that the service acquired a total of 12465394(!) wakelocks for a total time of 3 hours and 43 minutes!!!.

Just from this one service!

I am now experimenting with limiting the wakelock via Amplify, starting with the default limit period of allowing the wakelock to occur once every 240 seconds (once every 4 minutes). If that proves to be inefficient I'll either try bumping the period up to once every 10 minutes or even try completely blocking it while the phone is off using Power Nap like [MENTION=5414534]nmmsp[/MENTION] suggested.

The only issue with Power Nap, other than doubling what Doze already does, is that it takes the sledgehammer approach to battery drain by limiting pretty much anything and everything completely until you unlock the screen which is more than a little heavy-handed as it doesn't allow for the coalesced wake-up period for apps and the system to do their stuff.
[ONE Android Development] sco-mito:
Can anyone post an amplify list of what is better to limit and what is not?

Personally i use amplify and greenify with the last version of this rom
[ONE Android Development] suaverc118:
Stay away from powernap for the same reason you listed. I use amplify and if you have any questions regarding what and how much to limit, [MENTION=5867207]v7[/MENTION] is awesome as heck and will help you.
[ONE Android Development] r25txe:
Are you running the 28th test build?
[ONE Android Development] kryshnakishore:
running 28th build with Boeffla-Kernel, everything is fine including sot too. but these are small issues i face in common

1.live display goes off randomly (in cos13 its not a issue neither in cm)

2.some time keyboard arrow keys doent show up

3.wish i had only up/down arrows while connected to net

4.cos13 camera & gello browser should not reset for everytime i update rom

5. set background limit process to 4 even after reboot
[ONE Android Development] pinto83:
How to change Status Bar Battery Animation, somebody please guide, thanks. Need this very much like Oxygen OS or COS on our RR Marshmallow..
[ONE Android Development] KeyperOS:
Yes, to limit this particular drain you don't really have to go all nuclear with PowerNap, all you have to do is limit this one following wakelock. I am currently testing how it goes with allowing it once every 10 minutes (600 sec) but you can try your own values:

Unfortunately Greenify cannot control this particular drain as it is part of android but I always use it to control rogue apps plus it also has the option for aggressive Doze that kicks off in minutes rather than hours!

Yes, all tests are made using the 28th build like I mentioned earlier :)
[ONE Android Development] maxed4901:
Basket build is always down!!!! Isnt there any other way we can host the updates'?
[ONE Android Development] goast:
What do you mean we? You on the rr team? It's what they can afford. Or what they prefer. Chances are they aren't going to change that because you're complaining.
[ONE Android Development] maxed4901:
OMG!! Did you get out of the bed wrong side? if you wish to rant at some one, choose some one close so that an unknown person wont curse you,. Stop acting like 5 year old. Did i ask to change? As a team, i meant to say if we can or willing to contribute to something perhaps. Not for you to act like you are RR,.

With Respect to what the RR team can afford, i think you are in no position to decide that. I think the only fit person to say what you said to me is Varun.
[ONE Android Development] goast:
Get off your sensitive pedestal.. No one was ranting. I never stated I was RR. As for how I'm "acting" I'm acting like a user who came to check a thread of a ROM I use and all I see is you whining about basketbuild being down. And using terms like "we". Pretty sure you are one of many people using various ROMs having the same issue, just like afh and all the other hosting sites. Just be grateful "they" build for our phone and flash when it available. No one wants to hear you complain. As for me if u have anything else to say pm me.