yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] gudism:
I am currently running Phiremod 6.2 (not sure what release of CM7 this was based on) and I want to go to straight CM7 to utilise the better battery performance

.

I tried last week to flash CM7 n74 and had weird wifi issues that I couldnt fix (they were differnet to the usual drop out issue, but I wont go into as its not the point of my post) so I went back to the backup of Phiremod 6.2 I was preiviously running as I had zero issues bar the poor battery life.

my question is if I have another shot at CM7 (prob with n86) seeing as it has the 1.2 uboot update built-in, will I be able to restore my phiremod backup if I choose to flash back to the backup? that is if I encounter the same wifi issue?

Like seeing as the backup was made with uboot 1.1 will it be ok?

only asking as I dont have the time to be messing around flashing stuff then fixing stuff right now (i have 4 young children). If the wifi wont work, I'll restore....thats simple. But if it gooses something up....not so good :)

thanks
[Nook Color Android Development] Ronin3178:
Yes, i am pretty sure your backup includes everything, including boot. Even if it doesn't I believe the 1.2 uboot is backwards compatible, so you should still be able to restore phiremod.
[Nook Color Android Development] gudism:
thanks for that info, I may have to attempt to flash CM7 once more!

thanks again
[Nook Color Android Development] greenmky:
Been on nightly 87 for a day now, and no issues besides one random FC of the task bar and netflix being cranky after resuming from standby (which I kind of expect for a hacked app).

Video performance is better by far than CM7.0.2 stable - I would get choppy video and poor performance after leaving videos - that has cleared up entirely.

I went B&N stock (1.2 uboot) -> CM7.0.2 -> nightly 87
[Nook Color Android Development] I Am Marino:
I had a random moment today when my Nook started scrolling left and right on the home screens slightly by itself and would get stuck in between screens, only way to fix it was to shut screen off a few times with power button.
[Nook Color Android Development] paleh0rse:
Mine did that yesterday in the gReader app... I set it down and watched it wig out for 30 seconds before deciding to power it down. It has only happened once, though... /shrug
[Nook Color Android Development] ziggy34:
what version of recovery are you using? make sure it's 3.0.2.8
[Nook Color Android Development] I Am Marino:
Definitely a /shrug moment.
[Nook Color Android Development] angomy:
I have a D-LINK router running b/g wpa/wpa2 psk tkip and after some disconnect hiccups in early nightly 80s and beta1 haven't had any wifi issues, running nightly 87 with included (non-OC) kernel. Works fine with the router @ my dept which I believe has a netgear (Def not Belkin). Wifi hiccups were happening when router was set to AES though fixing that may just have coincided with updating to next nightly instead of router setting.

CM7-nightly@925mhz emmc
[Nook Color Android Development] kLAcK107:
I am also having WIFI issues with nightly 87. The wifi connects and drops every 10-15 seconds. I am using WPA TKIP. Back to Phiremod 6.2 and the problem is gone.
[Nook Color Android Development] butler360:
WiFi doesn't appear to disconnect for me (icon shows it's connected), but it seems very stop-and-go. Market connects fine when opened, then I click an app link: "a network error has occurred." Press retry a few times and it eventually works again.

Downloads are generally massively slow as well. Took 20+ minutes to download a 3MB file.

I'm on nightly 87.
[Nook Color Android Development] 911jason:
What brand router are you using?
[Nook Color Android Development] bekyndnunwind:
I use a Belkin Router, and I don't have any problems, but I'm still on Beta3.1 w/ 5/23 kernel.
[Nook Color Android Development] only one haze:
anybody know the answer to this? its driving me nuts and I cant seem to find anything about it other than I need it.
[Nook Color Android Development] derekr:
I have been using B3.1 to n85,n87, n87 and OC523 with no drop in battery overnight. Then last night I installed CPUspy, and this morning the battery % had dropped by 10% from 55 to 45% (I know because I am monitoring the battery discharge) CPUspy indicated no deep sleep.

Sooo, my question is whether it is CPUspy itself that might be causing the sleep problems??? It sorta makes sense that monitoring would require keeping the CPU awake.

I have uninstalled CPUspy.
[Nook Color Android Development] Ronin3178:
B3.1 5/23 OC, as you can see, I get plenty of deep sleep with CPUspy.
[Nook Color Android Development] Zorkman:
mine also does that quite a lot

very annoying while reading

powering the screen off and on seems to fix it TEMPORARILY

