[Q] Nook Needs an Upgrade - Nook Color Q&A, Help & Troubleshooting

Apparently I haven't been paying attention. Looks like my Nook is still running CM7 stable 7.0.2 and while I have been really happy with it. I think its time for an upgrade. I purchased the Galaxy Nexus on launch day and ICS is awesome. I want it on my Nook bad but I understand it may be awhile.
In the meantime what do you all recommend for now? Do I go with the latest stable build or nightly? Are the nightlies even available?
Edit: I see nightlies are up? I'm guessing I should probably stick with a stable build huh? Is there overclock ability in the latest stable build?

I haven't updated myself yet but vastly suggested by many members of using MiRaGe KANG, which also CM7 based.

I second MiRaGe. Latest CM7 based with all known fixes in including overclocking kernel. I've been using 12th Dec version and it seems very stable.
Nightlies got stuck in Mid November and I don't think they will resume until ICS starts up. MiRaGe is the best bet until there is a good ICS version available.

Related

[Q] what is RC

I was looking at the NC cm7 builds and saw one that said RC it isn't a nightly or a stable. what is it?
Release Candidate for the next stable version I believe.
chad11 said:
I was looking at the NC cm7 builds and saw one that said RC it isn't a nightly or a stable. what is it?
Click to expand...
Click to collapse
Nightlies are "alpha builds" they are the newest and freshest of the fresh when it comes to updates. However they can be buggy.
RC / Release Candidate. They are less buggier then the Nightlies but may lack some of the newest features.
Stables are even less buggier then RCs but will be lacking some features from the RC and Nightlies.

Which nightly is CM7.1 RC1 based on?

I am currently running CM7.1.0 RC encore and its been pretty stable, but I have been reading all the things people are doing with some the more recent nightlies. So I was wonder which nightly is RC1 based on and is worth the trouble updating to one of the more recent nightlies?
Thanks for your help
well, it's not. It's a stable release, so you should see it in that region.
http://download.cyanogenmod.com/?device=encore&type=stable
It released on 06/27, so most likely be the nb115
Phatdawg said:
well, it's not. It's a stable release, so you should see it in that region.
http://download.cyanogenmod.com/?device=encore&type=stable
Click to expand...
Click to collapse
you might have misread what version i am using. I am using 7.1RC1 = release candidate
votinh said:
It released on 06/27, so most likely be the nb115
Click to expand...
Click to collapse
thank you! would be worth while to update to a more recent nightly if so, which seems the most stable?
Phatdawg was right. The nightly, RC, and stable are different branches. They are not "based' off of each other. The stable is the one that should be (duh) stable. RC is pretty stable, but might have bugs. Nightlies have more bugs, but usually small ones that no one really notices. They also have cutting edge features.
well, you're best bet would be going with the nightly that was compiled before or the one after of the release date of the release candidate, in regards to figuring out which nightly it's closest in relationship to.
ikingblack said:
Phatdawg was right. The nightly, RC, and stable are different branches. They are not "based' off of each other. The stable is the one that should be (duh) stable. RC is pretty stable, but might have bugs. Nightlies have more bugs, but usually small ones that no one really notices. They also have cutting edge features.
Click to expand...
Click to collapse
For real? I'm close to the firmware groups and I always do think stable/RC/nightly build are based on the same one.
Nightly is image that build nightly, do have some more registers for testing or some enhancement but not ready to release yet. Up to a point that they think it have enough juice, not officially for manufacturing but for customers testing out or "playing with", they will release as RC and to the dead-line, they must release a stable image for customer.
Other way to say is: nightly build is special image for internally use while RC is distributed to customers/power user groups and stable is for selling products.
This "stable" doesn't mean 100% stable but they do have all bugs that introduced previously, fixed.
After the stable release, they will continue on their work, enhancement, more features, so more nightly builds and the process keep going.
Is the Android ROM building process different to other images built such firmware for router/switches or WDTV Live boxes?
wow getting some great info, thanks. I usually just troll the forums.
one thing that I noticed is that with 7.1RC1 and OC emmc kernel 6/30 it is not stable at all if you mess with the stock voltages using nook tweaks.
My main concern is usb host included in 7.1RC1? Or is that feature built into the kernels?
Am I missing much by using the RC1. Don't get me wrong I get great battery life and great performance.
Are any of the nightlies safe to run off of a 16gb sandisk class 2?
If you are using the SD card to boot, sandisk is the gold standard.
Anyhow, there are things you are missing both good and bad.
Just a few versions ago when Daligrin updated the gpu stuff, the nooks all grinded to a halt, so people have to downgrade to prior or wait for the the gpu to be reverted to prior.
But at the same time you get the integrated kernel now and you have various other improvements.
To answer your question, I think it's a good idea to update to a nightly every so often that has a set of "upgrades" that you want or need.
I usually wait for a few encore specific code changes before I move to another nightly, but if there is a specific encore change that I want to try out I will upgrade to a nightly sooner. Just depends.
mrkavanagh said:
one thing that I noticed is that with 7.1RC1 and OC emmc kernel 6/30 it is not stable at all if you mess with the stock voltages using nook tweaks.
Click to expand...
Click to collapse
I'm having no issues. Running mine off AEbobby912's listing I saw in the Nook Tools thread.
300- step 1 is 0.8125v
600- step 2 is 1.0v
800- step 3 is 1.1875v
1100- step 4 is 1.25v
1200- step 5 is 1.2875

Curious to know the most stable CM

