Why Op2 Not getting Official cyanogenmod - OnePlus 2 Q&A, Help & Troubleshooting

Guys today i have a serious doubt.Why Oneplus Two not getting Offcial cyanogenmod nightlies support.
its being 5 months i guess,
Yuphoria got official nightlies in just 1 month. Why only with Oneplustwo like this

I think because of disputes between cyanogen and oneplus.

Shivamnarang said:
I think because of disputes between cyanogen and oneplus.
Click to expand...
Click to collapse
Umm can be a possibilty.But then cyanogenmod wont support fons lik htc,samsung all na, der is something els

I also waiting for official cyanogen oxygen os sucks ....

Shivamnarang said:
I also waiting for official cyanogen oxygen os sucks ....
Click to expand...
Click to collapse
wow there are many guys like me
bro are u sure development will be there. i fear op2 is dieing
and helen said soon op2 ota will come. and she said its major update

Shivamnarang said:
I also waiting for official cyanogen oxygen os sucks ....
Click to expand...
Click to collapse
Whats official cyanogen oxygen?

Official cyanogenmod build . ?
Oxygen os (op2 default rom)

jjbro007 said:
Guys today i have a serious doubt.Why Oneplus Two not getting Offcial cyanogenmod nightlies support.
its being 5 months i guess,
Yuphoria got official nightlies in just 1 month. Why only with Oneplustwo like this
Click to expand...
Click to collapse
Yophoria got official cm support in 1 month because it run CMOS is stock firmware for it. So they already have a build to go at
jjbro007 said:
Umm can be a possibilty.But then cyanogenmod wont support fons lik htc,samsung all na, der is something els
Click to expand...
Click to collapse
Sent from my ONE A2003 using Tapatalk

Wongher said:
Whats official cyanogen oxygen?
Click to expand...
Click to collapse
he forgot a dot afte cyanogen

Shivamnarang said:
Official cyanogenmod build .
Oxygen os (op2 default rom)
Click to expand...
Click to collapse
Oh good i didnot mean cyanogenos.
i mean cyanogenmod nightlies. (it will be there for samsung also)

spencer24 said:
Yophoria got official cm support in 1 month because it run CMOS is stock firmware for it. So they already have a build to go at
Click to expand...
Click to collapse
Nooo
even yureka for Cyanogen device.it got cyanogenMod after 4 months.
anyway i got info about the issue.
actually for offcial support. first the device tree must be stable. for use no fingerprint or laserfocus. offcial nightlies will come only if they are fix by a dev . Just pray it happens soon.then only custom rom flow will start

jjbro007 said:
Oh good i didnot mean cyanogenos.
i mean cyanogenmod nightlies. (it will be there for samsung also)
Click to expand...
Click to collapse
Bro both of them almost the same cyanogenmodos is unrooted default rom. And cyanogenmod nightlies is lil. Buggy but not stable. 3rd party rom for devices

That's probably Oneplus 2 doesn't have an official device maintainer in the Cyanogenmod division.

Sign to get Oxygen OS open sourced.
ONEPLUS, Carl Pei, Pete Leu: Release Sources for Oxygen OS!We need more development. - Sign the Petition!
https://www.change.org/p/oneplus-ca...utm_source=share_petition&utm_medium=whatsapp

jjbro007 said:
Guys today i have a serious doubt.Why Oneplus Two not getting Offcial cyanogenmod nightlies support.
its being 5 months i guess,
Yuphoria got official nightlies in just 1 month. Why only with Oneplustwo like this
Click to expand...
Click to collapse
The way official CM works is by getting a solid unofficial release with a device/vendor tree, then somebody offers to maintain an official branch.
Complaining about it without contributing anything isn't going to help. Why don't you offer to do all the work and maintain the OP2 for CM?

CrashTestDroid said:
The way official CM works is by getting a solid unofficial release with a device/vendor tree, then somebody offers to maintain an official branch.
Complaining about it without contributing anything isn't going to help. Why don't you offer to do all the work and maintain the OP2 for CM?
Click to expand...
Click to collapse
Seriously did i complain. I just wanted to know the reason why. Anyway thanks For the Info
And i have no interest in development. let see someday will contribute something

