[How-to][NEW VERSION] Run Nookie Froyo off SD card

[AHfootball12]

Still having a sizing problem on the new version of FROYO

icons are REALLY spaced out, and notifications tab comes in VERY small in the center of the screen. Also, widgets are TINY and some are in turn hard to read

Is anyone having this problem where you can literally fit your thumb between icons?

I tried switching the launcher to Zeam and am doing 5x5 and the problem is still there.

Anyone having this problem or no?

Using the Zeam launcher I fit things to be 6 icons by 7 icons. This shrunk the spacing between icons to make it more tolerable, only my home screen now looks like the application launcher screen and my widgets are kind of deformed.

It seems that the system files act as if they are on a phone. Only way to explain it is when you launched a application that didn't go full screen? That is the size of my notifications window and ALL icons are the same size as on my Incredible. VERY frustrating that I can't take advantage of the larger screen and have to focus to read things.

No one else is experiencing this? For everyone else when you pull down the notifications window the entire screen is filled in just like the first version?

 

[ddigby]

It seems that the system files act as if they are on a phone. Only way to explain it is when you launched a application that didn't go full screen? That is the size of my notifications window and ALL icons are the same size as on my Incredible. VERY frustrating that I can't take advantage of the larger screen and have to focus to read things.

Anyone running 0.6.6 or 0.6.7 is going to see the same behavior. Most people probably don't think much of it because they've dealt with it before. You need to edit your /system/build.prop file and change the ro.sf.lcd_density to a higher number. The default on 0.6.7 is 160, I think the default on 0.5.9 was 250 if that's the look you're going for.

As far as how to edit the build.prop, you can follow the instructions on #2 in the Nookie Froyo tips thread, except you'll be changing ro.sf.lcd_density instead of the build fingerprint.

 

[bjordan]

Starting to regret this choice....

Unfortunately I can't help you answer the issues and questions you have. I've only had my NC for 2 days and haven't had a lot of time to mess with it. I do have Nookie on one SDcard running but it's not currently in my NC. I don't remember what the notification area looked like. I do remember the lockscreen was small. However a reboot solved that.

I also have another SDCard running the Honeycomb v4 preview ROM. I put it in just to check it out and didn't expect it to be usable (it is a preview). I was pleasantly surprised. I've been using it instead of Nookie for the past day and really like it.

Before you return your NC or really regret it I'd strongly suggest trying the Honeycomb preview ROM on an SDCard.

It doesn't suffer from the visual issues you are describing. The only main issue is in Portrait mode the notification area is off screen (when opened) because it thinks the screen is bigger. It's not a huge issue though. In landscape it works fine.

I'm not trying to derail this thread so any additional Honeycomb content/questions should probably be posted in this thread.

http://forum.androidcentral.com/bar...oad-install-honeycomb-nook-color-sd-card.html

However I did want to mention it here.

 

[viscosity22]

Anyone running 0.6.6 or 0.6.7 is going to see the same behavior. Most people probably don't think much of it because they've dealt with it before. You need to edit your /system/build.prop file and change the ro.sf.lcd_density to a higher number. The default on 0.6.7 is 160, I think the default on 0.5.9 was 250 if that's the look you're going for.

As far as how to edit the build.prop, you can follow the instructions on #2 in the Nookie Froyo tips thread, except you'll be changing ro.sf.lcd_density instead of the build fingerprint.

great advice, that's exactly the info I was looking for too, thanks!

 

[AHfootball12]

Anyone running 0.6.6 or 0.6.7 is going to see the same behavior. Most people probably don't think much of it because they've dealt with it before. You need to edit your /system/build.prop file and change the ro.sf.lcd_density to a higher number. The default on 0.6.7 is 160, I think the default on 0.5.9 was 250 if that's the look you're going for.

As far as how to edit the build.prop, you can follow the instructions on #2 in the Nookie Froyo tips thread, except you'll be changing ro.sf.lcd_density instead of the build fingerprint.

You are amazing.

 

[MrG]

