yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] cybertimber2007:
Did a card format & installed 0.6.7 to see if it fixed SD mount. Unfortunatley, the fix didn't work for me. When I enable USB storage, my computer brings up the "boot" parition :(

Suggestions?

On the plus side, the apps I searched for showed up without needing modification to build.prop! Also to the above poster, youtube is working for me.
[Nook Color Android Development] Moricon:
Thank you for this. on .0.6.7 as of today with the 1gh kernal running off a old Patriot SD card. Have a new class 10 due on Friday so it should be even better but not bad now at all.

2 issue (niether major)

Phantom voice when trying to play a youtube video

XDA app FC when trying to look atthreads.

Anyway great work. Love that fact that I can have this and NOT have to root my stock nook.

Thanks again
[Nook Color Android Development] smcmanus:
I've got everything syncing properly on my NC .6.7 build. I had to pull the GoogleCalendarSyncAdapter.apk off of my phone (EVO) to get that option to even show up under Settings -> Accounts and Sync. It works just dandy.

Needs to be installed to /system/app, chmodded to 06755, and then you reboot, and you should be able to sync.

My issue is 2 fold:

1. I've posted before about getting the /media partition to mount in os x (any os, actually) when usb storage has been started, and I'm connected to my laptop.

2. Has anyone noticed that when you reboot the nook, if you've got 0.6.7 on the eMMC, the /media mount point is empty?
[Nook Color Android Development] thecalip:
youtube works fine for me. install to emmc
[Nook Color Android Development] Homer_S_xda:
So, does anyone else have a problem with Terminal Emulator? I cannot get the number keys to work on whatever keyboard it is using.

Homer
[Nook Color Android Development] Quilombo:
Quick question: I installed this on my SD just to test the performance but later decided I wanted to use my eclair version on /emmc. I shut it down, removed the SD and rebooted but now it wont go past "touch the future of reading" screen. Any thoughts?
[Nook Color Android Development] philburkhardt:
Thanks for pointing me towards No Lock. It totally did the trick. I don't have a lock screen, but I can wait until the kernel issues are worked out.

I HIGHLY recommend No Lock for anyone having wake issues.
[Nook Color Android Development] taylor.fowler:
I havent had any issues with the numbers. However, the keyboard became super laggy when running the top command in busybox (as did button savior menu button).
[Nook Color Android Development] eismanxda:
SDCard problem fixed the permissions on /system/bin/vold were wrong. I did chmod 775 /system/bin/vold and used the below /etc/vold.fstab. After a reboot all was well. Fix permissions probably would have done this too.

Here is my /etc/vold.fstab

## Vold 2.0 Generic fstab
## - San Mehat (san@android.com)
##

#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################

## Example of a standard sdcard mount for the emulator / Dream
# Mounts the first usable partition of the specified device
dev_mount sdcard /sdcard auto /devices/devices/platform/usb_mass_storage/lun1/file /devices/platform/mmci-omap-hs.0/mmc_host/mmc1

## Example of a dual card setup
# dev_mount left_sdcard /sdcard1 auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# dev_mount right_sdcard /sdcard2 auto /devices/platform/goldfish_mmc.1 /devices/platform/msm_sdcc.3/mmc_host/mmc1

## Example of specifying a specific partition for mounts
dev_mount media /media 8 /devices/devices/platform/usb_mass_storage/lun1/file /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
[Nook Color Android Development] xboxexpert:
Are you flashed off the internal or running off SD? Also when you plug in the SD can you access both your EMMC storage and your SD Storage?
[Nook Color Android Development] djurkash:
No, problem, heard it from other member, thanks for my first thanks :D

I had problems even with no lock, so I installed 1GHz kernel, and using set CPU put minimum 300MHz for processor when sleeping...so far it does the trick...
[Nook Color Android Development] Keanen:
Is it just me or is the nookie-froyo-SDIMAGE.....gz corrupted? I have downloaded it many times and windows and WinRar are complaining.
[Nook Color Android Development] DatterBoy:
So based on what I have read, the image being VERY slow is dependant on the SD card. I have a patriot 8GB Class 4 and it crawls. Also seems that various brands and classes have very different results without class necessarily being the key factor. That sound right?
[Nook Color Android Development] m0sim:
I don't know what everyone else is using in terms of SD Cards, but I picked up a Kingmax Class 10 and it's been solid. It writes at about 11MB/sec, which is fantastic IMO.

