If you've received the OnePlus One XNPH30O OTA update, you might have noticed your battery life was severely reduced since installing it. You're not the only one - the CyanogenMod issue tracker for the One has a thread with well over 100 comments on the subject at this point.

CM seems to have nailed down the issue to problems with the power management and the proximity sensor. The former issue has been fixed and will be likely live in nightly builds starting today, and an OTA is being rushed through for those only using stable builds. The proximity sensor issue hasn't been resolved at this point, because CM is having a difficult time reproducing the issue reliably.

Screenshot_2014-08-12-16-19-40 Screenshot_2014-08-12-16-06-37 Screenshot_2014-08-12-16-33-09

Steve Kondik alleges the proximity problem is the result of a race condition that causes the phone's sensor to enter a "bad" state which then prevents the device from fully suspending (eg, ending wakelock). You can see all of Steve's comments on the thread here.

We are all over it and will do an expedited OTA after confirming in the lab.

Higher overall idle current was isolated to an i2c power management issue, this is resolved with the patches that just went in. We're idling at 3.5mA, which is LOWER than 25R, so yay for us :)

The proximity sensor issue is harder to reproduce but it's confirmed, we are working on this now.

Also, for you guys talking about the sensor being on all the time- the light sensor and proximity sensor are the same unit. If you have auto brightness enabled, you'll see this hardware block active when the screen is on. The issue we are looking at is a race condition with suspend which can keep the device from entering suspend because the sensor is in a bad state. You will see messages in logcat about unhandled messages (type 6) from the threshold indicator. We are looking for a reliable way to reproduce the issue.

Proximity sensor issue is fixed now as well. The issue could happen if the proximty sensor didn't warm up fast enough and the device reentered suspend. We'll push this thru an expedited OTA after running the full test suite. Thanks for the feedback.