comes back quite soon
[Nook Color Android Development] stolenmoment:
not CPUSpy

Not for me: n87 on SD, cyan menu u-boot, *not* OC, ondemand, 925/300. CPUSpy shows lots of deep sleep (overnight) plus some at most other speeds, and I'm getting my best battery performance on CM7 to date.
[Nook Color Android Development] I Am Marino:
I don't think cpuspy would cause it.

I get deep sleep sometimes and sometimes I don't.

Last night for example, I got 6 hours of deep sleep, the rest at 600mHz.
[Nook Color Android Development] chisleu:
CPU Spy is spying on a file (or virtual file) that the kernel (or something) keeps track of.

It doesn't do anything in the background.
[Nook Color Android Development] Xhorder:
I would also like to know how to do this...
[Nook Color Android Development] Expatriotex:
was on 3.1 with the 0513 oc with rock solid wifi

did a full wipe and flashed the bn1.2, then flashed the new. 32 nightlies and had the wifi problems on all of them

just flashed the 3.1 and 0513 again, only wiping caches and wifi is solid again.
[Nook Color Android Development] only one haze:
Well I went and flashed multiboot 0.4 from here and now I have my dual boot back.

Could someone please tell us how to go from this to the new uboot without losing dual boot? Or can the files that multiboot looks for also be added to the new uboot? Either way it would be nice to not have to reflash multiboot over the nightlies each time.
[Nook Color Android Development] jhnstn00:
Use rom manager. Go into recovery from there.

or power off then press both Nook button and power. Hold for 5 seconds after splash screen appears then release both.
[Nook Color Android Development] rickpref:
oh, that's right....need to go to recovery through Rom Manager.
[Nook Color Android Development] adma84:
Could this have anything to do with the YouVersion Bible app looking really crappy all of a sudden? Was very sharp on N5 but N7 looks quite a bit different to me. Would have thought HDPI would have looked better?
[Nook Color Android Development] Link3737:
Is anyone else having these issues or did I get a bad flash?

A) Whenever I highlight an item there's a blue bar that appears in the middle

B) Whenever I select wireless and networks in settings the application crashes

I thought nightly 5 was near perfect, and now both 6 and 7 have given me headaches :rolleyes:
[Nook Color Android Development] jhnstn00:
Same here.

Change theme I heard for fix 1

Add activities shortcut to wireless settings is only fix so far
[Nook Color Android Development] FletchF:
Does anyone know if this kernel has built-in tun support?
[Nook Color Android Development] likearaptor:
I'm not sure but when I tried to use VPN Conenctions it would FC, I just tried it with Nightly 7 build on CM7 and it still crashes
[Nook Color Android Development] newellj79:
To restore a backup using this method do i just restore from the rom manager in cm7?
[Nook Color Android Development] jhnstn00:
I'm not sure rom manager would do it. I would go into recovery via rom manager,then look for restore then restore from clockwork mod.

Sent from Continuum 2.2 w/ Sensation 1.2 (Awesome)
[Nook Color Android Development] rickpref:
If you did the nandroid with an SDCard recovery then you would need to do a nandroid restore from the SDCard recovery. If you did it from the emmc then restore from the emmc. I just flashed the 3.0.0.6 Recovery to the emmc, did a nandroi backup. Tried Ultimate Droid Nightly 11-22 (crapped my Nook). Went back into the emmc recovery and restored CM7 with no problem.
[Nook Color Android Development] newellj79:
Got it. Thanks!
[Nook Color Android Development] 18.4009:
Sorry I'm sure this has been asked but how do I access my internal storage through root explorer? I go into emmc and its empty. Same with /mnt/emmc.

Thanks!
[Nook Color Android Development] newellj79:
All of the sudden I'm having spontaneous rebooted with nightly 7. 3 times in 5 minutes. Anyone else?
[Nook Color Android Development] jimmy87lee:
I was able to fix this by downloading the LCD Density app and then selecting the density option that is one less than the default.
[Nook Color Android Development] openallnight:
Hi,

First of all CM7 is awesome. I have never seen as many apps on the market even in Froyo. Running into a couple of issues though

1)Maps is force closing

EDIT: This was breaking as i had changed density to 160. worked after changing density to anything above 160. I used 161.

2)Auto sync is not working (I dont see notification in top bar on getting gmail or any other auto sync configured email for that matter).

