yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] dalingrin:
UI accel won't be perfect but we can most likely get at least partial support. A good bit of the work being done in CM9 is to get legacy devices fairly well supported.

The primary piece that we're missing is the hwcomposer library. As far as I can tell, it is not required for basic UI acceleration. I asked fattire to make a build for the Nook Color with the OPENGL_RENDERER enabled. This along with a modification to Webkit allows even the Nook Color to have some UI accel.

The bigger questions that I have are centered around video playback. DSP codec support shouldn't be a major issue but going from DSP->GPU->Output might be difficult. The way its done on OMAP3 is DSP->Overlay/GPU->Output. ICS has changed how the overlay works..its seemingly gone. I'm not sure how we can fix/workaround this yet. I need to dig into the Android framework to get a better understanding.

EDIT: I'm totally wrong about the DSP. The DSP codecs will be near impossible to get working right now unless TI updates OMX for OMAP3. They will need a new API to use native window rather than an overlay. I will test the new soft codecs in ICS and see what kind of performance we can get with those. It might be our only option going forward. The good thing with the soft codecs are that they should working with the overlay replacement already without any work from us.

At the end of the day, even full UI acceleration isn't going to be perfectly smooth on the Nook Color. The GPU and memory bandwidth just can't handle all of it smoothly. It will at least be an improvement versus no GPU acceleration.
[Nook Color Android Development] dalingrin:
Yes. We've been doing this for a while but its just now being published for review.
[Nook Color Android Development] dreamhunterr:
Since LG is updating to ICS the Optimus Black which is afaik an OMAP3 with a SGX530 GPU, doesn't that mean we could eventually use OMX from there?
[Nook Color Android Development] luigi90210:
in theory it could be used but it might need to be back ported to our kernel version in order to work
[Nook Color Android Development] pavlos46:
OK so I am gonna apologize before I even start.

And yes I am very apreciative to all the things that our devs have achieved so far but...

Have you been around the Defy forum lately they are on ICS nightlies already with full h/w ui and other nice goodies and thats an OMAP 3610 device with SGX530 on .32 kernel.

Why can't we......

Pavlos
[Nook Color Android Development] motitas:
I've always had goodluck with those sw codecs so I feel like we'll be fine without the video playback.... probably not the best battery life though. Either way it's good to hear we'll be getting at least some level of UI accel even if it won't be silky smooth. Thanks for your work, I appreciate it.
[Nook Color Android Development] andyrubin1:
Hi anybody...? :D
[Nook Color Android Development] EnTg888:
It seems that driver is for Linux. As in, Ubuntu/Redhat/etc, and it was developed from the Android driver. There's a good chance we already have a working Android driver-but correct me if I'm wrong.
[Nook Color Android Development] unsivil_audio:
Sensitivity around the edge is physical limitation of the digitizer I think. I've never had a problem with it myself.
[Nook Color Android Development] marlonbr:
Holy ****! Awesome!
[Nook Color Android Development] xdp:
Keeping an eye on this. Even if UI GPU acceleration doesn't ever fully come onboard, I'm pretty happy with the responsiveness of CM7 currently, so if it's just like that I'll be completely satisfied.

I'm a little confused about how this works though. I thought the manufacturers had to release their kernel source which would include drivers and anything necessary to interact with the hardware. What are the closed-source components of this that are not included with the kernel? Will this be an issue on other older devices as well like the EVO?
[Nook Color Android Development] Dj-Gutz:
Can you explain why?

Adreno 200 seems to be doing fine ( pretty smooth )

SGX530 is better , and also the posted videos of the Optimus Black ( being worked by Ricardo Cerqueira ) shows perfectly smooth UI

[YOUTUBE]NxtPJozoahU[/YOUTUBE]

[YOUTUBE]iwpozyKyacY[/YOUTUBE]

Also , I guess it's a little early to ask but does USB-HOST currently works on ICS? or modifications needed for that too?

Thanks for all the hard work you guys put into this , you are incredible :D

I think the new driver will be able to give us true Multi-Touch ( more than 2 fingers ) , but I guess that should be concerned on a later date

OT :

CM9 UPDATE - http://www.cyanogenmod.com/blog/cm9-progress-update
[Nook Color Android Development] luigi90210:
he explained why in his post, the nook doesnt have the memory to handle it, and even if it did at the moment the nook doesnt run the same kernel version as the optimus black

