By 
It’s a bit frustrating to get bits and pieces here and there about an exciting new phone, but that’s what we’ve been forced to deal with when it comes to the OnePlus One. Last we heard, the device would be coming with the trusty old Qualcomm Snapdragon 800 processor clocked at 2.3GHz. It’s a quad-core SoC that delivers great performance and very respectable battery life.
And now we have first details about the battery. OnePlus has announced that the OnePlus One’s battery will have 3,100mAh in terms of capacity. We don’t know which technology they’re using, but we imagine it doesn’t make much of a difference to the end-user either way. We do know that the battery is not removable, though, which could make the OnePlus One a deal breaker for some.
For what it’s worth, OnePlus says their decision to make the battery non-removable was tough, but not without its reasons. They say a removable battery would have meant needing to design the OnePlus One with a protective layer for the motherboard, which would force them to limit the battery size to around 2,500mAh. They feel the trade-off to get to 3,100mAh will be worth it, though, as they’ll be working with the CyanogenMod team to optimize the device as much as they can.
The company’s front-runner Pete Lau ended the post teasing some sort of “mystery tech” that will “enhance and boost the user experience,” though they predictably left it with a cliffhanger ending and told us to stay tuned. Stay tuned, we shall.
[via OnePlus]
My hope is that this “mystery tech” will be one of the new super charging solutions that have cropped up over the past few years. Imagine being able to charger your phone in mere minutes, when it use to take a couple hours for a full charge.
Graphene supercapacitor batteries aren’t ready for mass production. When they are, that’s when I’ll be OK with a non-removable battery, since it won’t degrade like lithium-ion, and it can charge in seconds.
Do we have any idea when this ships?
I will need a new phone very soon and CM support out of the box is pretty appealing.
My hope is just that this OnePlus One’s wifi has a decent range and its GPS actually works. I’ve got the current One X and it’s a great phone except for the foregoing (said with just a hint of irony). I’ve been underwhelmed by the info about the S5 and am in a bit of a quandary as to what to get next.
This device might be my new phone since I’ve given some thought to getting a new device after seeing exciting new devices from MWC etc. Have had my S3 for about 18 months now.
“working with the CyanogenMod team to optimize the device as much as they can” sounds awesome and something I’ve always wondered why phone manufacturers don’t already do. It’s clear the custom ROM community are able to optimise battery performance so much more than manufacturers so why wouldn’t manufacturers tap into that source. Optimising the stock ROM for battery performance is a huge win as it affects every single user who buys the phone, were as a custom ROM optimised battery only affects a very small percentage of users of that phone. Not to mention, that optimising battery life seems so much easier and better to do than squeezing in a larger battery to accommodate poor battery efficiency in the software.
CM sucks (no pun intended) in battery life, it always drains about one third more than stock ROMs on every device. What’s more, that stock ROMs and kernels have always some back-door features to improve battery life, however it always breaks something, so I hope this won’t be the case…
That depends entirely on the device.
I was thinking -about one third- dependend on device (had CM on like 5-10 devices), I’m not claiming it as a general number for every device, however the fact is that CM on every device is always worse than stock (with stock CM kernel, on other custom kernel applies what I said below).
The battery life on Nook Color (Encore) is improved over the Stock Rom.
“always drains about 33% more than stock ROMs on every device”
Completely made-up nonsense. Where did you get that figure for “every device”?
I was thinking -about one third- dependend on device (had CM on like 5-10 devices), I’m not claiming it as a general number for every device, however the fact is that CM on every device is always worse than stock (with stock CM kernel, on other custom kernel applies what I said above).
You Aint lying. You sacrifice stability and some battery for the features and power
this is a moot point regardless since this is a groundup build from CM and not a ROM port.