I am running the RC2 and I came from Fresh 4.2 where the updates show in the Fresh Updater, However in the Synerfy one it only shows one download. My question is how do you get the nightlies for RC2. Im not a noob just normally either went to Freshes website and checked or read the forums, just little confused with the new rom?
For the most part, Myn offers nightlies prior to a release candidate (RC) and while still is beta form. He rarely, if ever, offer nightly builds afterward reaching RC status.
Posting & replying from my EVO 4G
I don't think there are nightlies to it. The Synergy Kingdom nightlies are based off something completely different.
Related
Ok sorry if this question is noobish but what is the difference?
They are both cyanogenmods but two different Download Thread.
Nightly's are not offically released by Cyanogen and RC's are, but they are both compiled by the same team. Plus RC's are considered stable enough for official release.
Sent from my HTC Vision using XDA App
Nightlies are what CM7 RC1 is based off of. It essentially IS one of the nightlies. The nightlies are automatically built by a bot every night at the same time so that all the changes made that day are packaged into a rom and that is what becomes the next nightly.
The nightlies will continue to be built becauase RC1 means release candidate and is not considered stable.
They will eventually release an official CM7 Stable.
G1ForFun said:
Nightlies are what CM7 RC1 is based off of. It essentially IS one of the nightlies. The nightlies are automatically built by a bot every night at the same time so that all the changes made that day are packaged into a rom and that is what becomes the next nightly.
The nightlies will continue to be built becauase RC1 means release candidate and is not considered stable.
They will eventually release an official CM7 Stable.
Click to expand...
Click to collapse
LOL "Built by a Bot Every Night" You made it sound so leet lol. I always it was some dude who just updates it and put it on.
But thanks. I am using RC1 right now everything is working so far. My last nightly was giving me reboot when i open my keyboard.
Also, you can always continue to flash the next versions of nightlies over the RC1, as other improvements and changes are made.
martonikaj said:
Also, you can always continue to flash the next versions of nightlies over the RC1, as other improvements and changes are made.
Click to expand...
Click to collapse
So the nightlies folowing an RC are based on the RC or on the previous nightly?
ok so i have been using the cm7 rc1 rom for about 2 hours. i find it amazing since this is the first cyanogen anything i have flashed. but then after about 30 min i found there is no 4g so i did some searching and seen people using 4g on rc1 but i haven't seen anything related to how they got it. so what i am trying to figure out is how did they get it? because the only gb roms i have seen with 4g are salvage and the gginggerbread 6 rom
RC1 does not have wimax. The latest cyanogen nightlies released after RC1 have it working. Download the ones that say supersonic here:
http://mirror.teamdouche.net/?type=nightly
I have 8 installed and am going to flash 12. Wimax works great.
thanks. i had no idea they kept up with the nightlys after the rc's. im still pretty new to all this
Is there an advantage of flashing cyanogenmod 7.0.3.1 if I am using nightly 64? Is it that more stable? Are the bug fixes noticeable? Or I might just wait until the 2.3.4 update...
I would say that really depends on your flashing habits. Do you usually flash nightlies when they come out? If you're just going to flash a new nightly when it releases then you probably shouldn't bother, but if you plan to stay on 7.0.3.1 for a while, then you may as well use it in case there were any small issues in the nightly that were fixed.
The nightlies (even the one that came out a few days) are basically newer than 7.0.3.1. 7.0.3.1 is a bug fix, but the nightlies are working towards 7.1. The question is whether you want to be running a "stable" build (7.0.3.1) or a dev build of the next version. That's your call.
You actually can't go from the nightlies to 7.0.3.1 without wiping data, as it's a downgrade.
MMS hasn't worked since at least #62, FWIW.
Telperion said:
MMS hasn't worked since at least #62, FWIW.
Click to expand...
Click to collapse
MMS works for me on nightly 64...sent a picture today to confirm it.
Sending works, receiving doesn't. Message fails to download.
stable is andoird 2.3.3. stable. nightly 64 is android 2.3.4. no mms download. not too stable. but if you don't donwload mms all the time, and don't mind asking "could you email it instead" then go right ahead and flahs the newest nightly.
Hey!
I want to put CM rom on my gf's wildfire and i didn't find anywhere the difference between the regular and the nightly version... can someone explain it to me?
Nightlies are experimental versions, which may be better than the stable, but, it may sometimes also have bugs not present in the stable. The building of nightlies is a continuous process, with a new nightly released everyday.
Another difference is that you do not get "official" support on the CM Bug tracker for nightlies, but, this is available for RC / Stable versions.
For your gf's phone, I would probably recommend you go with the stable.
thank you for your help!
stable is better for father, i think
I am a long-time user of CyanogenMod since I learned the beauty of rooting and flashing my HTC Hero years ago. But over the years of enjoying the benefits of running nightlies, I've always been nagged by the occasional build that is broken or buggy.
As a general poll question, what is the best method(s) of determining whether a nightly is stable for ROMs such as CyanogenMod, PAC-MAN, etc?
Do you have a favorite changelog, ROM rating website, or XDA thread that you reference before you flash that shiny-new build every morning?
Generally I would just check the threads to see what the flashers are saying. Or ask how it's gone for people. Usually if they have a bad experience with the nightly they'll post about it saying that they had to nandroid back to another build, or do so and so fix to get something working right.