yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Sine.:
"I got it" :D

Reading this thread since the beginning (even if I haven't a nook), I enjoyed seen your approach (it's not every days that a dev took the time to explain), and only by by reading I've already learned some things.

I would love to see a similar process for the TouchPad, do you think it could be possible? :)
[Nook Color Android Development] nukeruss:
I got it too. My Transformer Prime is getting jealous.
[Nook Color Android Development] msherwood:
I'm definitely not crazy and sound is working here as well. Coming from Fullofbugs1, I did a Nandroid backup, wiped data, cache, and Dalvik, installed Fullofbugs2 and sound was working on boot. Flashing GApps now... I'll see if it sticks.

Awesome work Fattire! Just waiting for a new laptop to start building.
[Nook Color Android Development] sednafx:
I think I must be dense. Where is the second release? fullofbugs2?
[Nook Color Android Development] fattire:
What release? What are you talking about? I just wrote a long-winded explanation about why I think you should build yourself and suddenly everyone's talking about a release.

Why would this be?!
[Nook Color Android Development] sednafx:
I saw the post above mine reference working sound in fullofbugs2. Thought there was a release somewhere, my apologies. I just synced a few moments ago and was waiting till the sound patch was pushed before I rebuilt.
[Nook Color Android Development] fattire:
No worries. Still, you should probably re-read it CAREFULLY, just to make sure. I fear some people are skimming, and that's never good.
[Nook Color Android Development] sunsurfer42:
This is good stuff! Hehehe. Thanks fattire, ill be doing my own build this weekend. You rock!
[Nook Color Android Development] Midnitte:
But thats how I managed to get an A in my world masterpieces class. D:

Thanks for the . =p
[Nook Color Android Development] sednafx:
Facepalm.

You my friend......
[Nook Color Android Development] msherwood:
Ummm... I don't know what anyone's talking about... *runs*

But seriously, sound is working. System sounds (clicks) and even Google Music. After a GApps flash.
[Nook Color Android Development] Midnitte:
Anyone else getting "Random offset: 0x9" (and "Random offset: 0x104") while trying to flash? :o
[Nook Color Android Development] nukeruss:
This is the funniest thread I've read today. Period...
[Nook Color Android Development] boomn:
That message isn't an error, it is because of a security feature added in ICS called address space layout randomization
[Nook Color Android Development] kcls:
Lol, I must be quite tired... am I not getting something here?

Tapatalkin it from my IHO CM7.1'd, MIUI Themed Optimus V
[Nook Color Android Development] fattire:
It's was so good, I told two friends...
[Nook Color Android Development] Novarider:
That's pretty sweet! I hope they get that running on the prime I'm planning on getting one.
[Nook Color Android Development] gsutton:
Thank you for all that you have done for the Nookcolor users. My device would be a disappointment without your remarkable work.
[Nook Color Android Development] jasoraso:
Dalingrin -

Just another note to tell you thanks for all you do. I have a Nook Color, and Touchpad, both running cm7 thanks to you!

If anyone doubts Dalingrin's understanding of the challenges facing CM9 on the NC, just look at his app (nook tweaks) and his kernel that he has already put together for cm7 on the NC. He is well aware of the bottlenecks and limitations of the hardware on the NC that B&N built as a color reader, and has already made several tweaks in the kernel and otherwise to eek out every bit of performance possible from the NC with cm7.

As a side note, several months ago, Dalingrin made a rare comment about the B&N folks and their programming skills - to the effect that he understood better than they their own product. I think the main reason that the Nook Tablet exists is because B&N understands the hardware limitations that exist in the NC, and that the bottlenecks in the graphics area with the screen resolution on the NC (and I wouldn't be surprised if much of that understanding comes from analyzing Dalingrin's work on cm7 for the NC).

Here's to hoping that Dalingrin CAN and WILL continue to work his magic to get us cm9 with the best possible performance, given the hardware limitations.

I appreciate Daligrin's dropping by to let us know that he is spending SOME of his time and energy on the Nook Color, and that there is a CHANCE that there might a usable CM9 in our future ...