Related

Contacting CM to update sources to KK

Hello friends.
As all of us see, LG released their KitKat sources long time ago. Our great developers like @dr87 @Savoca @houstonn and others made it with Their hard work to merge them so we have two stable / nearly stable roms: Mahdi and PA. But what with other roms? Most of the roms are based on CM, so they still have bugs.. During months, CM doesn't seem to have done ANYTHING.
So my question is, how about to send a message (or spam, in any way u name it) by all of us to CM, to the maintainer? We have official support, but in fact it's "support without support" in my opinion. Maybe after these messages they would finally start to do something, because it's like they forgot about G2...
Regards.
EDIT: so we have a way to contact => https://jira.cyanogenmod.org/secure/Dashboard.jspa
now we should make a well, polite message so everyone would copy it and drop there.
Another way it would be to ask the maintainer directly https://plus.google.com/+RicardoCerqueira
EDIT2: I gave a comment to Ricardo on Google+ here https://plus.google.com/+RicardoCerqueira/posts/4dc8kVBYuTq feel free to do it as well
The best bet would be to create an improvement note at their so called "Bug Tracker" considering that they are doing this for free, this would be the most polite form.
I support this initiative, but today be entirely honest M6 for me is almost bug free, fast and battery efficient.
Up to date sources is great, but if a rom is working well, I don't care if the sources are old!
Inviato dal mio LG-D802 utilizzando Tapatalk
Airidas said:
The best bet would be to create an improvement note at their so called "Bug Tracker" considering that they are doing this for free, this would be the most polite form.
Click to expand...
Click to collapse
could u give a link please? so we could prepare a message and then everyone would leave it there
vittogn said:
I support this initiative, but today be entirely honest M6 for me is almost bug free, fast and battery efficient.
Up to date sources is great, but if a rom is working well, I don't care if the sources are old!
Click to expand...
Click to collapse
I personally had CM for some time, and it never was so stable as Mahdi R1 which i have now. Besides that, a lot of roms like Carbon or Slim can't be simply updated from CM sources, so they still have bugs.
reas0n said:
could u give a link please? so we could prepare a message and then everyone would leave it there
I personally had CM for some time, and it never was so stable as Mahdi R1 which i have now. Besides that, a lot of roms like Carbon or Slim can't be simply updated from CM sources, so they still have bugs.
Click to expand...
Click to collapse
Here: jira.cyanogenmod.org
Thanks, so anyone is, i would say, good in kind speaking to prepare a message?
Oh and we could also use Google+ and ask the maintainer directly https://plus.google.com/+RicardoCerqueira
Replyed 2 times to posts in his google + account with message " When LG G2 is going to have updated KK sources? A lot of people are waiting for bug-free CM and CM-based 4.4 ROMs ". I hope that all you guys do the same.Cheers
Sent from my LG-D802 using XDA Premium 4 mobile app
Just to clarify, roms that are based on CM do not need CM to upgrade to 4.4.2 sources. The upgrade is done in the device tree / vendor files and kernel. The rom source does not need any changes and each rom maintainer for the G2 has the power to upgrade their rom to 4.4.2 G2 sources without CM doing anything, they just need to figure out the specific device tree bugs for each rom and fix them.
I am under the impression you think CM needs to upgrade in order for CM based roms to upgrade, feel free to correct me if I'm wrong :good:
dr87 said:
Just to clarify, roms that are based on CM do not need CM to upgrade to 4.4.2 sources. The upgrade is done in the device tree / vendor files and kernel. The rom source does not need any changes and each rom maintainer for the G2 has the power to upgrade their rom to 4.4.2 G2 sources without CM doing anything, they just need to figure out the specific device tree bugs for each rom and fix them.
I am under the impression you think CM needs to upgrade in order for CM based roms to upgrade, feel free to correct me if I'm wrong :good:
Click to expand...
Click to collapse
apparently theres a bit of confusion, there was some one nightly where the rotation wasnt working with the jb baseband, (im gussing on that nightly he used the kk source ) because flashing the kk baseband on that build fixed the rotation issue, but im not quiet aware of what the situation is ince im back on stock. anyways ill be swinging it on the latest nightly just to clarify my doubts. and im pretty sure they just want the maintainer to switch to kk source , btw nice to see you here hope your cooking something great for us
dr87 said:
Just to clarify, roms that are based on CM do not need CM to upgrade to 4.4.2 sources. The upgrade is done in the device tree / vendor files and kernel. The rom source does not need any changes and each rom maintainer for the G2 has the power to upgrade their rom to 4.4.2 G2 sources without CM doing anything, they just need to figure out the specific device tree bugs for each rom and fix them.
I am under the impression you think CM needs to upgrade in order for CM based roms to upgrade, feel free to correct me if I'm wrong :good:
Click to expand...
Click to collapse
Well, in the past I had some Android phones, and CyanogenMod was always first with upgrading everything, and then other developers were basing their ROMs on these updates. I mean, they updated everything, end other ROMs were updated fast. They're not giving support which they were giving in the past, that's all.
reas0n said:
Well, in the past I had some Android phones, and CyanogenMod was always first with upgrading everything, and then other developers were basing their ROMs on these updates. I mean, they updated everything, end other ROMs were updated fast. They're not giving support which they were giving in the past, that's all.
Click to expand...
Click to collapse
Did you get a response from Ricardo?
LenAsh said:
Did you get a response from Ricardo?
Click to expand...
Click to collapse
Nope, i saw i got some 1+ on my comment, i shared second comment today. nothing..
reas0n said:
Nope, i saw i got some 1+ on my comment, i shared second comment today. nothing..
Click to expand...
Click to collapse
Oh

