What exactly is differance between cm 6.1 and cm 6.2?
I understand building cm froyo source using git..... -b froyo but how would I go about building from nightly source?
Thanks
paperweight
you have to change the git link youre using. look on the cyanogenmod site for the right link
paperweight said:
What exactly is differance between cm 6.1 and cm 6.2?
I understand building cm froyo source using git..... -b froyo but how would I go about building from nightly source?
Thanks
paperweight
Click to expand...
Click to collapse
right now, "-b froyo" is the nightly, which I'm pretty sure is 6.2 rc1 or 2 now I think.
6.1 would be "-b froyo-stable" if I'm not mistaken.
Sounds good - All the .1's and.2's and Rc's gets a bit confusing - thanks
Related
Soo....?
I know about the nightlies... but I want the completed official CM 7 released by Cyanogen himself...
convolution said:
Soo....?
I know about the nightlies... but I want the official CM 7 released by Cyanogen himself...
Click to expand...
Click to collapse
You just broke the first rule...
The nightlies are made by Cyanogen...sigh.
Benefit of the doubt... maybe he means the completed CM7?
Well, just going by the fact that the Villain ROM is kanged from CM, I'd put my money on CM7.0.0.0 dropping first.
Sent from my HTC Vision using Tapatalk
First rule of CM is that you don't ask for ETAs.
Probably a stupid question,
But if I want to keep up to date with CM7 on the atrix, am I better off using the very occasional builds found at atrix-dev-team or using the nightlies now being hosted through Cyanogen? (is there any/much difference?)
Thanks!
lordloki77 said:
Probably a stupid question,
But if I want to keep up to date with CM7 on the atrix, am I better off using the very occasional builds found at atrix-dev-team or using the nightlies now being hosted through Cyanogen? (is there any/much difference?)
Thanks!
Click to expand...
Click to collapse
Nightlys are constantly changing stuff removed, stuff put in, some things good, somethings not so good if you're looking for the most updated and experimental go with nightlys but if you're looking for the most stable then go for betas. Thats all.
Gutterball said:
Nightlys are constantly changing stuff removed, stuff put in, some things good, somethings not so good if you're looking for the most updated and experimental go with nightlys but if you're looking for the most stable then go for betas. Thats all.
Click to expand...
Click to collapse
I should have been clearer, but you may have answered my question anyway. I recognize the general difference between autobuilt nightlies and betas -- I just wanted to make sure they were working from the same source (since atrix-dev-team and cyanogenmod aren't the same people)
thanks! (are they definitely the same source trees, just at different points?)
The way I understand it to have worked is that the atrix-dev team pushed code up into the nightly tree so the nightlies had official support for the atrix.
Whether or not the dev team push up their latest beta code is unknown. It would require them to merge changes with the nightlies which may or may not cause problems.
I'm fairly sure I've seen t0dbld state that the branches will remain separate at least for the foreseeable future.
is the nook color cm9 support going to continue? and when will it come out?
Yes support will continue. Rule number 1 of CM is NO ETA'S!!! You can download unofficial CM9 nightly builds in the dev subforum.
Sent from space
minnime007 said:
is the nook color cm9 support going to continue? and when will it come out?
Click to expand...
Click to collapse
It will be continued as nightly builds have been posted regularly.
koopakid08 said:
Yes support will continue. Rule number 1 of CM is NO ETA'S!!! You can download unofficial CM9 nightly builds in the dev subforum.
Sent from space
Click to expand...
Click to collapse
thanks, i just flashed the alpha , little buggy cant wait for official release!
Requests for ETA's can make people a little touchy.
Go to the development thread and look for the nightly builds compiled and posted by Samiam. He has a link on the first post which has his nightly builds. The devs have made some amazing progress since that alpha. I am running the nightly from a day or so ago. You'll be amazed. They are unofficial, and entirely great.
Being a total Android n00b, I just finished converting my SE X10 mini pro from stock to MiniCM-2.1.9+ nAa-11 kernel, and now I want to go on taking care of my ZTE Blade, but as far as I have seen by now, development for the ZTE Blade is quite different.
The official stable CM7 seems to be stuck at 7.1.0 since autumn, somewhere it was mentioned that nightlies have been discontinued, I could not find any info on kernel development, and progress only goes on with builds called KANGs?
Has official CM7 development shifted to CM9 only?
Can someone explain please, what KANG means?
Which CM 7.2 KANG is the current recommendation (I read about targetBSP, BurgerZ, burstlam and sej7278) and what are the differences?
You can say these as unofficial nightlies built by other people with their own small modifications but with all the official CM updates.
The names you mentioned are the one who built them
The one that i found fastest was the burstlam build but they're all pretty similar....except..targetbsp's version is more like a vanilla version meaning using all official cm updates only no extra mods etc. s
CM7 is still being developed, the only thing that stopped were the nightly builds, think it was hd failure on the server or something. CyanogenMod recently took donations for new servers, so they should be back up & running soon.
KANGs are just versions built from CM7 source, but not by CyanogenMod. There isn't much real development going on with them. They're just more recent because the CM7 nightly builds stopped months ago.
wbaw said:
CM7 is still being developed, the only thing that stopped were the nightly builds, think it was hd failure on the server or something. CyanogenMod recently took donations for new servers, so they should be back up & running soon.
KANGs are just versions built from CM7 source, but not by CyanogenMod. There isn't much real development going on with them. They're just more recent because the CM7 nightly builds stopped months ago.
Click to expand...
Click to collapse
great information included in this post had no idea that the cyanogen servers had some problems thanks for the information mate
Master One said:
Being a total Android n00b, I just finished converting my SE X10 mini pro from stock to MiniCM-2.1.9+ nAa-11 kernel, and now I want to go on taking care of my ZTE Blade, but as far as I have seen by now, development for the ZTE Blade is quite different.
The official stable CM7 seems to be stuck at 7.1.0 since autumn, somewhere it was mentioned that nightlies have been discontinued, I could not find any info on kernel development, and progress only goes on with builds called KANGs?
Has official CM7 development shifted to CM9 only?
Can someone explain please, what KANG means?
Which CM 7.2 KANG is the current recommendation (I read about targetBSP, BurgerZ, burstlam and sej7278) and what are the differences?
Click to expand...
Click to collapse
Go for Burstlam's build. Has good options for UI customisation and also has lesser battery consumption.
Sent from my Blade using XDA app
I have built ICS for a while now with no issue.
I needed to build 7.2 but when I built the gingerbread branch, it has only 7 in the title and modversion. I also tried gb-release-7.2 but it has the same issue.
I do know that the gingerbread branch wasn't 7.2 final, because the patch I made didn't port to the 7.2 Final build I downloaded from CM.
I even reverted the commits since Final was released, with no luck.
It is possible that gb-release-7.2 is correct, I suppose, but the fact that the build.prop and the ROM name are simply 7 has me second guessing that.
I almost just asked mgr666 in his thread, but I know he is pretty adamant about staying on-topic.
Anyone know how to do this? A google search shows people claiming that building the gingerbread branch builds 7.2, but I have had no luck building a ROM that corresponds with the official released Final from Cyanogen.
mateorod said:
I have built ICS for a while now with no issue.
I needed to build 7.2 but when I built the gingerbread branch, it has only 7 in the title and modversion. I also tried gb-release-7.2 but it has the same issue.
I do know that the gingerbread branch wasn't 7.2 final, because the patch I made didn't port to the 7.2 Final build I downloaded from CM.
I even reverted the commits since Final was released, with no luck.
It is possible that gb-release-7.2 is correct, I suppose, but the fact that the build.prop and the ROM name are simply 7 has me second guessing that.
I almost just asked mgr666 in his thread, but I know he is pretty adamant about staying on-topic.
Anyone know how to do this? A google search shows people claiming that building the gingerbread branch builds 7.2, but I have had no luck building a ROM that corresponds with the official released Final from Cyanogen.
Click to expand...
Click to collapse
Mateorod, I successfully built a 7.2 nightly in late April, but have not tried to build one since. It was a 7.2 nightly and I flashed it and it ran. I did something that was probably not necessary, I just started over with an android/system2 folder and set it up for gingerbread. I repo synced the whole branch again so it used another several GB of my hard drive. Then I was able to setup the env and brunch encore.
I just looked at the build.prop in the zip and it says CyanogenMod-7.2.0-RC1-encore-UNOFFICIAL. And I am sure it will not say 7.2 Final (or stable). It will just be another nightly (unofficial, as the call them now instead of kang).
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
Mateorod, I successfully built a 7.2 nightly in late April, but have not tried to build one since. It was a 7.2 nightly and I flashed it and it ran. I did something that was probably not necessary, I just started over with an android/system2 folder and set it up for gingerbread. I repo synced the whole branch again so it used another several GB of my hard drive. Then I was able to setup the env and brunch encore.
I just looked at the build.prop in the zip and it says CyanogenMod-7.2.0-RC1-encore-UNOFFICIAL. And I am sure it will not say 7.2 Final (or stable). It will just be another nightly (unofficial, as the call them now instead of kang).
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
Yeah, I did the same thing. I figured I could probably just switch to a branch, but I figured why bother being unsure. So I have a whole separate gingerbread source on my hard drive.
Basically, I did exactly what you describe. Searching the forums, here and for other devices, I have seen others with the same issue, some of them reporting switches between release candidates with no idea why. I never found any discrete solution.
I am sure it is my inexperience with git biting me in the butt again, but it hasn't come out right yet. I have clobbered, repo synced again, all that.
It does for sure appear to be just another nightly, but of CM7, not 7.2.
Like I said, I have checked it against final, and they are for sure not the same. This does not in and of itself mean much, I guess, but I did try and revert any commits since the Final came out.
The build prop and the modversion ONLY say 7.
I just booted to Ubuntu and repo synced system2, built the env, made clean, brunched encore. It built a zip with exactly the same build.prop name (7.2 RC1)
Sent from my Nook Color running ICS and Tapatalk
Right?
I tried make clobber in between a couple of my attempts. I have seen others complain of random RC switches as well.
There IS a way this is done. I just haven't figured out what it is.
Thanks for going through the trouble of building, Lar.