yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] productofusa:
For what its worth, I just bumped my NC up to nightly 150 from 7.1.1 rc. As I've seen the occasional "omg, bootloops, broken, what do I doooo?" posts from updating their rom, I thought id post a quickie rundown on how I get there. I assume this is how most people do it, but obviously the steps may not be exactly the same.

Anyone feel free to add input if they've got a as good/better way.

As I've had issues in the past I find that if I boot into recovery and use its functions from there as opposed to relying on Rom Manager I have far less problems with restores, updates, ect. While I really appreciate Koush's work and all, its just how I roll.

Download anything you need, I put nightly, newest gapps, (heh, never hurts to be prepared) and latest TitaniumBackup.apk on the root of the the sd card.

Backup apps in Titanium Backup

Backup bookmarks

Backup launcher

Nandroid backup

Boot into recovery

Wipe cache

Wipe dalvik cache

Wipe battery stats

Flash nightly

Reboot and check system settings, once everythings to your liking make another nandroid and delete any backups you wont be using.

I realize alot of folks take this for granted and its almost second nature, but for those of us that get lazy and tend to stick with a working rom, reminders never hurt. :rolleyes:

Feel free to beat up on me if I forgot something.
[Nook Color Android Development] ponyboy82:
Maybe I just like living dangerously, but to be honest I usually just download the nightly, reboot into recovery, flash the nightly, reboot into CM7, and then sometimes run Rom Manager - Fix Permissions. As long as I don't try anything stupid, I've never had problems. For whatever reason, I've never had luck updating directly from Rom Manager, but I haven't spent much time trying that approach.
[Nook Color Android Development] wallsg:
Between my wife and kids my Nook is almost never off. It's amazing how an "I don't know why you want to buy that" became a can't live without. The up volume button on mine is messed up and they don't even want me to ship it off to be fixed.
[Nook Color Android Development] bigbob23:
It happened again with N151. I wiped cache and Dalvik cache, then ran fix permissions before updating.

CWR showed:

Finding update package...

Opening update package...

Installing update...

E:Error in /sdcard/cm_encore_full-151.zip

(Status 1)

Installation aborted.

Again, I restored my latest backup and was able to successfully install the updated ROM.
[Nook Color Android Development] Colchiro:
Meanwhile I'd install a volume control app. I didn't see one that resides on the status bar tho. https://market.android.com/search?q=volume+widget&so=1&c=apps
[Nook Color Android Development] newellj79:
I use one called "audio manager". It does work from status bar.
[Nook Color Android Development] sisterchick:
I've seen that before with CM6. I'd suggest two things:

1) Copy your data to PC and reformat your SD card. Likely a bad block.

2) I've had mxed results flashing from ROM Manager. Restart to recovery and flash from recovery. Wipe dalvik, wipe cache, flash the rom THEN fix permissions (fixing comes after flashing).
[Nook Color Android Development] msherwood:
Awesome, that's good to hear. I might just try it out!

