Hi..
I Have a nexus one. My question is regarding the CyanogenMod Nighty and stable. whats the difference? Which one should i use? Which is better?
Thanks.
Nightly build = Work-in-Progress version. You can try new features, but it can be buggy and less stable. Besides, there's no support provided officially.
Stable = The 'Official' version.
great
Thanks a bunch, helped me out
FYI, the nightlies will also be the first to get major bugfixes like the wonk. That has been in the nightlies for almost a week, and they are still working on updating the stable to 7.0.4 to include it. The nightlies have also been running 2.3.4 for a couple of weeks, which was nice when the big security flaw came out that affected all versions except for 2.3.4.
Nightlies usually end up still being "stable", they just don't have any labels next to it, although occasionally there have been issues that will crop up that are usually resolved the next nightly (like earlier this week, a nightly caused the alarm app to FC whenever someone tried to set an alarm, this was resolved in the next release).
I usually stay behind on the releases, as I need my phone to be running and able to do the functions that I need. This way I can read what others are experiencing and see if it is worth upgrading to. Currently I am on #76 and I think #80 was just released.
Also, "stables" aren't always stables (which is the case in most programs). Just like with Windows, there are updates that need to be put out when security holes or major bugs are patched. But the smaller bugs will usually get fixed in the nightlies long before they ever make it to the stable.
Overall, I love the nightlies. I don't think I could go back to a stable build.
bassmadrigal said:
FYI, the nightlies will also be the first to get major bugfixes like the wonk. That has been in the nightlies for almost a week, and they are still working on updating the stable to 7.0.4 to include it. The nightlies have also been running 2.3.4 for a couple of weeks, which was nice when the big security flaw came out that affected all versions except for 2.3.4.
Nightlies usually end up still being "stable", they just don't have any labels next to it, although occasionally there have been issues that will crop up that are usually resolved the next nightly (like earlier this week, a nightly caused the alarm app to FC whenever someone tried to set an alarm, this was resolved in the next release).
I usually stay behind on the releases, as I need my phone to be running and able to do the functions that I need. This way I can read what others are experiencing and see if it is worth upgrading to. Currently I am on #76 and I think #80 was just released.
Also, "stables" aren't always stables (which is the case in most programs). Just like with Windows, there are updates that need to be put out when security holes or major bugs are patched. But the smaller bugs will usually get fixed in the nightlies long before they ever make it to the stable.
Overall, I love the nightlies. I don't think I could go back to a stable build.
Click to expand...
Click to collapse
I just checked the website and for the nighty it has #81. I understand the part of updating at night. My question is like how u said that you are on #76, so do you have to manually change to #81(by flashing and making a backup) or it automatically updates? Am confused.
You manually update like you would a normal release of CyanogenMod. If you have the premium version of ROM Manager, it can notify you of new nightlies and you can download them through it. If you don't have it, you would manually have to download the files from http://mirror.teamdouche.net.
And I ALWAYS recommend making a backup. That way, if one of the nightlies you install is all screwed up, you just revert to the last one and wait until it is fixed bfore you flash the next verison.
You don't really have to wipe when going to the next nightly. Just flash and all your data is in tact, just like a regular upgrade.
I suggest going with the latest nightly.
Related
I see in the Dev forum that the first RC1 of Cyanogenmod 7 for Milestone is available, but when I go to download it here, it doesn't seem to be available. I guess it would be called update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip but that last one available was the 11.02.15 release. Does anyone know whether the RC1-7.0.0-11.02.18 has been withdrawn for some reason?
I've been testing each and every build with good success, so I'm really keen to try the new one. I would ask in the dev forum, but I'm relatively new at the XDA forum and am therefore not eligible to post in it.
SF
Well, I eventually found the correct download link at https://github.com/downloads/nadlabak/android/update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip
Thanks,
SF
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
I would stick with cm6 for now. CM7 could use many improvements and as of now is very memory hungry (I was on the feb.10 release). CM7, however, has many bug fixes that are not implemented in cm6, for example, the wifi fix (wasn't working with some n routers before I think [depending on the security type or something] ) and it seems as though there is also the random freeze + random reboot fix (using another, older kernel) I would not switch to CM7, until many bugs are fixed. Also some games don't work.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
It's great. But video playing not working for me.
So I installed CM7 to try it out, and on RC1 my videos play fine (widescreen) using the included "Video" app. Well most of them do, one of them is displayed 4:3 for some reason?
I'm finding that it works quite well. Battery life is good, but there are a few bugs that need working out. CM6 is probably better if you need your phone to be 100% reliable, but I like to push the boundaries and play around.
Bugs or missing features so far:
- Button lights and keyboard backlight not working properly for me (and at least one other user here)
- Auto backlight brightness not working for me at all
- Volume button swapping/remapping not yet implemented, so that in lanscape mode left means louder (which is the wrong way round for me)
- Memory usage is a problem, so that Launcher pro keeps having to re-initialise
- Camera is VERY unreliable
- Getting random reboots and lockups, especially in Google Maps
Still, things are getting better with every release and I can always go back to CM6 if I want, since I made a Nandroid backup in OpenRecovery before I installed the CM7 update. I've just installed the RC2 update, so lets see how that goes...
SF
I've been running CM7.0.3 for several months now. I have it installed on uSD card.
What are the top reasons to upgrade (any big new features, or any NookColor specific improvements)? Should I go with CM7.1RC or a more recent nightly, if so, which? I really don't want to go through several iterations of trying to find a reliable nightly. So if you have been stuck on one for a couple weeks, which is it?
I'd just like to update to something more recent, but still reliable. I've read about Sleep Of Death... want to avoid those kinds of hassles.
I tried searching but can't find what I am after.
Thanks!
Newer versions are more stable, seem to have most if not all features working, and has the overclock kernel built in.
I was on 7.1RC1 for a long time, and had no issues. Now I've been on Nightly 176 for a few weeks, no problems with it at all either.
You should probably upgrade your size-agnostic installer to 1.3.
I don't know if 7.0.3 had the new kernel or not, but going from 7.0.2 to latest nightly increased battery life at least 3 times. No kidding.
Recent nightly would be the way to go. Big fixes include deep sleep witch gives a major battery increase, overclock kernel included, and tons of other stuff I can't think of right now.
To prevent SoD set up two profiles in tasker one for wifi on with screen on and wifi off with screen off.
Sent from my NookColor using Tapatalk
I just purchased a Nook Color from Ebay, and after
I initially followed several posts about creating a bootable SD card to test an alternate OS. The instructions were straight forward, and I was able to quickly create a boot SD. I booted, and things worked, but because my several Kingston MicroSD cards obviously have poor throughput, the performance on the NC was excruciatingly slow and rife with Force Close errors.
So instead of dropping more cash on a more compatible SD card, I decided to just install directly to the EMMC.
I installed the CM9 nightly, (yes, I like living on the bleeding edge) and I must say that I'm impressed. It is a bit sluggish at times, and the touch screen response and accuracy could be better, but overall, I'm pleased. I may revert back to a stable version of CM7 just to compare performance, but until then, I'm quite happy with the results.
Oh, and I set up my DROID Bionic as a WiFi Hotspot, and the NC connects to the Internet without any issue. Very nice!
Sounds like you're doing well.
I was a long term CM7 Nook user and got good value out of that, but switched to CM9 a couple of weeks ago.
Yes, I have lost a few things and the performance / touch response was a little better, but I am sticking with CM9 as it is significantly nicer to use and improving all the time.
Make sure you are over-clocked to 1200 and using Interactive governor to get the best out of it.
CM9
I have tested several nightlies of MC9,I love it except for two big problems
1.Touchscreen is not very responsive
2.Streaming video like Hulu,Netflix,HBO Go and internet TV do not work
So I keep going back to CM7.
Have you also noticed that you sometimes have to touch above and to the right of an icon to get it to work correctly?
It drove me crazy until I figured that one out.
Wow! Those are the EXACT issues I ran into. And so I decided to go back to the stable release of CM7. Performance is like night and day. I can't believe how fast CM7 is in comparison to CM9.
My only real complaint of CM7 is that many apps don't recognize it as a "tablet" so apps tend to look like they do on my DROID Bionic, just in higher resolution. I'm not seeing many apps that display tablet-specific display elements. Not a big deal but kinda disappointing.
I'm not giving up on CM9, though. I may try the dailies every few weeks or so to see how things have improved.
I'm using the "official stable" release of CM7. Has anyone have any good experience with the recent MiRAGE CM7 releases? I tried one from a couple days ago, and had problems connecting to the Market.
I am have those issues as well. However, I am going to stick it a bit longer with cm9 as the nook is not my primary tablet.
Sent from my Xoom using xda premium
Jim Barr said:
Wow! Those are the EXACT issues I ran into. And so I decided to go back to the stable release of CM7. Performance is like night and day. I can't believe how fast CM7 is in comparison to CM9.
My only real complaint of CM7 is that many apps don't recognize it as a "tablet" so apps tend to look like they do on my DROID Bionic, just in higher resolution. I'm not seeing many apps that display tablet-specific display elements. Not a big deal but kinda disappointing.
I'm not giving up on CM9, though. I may try the dailies every few weeks or so to see how things have improved.
I'm using the "official stable" release of CM7. Has anyone have any good experience with the recent MiRAGE CM7 releases? I tried one from a couple days ago, and had problems connecting to the Market.
Click to expand...
Click to collapse
I LOVE Mirage! It is so much faster than stock CM7.1.
FWIW CM9 seemed sluggish om my OC'd NC until I accidentally forced another reboot by running the battery down. The animations seemed smoother after that. It may just be perception though, as I wasn't really looking for it.
Installing using ROM Manager?
HI all,
I downloaded the CM9 nightly to update my Nook Color, which is currently running one of the CM7 nightlies, but an a little unsure on how to actually it. Are you using ROM Manager to install the updated ROM?
Currently running Rom Manager 5.0.0.6, which has Clockworks Mod Recovery 3.2.0.1 flashed.
And correct me if I'm wrong. This does include a kernel, right? I'm assuming I cannot run the 2.6.32.9 kernel I'm currently using in CM7 with this.
Later,
Robert
Which kernel you are going to use depending which cm9 build you downloaded. There are several modded versions of that kernel out there, and including the open-go drivers or not, etc. Every ROM will contain and run a kernel, and so it is automatically depending on which Cm9 ROM you choose. I believe that every build posted within the last three days or so obtains the newest modded kernel containing the experimental drivers and the patch that fixes the formerly prevalent SODs.
Since you have flashed the current stable CWR, I would flash through the CWR menu. Reboot into recovery, and make a backup. Wipe data, cache, dalvik and then choose zip on sdcard, and choosing your preferred cm9 build. Should be all set. Most flats the builds are basically great, but but if the nook isbyour primary tablet, and you may be glad you have a backup of your current cm7, as some bugs can make it hard to run the ROM daily. Battery issues and some laginess has been reported.
Cm9 seems to improve on an almost daily basis, so if you intend to switch permanently, you will probably want to reflashed to current build every several days. Once you have flashed the cm9 build, upgrading to a newer build only requires wiping cache and dalvik, and which is pretty easy and keeps your settings and data intact throughout. These builds are functional, and but meantnfor those who want tontry the most experimental ROMs and are willing to dream with the bugs and want to reflash the newest builds as they arrive.
Curious about experiences. Right now I'm on the M3 Experimental.
It's really stable.. By far the most stable cm10.1 build I've ever used. Only thing Is the instagram videos come out fuzzed out and you can't see anything. That Sux
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
Only one bluescreen in 24 hours so far. Using its boot image in the newest Slimbean, hope it continues to hold up.
I was just coming to post this exact same question. I had to go back to M3 because there were too many bugs in the subsequent nightlies.
But I think i'll try RC-5 and see what it's about.
I did flash it. Since that time I've had some issued with bluetooth where I've had to reboot the phone to get it to work. Also some "blue screen" and random reboots. Someone suggested I should probably reflash and clear everything (data, cashe, dalvik etc...)
jdekoven said:
I did flash it. Since that time I've had some issued with bluetooth where I've had to reboot the phone to get it to work. Also some "blue screen" and random reboots. Someone suggested I should probably reflash and clear everything (data, cashe, dalvik etc...)
Click to expand...
Click to collapse
The bluetooth issue seems inherent in any of the 4.2.2 roms. I've done clean installs , wiped with Darkside, etc. It doesn't really seem to matter.
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Installed 10.1.0 using the updater and had lots of problems. Audio bad, Bluetooth not working. Installed clean with a factory reset and it is very stable. Only issue is still some camera apps (Google drive scan, latest evernote) require setting Disable HW Overlays. But other than that, seems good
jdekoven said:
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Click to expand...
Click to collapse
Lots of random reboots followed by a blue screen, I have noticed that it happens a lot during or after viewing a video and certain games, it even has happened while texting. No where near stable, battery life is horrible and like I said the reboots are random but often.
I'm using the CM 10.1 stable release as the boot image for PAC-Man rom. So far, no blue screens, reboots or anything. I've messed around with it, adding the Google edition camera and other goodies I found in i717 forum. Flashed in the S-4 launcher and everything is still holding together. Battery life is okay, considering I'm using livewall paper and wifi also. 60% remaining after four hours.
I'll give it a few days to settle in.
10.1.0 (4.2.2), good so far
jdekoven said:
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Click to expand...
Click to collapse
I've been running the 'stable' version for a couple days and only one b.s.o.d. Runs smooth and battery is about the same at RC5. Camera is good as well. Don't use Blu-tooth so can't testify for that. I reboot every morning and that seems to make a world of difference.
Wish stock JB would come to us.
Anyone know how to get stock screen resolution back?
20130804-Nightly stable
Hey all, just thought that since I complained about how buggy the nigthlies were, I should come back and say that I am now on the 20130804 and it is very stable. I have been using it since Monday and i've only have one reboot. I initially had some screen flickering when I had a solid green background (from an MIUI theme), but I switched to another wallpaper and don't have that problem anymore.
Just FYI.
i changed to omnirom kitkat on my s3 a few weeks ago, and i just want to know if i should be downloading the latest versions?
thanks in advance, glenn.
gdaley1 said:
i changed to omnirom kitkat on my s3 a few weeks ago, and i just want to know if i should be downloading the latest versions?
thanks in advance, glenn.
Click to expand...
Click to collapse
It would be interesting to know other people's views on this too.
Well things usually get an update to be better ^^. So i'd say always. If you look around the forum you'll see there are still some (minor?) issues left which might or might not be important for you. If you stop updating you'll also miss out on potential new features and you can't contribute by filing bug reports ect.
Sent from my Find 5 using XDA Premium 4 mobile app
I usually go on omnirom's changelog to find any patches that pertain to me. Just the other week active display was not working. I updated immediately when next active display patch came out. I also update when there is a new feature I want.
Since even minor updates often have big impact (on battery life for example) I update on every nightly. But I keep a backup in case a weird bug entered the image.
I hope the build-in flash in my S2 is not the cheapest one since Samsung itself only updated once half a year or so - so I am (at least a little, little bit) worried that it someday will be worn out. Does anybody know if this is really an issue?
I update when I'm bored and happen to remember. Maybe twice or three a week. I usually check g+, device thread, or here for any update problems, though.
there's been a handful of times where I thought "ok I'm done fooling around with my phone... I'm pleased enough," but I'll update afterwards.
I've been updating on every nightly and then there was the data/wifi issue with the s3 i9305 and since then my phone just has not worked as it should at all safe to say the next nightly I find that seems to have no data/wifi issues I'll be sitting tight on. I know my friend has a system where he updates to the second newest nightly only, never the newest that way you're always up to date eventually but you get to see the feedback about the nightly first from everyone else having used it before you flash it, thus saving the issue of flashing a nightly that stuffs up pretty bad.
Also does anyone know when flashing a nightly it's OTA, if you want to go back to the previous nightly can you just flash it and it should work? Before I was having wifi/data issues I had the nightly on my SD card, then I flashed the new nightly, got data issues so I flashed the previous nightly that worked and still had the data/wifi issues...
In my opinion, you're rolling the dice with any upgrade. A nightly is just that, whatever was up that night. It might be better, it might be worse. Thankfully the OmniROM maintainers are generally pretty good about things and I haven't yet gotten a broken build. But it will happen. Invariably the night before you really, really need your phone to be working.
A cautious approach would be to maintain recent backups and only flash when you see something come up that you know you want. I like to flash on days when there hasn't been a change for a day or two -- let someone else find out that the "latest and greatest" isn't as great as they had hoped.
Yes, flash memory has a finite lifespan. If you look at the physical device layer, you'll see it. A good physical-to-logical block management layer ("wear leveling") keeps the cells reasonably evenly used and hides the failed cells from you. It might be in the device itself (microSD cards, for example), or in the driver/filesystem. You probably don't have to worry too much about flashing on a daily basis (as far as "wear" goes) as long as your device devs have made reasonable choices on how to put files onto the hardware of your device.
Being in the time zone that I am, the nightlies usually post when I am sleeping. Each morning, I check the change logs and newest comments. If there are a lot of early problem reports I pass on the build. If things look reasonably clear I download and flash.
Usually I update once or twice a week.
Now my device (SGS2) is with nightly 06/03/2014. This nightly working so well and is so battery friendly that I will keep it for a while longer.
And now the camera already has the option to choose where to save photos and videos (internal memory or external SD card).