yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] carguy88:
Wow

I had hoped that the devs would get into the NC when I bought it, but this far exceeds my expectations! I'll have to get this on my SD card as soon as I get home.

Also, 14 pages of comments in 2 hours? Amazing!

Thank you deeper-blue!
[Nook Color Android Development] :
I wasn't implying they all get access, just saying that some of those companies do, which is some mfg's have honeycomb code running even though it's not aosped yet. It was a response to this:
[Nook Color Android Development] altimax98:
I dont want to seem like one of those guys but why hasnt anyone ported the full sdk HC over. I know it wouldnt be perfect, but wouldnt the final sdk give us access to apps made for tablets?

I know aosp is the top dog as far as what we need for development, as well as that kernal, but it would be nice to have tab specific apps :-)

Sent from one of those missing Droids
[Nook Color Android Development] Midnitte:
Any idea if the ASOP code will bring further reduction in size? Kind of lacking on the microSD size atm... :3

Here hoping it gets released soon, and maybe they'll also get around to releasing the google tv source soon too :(
[Nook Color Android Development] Obs:
This doesnt touch internal memory right? Just runs like the Nookie Froyo SD versions?
[Nook Color Android Development] luigi90210:
yep its like nookie froyo SD

boot with sd card in to boot to honeycomb

take out sd card to boot to stock
[Nook Color Android Development] Homer_S_xda:
When you burn the HC image to SDcard you get four partitions. Enlarge the fourth partition to fill the unused space on the card (I use the most current Win32DiskImager). You can then do one of these methods to see the SDcard partition:

1) Mount the SDcard in Linux.

2) ADB or ADB wireless to use ADB for file transfer. (Easiest to get this to work first with a more stock OS. Then try the fancier ones.)

3) Use the Partition Mount tool mentioned earlier to mount partition 4, SDcard, so that Windows can see it.

IMHO 1) is the easiest and 3) is a close second.

Having said all that, now I see your issue. You should be able to mount the SDcard partition you setup above in the emmc OS by putting the loading information in vold.fstab. It is in /system/etc. UPDATE: It looks like maybe this is not fully implemented in CM7, yet.

Homer
[Nook Color Android Development] retox:
At this point the honeycomb sdk image is more of a novelty than anything, the work on kernel porting and CM7 will be much more benefical to the NC honeycomb port once the source is released for it. Think of it as focusing on the end game.

Edit: I'm not knocking any of the great work done with the image, just pointing out that the other focus areas seem to have priority at this time for good reason.
[Nook Color Android Development] danootz:
** nevermind... i must have glossed over those questions in the OP. Is there no definite functioning card? Is it really just a crapshoot on what cards work? :T

I cannot get this latest image to run on my Kingston 8gb Class 04 card.

I tried burning the image twice, using Linux and then Windows.

Each time I boot up I only get this:

ANDROID_

with the blinking underscore

What should be seen upon a proper boot? Is it just taking a long time to boot.

I keep getting the same two posts when I try to do searches for answers, but nothing helpful.

Have I missed some answer as to why it doesn't work?
[Nook Color Android Development] Cloudscout:
I've used a Kingmax 8GB Class 10 card and an ADATA 8GB Class 6 card. The ADATA was really slow but both cards worked.

Seeing the ANDROID_ screen is normal. It takes a little bit for it to boot, at least the first time. I believe subsequent boots are faster.
[Nook Color Android Development] execudroid:
I'm sorry if you've already responded to a similar question but currently search on xda isn't working so I figured I would just ask. I installed v.04 but i don't have market/youtube. I read something about this not being "legal" but how can I get Market google apps on this. Without those, I'm not entirely sure what to do with this thing.

Otherwise looks awesome man, thank you!
[Nook Color Android Development] execudroid:
Those are the instructions I followed, but I do not see Market or any google apps.
[Nook Color Android Development] execudroid:
Ugh, if I can't even figure out how to reply to a message on XDA how am I going to get market visible?
[Nook Color Android Development] eyew:
Anyone gotten Google Body to work on v0.4 ?

Don't see it in Marketplace when searching on NC.
[Nook Color Android Development] KidJoe:
Sandisk Class 2 16 gig works, but feels sluggish.