(see what I miss without XDA app? Darn you rooted Nook and your app problems)
[Nook Color Android Development] patruns:
While probably unrelated, I never fix permissions or wipe anything other then Davlik, which is checked off by default. I have not had a single update through ROM Manager fail when doing this. :)
[Nook Color Android Development] leapinlar:
Same with me. ROM Manager has always worked perfectly just checking wipe Dalvik. And I always check gapps because I have a custom version of gapps zip that modifies my install to change the lcd density automatically for me.
[Nook Color Android Development] patruns:
What density are you using and in what apps does it show the most improvement?
[Nook Color Android Development] iDidItAll4theNookie:
Any chance of bringing back the 950mhz option? I like the snappiness of 1100, but it really drains the battery fast. 800 is just a little too slow. :(
[Nook Color Android Development] Nburnes:
Use Dalingrins Nook Tweak from the market and set your own clock rates.
[Nook Color Android Development] leapinlar:
I use 240. I know must people do not like it that large, but I also have a Galaxy Tab ( 7" ) and that density is standard on that and I am used to it. Also that density is one of the three (240, 160 and 120) standard densities that is included in the Android standard, therefore all apps should work perfectly with it and they do. I considered 160 way too small for my old eyes. I used 187 for a while and it worked nice, but decided I wanted consistency between the tablets.
[Nook Color Android Development] rsage:
If you set it that high, does it cause weirdness in the status bar or anywhere else?
[Nook Color Android Development] Sincitybronze:
I like 240 as well. Haven't noticed anything weird except for sometimes the status bar fills up too much if I keep the quick notifications enabled.
[Nook Color Android Development] leapinlar:
The status bar is not weird, but crowded. I modify the tablet tweaks settings to only include the menu, back and notification button. I never used the search button and home is on the hardware. Tablet tweaks takes a little under half of the status bar. Still plenty of room for notifications. Everything else looks perfect. Especially the text in my widgets.
[Nook Color Android Development] iDidItAll4theNookie:
Thanks. I didn't know that one was out there. Just another reason to thank Dal!
[Nook Color Android Development] dexx0008:
same here, 800 too slow, too much battery drain with higher settings. wish it was still in the build, but will check out the app.
[Nook Color Android Development] khaytsus:
Only drains if you're using the CPU... If it's idle or not doing anything heavy, it's running at the lower levels.

If you're taxing the CPU for a long time, such as in a game or such that does not need the speed, downclock it temporarily. I do that for Zenonia, I have a shortcut to the CM Performance menu near my games, I pop in there, change max speed to 600mhz for that game and it uses half the battery that it would at 1100mzh and runs just as well. 1100mhz for me = 25%/hr. 600mhz = 14%/hr while playing that game.

But again, otherwise, no it does not use more CPU, unless you've set the governor to Performance which you shouldn't do anyway.
[Nook Color Android Development] newellj79:
How did u get a short cut to cm performance?
[Nook Color Android Development] Nburnes:
Long press screen > Shortcut > Cyanogenmod Settings > Performance settings
[Nook Color Android Development] Sincitybronze:
Hi guys...how do I go about submitting a request for a CM7 modification?
[Nook Color Android Development] fattire:
Just say what it is. Or implement it yourself :)
[Nook Color Android Development] cymoze:
Me three on this. I just went from n129 to n150 without a glitch going through ROM Manager, wiping Dalvik, not wiping data, and installing the latest gapps.
[Nook Color Android Development] jeremyshaw:
Just came back to a rooted NC :D previously had it at stock 1.2 for a while.
[Nook Color Android Development] crstfr:
New to the Nook world......well not me.. per say.... my 8 yr old son!.... .. i spend my time in the EVO4g section.. cm7...... but i'll be lurking in here.....posting .....

Nook Color... Rooted.. CM7 Nightly153!.....sucker runs smooth!...

Thanks guys!
[Nook Color Android Development] patruns:
Wow, didn't that just come out this morning? :)
[Nook Color Android Development] SCWells72:
Still can't get CM7 with .32 kernel to run smoothly...thoughts?

I've tried multiple times to move up from 7.0.3/.29 kernel to anything more recent with a .32 kernel, and every time I've had to restore my 7.0.3 backup. Basically the newer versions lock up on me frequently, often just booting the OS. Most of the time it appears it's trying to mount/scan the SD card (8GB class 4 Sandisk) because it occurs right after I see an SD card icon appear in the status bar, but I've booted it with the SD card removed and had the same behavior. Once in a while I get past the initial boot and am able to use the Nook, but then out of nowhere it locks up again.

I've tried upgrading in-place by just wiping the Dalvik cache and cache partition and fixing permissions, and I've tried upgrading by letting it wipe system and data and then using TB to restore my apps, and both lead to the same end.

My 7.0.3/.29 system has been running at 1300MHz with no issues at all, so when I try a newer CM7 ROM I always move up to 1200MHz and sometimes use Nook Tweaks to try for 1300MHz. Both of these clock speeds generally seem fine by themselves, but perhaps they're contributing to my lockups?

I normally use LauncherPro Plus, and my screens include Beautiful Widgets, Business Calendar widget, the LauncherPro Plus Gmail and Friends widgets, and AtomaRSS widget against my Google Reader feeds. It seems like I've heard that Beautiful Widgets could contribute here.

If I'm "stuck" on CM7 7.0.3, that's fine, but it just seems odd that others have been able to run more recent builds without issues (or at least that's my impression; please correct me if I'm wrong!) and I simply can't. I thought I'd reach out one more time here to see if someone might provide a suggestion on an approach to upgrade that might work for me.

Thanks in advance!
[Nook Color Android Development] crstfr:
i flashed Sunday morning at some point... son's b-day was sat!
[Nook Color Android Development] Sincitybronze:
OK, I wasn't sure if this was the thread or if I should request somewhere else. I posted this question on the general forum about improving the CM7 calendar.

http://xdaforums.com/showthread.php?t=1207392

I would really like to see an improvement to the calendar and its ability to integrate with Google Calendar. A "visible, not sync" option would be fantastic. My Samsung phone has a calendar that doesn't even have this option--it is linked only to the settings selected in Accounts and Sync. That works well, too.
[Nook Color Android Development] shumash:
USB Mount Times

I have nightly 150 installed on my SD (8gb Sandisk class 4), stock in emmc. I've been noticing that the time to mount the sd (and emmc, I think) seems to get longer with each boot (the boot time doesn't seem to have changed). I haven't added any new apps lately. The sd is brand-new since I was noticing the problem on an older class 6 card, but now it seems to be unrelated to degradation in the card. Any ideas as to what might be happening?
[Nook Color Android Development] Narfx:
You read it from me, probably. I think I'm the only one that had lockups right after boot with beautiful widgets a a theme applied with the first versions of 2.6.32 (the problem was quite consistent: one of every 2-3 boots I'd get a lockup). At least I don't remember anyone answering me :rolleyes:. That's why I simply decided to remove beautiful widgets from my screens. Since then I've had 0 lockups at boot, flashing the latest nightlies every 3-4 days.
[Nook Color Android Development] adma84:
thought I would add a little middle-school throwback in there (at least for my generation)