PS> just added the Transformer Prime to my wish list ... after seeing that Dalingrin might be dev'ing for it!
[Nook Color Android Development] Toys Samurai:
In the HoneyComb SDK ROMs, there are problems with the touchscreen (sometimes, it fails to recognize a touch completely). Does CM9/ICS exhibit the same problem?
[Nook Color Android Development] sednafx:
Same here! Though I am not sure what I need another device for? Already have 4 laptops, 3 desktops, and 2 tablets in my house. Ya... I am an addict.
[Nook Color Android Development] gordon1hd1:
:( I was hoping that you like the 7inch form factor, and might take an interest in the NT, seem that you prefer the 10inch form factor more. Well thank you for answer my question.
[Nook Color Android Development] koopakid08:
You're kidding right? Honeycomb is and always will be a fail. It was not ported with source code from Google, it was ported from the SDK.

---------------------------------
[Nook Color Android Development] fattire:
The issue w/the ics driver was two things had to be added--- 1. BTN_TOUCH flag needed to be registered when a finger went down and lifted off. 2. proper ids for the touches needed to be registered as well, as they were being misidentified. The new driver, updated by dalingrin, does both of these things, and so now touch works fine-- as well as it did before in cm7 as it's otherwise the same driver.

New kernel forthcoming will fix the color banding issue (when i get around to pushing it).

Update: added 3 pictures up top somewhere.
[Nook Color Android Development] fattire:
So this looks to me like you've got an overlay in android/system/vendor/bn/encore/ that you don't want. Try chucking that directory.
[Nook Color Android Development] nukedukem:
Fattire - would you mind sharing the steps you take to get this booting on the nook? keyodi posted a step by step in the other thread, but I can only get that to boot into a message that SystemUI has stopped.

Thanks for your work!
[Nook Color Android Development] newellj79:
Thanks. will try again. before I seen your reply I had already deleted android/system and was starting over. I thought maybe something from cm7 was effecting it. at any rate I appreciate it. awesome news from u above! can't wait.

Edit... while syncing It keeps hanging at 99% 233/235. Maybe I'm destined to not be able to build. ::(
[Nook Color Android Development] KnowledgeBroker:
Honestly, I've been wanting to get into it, I've been in the development section of xda, I downloaded the source in linux, started compiling.. but when doing more research it feels like there is a starting point I'm missing, or that I am skipping.

I really sincerely wished that devs who are tech savvy, but didn't already know all of the programing languages, shared step by step how they got to the point they did.. it feels like there are just a few things I am missing before I can shout "Eureka!"

I've jailbroken, rooted, modded every single device I own. My camera is hacked, my ps3 is hacked, I have hacked probably over 50 other devices for myself and others-- so I just wish I was seeing what I am missing to jump into the dev game.
[Nook Color Android Development] Dj-Gutz:
Defy dev's got FULL 2D/3D acceleration working now - THREAD / GIT + Proprietary Files ( New EGL libs )

Hope this helps ( I keep on watching close specs devices ) :)
[Nook Color Android Development] Backwardsblade:
As always, thanks for your continued support dalingrin and fattire. Will be following.
[Nook Color Android Development] brianf21:
I was able to compile it. I then created a recovery flash that copied over the kernel, ramdisk and system. It boots but the screen is black with a backlight. When I try to connect to it via adb I get the follow error

- exec '/system/bin/sh' failed: Exec format error (8) -

So, I know the kernel is loaded, but I can't do a logcat or dmesg. Now here is my question, do I need to manually recreate the ramdisk? I used the one that was created during the build process. Does the fact that the kernel loaded indicate that it is not a ramdisk issue and I am just barking up the wrong tree?

I checked the permissions for /system/bin/sh and they are 755 root shell.

Thanks for your work dalingrin and fattire!
[Nook Color Android Development] Nburnes:
Well got past SystemUI.apk force closing (by deleting it). Now Launcher force closes and can't move past that. >.<
[Nook Color Android Development] cchant:
delete it? lol
[Nook Color Android Development] Modded Darts:
progress

So I am sure that this has already been posted in the thread some where but as of right now what is working for cm9 and what isn't?

Thanks to Dalgrin, Fat Tire, and all others who are working on this build.
[Nook Color Android Development] mrapollinax:
First two posts in this thread will have all the information you need.
[Nook Color Android Development] fattire:
Yeah don't trust the ramdisk.img that's there. You can use the handy-dandy ramdisk-tools.sh that's in $OUT to recreate it. just use the -h flag and it'll give you instructions.

