Database Info

[Q] CyanogenMod 7.1 RC1 vs CyanogenMod 7.1 Nightly Builds

Hye, can I ask something?
What's the difference between
CyanogenMod 7.1 RC1 => http://forum.xda-developers.com/showthread.php?t=1240177
and
CyanogenMod 7.1 Nightly Builds => http://forum.xda-developers.com/showthread.php?t=1268304
Try to search for it, but still cannot find the difference.
Thanks.

Ummm, the differences come...get ready....nightly.
Sorry, not trying to be an ass, but couldnt resist. Nightlies are updated more or less nightly with new tweaks and features. RC is the last known stable, non-experimental build. If you follow the nightly thread, I'm sure someone will be posting links to the changelog.
Sent from my PC36100 using xda premium

It's okay. Still newbie here.
Yes, the word nightly. I know that, but after try searching the difference, still know nothing.
So, what do you mean is, nightly builds is official rom from cyanogenmod?

They are both official, but nightlies contain changes done to improve the roms, ofcourse doesn't always mean that it improves. Those are what I like to think of as "experimental". RC stands for release candidate. Rc's have been known to be the latest stable rom that is ready for public testing. Still, rc's are just released to receive approval, once everyone likes it, it may become official, or Stable release. You'll know when they're unofficial, they will state so in the threads name.

RC[Release Candidate] is the Stable Release While Nightly Builds are often modified with new tweaks and always improved, which means nightly are quick updated

CyanogenMod RC and Nightly Builds explained
In the world of CyanogenMod...
7.1 = indicates the version number of the mod
RC = Release Candidate, mostly bug-free, also known as "stable", change log usually available
Nightly Builds are
Beta
No change-log. Cyanogen fans accept that they would rather a Modder/Developer spend time working on a new version, than taking precious time to write change logs documenting every thing they did/tweaked.
Not released at a certain time (night).
Not released EVERY night, could be weekly.
A new "nightly" version is released, when the developer/modder is ready to upload it.
Any inquiries of when a new RC or nightly will be available will receive the following tin-can reply, "it'll be ready when its ready."
"Nightly" CyanogenMod fans/users are like Pit Bulls who haven't been fed in 3 days. They look forward to a new version every "night", even if its bugged and bad. If the a new "nightly" released version is very buggy, the CyanogenMod fan/user will simply restore/revert to an earlier CyanogenMod version that worked, whether its nightly or RC version, simply using the "restore" of a backup function. All CyanogenMod fans are advised to backup, before doing any changes. Those that don't, usually regret it, and won't do it again.
Those Developers/Modders working tirelessly to improve upon the CyanogenMod are doing it for the most part on their own time late at night. Bugs expected, because it wasn't thoroughly tested because so many CyanogenMod fans are eager and hungry for the latest version with cool features and tweaks and hope to not wait a month+ for an official-mostly'debugged-version(RC).
Each Android Mobile requires dedicated Modders/Developers, because every mobile has different ram/rom/processor/buttons/irks/camera and requires a special build. Therefore if you have an outdated mobile (ie. G1) that no dedicated Modders/Developers are using, you may never see an CyanogenMod update again.
In the world of updating a Android OS, if you fix/add one feature, it may/will break/not-work another feature. Usually the first thing to break/not-work the camera &/or the video camera &/or the front camera. If you're planning to become a Developer/Modder, expect a lot of frustration.
nartz said:
Hye, can I ask something?
What's the difference between
CyanogenMod 7.1 RC1 => http://forum.xda-developers.com/showthread.php?t=1240177
and
CyanogenMod 7.1 Nightly Builds => http://forum.xda-developers.com/showthread.php?t=1268304
Try to search for it, but still cannot find the difference.
Thanks.
Click to expand...
Click to collapse

nartz said:
Hye, can I ask something?
What's the difference between
CyanogenMod 7.1 RC1 => http://forum.xda-developers.com/showthread.php?t=1240177
and
CyanogenMod 7.1 Nightly Builds => http://forum.xda-developers.com/showthread.php?t=1268304
Try to search for it, but still cannot find the difference.
Thanks.
Click to expand...
Click to collapse
In answer to the qusetion; nothing.
The RC1 in the link is an official port for Cyanogen7 that is so much of a recent development that it is not yet included in the CM Nightly releases that have already been explained. I'm guessing that it will still be a port until after this round of updates when Nexx's excellent "RC1" will finally be fully integrated into the Cm device family.
As very little can happen to a nightly build sometimes, Nexx just can't be arsed to update nightly, he just does it when there's a biggy in the changelog.
Keep up the good work Nexx. v105 is Solid.
What do I know? http://download.cyanogenmod.com/?type=nightly&device=saga :s