Are these known problems and are there workarounds or solutions? #7 is my first CM7 experience.

Other issues:

3)XDA app crashes while viewing threads after login only. Just browsing anonymously works fine.

4)ROM manager is unable to get super user privileges. Get error performing privileged command. Is there a way to add it manually to allowed app list?

Edit: Reboot fixed Rom manager issue
[Nook Color Android Development] adma84:
did not work for me unfortunately (although I did it by hand) I changed to 179
[Nook Color Android Development] jimmy87lee:
I meant the pre-configured buttons. Since 180 seems to be the default, try 160.

edit: 170 seems to work too
[Nook Color Android Development] digitalslacker:
Thanks!

I downloaded LCDDensity for Root

default was 180, set it to 160. restart

worked great!
[Nook Color Android Development] racks11479:
Yeah. I'm at 160 at it looks fine except for the keyboards buttons. They are slightly smaller that the space provided.
[Nook Color Android Development] FletchF:
Bummer. It worked on rooted 1.01.
[Nook Color Android Development] Ronin3178:
I think thats a question for fattire.
[Nook Color Android Development] kLAcK107:
Planex MZK-W04N

I'm going to try switching to WEP to see if that fixes the problem.
[Nook Color Android Development] kLAcK107:
n87 complete reflash and wipe

Planex MZK-W04N: Can't get a solid connection no matter what

Have tried: TKIP, AES, WEP, NO SECURITY, G ONLY, FACTORY REST

EDIT: flashed to update-cm-7.1.0-RC0-encore-2.6.32-beta3.1 and wifi working good

now I can play my tegra games....
[Nook Color Android Development] boxcar8028:
I see in the change log there are fixes and the devs are testing. does anyone know what are fixes are? or how the testing is going. I'm keeping my fingers crossed.
[Nook Color Android Development] :
Just messing with a recovery.
[Nook Color Android Development] funcrusher:
Did a clean install of nightly 87 w/ 5-23 OC kernel -- everything is working great. No more SOD and battery is fantastic. Haven't really watched any video, so I can't comment.

Great work!
[Nook Color Android Development] fattire:
The cyan edition of u-boot is similar in features to the multi-uboot you referenced, but not exactly the same in functionality. They do more or less the same thing, although the cyan edition also provides an interactive menu to override default behavior as well as user-feedback so you know when you've hit the right button combo.

Also, the keypresses are slightly different to maintain backwards compatibility with power-N still being recovery.

And instead of a u-boot.order file, there is a u-boot.device file that allows you to pass boots "through" SD to load off of eMMC (which could then be overridden by the menu). u-boot.device affects the location of both the kernel and ramdisk.

There is no u-boot.altimg and u-boot.altram as the file names always default to uAltImg and uAltRam.

The Cyan Edition is also based off of BN's 1.2 u-boot source.

See j4mm3r's excellent description of the functionality.
[Nook Color Android Development] succulent:
I don't know if I have deep sleep or not. At random (rare) time after I put my NC to sleep and try to turn it on (even at full power), the screen won't turn on. But if I turn the volume up, I can hear the volume beeps. Sometime if I repeatedly press the power button, the screen would turn back on. I am using nightly 87, 1.2 uboot, and 5/23 OCK.
[Nook Color Android Development] bekyndnunwind:
On beta 3.1 w/ 5/23 OC and everything was peachy (besides PBD) but now my nook isn't sleeping. Its idling at 300, I'm going to restart and see if that fixes it.
[Nook Color Android Development] only one haze:
responded in j4mm3rs thread
[Nook Color Android Development] angomy:
Just had a weird crash on my freshly installed nightly 87 --- tried to change wallpaper with Quickpic after futzing around with some ebooks in FBreader. It took forever for Quickpic to process setting the wallpaper, and it came out completely black (blank) behind my icons. Tried to reboot and reboot menu wasn't coming up -- screen was just turning off. When I held it for longer than usual the CM7 Skaterdroid came up (no menu asking if I wanted to reboot, turn off, etc). Once CM7 booted up the wallpaper was showing normally.

Is there a place somewhere in CM7 that outputs an error log I can read?
[Nook Color Android Development] sinanju:
Phantom typing when using stock charger...

... appears to be gone. I just noticed. An unadvertised .32 improvement?
[Nook Color Android Development] Xhorder:
I'm just gonna ask a (possibly stupid) direct question:

Does the cyan u-boot support a dual boot (both on emmc) setup, like rookie1's u-boot does?

