yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] wpnyc2009:
Youtube starts on HCv3 but then fails.

I'm running HCv3. The Youtube app opens and starts a video but then fails after 5-10 seconds. Anyone else gotten this far? Anyone getting it to work fully?

Thanks. Happy Friday m8s.
[Nook Color Android Development] jaysckap:
Hey deeper-blue, thanks for everything. And Divine_Madcat thank you for bringing this back to life
[Nook Color Android Development] mazook98:
Anyone else noticed that the "screen sticking" issue/lockup that they (I know I do sometime in 3.0) get is actually a kind of a clear "leftover" from a browser that supports gestures?....FI...screen seems locked...about to reboot, in desperation, use gesture from browser for 'exit', then back to normal?
[Nook Color Android Development] neoslan:
Oh ****.

My Nook seems dead. I had formatted data,system, and boot. When everything was done, and flashed, I restarted. I was greeted with nothing. Nothing. No flicker on the screen, no image, almost like a plastic display Nook.

I didn't read OP very carefully, and I re-read it, and I suspect that my failure has to do with accidentally formatting "boot".

What should I do? I tried to do the 8x recovery, but nothing shows up.
[Nook Color Android Development] joenathane:
Make a bootable clockwork recovery sdcard like this one here

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

and reflash or restore one of your backups
[Nook Color Android Development] RobertsDF:
Find the file to flash back to stock and then start over with this. the Stock flashing will restore your boot.
[Nook Color Android Development] sark666:
Sorry, it's difficult to tell from the first page, is it correct that the only remaining issue is dsp?

It also says the UI is a little laggy, but I see other comments saying it's smooth. Isn't HC hardware accelerated? One of my hopes in using this is smoother ui performance.

Any other issues? Can this be put on an sdcard to try it out? I ask because there is mention of no sdcard support (without that hack).
[Nook Color Android Development] nexus15:
my observations

working very good, might actually be able to use this daily. with the deeperblue version the "tray" flyout that you can use to control some system settings was properly lined up with the right side of the screen. In this version is a bit off to the left, and when brought up to expose those controls it freezes the image so you cant actually see any controls. For instance play music and then use the flyout to pause/play. The button doesn't change.

The other as I think I saw noted is that after some time, and its not exactly clear to me whats causing it, the screen appears to 'stick' and buttons seem responsive but you cant actually get anything done because the launcher (or apps) are frozen requiring a reboot.

Finally in Google music and certain other things I think its missing some graphical capability because I have to search for songs and play them, I can not actually see the album thumbnails or list of music to play. It comes up black. Its probably related because gallery has a black background.

I definitely appreciate all the hard work so far.
[Nook Color Android Development] RobertsDF:
The newest version is smooth. there is a little lag occasionally but its not bad. Here is a link to the thread that has the SD card version of this.
[Nook Color Android Development] sark666:
Sorry I don't see a link. Also, jsut curious does it have any bt support at all?
[Nook Color Android Development] ax0r:
Thanks for this thread it has convinced me to buy the XOOM.. sold the nook and bought a XOOM wifi for 450 today ;-) :-D
[Nook Color Android Development] projektdotnet:
Works pretty well but most apps seem to FC for one reason or another, much improved to be sure :)
[Nook Color Android Development] RobertsDF:
@sark666, I forgot to post the link. Here you go. xdaforums.com/showthread.php?t=1074471. Bluetooth does not currently work with Honeycomb sdk.

@projekt,

Have you fixed permissions? I cannot think of any fcs that I have had. All Apps that I use work fine.
[Nook Color Android Development] botossi:
Divine, Deeper-b, and so many others, pls, dont let this "dream" die... HC was coming great... now the thread is like it has been forgot by you guys... ;)

We know that it is not an easy task to biuld something from nothing, but "if you build, they will come"... :D

Thanks for everything up to now !!! ganbatte !
[Nook Color Android Development] Divine_Madcat:
I can't say i forgot, but there are a couple of factors -

1) With 3.1, i was hitting a wall where the mods that previously worked were causing bootup to fail. Given that I was not the original designer of the mods, it is almost impossible for me to figure out how to fix the problem.

2) Almost all the work i was doing, was on my work time. This means that my real work just wasn't getting done. At home, i don't have alot of time, so there wasn't alot of extra time to develop what i have. That, and I am going to go on vacation this upcoming week.... WOOO.

