Anyone excited for OnePlus?

[KeithTalent]

Fortunately Cyanogen is awaiting final validation and should have the OTA out this week.

http://ausdroid.net/2015/04/06/cyan...-cm12s-to-oneplus-one-in-the-next-day-or-two/

Oh cool, so I will be able to just get that one like any previous update. I'm down with that. :thumbsup:

KT

 

[dlock13]

I flashed to OxygenOS, and I can definitely say it is an exceptionally stable ROM. There are a handful of issues that I've experienced, but for the most part, I only have 2-3 bugs. I've seen a list that other users are experiencing, but I've never had those.

It is fast, fluid, and definitely worth a try...... if you're looking for that stock Android feel. Coming from mostly Nexus devices, it ruins it for me when a company changes out so many features I like that Google created. I'm glad to be on essentially stock Android with only a handful of extensions and not huge modifications. I can't wait to see what they introduce in the next update.

 

[ThisIsChrisKim]

I flashed to OxygenOS, and I can definitely say it is an exceptionally stable ROM. There are a handful of issues that I've experienced, but for the most part, I only have 2-3 bugs. I've seen a list that other users are experiencing, but I've never had those.

It is fast, fluid, and definitely worth a try...... if you're looking for that stock Android feel. Coming from mostly Nexus devices, it ruins it for me when a company changes out so many features I like that Google created. I'm glad to be on essentially stock Android with only a handful of extensions and not huge modifications. I can't wait to see what they introduce in the next update.

Ever used the CM12 nightlies? I've been running the CM12 nightlies for the past three months or so and it's pretty stable overall, too. I'm interested to try out Oxygen if it's as stable.

 

[dlock13]

Ever used the CM12 nightlies? I've been running the CM12 nightlies for the past three months or so and it's pretty stable overall, too. I'm interested to try out Oxygen if it's as stable.

I have not tried it out. To be honest, I just got this phone about 2 weeks ago and have been using it on KK. I was debating on bumping it to the nightlies, but I knew CM12S was going to come out soon so I waited. I was also waiting on OxygenOS, and since it came out first, I jumped at the chance to be back on L. Other than a handful of bugs, it definitely is a great ROM.

 

[JimmiG]

I flashed to OxygenOS, and I can definitely say it is an exceptionally stable ROM. There are a handful of issues that I've experienced, but for the most part, I only have 2-3 bugs. I've seen a list that other users are experiencing, but I've never had those.

It is fast, fluid, and definitely worth a try...... if you're looking for that stock Android feel. Coming from mostly Nexus devices, it ruins it for me when a company changes out so many features I like that Google created. I'm glad to be on essentially stock Android with only a handful of extensions and not huge modifications. I can't wait to see what they introduce in the next update.

Many are reporting much poorer battery life, lower screen-on times and excessive wakelocks. Battery life is the most important thing for me, so that's a big deal. If anything, I would have expected better battery life with a more "bare-bones" OS.

I'll probably wait until CM12s is released, and then see what people are saying and decide which route to go. I might even wait for 5.1 before upgrading from CM11s. 5.0 seems to have a lot of problems, not just on the OPO but in general.

 

[dlock13]

Many are reporting much poorer battery life, lower screen-on times and excessive wakelocks. Battery life is the most important thing for me, so that's a big deal. If anything, I would have expected better battery life with a more "bare-bones" OS.

I'll probably wait until CM12s is released, and then see what people are saying and decide which route to go. I might even wait for 5.1 before upgrading from CM11s. 5.0 seems to have a lot of problems, not just on the OPO but in general.

It isn't an issue with the ROM per se. It actually is an issue with the Google Play Services. If you check out their forums or the Reddit for OP, there are many people posting fixes for it. I enabled one setting, and it definitely fixed my issue.

I'll be able to test the battery life more thoroughly today, and I'll post back letting you know what I get.

 

[IGemini]

Yeah, the battery drain is not an issue related to OS build. Google Play Service 7.x has wide reports of accelerated battery drain among AOSP and CM-type builds in the past month when it was released, and I've noticed the hit about as long. My phone had 400k+ wake up and keep awake requests combined in the past 18 hours when I checked, and I'm just using stock CM11S.

 

[JimmiG]

Yeah, the battery drain is not an issue related to OS build. Google Play Service 7.x has wide reports of accelerated battery drain among AOSP and CM-type builds in the past month when it was released, and I've noticed the hit about as long. My phone had 400k+ wake up and keep awake requests combined in the past 18 hours when I checked, and I'm just using stock CM11S.

Well if it only happens with AOSP/CM ROMs and not with Samsung, Motorola, HTC etc. stock ROMs, it sounds like it's an OS-related issue that developers of those custom ROMs will have to fix.

 

[ThisIsChrisKim]

Well if it only happens with AOSP/CM ROMs and not with Samsung, Motorola, HTC etc. stock ROMs, it sounds like it's an OS-related issue that developers of those custom ROMs will have to fix.

It's related to UpdateSystemActivity wakelock in GMS. In Most non-Google ROMs, this service is disabled by default. This causes Play Services to keep a wakelock. So enabling this service solves the wakelock issue.

Being on CM12 nightlies, I've noticed the battery life is decidedly worse than KK, but it's not bad enough to stay on KK. Probably 10-15% worse is my guess.

 

[Megatomic]

