yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] 911jason:
When you're in a book, hit the menu button to bring up the various Kindle app options. The one on the top right is GO TO which normally brings up options to go to the Table of Contents, the Beginning or a Location. Since the Kindle app won't sync non-Amazon books between devices, I have always just manually entered the location number to go to the right page. In Honeycomb, when I press the GO TO button it just closes the whole menu and returns me to my book without opening the window to enter a location.
[Nook Color Android Development] richdaley:
I see what you are saying. Mine does not work either but I can long press on the book on the home screen and choose Go To Location.
[Nook Color Android Development] jackal424:
Thanks for the tip. Im up and running.,

Love you guys.
[Nook Color Android Development] gsmhelper:
Thanks for hard works.

I set my NC screen time out to 1 and/or 2 minutes, but it never turn off. Any idea?
[Nook Color Android Development] shadowswittness:
Is there any news when the full release will be ? Will there be a version 3 ?
[Nook Color Android Development] britoso:
Works beautifully and its quite responsive!

thanks a lot for your hard work.
[Nook Color Android Development] 911jason:
Awesome! Thanks for the tip! =)
[Nook Color Android Development] samuelhalff:
Big thanks to Johnathan for buying me a beer. Much appreciated.

Sam
[Nook Color Android Development] macboat:
You won't be able to back up the apps installed under /system/app this way. Why not use Titanium backup?
[Nook Color Android Development] fzr-r4:
I do and did, but it only restored app data, not the apps themselves.
[Nook Color Android Development] mad1100:
I have a small question for anyone who can address it. I have gone through the process of trying to run this off the EMMC and everything appears to work properly, but when i try to boot up for the first time, I get no response from the device (yes the SD card is removed). Does anyone know what could be going wrong where it wont load? Thanks in advanced, I would really love to get this working!

As a bit of additional information, when I insert the SD card which has CWR and the HC zip, the nook loads up fine into CRW, so I know it must be something with the install but cant imagine what.
[Nook Color Android Development] fourtwentyteam:
What Rom are you coming from? Because I know at one point when I switched from honeycomb to GINGERBREAD(PHIREMOD) honeycomb had wiped my boot and I needed to restore my nook to stock. Symptoms were would not power on with or without the sd card. Sounds like you need to your nook to stock. There is a awesome site with super easy instructions on how to do this( no offence to anyone here at xda) the site is HTTP://mrm3.net/tag/nook-color/ and scroll down to nook color recover any bricked device. I got mine going again in about 50 mins or so....
[Nook Color Android Development] mad1100:
Well I tried a few different ones in the past two days including Auto Nooder, CM7, and a SD card version of HC v4. I guess its worth a shot to see if it works. Anyone else know what the problem may be?

Edit: I apparently cant even go back to stock to try again as I am getting a simple "installation aborted" in CWR. This is so depressing!
[Nook Color Android Development] constellanation:
I usually try to refrain from the I just flashed it posts, but after flashing this last night and getting to play around with it, it's really gorgeous! and once all the (to be expected at this point honestly) bugs get worked out, this will be an amazing tablet.

Thanks for y'alls work.

also this is a compliment, but I didn't think much would sway me from cm it being my usual rom of choice and all!
[Nook Color Android Development] 360Razir:
I just noticed this today for the first time. The screen goes semi-dark, but it is still on, as I can see it lit up. That explains the poor battery life on this thing.

Any one else have this issue, but then fix it?
[Nook Color Android Development] kendoori:
Are you using SetCPU with HC v4 eMMC 2nd Ed.? If so what are your settings?

Noticed that battery life is not great; albeit still usable. I own setCPU, but am a bit green about settings...I followed a recipe after I originally auto nootered. I'm mostly using the device for gapps and reading, light browsing, nothing more intense.
[Nook Color Android Development] kendoori:
LCD Density? am not using stock launcher