3) Call it silly, but I am really frustrated with Google. They claim that they are holding the source back because they don't want it on phones; yet they have had no problem with sub par tablets running a phone OS. Frankly, the SDK build is ok, but it will never be the real thing, because we can never make the code optimal. I have to admit, it is so discouraging to be so close, yet so far...
[Nook Color Android Development] :
We all appreciate your work, man! It's getting us closer to a true daily driver. I've been following this thread and it makes me all bubbly inside thinking about all the progress we've made despite the lack of source code.

Once my finals are done I'll see what I can do. Probably not much but you guys are inspiring a lot of us.
[Nook Color Android Development] 360Razir:
DM, cobbling bits and pieces of code and trying to make HC work is no small feat. I remember being on Sam's EMMC version and just trying to throw band-aid after band-aid at the build to get things to work. I really liked that version of HC, but not having video was a killer for me and since the dev worked had stopped on HC at that time (rightfully so), CM7 became my DD.

That being said, that you picked up the torch again and got people excited about the prospect of having a smooth/robust version of HC is pretty special. Hopefully more devs will have eyes-on for the SDK code and make do with it what can be done, given we may not see source in a very, very long time (most unfortunate).

And I am with you on HC source...it should be out and why they are holding it so close to their vest is not what I would have expected from Google at this stage of the game.

Great work thus far and many thanks.
[Nook Color Android Development] Divine_Madcat:
360 - Aye, i am very happy to see that the community joined my call, and has done their own work with the build. It feels good to have done something for the community, and i really hope it does not die with me going on vacation this week.

If it does, i promise that on my return, I will bang heads together with others here, and see what we can hammer out. I suspect however, that Deeper-Blue is going to be a miracle worker, and show this noob what can be done with the SDK 3.1. :D
[Nook Color Android Development] racks11479:
Have a great vaca Mr. Madcat!

-Racks
[Nook Color Android Development] dunndada:
This did not work for me... it messes with the signed zip. Abort Installation. I am having problems completing this task because i dont have adb.... any suggestions on how i can accomplish this. I unzipped the madcat file but did not unzip the rom.
[Nook Color Android Development] bdcrim:
I also struggled with this until I "unzipped and extracted" the replacement copy and pasted into the rom. Did you try several zip programs, winzip, winrar, etc.....
[Nook Color Android Development] projektdotnet:
If I get some free time this week I might have to re-flash and try again, the only apps I was really trying was youtube and the google music player (the one with the headphones for an icon) because that's what I mostly use it for.
[Nook Color Android Development] demonofsteel:
There are multiple ways on how to integrate the ramdisk provided by racks into hybrid-RC1. Here's a method which takes more time, but will be easier if you're having some little problems manipulating .zip files

1) Extract HC hybrid-RC1 in a new folder.

2) Extract racks ramdisk.

3) Copy the file uRamdisk that was extracted in step 2

4) Paste it in the folder boot that was extracted in step 1. It will prompt you to overwrite, make sure you say yes.

5) ZIP all that was extracted from step 1 (which now includes the new ramdisk from step 2 as well). You can call it "update-HC-hybrid-rc1.zip" again or you can also rename it (I named mine "update-HC-hybrid-rc1_v2.zip" just to make sure I didn't get confused later on. *IMPORTANT* Make sure that you do not zip the folder containing the contents from step 1, but zip the contents themselves (boot, data, ...).

6) Copy the file on an SD card.

7) Do a full wipe of everything on your nook. For myself, this step was needed even if I came from RC3 because it would fail to connect to wifi if I didn't format /data. What's weird is that I've been able to restore my previous /data from a backup after connecting to wifi after booting the device.

8) Now flash the file you copied on your SD card.

9) Reboot and enjoy!

If in any case you're still not able to succeed, just reply and then I can upload an already prepared zip later. It would be better if it came from Divine_Madcat himself so he could put it in the OP, but he may not get the chance since he's going out in vacation.

By the way, have a great vacation Madcat!
[Nook Color Android Development] dunndada:
First of all you guys are the ****.... very helpful, i havnt attempted this yet but am curious how i can unzip it and rezip it and not have any problems... anytime ive attempted unzipping a rom an rezipping it aborts the installation.
[Nook Color Android Development] mmone3:
Anyone else have luck with class 10 sd cards, I have never been able to see anything when its mounted in honeycomb. I'm hoping that sdk 3.1 build corrects this problem.
[Nook Color Android Development] dunndada:
i think i understand...
[Nook Color Android Development] dunndada:
will the new uboot 1.2 mess this up? if so how do i remove it
[Nook Color Android Development] dunndada:
UPDATE - Not seeing sdcard in honeycomb.
[Nook Color Android Development] racks11479:
Doh! Yes you are correct. I pushed it to xbin orginally and it didn't work. So I pushed it to /bin. Totally slipped my mind. Sorry. :eek:

Thanks for your efforts on this. I'm loving it! Gonna keep digging and see what else we can do to make this baby that much better. And with deeper-blue doing his thing as well. This is gonna be great!

Thanks,

Racks
[Nook Color Android Development] Philosophy757:
I will be trying this later once deeper-blue does his thing to it. Nice work!
[Nook Color Android Development] Divine_Madcat:
Given that my first trial came from the "working SU for Honeycomb", i think that counted. Anyway, it is through trial and error that we learn; you don't think this build came out of thin air, do ya? :P
[Nook Color Android Development] MACLUIS1:
So, it is not possible to install this Rom without formatting Data, right?.. I would like to try it, but I do not want to format Data until I try the latest kernells from Dalingrin.

Also, could I try this on Dual-boot along with CM7?. Would love to run both with the same Data partition.
[Nook Color Android Development] Divine_Madcat:
To be fair, switching between most any roms requires a format of the data partition. If you do want to try it though, just do a backup of your current rom. If you don't like this build, just restore the backup, and it will be like you never flashed it at all.

As for dual booting.. it should be possible; it will just need its install script modified like the preview SDK needed.
[Nook Color Android Development] seth.i.simmons:
I'd love to dual boot it too, what it would it take to change the scripts to install it in a dual boot partition on emmc?? I'd love to try it out, but I wanna keep my phiremod intact. Can't wait to see the finished project, keep up the good work guys!
[Nook Color Android Development] 360Razir:
The LCD Density being at 120 is much smaller than the 140 from the EMMC v2 from awhile back. Putting it to 140 made the text wonky in some areas, so I reverted back to 120. Going to take my old eyes a bit to adjust.

I too also tried to understand why 2 Framework.apk's in the App Mgr, both with differing sizes. Found the one in System/App, but could not find where the other one lies.

Also, Root Explorer does not indicate there is anything in Data/App, but via ADB Shell, I can see apps in there. Not sure if it was because I did not have SU working at the time, but as I could see apps in System, not sure if that is the issue?

Very nice effort thus far and looking forward to future updates.

EDIT: putting J4mm3r's 'su' in XBIN did not work when I tried that last night...BIN is the key to get it working.
[Nook Color Android Development] LarcenQ:
Racks, did you use your method of installing to SD Card or another's? I'd like to install to SD as well, would you mind sharing? Thanks ahead of time.
[Nook Color Android Development] botossi:
Keep up with the excelent work...

Just stop by to say that like everyone else, i'm looking forward for this !!! Good luck to all that are putting a lot of effort !!! and to all that are only listners :D
[Nook Color Android Development] declain:
Love that this is active again. Can't wait to load it up and play around. Thanks for the effort guys!
[Nook Color Android Development] racks11479:
Divine Madcat,

Mind if I prep this for my SD installs on my thread here? I'll be sure to mention to keep all issues regarding the SD install on that thread as well. I could also create an .img file if you'd like. Unless you want to just keep it focused on the EMMC install.

Your call.

Thanks,

Racks
[Nook Color Android Development] bigwilly90210:
DUDE! This is freaking sweet! I'm running the Second Edition of v4 Honeycomb off the eMMC right now. The NC is my girlfriend's and she was pretty pissed when she found out she couldn't access her magazines and the "read to me" children's books. lol. Now she's in love with Honeycomb. Ha. Just yesterday she asked if there was anything new happening with development. Imagine my surprise when I found this! AWESOME!!!!! Upgrading to SDK 11 should help a lot with app compatibility I'm hoping. I'm gonna wait till deeper-blue works his black magic, but major props to divinemadcatz for getting the ball rolling again! Best $250 I ever spent!!!! :D
[Nook Color Android Development] Divine_Madcat:
Please, by all means. Ill put a link to your's in the OP, so users can easily find what they are looking for. But yeah, the more, the merrier!
[Nook Color Android Development] racks11479:
You sir Rock! :D I'll drop a line once its up.

Thanks again,

