yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] demonofsteel:
On my side, I'm also trying to make 3.1 work. I can boot to it to a certain point, but it's not very usable.

I can run the "phone mode" UI without too much trouble, but as soon as I use a more complete "build.prop" that would give the expected HC UI, it keeps crashing.

I'm trying to do what I can and I'll update if I find anything interesting.
[Nook Color Android Development] animatechnica:
How do u get cm7 to change dpi , tried lcd changer but crashes on me
[Nook Color Android Development] zeno07706:
Really great to see the progress on this, thanks so much guys. it's running really smooth here and I love the new UI enhancements on hybrid RC1! I've just one problem that I hope one of you can help me with - I've been getting a tcp error/timeout here on racks' multiupload link for the past hour so I can't get the sdcard fix. Could someone please post me the direct link to rapidshare or megaupload please?

many thx,

z
[Nook Color Android Development] Galadriel7966:
Why don't you ask on the cm7.. hmm might make sense.. u might get a lot crap for posting in the wrong thread.. this is the honey thread
[Nook Color Android Development] sunrise3500:
Out of curiosity (and others with wireless issues on hybrid rc1), did you do a wipe after flashing the rom? I didn't and wireless wasn't working, just loops trying to connect.. after wiping, it's all good!
[Nook Color Android Development] strra:
You could edit the build.prop. I do it via root explorer.

You're looking for "ro.sf.lcd_density=161"

Just change the 161 to 200
[Nook Color Android Development] racks11479:
Here you go http://www.megaupload.com/?d=4QH6Y3AV
[Nook Color Android Development] fzr-r4:
I did not wipe. I wonder if one could just wipe the right wifi settings folder/files so as not to lose everything else.
[Nook Color Android Development] zeno07706:
Thanks very much racks :)
[Nook Color Android Development] altimax98:
how far into boot are you getting?
[Nook Color Android Development] :
Just wanted to say thanks! Rom is running great. This is the highlight of my day.
[Nook Color Android Development] demonofsteel:
As for now, I'm happy to where I've been able to get. I can boot HC 3.1 without any problem, but I can't test anything else because the touch screen is not working. I have no idea what I need to do to make it work.