If you go to Amazon and search: Kingmax Class 10, it should pop up for 30 bucks (prime eligible too).

Just my 2cents.
[Nook Color Android Development] Big-A-Rob:
Typically if you have problems with the market starting to download, but then never actually downloading you can do the following steps: clear cache, then force stop the market app, then clear data, then force close the google services framework app, and then reboot. That usually fixes any market downloading issue for me.
[Nook Color Android Development] indybong:
Anyone having issues with apps running in the wrong size (not full screen) Engadget is doing this for me.
[Nook Color Android Development] mrschmitz:
Yes. The Google Reader app.
[Nook Color Android Development] mrschmitz:
And yes, compatibility mode is unchecked in Spare Parts.
[Nook Color Android Development] indybong:
I just blew out the whole system, and reinstalled 0.6.7. Same settings, compatibility mode unchecked. Engadget now fills the screen, go figure? Good luck with your endeavors.
[Nook Color Android Development] MarcusMaximus04@gmail.com:
I'm a developer working on a game and, as such, was testing it on my nook color which is currently running nookie froyo(the latest internal memory, CWM flashable version with the vold fix). While doing so and running a logcat, I noticed that the accelerometer stats are spammed to the log constantly. I'm not sure if this is intentional or not, but such spamming to the log can slow things down a bit, I've found(it also makes debugging anything using the logs nearly impossible)
[Nook Color Android Development] mrschmitz:
Blew out the whole system...like a data wipe and factory reset, then a reflash via CWM? Or even more than that?

It almost sounds worth it. I'm running off eMMC, by the way, if that is different...
[Nook Color Android Development] danbutter:
Every few apps I try seems to be the size of a phone screen, but after closing them and opening again or rebooting they all seem to fill the screen.

The only thing that hasn't filled the screen is the notification drop down.

Don't really care about that as it can be read well enough and there isn't much interaction with it.
[Nook Color Android Development] Big-A-Rob:
So I'm NOT the only one with this issue. I don't have the issue with any apps, but the notification drop down is tiny for me.
[Nook Color Android Development] mcp2009:
Not deving but noticed the same thing. Also wondering why it's being done
[Nook Color Android Development] indybong:
Yep, Data wipe/Reset. Reflash Via CWM. I get a kick out of this stuff, so it wasn't a bother at all. I'm on the EMMC
[Nook Color Android Development] J-ROCK:
For those having issues with the small notification bar, you need to change the lcd density to 210. Download an app on the market to do so.
[Nook Color Android Development] cicada:
Protip: logcat accepts filters, and/or you can filter the output with grep or the like. This build is in debug mode as it's basically impossible to track down system issues *without* that data. That said, I do agree the orientation listener is far too chatty ;)

Once the system feels more stable to me I'll build it in release. Debugging really doesn't slow things down significantly, though, as android uses a small rolling buffer for that data.
[Nook Color Android Development] voodoomurphy:
Well I flashed and now I can't get ADB to recognize the device. So I thought I'd manually install the vendor.apk and gmail.apk from my dropbox account. They install but just flash and FC when I try to open them. Any suggestions folks?
[Nook Color Android Development] cosine83:
Three issues I'm having here that may or may not be fixable:

1) Wifi sleep policy is not changeable. It turns off when ever the screen turns off (manual or automatic) and it's kind of a pain. I've tried turning the policy off with spare parts, going into settngs > wireless and networks > wifi > hit menu then advanced and nothing does it.

2) When the screen turns off, turning it back and unlocking is iffy at best.. Oddly, when the screen turns off automatically and I turn it back on it will kind of go into a sort of wake loop where it will turn the screen on, turn off after a few seconds, then turn back on on its own. Takes a few attempts to unlock the screen.

3) The touch screen is very insensitive after booting and turning it off then on seems to resolve that issue. Any idea why this is and if there's a more permanent fix?