idk why people are obsessing about the optimus black though, it has nothing to do with the nook color even if it has similar hardware(i use similar because there are A LOT of differences between the 2 the main one being processor) and even if they were compatible the drivers for the optimus black wouldnt work on our nooks because the optimus black runs a newer kernel than the nook
[Nook Color Android Development] pavlos46:
OK what about the Defy, same amount of ram same kernel version.... any explanation there ?
[Nook Color Android Development] sednafx:
It may be best to wait and see what the dev's are able to do than to speculate on similar devices and their performance. I have faith in Dal and the other devs.
[Nook Color Android Development] angomy:
because each device has a different number of devs each of whom can only commit a certain amount of (I should mention unpaid, of their own good will) time?

Remember what Thumper's mum said..
[Nook Color Android Development] KnowledgeBroker:
NOOOOOOooo.. don't say that, the SOD got so bad with 7.2cm I couldn't handle it anymore, as awesome as ICS sounds, I was looking forward to not having SOD more than anything else. I'm actually installing miui because it is the last rom I remember running that I didn't know what SOD was, haha.

And if I'm reading right, people are compiling their own builds while development is going on to test changes and help out right? There will eventually be an official release still though right?

Also, I just realized what sucks about miui.. I want my buttons and bar at the bottom damn it. :(
[Nook Color Android Development] gambit07:
As far as the SOD's go, make sure you're not using beautiful widgets (maybe any weather widget). I got rid of beautiful widgets and I almost never have SOD's anymore. Hope that helps!
[Nook Color Android Development] KnowledgeBroker:
Thanks, when I upgraded to 7.2 I had just done a full wipe and had SOD more often than anytime before.. and that was before I installed any apps at all. It is sad though, I'm so used to having buttons in my status bar and the bar at the bottom, that could actually be a deal breaker for me!

With the progress being made on ICS though I'm not overly worried, I mainly use my nook to consume news or any of the other things I don't think are worth killing my phone for..
[Nook Color Android Development] galorin:
Not sure if this is the right place to ask, been away from XDA for a long time. Anyhow...

Just ordered a refurb Nook Color, probably won't use it in anger as a tablet, I've got a ZTE Blade on CM7.2 to keep me happy, this is more for tinkering. I've done some Linux dev work before, C programmer for the past few years, maybe not enough to help. Is there anything that I can do to assist in the CM9 development?
[Nook Color Android Development] Stale_bread:
Mac OSX lion

The instructions you posted on google docs says Linux. Are the steps the same for OSX? I have tried building several times but it always hangs at creating the folder with a period in front, ".repo". Is building ics possible on a Mac? There is a wiki for building gingerbread on a Mac, is Linux my only option?
[Nook Color Android Development] Modded Darts:
fattire

I thought he tried osx and he ended putting a linux partition on his mac but he said it might be possible.
[Nook Color Android Development] tsukaza:
I went back to 7.1 for stability and fired up my backup PC and upgraded it to Ubuntu 11.10, going to try to build this beast myself :rolleyes:
[Nook Color Android Development] Nburnes:
It's possible. Change necessary ICS things and other misc and you have it. (Hopefully. I don't have a Mac) http://wiki.cyanogenmod.com/wiki/Barnes_&_Noble_Nook_Color:_Compile_CyanogenMod_(OS_X)
[Nook Color Android Development] Midnitte:
Just build from source and take a go at it =p
[Nook Color Android Development] hololight:
Is sound still broken? Does anyone know where the issue is? I can try ajd take a look if no one else is working on it.
[Nook Color Android Development] jschill31:
Hello,

Are you positive that the issue you are having is SOD? When your unit is working have you had any black screens and then references to "Trebuchet"?

Cheers
[Nook Color Android Development] speedfreak007:
fattire said he's working on it and will release a build with sound soon.
[Nook Color Android Development] Dj-Gutz:
Actually I think unforgiven512 is concentrating on sound ( probably collaborating with fattire )

You can check out his GIT for progress
[Nook Color Android Development] inportb:
What's the difference between a really harsh sod and a garden variety sod?
[Nook Color Android Development] nukedukem:
There are great resources on setting up a mac on the AOSP website in the "initializing a build environment" section. If you are running Lion there are a few extra steps required but it is definitely possible. I can't remember exactly what I had to do but I do remember that qemu stuff won't compile under Lion and you have to use XCode v3.x but these are easy to get around. Let me know if you have questions I could probably think back far enough to help a little.