David Ruddock
David's phone is whatever is currently sitting on his desk. He is an avid writer, and enjoys playing devil's advocate in editorials, and reviewing the latest phones and gadgets. He also doesn't usually write such boring sentences.

  • remister

    I am still running 25R. I haven't been requested to 30O yet, I guess for good reason.

    • Shyuan

      Agree, I'm still running 25R too and haven't got any system update notification, I believe the OTA update was held on since one or two major bugs were reported at their JIRA instance regarding 30O.

      • Jorge

        i just received mine this morning and was happy to see the update notification...since the update, i wish i would've been like you guys and not received it xD

      • Rami

        They did not the rollout, it is still going out slow, and even this morning, after the confirmation of the battery issue, the rollout percentage went from 50% to 75%, so they are still going ahead and when the patch is available it will be a small update for the 30O instead of a complete 100+ MB one. that's what I am guessing.

        • Shyuan

          As soon as I commented this, I got my updates like on the same day. Fortunately, I haven't got any battery drain issue. Maybe because I don't use the gestures and double tap to wake all this while. After updating to 30O, I do however turned off the double tap to sleep.

  • Mladen Kovacevic

    The funny thing is even with the reduction I still get a full day's charge.

    • tintin.92


    • http://www.androidpolice.com/ Artem Russakovskii

      I wish I could say the same (this is 2.5hrs screen on time).

      • https://twitter.com/#!/psychomaniac189 psychomaniac189

        is this on 11s? damn thats terrible. first day i got mine im on cm11 nightly and up up to 12 hours with 4.5 hours of screen on time

        • http://www.androidpolice.com/ Artem Russakovskii

          Yeah, 11S.

        • dmo580

          Right but everyone's use cases are different. Your 4.5 hours could be someone's 10 hours reading an eBook or someone's 2.5 hours if they're playing heavy 3D games and streaming music over LTE for example.

          So even if 30O has extra drain, you can't just compare two users' battery runtimes. You need to run a standardized benchmark.

      • dmo580

        The thing is your own screenshot shows that standby power is still excellent. Look at the flat line. Without running the 25R versus 30O versions side by side on the same benchmark, its hard to say which one is significantly worse.

        I might agree with you 30O is worse, but its not too noticeable to me and I would've thought it was within the realm of good battery still. Honestly, anything is better than a Nexus 4.

        And to give you an idea of my battery life, I ran with 2.5 hrs SOT and 1 hr of tethering at Google I/O and came out with 39% battery. So your results don't seem bad at first glance.

        I'm sure there are screenshots that could make 25R look bad too, but that's why we need to use apples to apples benchmarks when talking battery

    • DirkBelig

      I immediately (i.e. within 2 hours) realized that something about the update was guzzling power as I went from losing <1%/hr to 3-4%/hr on standby. Yikes! I deleted the battery stats file and rebooted as some suggested, but it was only after disabling double-tap to wake did it slow the bleeding. Very inconvenient as I actually use that a lot unlike any other gestures. (I'd disabled V after having the torch come on in my pocket and it being inconsistent in responding anyway.)

      Yesterday I put the phone back on the charger at 10% after 23h with 3-3/4h SOT. For reference, in the first days after getting the phone (before the battery had been broken in) I was getting 5h SOT in ~21h and I had one time where I went 40h with 3-1/4h SOT.

      While I AM getting a full day's use, I'm clearly losing SOT or standby time. Roughly 20-25% of the former, 40+% of the latter. My phone has clearly been reduced from nearly unbelievable battery life to merely OK and after 6 weeks of "I can't believe how long this battery lasts!" to have to worry about whether a boost charge will be needed blows.

      I'm not sure what's so complicated about running down this bug. Can't they just run a compare on the unbroken 25R code to the broken 30O?

  • tintin.92

    I'm guessing this is a result of using proximity sensor to prevent lockscreen gestures activating in the pocket.

    Does this mean the that disabling the lockscreen gestures will solve this, temporarily?

  • Anaron

    I haven't noticed a difference in standby time with the latest update. And neither has my friend. Neither of us use the gestures feature so that's likely why we haven't experienced it yet.

    With that said, I'm glad they're working on a fix. It has "blocker" status meaning it has the highest priority right now out of all the reported bugs.

  • http://www.androidpolice.com/ Artem Russakovskii

    I'm definitely looking forward to this fixer.

    • remister

      Ouch, what's your own screen time total?
      Nevermind, scrolled down and got my answer.
      PS You have a reminder.

      • http://www.androidpolice.com/ Artem Russakovskii


        • Srinivas Arnepalli

          Artem, are you using any lockscreen gestures?

          • http://www.androidpolice.com/ Artem Russakovskii

            I am, I have the O and V enabled.

          • jonathan3579

            I have both disabled and I'm still dropping battery percentage like a rock. :(

          • imtired

            I am too. Maybe is it the double tap to lock and unlock?

    • Matthew Budden

      Ouch. Why's the "sdcard" so high? Watching a movie or something?

    • jonathan3579

      Seriously. After the last update, my amazing battery life became shit.

      • dmo580

        Is it really that noticeable? I haven't seen that big of a change on my end. I measured idle drain is now at 1.3% / hour versus 0.9% / hour before on 25R. While that's a jump up, that's not the difference between good and shit.

        Note my tests were done over 8+ hours of overnight tests. While it would've been ideal if I could've tested for 24+ hours, I don't have that luxury.

        I know its easy for everyone to jump in now and say they noticed bad battery, but I can guarantee you 95% of users are guilty of placebo effects. There could be easily a battery improvement and someone could claim an opposite effect and a good number of users would agree with their own anecdotal evidence.

        Its important to run apples to apples tests and not to just base things off of uncontrolled observations.

        • jonathan3579

          I can say this because I left my phone at home untouched while I was at work. I had pulled it off the charger before leaving and it was at 100%. 10 hours later, it was at 70% with 5 minutes of screen-on time.

    • imtired

      Used my phone with 30 minutes of screen on time and left it alone for twenty minutes. Android OS is literally at 30%, the same as my screen usage. I think I might factory reset until this update...

  • Rorix

    got the OTA yesterday and since i never had the gestures enabled i still have rock solid performance. could be placebo at this point tho.

  • Fatal1ty_93_RUS

    Cyanogen quality, no wonder Koush left the company

    • Will Tisdale

      Yeah. It's funny really - as you know I got slated by all the CM apologists for my comments about CM being buggy junk the other day, but this kind of thing proves the point.

      It wasn't just one serious issue that they managed to introduce in the latest OTA, it was 2 - an i2c PM issue and this proximity sensor issue...

      You really have to question the competence of the people working on it...

    • mark01

      bunch of noobs, good to please beginners in android modding, way different from serious stuff.

  • rslh

    In reality, it's not as bad as it sounds; it's just not as good as it was. I'm patiently waiting.

  • Ajb.esquire

    Nothing worse than a "race condition" ruining your battery life. We are all people regardless of colour, we are all entitled to the same battery life!

  • Guest

    I updated to the latest version couple of days ago and my battery is probably worse by like 5% . My screen on time improved but idle time was bad.

    • Srinivas Arnepalli

      what's your screen on time before and after the improvement that you see?

  • rasik

    I updated to the latest version couple of days ago and my battery is probably worse by like 5% . My screen on time improved but idle time was kinda bad

  • parkerjh

    Do you need to root to get the nightlies?

    • http://www.androidpolice.com/ Artem Russakovskii

      You never need root to change OSes with bootloader unlockable devices.

      • parkerjh

        Thanks, appreciate the reply. So though it is "unlockable", do I need to unlock it? Or can I just put the ZIP file on the phone and flash it without doing anything else?

        • http://www.androidpolice.com/ Artem Russakovskii

          I believe you have to unlock to flash nightlies. Stock firmware and updates to it can be flashed without unlocking.

          • parkerjh

            Ok: how does one unlock vs root? I'm so confused- I figured this device would already be rooted and unlocked. Guides I have read and tried to follow do not work for me. Frustrating. I feel like I'm using a pre-pre-pre Alpha experiment. Too many bugs. Terrible battery. Not ready for release.

          • Christoffer Hulthén

            This guide should help you: forum.xda-developers.com/showthread.php?t=2788632

          • parkerjh

            Thanks- I did find that one but don't have a PC handy: tried to do it with my Mac running Parellels but it didn't work. I'll have to borrow a PC from someone, thanks again for the link.

  • rickneworleansla

    I've seen many users reporting somewhere around a 1% per hour battery drain overnight in suspend. I haven't monitored it myself yet since I just updated yesterday. Before updating I could leave the phone in suspend all night and wake up with only 1% less battery. I will monitor it tonight to see what I get now on the new OTA.

    It does seem to be draining faster today than it normally does. Even with this problem it probably still gets better battery life than most phones.

  • Alf Zamudio

    Calkulins stock ROM based on 30O. 85% left with 1hr 40min OST. runs fluid as well.

  • dude

    Not me, my battery is pretty good, I tend to do a factory reset after the update.

    • http://www.droid-life.com/ Steve B

      Trust me, the battery is dreadful after the 30O update. I did a full wipe and reflashed the factory images.

      I've had the phone for 5 weeks now. Weeks 1-4 the battery was amazing, since 30O I've seen a significant drop off. Same usage, I normally put the phone back on the charger at night with +40% remaining, since the update >15% every night.

      • grumpyfuzz

        You could flash franco kernel for the time being as his latest kernel update fixes this issue.

      • Daniel Pasut

        luckily I haven't notices this issue. Since I got the phone two weeks ago I've been getting roughly 30 hours of charge with 4-5 hours SOT. That's not as great as I know the phone is capable of, but it's still fairly decent in my opinion. Compared to Artem's screenshots of battery issues my phone seems to be completely unaffected.

  • Grayson

    From a former OnePlus One owner, this is exactly why I got rid of it. Bugs galore. All phones have bugs, sure, but the OnePlus One had more bugs than any phone I've used in recent years. It was just ridiculous. No different than running CM night lies on any other phone in terms of stability.

    • DirkBelig

      As a current 1+ owner, I'm curious as to what you were doing that exposed all these supposed "bugs." Until this update caused the battery drain issues, I've been quite satisfied in the 6 weeks I've had mine.

      I think bashing 1+ is the new phony nerd pose like squealing that "Origin is malware" for the herds who thought bashing EA made them look kewl.

      • Grayson

        Not just getting in on the 1+ bashing action bud. I actually bought the phone and wanted to like it, and I did like many things about it, but I found the software to be very buggy. Here's a post I made on xda detailing all of the bugs I experienced since you're curious: http://forum.xda-developers.com/showpost.php?p=54415774&postcount=6

    • http://www.droid-life.com/ Steve B

      You have no f*cking clue what you're talking about. You just came here to flame because you were butthurt that you didn't get an invite.

      Yes, there were bugs, but nothing more than you get from Samsung or Htc. At least with CM, you know you'll get an update fast, instead of waiting for 3 months.

      • Grayson

        What are you talking about numbnuts? Do you know how to read? I got an invite, bought the phone, used it for a few weeks, and then got rid of it because I didn't like it. I'm not butthurt about anything. Sounds like you are though haha. By the way, interesting that the unlocked HTC One and Moto X both got 4.4.4 before the OnePlus One. Oops, so much for fast updates.

        • http://www.droid-life.com/ Steve B

          I read just fine f*cknuts. I'm calling you a liar boy.

          • Grayson

            Lol, why would I lie about that? So I just went through the OnePlus forums for weeks posting about kernels, ROMs, experiences, etc. just for pretend? Look for posts on XDA by gtg465x. I can post my OnePlus receipt if you're really that stiff.

          • http://www.droid-life.com/ Steve B

            Cool story bro.

  • _artem_

    Franco kernel already includes cm patch that fixes battery drain

  • jeffhesser

    Don't get me wrong, I love news about the OnePlus but this feels like a newsified changelog lately.

  • [A]dri[A]n

    Battery life definitely isn't as good, but it's still better than most phones Haha At least we'll be getting the fix pretty soon :)

  • http://www.volkswagen.de/ Quailallstar

    I was very disappointed when I realized the increased brightness on the capacative buttons was not fixed - even when the change-log indicated it would be.

  • Ryan Lounsbury

    My battery life has certainly been reduced since the OTA but I still get a full days worth of battery. I did get 1.5 days worth or so prior to the update.

  • grlzzz

    I took the 30O OTA and got bad battery life as a result. Silly me, I also lost root. So I decided to give PA a whirl till the next OTA comes out. Cyanogen has did an awesome job with CM11s for the 1+1. I'm not even a fan of Cyanogen but it has proven to be a real stable rom. I'm not going to knock them for a small issue that will be fixed soon. Even with the increased battery usage its kicking the ass of the battery life of the majority of Android phones on the market.