yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] haze_nme:
Vendor files for encore

I noticed that there are not any github repos for the vendor files. I extracted them using the extract script in the JB branch of the device tree and made a repo so anyone without access to a NC can add this to their local_manifest.xml

<project name="hazenme/android_vendor_bn_encore" path="vendor/bn/encore" remote="gh" revision="master" />

Then when you repo sync you will pull the vendor files. This is helpful if you are building on a VPS.

My only concern is that we are not allowed to host those files, which would explain why there are no repos for them.
[Nook Color Android Development] fattire:
CM10 for NookColor Build Instructions

Consider this tutorial "experimental" and a rough draft. It's an upgrade to the CM9 build guide for ICS and is intended for those to learn how to build NC jellybean...

Keep in mind, this process is rapidly changing and so repositories in local_manifest.xml are subject to change, for example. But it's also for people, especially those who are just joining us, to get an idea of what building a full operating system for a device like the NC is like.

The information here is available if you read through the forum, but I wanted to collect it in one place. Last time, we had hundreds of people building Android from source code for the first time. If someone would like to give it a shot, I'd be curious if it works for ya. (Update: I should also emphasize that this is a VERY experimental, flaky, and in-progress build. It will be using the 3.0 kernel which has known issues with sleep and all kinds of things. Video won't work, sound will be weird, etc. So expect all that. This is for learning and/or fixing purposes only.)

CM10 for NookColor Build Instructions
[Nook Color Android Development] lekofraggle:
I think I found the problem. My git got messed up when I was playing with different gcc installs. After I ensure all is well, I will add osX instructions as there is at least one new step. Install gcc 4.8 (I think this is necessary even on Lion and Mountain Lion)

This is amazing.

~Leko

Edit: local_manifest is syncing.

Another edit, No go, same issues. My manifest synced, but I got the same error on build

make: *** No rule to make target `vendor/cm/proprietary/RomManager.apk', needed by `out/target/product/encore/system/app/RomManager.apk'. Stop.

I re-ran ./get prebuilts, and on lunch, I do not see encore listed anymore.
[Nook Color Android Development] eyeballer:
Yes, please add in the comments anything you find helpful for osx users.
[Nook Color Android Development] jschill31:
Hello all,

Not sure what if anything I can contribute but I will get my build machine set up tonight.

Cheers
[Nook Color Android Development] krylon360:
we wouldn't have given out the instructions to build if we haven't built it ourselves.

now, please keep this thread to dev related questions or comments only.

This includes not asking if anyone can post a zip or can anyone build it.

When someone does build it we ask that a kang not be posted. This is a highly experimental build and we are busting our asses off working out the kinks just to get it to run. The last thing we need is for someone to build it post a cm10 kang thread and not know how to fix the bugs and wait for us to fix them. When we feel its ready for a broad user base it'll be posted and hopefully merged into the CM manifest.
[Nook Color Android Development] lekofraggle:
Alright, I am closer and farther away. I did get past the ./get prebuilts issue, but now I get this...

host C: adb <= system/core/adb/usb_osx.c
In file included from /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/IOKit.framework/Headers/usb/IOUSBLib.h:27:0,
from system/core/adb/usb_osx.c:21:
/Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/IOKit.framework/Headers/usb/USB.h:594:9: error: too many #pragma options align=reset

I think it is a different gcc issue. So, I will try a different variety. I am busy for the next few days, but will let you ll know when I make progress.

~Leko

P.S. WEM 97, read back a few pages (I think real progress started on pg. 243), you can see the exact builds made and the limitations. There are two different kernels, and they both have different limitations. The instructions are for the 3.0.

As far as time wasted, it is a learning curve. If you look at it like that there is no wasting. If you are looking for a production piece, you will be sorry. I was on sneak peak v1 of ics (I did not have time to troubleshoot these problems so I waited as patiently as I could), and I can say as soon as these builds are close to becoming almost stable, I bet someone will release. This has been said before, and that is why people are being curt.
[Nook Color Android Development] krylon360:
Here's a tip. get off reddit; and stop taking TL;DR to the head.

If you would have gone through this thread, you would see that 10 pages ago, we had it booting. Hell, fattire even POSTED SCREENSHOTS from jb 9 pages ago, and I have posted videos of jb on multiple pages. Take time to read. If you don't want a "half-assed answer" don't ask a "half-assed" question.