Racks
[Nook Color Android Development] arrjaytea:
Things have been awful quiet around here since Murdock's tweaks were merged. Thrilled to see this progress.
[Nook Color Android Development] racks11479:
Not sure if this will help in anyway. I know deeper-blue is working on full tablet-Market. But maybe a temp solution for the time being? I used only the Vending.apk from this thread . Repackaged a zip with su and the new Vending.apk.

Su works, market loads. Tried downloading an app and this is the logcat I get.

D/wpa_supplicant( 1748): buf LinkSpeed 54
D/vending ( 1184): [73] LocalAssetDatabase.notifyListener(): -5300756322275216656 / DOWNLOAD_PENDING
[COLOR="DarkRed"]W/GoogleLoginService( 1326): accountHasFeatures: FEATURE_LEGACY_HOSTED_OR_GOOGLE requested, which is no longer supported, returning false
W/GoogleLoginService( 1326): accountHasFeatures: FEATURE_LEGACY_HOSTED_OR_GOOGLE requested, which is no longer supported, returning false[/COLOR]
E/vending ( 1184): [73] AccountManagerHelper.getAuthTokenBlocking(): no matching accounts for ANDROID_SECURE
E/vending ( 1184): [73] RequestRunnable.run(): Fatal error from server: Sent a bad request.
D/wpa_supplicant( 1748): CMD: DRIVER RSSI
D/wpa_supplicant( 1748): wpa_driver_tista_driver_cmd RSSI
D/wpa_supplicant( 1748): rssi command
D/wpa_supplicant( 1748): wpa_driver_tista_private_send ioctl_cmd = 810a22 res = 0
D/wpa_supplicant( 1748): wpa_driver_tista_get_rssi data -77 beacon -78 success
D/wpa_supplicant( 1748): rssi_data -77 rssi_beacon -78
D/wpa_supplicant( 1748): buf TAWIL_WIRELESS rssi -78
D/wpa_supplicant( 1748): CMD: DRIVER LINKSPEED
D/wpa_supplicant( 1748): wpa_driver_tista_driver_cmd LINKSPEED
D/wpa_supplicant( 1748): Link Speed command
D/wpa_supplicant( 1748): buf LinkSpeed 54
D/dalvikvm( 1415): GC_EXPLICIT freed 323K, 10% free 5670K/6279K, paused 2ms+4ms
D/dalvikvm( 925): GC_CONCURRENT freed 2010K, 61% free 12742K/32327K, paused 3ms+6ms
D/vending ( 1184): [73] LocalAssetDatabase.notifyListener(): -5300756322275216656 / DOWNLOAD_FAILED
D/vending ( 1184): [73] VendingNotificationManager.showNotification(): Showing notification: [AssetID=-5300756322275216656, NotificationID=647747914, Title=Kindle, Message=Download was unsuccessful, please try again.]
D/dalvikvm( 1036): GC_CONCURRENT freed 373K, 11% free 6900K/7751K, paused 2ms+3ms
D/Tablet/NotificationPanel( 1036): notificationCount=1
I/ActivityManager( 925): Starting: Intent { act=android.intent.action.VIEW cmp=com.android.vending/.AssetInfoActivity (has extras) } from pid 1184
D/SurfaceFlinger( 925): screenshot: sw=173, sh=101, minZ=0, maxZ=21015
D/SurfaceFlinger( 925): screenshot: result = OK
D/wpa_supplicant( 1748): CMD: DRIVER RSSI

I'm assuming the error is due to the fact that this build is from SDK11 and the Vending apk is from the previous build? Maybe theres a workaround? I dunno, just throwing stuff out there.

-Racks
[Nook Color Android Development] roger_n:
What can I say 'AWESOME"
[Nook Color Android Development] dalingrin:
Divine_Madcat I'll help you with the kernel as soon as I get 2.6.32 squared away. Might be able to help a bit with the userspace stuff too.
[Nook Color Android Development] Divine_Madcat:
Rock on my friend.. any help is awesome.

For what its worth, i am using the kernel that was included in the last released EMMC honeycomb build, as found here (which looks to be just before the last released 2/25 HC kernel): http://xdaforums.com/showthread.php?t=947071
[Nook Color Android Development] dalingrin:
I would call an external script from the init to delay mounting the partitions. The last time I looked at Honeycomb /system would not mount with overclock kernels.
[Nook Color Android Development] demonofsteel:
If done correctly, you should not have any problems doing this.

I personally use a 16 GB class 10 card without any problem. If you're using the latest hybrid-RC1, make sure you apply the ramdisk provided by racks.

