yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] altimax98:
Running this now and i would say your 100% right. There isnt a slot even there for a SD card in the storage tab, unlike when running RC3 and requiring a format on SD.

Ive also got a few more little issues on my hybrid build.. My screen wont shut off, it only goes black but never actually turns off... anyone else with this issue? I really like this build but it needs a bit of help :)

I mirrored the Xoom build keys and the market still wont show body, is the market now looking somewhere else for the keys for certain apps?
[Nook Color Android Development] chisleu:
Downloading the hybrid. Hope I can figure a way to backup my cm7 install so I can restore as I doubt I will be happy with this (for now)

I'm really looking forward to access to android 3.0.

Have you seen the Blackberry tablet commercial

? I think that interface is really interesting. Maybe not perfect for me, but really awesome all the same.
[Nook Color Android Development] bigwilly90210:
If you figure it out, let me know. ha. I was gonna show it off with my little bro taking high school biology to his teacher. we're both android nerds and love this little tablet so much thanks to you guys. does the hybrid build run smoother at all than v3? idk why, but the stock launcher is what was killing me before. as soon as it's gone the whole experience is so much faster. didn't feel that way on the xoom at all. freaking dual cores jerk
[Nook Color Android Development] altimax98:
Its really having the source that will improve the way it runs. The hybrid is good, but the SDcard issue is annoying, but hey its all in the name of Development lol. The only thing thats killing me is my screen wont shut off :(

It is a ton smoother then V3 was. Im on stock launcher, and ive NEVER run the stock comb launcher.
[Nook Color Android Development] bigwilly90210:
i played with one. it's pretty cool, and the size of it really makes me think of our nook colors. lack of physical buttons on it made it a horrible experience trying to get out of some apps that didn't include buttons. even the demo guys (3 of them) couldn't figure it out with me. lol. they (BB) stole most their OS design from webOS. which is good, but i don't think I'd choose it over honeycomb at any rate. gesture support is cool. it's new too, just like honeycomb. we'll just have to see where it goes. honeycomb becoming ice cream sandwich is gonna be a big deal at the end of the year. i'm really excited to see where android is in a year from now. probably at the top! :D
[Nook Color Android Development] jaysckap:
I no what your saying this wasn't directed towards you I agree CM has alot to do with just about everything and I like them for that. I was just trying to say no matter what device or thread you look at it seems that CM is the general focus rather than what the topic is. How many times does someone have to say "CM is the best, CM has that option, CM has less bugs, CM did it first, is this based off of CM?, ect..." it just sucks that the focus gets takin away from the dev and his work.
[Nook Color Android Development] KitF:
The 3.1 SDK is out, by the way. Hopefully it won't be too painful to update this to that.
[Nook Color Android Development] demonofsteel:
Ok, I've just tried hybrid-RC1 and I must admit that I'm quite impressed with how smoother the scroling is (altough I still need to rotate the device to sometimes get out of the app drawer), but I don't see any advantage of using it right now as it's less functional (altough nicer looking).

I think I prefer having the real HC soft keys, I don't really like those from hybrid-RC1.

We've got great news today... Google revealed HC 3.1 today at Google I/O 2011. Right now, I think only Xoom is being updated, but the SDK is already downloadable.

In fact I'm already running it in an emulator, maybe some parts of it could be used. (Just saying, I've never build a rom from an SDK, so I don't know if it's possible.)

I've had the chance to play with a Blackberry Playbook for a few hours 2 weeks ago and I must say that it's now very user friendly. I would get an iPad or any Android tablet before a playbook. It was probably the worst tablet experience I had in my life (I even prefered Win XP tablet PC edition).