Maybe if I find time I could write up a basic how-to for OSX Lion.
[Nook Color Android Development] Midnitte:
Might that link not help? =p
[Nook Color Android Development] nukedukem:
Thats a great resource, only it is a little out of date. ICS won't compile without some more tweaks in OSX Lion. After a quick look through the one thing that stands out in my mind is installing XCode v3.2.6 specifically. The XCode available for Lion won't work. Someone posted a link acouple pages back that showed how to install v3 in Lion using terminal. I think if someone followed the wiki, and installed XCode 3.2.6 where it states to install Developer tools from the disc, I think it would work.
[Nook Color Android Development] Stale_bread:
Whoa, alright. Well I think I'll just go get Linux ;)
[Nook Color Android Development] nukedukem:
Haha it's actually not that hard to do. If you follow the wiki it will set pretty much everything up for you. If you are using snow leopard it should be all you need i think. If using Lion it's real easy to install the correct version of XCode.
[Nook Color Android Development] Stale_bread:
Would I have to uninstall the version of Xcode I already have installed? I need my current version for an app I am working on.

Also, why would building android need Xcode?
[Nook Color Android Development] Nburnes:
Anyone know why I cannot adb my device from Ubuntu 11.10? Always just sits at waiting for device >.>
[Nook Color Android Development] Stale_bread:
I would blame unity ;)
[Nook Color Android Development] pdanders:
Just spin up a linux VM to compile.. VMs are easier to deal with anyways
[Nook Color Android Development] nukedukem:
You can install it alongside your current version and then point your Android tools to it. It's a specific Mac OS sdk included in xcode that you need iirc. You could probably install just the sdk without the whole 4gb xcode package.
[Nook Color Android Development] nukedukem:
Does your device serial number show up when you type "adb devices"?

If it's just a question mark and no serial number you can go to the advanced menu under storage and select the mtp option and I think it will work. Idk I'm not at my machine atm.
[Nook Color Android Development] Nburnes:
Worked great, thank you. Dk why I didn't try it before >.>
[Nook Color Android Development] keyodi:
The sdcard won't mount in ubuntu using mtp unless you install mtpfs: sudo apt-get install mtp-tools mtpfs. However, ptp works without the need of any tools.
[Nook Color Android Development] 911jason:
Oops... just found my NC dead (was ~65% when last used). After charging for a few minutes it booted up and guess what? Airplane mode was NOT on. Guess I'll be making sure to leave that on from now on.
[Nook Color Android Development] DizzyDen:
Actually... perfect timing... my dev box crashed with hardware failure... I'm setting up an Oracle Virtual Machine setup of ub 11 now... will try this and let you know how it goes.
[Nook Color Android Development] khaytsus:
I debated putting this in the Users or Dev thread... but I figure it might be useful here.

If you're wanting to tinker, but only on SD, and find that your VeryGreen SD card boot partition is too small you have two options... If you have access to a Windows machine, this thread post will help:

http://xdaforums.com/showpost.php?p=16028869&postcount=1214

On Linux, this script will help:

http://www.omappedia.org/wiki/SD_Configuration

The secret sauce is that the partition must start on sector 63. You can do it by hand, then mkfs.vfat, the fat formatting isn't critical, then copy the verygreen files over, and your shiny ICS zip.

I compiled today, thanks to the Makefile inportb provided, and works great! Installed the 4.0.3 gapps linked here:

http://xdaforums.com/showpost.php?p=20455329&postcount=536

Suggestion: Turn on Airplane mode first then, then re-enable wifi.

I've had few problems so far.. Market crashes periodically, a few games won't load, I get ExchangeCalendar FC's every so often, and I had to remove DSPManager so it'd stop FC'ing.

It's as fast as I recall CM7 running off SD card (periodically laggy, particularly downloading from Market) but it's really smooth in a lot of places. Scrolling in browser, Engadget app, etc, is silky smooth. No problems on wifi (wrt54gl, ddwrt), and to make it a tad smoother overall I have played with SetCPU at 1100Mhz/300Mhz and InteractiveX.
[Nook Color Android Development] Midnitte:
Or you could always install NOOKbuntu onto your nook and compile from there ;P