Also I guess I can push the egl stuff that finally made it upstream so everyone can enjoy the blue. Look for that soon. I worked last night on backporting netfilter stuff as well to the kernel, but it's panicking so we'll see if I can figure it out. There's a shortcut solution using a dummy netfilter as a backup...
[Nook Color Android Development] mrmark93:
I remember that ad when it was 'in play'...

oh, and thanks, I got it.
[Nook Color Android Development] dizgustipated:
Pure, pure, 100% pure genius!

I dev on an older computer, with a mere 1gig of ram,

needless to say it causes some make otapackage and bacon commands!

With-out stumbling upon this awesome "little" script, (with modifications for my device)

I would be stuck, forever building Heimdall images.

Now, with a quick,

make snapshot

&

make package CLEAN=1

I know have the ability to make a flashable zip in the blink of an eye!

Which is signed, and packaged correctly.

Not to mention build more efficiently

Thanks!!

kudos!!

and to FatTire also!

I was curious If I could spread this to my dev team, to help us make a better CM9.

Who else do I need to pro quire permissions from?

Again,

Great, just great

:)
[Nook Color Android Development] xdp:
Also curious when the keyboard got so tiny, the old size was perfect.
[Nook Color Android Development] jschill31:
Hello,

Seem to keep getting the same error, even after make clean:

host Executable: minigzip (out/host/linux-x86/obj/EXECUTABLES/minigzip_intermediates/minigzip)

true

Install: out/host/linux-x86/bin/minigzip

Target ram disk: out/target/product/encore/ramdisk.img

/bin/bash: line 1: 25492 Broken pipe out/host/linux-x86/bin/mkbootfs out/target/product/encore/root

25493 Illegal instruction | out/host/linux-x86/bin/minigzip > out/target/product/encore/ramdisk.img

make: *** [out/target/product/encore/ramdisk.img] Error 132