Any chance to get CM or AOSP?

Is there any chance to get CM or AOSP roms in future?
Source code has been released (yay Huawei!) so it shouldn't be long to get CM at least.
kimtyson said:
Source code has been released (yay Huawei!) so it shouldn't be long to get CM at least.
Click to expand...
Click to collapse
Great news! Any link for this?
Next month I'll buy the P8 Lite ALE-L21 and I hope that I will be able to install AOSP/CM12.
think this dude is on it
http://www.htcmania.com/showthread.php?t=1066152
Nope
sgspluss said:
Is there any chance to get CM or AOSP roms in future?
Click to expand...
Click to collapse
Its November 8th and still no Custom Rom Developers.....!!!! Do something please
Reyengine said:
think this dude is on it
http://www.htcmania.com/showthread.php?t=1066152
Click to expand...
Click to collapse
This dude indeed is making AOSP rom for our ALE 21 , but he is stuck at this moment , some problems with video decoder ...
I have made roms for my other phone wiko rainbow , so when i have a good source i can try to make cm or aosp working on our ALE21

[Discussion] Official CM14 nightlies for Bacon

Discussion and information about official cm14 nightlies.
Download latest nightly: get.cm/?device=bacon
Installation:
First time flashing CyanogenMod 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash CyanogenMod
Optional: Install the Google Apps addon package
Reboot​
Useful links
Latest twrp recovery: Download from here
Install twrp recovery: Official instructions
Gapps: Open Gapps
Jenkins: Build history of jenkins
(Check the build process)
Cyanogenmod code review: Gerrit review
Simple changelog: cmxlog
Device tree: Bacon cm14.1
Kernel tree: oneplus msm8974​
The odds are v might never get official cm14 .. but things might just change.,, All we gotta do is wait
vickeye said:
The odds are v might never get official cm14 .. but things might just change.,, All we gotta do is wait
Click to expand...
Click to collapse
The test builds out there seem fairly good. So I think odds are with us
vickeye said:
The odds are v might never get official cm14 .. but things might just change.,, All we gotta do is wait
Click to expand...
Click to collapse
Odds that we won't get a official? Why you claim this? There are phones older than Bacon that will be getting bacon.
the_rooter said:
Odds that we won't get a official? Why you claim this? There are phones older than Bacon that will be getting bacon.
Click to expand...
Click to collapse
May be I was wrong .. but if you look at the so called "801 and noughat drama " and there isn't a official branch for cm14 yet .. again I may be wrong .
vickeye said:
May be I was wrong .. but if you look at the so called "801 and noughat drama " and there isn't a official branch for cm14 yet .. again I may be wrong .
Click to expand...
Click to collapse
That was related to not getting official COS i.e. Stock ROM won't get Nougat. CM nightlies will be available just have to be patient they don't need to go through CTS
the_rooter said:
Odds that we won't get a official? Why you claim this? There are phones older than Bacon that will be getting bacon.
Click to expand...
Click to collapse
Bacon in bacon? OPO inception.
I'm sure CM14 will come to OPO in an officially branched CM capacity, but probably not a stock OnePlus commissioned capacity. Does that make sense? I'm still thinking about bacon in bacon...
https://github.com/CyanogenMod/android_device_oneplus_bacon/tree/cm-14.0
cm14 branch for bacon? someone post it in official cm13 nightly thread.
varben said:
Can we discuss about cm14? What is achieved until now? How are the early unofficial ROMs? Will we have an official cm14?
Seems like cm14 branch is up: https://github.com/CyanogenMod/android_device_oneplus_bacon/tree/cm-14.0
Click to expand...
Click to collapse
lets see.. i hope so
varben said:
Can we discuss about cm14? What is achieved until now? How are the early unofficial ROMs? Will we have an official cm14?
Seems like cm14 branch is up: https://github.com/CyanogenMod/android_device_oneplus_bacon/tree/cm-14.0
Click to expand...
Click to collapse
So its a green light for bacon users waiting for official cm14 right?
Sent from my A0001 using XDA-Developers mobile app
vickeye said:
May be I was wrong .. but if you look at the so called "801 and noughat drama " and there isn't a official branch for cm14 yet .. again I may be wrong .
Click to expand...
Click to collapse
The oneplus x with the same chipset as baocn has had a cm14 branch for a while now so I doubt they'll leave us behind
gursimar said:
So its a green light for bacon users waiting for official cm14 right?
Click to expand...
Click to collapse
Personally I can't say. But is a small step towards a possible official cm14 (imho)
Maybe this thread wakes up soon, there is bacon cm14 commits
Well, let's analyze it a bit. Official 6.0 release: 05.10.2015. First official cm13 nightly build: 24.11.2015. So, cm release just 1.5 month after official Marshmallow release.
Nougat release date: 22.08.2016. Most likely, we won't get anything usable after 1.5 months. Now we have nothing (nothing official, even official cm14 sources are unusable currently).
I see no reasons to be optimistic. Progress is much slower this time.
giaur said:
Well, let's analyze it a bit. Official 6.0 release: 05.10.2015. First official cm13 nightly build: 24.11.2015. So, cm release just 1.5 month after official Marshmallow release.
Nougat release date: 22.08.2016. Most likely, we won't get anything usable after 1.5 months. Now we have nothing (nothing official, even official cm14 sources are unusable currently).
I see no reasons to be optimistic. Progress is much slower this time.
Click to expand...
Click to collapse
It is just the processor support missing, from what I read. Other commits will follow more easily.
And finally bacon commits on gerrit...
http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_oneplus_bacon
giaur said:
Well, let's analyze it a bit. Official 6.0 release: 05.10.2015. First official cm13 nightly build: 24.11.2015. So, cm release just 1.5 month after official Marshmallow release.
Nougat release date: 22.08.2016. Most likely, we won't get anything usable after 1.5 months. Now we have nothing (nothing official, even official cm14 sources are unusable currently).
I see no reasons to be optimistic. Progress is much slower this time.
Click to expand...
Click to collapse
Agreed. It will probably be slower this time around since Cyanogen has let go of 20% of their workforce since CM13 was released.
Sent from my A0001 using Tapatalk
Elius2676 said:
Agreed. It will probably be slower this time around since Cyanogen has let go of 20% of their workforce since CM13 was released.
Click to expand...
Click to collapse
I don't see the connection here with cm14 and Cyanogen work force.
Cm doesn't depend on paid workforce.
varben said:
I don't see the connection here with cm14 and Cyanogen work force.
Cm doesn't depend on paid workforce.
Click to expand...
Click to collapse
I suggest you start doing your homework before speaking. Hint: go through the gerrit commits and look for people with "@cyngn.com" emails. maybe starting from Steve Kondik himself.
fmc000 said:
I suggest you start doing your homework before speaking. Hint: go through the gerrit commits and look for people with "@cyngn.com" emails. maybe starting from Steve Kondik himself.
Click to expand...
Click to collapse
Well, I think I did mine. CyanogenMod and CyanogenOs (from where the workforce was "fired") is not the same. So, please Carry on! This discussion is not useful really. It is discussed to death already.