I'd previously mucked with LCD density (to good effect) when running Eclair. Now running HC am wondering if this is relevant to play with. I read somewhere in this thread that this messes up the stock launcher; however, I'm using Zeam... any recommendations are appreciated. Pumping this up under Eclair was worth it to me.
[Nook Color Android Development] luigi90210:
in my experience setcpu will degrade performance and battery life, plus you dont need it to overclock though as the kernel will do it for you
[Nook Color Android Development] luigi90210:
i read somewhere that 180 density was the max it can go to without messing with the stock launcher but since you dont care if the stock launcher FC's you can try what ever number you want
[Nook Color Android Development] fzr-r4:
using setcpu, it would only stay at max CPU speed for me, which would explain worse battery life.
[Nook Color Android Development] kendoori:
Mucking with LCD Density really threw off keyboard (basically squashes it). My read at this point is to not bother.
[Nook Color Android Development] luigi90210:
yep it did that to me as well, thankfully i also bought droid overclock and so far it doesnt degrade performance and it doesnt have the clock speed glitch your explaining

i recommend using that if you bought it
[Nook Color Android Development] dralibak:
Hi. perhaps the answer to these questions already exist .. but if you may please guide me to the right direction.. I tried to look these up in the threads.. but no major success.

1. my internal storage count total = 0.92 GB ! I should have 5! it's not reading correctly!

2. For the life of me, I've tried it ALL all kinds of drivers, downloads .. I JUST can NOT get the ADB to work1 I've tried android SDK, I've tried the other thread that has an automated ADB install, ...

a) in development under the application.. I should have debugging and Mock location ON right? ==> then the nook is not recognized... but if I shut it off, then it's recognized but not clickable..

b) i can't connect to the SD card!

?

3. The hard keys --> I see the button volume up and down being described as re-mapped with the added softwares... but what about the N in the middle or Menu button with the book sign.. etc ?

none of my buttons are functional as it stands except volume up and down for volume indeed.

4. I get a lot of wifi disconnections .. is this my wifi connection (adhoc) or is there an issue?

5. My Market .. I can download... but it's not storing any dowloaded apps under the "my apps" .. it's empty! what do I do about this?

6. Are there any plans in the very very near future for any updates?

Thanks for your replies in advance.
[Nook Color Android Development] BKCtree:
The SD card does not have enough space to add the file?
[Nook Color Android Development] dralibak:
i have 32 GB SD card.. IF you're answering to my post .. and there's only been 1 gb used
[Nook Color Android Development] EpicFail236:
Alright, in order:

1) "internal storage" is not the same internal storage in stock. in this case, internal storage is referencing the data partition, where your android apps are installed and store their data. As of right now, there is no easy way to directly access the internal 5GB storage drive directly... we should work to fix this though. stay tuned for that.

2) ADB is difficult sometimes on the nook. If you haven't been able to access it using the drivers found in this forum, have you tried adbwireless yet? That usually gives me results, regardless of what hardware issues im having. As to accessing the sd card, have you tried the nookums storage mounting app on this forum yet? It seems to allow mounting when you are otherwise unable to.

3) I chose not to remap the "n" key in my software simply for the fact that placing your device in a position where you don't have a home key accidentally could cause serious problems. If I get enough requests to do so, I could see about getting that working, though I'll have to do some testing to see how useful it could be.

4) I have had issues with adhoc wireless on pretty much all versions on the nook except for the CM7 nighlies (and those have their own wireless issues) so you aren't alone there. As to fixes, I would usually just restart the nook when things started acting funny, then it would go away for a while. Inconvenient, but acceptable at the time.

5) that is strange... once you get ADB started up, you may want to try installing the apps directly through that and see if you have any better luck there.

6) Dunno, as I'm not the one making them, but I would assume making any more development efforts would be silly before source is released, which should be relatively soon.

Hope that helps some :)
[Nook Color Android Development] constellanation:
as for number 5 in his list, I'm experiencing the same :)

as well as the known wifi issues.

and adb is a pain on the nook! it recognizes my n1 perfectly fine but I cannot get it to find the nook.
[Nook Color Android Development] dralibak:
hi thanks for your response. I didn't get exactly (after reading your comment even though I'm sure you're being clear) why you find the n button or the book/menu button useless... at this second we don't have a home button (at least the way i see it..) and having the n button as that could be real nice..

also there there are no ways of closing all apps that open as not all have an exit in their menu... they all gather up in the notification bar... with no way to clear them... and to close them... system gets to slow down and the notification bar gets cluttered wish there was a clear button on notification button, and wish there was a button to close any or all apps...