I'm not using uboot, but I use multi-uboot which does the same thing and I don't have issues. uboot resides on the sd card, so you just have to remove the uboot files, but I would advise to do a complete format of the sd card if you want to get rid of it.

Also make sure that you use the ramdisk provided by racks if you're using hybrid-RC1.
[Nook Color Android Development] dunndada:
Everything went well with copying the uramdisk over the previous one in /boot. The rom flashed. I powered down and inserted my sd card and powered up, i saw Read Forever and then saw nothing... no boot animation what so ever. Just black screen. I thought i needed to boot up to my cwm sd card but when i picked up the nook and pressed the power button HC was fired up and ready to go. The rom ran well however i am still not seeing my sdcard anywhere.
[Nook Color Android Development] hockeyfamily737:
I've been playing with this build all weekend and the better part of the day, and I won't rehash known issues, but what I did find is that running this rom I cannot connect to my adhoc network. Wifi is fine at home, but wont see my tether. Install was good with a full wipe 1st. Problem is present on both EMMC & SD installs......Nonetheless, nice job.
[Nook Color Android Development] riceboyler:
I've looked through the thread and never saw a response as to whether the SD card reading issue ever got resolved for the RC1 Hybrid. I tried it and had the same issues, so I went back to RC3 because I need my SD Card. Thanks for all that everybody is doing. I've been using RC3 as my daily for the past 5 days and I'm in love with it!
[Nook Color Android Development] bdcrim:
I fixed mine by replacing wpa_supplicant with the unzipped file in the following links op. I backed up the original, renamed the new one to wpa_supplicant and rebooted. Works great.

http://xdaforums.com/showthread.php?t=868354
[Nook Color Android Development] hockeyfamily737:
Thank you!!! I'll try it soon as I get a chance. I looked all over for a fix and never found that thread.
[Nook Color Android Development] skgtheblij:
Getting ad-hoc wifi:

There's a way to kind of automate all this with ADB, which i've used. this thread describes how to do it. You'll need to change it to a .bat file (someone says how halfway through the post) then, type:

followed by

and you should be good. The thing is, once you have the .bat file, it's a pretty easy process every time you flash.
[Nook Color Android Development] hockeyfamily737:
Thanks again guys, I never even booted into my stock Nook. I loaded up CM7 from day 1, which never had a problem reading either AP or adhoc. So when I loaded this up to play with over the weekend I was like WTF?!? It was driving me nuts. LOL
[Nook Color Android Development] 360Razir:
Also, give this thread a look...particularly Post #16 by KitF. This is what I used when I was running HC EMMC v2 from Sam and it worked great. All I did was run the .bat and adhoc just worked without issue with my DX.

http://xdaforums.com/showthread.php?t=872521&page=2

EDIT: attached are the files that I used when running the previous version of HC, so hopefully this will work for this version as well (make backup first, jic).

I dumped all the files into my ADB directory (C:\android-sdk-windows\platform-tools), attached the B&N cable to my NC via USB (already confirming ADB worked ahead of time) and then double-clicked on NC_wifi.bat and the script just did its thing.
[Nook Color Android Development] sticknui:
no softbuttons or wifi

I flashed this rom twice and both times it comes up on my screen with no soft buttons. I figured i would just load an alternate to get me through for a while but it also wont connect to my home wifi so I cant access market or configure my account on here. I had the sdcard image for a while and it worked well enough except for the market problem so I installed this one since it had a working market. But now i am stuck, do I need to format some partition on my nook prior to flashing this rom?

edit: A factory reset and cache wipe from clockwork has fixed the wifi and soft button issue.
[Nook Color Android Development] Rockwig:
reboot issue?

I'm hoping somebody can help or point me in the right direction. I have this installed to EMMC (running hybrid-rc1, with madcat's RAMDISK) and it appear that after the 8th reboot (even good reboot) it goes back to stock. Is there a way around this? I don't have CWM installed. I've been installing these through a CWM SDCard.

Any help would be greatly appreciated
[Nook Color Android Development] jonstal:
This worked like a charm! Thanks! Sd-card is recognized now. Just having some issues with music and youtube force closing, but everything works great :)
[Nook Color Android Development] wwalker1017:
when i try to install .apk files i downloaded on the nook using root explorer, i get "there was a problem parsing files". do i have to use adb to sideload apps or is there a workaround for this?
[Nook Color Android Development] Techienana:
You could try to move them (turn on r/w permission in the box at the top) to the data directory: I put them in data/app and then reboot. They self install usually.