Sandisk class 4 8gig works more smoothly.

The "generic" class 4 "made in japan" cards that came in my Moto Devour (8gig) and Droid X (16gig) are slower than the sandisk class2 cards I have (both actual use with froyo and HC, as well as benchmarks)

There have been mixed results reported with some 16 gig CL 10 cards, some work fine, others don't. I've read many posts of Transend 8gig CL6 cards working well with HC and Froyo.

some were trying to create a thread for people to post their uSD card experiences. Its mostly just "I have this card, it works (or didn't)" See -> http://xdaforums.com/showthread.php?t=959316 .. it would be helpful if people also include brand, size, speed, specific model number if they have the package, bench mark scores for the cards (to get an idea of which are really the fastest, perform to their Class ratings, etc.) in their posts.

To avoid the uSD issue, some recommend to just install HC to eMMC. (I'm waiting on an HC AOSP build for that)
[Nook Color Android Development] epakrat75:
This is probably not the place to post such a question but did you search these forums or see this?

http://xdaforums.com/showthread.php?t=976131
[Nook Color Android Development] msherwood:
The market on the NC port has the wrong footprint - some device I've never heard of. Google doesn't see it as a 3.0 tablet, so you can't even push it to your Nook from the web. Someone will have to get their hands on the APK, or a more probable scenario is an AOSP ROM where the footprint is that of the Xoom or something.
[Nook Color Android Development] retox:
The fingerprint for the XOOM is in the wiki, here it is: ro.build.fingerprint=verizon/trygon/stingray:3.0/HRI39/101999:user/release-keys
[Nook Color Android Development] msherwood:
Ah fingerprint... I knew I had the wrong word. So where do you change that in the file system to be able to access 3.0 apps?
[Nook Color Android Development] fwdixon:
It's in the build.prop file in /system.

I've got mine changed to that fingerprint and also upped the sdk version to 11 (was 9) but still no google body. Oh well.
[Nook Color Android Development] RMHisCOOL:
http://dl.dropbox.com/u/16838439/Body_1.0.apk

Edit: I got a parsing error, but there's the file if anybody wants to try to get it to work.
[Nook Color Android Development] fwdixon:
It installs, but FC's on launch.
[Nook Color Android Development] GrillMouster:
Can anyone confirm whether the gallery in HC is finally doing 24-bit color, or if it's still doing 16-bit (they downgraded with 2.1)? In 2.2 and 2.3 the browser shows 24 bit colors. Also, does it show full resolution of high resolution images in the gallery, or does it still compress, creating a pixelated view when you zoom in 1:1?
[Nook Color Android Development] RMHisCOOL:
I had the same issue on the USA today app. Pulse, HNDroid, and SI work well, though
[Nook Color Android Development] RMHisCOOL:
The gallery from the preview SDK was broken, so the one in this build is from a 2.2 build, I believe.
[Nook Color Android Development] :
What would be the best SD card to use when the final build of 3.0 is released? I've heard mixed reviews on cards so far. I'm using a Sandisk 8gb class 2 card now for this preview, and it works fairly well, with just a bit of a lag. I'm sure the final build will need a better card though.
[Nook Color Android Development] iceflow420:
Fragments

I know, "No one wants to touch Honeycomb until AOSP is released", but Google just released the Fragments API (per android-developers.blogspot). From what I've read, this seems to be the missing piece to the SDK 11 that Xoom is running and the SDK 10 that we are.

I am not a developer, nor have I ever claimed to be, but wouldn't incorporating the latest SDK and the fragments API give us access to the entire Xoom library?
[Nook Color Android Development] smaskell:
I think you're missing the point of the fragments api they just released. This is a way for developers to include fragments in their apps for different versions of android. It's like taking the support for fragments off of the device and putting it right into the app. You don't add it to a rom, you add it to an app.
[Nook Color Android Development] epakrat75:
I don't want to want until AOSP. I've had good luck making a bunch of improvements I wanted to my own copy of DB's HC v4. When this project lost it's steam, I had it to do what I wanted myself unless I wanted to wait. I might even it available to others if desired / permitted / allowed, etc.

I also will have some time this weekend to "begin" to attempt an update of it to the final SDK level if someone would be kind enough provide an uploaded of a zipped "system" / "data" dump of the Final HC API level SDK image or both. Alternatively, if someone can tell me how to do it myself then I'll try that. I'm technically inclined but not quite an Android dev yet so I should be able to follow instructions. I already have the SDK installed, setup and working. Eclipse too. Don't expect miracles, though.

The Fragments API will not help our cause. It instead will allow devs to make an (new / existing) app function differently on phones / tablets without maintaining two apps. Very cool, if it works. The SDK 11 part we've need has already been released for a while.
[Nook Color Android Development] jwortiz:
Hi,

I got the image on the microSD card and booted. I now get the following message:

"Enter password to decrypt storage"

What's up with that?

Thanks
[Nook Color Android Development] epakrat75:
Didn't ever happen to me in all the times that I've flashed. FWIW, my NC boots fine everytime.

Did you search / see this? - http://xdaforums.com/showthread.php?t=950074

Please continue the discussion of your issue(s) in that thread. Hope it helps! :cool:
[Nook Color Android Development] j4mm3r:
Its already there...

Everything you ask for is out there on the web already. Just download the latest SDK from developer.google.com and create an AVD with a target for Android 3.0 and then orcourse you have the "working" HC image from this thread to pick off the bits and pieces that are required for the Nook. And I recommend you to join #nookie on irc.freenode.net to ask questions that you have (but limit them to developer related and dont expect anyone to hold your hands).
[Nook Color Android Development] Cloudscout:
If I had to guess at the release date for Honeycomb AOSP source, I would say April 24th. Apparently Motorola has a 60-day exclusive on HC for the Xoom.
[Nook Color Android Development] luigi90210:
Idk where i read this but i believe the open source license(i believe its called gpl) states that they have 30 days to release source code
[Nook Color Android Development] EGOvoruhk:
Most of Android (except the kernel) is Apache, not GPL
[Nook Color Android Development] epakrat75:
Convenient tool for extracting SDK images...

In case anyone else wants to fool around with the SDK images on Windows, I'd thought I'd at least save them the trouble of figuring out how to extract the information inside the SDK .img files by attaching this archive. The SDK image uses the YAFFS file system, so that's why this utility / tool is necessary. The attached file contains a CMD (windows batch) file. Just extract the attached archive to it's own folder (any where), drop any SDK "system.img" into it, run the batch file and you're done. Having it setup this way, worked out easy and quick for me. :cool:
[Nook Color Android Development] bandroidx:
ok this is weird. I put HC on sd on my new NC and went to root it and load gapps and cant get adb to work at all :(

I tried both my win pc and my fedora laptop, linux detects it (as seen via dmesg on the laptop) but adb devices shows nothing in both win and linux.

i tried toggling usb debugging off and back on several times with no luck.

I know adb works on both machines, i use it to develop for several phones. Do i possibly need v10 of the tools cause of HC?

is there another setting in HC i am missing?

thankjs
[Nook Color Android Development] nexus15:
I have no programing/dev skills. So I will be cheering on your efforts. I too think a build of HC from the final sdk will allow us to run the Gapps from the xoom (like the 2 pane gmail) on our nooks.
[Nook Color Android Development] mwoelmer:
This happened to me as well. I tried all of the fixes that people have posted, but none worked. Ultimately I started over.
[Nook Color Android Development] :
The thing about release the source code within a certain amount of time applies to people who use code, not people who create it.

Google is currently the curator, if they never want to release the code for HC they don't have to.
[Nook Color Android Development] blushrts:
I just spent over two hours trying to get adb to work on my Nook color. I turned off wi fi and it started working. Hope that helps.
[Nook Color Android Development] miniaturepeddler:
okey, dokey. I've spent the day getting this up and running on my Nook.

Getting the preview HC onto my SD card was actually fairly easy, given the instructions given. But I was totally stymied by the lack of market, so I stumbled around till I found the nice little util kit to install ADB on my windows machines. I began work on my windows 7 laptop, till I ran out of energy, (forgot my power cord at work), this provided me enough time to prove the adb worked and to download the market app and the googleservicesframework before I had to switch to my Windows Vista running under VMWare on my Mac.

Installed nookcolor-EasyADB on the system, plugged in my HC booted Nook (I had already configured its wireless in case I needed it) and installed the driver from the subdirectory that I had created via the EasyADB. Voila, I know had access to my Nook and followed directions to install the files into the system files of the Nook.

Rebooted the nook and I had Market.

I successfully installed Titanium Backup, RomManager, Nook Reader, Kindle, Wifi Analyzer, Pandora, Adobe Acrobat Reader, EZ PDF Reader, tapatalk pro, all successfully.

The standard email app worked once configured.

What is missing for me now is the gmail app (Its nice to seperate my gmail from my normal email), youtube, dolphin browser, Opera Browser, or Firefox browser and Flash 10.x

None of them are accessible via the marketplace.

This is more of a blog of my efforts.

I want to thank the orginal developer and the rest of the team for the components that I have used so fare.

Quadrant Standard tells me that the HC is hitting a 1125 benchmark test.
[Nook Color Android Development] Divine_Madcat:
That is my worry. It seems like Google is taking longer to push this to AOSP longer than any other build. I guess it could be that since HC wasn't even really finished when Moto pushed it, maybe they are still actually working on it. That, or they aren't putting this on AOSP like other builds, which will really suck.. :(
[Nook Color Android Development] :
They have to finish merging it with existing code and testing. That's the "holdup".

Similar to when CM has to update after a new AOSP release.
[Nook Color Android Development] Paul22000:
Can you please link where you read this?

Pretty sure that's 100% false.
[Nook Color Android Development] britoso:
The NC uses a different port for adb and the default setup of the adb server does not detect it.

add "0x2080" to %USERPROFILE%\.android\adb_usb.ini

I had to redo this after I updated my sdk to 3.0
[Nook Color Android Development] bjitty:
Thanks for posting this I can't wait to try it when I get home. I've tried everything else and basically given up on ADB for a while.
[Nook Color Android Development] FrasierCrane:
They just put the Honeycomb statue up a week ago. It was almost two months from when the Gingerbread statue went up to the Gingerbread AOSP release. Consider the Xoom a public beta, and it all makes more sense. ;)
[Nook Color Android Development] bandroidx:
thanks i tried but it still isnt working :(

driving me nuts. its hard to type in connectbot on the damn thing tryign to diagnose the issue!

\
[Nook Color Android Development] bandroidx:
thanks! i havent tried it but this makes sense! maybe i need to update my tools?

thanks!
[Nook Color Android Development] Cloudscout:
I didn't read it. I was told by a Motorola rep.
[Nook Color Android Development] luigi90210:
well he lied

there is no exclusivity to honeycomb other wise samsung and lg wouldnt have been able to show their 3.0 tablets at MWC
[Nook Color Android Development] Darkdeity9194:
is this project being continued? I'm curious as I may be getting a Nook Color hopefully soon. It has been a mean while since the first post was updated.
[Nook Color Android Development] RMHisCOOL:
It's probably not going to be updated until the AOSP is released. This is about as good as the SDK preview image is going to get (which is very good and usable btw). There isn't much point in a dev patching and working around things, when it makes a lot more sense to wait for the source and have everything work more efficiently. This is my daily driver, and very good though.
[Nook Color Android Development] Contra1971:
workes well, even sound, but is it possible to get the market on it?
[Nook Color Android Development] RMHisCOOL:
Oh yeah, all gapps work fine, as do the 40 or so apps I use. Video playback is the only big issue, but to me that's not a big deal. When AOSP comes everything will just be even smoother. The fact that somebody turned a preview SDK into a very usable, good ROM blows my mind.
[Nook Color Android Development] RMHisCOOL:
This method still works:

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

or if you're interested in a HC rom on EMMC which already has gapps, you can find it here:

http://xdaforums.com/showthread.php?t=947071
[Nook Color Android Development] Darkdeity9194:
I thought the AOSP was released when the Xoom made it to stores. Do you have any clue as to when it will be made available?
[Nook Color Android Development] smaskell:
that's what we were all hoping would happen..

nobody know when it will be out
[Nook Color Android Development] Cloudscout:
I hope he was wrong but it is plausible. The exclusivity would, presumably, be applicable to shipping products. Samsung and LG may have shown their tablets at MWC but they aren't shipping them yet.

T-Mobile has even given an ambiguous "Spring" timeframe for the G-Slate which could be anywhere from March 21st to June 20th.

Again, I hope it's inaccurate information but I guess we won't know for sure until someone other than Motorola starts shipping an HC tablet or April 24th rolls around. Whichever comes first.
[Nook Color Android Development] lizhiwei:
Does anybody find that in the browser, the button to close a tab is not sensitive ?

I wonder if this is because the size of the button is small or is it because of the NC's edge sensitivity being less than ideal?
[Nook Color Android Development] bandroidx:
I believe the kernel this uses has been recompiled with some changes made to make the outside 4 pixels or so unusable. I am not sure how this HELPS, (seems it would make it worse) but i am sure there was a reason. this could be why your having this issue?
[Nook Color Android Development] lettcco:
Google Calendar addon

Love what you have done deeper-blue, thank you very much for your work. Can't wait to see your next version (waiting on AOSP?).

I am using V4 right now, but for me to use it as a everyday driver, I need my calendar. So I searched around, and thanks to Sameulhalff, and jleecong for the honeyGapps.v2 scripts, I editted it for the calendar to work per Sam's instruction.

you must have ADB working.
[Nook Color Android Development] Paul22000:
Yes, I found that you have to tap the very bottom of the tabs (farther from the edge of the screen) for it to recognize your finger. Not sure why.
[Nook Color Android Development] idr4gon:
I tried flashing the HC image to my new 8GB A-Data Class 6 MicroSDHC but there was an error midway through. (I don't remember what it was). But when I tried to flash it again, it didn't work. It says the disk is write protected or something strange (I've tried two different adapters, obviously with the switch not locked).

I've tried these windows programs, disk utility on a mac, and disk utility and terminal on linux. When I plug it into my ubuntu machine, it totally freaks out about all the partitions and constantly tries to mount them. How can I properly reformat this card and try again? I didn't think formatting a drive could be so ridiculous. :eek:

edit: easus isn't able to write either, I have no clue what's wrong. Maybe this card is just bad? (I've never had bad flash media.)

edit #2: was finally able to format the card using of all things, an old canon point and shoot camera.

Now when I try to write the image, I still get the same error.

"an error occurred when attempting to write data from handle. error 8"

Could it really be a bad card? I've tried to use it in the camera and for files and it works fine for that. I've also re-downloaded the image twice and tried an older version of win32diskimager.

edit #3: nookie froyo burns just fine. but it's having trouble booting :\. Guess it is the card....
[Nook Color Android Development] DanielNTX:
Two Q's: Location Services & Dalingrin's OC kernel on v04

So I tried to read through every post in this thread and location services was mentioned as working, but there was no direct instructions or links on how to make it work. Maps can't locate me. What are the precise instructions on enabling Location Services so Maps and other apps like Foursquare can find me?

My second question is does Dalingrin's OC kernel actually work on v04? In that thread it states: "The kernels are not playing nice with honeycomb. Will repost as soon as I have time." for the replacement kernels.

Any guidance would be appreciated.
[Nook Color Android Development] svennn:
I can't help with your first question but I can help with the second.

It does work, I use it. However, your NC will not sleep correctly. This burns battery very fast. I was seeing 10% loss in an 8 hour span with the screen off. I hope it gets fixed eventually as I really liked Honeycomb on the Nook but ultimately went back to stock rooted. I use it mostly as a reader so longer battery life was important to me.
[Nook Color Android Development] DanielNTX:
I installed Dalingrin's OC Kernel (specifically this one update-HC-dalingrin-OC-sd-022511.zip) and it just hung at startup with a black screen after the A N D R O I D... I had to boot into 1.1 on the eMMC and replace it with my backup of the old kernel for it to boot. What am I doing wrong when replacing uImage?

Regarding location services. I wish I could figure out how to get it to work. I added the two recommended files from one of the earlier threads with no success.