thanks for all your efforts
[Nook Color Android Development] constellanation:
Anybody gotten gtalk to work on this build?

Edit: turns out send doesnt work but enter on the keyboard does
[Nook Color Android Development] britoso:
Is there a fix for the market not being able to install apps bug? I read on page 2/3 that it was fixed in the second version, but I'm on that and still cant install anything from the market. Adb install worked when I removed the SD card and tried. But the sd card is not detected after I re-inserted it. Will reboot.

I'm on build 20110131.162619, matches the version in the version 2 update zip.
[Nook Color Android Development] rulevoid:
I got market working by clearing cache in android framework then market then force closed both after clearing cache. After a reboot installs work fine now.

Anyone know how to get Superuser permissions working? I updated su and downloaded superuser from the market. Still nothing is allowed to even ask for permissions. Any ideas? Also my screen in portrait on the home page is missing the left and right edges, is there a way to fix the resolution in that view?

EDIT: Nevermind just realized i flashed the first version. I will try the second version now.
[Nook Color Android Development] constellanation:
My market downloads fine just doesnt show them in the my apps section of the market

Im on the 4rth version
[Nook Color Android Development] klfaulk:
So easy it's stupid

Thanks to Sam and others.

Download HC v4 eMMc 2nd ed. zip file to computer

Install zip on root of sdcard (I used a card reader to put the zip on the sdcard)

Put sdcard in Nook

Boot to Recovery (Clockworkmod and Rom Manager were already installed)

Make backup

Format system, data and cache

Use back key (nook power key) to go back to main CMW menu

Select install zip from sdcard

Select HC v4 eMMC 2nd ed.zip