Can't wait to see the first stable release, CM7 is great but 4.0 def seems to be an awesome major step

Is there any reason you didnt opt for 1200mhz instead of just 1100? :o
[Nook Color Android Development] khaytsus:
I used 1200 and 1100 on CM7, and 1200 always drove the heat up and used the battery quite a bit more for no obvious performance gain. I never looked into it, but Dalingrin had a quite thorough explanation of CPU silicon and how to check automatic voltages to see how good your CPU is, I suspect mine was having to drive the voltage up pretty high at 1200.
[Nook Color Android Development] jwzg:
I like this. Make em work for it, and PM me anytime if you have any issues with noobs because of your stance.

This is the kind of spirit that caused me to take the plunge back in the old WM days. Keep up the good work. For various reasons, I don't build myself these days, but I imagine there's someone here that will build a great ROM that I'll load up on the wife's NC.
[Nook Color Android Development] iDidItAll4theNookie:
That was my thought as well. There's a free Virtualbox for OS X, too. As long as you have the resources to spare, it makes for a pretty painless multi-OS box without the fear or trashing your bootloader. What better way to use a quad core (or greater) and all that cheap RAM, right? :D
[Nook Color Android Development] newellj79:
just very often. I synced and built this morning and haven't had one since. its been great. also I haven't seen any references to the launcher (asked a few posts above quoted post).
[Nook Color Android Development] sednafx:
That's what I did. I have a 3.4ghz quad (2600k) with 16gb of ram. The only issue I saw was that vbox uses all four core but only one thread per core. So I had 4 threads that was not utilized. Would that significantly help build times? I wouldn't mind setting up at mint dual boot if it would help build time.
[Nook Color Android Development] Taosaur:
Would it be insane/unworkable to try building (and/or unpacking/repacking Ramdisk) from a live USB? Unfortunately, I do not have the resources for a VM on my aging Windows box.
[Nook Color Android Development] jewnersey:
very nub Q. my nook isnt listed in adb devices. its just blank.

what am i doing wrong

I was able to mount USB in recovery and access my sdcard, but devices lists nothing
[Nook Color Android Development] Nburnes:
Then why not just dual boot? It really is painless. I've been doing it for years.

Same question I asked a couple pages back. You need to mount it as MTP under Storage in settings, then it will show up in ADB.
[Nook Color Android Development] dreamhunterr:
I built if from source without issues, works pretty damn well!
[Nook Color Android Development] Midnitte:
Using a live USB isnt a bad idea (if you dont want to mess with partitions), need to get one that is persistent though
[Nook Color Android Development] jewnersey:
continuing the nubness.. If i am in recovery, after wiping /system /data /cache, how can i get into settings to mount mtp. (i am at the adb sync system instruction)

and if that setting is in ubuntu. i do not see any Storage section in my system settings.
[Nook Color Android Development] nukedukem:
http://nookdevs.com/NookColor_USB_ADB
[Nook Color Android Development] Taosaur:
Hehe,

Taosaur: I have no bread!

Nburnes: Why not eat cake?

;)

For whatever reason, Windows 7 balks at shrinking enough to permit a Linux install. It's recommended with Windows 7 that you let it shrink itself, and I'm hesitant to force the issue given that I don't currently have the Windows install media in a usable form, should anything go wrong. Someday in the far future when I am less broke, I intend to pick up a SSD as a system drive and re-install everything, at which point I will add Ubuntu off the bat.

I have an 8GB USB around here that is probably already running a System Rescue ROM, and I think LiLi USB can make pretty much any build persistent.
[Nook Color Android Development] jewnersey:
thanks, got adb working now:

root@mtpc:~/android/system# cd $OUT

root@mtpc:~/android/system/out/target/product/encore# adb sync system

syncing /system...

cannot open '/root/android/system/out/target/product/encore/system/': No such file or directory

root@mtpc:~/android/system/out/target/product/encore# ls

clean_steps.mk obj previous_build_config.mk
[Nook Color Android Development] nukedukem:
I have no idea why your $OUT dir has only two files. I would try to compile again. Did your build finish without errors?
[Nook Color Android Development] jewnersey:
watching it build there are a lot of warnings and stuff.. and then the final output is