I heard that the delayed nightly builds have been due to added WiMax complications for my beloved EVO. Don't forget, if you guys get impatient, you can always Build from source. Just modify the instructions for encore instead of supersonic. You will need a 64 bit processor/OS to do this
[Nook Color Android Development] mrty4short:
Setting the lcd density to 169.33333 all apps seem to work with no issues. But the comment on gerrit to fix the scale for the lock screen found here http://review.cyanogenmod.com/#change,3487 with that lcd density seems to make it look really bad. Hopefully there is a way to fix this leaving it at 160 seems to make it work but some apps force close.
[Nook Color Android Development] Dadeeo:
Anyone trying nightly #11 yet? My new NOOK Color will be here Friday and I really want to try CM on it, I only rooted my last one...
[Nook Color Android Development] dalingrin:
No major changes.
[Nook Color Android Development] timekeeper:
Not Ie5ece40e Fix issue with DPI and I739da1b8 Set lcddensity? Are those meant to fix the issue with Maps out of the box?

Downloading nightly 11 now, woot.
[Nook Color Android Development] adma84:
no major changes? I thought that I saw a ton of merges from 2.3.3 into CM yesterday? Did these not hit N11yet?
[Nook Color Android Development] newellj79:
Nightly 11 running smooth. I haven't noticed any big changes. Market still doesn't show my apps, maps still fc's. Anybody notice anything else?
[Nook Color Android Development] tony1208:
dl 11 now...wish there was a change log
[Nook Color Android Development] adma84:
review.cyanogenmod.com and look at merged...
[Nook Color Android Development] pavlos46:
Just changed. My resolution to 161 and both myapps and maps work.
[Nook Color Android Development] jd95:
i can not get market to even load in v11
[Nook Color Android Development] subcypher:
I can't get gapps to load at all, not just the Market.
[Nook Color Android Development] jblues1969:
A couple of dumb questions I haven't been able to find clear answers to:

1. Once you flash CM7 onto the EMMC, can you use Clockwork to retore back to a backed-up image? I'm keeping the SD card I use with my rooted 1.1 image aside and using a different one to flash CM7.