Wait several minutes for install to finish (You'll get a message when its done)

Select Reboot System at top of CMW menu

Voila! There you are in Honeycomb.
[Nook Color Android Development] xdauser2008:
for noob's like me

http://tipstir.the-talk.net/t2428-nook-color-honeycomb-30-install
[Nook Color Android Development] 911jason:
You're using Zeam on Honeycomb eMMC 2nd Edition? I got nothing but immediate Force Closes every time I tried it... sadly went back to LauncherPro Plus.
[Nook Color Android Development] samuelhalff:
This applies to the previous edition...
[Nook Color Android Development] lschroeder:
I could use this approach with CMW 3.0.1.0 and rooted Eclair 1.1.0 running from eMMC. Correct? Later I might want to rename in /clockworkmod/backup/ the folder with a name that reflects date, ROM type, features.

Technically could I use this approach with CMW 3.0.1.0 or higher and any ROM in eMMC to load a different ROM to eMMC?

Do we need wiped cache, dalvik (if dalvik locks up - forced reboot to recovery) before Format system, data and cache?

If anything goes really bad what should we have on a boot-able sd card?

Sorry for all the questions.
[Nook Color Android Development] kendoori:
I did have problems with Zeam when I upped the LCD Density settings, but at defaults it works fine for me.
[Nook Color Android Development] luigi90210:
Why does the settings.db keep breaking itself. It literally is driving me up the wall.
[Nook Color Android Development] supernoman:
Running v2. Mine seems to slow down over time. The browser takes a while to load pages and consume a lot of RAM. I end up have to kill off stuff or reboot.
[Nook Color Android Development] fzr-r4:
broke last time for me after trying the beta honeycomb music player and modifying my init.rc file.
[Nook Color Android Development] luigi90210:
Well it just broke on my nook. I literally just turned it on and boom no lockscreen
[Nook Color Android Development] bdcrim:
Deleted......
[Nook Color Android Development] 360Razir:
I had same problem. For some reason with my NC, Zeam did not like the 140 'LCD Density' that was in the build.prop from Sam. I edited the build.prop to make it 160 and it is working just fine. Why it works for some at 140 and not others is beyond me. Luck of the draw, perhaps.

I also edited the build.prop to make it appear as a tablet and I am able to see some tablet apps finally (New York Times, for one). Sadly, no Google Body, so not sure what that is keying on. I think in another post someone thought it was looking for this, which can be found in the Xoom build.prop: ro.board.platform=tegra

Not entirely sure, though. Would be cool to check out on the NC, though, if it was capable of running without the need for a Tegra 2 processor.
[Nook Color Android Development] 360Razir:
Mine broke when messing with the 'init.rc' file also. Easy to get it back, just a pain in the a$$ to re-configure my settings. Mine has never just broke on its own...always user error of some sort.

I could never get the init.rc to keep my edits after reboot anyway, so I am sure that file is linked elsewhere in the build. I am pleased with what I am seeing in the Market now, so not sure I see a need to mess with that file anymore.
[Nook Color Android Development] 911jason:
Can I edit build.prop with Root Explorer and the default NC text editor? Or do I have to use ADB?
[Nook Color Android Development] fzr-r4:
Ditto here with init.rc not keeping my edits after a reboot.
[Nook Color Android Development] samuelhalff:
Init.rc is located in uRamdisk. The file your editing is a temporary image, reinitialized on each boot.

To make the change permenant, u need to edit uRamdisk (boot partition). Editing uRamdisk requires you to decompile it and building it again after having applied the necessary changes to init.rc.

See nookie froyo technical page on nookdevs for a how to.

Sam
[Nook Color Android Development] 360Razir:
I just modified it using Root Explorer's text editor and it worked just fine; kept changes even after reboot.
[Nook Color Android Development] akarol:
Loving the ROM. However, I'm wondering if there's a way to remove All Animations. I have selected that option on the Settings, but it doesn't seem to change anything. I don't like the lag when tilting, opening app drawer, etc.

Thanks...
[Nook Color Android Development] 360Razir:
I removed all animations from within Spare Parts. I am using Zeam and within its settings, I have also removed the animations for the app drawer as well. No lag with rotation for me, either in Zeam or in various apps (Gmail, email, Google Voice, etc).
[Nook Color Android Development] fzr-r4:
Just checking: does Google Voice actually run for you?

And Sam: thanks for the info on init.rc!
[Nook Color Android Development] akarol:
Why would you replace HC's amazing homescreen with Zeam's crappy looking one? I would have stuck with Froyo if that was my intention.

Also, all animations in Spare Parts were off as well and I'm still getting the little animations when opening/closing drawer, etc.
[Nook Color Android Development] 360Razir:
Yes, I recover it from My Backup Pro, which ultimately came over from my DroidX. I can send & receive messages and I am even notified of missed calls.
[Nook Color Android Development] 360Razir:
There in lies the rub....when running stock (which I have run a lot, since I keep re-building my NC to test various things), I could never get the animations to go away in the stock launcher when going into the app drawer. I don't have that problem with Zeam.

Not sure if this is going off topic, but since this is germane to HC, I would be curious to hear what you like about the stock launcher vs. an alternative one? Maybe I haven't been using stock to its full potential.

For me, one thing I like to do is re-size widgets, which helps with the size of the NC and that wasn't an option in stock. I also like that I get a menu key all the time with Zeam. That didn't show up in stock.

But, again, maybe I just didn't undress stock far enough to get a look at the really good stuff?
[Nook Color Android Development] luigi90210:
adb pull /data/data/com.android.providers.settings/databases/settings.db
C:\temp>sqlite3 settings.db
SQLite version 3.6.22
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> select * from secure where name='device_provisioned';
10|device_provisioned|0
sqlite> update secure set value=1 where name='device_provisioned';
sqlite> .q
c:\temp\adb push settings.db /data/data/com.android.providers.settings/databases/settings.db

thats how you fix the nook's home button
[Nook Color Android Development] fzr-r4:
Wow, this is the first I've heard of successful useage of google voice on HC (SDK or Xoom). I'm going to have to look into this . . . .
[Nook Color Android Development] akarol:
Well, I particularly like the way we can add widgets, wallpapers, etc. It's very intuitive seeing what they all look like and simply dragging it to the particular screen you want it in.

Now, why are you using Zeam launcher with the HC ROM? Aren't people getting better performance with other ROMs out there?
[Nook Color Android Development] fwdixon:
what exactly did you edit? I changed ro.board.platform=omap to ro.build.platform=tegra and now screen goes blank after the android_ screen. Oh well.
[Nook Color Android Development] 360Razir:
Oh, yeah, DON'T change that! :p That will def make your NC not boot, as you already discovered. Sorry that happened to you and I apologize for not clarifying in my earlier post.

You want to change this line: ro.sf.lcd_density=160

Also, just a note, if you like smaller (lower the #, the smaller the font, icons, etc), then 150 also works for Zeam. I am rolling with 160 for now, but may change it back to 150. Having used 140 for awhile, it took a bit to get used to how big things had become with 160, but some programs that wouldn't run for me previously now seem to run fine (Moon + Reader in portrait being one that comes to mind). Again, not being a dev, but more of an avid end-user, I am not sure why that is.

Hopefully you did a CWR backup before changing the build.prop file. Now that I have a good backup, I am more confident in mucking with my NC. I actually tried changing every line in my build.prop to match that of the Xoom...some things met with success, some didn't, making my NC unbootable.

One more thing, aside from changing the "fingerprint" to match that of the Xoom, I also changed this line to read: ro.build.characteristics=tablet

Not sure if that is what did it, but I am now able to see some apps in the Market that say they are for a tablet (New York Times & More Good News), where I wasn't seeing them before. Your mileage may vary.
[Nook Color Android Development] 360Razir:
Again, for me, the opposite seemed true. Now that I have no animations and in Zeam no animation for the app drawer, things are blazingly fast. I guess I also like having some icons I use often in the dock. I use Desktop Visualizer, so I don't have a lot of icons in the dock, but just enough.

Also, I forget how many rows/columns are in the default launcher, but with Zeam, I juice mine to 8 for each, as I like to use as much real estate as I can. One thing I liked about LP Pro was that I could set both to 10 each! Sadly, 0.83 seems just a bit too laggy for me, even so on my DX.

Again, I didn't add a lot of widgets to the stock because of the lack of re-sizing, but I may play with it some more and do some speed comparisons (with my eye, not using anything fancy). I do like how intuitive it is to add widgets, etc. in stock, but I only use 3 screens and once I setup my homescreens, its not like I change it a whole lot anyway. However, you have given me the inclination to play with stock some more :)

Btw, as a side note, I am pretty happy with my Quadrant scores....getting 16xx - 19xx and I can definitely live with that!
[Nook Color Android Development] prodigy2m:
Dual Boot Question

Does this version works with DUAL eMMC BOOT? Or the ROM needs to be modified to work with it? :confused:

Let me know, thanks.
[Nook Color Android Development] bdcrim:
Need a little help here. I flashed this rom through internal cwr (3.0.1.0) and have enjoyed playing around. I am headed back to CM7 for now. I put cwr on a sd from iomonster and cannot get back into recovery. I am not sure if this is typical of this rom, but when I flashed it (after formatting system, data and cache), the "future of reading screen" was no longer part of the boot process. I have tried properly booting from the sd card but it boots the rom. Any ideas? Thanks
[Nook Color Android Development] prodigy2m:
Did you try holding volume up and vol down while booting?
[Nook Color Android Development] bdcrim:
Yes, just tried. Thanks. No change.
[Nook Color Android Development] shadowreader:
angry birds FC with 2nd edition

Hi Samuel et al....thanks so much for all of your work. I just upgraded(reflashed) my NC from the first edition to 2nd of your rom. loving it especially the fact that google maps now finds me somehow(wifi I guess?). anyway, my main disappointment now is that angry birds FC's every time. I have tried several versions including the ones that show up in the market but they force close immediately upon launch. this wasn't the case with my 1st edition Honeycomb install. any thoughts? thanks,

Tony
[Nook Color Android Development] klfaulk:
Look in your apps for bootrecovery util. It was incuded in the 2nd edition zip. Open the app to get to CWM Recovery. Worked for me under the exact condition you described.
[Nook Color Android Development] samuelhalff:
You can try the internal utility as stated above. But to be honest, boot priority on the sdcard is hard wired, no software manipulation can prevent you from booting a cwr sdcard. What I mean is that my rom cannot be responsible for your nook refusing to boot from the SD. Sounds like your SD isn't bootable, for some reason.. check the SD, the .img file and your burning process.

Sam
[Nook Color Android Development] bdcrim:
Thanks, it allowed me back into recovery. I tried everything but that. Much needed app for this build. Restoring my CM7 backup as we speak.