Now back on topic. We've taken the day off. :) Though, ive been digging into PVR source and versioning, and am going to try to merge in omapzoom's 3-3 kernel pvr source with ours tomorrow night, with the exception of the pvrversion.h which doesnt mach what we are using as our SGX prop files (rowboat's DDK 1.8 SGX source). (The version in our current kernel source matches.)

If I can get it to work; ES4.x has the kernel modules we WANT. they didnt include them with 5.x but there is a way to build them. been working on that while I can at home.
[Nook Color Android Development] fattire:
Really?

"read the forum"?

Yeah, dude. Read the forum. No one is hiding any top sekkrit info. The instructions I posted are called "CM10 for NookColor Build Instructions" not "Hey I Have A Random Theory About Building CM10 That Came To Me In A Dream". As Krylon360 notes, there are also about 3 weeks of posts, including screenshots and videos as well as numerous build details, questions, comments, and other discussion about the build. That follows months of ICS discussion, several build guides, and a parallel 3.0 kernel thread.

Then you show up, read what- the most recent post, and are like "hey, is this all like, theoretical, man?"

What?
[Nook Color Android Development] jromney:
Fattire, Eyeballer and Krylon360 and all the other devs. Thank you for another project that will keep me up into the wee hours of the morning :)

One caveat that I noticed. I tried to compile on my old CM9 build environment (Ubuntu 10.04 32-Bit) with the new local-manifest. I got pretty far, but the brunch error'd out. After some research, Jellybean needs to be built in a 64-Bit environment?! I completely rebuilt my virtual build environment from scratch to 64-bit; VMWare 4.0.4, Ubuntu 12.04 64-Bit (2GB RAM, 30GB HD). Repo syncing now.

Thanks again for all the hard work and getting me once again back into the bowels of Linux!
[Nook Color Android Development] krylon360:
64bit has been a req since gb. There was a hack to get around it but that was since blocked in ics.

I probably would have gone with 10.04 which is what I'm using. Mainly because I've seen issues compiling on 12.04. Let us know if you need any help.
[Nook Color Android Development] ManelScout4Life:
I had everything setup and was in the process of building the rom when I ran out of space on my virtual drive.

Now I got everything setup again and should have a rom by tomorrow!
[Nook Color Android Development] newellj79:
Where can I find the build guide? I use to build cm9 all the time (thanks to fattires help, as well as others) but I've been playing with other toys for a couple of months. Looking forward to trying to build this. Thanks.
[Nook Color Android Development] ziggy34:
One page back.

http://xdaforums.com/showthread.php?p=29075653

Sent from my A500
[Nook Color Android Development] doncaruana:
Actually, the post with the build guide link in it is here, but the build guide itself is here
[Nook Color Android Development] ManelScout4Life:
Almost ran out of space again! but, success!
[Nook Color Android Development] ManelScout4Life:
if i wipe data and flash my build it won't get bast the boot animation. flashing on top of the aokp rom gets me to Android is upgrading screen. I'll play with this more later
[Nook Color Android Development] jschill31:
Morning all,

For some reason I am getting make errors? Any help would be greatly appreciated.

"mkimage" command not found - U-Boot images will not be built

make[3]: *** [arch/arm/boot/uImage] Error 1

