CyanogenMod shut - ONE Q&A, Help & Troubleshooting

The team behind CynanogenMod has declared the existing brand dead, and announced plans to fork the source code of the mobile OS.
Does this mean there will not be CyanogenMod version after 14.1? Or does it mean that they will not provide official builds for devices?

Yes to both, because what is left of CyanogenMod will be forked into LineageOS. No nightlies are to be developed after today. The OS will lose all Cyanogen-related branding as the brand could be sold. LineageOS will have zero affiliation whatsoever with Cyanogen.

deleted - wrong thread

SirSoviet said:
LineageOS will have zero affiliation whatsoever with Cyanogen.
Click to expand...
Click to collapse
LineageOS (or LOS) will be composed of several Cyanogenmod developers. Just want to remind that.

riahc3 said:
LineageOS (or LOS) will be composed of several Cyanogenmod developers. Just want to remind that.
Click to expand...
Click to collapse
That's basically what I said though. Cyanogen is not related to CyanogenMod, at all.

Wrong section, it should be to General talking not troubleshooting
P.S. Already mentioned from other posts

Related

[Q] Building AOSP (not CM) for the OPO, is it possible?

Hi, I've just received my OPO on the 27th. I was really interested in Android development when I had my Nexus 5 and started building my own AOSP ROM, I've been looking into doing the same for the OPO but am unable to find an actual way of building AOSP with Google's code. I know OPO released their AOSP kernel source here: https://github.com/OnePlusTech/android_kernel_oneplus_one and CyanogenMod has thiers here: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974 but I'm unable to work out a way of including these into my AOSP build and I would prefer to not build CM.
Note: I'd like to build AOSP myself, I'm fully aware that there is a current official OPO build available.
Thanks in advance,
Lewis
LewisD94 said:
Hi, I've just received my OPO on the 27th. I was really interested in Android development when I had my Nexus 5 and started building my own AOSP ROM, I've been looking into doing the same for the OPO but am unable to find an actual way of building AOSP with Google's code. I know OPO released their AOSP kernel source here: https://github.com/OnePlusTech/android_kernel_oneplus_one and CyanogenMod has thiers here: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974 but I'm unable to work out a way of including these into my AOSP build and I would prefer to not build CM.
Note: I'd like to build AOSP myself, I'm fully aware that there is a current official OPO build available.
Thanks in advance,
Lewis
Click to expand...
Click to collapse
It's advisable that you create your own tree from the CAF MSM8974 using CM GPS and other drivers and build CAF AOSP. Otherwise, it's close to impossible/very difficult. Pure AOSP is again near impossible/very difficult for non nexus devices.
Thank you very much for the reply, so building AOSP is pretty much impossible then?
I was having a look around on the internet last night and came across this: http://developer.sonymobile.com/kno...uild-aosp-kitkat-for-unlocked-xperia-devices/
Would there be a way of adapting this guide to allow for an easier build process of AOSP for our device? The other confusion that I face is if it's impossible to build AOSP for the OPO then how are ROMs such as this available?
LewisD94 said:
Thank you very much for the reply, so building AOSP is pretty much impossible then?
I was having a look around on the internet last night and came across this: http://developer.sonymobile.com/kno...uild-aosp-kitkat-for-unlocked-xperia-devices/
Would there be a way of adapting this guide to allow for an easier build process of AOSP for our device? The other confusion that I face is if it's impossible to build AOSP for the OPO then how are ROMs such as this available?
Click to expand...
Click to collapse
VanirAOSP uses CM trees as of now. Again, CAF AOSP is basically AOSP for non nexus Qualcomm devices., and any experienced dev can whip up a tree and get it working. Also, reaally good devs can/may be able to port AOSP if they wanted. It's a matter of whether they want to do it or not.
That link is for Sony devices only because Sony already provides CAF trees as an OEM so devs can build.
rudi_j7 said:
VanirAOSP uses CM trees as of now. Again, CAF AOSP is basically AOSP for non nexus Qualcomm devices., and any experienced dev can whip up a tree and get it working. Also, reaally good devs can/may be able to port AOSP if they wanted. It's a matter of whether they want to do it or not.
That link is for Sony devices only because Sony already provides CAF trees as an OEM so devs can build.
Click to expand...
Click to collapse
Ah yes, I see what you're saying now. Thanks for clearing this up for me! I just noticed when I looked at the VanirAOSP ROM thread that it states CM for it's credits, haha. I apologize for my ignorance.
Hello
I would like to create my first rom for oneplus one but without modification from OMNI or CM, basically vanilla rom. but I have some doubts.
Can I create a rom based on AOSP with device tree from OMNI/CM right?
Thanks!