Also, I see sleep death a lot. Is this fixed in one of the other kernels or expected to be fixed in the next release? It's kind of annoying. I don't like the stock setup as it has a huge lack of options (in Nook Color Tools) for me since I'm used to Android on my phone.
[Nook Color Android Development] xboxexpert:
I edited my file in /system/bin to reflect your changes now my Nook doesn't power on. Even after re flashing it does not power on.
[Nook Color Android Development] MarcusMaximus04@gmail.com:
Ah, ok, so it is intentional. Anyway, thanks for the suggestion of filtering the logcat, I'll go ahead and do that in the future. Keep up the good work!
[Nook Color Android Development] jamesbra:
When I unmount and remove the sd card the system does not recognize the sd again until the system is rebooted. Anyone else noticing this?
[Nook Color Android Development] Big-A-Rob:
Thanks for the advice. I had tried that before, it did work but made everything huge. After tinkering with the values I found 180 to fix the notification drawer and keep the rest a reasonable size.
[Nook Color Android Development] HipCat:
I'm getting two loading screens and then it goes to an screen that says "ANDROID" to the side. I'm using autoNooter for 1.0.1 and flashed my SD card properly...
[Nook Color Android Development] Big-A-Rob:
I downloaded No Lock and still have the wake issues. I have tried a combination of the following: Set CPU set the clock to 300 when screen is off, wifi sleep policy set to never, removed phone and telephonyProvider apk's, No Lock enabled. I tried the 1100 and 1000 kernels. It's kind of weird because I wasn't having any problems, then it started waking but the screen was unresponsive, now anytime the screen sleeps I have to hard reboot. I kind of got progressively worse. Pretty much unusable at this point.

Has anyone found a combination of settings that might help as a work around until this is corrected?
[Nook Color Android Development] xboxexpert:
Any idea why I get a black screen on loading. I can boot off the SD but not off eMMC on anything I flash.
[Nook Color Android Development] philburkhardt:
No Lock stopped working for me too. It seemed to be working great for a while, then it was almost as if the wake issue got worse. Same thing, unresponsive screen and have to hard reboot to get it going again. I also tried the 1000 and 1100 kernels.

I started from scratch. Formatted all of the cache's, cleared data and reinstalled froyo, and gapps. This time when installing gapps, I removed some phone related apk's and the car panel. I have added back all of my apps except for my games. I have applied the nook froyo clean theme, and I have set my density to 210. I also edited the build.prop file for better market compatibility.

Everything has been running fine since yesterday afternoon. No wake issues yet. I am making a backup right now. When it is done, I will test the kernels again.
[Nook Color Android Development] willsurg:
same

hey guys, I confirm as you have found, no lock works for a while then stops, set cpu setting work for a while, same then stops. I am now 2 days with out the wake issues, and what I did in addition to all of the above , is turn off the automatic data syncing, under accounts. I unchecked both options 2 days ago, and thus far no problems. the only drawback is having to re-enable it to run the Market application, but, thus far it has worked. try it out and get back to me if somebody else has a better solution..
[Nook Color Android Development] taylor.fowler:
So far so good for me doing this (Regular Nookie froyo 0.6.7 emmc, Nookie Froyo Clean theme, 1.1 OC kernel):

1) Installing NoLock

2) Following these instructions

3) Setcpu Profile for 300mHz-300mHz while screen is off

I can use the power button to sleep/wake just fine (no lockscreen though) and have had it running pretty stable for the past couple days.

However, you need to run that terminal script every time you reboot (checking the PID number because it changes every so often)!

Edit: Looks like this worked for about 2 days or so before hitting me with the issue again. Now it seems to be happening every 8 hours or so. Ugh.
[Nook Color Android Development] ron_e:
XDA App problems

I tried searching for an answer but did not find any. Ever tried searching for XDA app on the XDA forum. :)

I just update my nook with this today. Most things are working fine. The one problem I am having is with XDA App. I run it and then hit favorites. It prompts me to login which I do. I add a couple of items, then select one. When I try to drill down to see the messages in a thread the App force closes on me every time. I tried clearing the app data and uninstalled/re-installed the app with no success.

I did a wipe before flashing Froyou to the internal memory.