make[2]: *** [uImage] Error 2

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory `/home/jim/cm10/kernel/bn/encore'

make: *** [TARGET_KERNEL_BINARIES] Error 2

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

jim@jim-desktop:~/cm10$

Cheers
[Nook Color Android Development] eyeballer:
sudo apt-get install uboot-mkimage
[Nook Color Android Development] jschill31:
Thank you for the quick response, and I will certainly try this but why in the world would my mkimage un-install itself? I have built for months with this machine... Anyway, I did see there were some new tools that I had not updated in my SDK so I also did that and will give it a go again.

Cheers

Update, for some reason it did indeed download and install the package...I wonder what I did to erase it from before? I feel stupid....thanks eyeballer!
[Nook Color Android Development] eyeballer:
I'm not sure what causes this, I had the same thing happen to me a while back on ICS. mkimage is included in the cm repo so you shouldn't really need to install it, but for some reason either it doesn't get called in time or correctly. Installing the package obviously takes care of it though.
[Nook Color Android Development] jschill31:
Thanks again for the heads up although it is strange why it happens like you say. My machine is still crunching away without further errors so far so that was it. WOW do this take forever to build the first time . :)

Cheers
[Nook Color Android Development] eyeballer:
Unfortunately your build won't boot =/

I just pushed a change to the boardconfig that will allow it to boot but audio is still broken. Might want to re-sync and rebuild. Alternatively, you could let your build finish and try this fix from fattire to get it to boot: http://xdaforums.com/showthread.php?p=29100091#post29100091

Hopefully you enabled ccache with the build so future builds will be much faster.
[Nook Color Android Development] fattire:
Yeah, some changes were pushed upstream to the main cm repositories yesterday relating to legacy sound, so we have to adjust our stuff to maintain compatibility... this is discussed in the NC general section in another thread but the fix for now is to remove the AUDIO_LEGACY fromthe boardfile... sound breaks, but th boot continues... so let's see if we can re-enable sound.

Everyone having fun?! :)
[Nook Color Android Development] lekofraggle:
Okay, I have a noob question here.

I found this repository which may solve the osx issues. But, I cannot for the life of me figure out how to add it to my local_manifest.

This is the site.

http://review.cyanogenmod.com/#/c/19157/.

I have been reading git changes for a while, but have never committed them.

Thank you all in advance for your help.

Again, Sorry for the stupid question.

~Leko
[Nook Color Android Development] fattire:
How to try a proposed commit on gerrit

Heh, this one is easy.

cd to your source code-- let's say ~/android/system (or type "croot")

on your browser, go to the page you referenced and click on the little brown icon that when you mouseover it, it says "copy to clipboard". It's on the far right under "Patch Set 1"

now cd build to get to the build directory.

To apply this commit, paste the command you copied: git fetch http://review.cyanogenmod.com/CyanogenMod/android_prebuilts_gcc_darwin-x86_arm_arm-eabi-4.6 refs/changes/57/19157/1 && git cherry-pick FETCH_HEAD

Done! The changes are applied automatically.

Note: xda's forum software is shortening the link in the command you copy/past, adding "..." to the URL part. That's not part of the command, so make sure you get the full command from the site, not this forum post.
[Nook Color Android Development] eyeballer:
That's already merged, so those files should be in your source folder.

We default the kernel build to use gcc 4.4.3 since it wouldn't boot when built with 4.6.x. If you want to build it with a different toolchain, you can specify it by changing this: https://github.com/fat-tire/android_device_bn_encore/blob/jellybean/BoardConfig.mk#L84
[Nook Color Android Development] jschill31:
Always enable ccache...well saved me the time of even trying. Re-syncing now and moving on.

Thanks everyone, this is just the way it goes this early in the game. ;)

Cheers
[Nook Color Android Development] ManelScout4Life:
removing the audio file from sys let me but it but no touch support for some reason. I'm going to rebuild and try again
[Nook Color Android Development] fattire:
Hold off. I think the sound thing is fixed, but another upstream bug seems to break us (and probably anything that doesn't define TARGET_SOC)

with http://review.cyanogenmod.com/#/c/19142/9/services/surfaceflinger/Android.mk,unified line 60

Sluo tracked down the error so hopefully this will be fixed soon. This is what happens when all kinds of exciting changes and fixes are being submitted simultaneously.

In the meantime, if you wanted to just pull that commit and try building, it would be a good way to make sure this is the issue.

croot

cd frameworks/native

git revert f6b9500a44e03414c52d26b87dae47338696f200

then rebuild.

Let us know if it works, builders!
[Nook Color Android Development] lekofraggle:
I thank you so much because you guys taught me not only how to grab a new repo, but also how to make edits without messing everything up. I now understand how gits totally work.

/tangent

For those who do not know how this all works, if you fork a repo, you can make edits without messing up the good stuff. I apologize if this is privileged info and you all do not want 6 billion people forking your hard work. If that is the case and I overstepped, as always, just delete. I am learning as I go here and wanted to share what I can.

~Leko
[Nook Color Android Development] jschill31:
Hello all,

Builds fine but only black screen when booting. I am re-syncing again and trying another build.
[Nook Color Android Development] eyeballer:
As fattire mentioned a couple posts up, this is because of some merges in the mainline. To fix it we submitted a patch to cm, but you'll need to manually cherry-pick it in for now until it's merged

http://review.cyanogenmod.com/#/c/19816/
[Nook Color Android Development] jschill31:
Cool, doing this then re-build. BTW, did it already merge? When I repo-synced it pulled some additional things from the fat-tire git.

croot

cd frameworks/native

git revert f6b9500a44e03414c52d26b87dae47338696f200

Cheers
[Nook Color Android Development] fattire:
No there are some new fixes from steve676 for sound. But the change from eyeballer hasn't been merged yet (it's in frameworks/native) and w/o it I'm guessing a lot of nightlies will be broken tomorrow...

also, just so you're aware, everytime you repo sync you will be undoing any commits in repos that are in the manifest.. Changes that have been made and not commited won't be overwritten, but if you've applied eyeballer's patch and then re-sync, you'll lose them and have to make 'em again.
[Nook Color Android Development] eyeballer:
The cherry-pick replaces that revert, so no need to revert, just sync and apply the cherry-pick as discussed earlier. sluo just checked in a fix for audio which is what you picked up.
[Nook Color Android Development] jschill31:
OK, got it.

Thanks

---------- Post added at 11:09 PM ---------- Previous post was at 10:50 PM ----------

Guys,

So far this runs great, is it me or is the UI phone mode? BTW whomever fixed the sound I thank you. Signed into Google and downloading apps from the market now.

Excellent!
[Nook Color Android Development] leapinlar:
It probably is phone GUI. The nexus 7 with jb runs that. I understand there are some hacks to change that, but don't know if you can change it with build configurations.
[Nook Color Android Development] lekofraggle:
For now, edit your build prop with this.

ro.sf.lcd_density to 170

Which is closer to the Nooks native 169 anyway. However, this may break the market. You could try the one over in the paranoid android forum.

I got it from one of the news threads a few weeks ago.

http://www.xda-developers.com/android/full-tablet-ui-on-the-google-nexus-7/

It should be easy to put in the build, but It may break other things. So, for now this may be best. I will try as soon as I can figure out what is going on with my build. I am close to just installing a virtual box.

~Leko
[Nook Color Android Development] jschill31:
Hello all,

Anyone having issues with WiFi surviving on reboot?

Cheers
[Nook Color Android Development] fattire:
Re: wifi-- probably. please fix it :)

eyeballer/steve676's fix to surfaceflinger is merged now, so no need to bother with any patches.

As of right now, the device should be good to go. So I think it's mostly gonna be kernel fixes for a bit (unless something upstream breaks again)...
[Nook Color Android Development] krylon360:
Just did a fresh sync and build. Wifi works just fine after reboot here.

Now if I can find a way to tell if it's using my pvr modules or not......
[Nook Color Android Development] krylon360:
submitted change http://review.cyanogenmod.com/#/c/19867/ to recognize the OMAP_ENHANCEMENT flag and associate it with com.ti.omap_enhancement = true in system.prop
[Nook Color Android Development] eyeballer:
Yep, wifi and audio are still pretty unstable right now. They seem to die if you let the device deep sleep or even after a few reboots. As fattire said, we definitely need some kernel help. keyodi should be back sometime this week but if anyone else can contribute please do!
[Nook Color Android Development] krylon360:
confirmed. Shut down and turned it on when I got home from work; wifi busted. Audio seems to die during reboots also but after a couple of loops it kicks back into gear.

Well its 910am. I'm going to bed!
[Nook Color Android Development] lekofraggle:
Hey all. It has been a long time chasing my tail. I have learned a lot, but I am going the virtual box rout so I can actually get a build going and maybe help troubleshoot that. Even if I figure this out, I am on Snow Leopard and three versions behind in xcode (3.6) so, any progress I make there may not help too many people.

If anyone else is trying to build on osx, the main incompatibility is gcc, gcc 4.4.3 does not work well on osx, and the others give numerous gcc or other c dependency based errors.

The closest I got, was using 4.4.7 from macports. Yet, I still am pulling out my hair.

Thank you for your help.

P.S. If you try this, you do need to edit the file referenced a few pages back. You will not be able to build on a mac with any other gcc version than 4.4.3 unless you do.

~Leko

Edit, at last I could not.
[Nook Color Android Development] ManelScout4Life:
Man all I'm getting is black screens on boot up now. Is there a way I can fimd out why this is happening
[Nook Color Android Development] fattire:
adb logcat should have some info..
[Nook Color Android Development] ManelScout4Life:
I just get waiting for device. I followed the steps to a T. I get no errors and the rom builds. It's final size right now is 138.4MB
[Nook Color Android Development] eyeballer:
When did you last sync? Unless you reverted that change, used the cherry-pick or built early this morning all you'll get is a black screen. Remove any edits, re-sync and rebuild and it should be fine.
[Nook Color Android Development] jromney:
I'm almost there, but I am getting the following error when I extract the proprietary files and won't let me complete the build/brunch.

remote object '/system/usr/share/alsa/pcm/surround71.conf' does not exist

I'm using Eyeballers latest CM9 build to extract. TIA
[Nook Color Android Development] Whompy:
surround71.conf

I had the same issue. Someone posted all the proprietary files in a repo a few posts back, don't remember the location though. Don't try to boot it a bunch of times and keep turning it off during the lovely black screen though... killed my bootloader and had to go through the whole bootable microSD to fix it. Any chance someone's made a bootable TWRP2 microSD? Would be nice to have on hand for anti-bricking in the future. Here's the contents of the file if it helps, throw it in vendor/bn/encore/proprietary/usr/share/alsa/pcm/:

#
# Hardware output from 7.1 speakers
# Samples must be positioned:
# chn0 - front left
# chn1 - front right
# chn2 - rear left
# chn3 - rear right
# chn4 - center
# chn5 - lfe
# chn7 - side left
# chn8 - side right
#

pcm.!surround71 {
@args [ CARD DEV ]
@args.CARD {
type string
default {
@func getenv
vars [
ALSA_SURROUND71_CARD
ALSA_PCM_CARD
ALSA_CARD
]
default {
@func refer
name defaults.pcm.surround71.card
}
}
}
@args.DEV {
type integer
default {
@func igetenv
vars [
ALSA_SURROUND71_DEVICE
]
default {
@func refer
name defaults.pcm.surround71.device
}
}
}
type empty
slave.pcm {
@func refer
name {
@func concat
strings [
"cards."
{
@func card_driver
card $CARD
}
".pcm.surround71." $DEV ":CARD=" $CARD
]
}
}
hint {
description "7.1 Surround output to Front, Center, Side, Rear and Woofer speakers"
device $DEV
}
}
[Nook Color Android Development] leapinlar:
Eyeballer made one and included it in his guide thread.

See here:

http://xdaforums.com/showthread.php?p=12797652
[Nook Color Android Development] lekofraggle:
I live by twrp on SD. Unfortunately I can not share it because it has a lot of personal data on it. I can posts when I get around to it. In the mean time, here is how I did it.

The instructions are on the twrp site now. It is really easy.

First, make a boot able SD card.

Check out this thread

http://xdaforums.com/showthread.php?p=11987469

[RECOVERY] Making an updated bootable ClockworkMod SD

Then just replace uRecRam and uImage with the files on the twrp site.

You have to rename the files.

I have not gotten goo to use them though. This way I have a clean stock recovery waiting to fix a horrible recipe.

Sent from my NC_CM9 using Xparent Cyan Tapatalk 2
[Nook Color Android Development] eyeballer:
Oops.. not sure why that isn't in the latest build. I was moving some things around on my buildserver so something must have gotten lost. Fixed now.

Also, I now have a TWRP 2.2.0 sdcard image at the bottom of the TWRP page: http://teamw.in/project/twrp2/43
[Nook Color Android Development] jromney:
"If they build it, we will brunch it"
[Nook Color Android Development] jschill31:
Hello,

Here is a great boot animation to use with your build. http://xdaforums.com/showthread.php?t=1782106

Cheers
[Nook Color Android Development] keyodi:
Try removing MMC_CAP_POWER_OFF_CARD or MMC_PM_KEEP_POWER from the peripheral file and see if wifi still works on resume or after a reboot.

additional info: in the zoom peripheral only MMC_CAP_POWER_OFF_CARD is set
[Nook Color Android Development] fattire:
Another one builds!

Welcome to the club!