One function that is nice tough is the pairing to blackberry phone option.
[Nook Color Android Development] jaysckap:
Have you tried the Acer tablet?
[Nook Color Android Development] bigwilly90210:
OUCH. ha. WinXP was cool at the time, but looking back... wow. ha. Is there much reason to update the SDK build 3.1? Maybe source code for it will be released? Google didn't say anything about Honeycomb's source code, but they did say Ice Cream Sandwich (notably missing a version #) would remain open source.
[Nook Color Android Development] bigwilly90210:
ok looked over 3.1 features again and I must say, host mode would be effing sweet. now my extra ps3 controller can be put to good use! including that in ICS for phones is gonna rock! the movie editor looks interesting, as well as the "Movies" app. Other than that apparently the browser is supposed to be "quicker" and resizable widgets on the stock launcher. Pretty sweet if you've got a Verizon Xoom I guess... ha. I'm updating my SDK right now.
[Nook Color Android Development] fzr-r4:
wouldn't 3.1 also increase the odds of Flash working?
[Nook Color Android Development] altimax98:
Host mode will only 'hopefully' make things a little smoother for us. But the host mode and such, id be shocked if they make it to the Nook. Our kernals and such need to be updated to support that. Our best hope is to look forward to Ice Cream Sandwich to get a 'semi-official' nook upgrade when they release that source. Google already basicly said the 3.0 and 3.1 source will NOT be released
[Nook Color Android Development] altimax98:
We need a .32 kernal or something that supports our DSP before we can consider flash, unfortunatly. Hopefully since the .32 kernal is semi-complete for the CM7 builds, maybe a kernal DEV will come this way
[Nook Color Android Development] Sincidius:
Like this version. It has been the first to run the CNN tablet app for me successfully (even though a force close once in a while). SetCPU helps a little, but the overall experience is well beyond any previous versions of HC. Great job! With these updates coming so fast, I can't wait to see what you guys come up with next!
[Nook Color Android Development] Divine_Madcat:
Been there, tried that, could not get it to boot, AT ALL. :(

Not to say i won't keep trying, but i will have to ask for patience. :)
[Nook Color Android Development] ieAnd:
Soon as SD card is supported again, I'm going to be on this ish like Jersey Shore on bad one-liners. So excited for some relatively smooth Honeycomb action. And with the rate of updates, this will be a great daily driver soon.

Keep up the good work!
[Nook Color Android Development] randomblame:
It just froze up on my computer haha

2nd attempt froze up again

it takes about 5 minutes for the android loading screen to go away and opening the app drawer basically kills it. this is on an i7 920 overclocked beyond reason with 6 gigs of triple channel ddr3 and a 3 way striped raid array - makes it seem unlikely that the nookie will have a chance. They must have purposely nerfed this build because the 3.0 version works flawlessly. Maybe wait for revision 2....

Edit finally got it running slowly by deleting that virtual device and making a fresh one with all default settings and setting emulator.exes priority to above normal in task manager good grief

While typing on it it switched to Japanese haha go google! How are we supposed to use this as a development tool?
[Nook Color Android Development] bigwilly90210:
As much as I hate to agree with you, its true that Google probably won't open source Honeycomb. I see their reasons for it, but I still don't agree with going against their mantra "don't be evil" and not keeping an open source project open. Even if it means nothing to the general public, it means a lot to people like us. And it kills a lot of projects that rely on it. Like this one. You guys have made tremendous progress making this build bounds and leaps superior to stock software. Thanks so much for the painstaking work.

Hopefully we'll get the ICS source code in a decent time frame. I'm keeping this little tablet at least a year+.
[Nook Color Android Development] altimax98:
Can anyone else confirm this for me. Im running hybrid and my screen wont completely shut off :( ive installed twice so far, i can do with the sd card for now but not a always screen on problem :'(
[Nook Color Android Development] bigwilly90210:
LOL. Good to know, cause I was gonna try it on my AMD X4 BE @ 3.4 with 8gb Dual channel and a 2 way RAID. Ha. If yours can't handle it, there's no way mine will. Freaking Intel optimizations... lol. Maybe it's not worth a 3.1 build... ha. Also, why would updating to 3.1 help with Flash work? Just curious.

Also, instead of an emulator, here's the thread on the download for 3.1 on a 3G Verizon Xoom here
[Nook Color Android Development] chisleu:
They have said repeatedly that they will indeed release it. It is already (obviously) available to developers who sign an NDA.

They don't want it released because it the source is full of hacks. They are cleaning it up, then it will be released. Probably around summer.

I'm super excited about 3.0. Can't wait to see a real 3.0 build on our tablet. I'm close to buying a 3.0 tablet (galaxy or something? I donno.)
[Nook Color Android Development] bigwilly90210:
Ahh, I've heard its pretty shoddy too. Mostly just cobbled together for the Xoom I assume. Well if it is released anytime soon, it'll be a great summer! :P ha

Also, if you're looking for a "real" tablet, the Galaxy Tab 10.1 looks incredible. Early reviews (read: lucky bastards that got one at I/O today) say its a lot smoother and quicker than the Xoom, even with the same Tegra 2 chip.
[Nook Color Android Development] altimax98:
Sad to say i disagree. Google legally does not have to release the source, and honestly from a corporate standpoint why release something that is a hack and your not proud of. Google is not proud of HC at all, it was rushed and all motorolas fault. If moto wouldnt have pushed so hard HC would probably release as the Ice Cream Sandwich build and everyone would have benifited. Phone versions wouldnt have builds 2.3.1-2.3.4 and HC wouldnt have 3.0,3.0.1,3.1.

I hope we get the source to build a kickass rom, but i wont hold my breath
[Nook Color Android Development] bigwilly90210:
Hey guys! Just thought I'd drop this helpful link here:

3.1 Platform Update Summary

If we can get that new Open Accessory thing working (and some tangible devices come to Market) do you think a camera add on could be possible? I have no idea what APIs or hardware requirements there are, but it would awesome to see (for any Android phone/device really) peripherals and accessories just like on a pc. Bluetooth, camera, GPS, even mic input or gaming input would be incredible and add a whole host of new innovations for Android devices. Plus it'd be incredible on our Nooks! Anything you lack on the device could be added on later... how cool would that be? Anyways, if you guys are getting sick of my random rants of nonsense, just let me know. It wouldn't hurt my feelings. ha
[Nook Color Android Development] chisleu:
I don't get it. No they don't have to release it. It's their code and licensed under Apache, right?

They aren't proud of the code, hence the delay, but it has been said by google execs, repeatedly, that it WILL be released and it's only delayed while they fix some things in the codebase and add native phone support or something.

I guess I'll just listen to the google execs and keep my hopes up.
[Nook Color Android Development] skgtheblij:
I think Google will release the source.

One of their main reasons for not releasing it before was that they didn't want people cramming it onto phones in China or whatever. I predict that the source for 3.0 and 3.1 will be released simultaneously. Google said that they wouldn't release the source until after 3.1 came out. so this is good news for us.
[Nook Color Android Development] chisleu:
http://www.youtube.com/watch?v=OxzucwjFEEs&feature=player_embedded#at=11

They just repeated again today that it will all be open source. I believe them because lying would only make them look bad.
[Nook Color Android Development] ADude:
If you install Clockwork Mod Recovery to a bootable SD card (see the "CWM" thread), then you can run "nandroid backup" which backs up everything.

Then you can later run "nandroid restore" from the same SD card (which has CWM and the backup) and CM7 will be back like nothing every happened.
[Nook Color Android Development] altimax98:
Can someone test this so it can be added to the bugs for hybrid.. turn on autorotate and see if your screen shuts completely off when you hit the button or it just goes black

Sent from one of those missing Droids
[Nook Color Android Development] yerand:
no, the eee Pad does have an sd card port... it actually can support two at a time... one on the device and one on the dock
[Nook Color Android Development] altimax98:
Yeah i just read up on that, but it supports SD card storage in a 'windows' like manner. So it may use its own software to support it and omit it from the HC build. Because that storage menu doesnt even have a spot for SD card, it is intentionally modded like that.
[Nook Color Android Development] Rockwig:
I stand corrected. The only reason I suggested that was because I was looking at one of the system dumps and noticed a setting in the build.prop that said "tablet, no sdcard".
[Nook Color Android Development] flipper2006:
i cant connect with my wireless for some reason with RC1(hybrid). I'm rebooting after the initial boot but this is first time i couldnt even connect. It sees the network, but it kepts getting error on wireless, maybe because it's wednesday :eek:

I have a Iconia, but i keep playing with the Nook because it's eaiser in the hand
[Nook Color Android Development] racks11479:
Madcat,

I'm uploading an SD image of your Hybrid RC1 now. The file is rather large. 450mb compressed. I even zeroed out the partitions before compression. Seems like the system files are whats taking up the most space. So it's gonna take a while. So I'll post an update in the morning. Let me know if you rather me just PM you the multi-upload link so you can post in OP. Or for me to just post it here.

Thanks,

Racks
[Nook Color Android Development] fzr-r4:
I couldn't connect to wifi with it, either. I'm back on rc3 mostly because of that. I have a hidden SSID with WPA2. nothing too special, so I wonder what was wrong.
[Nook Color Android Development] lschroeder:
This sounds great! Thanks Madcat and racks11479. Will be looking here or OP for the link. Currently running phiremod's V6.2 OC 1.3 on emmc and Dal's 2.6.32 kernel on sd card. Would like to put Hybrid RC1 on another 8gb sd card.

I am also thinking about putting stock or rooted 1.2 on a 4gb sd card. I use a 16gb data/video/music sd card with phiremod's v6.2. The nook sd card system is just great for me.
[Nook Color Android Development] ScottyNuttz:
I had this problem too, but I fixed it by clearing the dav. cache and doing a factory reset, then reinstalling. Now wireless is fine.
[Nook Color Android Development] Oskiee:
:ODD

I spent a couple hours yesterday setting up HybridRC1, and it worked great. Except for the low performance (even after overclocking on SetCPU, but who knows maybe it didnt actually overclock) the experience was great. The only thing this makes me want to do is buy the new Galaxy tab more :O( ... im already saving for one. Im no programmer(but wouldnt mind learning) but id like to help some how if i can.

Edit: By the way, i can say that flashing with CWM 3.0.0.6 works fine. I havent found/been-to-lazy-to-figure-it-out a to burn the newest version to my bootable SD.
[Nook Color Android Development] demonofsteel:
Hi Madcat,

Since you seem to be having issues to get the new 3.1 SDK to run, I did a dump of it for you. The dump is from a complete unmodified state (except busybox which is required to get the dump).

I'll send you a PM with the link to it. The file is hosted on my server and I would not want all of my bandwidth sucked.

If someone else would like the 3.1 SDK dump, let me know and I'll work something out.

Hope you'll be able to do something with that 3.1.
[Nook Color Android Development] Divine_Madcat:
Hey, i appreciate it, but it was actually the modified dump that i had problems running. :) Though, i did a dump straight from the .img file, so perhaps you dump might come out a little different. Can't hurt i guess. :)

And rack, feel free to post it here, just in case i can't get to my PM"s right away. :)
[Nook Color Android Development] demonofsteel:
Mine was done by ADB with the emulator running. It would be strange if it would be any different, but you can take a look at it anyway.

I'll try to see if I can make anything out of that 3.1 tonight or tomorrow.

***

EDIT

I've updated the system dump by having the emulator run at the same resolution as our nooks. I don't know if it changes anything, but I've updated the dump anyway. You can download it using the same link I provided you by PM.

I've also dumped /data since I noticed there's some interesting stuff in there. Let me know if you need the link.
[Nook Color Android Development] tony1208:
I also flashed v3 via cwm06 emmc....no issues....
[Nook Color Android Development] Divine_Madcat:
So, I am at wits end here, since i am not sure what is happening. No matter what i do, i cannot get the modded 3.1 to boot on our devices. I suspect that it may actually be the ramdisk that is having issues, but i cannot confirm. Frankly, i am pretty much out of time to work in this... my work is falling behind, and sadly, the SDK port is not worth my job (everything i have done so far has basically been on work time). For anyone who wants to play with what i have started, here is the SDK port:

http://www.mediafire.com/?e467fidjn53pe3e

For those curious about the error, this is the entire logcat from the boot:

I/DEBUG ( 813): debuggerd: Feb 16 2011 19:29:36

D/OMXRM ( 821): [Resource Manager] - start resource manager main function

I/DEBUG ( 813): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG ( 813): Build fingerprint: 'generic/sdk/generic:3.1/MASTER/123685:eng/test-keys'

I/DEBUG ( 813): pid: 811, tid: 811 >>> /system/bin/vold <<<

I/DEBUG ( 813): signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr a7d04270

I/DEBUG ( 813): r0 a7d04270 r1 00000000 r2 00000d80 r3 00000000

I/DEBUG ( 813): r4 00000000 r5 00000000 r6 00000000 r7 00000000

I/DEBUG ( 813): r8 00000000 r9 00000000 10 00000000 fp 00000000

I/DEBUG ( 813): ip 00000000 sp bec32858 lr 00000000 pc b00015d8 cpsr 60000010

E/OMXRM ( 821): OMAP version not supported by RM: falling back to stub mode

The interesting thing, is that adb is responsive, and can even do a remount on the /system partition.

Deeper-blue, or anyone else willing, if you have some free time and ideas, have at it. When i get the time again, i will try more, but i have to take a break guys, sorry.
[Nook Color Android Development] arrjaytea:
Real life beckons. Take care of that first, don't let this stress you out, and know your work has been appreciated.

:)
[Nook Color Android Development] crea78:
The exact same thing is happening with my wireless connection. Even my neighbor who has an unprotected login cannot connect as well. :confused:
[Nook Color Android Development] Rockwig:
SDcard issues...

I think the SDCard issue might be because the Max Partitions is set to 4, where the Nook actually has 8. I'm really just grasping at straws here (from looking at the logcat "E/DirectVolume( 808): Dv:partAdd: ignoring part_num = 5 (max: 4)"). I'm not sure how to change it to 8 to test...
[Nook Color Android Development] flipper2006:
is there a fix for this?
[Nook Color Android Development] fzr-r4:
yes, thank you, Madcat. what you and deeper-blue have accomplished, not to mention shared with us, is amazing.
[Nook Color Android Development] E_man5112:
I think if someone can get the SD card working, this will be a real daily driver. Thanks for all the hard work Madcat!
[Nook Color Android Development] racks11479:
Well it seems to me that the reason the SDcard isn't mounting is because there are no mount points created for the SDcard in the uRamdisk. I was able to get the Hybrid-RC1 to mount the 4th partition (/sdcard) of the SDcard rom. Will be posting soon. :)

I haven't flashed this to EMMC, but if someone wants to try it out. PM me and i'll send you a modified Ramdisk to try out.

-Racks
[Nook Color Android Development] Rockwig:
That would make sense if the ROM can only see up to 4 partitions. Does anybody know of a way to have the sdcard be one of the first 4 partitions of emmc?
[Nook Color Android Development] racks11479:
Well, i don't think it matters about what partition the SDcard is on. Because I was also able to get it to mount by Dualboot setup on the 7th partition as SDcard as well.
[Nook Color Android Development] Rockwig:
I guess I'm wrong. Not the first time. Won't be the last time.

Thanks!
[Nook Color Android Development] racks11479:
No biggie, you live and you learn right? :D
[Nook Color Android Development] altimax98:
Thanks to Racks, SD card access is now working. Tested with TIBU... Ill let racks post it up:

Bugs with SD Access:

1: Does not appear in settings

2: Requires reboot when card is removed if powered on
[Nook Color Android Development] racks11479:
Yeah, its an ugly workaround for the time being. Still haven't been able to pinpoint the issue with Settings not recognizing it yet.

-The SDcard is being mounted on init.

-So there is no safe way to remove the SDcard without powering down first.

-Also for the Nook to recognize the SDcard it needs to be in the slot before powering on. Since the mount command is being executed on boot.

Will continue digging and see what I come up with. Can't wait till this is stable enough to be my daily driver! :D

Just replace your uRamdisk with the one attached. Make sure to make a backup of your uRamdisk just in case.

**Use at your own risk!**

Download: madcat-hc-ramdisk-SDmount.zip

Thanks to altimax98 for testing this out for me. :)

Thanks,

Racks
[Nook Color Android Development] Divine_Madcat:
Racks - thank you for your work! I have updated the OP with your new ramdisk.. Keep up the great work! :)
[Nook Color Android Development] demonofsteel:
I'm currently running "hybrid-RC1" with the ramdisk provided by Racks and it works!

Thanks!
[Nook Color Android Development] gregh77:
does this boot from SD?

does flash and video work?
[Nook Color Android Development] Dragracekid:
Nevermind I found it
[Nook Color Android Development] racks11479:
No, thank you sir for reviving honeycomb. I'm just trying to do my little part to get to the daily driver we're all longing for. :)
[Nook Color Android Development] joenathane:
The 3.1 SDK should be out soon, i'll be very excited to give it a try!
[Nook Color Android Development] Divine_Madcat:
I actually was working on it as of 11:00MST yesterday. I am not sure whats up, but something about the image is different, and so far, will NOT boot as it is currently modified (aka, using the same mods that made 3.0 work). Given how early it fails, it may be the ram disk, but without a proper linux system where i am, i cannot decompile the SDK ones, to see what might have changed.

If there was a needed change in the ramdisks, it would be possible for somebody to modify the one we currently have (most recent version made by racks), and apply such changes to it. I have already modified (and posted) the modded SDK, meaning you would be good to go, IF it were only the ramdisk... IF. If somebody is looking for a project, this might be a good one to jump in with.. or if Racks gets bored again. ;)