All ROMs Ever thread

Do not post "Thank you" type responses.​[SIZE=+3]ALL ROMS EVER (Intro to be added)[/SIZE]
[SIZE=+2][INDEX][/SIZE]
[SIZE=+2]Helpful Information[/SIZE]​[SIZE=+1]Welcome, this thread has been created to encompass everything you may need for your android device. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread, or create your own thread in the Q&A forum. Do not use this as a general help thread.
Since most ROMs are MM now I will split ROMs in this thread into 2 sections, MM and EOL.
This thread probably isn't going to help anyone. If it does help you, however, please tell me the usage in a post!
Please tell me if I made any mistakes in the categorization, and add on new ROMs as they come out/those which I forgotten to add.
Lastly, Stock-Based ROMs will not be added unless it is being ported to other devices eg. Xperia ROM ported to XOSP to other devices[/SIZE]​Click on a Link below for More Info
MM ROMs
Toolchains
EOL ROMs
Kernels
Useful links any general index should have
http://forum.xda-developers.com/showpost.php?p=65849943&postcount=34
*​Forum Rules | New Users Guide | XDA Tour | Report Posts​Please look for a similar INDEX thread when visiting another device forum.
If you would like to create an [INDEX] please Click Here.
A special thanks to everyone who contributed to the production of this INDEX
Please note: This is and will be, an ongoing WIP​
MM ROMs
*Mainly* CM-Based:
CyanogenMod
Temasek's CM
PAC ROM (And their cute but old website copyrighted 2014)
AICP
BeanStalk ROM
BlissPop ROM
AOKP
Resurrection Remix
XOSP
crDroid
CyanPop
OctOS
Marsh
MoKee
LiquidSmooth (+Slim base)
FlexOS (This is relatively obsolete as compared to Team Flex's AOSP-based Flayr OS)
OwnRom
TeslaOS (Not to be confused with Tesla by GZR)
*Mainly* AOSP/CAF-Based:
Dirty Unicorns (And CAF)
Pure Nexus
Cyanide L MM (Apparently it isn't Cyanide M) (Un-merged with Fusion from VrToxin)
OmniROM
Tesla by GZR
Slim
YAOSP
SlimYAOSP (Repo Init THIS first)
Nameless ROM
Broken ROM
Chroma ROM
MoKee
UberMallow (Previously OptiPop)
CandySix
FlayrOS
Exodus ROM (Quite confused as to which manifest to link to)
Validus by GZR
TipsyOS
OrionOS
Screw'D AOSP
AOSiP
ZephyrOS
BenzoRom
Beltz Rom (AOSP with DUI)
Cardinal AOSP
Citrus CAF
Evervolv
CopperHead OS
Toxic OS
All Purenexus and Slim mods from the guys at http://forum.xda-developers.com/slimroms/general/rom-builders-collective-t2861778
Toolchains
Guide for using below TC
UberTC (And Github) (For Pre-Built TC refer to BitBucket)
Linaro
SaberMod (Pre-Built TC at their website)
Hyper Toolchains
DragonTC
Christopher83's custom TC builds
Archi's Toolchains (Change the branches to change TC)
EOL stuff
VrToxin (Apparently some internal strife)
Fusion (Merged with Cyanide to VrToxin, then VrToxin died)
Archidroid/Archikernel (Should be getting a revive soon since Archi got an OP2)
Perseus Kernel (IDK why it died, too long ago)
Minimal OS (IDK why it died. Wanted to build this in particular because LP Minimal is awesome but suddenly github activity stopped)
Paranoid Android (RIP will miss you guys. They got "bought over" by OnePlus to dev OxygenOS)
F-AOSP (IDK why it died.)
Yank Kernel (I think he just gave up or something)
[*]80% of Dirty Unicorn (Went over to some Russian company) (Hi Mazda/Alex Cruz)
Euphoria OS
RadonX
Nexus Experience
Custom Kernels
AK Kernel
Lightning Kernel
Agni kernel
Arter97's Kernels
Boeffla Kernel
Franco Kernel
ElementalX
Phasma Kernel
Kylo Kernel (Same as above...???)
Some random modded kernels mostly in Nexus forums I didn't bother to add
RIP people.
A filler and awareness post.
See you in heaven. I know you are in a better place now.
TonyStark
FlashVetrin
Please add on. So far I only know of those two ^^
Garbage Link Collector
Another Link Collector (But not structured so Garbagely)
A ROM Building Guide for you to build ANY ROM on this list
XDA New User Guide
How to shake off "n00b" status
How to get Moderator's attention (Don't waste their time unnecessarily though )
Requests to Mods (All users welcome)
Logcat (MEOW)
Commonly used acronyms on XDA
How to become RC/RT
Signature Code Sharing
Archi's Optimisations (And for MM)
Index Project
Ask Away Project
Anti-Piracy/ContentGuard
NEED-TO-READ 1
NEED-TO-READ 2
Special thanks to:
@Trafalgar Square
@sd_shadow
@kuzibri
@zelendel
And everyone else at the Index Thread!!
Temporary to-do:
CarbonROM
others?
limjh16 said:
Last one
Click to expand...
Click to collapse
I would add descriptions and differences between rom types
https://en.wikipedia.org/wiki/List_of_custom_Android_firmware
http://android.wikia.com/wiki/Category:Custom_ROMs
http://lifehacker.com/5915093/five-best-android-roms
Sent from my KFFOWI using XDA Labs
limjh16;65315332
said:
CM
AOSP
Others
Kernels
Dead ROM/Kernels
Useful links any general index should have
[/INDENT][/INDENT]
*​Forum Rules | New Users Guide | XDA Tour | Report Posts​Please look for a similar INDEX thread when visiting another device forum.
If you would like to create an [INDEX] please Click Here.
A special thanks to everyone who contributed to the production of this INDEX
Please note: This is and will be, an ongoing WIP​
Click to expand...
Click to collapse
Hi,
sofar, so good. Would it be an idea to also add an item which devices are supported and which not? I would remove the item "Dead ROM/Kernels", they are of no use for your thread and may cause confusion.
kindest regards,kuzibri
Here is a big list of porting and compiling rom guides
[Guides][Updated] All Guides @ One Place By Hpsgill by Hpsgill
kuzibri said:
Hi,
sofar, so good. Would it be an idea to also add an item which devices are supported and which not? I would remove the item "Dead ROM/Kernels", they are of no use for your thread and may cause confusion.
kindest regards,kuzibri
Click to expand...
Click to collapse
That item is meant for stuff like AOKP where its dead, but for those who want kitkat then they can refer.
sd_shadow said:
Here is a big list of porting and compiling rom guides
[Guides][Updated] All Guides @ One Place By Hpsgill by Hpsgill
Click to expand...
Click to collapse
Will have a look and add to useful links section.
This thread is gonna take really long to get updated I am very busy with school haha...
limjh16 said:
This thread is gonna take really long to get updated I am very busy with school haha...
Click to expand...
Click to collapse
Why did you choose to start such a thread, which is very time consuming, when you are so busy with school? If I were you, I would restrict your available time to make an index thread of your own devices (i9305 or SGS3-LTE). I can understand your wish of creating the thread that's in your mind, but you do need/have the time to create and maintain it, which is IMHO almost impossible when you are also at school. If you still want to create this ALL ROM EVER thread, ask help from other members to help you, cause you cannot do it on your own. Nevertheless, if you still want to continue with this ALL ROM Ever thread, I'm willing to help you where ever I can. :good:
kindest regards, kuzibri
kuzibri said:
Why did you choose to start such a thread, which is very time consuming, when you are so busy with school? If I were you, I would restrict your available time to make an index thread of your own devices (i9305 or SGS3-LTE). I can understand your wish of creating the thread that's in your mind, but you do need/have the time to create and maintain it, which is IMHO almost impossible when you are also at school. If you still want to create this ALL ROM EVER thread, ask help from other members to help you, cause you cannot do it on your own. Nevertheless, if you still want to continue with this ALL ROM Ever thread, I'm willing to help you where ever I can. :good:
kindest regards, kuzibri
Click to expand...
Click to collapse
I didn't expect my first term of school to be so hectic, I created this before my term started. It's alright, I'll just leave this here. Not like anyone except you and sd_shadow comes here... but I'll try to update once a week.
To be honest most won't bother as not all roms are available for all devices.
Also don't put any fair in what someone else thinks of a rom. Their opinion almost never really matters.
zelendel said:
To be honest most won't bother as not all roms are available for all devices.
Also don't put any fair in what someone else thinks of a rom. Their opinion almost never really matters.
Click to expand...
Click to collapse
Hmm true... But I created mostly for me cuz I was just going around xda finding a ROM to build so I thought this thread would help.
limjh16 said:
Hmm true... But I created mostly for me cuz I was just going around xda finding a ROM to build so I thought this thread would help.
Click to expand...
Click to collapse
No sure where it would help but ok. Going around building roms from other groups will not last long. More and more teams are closing their source and not letting others use it.
So if your worried about building then I would start my own project and start from scratch with it. Aosp not CM
zelendel said:
No sure where it would help but ok. Going around building roms from other groups will not last long. More and more teams are closing their source and not letting others use it.
So if your worried about building then I would start my own project and start from scratch with it. Aosp not CM
Click to expand...
Click to collapse
Well I just started learning how to build so idk how to start off my own ROM project... But I am interested...... Teach me please...?
limjh16 said:
I didn't expect my first term of school to be so hectic, I created this before my term started. It's alright, I'll just leave this here. Not like anyone except you and sd_shadow comes here... but I'll try to update once a week.
Click to expand...
Click to collapse
Hi,
it's no problem that it will take longer that you thought initially. I agree with @zelendel regarding this: "So if your worried about building then I would start my own project and start from scratch with it. Aosp not CM" Cyogen Mod is a world on it's own and accepted as a fully functional OS. Regarding the fact that only sd_shadow and I, besides zelendel now, only visit your thread, is logical because it's a WIP.
kindest regards, kuzibri

Will community continue to develop to this phone after cyanogenmod is done in 6 days?

Will community continue to develop to this phone after cyanogenmod is done in 6 days? As some of you may know Cyanogen inc had lots of issues so they decided to shutdown the company after 7 years of work. Some of the official devs started to tease a cyanogenmod reborn, named Lineage OS. You can find them on twitter, facebook, google+ and their new site lineageos.org . The site is still wip but i hope that Lineage OS will be developed for this phone and i dont have to throw my phone off the window just cause i dont have the latest update
As the source code will still available and the team is willing to continue, I see no reason for stopping, as long as our device maintainers support this device. But it may slow down a bit for a while, it's been a major transition after all. And rest of the custom ROMs might get affected too. Better to stay tuned in every thread possible, ours is not so big
Broadcasted from Zeta Reticuli
Gravemind2015 said:
As the source code will still available and the team is willing to continue, I see no reason for stopping, as long as our device maintainers support this device. But it may slow down a bit for a while, it's been a major transition after all. And rest of the custom ROMs might get affected too. Better to stay tuned in every thread possible, ours is not so big
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
youre right. i guess ill make sure im in the latest nightly in the next days if anything happens
The question is will CyanogenMod continue to live now that they have lost all support from Cyanogen, including build servers, monetary, and technical support... CyanogenMod will be renamed to LineageOS... The biggest problem is all development on Moto G 2015 (and many other Moto devices) is based on CyanogenMod, and there is no other source at this time. How will that play out? We don't know yet...
A well formed (and informed) answer from Stack Exchange's Android Enthusiast group:
CM's own blog is unreachable now, but XDA-Developers already summed it up and clarified some important bits:
All monetary and infrastructural support for CyanogenMod from Cyanogen Inc. will cease. -> CyanogenMod will no longer receive nightly builds after December 31st... unless the team finds another host to build nightlies.
The CyanogenMod team will not continue official development on the project.
CyanogenMod will rebrand as LineageOS.
Since it's clear that Cyngn is going in a new direction, Cyanogen OS will almost certainly have no future, since it's not community-driven in the first place. CyanogenMod, on the other hand, will live a bit longer, until Lineage dawns (or fails).
Click to expand...
Click to collapse
Wasn't Omnirom a fork of CM after the creation of Cyanogen Inc? As I recall all the developers were upset over going commercial and the future of cyanogenmod. Lineage OS would in essence be a fork of Cyanogenmod as well. I think it will really depend on whether they can find funding for some build infrastructure and how many developers jump on board.
acejavelin said:
The question is will CyanogenMod continue to live now that they have lost all support from Cyanogen, including build servers, monetary, and technical support... CyanogenMod will be renamed to LineageOS... The biggest problem is all development on Moto G 2015 (and many other Moto devices) is based on CyanogenMod, and there is no other source at this time. How will that play out? We don't know yet...
A well formed (and informed) answer from Stack Exchange's Android Enthusiast group:
Click to expand...
Click to collapse
The repositories are being mirrored (probably 'forked' is the correct term) into linageOS so I think we'll have a copy of our source code. And they said the source code for CM would still be available.
https://github.com/LineageOS?tab=repositories
Broadcasted from Zeta Reticuli
BTW, it isn't ending on Dec 31st like most people thought... it's ending prior to Dec 31st... They lost DNS and Jenkins yesterday, the blog is gone (so no reference to the official posts), official Cyanogen and CyanogenMod websites are down, and probably more that I haven't noticed mentioned yet are gone already.
But https://download.cyanogenmod.org is still live.
What would be the status of other custom roms that are based on cyanogenmod. Would they be affected ?
aa1010 said:
What would be the status of other custom roms that are based on cyanogenmod. Would they be affected ?
Click to expand...
Click to collapse
Of course...ALL ROMs for this device, except stock based ones, use the CM device tree and base code... Will LineageOS replace that? Right now it appears that way but time will tell.
To be honest, if CM/LineageOS doesn't make it... Probably 80℅ of all ROMs out there will disappear as we know them today, we really don't know the long-term effects this will have on the ROM community.
Some dumb questions:
1. LineageOS is the same team as CM?
2. There's a release date for the lineageOS and it will be compatible with moto g 2015?
3. To keep updated is better to wait or change to an AOSP based rom since AOSP will still be releasing?
h0ttentot said:
Some dumb questions:
1. LineageOS is the same team as CM?
2. There's a release date for the lineageOS and it will be compatible with moto g 2015?
3. To keep updated is better to wait or change to an AOSP based rom since AOSP will still be releasing?
Click to expand...
Click to collapse
1.2.3 i dunno but i hope everything will be fine
h0ttentot said:
Some dumb questions:
1. LineageOS is the same team as CM?
2. There's a release date for the lineageOS and it will be compatible with moto g 2015?
3. To keep updated is better to wait or change to an AOSP based rom since AOSP will still be releasing?
Click to expand...
Click to collapse
1. Yes, to a point... for more information look at http://lineageos.org/Yes-this-is-us/
2. We don't know yet, they do not have build servers at the moment
3. I would wait, there is little chance of getting a working AOSP device tree at this time, but we will just have to wait and see.
The point is, right now we don't know exactly how this is all going to play out... we need to have patience and just see what happens.
---------- Post added at 01:29 PM ---------- Previous post was at 01:12 PM ----------
I would suggest everyone following this thread, look here: http://forum.xda-developers.com/2015-moto-g/general/cyanogenmod-to-lineageos-t3526944

official or unofficial

Hi, i always wanted to know but Never ask..
Now i want to know about and sorry of simple demand.
What is the diference between an official ROM and unofficial ROM ?
And also diference of thread Android development with original Android développement.
Thanks.
green2005 said:
Hi, i always wanted to know but Never ask..
Now i want to know about and sorry of simple demand.
What is the diference between an official ROM and unofficial ROM ?
And also diference of thread Android development with original Android développement.
Thanks.
Click to expand...
Click to collapse
It's actually fairly simple... an "official" ROM is one that is authorized, and often supported by, the development team of that ROM and the device is considered an "officially supported device".
But since the source code for these ROMs is open source, anyone can build or compile them for their device or another device that isn't officially supported. The ROM is not supported by the development team, but by the ROM maintainer/builder only. These types of builds that are either not officially supported devices, have modified the source code outside of the original developers guidelines, or not authorized by the development team are called "unofficial". They may even be by the same maintainer as the official version, but they modified (perhaps used a different toolchain) from the original guidelines for the ROM and it cannot be considered official any longer.
Really, it's boils down to: is the device supported and authorized by the core ROM development team... if yes, it's official... if no, it's unofficial.
Android Original Development is supposed to be for ROMs, kernels, and other projects that are completely original by the author, or authorized originals... Cyanogenmod/LineageOS is a good example of this... ROMs like Resurrection Remix are not considered "original" because they are based on Cyanogenmod, thus they just go into the Android Development section.
If in doubt about what the forum groups are for, read the sticky posts in each group.
Thanks now it's more clear

AOSP ROM support?

Are there any AOSP support for this phone? Also is there a telegram group
iXanza said:
Are there any AOSP support for this phone? Also is there a telegram group
Click to expand...
Click to collapse
Yes aosp. no tg for that. Some are familiar with Resurrection Remix for op7T and all the other roms I built for it. Building a device tree rn.
FullOfHell said:
Yes aosp. no tg for that. Some are familiar with Resurrection Remix for op7T and all the other roms I built for it. Building a device tree rn.
Click to expand...
Click to collapse
Are you going to build for the 8T??
I was going through various posts and thought NO devs / builders bought the phone.. fingers crossed, if you do and need a tester shout out
TrOjAn
FullOfHell said:
Yes aosp. no tg for that. Some are familiar with Resurrection Remix for op7T and all the other roms I built for it. Building a device tree rn.
Click to expand...
Click to collapse
Thank you for this update.
FullOfHell said:
Yes aosp. no tg for that. Some are familiar with Resurrection Remix for op7T and all the other roms I built for it. Building a device tree rn.
Click to expand...
Click to collapse
All eyes on you. Hope we see TWRP quickly
Good to hear the possibility! cheers
Is there a reason this phone seems rather unpopular in terms of development? The Nord is only a little older and had tons of ROMs to choose from. Is it because the 8T was released with Android 11 maybe?
bemymonkey said:
Is there a reason this phone seems rather unpopular in terms of development? The Nord is only a little older and had tons of ROMs to choose from. Is it because the 8T was released with Android 11 maybe?
Click to expand...
Click to collapse
From what I've read and experienced, it can take a few months for the development to boom for most new phones.
Looks like Pixel Experience 11 was just posted. Things are moving forward, woohoo!

Categories

Resources