[Q] question about CM12 Unofficial Hammerhead

It seems that since a couple of new builds in, there's suddenly a stream open to the official OTA updates in the CM updater in the unofficial builds of @mo976, are these builds similar or identical? What's the difference?
I might be mistaken though, but wanted to be sure about this..
Thanks a lot, I'm enjoying these builds either way mo976. :good:

Difference is, one is official, and the other isn't. Best to rely on the official one because of the amount of people working on it.

Thanks man :good:

Question about custom roms vs CM12S/Oxygen

Hey guys,
Just a quick question that I'm hoping someone can clear up for me. I have been flashing phones since the Vibrant and I seem to recall back then (and other phones I've had after such as the Sensation) devs would use the source of the firmware released from the manufacturer to create more stable roms and until that source was released there would be the possibility of the bugs.
I am coming from a Nexus 5 which I just used the stock rom since I wanted the OTA updates so it's been a while since I've flashed custom roms.
My question is, is the OPO the same way in the sense that in order to have more stable roms the source has to be released by CM in order to be more stable or is this a whole different beast where that isn't a necessity?
Thanks.

CM11S/CM12S is derived from the CM11/CM12 nightlies, all current ROMs are based on those CM sources, so all current ROMs are up to date. If you're flashing CM12 nightlies there's nothing extra that you need to do because firmware and modem is built in, but if you're flashing another custom ROM you need to flash the appropriate firmware and modem before flashing the ROM.
Oxygen is the exception to the above information, in the sense that it isn't based on CM. Flashing Oxygen will automatically flash the appropriate firmware, but if you want to revert back you need to flash the correct firmware/modem first.
Transmitted via Bacon

timmaaa said:
CM11S/CM12S is derived from the CM11/CM12 nightlies, all current ROMs are based on those CM sources, so all current ROMs are up to date. If you're flashing CM12 nightlies there's nothing extra that you need to do because firmware and modem is built in, but if you're flashing another custom ROM you need to flash the appropriate firmware and modem before flashing the ROM.
Oxygen is the exception to the above information, in the sense that it isn't based on CM. Flashing Oxygen will automatically flash the appropriate firmware, but if you want to revert back you need to flash the correct firmware/modem first.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, I did not know that but it does clear some other things up.
One other question, when a Samsung (for example Galaxy S5) rom is leaked, developers will use the latest leak to update their roms but typically a rom won't be "stable" until it is based on the source that is released.
Is the OPO like that as well where the custom roms need to have a source released in order to do that (is this the google android source or CM source?), I guess I'm trying to find out the stability of the roms versus a stock rom and whether there will be more bugs in one or the other.

sahil04 said:
Thanks, I did not know that but it does clear some other things up.
One other question, when a Samsung (for example Galaxy S5) rom is leaked, developers will use the latest leak to update their roms but typically a rom won't be "stable" until it is based on the source that is released.
Is the OPO like that as well where the custom roms need to have a source released in order to do that (is this the google android source or CM source?), I guess I'm trying to find out the stability of the roms versus a stock rom and whether there will be more bugs in one or the other.
Click to expand...
Click to collapse
That's what I answered in my last reply. The CM nightlies are the source, all ROMs are built based on those nightlies (except for a couple). This phone is nothing like a Samsung or an HTC where the stock ROMs are different from the aosp ROMs or CM based ROMs. The stock ROM for this phone is the CM ROM. The stock source is always released, every single day.
Transmitted via Bacon

timmaaa said:
That's what I answered in my last reply. The CM nightlies are the source, all ROMs are built based on those nightlies (except for a couple). This phone is nothing like a Samsung or an HTC where the stock ROMs are different from the aosp ROMs or CM based ROMs. The stock ROM for this phone is the CM ROM. The stock source is always released, every single day.
Transmitted via Bacon
Click to expand...
Click to collapse
Got it! Thank you!!

timmaaa said:
That's what I answered in my last reply. The CM nightlies are the source, all ROMs are built based on those nightlies (except for a couple). This phone is nothing like a Samsung or an HTC where the stock ROMs are different from the aosp ROMs or CM based ROMs. The stock ROM for this phone is the CM ROM. The stock source is always released, every single day.
Transmitted via Bacon
Click to expand...
Click to collapse
Not exactly true. CM is AOSP BASED, but modified - sometimes quite a bit. In the case of CM12S - this is a ROM specific to the OnePlus One. It isn't the same as CM12. It is only for this specific phone, and has some features in it that are specific to this phone.
I'm not sure why anyone would want to install Oxygen OS, unless they have just been brainwashed by OP that CM is now bad. Well that and the fact that CM still hasn't released 12S, nor am I convinced that they ever will. They seem to be pretty terrible when it comes to keeping up with the commercial side of things... Very amateurish.