Logins did not save but the XDA app at lease would let me setup favorites and would remember them each time a logged in.
[Nook Color Android Development] J-ROCK:
Seems like I have to wipe cache and dalvik, once in a while, to get youtube and other apps to work properly, or else youtube won't play.
[Nook Color Android Development] jkurl:
Great job w/ the rom. The only problem I am having it getting market to work. I installed market w/ apkinstaller but all i get is it will open and then close right away. anyone got any solutions for this.
[Nook Color Android Development] ericman77:
I did have a lil lag after installing.used it for a few days then installed this 1.1 g kernel now its alot smoother and faster. Thanks for the great rom heres the kernel i used http://xdaforums.com/showthread.php?t=925451
[Nook Color Android Development] bbtheory:
Huh, this is an excellent find willsurg!!! Tried it on my nook and it seems to work, no more sleep death!!!! Thanks!!!

Edit: Darn, it just did it again.... back to the drawing board...
[Nook Color Android Development] Biff Rosco:
So far, this combination is the only thing that has solved my wake issues. Time will tell! Thanks.
[Nook Color Android Development] cicada:
Udpated 2nd post with a warning about formatting SD.

I've confirmed that there is indeed a bug which causes the system to format /boot instead of /sdcard when this option is used.

Do not use the Settings -> SD & Card storage -> Format SD Card option from NookieFroyo!

Work is being done on a boot-fix CWM zip to recover in case you do accidentally format /boot, which will require using CWM from a bootable SD card such as IOMonster's Monster rootpack.
[Nook Color Android Development] willsurg:
of course, 1.5 hours after I post my last message, same wake issue poped up. I think its happening because I post that I am not having problems and universal flashaholic gods are bringing karma to my door. Before I saw the post above about killing mediaserver, so that others dont waste their time. I tried, which obviously did not work, to clear dalvick cache, along with all of the caches, using a market program to clear them. (it did not work) so I have used the kill mediaserver and thus far it has alleviated the screen wake. Hopefully I have paid my karmic debt by now?!?!

edit:: well that did not last very long :( , off to reflash and start from scrap!
[Nook Color Android Development] bbtheory:
Any ideas on fixing the "sleep death" issue?
[Nook Color Android Development] buffnutz1:
I found the gapps zip in here. I just don't know what to do with it now. Some install, some don't. and the ones that do, don't work. Is it flashable? Can someone give a quick tutorial? thanks
[Nook Color Android Development] cosine83:
Try these GApps. They're 100% flashable and work.

http://www.mediafire.com/?va7y3h6kys85j36
[Nook Color Android Development] jkurl:
I have had the sleep screen death a few times but other than that this thing runs pretty smooth. If anyone hasn't gotten gapps to work here is another way to do it.

ADB Installation of Google Apps:

1. download the google apps files, and unzip the file so that it extracts the folder called 'system' into the 'Tools' directory in the SDK folder. **

2. Now you'll open a command prompt in Windows (start menu>run>type 'cmd') and navigate to the correct folder (cd [folder directory's path]). On Mac, this would be done via Terminal.

3. Now, with your NOOKcolor connected to your computer's USB port, type the following (of course, hit enter after each line):

adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system

adb push [here, enter the path to your SDK tools folder]\system system/

adb reboot

4. Now your NC will reboot. When it boots, you'll have Market, Gmail, Google Maps, and many more Google apps.

* If you're getting a "device not found" error when running adb, download and unzip this file, open install.exe, and follow the on-screen prompts (this will install drivers so your computer will recognize the nook).

Here is the link http://forum.androidcentral.com/bar...ion-install-nookie-froyo-internal-memory.html

I ended up putting the tools folder in the platform-tools and it made it just easier to push the apps. I would take the vending.apk out and put the newer market apk in its place. Also I have found facebook comes w/ it but I get a force close when I open it. Hope this helps some people out.
[Nook Color Android Development] philburkhardt:
FYI: You can put the gapps right in the platform-tools folder. No need to do anything with the tools folder. Also, you can drag & drop the gapps system file into the command prompt after you type "adb push". Then you can put the gapps system folder wherever you want, and you don't have to figure out and type the whole path.

You can also open the gapps folder and remove any apks you don't need, like the facebook one. I removed all the car panel stuff, and a few other things.
[Nook Color Android Development] jkurl:
Yep I have been pulling and pitting updated versions and testing stuff stupid Facebook still doesn't work. I really don't use FB but this tab is for my wife. I just installed FB full version. I just left the car app in got tired of messing around w/ it. Thanks for the info. That will make it easier next time.
[Nook Color Android Development] Homer_S_xda:
You could always go here first.

