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.
Related
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.
UNOFFICIAL AOKP Nightly Builds​
Since AOKP development has started picking up with their addition of their new Gerrit server, I've decided to release nightly builds for AOKP. These should be released every day anywhere from 6-9pm depending on when I get time to do it. Also, some days I might not get the time. However, it should be almost every day that a new build comes out.
All credits go toward the entire AOKP team for their efforts in making one of the most customizable builds out there right now. It is absolutely fantastic.
You can download it by sorting by date uploaded right here on my goo.im profile:
http://goo.im/devs/rohan/tenderloin/aokp_nightlies
Note: These downloads are provided untested. This might break your system so be sure to keep a backup handy. Nightly builds are usually more unstable than any other type of ROM, but if you want the latest features then use this. I do not take responsibility for anything that may happen to your system.
Another note: These downloads do not come with any sort of support. Do not ask for help in IRC for aokp if you are running these nightlies. They are not official and thus are not officially supported. So don't go and give roman and the other devs a headache
And another note: They don't come with gapps, download those separately from goo.im or some other source.
You should just be able to download and install the zip in CWM, then wipe caches. Reboot and enjoy. No other wiping is needed, only caches.
Right now I am building on my personal PC (I don't have a server) so I apologize if it takes a while to get builds up! My system isn't the fastest at making builds haha
I will be making these ROMs updateable via the goo.im app probably this weekend, I don't have much time right now to figure out how it works.
If you want to find out when I release the new nightly, follow me on twitter: http://twitter.com/rohanXm
Looking forward to it!
Is there a changelog like the CM nightlies?
What exactly is aokp?
Ventus_zx said:
What exactly is aokp?
Click to expand...
Click to collapse
http://knowmydroid.com/blog/what-is-aokp-rom-how-is-it-different-from-cm9
AOKP is pretty awesome. I run it on my Epic 4G and I agree it's more customizeable than CM9 and pretty solid in terms of reliability . Thanks for these Touchpad Nightlies Rohan! Installing it as we speak!
Nburnes said:
Is there a changelog like the CM nightlies?
Click to expand...
Click to collapse
You can find what was merged here:
http://gerrit.sudoservers.com:8080/#/q/status:merged,n,z
It will display some other device stuff, though most AOKP stuff from that gerrit is for the entire AOKP as a whole and not device specific.
Can I flash the cm nightly 120 dpi patch or will it break things?
rsalinas1 said:
Can I flash the cm nightly 120 dpi patch or will it break things?
Click to expand...
Click to collapse
The only "side effect" is that you cannot access the Trebuchet settings and your build.prop values will be different leading to some funky and wrong info in your About Tablet area of your settings.
rohan32 said:
The only "side effect" is that you cannot access the Trebuchet settings and your build.prop values will be different leading to some funky and wrong info in your About Tablet area of your settings.
Click to expand...
Click to collapse
I just changed it under general ui with rom control settings. Thanks though, its very smooth so far.
Anybody else get a System UI has closed error. Weird, hopefully it was a one time thing. Flashing the 4/20 now. Hopefully that fixes it, I did a full wipe and will wipe again
Sent from my aokp_tenderloin using XDA
SUPREME Mods v1.5
Do I need to apply the SUPREME Mods v1.5 after flashing your rom or are they already applied also are you using your XENON kernel
BIGSimon said:
Do I need to apply the SUPREME Mods v1.5 after flashing your rom or are they already applied also are you using your XENON kernel
Click to expand...
Click to collapse
I would assume that the nighties don't use either of those things.
Nabobalis said:
I would assume that the nighties don't use either of those things.
Click to expand...
Click to collapse
OK thanks, just asked as both are by rohan32, will try with and without to see if any difference.
BIGSimon said:
Do I need to apply the SUPREME Mods v1.5 after flashing your rom or are they already applied also are you using your XENON kernel
Click to expand...
Click to collapse
Yup you need to reflash the Package and nope its the default Cyanogenmod Kernel.
This build is 100% AOKP "stock", as in its simply compiled from source with no changes.
rohan32 said:
Yup you need to reflash the Package and nope its the default Cyanogenmod Kernel.
This build is 100% AOKP "stock", as in its simply compiled from source with no changes.
Click to expand...
Click to collapse
The Supreme mods work fine but the xenon kernel broke my wifi (not had any wifi issues on any build) so back to cyanogen kernel and everything is working
The latest nightly (5/07) fixed my screen off/sound bug. All previous builds of AOKP had a muffled or distorted sound bug that appeared once I dimmed the screen while playing music. Bravo! I believe the fix came from the Classicnerd team, who once again prove they are contributing in remarkable ways. Bravo to them as well!
is this wifi driver included in the nightlys?
http://review.cyanogenmod.com/#/c/15570/
matteebee said:
The latest nightly (5/07) fixed my screen off/sound bug. All previous builds of AOKP had a muffled or distorted sound bug that appeared once I dimmed the screen while playing music. Bravo! I believe the fix came from the Classicnerd team, who once again prove they are contributing in remarkable ways. Bravo to them as well!
Click to expand...
Click to collapse
I tried both the 05/07 and 05/08 AOKP nightlies and the screen off/sound bug is still there just like any other ROM I have tried. Are you sure that you have the volume turned up enough?
can has new build?
Okay...I may have missed a post or two....but I am just wondering why CM9 and AOKP have both been discontinued before a stable release of CM10...
it seems kind of unusual to do stuff like that...i dunno, i'm not trying to say you guys aren't doing things right or anything...i'm just confused...
Cm9 is not discontinued.
Eyeballer's nightlies are still active.
Only some other projects stopped.
Cm10 sure still need a lot of time till it gets stable.
Powered by my IceCold 8.3 DHD
RASTAVIPER said:
Cm9 is not discontinued.
Eyeballer's nightlies are still active.
Only some other projects stopped.
Cm10 sure still need a lot of time till it gets stable.
Powered by my IceCold 8.3 DHD
Click to expand...
Click to collapse
^ This
Sam's build was just that...a build. He had it automated to sync up source, build, and provide to everyone. Eyeballer's build are still going I believe, and you can always learn to build from source. There is still code being submitted for ICS as well as JB.
gracias you guys...
like i said, i missed a couple posts and it was merely a wandering thought that i could not find an answer to...so thank you
:laugh:GAH! nevermind. browser messed up and did not load the page. Or Im an idiot. Question already answered.
I know this is a development forum,but I wanted to raise attention for the new build of CM 7 with continuous update,I like the CM 9.10 work here but I think they need more work to be ready for daily use.
so I strongly recommend the new CM 7
download:
http://get.cm/?device=legend
Any important changelog? The last 7.2 stable is quite stable
http://changelog.bbqdroid.org/#legend/cm7/next
but it is till 15/11
I am using the nightlies for some time now, from http://download.cyanogenmod.org/?type=nightly&device=legend. However, I was wondering what the changes in the last nightly are, filesize is different from previous,but changelog says No changes.
Anybody knows?
wim69 said:
I am using the nightlies for some time now, from http://download.cyanogenmod.org/?type=nightly&device=legend. However, I was wondering what the changes in the last nightly are, filesize is different from previous,but changelog says No changes.
Anybody knows?
Click to expand...
Click to collapse
This site shows more info:
http://review.cyanogenmod.org/#/q/status:merged+branch:gingerbread,n,z
Last nightly from March 1st, it's no longer building them?
There's really no more point in CM7 nightlies if no more features are going to be announced and added to CM7 legacy devices. Unfortunately, users of these devices are content with CM7 as they are or else they'd buy a more powerful device, given how it's >3 years old.
I guess the nightlies until March were meant as flexibility to those unable to run the CM7 stable series.
As much as I'd hate to say it, if you want more out of Android and custom ROMs, I guess you're going to have to upgrade.
Dear friends the account of CyanogenMod show an early source of the CM12,
hope that some one build a CM12 for us, till i get new laptop to do that.
https://github.com/CyanogenMod/android_system_core/tree/cm-12.0
https://github.com/CyanogenMod/android_vendor_cm/tree/cm-12.0
sycolon said:
Dear friends the account of CyanogenMod show an early source of the CM12,
hope that some one build a CM12 for us, till i get new laptop to do that.
https://github.com/CyanogenMod/android_system_core/tree/cm-12.0
https://github.com/CyanogenMod/android_vendor_cm/tree/cm-12.0
Click to expand...
Click to collapse
trying to build now..fetching repos at the moment. I dont think this will work out but we'll see
Edit: didnt work out. what a surprise
@hutilicious sadly that it didn't work!
sycolon said:
@hutilicious sadly that it didn't work!
Click to expand...
Click to collapse
cyanogenmod hasnt any working device specific configuration and code for yuga in cm12 at the moment.
i tried using pabx yuga.xml and TheMuppets blobs, but got errors with conflicting repos I couldnt resolve, may be due to that I have only basic knowledge about all of that.
I guess as for now, we have to wait until CM starts building nightlies (a leaked document says dez. first) or use pabx/thomas AOSP port for yuga, which can be used as a daily driver already.
@hutilicious i'm already using @pabx ASOP port
you seems to be crazy over lollipop anyway for CM12 as far as I know the popping sound will be finally be fixed it was due to qcom introducing of deep buffer, anyway as far as I know that's all but you can expect nightly before 2015