See thread, specifically his example config 3:

http://xdaforums.com/showthread.php?t=947698
[Nook Color Android Development] fattire:
Yes. The alternate boot is described above and in j3mm4r's thread.
[Nook Color Android Development] RoboRay:
Never had that problem even on stock. :confused:
[Nook Color Android Development] bigbob23:
I finally bit the bullet and installed CM7 (nightly 87, Dalingrin's OC kernel) on eMMC instead of the SD card. I also edited build.prop to get rid of the chipmunk effect on Netflix. All looks fine (I'm sure I'll figure a way to screw it up)

Thanks to all of those who have made this possible ;)

Edit:

I just noticed a new problem. After I edited /system/build.prop to get Netflix working correctly (using HTC Vision), the Nook app could no longer download books from B&N. It gave an error message saying to contact Barnes & Noble. After changing build.prop back to the original, downloads worked again.
[Nook Color Android Development] Xhorder:
Ok, I got it. All I had to do was rename the UEImg and UERam that were still in my /boot directory to UAltImg and UAltRam.

Thanks!
[Nook Color Android Development] greenmky:
Phantom key presses is a hardware problem. I'd return it. A good NC doesn't do that, even on the charger.
[Nook Color Android Development] sinanju:
Two things:

-B&N's response to a report of the problem was, "Yeah, they do that. Leave it alone when it's charging."

-As I said... the issue is gone...Why would I return it now?
[Nook Color Android Development] camalus:
That's not a problem. Its what happens when you edit your build.prop to something that is not your nook.

Its a give and take to use Netflix. Just one of those things you have to deal with.
[Nook Color Android Development] bigbob23:
That's what I was afraid of. Hopefully Netflix will update the app to actually support the Nook Color.
[Nook Color Android Development] GabbleRatchet:
Its a bad charger, not a bad nook. The charger that came with mine did it, but I was able to test others until I found a good one. Seems to be about 50/50. Out of curiosity, was that response from customer support or a store employee?
[Nook Color Android Development] RoboRay:
No, they DO NOT do that.

When the NC first came out, B&N replaced a lot of bad chargers that were causing touch screen problems while connected. You probably got one of those.

Did you get the NC recently or have you had it for several months?
[Nook Color Android Development] GSUBass05:
I just downloaded a book yesterday from the B&N Android app. I've made the changes in build.prop to allow for netflix streaming. It might be something else. Have you checked to make sure your credit card information is up to date on the B&N website?
[Nook Color Android Development] dexx0008:
this is why it would be nice to know why this (chipmunk voices) started in the .32 kernel. since netflix removed the device requirement from the app in it's update you wouldn't need to update build.prop

The post above says the problem might be unique to your device which is good because I do have to edit the build.prop for another reason, and it gets annoying to modify it and restart it all the time when you want to use various apps.
[Nook Color Android Development] khaytsus:
No problem here, I downloaded several free books today.. Using the two-line build.prop update.
[Nook Color Android Development] bigbob23:
That's good to know. Perhaps my experience was a glitch of some sort.
[Nook Color Android Development] danvee:
Hi bigbob!

Did your glitch cure itself? I'm experiencing the same thing using the same builds. I don't remember this happening back with R85/latest OC kernel. I'll have to reload that version and check out the Nook app.
[Nook Color Android Development] LongbowFoSho:
So what is the best nightly for a battery life and stability?

PBD started on nightly 87, right?
[Nook Color Android Development] newellj79:
I believe it started with 84, the first official .32 build.
[Nook Color Android Development] LongbowFoSho:
Is 84 pretty good on battery life and stability?

I'm putting this on a very un-tech-savvy friend's NC, so I need something that I won't have to tinker with on a daily basis.
[Nook Color Android Development] newellj79:
For me 86 which is the same as 87 has been rock solid.
[Nook Color Android Development] Deaks2:
In that case I'd stick with 7.03
[Nook Color Android Development] buzz killington:
I had it as far back as nightly 75, when it was still on .29 with the stock 1.2 uboot.
[Nook Color Android Development] only one haze:
Thanks for posting this. I have seen nothing mentioning uEImg and uERam and kind of overlooked them. Got the cyan version working now!
[Nook Color Android Development] nolook:
87 has been rock solid -massive upgrade from honeycomb