Homer
[Nook Color Android Development] buffnutz1:
I flashed them with CWM and it didnt work. I get the android with the triangle and exclamation.
[Nook Color Android Development] long2know:
Anyone have a link to a working YouTube APK with HD/HQ support?
[Nook Color Android Development] dillydawes:
The only thing that i can think of that doesnt work for me is youtube and the net work wont work after it wakes up after sleep....but i just use a widget to get it to work ....by turning it off and on.

Secondly there is some apps that FC but i expect that from a dev build...... let me know where i can donate to the project, my paypal and testing is the only way i could contribute to the project.
[Nook Color Android Development] Nooter:
Actually, there's a much easier way to reformat/repartition than using a tool on your PC: use your Nook!

As noted below, ONLY DO THIS IF YOU HAVE ECLAIR AS YOUR DEFAULT BOOT OS.

To reformat your card: remove the microSD card, reboot out of FroYo and into stock (Eclair), then insert the microSD card. You can then go to settings -> device info -> SD card -> unmount, then format to get your original card back.
[Nook Color Android Development] xenithorb:
FYI: Do NOT do this in Froyo (as casually noted by the author), it will render the system unsuable upon reboot. IIRC, it formats /boot, by accident.

Just thought that was worth mentioning, again.
[Nook Color Android Development] Nooter:
Good point! I have updated my original post to reflect this.
[Nook Color Android Development] HotShotAzn:
Did this issue every get resolved? I am having the exact same problem. I tried flashing CWR via ROM Manager and it says it was successful. Then I tried rebooting into recovery from Rom Manager and it goes straight into Froyo. Than I tried it in a terminal (reboot recovery) and it just reboots back to Froyo.

Any help?
[Nook Color Android Development] cicada:
This should be an entirely unecessary step - if you used my flashable .zip to install NF 0.6.7, you already had CWM installed. You don't need to 'reflash' CWM after installing.

If you're running from the SD card, CWM is not supported while the card is inserted - the NC chooses the bootable SD card first, and NF's SD image does not contain CWM.
[Nook Color Android Development] HotShotAzn:
Hmmm, interesting. I did use your zip to install NF. I had a different version of Froyo and the same thing was happening so I thought I would try to flash your version.

I'll go back to stock and try it again...
[Nook Color Android Development] HotShotAzn:
Well, I'm not sure if I had junk files or what but I booted to CWM via uSD then flashed my backup 1.1 files. Once it was in 1.1, I booted to CWM an flashed cicada's image (again) and now I'm in Froyo with working CWM.
[Nook Color Android Development] ulimtong:
I only have 942mb spaces for apps.

I installed Nookie Froyo 0.6.7. It is working great and I love it.

But I only have 942mb for user space according to Mini Info apps.

As far as I know there should be 8gs of totall space. I should have more space at least even after Froyo OS. Does any one know how to get more space for installing apps?
[Nook Color Android Development] philburkhardt:
That is the internal app storage. All apps, even the ones that CAN run from the SD, still deposit information to your internal app storage.

If you get an Apps to SD ap from the market, that will move most of the information for some apps to the SD card. When using an Apps 2 Sd app, you will notice that only part of the app is moved to the SD. The rest remains on the internal storage because that is where it needs to be for the app to run. You will also notice that widgets are unusable if you move them to the SD card. The problem that I have run into with Apps 2 SD apps is that every once in a while it stops recognizing the app on the SD.
[Nook Color Android Development] ulimtong:
Thank you for your reply. I am running Nookie Froyo from eMMC. Where can I find the missing space?
[Nook Color Android Development] adma84:
so...I was prepping to flash to internal emmc, and formatted boot, system, cache, and data...

don't think I was supposed to format boot

now, all I get is a black screen. Can't get it to do anything, or even boot off of my monster IO card, any ideas? seems kinda bricked
[Nook Color Android Development] djurkash:
You must use CWR from SD card...and don't worry, if you bricked it, you`d be the first...
[Nook Color Android Development] adma84:
yeah, using my monster IO card, which I have used to do all backup/restores... but all I get is black screen, had to hold power + N for over 30 seconds to fix it...that felt close :)