Anyone know what is different between CM9 nightlies and CM tenderloin ROM ?
Note: still waiting for TP Mic working with ICS !
Dont quote me on it...
But tenderloin is the name of kernel source for HP Touchpad...so every rom will have that word in it as everyone is using CM's kernel....
Difference between nightly and the rom is that....devs picks small fixes and stuff from many palces and includes them in the nightlies...when bunch of nightlies reaches a point where they make difference..they are converted into the next release of the rom...
All of these ROMs are based off of Ice Cream Sandwich. Each developer(s) put their own stuff on it though. For instance, I am using the AOKP ROM and it has a lot more customization options than CM9. Other than that, they are pretty much the same.
Nightlies are releases usually every night, and contain small fixes that were worked on that day. However, there can also be many more bugs than stable (alpha/beta) releases.
Related
Just one caveat: I have done searches (read: multiple).
How in the world does CyanogenMod get to all of the supported devices? All of a sudden once CM9 is released, for phones/tablets moving from CM7 to 9, does it go out to all devices or what? Does it need to get ported from the source for each and every individual device? In general, how is CM updated and how does it get out to the officially supported phones/tablets?
Cyanogenmod ROMs do indeed have to be ported to each individual device and maintained. Once a device receives official support from the Cyanogenmod team, daily changes made to the AOSP source code (tweaks and bugfixes by the various contributing devs) are automatically compiled by a "buildbot" and released at the end of each day (thus these builds are called "nightlies"). These nightly updates are then made available for download through the Cyanogenmod website and through ROM Manager. Once code updates reach a certain plateau, a "final release"-worthy balance of features and stability, the build is released separately as a "stable" build (such as CM7.1), though you can still download it from the website or from ROM Manager just as with the nightlies. CM9 will eventually receive the same treatment and be released in the form of nightlies and stable builds.
Further (highly recommended) reading can be found here: http://www.cyanogenmod.com/blog/the-current-and-future-state-of-cyanogenmod-nightlies
Has anyone seen John Connor?
so the nightlies don't have to be ported, but every major revision does?
hugabu said:
so the nightlies don't have to be ported, but every major revision does?
Click to expand...
Click to collapse
No.
"Porting" is just a word used for the process of making the rom work on any certain device.
So to answer your question, once the work of porting CM to the certain device is done, that port is used as the base for both the stable and nightly builds.
Look at the analogy of when a new phone comes out, case manufacturers create a mold to use to make their cases fit the certain phone, and that mold is used to make all kinds of cases. Same concept
Okay so while everyone is looking out for Cyanogenmod 9, I'm still wondering about CM7...
Simple question, if there is already a stable build, what are the purpose of the Nightly builds? In the link http://www.cyanogenmod.com/devices/samsung-galaxy-s2 you can select between, Stable, Experimental and Nightly builds. Why would one choose a Nightly build over the Stable build?
Because a nightly is the latest version of the rom. But it is likely to have more bugs then the stable.
For our device there is no CM build labeled as stable. But the nightly builds are stable for daily use.
Can you still follow me? It's just how the rom is labeled.
Lennyz1988 said:
Because a nightly is the latest version of the rom. But it is likely to have more bugs then the stable.
For our device there is no CM build labeled as stable. But the nightly builds are stable for daily use.
Can you still follow me? It's just how the rom is labeled.
Click to expand...
Click to collapse
That's not entirely true, there is a build labeled "stable", here.
However, it's an old build, and you would be better off using a more recent build. I would go as far as recommending a kang build, because the latest nightly is also old. There will be no more nighties for CM7, because CM9 should arrive... in the near future.
The latest semi-official kang, built by codeworkx, is here.
I'm using Novek's build without problems (it contains more recent commits than codeworkx's), which you can download here.
You guys are aware right that Erik Hardesty a.k.a. dalingrin is wokring on ICS for touchpad and has promised (citation needed) to deliver before CM9? Now, I want to know if he indeed delivers, then will his work to taken to make the CM9 build faster and then will he be included in the official CM team. I am asking this because I have a Moto Defy and before CM7, Quarx, Epsylon and others compiled it and I think they are now in the CM team. Just curious on how it works.
He is already a part of the CM team, he is the CM maintainer for the Nook Color.
That's news.. well for me! But if there is someone else in his place who is ot in the CM team then what happens?
abhi.eternal said:
That's news.. well for me! But if there is someone else in his place who is ot in the CM team then what happens?
Click to expand...
Click to collapse
Then its not a CM9 build. Basically the CM team are a bunch of developers on different devices. In the case of ICS each developer will build their versions and it will be pushed and integrated into the CM9 list when CM9 is ready to launch. However, in the case where a CM team member's build is ready to be tested before CM9 is ready then they will most likely post them as a under a different title because its not integrated as a CM9 device yet.
In the case that another developer releases an AOSP ROM into the wild then he can do whatever he wants with it and it has nothing to do with the Cyanogenmod team whatsoever.
Samsung Galaxy S Captivate ICS CM9, Glitch Kernel | HP TouchPad CM7 Xron Beta 2.9.1
@iamsamsamiam: I get your point but if that is the case then how come Quarx and Epsylon (for Motorola Defy) are in the official CM team now (I think they are [citation needed!]). If you are not aware, CM7 had no love for Defy for a very long time and that gap was filled by Quarx at first. Afterwards, when we had a almost complete working rom based on CM7, these devs were included in the official list. I just want to know is this how it happens?
abhi.eternal said:
@iamsamsamiam: I get your point but if that is the case then how come Quarx and Epsylon (for Motorola Defy) are in the official CM team now (I think they are [citation needed!]). If you are not aware, CM7 had no love for Defy for a very long time and that gap was filled by Quarx at first. Afterwards, when we had a almost complete working rom based on CM7, these devs were included in the official list. I just want to know is this how it happens?
Click to expand...
Click to collapse
And there are still a ton of devices out there without any Cyanogenmod ROM at all. I guess its more like a developer who wants to code for a particular device and wants to put a CM flavour to the ROM and gets permissions from the CM team to use it and builds a CM ROM and I guess they would become part of the team as a de facto point since they continue to support their build. Remember there are a ton of other ROM developers out there that don't use a CM base and does things their own way.
Cyanogenmod isn't always going to be the "best" ROM out there for every device, but they're trying to support many devices out there. The devices that get support are reflected upon the community and the more popular the phone the larger the community. And developers come out of said communities and maybe one of those developers wants to make it into a CM build.
Samsung Galaxy S Captivate ICS CM9, Glitch Kernel | HP TouchPad CM7 Xron Beta 2.9.1
That made sense!
what's the difference between the cm in http://get.cm/?device=olympus and http://forum.xda-developers.com/showthread.php?t=1257574 (Ba2tF) ??
and how the nightly stoped at november? is it Ba2tF something final?
kossel said:
what's the difference between the cm in http://get.cm/?device=olympus and http://forum.xda-developers.com/showthread.php?t=1257574 (Ba2tF) ??
and how the nightly stoped at november? is it Ba2tF something final?
Click to expand...
Click to collapse
Ba2tf is a beta release by the Atrix dev. team, who originally ported CM7 to the Atrix; it includes Atrix specific fixes from the previous beta release.
The nightlys are released by the CyagonMod dev. team, based off of the work provided by the Atrix dev. team. The nightly updates include fixes, new test build ideas, etc. that have to do with CM7 in general, and may or may not include specific updates for the Olympus (aka the Atrix).
The nightlys and also the Atrix dev team beta builds have been suspended more or less, due to the fact that most of the members of both dev teams are allocating their resources towards working on getting CM9 out. Last estimate I herd of a release candidate for CM9 was something like April???
There are also weekly builds released by the Atrix dev. team (see corresponding thread in dev. section). These are kind of alike nightlys (except that they are weeklys ) released by the Atrix dev. team to try out fixes, new things, etc.
The most stable of the three choices you have to choose from is probably the beta build by the Atrix dev team (Ba2tf). Although, I've been using the most recent nightly for the last month or two and have had no problems. The most recent weekly has incorporated the fingerprint scanner into it.
If I have gotten any of the above info. incorrect, please feel free to correct me anyone.
thanks for the very thorough summary.
wow thank you very much! you have cleared all my doubts and even questions that I wanted to post later lol
This helped clear up a bunch of confusion for me - thank you
I have time and I like building ROMs, but I have a problem, there are a lot of roms and limited storage in my computer. So I can build at least 6 different roms.
I already have Resurrection Remix(CMbased), AOKP(wont boot, for now, when they used some CM stuff like KK may work), BlissPop(finish download of sources as I'm writing this), OMNI(the same as AOKP), DU(I'll download it tonight), SOKP(I don't know anything about this rom in LP, but in KK was very good) and PAC(to build UMTS).
These is what I have now(I know I say 6 different roms and I have 7 ), roms CMBased is easy and only use 2/3 GB on my Computer but for example DU and AOKP are AOSP based so this roms may work because all the parts of the rom are directly from Google and don't have any modifications like CM does to make it compatible with our device, some things I can do to make it work like AOKP KK, but LP is starting and every version 5.0, 5.0.2, 5.1.0 have a lot of changes between versions and Google does not give time for developers to make enough changes to achieve a stable version, so I don't have any base to use or pick changes.
Only told me what rom do you want and I see what can I do
Regards and sorry for the inconvenience.
I heard that BlissPop is good and I want to try it but I also like what you did with RR and Aokp...
I don't know,maybe the best thing would be to make one but awesome rom!
I'll be happy with your decision :thumbup:
Sent from my Razr XT910
I'll try anything based on AOSP. Since you are having problems with AOKP, I will try DU and Omni... Thanks, @tonyt.!