All I can tell is that the boot seems fine, the sensors work fine (I'm able to rotate the HC lock screen).

I'm using a build.prop file using parts of the 3.1 SDK infos, parts of Madcat's infos and parts of the new 3.1 xoom infos.

It looks alright, but I cannot get anywhere past the lock screen which is not really helpful. ADB doesn't work with my nook (but it works with my Motorola Milestone and works with the emulator), so I cannot test other stuff using ADB either. I'll look into resolving my ADB issue later.

In my test build, I've used the 3.1 SDK that I dumped (which I also shared with Madcat as well). I've also used the apps that come with the 3.1 SDK (the /data part). I've also integrated Madcat's file from hybrid-RC1 hoping that it would give me the touch screen, but it did not.

@Madcat: You should be able to achieve at least the same result using the files I shared with you. When you will have time to work on this, you will certainly get more done than me since you're far better than I am at this.

In the meantime, if someone knows how to make the touch screen works, can you let me know? I would be able to test more out of 3.1.
[Nook Color Android Development] altimax98:
is there anyway you can get the file uploaded or a link pm'd to me so i can have a crack at it to continue where youve gotten?
[Nook Color Android Development] Divine_Madcat:
Which ramdisk were you using?

Keep in mind, when i say it was not booting, i mean my modded work, not the original dump you gave me. If you want, can you post (or send) me your starting point, since i know it boots, and then i can work on modding it.

Or, if you want to try it your self, download the 3.1 mod that i have already posted, and do a diff compared to the base SDK. You will see most of my changes are in /bin and /lib, which are the same changes needed for the previous SDK.
[Nook Color Android Development] demonofsteel:
I'm building my latest work and I'll give you the link when completed. It may take a while since I was desperate that I included everything I could find in my latest test build (all the files from the 3.1 SDK and all missing files found in Divine_Madcat's hybrid-RC1), so the file size is 249MB (I could have done some cleanup, but more than required is never too much).

I'll send you the link by PM since this is uncomplete work and I've put the file on my home server since it would take too long to upload online.

***EDIT***

Forgot to mention that I first used Divine_Madcat's ramdisk, then later switched to Racks ramsidk. I've resolved booting issues when using Racks ramdisk, but it could also be due to other changes I did at the same time.

***EDIT2***

I think I didn't even use rack's ramdisk, but not sure since I deleted that build already.
[Nook Color Android Development] Techienana:
okay, everything else is fabulous but I can't install Aldiko, Angry Birds, or Angry Birds Rio, I am able to use the NI calendar and it synced with my Google calendar.

Any help on Aldiko, Angry Birds, or Angry Birds Rio? If I remember correctly, I had them installed on rc2 but no go on rc3.
[Nook Color Android Development] Divine_Madcat:
demonofsteel - Thanks for your upload. I tried working with it; specifically, making the changes to /lib/ that were needed, but it still fails to boot with the same error i posted before. Its driving me crazy, but i think i have to stick to my mental health/work catchup break right now. Ill stick around to answer questions, but i am just making no progress otherwise...
[Nook Color Android Development] demonofsteel:
What kind of error are you getting? I guess the error occurs after trying to make the touchscren working.

I'll take a look at this tomorrow, I'll start from a new clean base and I'll try to make the touch screen work from there.

I'm not very confident about this since you didn't make it work, but I'll try.

If not successfull, I'll upload my work on 3.1 (cleaned up of course) hoping someone can solve this out.
[Nook Color Android Development] racks11479:
I'll take a looksy as well if you wouldn't mind it. :)
[Nook Color Android Development] Divine_Madcat:
I don't think the system is even getting there. This is the ENTIRE logcat from a boot attempt:

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

With what i am doing, it doesn't even get to the little blue Android_ text, let alone the boot animation or lock screen...

I welcome all the help i can get from this awesome community. Please, knock yourself out. :D
[Nook Color Android Development] demonofsteel:
I see that the boot process doesn't go very far after making your changes.

Well, I could not sleep, so instead, I put up a clean HC 3.1 SDK dump and I've uploaded it on multiupload.

I did not even try it, but I assume it should get up to the honeycomb lock screen with the halo since it has been built the same way as my other tries before I messed them up.

It's a completely stock dump of 3.1 SDK (/system and /data) used with Divine_Madcat's scripts and racks ramdisk (I just used all of the hybrid-RC1 files and removed /data and /system to include those from the 3.1 SDK).

What's left from here? well basicaly everything that will render the device usefull to the end user. That means touch screen, wifi and I don't know what else. The rotation worked for me at the lock screen, at least we've got something.

I'll try to work on this tomorrow, but I post it online so some of you can try and get some work ahead of me. You will most likely need to use Divine_Madcat's original files to make things work.

Here's the multiupload link to what we all want on our nooks in the end...

http://www.multiupload.com/DDUJ0AUMHO

Have fun!
[Nook Color Android Development] altimax98:
I duplicated your logcat and issue. But im at the flashing android logo. Ive modded a bunch of files too. :(
[Nook Color Android Development] fadi33:
How do we use the new uRamdisk. i unzipped the hybrid rc1 zip image and replaced the the file but couldnt flash it. so i assume we need to push it via adb. what is the command to do so. or can we get an updated ROM with the uramdisk already in place for novices like me. Thanks
[Nook Color Android Development] Divine_Madcat:
If you are using windows (all i can test on), you dont need to unzip the HC rom. Just view the zip in windows (double click it like a folder), and delete the old ramdisk int he /boot directory. Then take the new uRamdisk (yes, you do have to extract that one), and copy and paste it into the still open zip. You will be able to then take the updated zip and flash.
[Nook Color Android Development] racks11479:
Ok, I just flashed the zip by demonofsteel. But for some reason I can't even get to where you guys are. I'm stuck @ the Android_ blinking screen. Logcat says

Looks like an error in system mount? Any advice?

Thanks,

Racks
[Nook Color Android Development] Divine_Madcat:
Make sure your SH isn't just a simlink (will show up as a file of almost zero size).
[Nook Color Android Development] racks11479:
No definitely not a symlink.... sigh*

It seems to me that /system isn't being mounted correctly for me, not sure why. Using same ramdisk and files as what was posted.

I was hoping to at least get to where you were to dig further, but guess I'm stuck here for now. Will keep tryin'

Thanks Madcat.

-Racks
[Nook Color Android Development] hubtime:
What is working in RC1

Madcat,

I would like to add my profound thanks to the throngs of happy NC owners who are happily drafting behind you as well as the contributors.

Also, are you planning to update the "What working/Whats not" for RC1 in the OP? That would be much appreciated.

NOTE: Given the fact that I have been a member since 07 I shouldn't be at Junior status... I know... I'm embarrassed. I'm rather quiet but I am moved by your efforts and Deeper Blues before you. Thanks again!
[Nook Color Android Development] Divine_Madcat:
Damn, that is frustrating. Sorry about that - i had that error, but that is why i suggested the files (since when you first grab em, they are all just links to xbin).

I wish i knew what it was about this update that is killing us. THe first thing that comes to mind, is did they change the format of the partition (ext3, ext4). I have tried both ext2 and ext4, but same results. Didn't try ext3, but not for any specific reason past time.

In their System.img; is there any way to tell what file system the .img unpacks to?
[Nook Color Android Development] fadi33:
I get a

E:can't open /sdcard/update-HC-hybrid-rc1.zip

(bad)

Installation aborted

I tried updating the zip files twice thinking the first time the zip got corrupted.

The card is fine because I am able to flash the original hybrid RC1 file.
[Nook Color Android Development] racks11479:
Flash the original. Then just replace the uRamdisk in the /boot partition with the updated one. No need to repackage anything.
[Nook Color Android Development] demonofsteel:
I just took a look /system/bin/sh is 140Kb and the one in Divine_Madcat's hybrid-RC1 build is 144Kb.

If it can help, I did a "ls -la" in /system/bin from the 3.1 SDK emulator and here is the result for /system/bin/sh

lrwxr-wr-x root shell 2011-05-05 01:40 sh --> mksh

And here is the result for /system/bin/mksh

-rwxr-wr-x root shell 143692 2011-05-05 01:40 mksh

I unfortunately don't have my nook with me, so I can't do some testing yet, but I will definitely be trying later today.

***EDIT (forgot the most important thing I wanted to say) ***

I didn't test that test build, but my previous one worked up to the lock screen. The main differencse is the uRamdisk that I changed (I used the one from racks instead of the one from Divine_Madcat) and that I didn't include previous files from Divine_Madcat's builds.
[Nook Color Android Development] fadi33:
How do i replace it? I tried to push it via adb but i get an error saying the file is read only. I dont have much linux knowledge, so what are the exact commands to replace the file. TIA
[Nook Color Android Development] racks11479:
Well, its good that you have adb.

You can't really just push a file to boot via ADB. You would have to create a mount point for /boot. Or just run the following commands in ADB shell:

$ adb shell
# echo /dev/block/mmcblk0p1 > /sys/devices/platform/usb_mass_storage/lun0/file

That will mount the /boot partition on your PC as a USB drive. Just remember to eject it before disconnecting your nook from your PC.

**Or better yet. Try samuelhalffs NookColorUMS app. Not 100% sure if it's compatible with the latest SDK. But give it a go if ADB doesn't work for you.**

-Racks
[Nook Color Android Development] fadi33:
the adb code worked perfect. Now I can see my sdcard. Thanks racks, madcat, and all who have brought the HC experience on our NC.

Also I can confirm that NookColorUMS does work, at least to mount the sdcard into windows. haven't tried mounting the /boot partition.
[Nook Color Android Development] Rockwig:
build.prop changes

I found that if I changed the following line in the build.prop

ro.product.cpu.abi=armeabi

to

ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi

I can get Flash 10.2 and Google Earth to download and install from the market.
[Nook Color Android Development] sthacher:
Maybe I'm stupid but I can get my into recovery after flashing. Wifi isn't working for me it scans but doesn't see all networks. So I guess my question is, do we still have recovery after this? Did the button combination change to get to recovery? I want to wipe everything and reflash this see if I get better results.
[Nook Color Android Development] Anon87:
does having the flash player installed make any difference?
[Nook Color Android Development] sthacher:
I cant seem to get adb to see the nook. Tried all usb ports and 2 cables it used to work. I guess Im going to walmart to pick up and sd card to reinstall clockwork so I can reflash cm7

**Edit**

Disregard some how the drivers were missing
[Nook Color Android Development] racks11479:
Thanks for that, after replacing the sh file with the one from Mad_cat's Hybrid. I'm where you are, stuck at the lock screen with no response to touch. One step further for me i guess. :)

Thanks again,

Racks
[Nook Color Android Development] dunndada:
Will this be helpful to our community?

http://www.engadget.com/2011/05/12/viewsonic-7x-shrinks-honeycomb-to-7-inches-for-the-tiny-handed/
[Nook Color Android Development] Divine_Madcat:
Not really - screen size has never been an issue. We need code compiled for our device (or, as close as we will get, which is an Omap 3630 CPU); that new tabby is still the same VERY incompatible Tegra 2, which means we cannot use most of the android compiled code it has...
[Nook Color Android Development] ax0r:
Wanted to post to give thanks.. I think you guys should honestly focus on 3.0 SDK its been making huge improvements in performance. The hybrid with the ram disk OC to 1100 is suprisingly smooth.

Also, was reading through the G Tablet forum and i noticed that they had something posted about Google announcing no source code EVER for Honeycomb.. This was as of 5/10.

Question: Honeycomb source -- will it ever be released? (And no, it wasn't me who asked, but I was in line to :) )

Answer: Because of the way GIT works, all the changes will be available eventually. But when asked if there will ever be a branch folks can download and build, or if they ever plan to release something for the current legacy tablets, the answer was "Ask us in Q4." (which happens to be the target for Ice Cream Sandwich.)

http://m.androidcentral.com/fireside-chat-android-team-highlights-io2011
[Nook Color Android Development] demonofsteel:
Time for my update of the day...

First, I've been able to fix my ADB problem with my nook, I was able to use ADB with any device except my nook, so it's now fixed and I can test 3.1 even better now.

I've played around with the device testing 3.1 today and here's where I stand. First, time for a screenshot!

That doesn't mean good news tough even if that screen looks good. I've managed to get up to that screen by sending keys using ADB, so I sort of cheated. I booted the device by copying all of the missing files from the bin, etc and lib folders from Divine_Madcat's hybrid-RC1 into the 3.1 SDK. Note that I only copied the MISSING files, I didn't overwrite the existing ones that were dumped from the 3.1 SDK. By instaling that ROM, things look good, it boots, lockscreen shows up, rotation works, but touchscreen doesn't (that means that the touchscreen drivers are in the files I didn't overwrite).

I navigated through the whole UI by sending keys through ADB, it's painfull, but at least I now know that the build seems to be working well enough.

By the way, does anyone know if there is a possibility to remote control a device through ADB? It would kind of be very usefull at this point.

One thing that I've noticed which may help interested developpers is that I found out that the touchscreen is kind of half working...

What I mean by that is that we cannout touch anything, but after unlocking the device and waiting about 1 minute until the device dims the screen before turning it off and locking it, I found that I could touch the device to prevent it from going into sleep and the brightness returned to it's normal state.

So I'm now seeking advice on what I could try now at this point. Should we recompile a touchscreen driver? I'm just asking since I don't know what to try at this point and I wouldn't be able to compile the touchscreen drivers.

For those seeking information about the touchscreen, I found this...

http://www.androidtablets.net/forum/nook-color-technical/3483-nookcolor-full-specifications.html

My next option would be to try to replace files from the 3.1 SDK by those from hybrid-RC1 one by one (or about 10 at a time since there's lots of them) and see which one causes the device to fail at booting when integrating all of the files from hybrid-RC1.

I don't really want to do that, that's why I'm seeking advice and help.

Other than that, didn't get the chance to test wifi since I prefer waiting until I won't have to send keys through ADB to test that.
[Nook Color Android Development] joenathane:
Very nice work!

This https://market.android.com/details?id=org.onaips.vnc&feature=search_result

should do the trick, VNC server for remote control....
[Nook Color Android Development] demonofsteel:
Thanks joenathane, I will definitely be looking into this, I'm sure it will help me at the point where I stand.

I'm doing more testing now and I found that when copying everything from /system/bin from hybrid-RC1 into 3.1 SDK (without overwriting everything from /system/lib), I get stuck at the boot logo (the animated stock logo that we can see in the boot sequence of every android device that didn't change it's boot logo).

When overwriting everything from /system/lib (without overwriting /system/bin), I get stuck at ANDROID_ (where the "_" flashes). I didn't get time yet to analyze the logcats, but here's a funny line which made me lauch a little bit that I noticed when printing the logcat after overwriting /system/lib...

I/DEBUG ( 930): debuggerd committing suicide to free the zombie!
[Nook Color Android Development] KitF:
This sounds EXACTLY like the problem deeper-blue had with his first port and what fattire and dalingrin had during porting CM7.

Maybe they can chime in?
[Nook Color Android Development] skgtheblij:
Thanks again for all the great work everyone. I'm really getting excited about the progress you all are making with 3.1 I for one am in favor of further development on that as opposed to 3.0, as long as it is practical. It seems the source for each will come out around the same time anyways.

I like this new HC build, and it might become my daily driver, but I just can't get market to work. It doesn't download anything. I can search for apps, see the apps that i've purchased in the past, etc. but when I try and download something, the download progress bar just scrolls indefinitely. Any ideas?

Thanks!
[Nook Color Android Development] bigwilly90210:
hey guys. just wanted to send a last sad post. apparently my gf has deemed the tablet not worth her time and therefore not worth her money. it was a glorious but short lived week I had with you guys, but we returned the nook color this morning. *sigh* Oh well. Maybe we'll pick one up again down the road. Until then, I'll be checking in to see how you guys are doing. Looks like there's a lot of great new people contributing and I know this project is gonna continue to take off! Keep up the good work everybody! And God bless!
[Nook Color Android Development] RobertsDF:
Yup, deeper-blue fixed this pretty quickly when the sdk was first released. You should try to get in contact with him demonofsteel.

EDIT: Possibly try this? http://nookdevs.com/Multitouch#Downloads
[Nook Color Android Development] demonofsteel:
That's interesting! I'll take a look into it later on tonight.

Thanks for sharing.
[Nook Color Android Development] Divine_Madcat:
That is for the eInk Nook,and not the Nook Color..
[Nook Color Android Development] altimax98:
That's for the original nook

Sent from one of those missing Droids
[Nook Color Android Development] MrPib:
Well geez, what is your girlfriend going to do for fun now?

Oh. never mind -- just noticed your name.

:D
[Nook Color Android Development] altimax98:
I too got the zombie release lol. I researched my logcat and besides the other huge list, it seemed to notate a folder in the USR folder.... im testing some things now, it has references to wifi and omap in there
[Nook Color Android Development] demonofsteel:
Thanks for letting me know, I didn't examine the link in detail.
[Nook Color Android Development] deeper-blue:
I have a working SDK 3.1 version with touchscreen, sound, wifi, graphics and as usual without hardware video decoding.

I'm working on fixing the issue that the screen sometimes seems to be stuck, other than that it works well, when I solved that I'm gonna give it out for everybody to play with.
[Nook Color Android Development] racks11479:
Man deeper-blue, you are amazing! I get all giddy inside everytime I see that you've posted something. It could be non-sense for all I care, but it mostly never is! :D

Thank you sir, and looking very much uber excited with anticipation for your HC release!

Thanks again for all the work you put in!

-Racks
[Nook Color Android Development] MrPib:
Awesome! Does the Market let you install stuff?
[Nook Color Android Development] xboxexpert:
Sounds like my GF when I stopped spending all my time with her and more time with my nook. LOL
[Nook Color Android Development] Divine_Madcat:
Sounds awesome DB. Thank you for your continued work on this; if i could hand the thread over to you, i would gladly do so. :)
[Nook Color Android Development] etx:
I gave this a shot last night, and its really nice. Thanks for your guys hard work. 3.0 is so much smoother and responsive than pre 3.0 versions I've used on the nook color. I just have to get my sdcard working with that new ramdisk now.