mhannigan said:
Not exactly true. CM is AOSP BASED, but modified - sometimes quite a bit. In the case of CM12S - this is a ROM specific to the OnePlus One. It isn't the same as CM12. It is only for this specific phone, and has some features in it that are specific to this phone.
Click to expand...
Click to collapse
I know that CM is essentially aosp, and CM11S/CM12S is 99% CM11/CM12, with just a couple of fancy apps thrown in on top to make it seem a bit different. It really is just like a milestone release of the main CM branch, a stable release.

Not Exactly.
Heisenberg said:
I know that CM is essentially aosp, and CM11S/CM12S is 99% CM11/CM12, with just a couple of fancy apps thrown in on top to make it seem a bit different. It really is just like a milestone release of the main CM branch, a stable release.
Click to expand...
Click to collapse
Not really. There are no apps of which I am aware that that put in the "S" release. But there are features specific to the needs of that device and to that user community that add value.

mhannigan said:
Not really. There are no apps of which I am aware that that put in the "S" release. But there are features specific to the needs of that device and to that user community that add value.
Click to expand...
Click to collapse
CameraNext, the custom lockscreen. Both apps that are unique to Cyanogen OS. I'm sure there are more but I don't run that ROM so I can't check. You can believe it or not, but Cyanogen OS is just CM with a few extra apps/features. Your lack of belief in it doesn't stop it from being true.

What is the reason for the cyanogenmod 13 not working on the newer build numbers?

Is there any method we can change the build number on the cm13 zip file we download to be able to install it on a newer version?
or is there any method for us to build the cyanogenmod 13 rom on our own(since everything is available)? It should help many people. Also if possible I would like to build an aosp rom for our devices. I have another stupid question, please bear with me. Someone has created the cyanogenmod rom for us and it is official, but they did not make any posts in the xda forums .

Im curious about some of this stuff, too. Especially the reason why you can't flash on the newer firmware, and why no CM thread.

rouyal said:
Im curious about some of this stuff, too. Especially the reason why you can't flash on the newer firmware, and why no CM thread.
Click to expand...
Click to collapse
exactly! hope to find out soon.

newer builds have a different bootloader. probably just the guy hasnt noticed because he uses cm13 which doesnt touch the bootloader

Looking for *stable* custom ROM

I realize that this is not the first topic to ask for custom ROM advice, and that the general advice is "try some and pick the one you like best". This thread is different in that I am specifically looking for a stable custom ROM. I was surprised to find out that LineageOS does not offer any stable builds for our device, nor does AOKP; they both only offer nightlies. Are there alternatives that do offer stable builds?

You can try Ressurection Remix. I used it last month and its pretty stable. Also this ROM recently (22.12.17) got update.
Also have great customization options too!
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-n-5-8-2-t3587204
But if you want good Oreo 8.1 Rom then I suggest crDroid. I use it now and i am satisfied with it. Only flaw that i cant get Magisk root to work. (also recent update 21.12.2017)
https://forum.xda-developers.com/2015-moto-g/development/rom-crdroid-android-4-0-t3696388

Nothing is as stable as stock.

I am specifically looking for a stable custom ROM
Click to expand...
Click to collapse
me too Nougat will be preferable, so maybe someone with experience will say something, now I am on stable STOCK

do you want a 7.1.1 build (probably CM/Lineage 14.1) or Oreo (probably new aospex https://forum.xda-developers.com/20...xtended-rom-v5-0-t3681997/page53#post75051303 but camcorder not work in 8.x builds have to use footej or cameraFi2.) Holler if you need more pointers. LinOS 15.x is not supported at the moment even though the thread is there.
look at https://forum.xda-developers.com/2015-moto-g/general/pursuing-8-1-osprey-moto-g-2015-t3718416 for pointers to 3 other 8.x builds.

You can try this - Ressurection remix, very stable Nougat 7.1.2
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-n-5-8-2-t3587204

Resurrection Remix is not stable - according to the topic you link to, it's Beta

If Oreo roms do not have full functionality, then I'll have to stick to Nougat!

yep.

I have been running nightlies (12/15 and updated to the 12/29 yesterday just because I was messing with something) on Lineage OS 14.1, and as far as I'm concerned, it seems as stable as a CM 'snapshot'. This is my primary phone, and I haven't had a random reboot, or any issues to speak of like I was used to with older ROMs on previous phones. I've been on it for a few weeks, finally decided it was time to unlock the bootloader and get off of the stock ROM, since the device is well past the stock OTA window.
If you recall on CM, "stable" releases were pretty rare and usually came out well after the next android version was already released. I'm planning to update maybe once a month, I don't see the need to jump on every nightly, but occasionally something interesting gets added to an update.