2. When creating the flash SD card for CM7, I read the instructions and put the Gapps and latest CM7 daily directly on the root of the card. Can I also put the overclock kernel directly on the card before I flash it?
[Nook Color Android Development] tominabox1:
I have not tried this myself but apparently the gaaps will work if you change your lcd density to 168.33333 (use 5 3's) in build.prop
[Nook Color Android Development] buffalosolja42:
Did you use the gapps.zip provided once I did it worked fine for me (using v7 didn't try 8) about to flash 11 and change screen resoulition to what everyone suggested.
[Nook Color Android Development] jkurl:
this is one of the best builds since V5.
[Nook Color Android Development] kronium:
Anyone consistently get My Apps to work with v 11?
[Nook Color Android Development] bonobomidwest:
Before this typo mutation propagates further... the correct value is 169.33333

http://xdaforums.com/showpost.php?p=11703533&postcount=308

:)
[Nook Color Android Development] newellj79:
Change LCD density to 161. If u don't already have the app its called LCD density. Fixes maps too.
[Nook Color Android Development] tominabox1:
ah good catch. I tried 169.33333 on v11 and it did not fix any of my apps displaying correctly (mount sys ro/rw, google reader etc) so I thought maybe 168 was correct. Alas, neither seemed to work on my device.
[Nook Color Android Development] Hindle1225:
Just a thought... Have you tried "format /system" during all your cache cleaning before install?
[Nook Color Android Development] Ronin3178:
Agreement here on that, I have been on .32 for a while now, but if you are moving from a .29 system I would format everything but boot and data. I think that would solve your problem.
[Nook Color Android Development] CapnBry:
I figured I'd post some numbers for power use comparison, because I've found others' posts useful for deciding to upgrade to N151 (from RC1).

First of all I've undervolted from the standard voltages. To test each voltage, in CM Performance, I set the governor to "performance" the max CPU speed to the speed I was testing. I then lowered the voltage until I got any sort of error in a suite of running Quadrant, SmartBench, Linpack, Vellamo, and NemaMark1 in succession three times (each one once, then repeat twice more). At that point I bumped the voltage back up 1 notch.

1200MHz 1.3375V

1100MHz 1.25V

800MHz 1.1V

600MHz 0.95V

300MHz 0.8125V

Activity: eBook (one hour per test)

Screen brightness: MIN, WiFi: Off = 1%/7.1mins

Screen brightness: MIN, WiFi: On = 1%/6.7mins

Screen brightness: 40%, WiFi: Off = 1%/5.1mins

Screen brightness: 40%, WiFi: On = 1%/4.6mins

Sure this isn't "web browsing" which isn't a very comparable metric from one user to another, but it gives you an idea of sort of a maximum run time.
[Nook Color Android Development] junkrobot:
I just got back home, so I updated to nightly 153, but now my NC refuses to bring up the prompt so I can transfer files to the device. Also, the battery reporting is as wonky as ever, randomly jumping from 83% to 100% in about two seconds.

Any tips, everyone? These two problem seem like they'll always plague me.
[Nook Color Android Development] crstfr:
+2.. i have to say .. i did format system/cache/data....... then installed.. and it ran smooth... i never did that in the past.. just this once on the nook but it worked.... and i read that on the guide i used...

good call Hindle!
[Nook Color Android Development] crstfr:
on 153 myself.. .. but no issues here.... i'll talk to my son tonight(its his) and see if anythings been jacked... but its oc to 1100... and was running smooth... running live wallpaper too... its love!
[Nook Color Android Development] crstfr:
ok now my own questions....... i have an EVO...with all my son's games/data on it.... i use TB to back up.....

I've installed all the games on his new nook.. and also have TB on that.... can i just copy and paste the files for the games into the nooks TB folder.... ??..i'm assuming it wont overwrite because of a different file name/date... I've tried this before with no love~...... ...now when i go into TB i should have two backup dates .. correct?... hhmmmm i know its this easy, but making this work..g.r.r.r.r.r.

thanks guys!!..
[Nook Color Android Development] Ronin3178:
I have done this with a single app before. I was able to d/l GOF2 THD on my D1, and not able to on the Nook. So I backed up app with TB, found the 3 files in the TB directory, shared/ d/l'd via dropbox to my Nook and restored with TB.

I would say your idea should work, maybe delete all backups on Nook before you copy over files, then once all is restored, redo the backups.
[Nook Color Android Development] Hindle1225:
Glad I could help. I noticed others in the past mention you only need to wipe cache partion and dalvik cache before updating, but... I format system, wipe data and all cache before I load another rom or update. I do this for all my android devices and it never fails me. I should note that I always backup in CWR before updating or loading a new rom.
[Nook Color Android Development] crstfr:
that's all i do on my evo.. dalvik and cache... never went in to format system.. but seemed to work!
[Nook Color Android Development] crstfr:
i'll try it ... thanks!
[Nook Color Android Development] leapinlar:
You do not need to format /system if you are flashing a CM7 ROM (including nightlies). The install zip automatically does that for you. The CM7 install zip 1) backs up your gapps, 2) formats your /system 3) installs the new /system from the zip and 4) restores the backed up gapps. It then does a few other housekeeping things like setting symlinks, etc.

