There is a new site now to check the changes in different nightlies of CM7 and CM9. Go check it out.
http://changelog.bbqdroid.org/
Already knew, thanks for informing others
Is there more than one CM9 rom in development for P500 or just the one?
Related
I saw there are cm7 roms in the development forum for atrix, but in cm site the atrix is not on the list of "devices".
checked the nightly build last one was november.
does this mean cm in the forum which supports atrix, is not official one?
kossel said:
I saw there are cm7 roms in the development forum for atrix, but in cm site the atrix is not on the list of "devices".
checked the nightly build last one was november.
does this mean cm in the forum which supports atrix, is not official one?
Click to expand...
Click to collapse
It is officially part of CM tree, officially supported as in just the development. No "Final" or "Stable" version that has everything working, therefore it is not on the official page. But that will come in time.
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
There is a new site now to check the changes in different nightlies of CM7 and CM9. Go check it out.
http://changelog.bbqdroid.org/
thanks for the advertising, but this was already said on another post.
original thread : http://forum.xda-developers.com/showthread.php?t=1667390
What does it take for a ROM to move from unofficial to official or is that not how it works? For example, I run cm11 official because its official. I would like to run cm12 but it says unofficial.
Sent from my LG-VS985 using XDA Free mobile app
Someone can correct me if I'm wrong.. But... Unofficial is usually when someone compiles the build themselves and share. They sometimes add commits that have not been merged into official builds. Sometimes add add-ons that may not be supported in official builds. Sometimes a dev team may not have a maintainer for a specific official build. Most times unofficial builds aren't always as dependant as official. Sometimes they can be better.
As for CM 12. It went official last night. They are nightly builds, but they are official now. The thread is in the original development section. You can go to the CM site and it shows all the official 11 builds and then starting with 1/6 it is now on official 12 nightly. Hope that helps. ?
Just to clarify. The official CM11 thread is where to go for more info right now. Sure they will probably start a new one soon, but the link still takes you to CM and the latest build is the CM 12 from today 1/6. http://download.cyanogenmod.org/?device=vs985&type=nightly