I dont iunderstan diffoerence between nightly ,stable or rc.
Any suggestions
Sent from my ZTE-BLADE using Tapatalk
A nightly is a build done automatically every night that includes all that day's changes, they aren't tested & could contain bugs, but you get the latest features.
A release candidate is a testing version, released to see if there are any bugs before it goes stable. If bugs are found then they're fixed & another release candidate is produced.
A stable release is when all the major bugs have been worked out of the release candidates, often it's the same as the last release candidate version.
Related
probably a stupid question but i see cm roms update frequently with their being a new base, what does the new base improve in the rom
marc187 said:
probably a stupid question but i see cm roms update frequently with their being a new base, what does the new base improve in the rom
Click to expand...
Click to collapse
CM is constantly updating its code for various OS fixes every few days. You can either use nightly builds (the name comes from the fact that for open source code people would upload their code during at night and the resulting amalgam would come out as "new" code but often unrefined so it would be less stable)
or go with the latest stable builds with minor updates to the code.
I want to build a stable 4.4.2 omni, but omni codes in github had updated to 4.4.4, and I do not know how to roll back.
In CM, there is always a build-manifest.xml in its rom and I can easily roll back to the status defined by build-manifest.xml (http://wiki.cyanogenmod.org/w/Doc:_Using_local_manifests#The_local_manifest).
Then I wonder how can I get the xml file to obtain the same repos as you guys in a stable release?
New CyanogenMod 13 snapshot build (ZNH5Y) is rolling out.
The Android ROM community isn't quite as active as it was a few years ago with Android itself becoming more feature-rich. Still, CyanogenMod is chugging along with support for a ton of devices and a reasonably fast update cycle. A new snapshot build of the Marshmallow-based CyanogenMod 13 is now official (ZNH5Y), and it will be available on the first wave of devices today.
This is a snapshot build, meaning it's the most stable build of CM you can get. Of particular note, this version of CM will include all security patches up through the August bulletin. Build ZNH5Y also includes fixes for several of the recently reported Quadrooter kernel vulnerabilities. Two of the vulnerabilities aren't accessible to the CM team, so those patches need to come from further up the chain.
If you're running the ZNH0E snapshot build, you can flash the new one on top of it. ROMs for various devices will roll out as they are ready. Today, you can expect downloads for popular devices from OEMs like OnePlus, Samsung, and Motorola, as well as most Nexus devices. The full list is available on CM's blog post, but they're all code names.
Source: http://www.androidpolice.com/2016/08/15/new-cyanogenmod-13-snapshot-build-znh5y-rolling/
CM 13.0 Release – ZNH5Y - http://www.cyanogenmod.org/blog/cm-13-0-release-znh5y
Full changelog: http://pastebin.com/ptatg6kh
cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon.zip
Link - http://download.cyanogenmod.org/get/jenkins/174518/cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon.zip
Which is better / newer ? This on ore this one cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b ?
Thanks in advance
EDIT: I discovered what is difference, this one is cyanogenmod the other one is cyanogenOs, i got wrong with the filename.
I get reboots every time I receive a phone call with clean install and the latest stock opengapps. Works fine without opengapps, now trying to get it to work without the google dialer.
Edit: ok I looked into it, I never had to do this on recent cm13 nightlies but it's necessary to set dialer as default app for phonecalls.
Spaghetti-XRY said:
Which is better / newer ? This on ore this one cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b ?
Thanks in advance
EDIT: I discovered what is difference, this one is cyanogenmod the other one is cyanogenOs, i got wrong with the filename.
Click to expand...
Click to collapse
Your are trying to compare CM with COS?
I am the proud owner of two Oneplus One devices. (TWRP 3.0.2.0)
Just dirty flashed cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon on top of the previous Snapshot version on my two devices.
DDR is wiped perfectly.
Flash process well documented (log on screen)
After Flash, do a wipe of Cache / dalvik (just to be sure)
That's all. Works well, no issues.
Again, a nice job of Cyanogen.Mod... (Some may not like them, but I (and my devices) do like them)
hay guys
I have to format and update my moms phone it is running CM 13 since I gave it to her. I need a good stable rom to update her phone do you guys have any suggesions
msfrox said:
hay guys
I have to format and update my moms phone it is running CM 13 since I gave it to her. I need a good stable rom to update her phone do you guys have any suggesions
Click to expand...
Click to collapse
Try MOKEE rom (History)...
https://download.mokeedev.com/?device=wt88047
What's the difference between history and release
msfrox said:
What's the difference between history and release
Click to expand...
Click to collapse
RELEASE: Tested after integrating new features, more stable than NIGHTLY. (Odexed builds)
NIGHTLY: Built daily with newest code and experimental features, might contain undiscovered bugs. (Deodexded builds)
HISTORY: Final odexded builds once a newer Android version is out and being built.
EXPERIMENTAL: Released when a new device is added or when a new feature is added for public beta testing and feedback. (Deodexded builds)
UNOFFICIAL: Maintained separately by individual developers, usually involves modification of shared code which cannot be merged (affects other devices), therefore maintained by the developer himself.
Nice thanks
History means stablest
I have seen from the screenshot of the latest beta build. The build name has changed to opr1 instead of Tissot in the first beta build.. also new to posting threads on xda I don't know how to attach photos so wasn't able to attach one ....
Starting with Oreo, individual builds are identified with a new build ID format, in the form of PVBB.YYMMDD.bbb.
The P part represents the first letter of the code name of the platform release, e.g. O is Oreo.
The V part represents a supported vertical. By convention, 'P' represents the primary platform branch.
The BB part represents a alpha numeric code which allows Google to identify the exact code branch that the build was made from.
Click to expand...
Click to collapse
https://source.android.com/setup/build-numbers
So OPR1 means it's an Oreo build, primary platform branch, built from code branch r1.
r1 could be Release Candidate 1, which suggests that Stable is near.
Nevermind, it means it's based on Google's first stable release of Oreo. Like developer previews are D1, D2 etc., and .1 version bumps are M1, M2.. etc
So OPR1 means it's an Oreo build, primary platform branch, built from code branch r1.
r1 could be Release Candidate 1, which suggests that Stable is near.
Nevermind, it means it's based on Google's first stable release of Oreo. Like developer previews are D1, D2 etc., and .1 version bumps are M1, M2.. etc[/QUOTE]
Hmm ... This sure explains it well and Thanku