following up on this..... when I pulled the NF SD card out (NFv0.6.7), and allowed the nook to boot into the BN reader, I was not able to power it off! According to the OP, the NF SD programs do not affect the original nook code? I was able to finally turned it off after I tried repeatedly holding down the powerbutton and pressing N. The NC I started with was brandnew with firm ware 1.1. Anyone else notice this?

 

[sydmusic]

Mac OS -specific question

Hello everyone. I had a thrilling, if at some times harrowing experience first rooting my nc then finding the froyo sd card install preferable. I stumbled my way through most things without a hitch (thanks to all the incredible hard work of the folks here) and the only remaining hiccup I'm having is installing the google apps using adb from my Mac. I know adb is running. I know I need to invoke it from within the program-tools directory and start each command with ./ adb. And I'm able to run ./ adb --help and see feedback.

But that's about as far as it gets. When I copy and paste the terminal command from the OP, even if I alter them to begin with ./ adb they will return a device not found error. my nc is plugged in and I've tried in both USB debugging mode (not mounted on desktop) and in USB storage mode (mounted).

One thing that seems to have changed quite recently is that adb resides in the program-tools directory instead of the tools directory. Is it possible the system folder from google apps needs to be in program-tools instead? If so, how would this change commands required? If not, any advice on what I might be doing wrong? I think this has everything to do with os x terminal.

Thanks again
S

UPDATE: Some googlin' in the light of day and I think I'll have a better idea what to do when I get home. Bash profiles, etc. So...hold that thought....

UPDATE2: For anyone googling wondering why Terminal won't see the Nook Color when you ./adb devices -- THIS is the piece of code you're looking for. It needs to load a driver:

sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; ./adb kill-server; ./adb devices"

 

[techienana]

I don't know if anyone else was as confused as I was trying to use adb.exe to install the Google apps but I finally figured out what I was doing wrong. I followed the instructions exactly but was always getting the adb error message. Turns out that for me it was something as simple as turning on USB storage on the Nook so that I could transfer files. DUH!

 

[rc28a]

Wow just installed this.amazing

 

[jscottcollins]

This would not work for me at first. I did some searches, and it turns out that in order to push the google apps to the nook, the app super user must be open on the nook. After i figured this out everything worked great. This is especially pertinent to those who are experiencing the protocol fault error.

 

[MrG]

Need some help. I keep getting an error when I try to install the flash apk on NF0.6.7. Same error with app manager or via adb saying I need to free up some space. I've deleted data/cache but don't know whatelse to do. got a 8gb card which reads correctly as Gb capacity (use the aesus partition manager in tips).tks

 

[rootkit123]

I've previously built up a *working* Froyo SD card on a Class 6 16GB card. I just got a Class 10 4 GB card in the mail and wanted to use that instead.

I've followed the exact same steps I did for the working 16GB card -- basically, burn the image to the card, pop it in the NC, and power on. However, with the 4GB card, it fails to boot to the card every time, the stock ROM loads and treats the 4GB card as storage.

Is this the "SD mount problems" alluded to in the OP? I'm using 0.6.7. It's really bugging me that I've got it to work with one card but not another.

EDIT: I was able to burn and mount a different 4 GB Class 10 card by the same manufacturer (Kingmax). So I guess this problem was just limited to this card? I know the process doesn't create identical cards every time, but man alive. Lesson learned, I guess.

 

[roberto]

Uninstalling apps

I installed Froyo on a SD card and it is up and running. There are a lot of pre-installed apps that don't apply here (mainly camera & phone related) but when I try to uninstall them (Settings -> Applications -> Manage applications) the Uninstall button is greyed out (it is available for apps which I have installed, however).

Is there any way to uninstall these unneeded applications? It would free up a small amount of memory plus unclutter the Apps screen.

 

[drwohl]

Missing apps from the market?

I've got Nookie Froyo running fine from the SD card (thanks!!), but there are several apps I can't seem to find on the market. Facebook, for example. And Dolphin Mini browser. Not having a Facebook app is a bit of a problem, and I love using Dolphin Mini on my rooted NC. Any idea what's going on here?

 

[dcreed]

drwohl:
You may need to change your Nook Color's fingerprint for more apps to show up in the marketplace. Here's a quote from another thread:

Open Root Explorer, navigate to system/, mount as r-w, and open build.prop in a text editor. Find the line that starts with ro.build.fingerprint= and change it to the following:

ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys

Now from your homescreen, hit Menu>settings>Applications>Manage Applications>All, and find Market. Select clear cache, and then force stop. Then, still under All, find Google Services Framework, and hit wipe data, and then force stop. Reboot, and many more apps should show up!

BE VERY CAREFUL changing that line in the build.prop file; I f'd it up once and had to start over. Might want to just comment out the original line (add a # before it) and add your own. Working in Landscape mode makes it easier to see linewraps, too.

 

[drwohl]

drwohl:
You may need to change your Nook Color's fingerprint for more apps to show up in the marketplace. Here's a quote from another thread:



BE VERY CAREFUL changing that line in the build.prop file; I f'd it up once and had to start over. Might want to just comment out the original line (add a # before it) and add your own. Working in Landscape mode makes it easier to see linewraps, too.

This is probably a stupid question, but once I've mounted system as r-w, how do I open build.prop in a text editor? Is that within Root Explorer?

 

[dcreed]

Yah, do a long-press on build.prop in root explorer. One of the options on the popup is "open in text editor". (One of the options is also copy, which might be a good idea.) By default a tap on it opens it read-only.

 

[Pink Freud]

Ok, It's time to admit that I need help.

I bought a NC last weekend and got it on Wednesday, and had no intention of risking rooting it until I heard of the nookie Froyo SD card boot. I installed Nookie Froyo 0.6.7 on a 16GB Sandisk Ultra class 4 card using my Toshiba Win7 laptop Sunday morning and it works great. I Even got the Google apps loaded after figuring out that I needed to set the screen to not time out after 15 seconds. It's downright beautiful, and you guys rock the house.

The main problem I've had, though, is with the carnfugled sdcard partition. It refuses to show up in Windows 7, regardless of what I try. I've been jacking with it all day today and all night, and nothing works. I've tried loading vold, and a dozen other methods that I can't remember at the moment because my brain is fried to a golden brown, then I started over completely, re-burning the image to the sdhc card again and trying all the methods once more. I had hell trying to get the dev kit drivers to load, and had to force windows to use the "Android adb interface" one, and even tried the other two, "android bootloader interface" and "Android Composite ADB Interface". No dice. When I plug the NC in, I can see the storage devices appear in Windows Explorer for a split second and then they disappear.

Also during all of this, I noticed that on my NC, under "SD Card and Phone Storage", that the SD card only showed 800MB of storage space. After a lot of searching, I found out that this is standard and that you have to use a partition program to change it. I thought to myself, "Well I better fix that before the not-showing-up thing." so I downloaded "Minitool Partition Wizard Home Edition", located the card's "sdcard" partition and resized it to 13 GB. Plugging the card back in, it now tells me that the SD card is damaged and won't mount it. I tried resizing it again to 12 GB, and even telling Minitool to format it in FAT32, but it still says the same thing. I loaded vold again, just for a why-the-hell-not, and still no change.

I am extremely tired now, so I am going to sleep and praying that when I get up tomorrow some kind soul will have posted information that might aid me. Thank you, in advance, for anything at all that can be useful. I know it has to be something simple that I'm missing, but I cannot divine the answer alone.

I think I'll have a shot of whiskey before bed.

 

[rootkit123]

I think I'll have a shot of whiskey before bed.

Well, you're able to get a working card. That's a start.

I'm not sure what you mean when you state that Win7 couldn't "see" your sdcard partition. In the sense that you couldn't write to it from Windows by, say, navigating to my computer and double-clicking on a folder called "sdcard"?

You might need to restore your card to being bootable, then resize the sdcard partition, then boot into it on your NC. Now use adb to sniff out the sdcard partition. Try something simple like "adb shell ls /sdcard" (I was able to use the ls command to see my sdcard from adb -- I can't recall if that was the exact syntax.)

I can't guess at your intentions, but if the thought was that you could write/read to /sdcard from Win7 as though it's another windows folder, that ain't happening. You need to push/pull files to that directory using the appropriate adb commands or something like Browsix/Dropbox. See here.

 

[vor]

You need to resize the sdcard partition with Easus