Just wondering what ROM people say is the most stable and dependable. I've heard 201 is the best out right now. Opinions?
Sent via Tapatalk on my *voided* Evo running CM 7.1.0
At the moment I'd say the most problem free is MiRaGe. None of the stables or nightlies have the latest SOD fix in plus other fixes for things like phone signal icon showing up.
MiRaGe has these fixes in plus some other optimizations.
bobtidey said:
At the moment I'd say the most problem free is MiRaGe. None of the stables or nightlies have the latest SOD fix in plus other fixes for things like phone signal icon showing up.
MiRaGe has these fixes in plus some other optimizations.
Click to expand...
Click to collapse
+1 for MiRaGe.
Merry Christmas
MiRaGe for me with the mods suggested. http://forum.xda-developers.com/showthread.php?t=1344873
+1 MiRaGe.
Since no more official CM nightlies are coming, I've also started using Mirage off SD boot. No problems so far.
mr72 said:
+1 MiRaGe.
Click to expand...
Click to collapse
I have done 2 Nooks with this and have found it pretty good except I can't seem to apply updates per the normal process. Haven't needed to yet (didn't use the updated theme because it wouldn't apply)
@bobstro CM tweeted awhile back (shortly after AOSP released ICS source 4.0.1) that stable CM 7.2 was in the works still. I believe they are finalizing stability issues while also working on the new CM9 simultaneously. It's just that most devs are playing with the new source right now, getting preliminary work done to set up CM9.
But as far as recommendations go, Mirage Kang is solid. Just be sure to rename phone.apk to phone.apk.bak for increased battery life.
I also recommend LauncherPro, however, with this ROM, I cannot get versions newer than 0.8.3 to install.
disynthetic said:
@bobstro CM tweeted awhile back (shortly after AOSP released ICS source 4.0.1) that stable CM 7.2 was in the works still.
Click to expand...
Click to collapse
I'll definitely check it out when it becomes available. n253 was giving me grief that Mirage seems to have cleared up in the meantime!
I believe they are finalizing stability issues while also working on the new CM9 simultaneously. It's just that most devs are playing with the new source right now, getting preliminary work done to set up CM9.
Click to expand...
Click to collapse
I'm definitely looking forward to checking out CM9 as well.

[Q] What are the cool kids using these days?

I've dusted off my NC after a few months packed away. I'm pondering loaded a new rom/kernel/whatever. Unfortunately, I haven't kept up with what's available and cool development advancements, etc. I'd appreciate some recommendations on the latest and greatest stuff. I'm currently running CM7 with Dalingrin's OC kernel that I got last June. I'd like to get something with bluetooth support (heck, for all I can remember, what I currently have supports bluetooth).
Anyway, thanks in advance for any recommendations.
I am dualbooting from EMMC. CM7 Mirage Kang and CM9 with Open GL. I do not update CM9 that often because it is in alternate and takes about an hour to update total. I do update when a new CM7 Mirage Kang comes out though.
Installing the dualboot setup is a breeze updating primary is a breeze too. It is just a pain for me to update alternate.
Thanks. I'm curious, can you tell me what Mirage Kang is? And what does Open GL buy me? If I wasn't going to dual boot, would you recommend CM7 or CM9?
Definitely Kang, http://forum.xda-developers.com/showthread.php?t=1344873
CM9 isn't even officially in Beta testing yet.
flu13 said:
Thanks. I'm curious, can you tell me what Mirage Kang is? And what does Open GL buy me? If I wasn't going to dual boot, would you recommend CM7 or CM9?
Click to expand...
Click to collapse
Mirage Kang http://forum.xda-developers.com/showthread.php?t=1344873 is just a modified build of CM7 that is updated when any useful release is released. So it's not a nightly thing. I love it!
As far as CM9 open gl, I think it has something to do with movies and such. It is not enabled by default on the CM9 nightly so I don't think it would hurt.
I would recommend CM7 Mirage Kang if you are not going to dualboot as CM9 is not really ready for prime time. I have it on mine because it is not hurting my current set up. I actually have alot more space on CM7 than I did when I wasn't dualbooting. I would recommend repartitioning so you have more space for apps and games on EMMC. I would use the 1.96gb scheme as found here http://forum.xda-developers.com/showthread.php?t=1094371 .
Please also note that dual booting is not limited to CM7 and CM9 but it works for almost any combination. Stock, CM7, CM9, MIUI (did I spell that right) etc. So maybe run a rooted stock and CM7 on the same machine.
Thanks a million, zires. I've now got myself a zippy new Mirage Kang Nook with the supercharger and everything.
I had to come back after using this for a while and comment that the battery life is amazing compared to what I used to get. Thanks again.

EOS Nightlies vs Stable

Anyone jumped from the current EOS 1.0 stable to the nightlies lately? Or vise versa.
I'd love to know how it went if there was any differences.
I've been happily on 1.0 for months but interested to see if there's any worthwhile improvements.
wingray 91 is great, and seems very stable.
I love the nightlies, especially #91, which is ICS 4.04, with their latest mods. Going from stable was same as from a nightly for me, just remember to flash the nightly along with the latest gapps, before you get out of rom manager, and make a backup prior to install that way you can always go back to how you were.
Sent from my DROIDX using Tapatalk
brent0r said:
Anyone jumped from the current EOS 1.0 stable to the nightlies lately? Or vise versa.
I'd love to know how it went if there was any differences.
I've been happily on 1.0 for months but interested to see if there's any worthwhile improvements.
Click to expand...
Click to collapse
If you check the change log. There has been a bunch of changes.

Resources