make: *** No rule to make target `vendor/bn/encore/proprietary/egl.cfg', needed by `out/target/product/encore/system/lib/egl/egl.cfg'. Stop.

make: *** Waiting for unfinished jobs....

target StaticLib: libwebp-encode (out/target/product/encore/obj/STATIC_LIBRARIES/libwebp-encode_intermediates/libwebp-encode.a)

looking back over the instructions for building CM. i missed the proprietary files because i had already wiped my nook. that the problem?

EDIT: tried the make -j instaed of mka. looking a little better now.. ill post results
[Nook Color Android Development] khaytsus:
You could build off a live, but you'd have to write the files to a real disk. It's around 26G when it's done building.
[Nook Color Android Development] nukedukem:
I wondered if you hadn't missed the proprietary files if you weren't able to adb into your nook. You are going to need those. Flash cm7 and then pull the files before trying to build again.
[Nook Color Android Development] jewnersey:
alright doing that now.
[Nook Color Android Development] jschill31:
Hello all,

I feal silly asking this but here goes... Back on post #537 Fattire makes reference to being able to remove the link to "local_manifest.xml" that we needed to do as a work around. I thought I did that but when I sync'd last night and pushed out the files I do not seem to have the changes that are referenced? I think I must not be breaking this link correctly, could someone please explain exactly what to remove or how to overwrite? Also there is a reference to being able to actually "mkimage" now but the guide still refers to pushing the files out. I would much rather make a flashable image, could the guide be updated to include the "mkimage" option? Each build brings new options as well as some new challenges. I for one am enjoying this process and have learned far more than my prior "kanging" ability. Thanks for giving me an extra kick in the a$$ and pushing me to learn instead of mod.

Cheers
[Nook Color Android Development] inportb:
I'm pretty sure fattire means that you should update your local_manifest.xml with his latest version. His stuff has not been merged into the official CyanogenMod repo yet, so local_manifest.xml is still required.
[Nook Color Android Development] newellj79:
Is anybody able to write directly to the sd card via download (gmail, browser, dropbox, etc.). I can't. Maybe i'm missing something...
[Nook Color Android Development] Homer_S_xda:
Nevermind...
[Nook Color Android Development] jewnersey:
well i quit.. thanks for your help though.

i installed cm7, pulled proprietary files and tried to start things again but now everything is just wack, some commands work, others arent, so i dunno what to do
[Nook Color Android Development] fattire:
How's this one?

Jump to the section on installing...
[Nook Color Android Development] fattire:
I already removed the reference to the AOSP version of Launcher, so if you use the pastebinned local_manifest.xml, it should default to Trebuchet, the CM9 version with some enhancements...

So, for those who may not be familiar with exactly how the nook boots, basically it goes like this:

Power turns on -> U-Boot (the bootloader) starts up, and starts the -> Kernel.

The kernel (look up "kernel" in wikipedia for those not sure what this is) then needs something to boot "from"-- so what is used is a tiny little directory full of stuff called the "ramdisk". The ramdisk folder loads into memory and it contains a little binary program called "init" and a script (init.encore.rc) that tells the kernel what to do next-- in this case it's mount three partitions on the emmc-- /system /data and /cache. the script also starts up some basic services used by the computer, and starts up Android itself.

A while back I made a somewhat simplified illustration of this boot up sequence. Sorry if you've seen it before...

Anyway, so the ramdisk, called "uRamdisk" is a folder which needs to be wrapped up in a special format so that the kernel can read it and unpack/use it during the boot. For OMAP (the Texas Instrument platform which Nook is based upon), this file needs to be created using (in part) the mkimage command.

mkimage is an open source program, included as part of u-boot (the bootloader). Barnes and Noble provide the source, since it is GPL'd, but though it's been modified by them, it wasn't written by them.

mkimage is included with cm7 and now is a part of the build-- meaning that when you build cm9, you'll also be building mkimage so you should have it available.

the step of making the "update.zip" is basically all there, but hasn't been turned on yet in cm9. Unforgiven512 is working on that as we speak. Or better be. So in a perfect world, the final output of a successful build will be that update.zip, not a bunch of files in /system/etc.

[YOUTUBE]v3rhQc666Sg[/YOUTUBE]

Lots of people have been saying this!
[Nook Color Android Development] fattire:
If you're a little more specific, I'm sure people can/will help you finish...