Was it 44s?
Yes it was 44S.
Transmitted via Bacon
timmaaa said:
Yes it was 44S.
Transmitted via Bacon
Click to expand...
Click to collapse
Almost feels like they abandoned updates?
SysAdmNj said:
Almost feels like they abandoned updates?
Click to expand...
Click to collapse
At the time, yes.
But soon a CM12S update is coming
Stay tuned for that!
Why? They haven't. You need to understand that the next update is a whole new Android version, and it's vastly different from the last. There's been a lot of work to do. Do you read this forum? It's been discussed pretty extensively the last couple of months.
Transmitted via Bacon
I believe they said 3 months after Google releases lollipop they will have cm12s ready. It's pretty close to that time frame. Meanwhile there's plenty of development on custom ROM's based on lollipop and cm12 already in the various sections here... There definitely isn't any abandonment here
Sent From Lollipopified Bacon Goodness!
ek69 said:
I believe they said 3 months after Google releases lollipop they will have cm12s ready. It's pretty close to that time frame. Meanwhile there's plenty of development on custom ROM's based on lollipop and cm12 already in the various sections here... There definitely isn't any abandonment here
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
Technically the timeframe has expired now (5.0 was released on the 2nd of November I think). Doesn't really matter though, the update is in testing so it shouldn't be too far away.
Transmitted via Bacon
timmaaa said:
Technically the timeframe has expired now (5.0 was released on the 2nd of November I think). Doesn't really matter though, the update is in testing so it shouldn't be too far away.
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah it's off by a bit that's true lol. I got my phone pretty much at the end of the cm11s phase (I think there were two updates after I got my phone, 38 then 44). I'm not sure how custom ROM's compared to stock cm11s in terms of features, customizations, etc, so I'm left wondering if there will be many differences between the official cm12s ROM and custom ones. I'm hoping there will be, otherwise it doesn't really matter which ROM you run apart from looks or something I guess lol
Sent From Lollipopified Bacon Goodness!
Related
Hi all,
I'm new the the OPO having just left the Nexus line after a long time.
I'd love to use the capacitive buttons but really hate how they're opposite to the Android guidelines. Is it possible to remap them so they're the same as the Android on screen ones?
TIA.
Sent from my A0001 using Tapatalk
I know its possible with a custom ROM
itsdacj said:
I know its possible with a custom ROM
Click to expand...
Click to collapse
So it's not possible on stock CM11S?
Sent from my A0001 using Tapatalk
Looks like there is a way!
http://www.reddit.com/r/oneplus/comments/2at44f/how_to_switch_the_settings_and_back_hardware/
Sent from my A0001 using Tapatalk
Ah but it requires root :/
Root, and unlock bootloader and Install the latest Oct. 21st verion of SLIMKat and be over it.
You have so much customizations under a super clean and LIGHT ROM. In fact, most of what Android Lolipop is coming out with has ALREADY been out on custom roms ages ago.
Think of it as Google finally taking ideas from the development community.
spr33 said:
Looks like there is a way!
http://www.reddit.com/r/oneplus/comments/2at44f/how_to_switch_the_settings_and_back_hardware/
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I confirm that this method works.
Also a Nexus user.
itsdacj said:
Ah but it requires root :/
Click to expand...
Click to collapse
Yeah, of course it does, that's to be expected with such a modification.
Transmitted via Bacon
timmaaa said:
Yeah, of course it does, that's to be expected with such a modification.
Transmitted via Bacon
Click to expand...
Click to collapse
I knew that but it's a shame CM doesn't allow it
Sent from my iPad using Tapatalk
I fail to see the problem with root since in your sig it says you are testing ROMS and kernels ...
itsdacj said:
I knew that but it's a shame CM doesn't allow it
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Bro, theres hardly any adblocker(ad free is what I use) that doesnt need root. Are you telling me you're letting all kinds of tracking scripts/cookies, youtube ads, animated epilepsy inducing garbage steal your time/cpu/battery/data bandwidth?
GET on that root train right now. This goes for everyone.
Cholerabob said:
I fail to see the problem with root since in your sig it says you are testing ROMS and kernels ...
Click to expand...
Click to collapse
I need to update that. Went back to stock because of battery life. Its difficult to keep it updated when you don't own a PC.
itsdacj said:
I need to update that. Went back to stock because of battery life. Its difficult to keep it updated when you don't own a PC.
Click to expand...
Click to collapse
My phone has a web browser installed, I just use that.
Transmitted via Bacon
So I got my 1+1 a few days ago and am okay with CM11s.I see blisspop is popular and people are getting good battery with it. But are there Abby downsides of upgrading to L? Should I wait for stable CM12s
Sent from my A0001 using XDA app
SilentRazor said:
So I got my 1+1 a few days ago and am okay with CM11s.I see blisspop is popular and people are getting good battery with it. But are there Abby downsides of upgrading to L? Should I wait for stable CM12s
Sent from my A0001 using XDA app
Click to expand...
Click to collapse
It's daily driver material. Just don't flash the most recent nightlies. They have some firmware update issues.
I have been using using Temaseks rom and its as smooth as possible, well worth upgrading to.
rudi_j7 said:
It's daily driver material. Just don't flash the most recent nightlies. They have some firmware update issues.
Click to expand...
Click to collapse
Not true, I have most recent CM12 nightly and it's ok.
giaur said:
Not true, I have most recent CM12 nightly and it's ok.
Click to expand...
Click to collapse
Maybe not true for you, bit still true for others.
Transmitted via Bacon
timmaaa said:
Maybe not true for you, bit still true for others.
Transmitted via Bacon
Click to expand...
Click to collapse
Nobody confirmed this problem on Oneplus. There are some problems on Find7/Unofficial CM12 builds (there is no official CM12 for Find7). It's safe to user latest CM12 nightly on bacon, dont be afraid
giaur said:
Nobody confirmed this problem on Oneplus. There are some problems on Find7/Unofficial CM12 builds (there is no official CM12 for Find7). It's safe to user latest CM12 nightly on bacon, dont be afraid
Click to expand...
Click to collapse
I'm not afraid. I'm simply saying that just because you are not experiencing a particular bug personally it does not mean the bug doesn't exist for the greater community.
Transmitted via Bacon
timmaaa said:
I'm not afraid. I'm simply saying that just because you are not experiencing a particular bug personally it does not mean the bug doesn't exist for the greater community.
Transmitted via Bacon
Click to expand...
Click to collapse
Not only me, many people flashed today CM12 build and nobody has any problems. I have no idea why do you think there is any bug on latest CM12 nightlies?
giaur said:
Nobody confirmed this problem on Oneplus. There are some problems on Find7/Unofficial CM12 builds (there is no official CM12 for Find7). It's safe to user latest CM12 nightly on bacon, dont be afraid
Click to expand...
Click to collapse
timmaaa said:
I'm not afraid. I'm simply saying that just because you are not experiencing a particular bug personally it does not mean the bug doesn't exist for the greater community.
Transmitted via Bacon
Click to expand...
Click to collapse
Well, usually a minor glitch or bug wouldn't be a big deal, but here, the consequence could be a hard brick as reported on the Find 7. There's no coming back from there, and official or unofficial doesn't matter because both are from the same sources.
rudi_j7 said:
Well, usually a minor glitch or bug wouldn't be a big deal, but here, the consequence could be a hard brick as reported on the Find 7. There's no coming back from there, and official or unofficial doesn't matter because both are from the same sources.
Click to expand...
Click to collapse
Find7 != Oneplus, latest nightly is tested by many people and it's ok on bacon. Besides - sources are the same but there can be something messed while compilation process that prevents rom to boot. Do you mean hard brick, so phone is completly bricked and can't even boot into recovery mode?
giaur said:
Find7 != Oneplus, latest nightly is tested by many people and it's ok on bacon. Besides - sources are the same but there can be something messed while compilation process that prevents rom to boot. Do you mean hard brick, so phone is completly bricked and can't even boot into recovery mode?
Click to expand...
Click to collapse
Yep. Hard brick as in an expensive paperweight. CM has merged a commit to stop CM nightlies for Find7 and Bacon temporarily because of this issue. They merged some firmware update which has botched everything up.
rudi_j7 said:
Yep. Hard brick as in an expensive paperweight. CM has merged a commit to stop CM nightlies for Find7 and Bacon temporarily
Click to expand...
Click to collapse
Which commit is it? CM nightlies are still available for bacon, I have installed today nightly. And I can't see any CM12 nightlies for Find7, there are only CM11
giaur said:
Which commit is it? CM nightlies are still available for bacon, I have installed today nightly. And I can't see any CM12 nightlies for Find7, there are only CM11
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/85323/
Sent from my A0001 using XDA Premium 4 mobile app
rudi_j7 said:
http://review.cyanogenmod.org/#/c/85323/
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's merged today morning, 14.01 nightly was compiled yesterday and it's still available: http://jenkins.cyanogenmod.com/job/android/98199/console download is here: http://download.cyanogenmod.org/get/jenkins/98199/cm-12-20150114-NIGHTLY-bacon.zip
It seems there will not be new nightly tommorow, the one already built is ok.
@timmaaa what do you use?
Sent from my A0001 using XDA Free mobile app
And I guess no CM12 nightlies, which Blisspop version should I hop on to?
Hi everyone.
I'm using CM11 44s and I just got OTA update.
The only modes I'm using are the CameraNext v11 and 3 way speaker mono mod, I believe from the same nice dev who mods the camera app.
If I'll flash the OTA update, I'll lose my root and my mods
Is there a way to flash the new CM version and not loosing root?
I'll then reflash the camera mod and speaker mod.
On a side note, why does it take so long to release lollipop to OnePlus devices?
Thanks.
It didn't take long to get Lollipop on this device at all, there are literally dozens of Lollipop ROMs available, and they've been available for quite some time.
You can keep your mods if you use the modified OTA file, you'll find that in the OTA thread in the general section. You can help losing root, bit that really shouldn't matter because it takes less than a minute to flash SuperSU and get it again.
Transmitted via Bacon
But lollipop is not officially released for the opo. I installed it and got many issues like the phone dials on its own or people can't hear me.
CM12S hasn't been released yet, but that doesn't mean anything, CM12 (along with dozens of others) has been around for ages. You just need top find the right ROM, I'm running LP and it's perfectly stable for me.
Transmitted via Bacon
What ROM do you use?
It's in my signature, Vanir-Exodus.
Transmitted via Bacon
Evita?
timmaaa said:
It's in my signature, Vanir-Exodus.
Transmitted via Bacon
Click to expand...
Click to collapse
kenhicg said:
Evita?
Click to expand...
Click to collapse
What about it?
Transmitted via Bacon
So the cm12s update has been released and as long as know it is supposed to come over the air to cm11s devices but im not sure im running cm11s.
iy doesnt say Cyanogen on the back of the device. i have not rooted flashed or done anything like that
it says the cyanogen version is 11.0-XNPH05Q
im pretty confused and need a answer quick..
sorry for bad english.
You are running CM11S and will get Cyanogen OS 12.
New OPOs don't come with the Cyanogen branding on the back.
THANKS
Amro90 said:
You are running CM11S and will get Cyanogen OS 12.
New OPOs don't come with the Cyanogen branding on the back.
Click to expand...
Click to collapse
Thanks for quick answer and the question now is when i will get it. have you got it? if so when?
AntonAtom said:
Thanks for quick answer and the question now is when i will get it. have you got it? if so when?
Click to expand...
Click to collapse
Can't really tell when you will get it. Probably in the next few days. I didn't get the OTA so I just flashed it with the fastboot images.
Amro90 said:
Can't really tell when you will get it. Probably in the next few days. I didn't get the OTA so I just flashed it with the fastboot images.
Click to expand...
Click to collapse
Right... As per Carl, the updates are pushed in batches not limiting to any geographical areas.
Within next few days almost everyone should have it.
Hello there, I'm a developer from the deprecated mt6589 chip. And now I'm switching to Bacon 16GB. I would like to know if the development of Bacon will continue to N or not (officially by Cyanogen?
Thanks.
It is officially discontinued, but I can bet my word that it would easily last till
Android P
Transmitted via BACON
MZO said:
It is officially discontinued, but I can bet my word that it would easily last till
Android P
Transmitted via BACON
Click to expand...
Click to collapse
Hope so!
I've had some devices like S2 and E975, their official support ended years ago, they're still on MM
Transmitted via BACON
MZO said:
It is officially discontinued, but I can bet my word that it would easily last till
Android P
Transmitted via BACON
Click to expand...
Click to collapse
Can you please give some source about this?
Steve K. said if Qualkom continues to support some think that 'N' needs than they will continue to support it, and if this huge amount of people continues to use Bacon.
https://forums.oneplus.net/threads/...-for-oneplus-one.440897/page-21#post-14718596
Sent from my A0001 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=3366733
Transmitted via BACON
MZO said:
http://forum.xda-developers.com/showthread.php?t=3366733
Transmitted via BACON
Click to expand...
Click to collapse
that really doesn't say a lot.....
production ends....no word about software end support
MZO said:
It is officially discontinued, but I can bet my word that it would easily last till
Android P
Transmitted via BACON
Click to expand...
Click to collapse
Please don't spread false information.
Sent from my A0001 using Tapatalk
karthi89 said:
Please don't spread false information.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Wish it was false mate. But till now almost every OEM has had 2 years of software support time, so would this, and you guys babbled about source. I sent you. I'm trusting the same one, I'm basing it on same one. I'm not the one falsely reporting, whatever has to be done has to be from him. I have just spread the word as YOU GUYS ASKED.
Transmitted via BACON