official and supported for LONG TIME ROM for Redmi note 3 pro KENZO

post it every rom supported officially and for long time for kenzo!!!!
Cyanogenmod ..... Resurrection remix
Petar86 said:
post it every rom supported officially and for long time for kenzo!!!!
Click to expand...
Click to collapse
Stock:laugh::laugh:
aosp leaked qualcomm rom
Sent from my Redmi Note 3 using Tapatalk
sakibshahriyar98 said:
Cyanogenmod ..... Resurrection remix
Click to expand...
Click to collapse
cyano and rr release are stop from 20/08 .....
other????
Petar86 said:
cyano and rr release are stop from 20/08 .....
Click to expand...
Click to collapse
Last CM snapshot was 20/08. Nightlies have not stopped.
goofball2k said:
Last CM snapshot was 20/08. Nightlies have not stopped.
Click to expand...
Click to collapse
i know but it s not good
Cyanogenmod nightly is stable enough for daily use
without thinking, Resurrection Remix 5.7.4
rajkunisetti said:
aosp leaked qualcomm rom
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Leaked from where?
Sent from my Redmi Note 3 using Tapatalk
Debloated Stock.
up
Siddk007 said:
without thinking, Resurrection Remix 5.7.4
Click to expand...
Click to collapse
How to get RR updates. I cant find build after 8/20.
Audacity4545 said:
How to get RR updates. I cant find build after 8/20.
Click to expand...
Click to collapse
You probably won't find many or even any builds of RR past today's one. TheStrix has shifted to working on Android Nougat. RR is pretty stable mind you - if you look hard you might find the odd glitch or a crash that's hard to reproduce. Rare though. Likely the same sort of experience from the official CM builds, just without the RR features patched in. They're both maintained by him.
A good option for long-term support would be the xiaomi.eu MIUI builds... basically stock kenzo software without the superfluous MIUI stock apps baked in. It gets weekly patches.
Wish I'd tried more AOSP ROMs, there's likely some perfect vanilla android builds on here.
Nexus Experience Rom best Aosp Rom, stable, fast and batteryfriendly
CitrusCAF nougat ROM extremely super and stable
https://www.androidfilehost.com/?fid=385035244224383350
drmuruga said:
CitrusCAF nougat ROM extremely super and stable
Click to expand...
Click to collapse
Link to this ROM
ilvmyname said:
Link to this ROM
Click to expand...
Click to collapse
Added
drmuruga said:
Added
Click to expand...
Click to collapse
Thanks, but you should not just provide the link to the download, Link to the source where the original source was please?

No official LineageOS builds for Redmi 3s ('land')?

I see a couple of unofficial LineageOS builds for this phone, which are well received by testers/users. However, there is no official LOS build. Why is that? Isn't this phone hugely popular in India and China?
sclip said:
I see a couple of unofficial LineageOS builds for this phone, which are well received by testers/users. However, there is no official LOS build. Why is that? Isn't this phone hugely popular in India and China?
Click to expand...
Click to collapse
It's because Los guys have high standards (ie. completely bug-free) for their rom.
But soon we'll have our Official rom because a developer has applied for offical tag and it's in process ?
Sent from my Redmi 3S using Tapatalk
Problem from saving docoments which is downloading from google or drive and it also can't open from apps like adobe or office suite
lscambo13 said:
...soon we'll have our Official rom because a developer has applied for offical tag and it's in process ?
Click to expand...
Click to collapse
Thanks. Which Dev is that? Also, do we have an ETA for that? I am sick of MIUI8 with a lax update policy and bloat.
sclip said:
Thanks. Which Dev is that? Also, do we have an ETA for that? I am sick of MIUI8 with a lax update policy and bloat.
Click to expand...
Click to collapse
It's the one https://forum.xda-developers.com/showthread.php?t=3576227

Categories

Resources