Well if it only happens with AOSP/CM ROMs and not with Samsung, Motorola, HTC etc. stock ROMs, it sounds like it's an OS-related issue that developers of those custom ROMs will have to fix.

My OG Moto X has the Google Play Services 7 issues, lots of us reported it on the Moto forums. It's not just the ROM/Nexus world suffering here.

On a separate note, I bought another BNIB OPO yesterday, should be in my hands early next week. I'm hopeful that CM12S will be released soon thereafter, if not I'll flash OxygenOS next weekend.

 

[poofyhairguy]

Yeah Lollipop is easily the buggiest Android since Honeycomb, welcome to the party.

 

[IGemini]

Trolls gonna troll.

Moving on, OnePlus' CEO confirmed today that CM12S passed verification and should be pushed in the next few days.

http://9to5google.com/2015/04/10/oneplus-cm12s-release/

 

[poofyhairguy]

Trolls gonna troll.

Who is trolling? Not me, Lollipop is filled with bugs:

http://fieldguide.gizmodo.com/the-worst-bugs-in-android-5-0-lollipop-and-how-to-fix-t-1663090445

JimmiG is right that some OEMs are fixing these bugs in their ROMs, but anything AOSP is going to have some issues. There is a reason 5.1 came out so quickly after 5.0. I am just saying don't blame the device or the ROM, it could be the entire OS that is causing an issue. I hope yall get a 5.1 ROM quickly.

 

[JimmiG]

Who is trolling? Not me, Lollipop is filled with bugs:

http://fieldguide.gizmodo.com/the-worst-bugs-in-android-5-0-lollipop-and-how-to-fix-t-1663090445

JimmiG is right that some OEMs are fixing these bugs in their ROMs, but anything AOSP is going to have some issues. There is a reason 5.1 came out so quickly after 5.0. I am just saying don't blame the device or the ROM, it could be the entire OS that is causing an issue. I hope yall get a 5.1 ROM quickly.

Yeah, it's the responsibility of the OEM to make sure the hardware and software they ship to customers work properly. It doesn't matter if the issue is caused by Google. Unless it's a Nexus, I'm not a customer of Google - I'm a customer of Samsung, LG, OnePlus etc.

I'm happy with my OPO, but before using the privacy guard to kill off Google Play Services, it was using 70% of the battery. On my LG G2 it was using ~3% and on my Asus Memo Pad, it's using 2%. Those are all running 4.4 KitKat. Now the phone works mostly as it should, but the workaround can cause problems (indeed I get the occasional message that Google Location Services has stopped).

About the bugs - Wow - I do hope 5.1 comes out quickly.

 

[IGemini]

When the issue pops up even on Nexus devices with a core Google program, it seems irresponsible to shift the burden on fixing the problem to other OEMs. Just how I see it.

KitKat had a fair share of known issues too, but most of them I never experienced. Hopefully the update will still be as stable as the nightly builds have seemed. I don't want to be pining for CM12.1 before OTA has already happened.

 

[dlock13]

Well, after using it for the past couple of days, something sucks about the battery. I can go from 4:30 AM to 5 PM with probably 65-75%battery left. Problem is that is with around an hour SoT.

I just checked my battery stats today and lo and behold, Google Play Services have been awake for nearly 7 hours. Granted I did end the day with 50%battery life, but looking at the stats, I should have had more.

 

[Artdeco]

4 invites, they expire soon

https://account.oneplus.net/invite/claim/GLEN-SXXS-QP06-WGUR
https://account.oneplus.net/invite/claim/GLTM-XRJY-XRNJ-QQJU
https://account.oneplus.net/invite/claim/GLNM-7HNI-ZVPQ-RTYF
https://account.oneplus.net/invite/claim/GLDA-PQAO-DNTS-MJ0M

 

[Megatomic]

Well, after using it for the past couple of days, something sucks about the battery. I can go from 4:30 AM to 5 PM with probably 65-75%battery left. Problem is that is with around an hour SoT.

I just checked my battery stats today and lo and behold, Google Play Services have been awake for nearly 7 hours. Granted I did end the day with 50%battery life, but looking at the stats, I should have had more.

The Google Play Services bug is a huge topic of discussion over at the OPO forums these days. v7 of the services brought woe to many.

 

[IGemini]

It's official. Cyanogen announced that the rollout of CM12S starts today.

https://cyngn.com/blog/cyanogen-os-12-is-the-sweetest

 

[KeithTalent]

It's official. Cyanogen announced that the rollout of CM12S starts today.

https://cyngn.com/blog/cyanogen-os-12-is-the-sweetest

Hell yeah! Hopefully it's waiting for me when I get home. :awe:

KT

 

[blackdogdeek]

What are the fixes for the Google Play Services issue?

 

[ThisIsChrisKim]

What are the fixes for the Google Play Services issue?

Re-enable a systemupdateservice.

 

[IGemini]

So, I got sick of waiting and decided to sideload this sucker. Used the instructions here:

http://webtrickz.com/guide-to-update-oneplus-one-to-cm12-lollipop-os/

No root required. Was up and running with CM12S in about 15 minutes, most of that spent with Android rebuilding the apps.

 

[Megatomic]

I just downloaded an OTA image and flashed in the recovery provided with the phone. Nothing special, no muss - no fuss. It took a while to get used to Lollipop but it's growing on me.

 

[isekii]

is it stable? any noticeable bugs in CM12?