I don't seem to have any battery issues either.....
[Nook Color Android Development] LongbowFoSho:
This ROM absolutely rocks. Combined with the new OC kernel, this makes the Nook into a true iPad killer for realz.
[Nook Color Android Development] nicros:
General CM7 questions

Running the 87 build on my NC- love it so far!

Couple of quick questions...

1. On a friends nexus one phone, the app display has a really nice 'wrapping' effect for scrolling apps on and offscreen- anyone know if there is a setting to get this to work, or know how to get it to work at all?

2. For themes, how does this work? I have a ADWLauncher section under settings, where I can set a couple of themes. And then in apps, I also have a little Theme Chooser. In downloading themes from the market, it seems that these are somewhat independent things... Primarily I would like to change the appearance of the battery icon and things on the very bottom bar- is it possible?

And lastly, whenever I add the google news and weather widget, regardless of what size I make it it shows a tiny little weather icon and maybe one news story- if I ask it to take up more space it does- but does not show any additional data. Is it possible to make this widget show more data? I would like to turn my nook color on, and see maybe 10 headlines and a good weather summary- can it be done and how?

Thanks!
[Nook Color Android Development] Lyphen:
Is USB mounting of eemc/sd available in any of the newer nightlies?
[Nook Color Android Development] jkabaseball:
I am having issues with GApps. I am switching back to CM7, so I grabbed the latest and greatest. I installed the 1.2 fix, then CM7, the OC kernal, then gapps, and it doesn't show when I boot up. I tried another version of GApps and same thing, nothing is listed. I can't even add a gmail account. Did something change? Want the latest and greatest but not if I can't get apps.
[Nook Color Android Development] bucketheadmn:
n87 and tablet tweak bar fore close

n87 is running almost perfectly for me. The only problem I seem to be running into is that the tablet tweak bar force closes - most of the time it will come right back, but a couple of times I have actually had to reboot.
[Nook Color Android Development] newellj79:
There is a free app in the market called "notification restart". All it does is restart the status bar, its genius, a must have for us right now.
[Nook Color Android Development] bigbob23:
When you plug in a USB cable, it will show a USB icon in the status bar. Press the circle with an up arrow and you will see "USB connected". Press that and then press "Turn on USB storage" followed by "OK". Both the /emmc and /sdcard partitions will be mounted.
[Nook Color Android Development] hungryTux:
Hi I'm on n87! Must say its been pretty rock solid so far. I just have one question though. I don't see the USB debugging enabled notification in the status bar when I connect my NC to my Mac, just the option to turn on USB storage. I have the debugging option enabled in the settings. 'adb devices' doesn't return any output presently. How do i get this working?
[Nook Color Android Development] pryonix:
ISSUE #1

Which build are you running? Please mention any customizations: CM7 Nightly 87 using Dalingrins OC Kernel 5/23 at 1.2Ghz running on SD.

App or process having the problem: -

Steps to reproduce the problem: -

Describe the issue as well as you can:

The NC turns off by itself (completely off, not just sleep). This has happened to me twice already since I installed CM7 N87 the other day. I used to have Phiremod 6.2 and never encountered this issue. I've never had the NC suddenly shut down on me though while I'm actively using it.

Observations: Both times it has happened were times I left the NC alone for extended periods of time (meaning more than 30 mins) without the power cord plugged in AND moved out of wifi range (or wifi turned off temporarily). I cannot ascertain so far if losing wifi triggers this since the 87N frequently loses the wifi (see next section for wifi problems) signal but does not shut down

Relevant logs(logcat, dmesg): -

----------------------------------------------------------------

ISSUE #2

Which build are you running? Please mention any customizations: Same set-up as previous

App or process having the problem: Wifi

Steps to reproduce the problem: -

Describe the issue as well as you can:

There are two problems w/ wifi:

1) NC will lose internet connection via wifi (icon will turn from green to white meaning that it is still connected to the wifi but loses the internet part of the connection). Occurrence: FREQUENT. Happens at least twice every hour. Workaround is to turn wifi on and off. Sometimes it fixes itself.

2) NC will lose wifi signal (icon will turn show extremely reduced wifi signal even though I'm sitting beside the router and all my other wifi-devices show full strength). Occurrence: MODERATE. Happens at least three times a day. Workaround: None needed so far since I can still surf/download fine. It's very annoying though.

Relevant logs(logcat, dmesg): -
[Nook Color Android Development] fattire:
See PBD discussion. Do you know if you had this problem before using the OC kernel?