make: *** Deleting file `out/target/product/encore/ramdisk.img'

jim@jim-desktop:~/android/system$

Not sure what has broken after several successful builds? Deleting the minigzip just seems to rebuild it...am I correct in thinking minigzip is corrupt? Anyone have any ideas?

Thanks
[Nook Color Android Development] inportb:
Glad that worked for you; it's MIT'd, so feel free to use it in your project. Though, I'd like to mention that it probably needs some cleanup ;)
[Nook Color Android Development] alershka:
Well, after reading the post for at least the 20th time. I did slow down and read it much much much more carefully and to my surprise, it is now all clear.

I was successful in getting my build up and running last night. Now I have something else to do tonight. Thank you so much for everything. It hasn't always been easy but it has been fun.
[Nook Color Android Development] fjevel:
Why would you load an ICS driver on CM 7.1? And why bring this up in a dev thread for ICS?

-KJ
[Nook Color Android Development] Jainyankee1993:
How are you going to put it on to a SD card?
[Nook Color Android Development] Midnitte:
Ah ok, thanks! Now any reason ics gapps would say "bad"? D:

Republic Wireless using Tapatalk
[Nook Color Android Development] pbot:
I have the same problem as mentioned recently, the latest builds will bootloop just using verygreen's installer. Since verygreen's installer doesn't wipe, you will need to install the first sneakpeek which boots on SD fine then a second sneakpeak over it if there was one.

If you resize the partition and rename gapps, verygreen's will do both at the same time.
[Nook Color Android Development] MrColdbird:
Im kinda curious, is the walkthrough draft still up 2 date?

Do we still have to do step 4 to get emmc working or has it been included into the base already?

I'm also wondering whether the Beagleboard Patches have been included into the base, if not - if they will be included eventually and whether I should apply them myself.

Do you guys notice a lot of changes with them or not? Any downsides to using them?
[Nook Color Android Development] crono141:
How is battery life on the newer source builds?
[Nook Color Android Development] jalexishg:
I always support developers donating and helping in every way I can unfortunately not everybody have a super computer to build. I try and my computer is not strong enough to let me compile on it, I have 3 laptops at my house my wife computer is a no no, next my 13.3 MacBook 03 is not strong enough and last but not least my Acer aspire one (net book). I do understand what you trying to do here but what can I do ? Not enjoy progress, cause I can't build on my computer ? Like its my fault, I never ask for ETA or for updates but as I see here we ain't getting no zip update Anytime soon, well I guess I'm letting my device go since I need a to have a computer to build that I don't have. I love my nook I think is one of the best devices ever but if I have to spend $300+ on a computer just to build when you can share some updates, I rather buy a new tablet. Not all of us have the time or ability to build and I do donate a lot of my money I can provide proof, I'm not demanding an update I'm asking to be fair with some ppl.
[Nook Color Android Development] johnny15:
You should keep an eye on the second post of this thread. Fattire posts updates there and you should read them carefully! You might find something interesting in there. :)
[Nook Color Android Development] crono141:
Read back a few pages. Fattire posted an explanation post in the last 5 pages that contains everything you need to get what you want. ;)
[Nook Color Android Development] dizgustipated:
Very clever.

I'm seriously thinking about adopting that method
[Nook Color Android Development] jalexishg:
I did.

I don't want nobody to think I'm demanding an update or telling someone what to do. I'm trying to find a cheap computer or upgrade the ones I have to see if I join the development of this device believe me nothing will make me feel better than being able to be part of something this big. But xmass just past, another holiday coming (3 kings since I'm from Puerto Rico), money is tight at the moment. All I just want is a changelog saying this is what we got so far, I DON'T NEED A LINK OR A ZIP to be happy. I understand most of you guys do this for fun or in your free time and nobody is paying you guys but a little details of the progress wont kill at least for me. Sorry If anyone got offended by this, I was just expressing how I feel.
[Nook Color Android Development] MrColdbird:
Oh well... currently rebuilding. Hopefully up 2 date in an hour.

My i5 should handle this. :)
[Nook Color Android Development] zequav:
What's the newest recommended gapps? Still _v8? Any place to keep track of them?
[Nook Color Android Development] Yunkmaster:
I am really sorry!

After i have read your post, there are only two options:

1. i'm just too stupid

2. my english is too bad :(

Yunky
[Nook Color Android Development] MrColdbird:
I guess I was too fast to talk.

Just came back to the PC to see it errored out on me... it seems there out/host/linux-x86/bin directory doesn't exist and the compiler complains about the dx tool missing, which is no surprise seeing as the directory it should reside in is nonexistant alltogether.

Any ideas? Did I miss something? I used to be able to build this just fine.
[Nook Color Android Development] fjevel:
3. You're not reading the post thorough enough...

4. You didn't find the clues left by others; read the last few pages after fattires last post.

:)

-KJ
[Nook Color Android Development] mrapollinax:
Since I've been building and flashing on my own I missed the excitement. Just wanted to throw in my thanks to fattire, dal and everyone on the dev team.

Best damn dev team there is. PERIOD.

;)
[Nook Color Android Development] MrColdbird:
Damnit... corrupt sync... I simply missed a bunch of files I think.

Retrying a sync now... please work.

EDIT: For those worried bout movie playback. Stick to Mobo Player + ARM7 Neon Codec Pack, then change the decoding setting to "Software Decoding".

Works great for me.
[Nook Color Android Development] Neckberg:
You should really re-read fattires post, period, point blank.

In the post you will find all of your answers.
[Nook Color Android Development] bassrebel:
just go to the second post, read everything and you will find all the updates, what's working, what's not...

I just tried the .zip full of bugs to see if I could do some quick OnLive gaming with my xbox360 controller, but not yet... *sighs* I guess I'll have to wait a lil bit more
[Nook Color Android Development] bytte:
I expected the screen input code to be independent of ICS - but I may well be wrong - hence my question.

Was this a bug in the original driver or an ICS required change - the ICS community seemed like a good place to ask.

I didn't expect ICS changes to break apps. If you are happy nothing is wrong I'm sorry to have wasted your time.
[Nook Color Android Development] jewnersey:
i got it. . .. .

ive also learned a lot by building, so thank you..
[Nook Color Android Development] michaeljr10wv:
This might be a stupid question, I havn't built it for a few days, but is sound in the repo now?

Mike
[Nook Color Android Development] DizzyDen:
Verygreen's script does a wipe... watch the screen closely when you do an update ;)

I understand money being tight in this day and age... but understand this is similar to any software... only its free... you can't get the newest bells and whistles until the developers decide its ready for release... until then you may be stuck at using what currently exists. That is not necessarily a bad thing.

And to be honest... your first post about it did come across as demanding a release.

Read fattire's post a few pages back and pay special attention when he mentions the period at end of 3rd sentence... also notice the underlined word at the end of that sentence drawing attention to it and making it easy to find.
[Nook Color Android Development] segfaultex:
Was there a solution to the errors in the second code block for this? :confused:

I'm having the exact same problem except everything is in ~/android/system .

My machine is also Ubuntu 11.10 server but running on a poweredge 1850 not a vm.
[Nook Color Android Development] rhester72:
Dumb question: Does ICS/CM9 for the NC utilize Dalingrin's kernel (or at least kernel mods) from CM7 (particularly those concerning CPU steppings and volume control)?

Rodney
[Nook Color Android Development] fattire:
Yes. You should be able to use SetCPU as well as Nook Tweaks. Be careful with overclocking though...
[Nook Color Android Development] scottgti:
Is anyone using this on sd? I have seen a few people having issues . How would one start with a fresh install on sd? I have made cm7 sd cards many times. I have failed at making cm9 sd cards many times. Any help would be appreciated. Thanks to the devs for everything. Period.
[Nook Color Android Development] MrColdbird:
Finally managed to pull a full copy and compile without errors... installed on my Nook, all fine and dandy...

But still no sound?! The hell?
[Nook Color Android Development] boomn:
Yep, just did it last night using tips I saw in this and the other CM9 thread.

flash verygreen's generic-sdcard-v1.3.img

use a partition manager to expand the boot partition (I don't know the minimum necessary but I made it ~150mb and it worked, I used Easeus partition Manager)

drop the sneakpeak1 zip on the boot partition

insert into Nook and boot to let the verygreen installer run

reboot into CM9 and let it sit for a little while to settle down

put card back in pc and drop sneakpeak2 onto the card

insert into Nook and boot into recovery to make the verygreen installer run again

reboot into latest CM9 build!
[Nook Color Android Development] scottgti:
Thanks. I'll check in a little bit. I was so close. I may have made boot partion too big?

Edit- I'm sure it's user error.
[Nook Color Android Development] boomn:
I don't know, I can't see that being an issue. I do remember seeing in one of the comments that you need to make sure that resizing didn't change the location of the first sector of the boot partition. I think the Nook requires it to be at sector 63

What errors did you run into?
[Nook Color Android Development] scottgti:
As verygreen installer is working I notice a lot of I/O errors. Seems to hang at note: mmcqd[563]. Exited with preempt_count 1

I used sd formatter. I used winimage to write verygreen. I used partion master to resize boot to 150 mb. Hangs on install. Thanks for the help. I love ics on my xoom, I'm patiently waiting for the nook.
[Nook Color Android Development] scottgti:
And boom goes the dynamite. I believe my Sandisk 4g class 4 sd card just crapped out. Trying with other card, no errors. I knew I was doing it right. Thanks for the help.
[Nook Color Android Development] Yunkmaster:
Blindness with healthy eyes is a real disease!

But finally...

Got it!

Yunky
[Nook Color Android Development] J-ROCK:
Thanks to Fattire I have been very SUCCESSFUL!! Thank you!
[Nook Color Android Development] Midnitte:
No one? D: Cant seem to flash gapps on this latest zip... :(
[Nook Color Android Development] alershka:
Any thoughts on when it might be safe to be able to build again? I have the latest gift installed which should be great as a daily driver but I don't want to flash a build over it and lose it's leaky greatness.

---------- Post added at 01:19 AM ---------- Previous post was at 01:15 AM ----------

I did a quick google search for ICS GApps 4.0.3 and used that. I did it on the Nook but did a wipe before I flashed Gapps so I don't have the site anymore. The name of the file is Gapps ICS 4.0.3 11.12.22.zip
[Nook Color Android Development] MrColdbird:
No matter what I do I cant get sound working!

Damn this. >_<

Everything compiles fine, no trace of a single error... everything works but not the damn sound. This thing is mocking me!

I'm desperate now. Are there Hardware Differences between Nook Colors that could cause this or what could be the cause for my problem?

Does someone have the slightest idea?
[Nook Color Android Development] JP12:
The sound fix isn't merged to source on GitHub yet.
[Nook Color Android Development] mkm1126:
http://www.mediafire.com/?db9zc0mq1lj0gqe

Try that one.
[Nook Color Android Development] MrColdbird:
I'm relieved now.

I thought I had gone nuts and did something totally off when compiling. Some voodoo mumbo jumbo going wrong or something.
[Nook Color Android Development] aqtrans:
Maybe something to do with the Java SDK you installed? I had to install the JDK6 package from the AUR on my Arch x64 server: http://aur.archlinux.org/packages.php?ID=51907