However, other ROMs for other devices may require the format.
[Nook Color Android Development] leapinlar:
The calendar that you are using with CM7 is part of the gapps package that is added to CM7 after it is installed. I don't think the CM7 development team controls how that calendar works. Google does. I too like my Samsung calendar on my other device. On my Nook I use Calendar Goo. It is more like the Samsung calendar. And syncs very nicely.
[Nook Color Android Development] junkrobot:
I seem to remember there being some USB to PC issues way back in the earlier CM7 builds, but anytime something odd like this has happened to me before, I could just fix permissions, reboot, and then it'd be fixed. Now, the best I can get is the USB connect icons flashing in the status bar for a split second only to shut down before I even get a chance to hit the buttons. Frustrating stuff. Maybe this is an issue that'll be resolved in a build to come?
[Nook Color Android Development] SCWells72:
Yeah, I've done full wipes during upgrade. In fact, I tried one more time today where I did told ROM Manager to make a backup of my current ROM and wipe EVERYTHING before installing n150 and gapps. After that booted I starting doing simple configuration in system prefs like tablet tweaks, overclocking the CPU to 1200MHz, etc. Then I used Titanium Backup to restore a small subset of my apps/settings including Amazon AppStore, Amazon Kindle, Beautiful Widgets, and Business Calendar. Somewhere in there it locked up on me again and started doing the same thing. I'm not sure how to approach it more cleanly than that and still have access to the apps I use... Ugh.
[Nook Color Android Development] Hindle1225:
I should add that I dont use rom manager for anything other than using the notification that a newer rom is available. I do everything out of clockwork recovery - wipe, format, install, ect..
[Nook Color Android Development] liam.lah:
There is an option inside TB that does this, longpress on your desired app, should be something like "send app" or "send backup", you can dropbox it or whatever from there, knowing it has sent all the right files.

Dude. Do a nandroid.
[Nook Color Android Development] Sincitybronze:
Thank you for your reply, leapinlar. I didn't even think about the calendar being a gapps component. Good point. I would like to try out the calengoo (I assume this is the app you were referring to?) but can you tell me how you set this up before I spend the whopping 6 bucks (haha) to buy it? Did you uninstall the stock calendar first or did you just leave it on your Nook?
[Nook Color Android Development] leapinlar:
Yes I did mean Calengoo. I just installed it leaving the stock calendar alone. Set it up to sync with google calendar. The stock calendar storage component works in the background.
[Nook Color Android Development] rsage:
Netflix issues w 153?

I just flashed nightly build 153, I'm coming from 150 or 151 (don't remember exactly). Prior to flash, Netflix was working fine. After flash, the video still seems ok (maybe a little choppy), but the audio is off by about 2 seconds (out of sync). I cleared cache and dalvik from cwm, cleared data for the Netflix app, rebooted, etc., no difference. Anyone else having this problem?

Figures, this is the one time I forgot to nandroid before flashing a new nightly...

BTW, I'm at stock LCD density, overclocked to 1100, no undervolt, and 32 bit dithering on in CM settings and nook tweaks.
[Nook Color Android Development] leapinlar:
I just read your other request on the other thread. You do not like the stock app syncing all the time and using battery. I also have Calengoo installed on my phone and I did not want it syncing all the time either since I am on a pay as you go data plan. My solution was to turn off autosync and get a program called "Synker". It allows me to set up a widget to sync the google calendar only when I ask it to (manually). I only do it when I am at home on wifi. Looks like this could work on the Nook too to save battery.
[Nook Color Android Development] RASTAVIPER:
Noneed for formating anything when I went from Phiremod 6.3 to nightly 129.

Just wiped Delvik cache.

Sent from Nook Color on Cm7 Nightly 129 @1.300Mhz
[Nook Color Android Development] rsage:
Tried reinstalling Netflix, changing LCD density, turning off 32 bit and dithering, etc., no change. Guess I'll try to flash back to an earlier nightly later.

Edit: Flashed build 154 (which is a little larger than 153 but lists no changes), still had the same problem. Let a movie play in Netflix for about 10 minutes, and suddenly everything snapped back in sync.
[Nook Color Android Development] :
OMG I can't wait for this to be pushed:

http://review.cyanogenmod.com/#change,6833
[Nook Color Android Development] Nburnes:
Yup, I have been personally watching that myself.