yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] fattire:
We should add this to the build, and perhaps look into cm adding it as well.
[Nook Color Android Development] krylon360:
Found the issue with WiFi I was having. The build isn't creating ipconfig.text which goes in /data/misc/WiFi. So when you do a factory reset and flash, it deletes that file and no WiFi. Restored cm9 reflashed cm10 without wiping and i have WiFi now.

Deeper-blue fixed the keyboard layout and added soft keys. Those are now in the encore jellybean epo

Posted from cm10
[Nook Color Android Development] steven676:
That would be nice, but (assuming you mean building procps as part of the Android build, not treating it as a proprietary blob) it would involve actually porting the code correctly to Android. This binary is just statically linked against glibc to avoid that work.
[Nook Color Android Development] Cypher2:
NC voltage - Nook Tweaks

@dalingrin:

I have experienced many freezes with eyeballer's builds, even up to the more recent ones, opengl and non-opengl ones. Changing the performance options and the rendering properties didn't help either.

I stumbled on your nook tweaks app on the market and gave it a go: I found that pumping the default voltages enabled better performance and got rid of lockups and freezes.

is there any way to up the voltages on the default loaded kernel for the next builds? (your app doesn't load the settings on boot even when it is asked to do so)? Or is it possible to add an option within cm to play with voltages?

Thanks
[Nook Color Android Development] BobbyBest:
Did you OC? Usually the pre-set voltages should be more than high enough for 800 MHz...
[Nook Color Android Development] antp121:
Holy sh!t you guys are epic.... I moved on to the touchpad but I'm still running cm9 on my nc thanks to you guys :)
[Nook Color Android Development] Cypher2:
No OC. I simply pumped the voltages and kept the throttle at conservative. I put min. To 600 and Max to 1200.

My cm9 installs are choppy if I don't do that.

Any idea if that is normal?

How is the performance on cm9 for you guys?
[Nook Color Android Development] fattire:
CM9?

Oh, I kid.
[Nook Color Android Development] Henk Poley:
OC = OverClock = a higher amount of clock ticks than regular

The regular maximum clockspeed of the Nook Color is 800. If you set max higher (to 1200), you are overclocking.
[Nook Color Android Development] krylon360:
got it to load the sound driver:

http://pastebin.com/uR7n64yr

EDIT: Hrm; cant get it to load again.... CRAP!

Still doesnt play though. gotta figure out the libwvm.so issue.

I've tried different ones in both /system/lib and in /system/vendor/lib like it is on the N7

This is what I come out with:

http://pastebin.com/v7y0YLjA
[Nook Color Android Development] Cypher2:
I know what overclock is and means. I assumed I wasn't overclocking since those clock speeds were built in to dalingrin's kernel. I would consider it being over locked if it passed over the 1200 mark. 800 is so yesterday :).

But ya. Even at 1200 there is choppiness unless I pump the voltages. Anyone?
[Nook Color Android Development] leapinlar:
Not all nooks are created equal. Some cannot even OC to 1100 without choppiness. It really depends on the quality of the chip in your unit. But raising voltages does help some, but be careful, the unit will run at a higher tempurature.
[Nook Color Android Development] mateorod:
I am not certified thread police (oh, if only!) but pretty please don't scare the devs back to IRC. We have end-user space for this stuff.

If you have an idea for the kernel, go ahead and make it yourself. But AFAIK dalingrin isn't taking feature submissions at this time...let's all be quiet and maybe they will keep sharing their progress on JB.
[Nook Color Android Development] eyeballer:
For those building along at home, the bionic part of the patch is no longer needed. deeper-blue submitted it and it's merged into cm http://review.cyanogenmod.com/#/c/18945/

Also, not sure if this was mentioned, but you'll want to remove kernel/bn/encore so that your build uses the prebuilt kernel instead of inline building, otherwise you'll get a black screen. Might be a gcc issue with our 2.6.32 kernel.
[Nook Color Android Development] fattire:
I'll just leave this here.

For more do-it-yerselfers, I was trying to see if we could use the hardware/ti/omap3 repository from TI on the jb-release (or jb-dev) branch rather than the ancient version provided by cm. To do this, add the following to your .repo/local_manifest.xml:

<remote fetch="git://git.omapzoom.org" name="oz" />

<remove-project name="CyanogenMod/android_hardware_ti_omap3" />

<project name="platform/hardware/ti/omap3" path="hardware/ti/omap3" remote="oz" revision="jb-release" />

You'll notice after repo syncing that you get some build errors. This patch seems to get those build to complete. Mostly it was a ton of "LOCAL_MODULE_TAGS := optional" but a couple more changes seemed to be necessary.

The catch? It's nearly 3am and I haven't tried a new build to see what happens.

Guinea pig anyone? If no one tries it by tomorrow some time I guess I'll give it a shot.
[Nook Color Android Development] steven676:
While we're on the topic of guinea pigs ... this was tried out, but krylon ran into this problem -- the legacy ALSA libaudio.so fails to link because of a missing symbol. A reading of platform/frameworks/av/media/libmedia/Android.mk implies that this symbol (demangled, it's the constructor for the AudioParameter class) is included in AudioParameter.cpp, which is the only component of libmedia_helper.a, which should be linked into libmedia.so in its entirety ... and yet I can say with confidence this isn't just a byproduct of our various build system troubles, because the symbol doesn't appear in libmedia.so in the offical builds either.

We're presumably going to have to figure out how to build these components properly at some point, but for now, I've built audio.primary.encore.so and libmedia.so by hand:

http://www.ocf.berkeley.edu/~sluo/android/audio.primary.encore.so

http://www.ocf.berkeley.edu/~sluo/android/libmedia.so

If anyone wants to be the guinea pig ... install libmedia.so to /system/lib and audio.primary.encore.so to /system/lib/hw. Grab libaudio.so, libasound.so, and liba2dp.so from /system/lib a CM9 system and install those to /system/lib. Grab https://gist.github.com/3103399 and stick the contents in /system/etc/audio_policy.conf. Boot and hope for sound, or at least revealing log messages ...
[Nook Color Android Development] krylon360:
http://pastebin.com/vUH1FKUn

Looks like I "might" have gotten the video and audio codecs to pick up. but audio driver is still a no go.

Edit

okay yes, video does work. No Audio though

Had to use VLC since for some reason the Video Player isnt on here, and my wifi has been busted ever since I sync'd CM merges yesterday.

http://pastebin.com/Q0KARJXy

[YOUTUBE]DfQkV4abpEI[/YOUTUBE]
[Nook Color Android Development] steven676:
E/HAL ( 1089): Cannot load library: link_image[1916]: 1089 could not load needed library 'libaudio.so' for 'audio.primary.encore.so' (reloc_library[1331]: 1089 cannot locate '_ZN7android11AudioSystem8popCountEj'...

Damn, we've still got symbol issues. Might have to actually port libaudio properly ...

For reference:

$ c++filt _ZN7android11AudioSystem8popCountEj
android::AudioSystem::popCount(unsigned int)

That ring any bells for anyone?
[Nook Color Android Development] fattire:
FWIW my patches to hardware/ti/omap3 do work. I just did a clobber build and it's booting and working. seems a little smoother w/the 3.0 kernel. Eyeballer though is having trouble applying the patches. Not sure why.

I tried the audio.primary.encore.so and libaudio.so but didn't have sound. I didn't use the audio policy conf tho.

E/AudioPolicyManagerBase( 107): could not load audio policy configuration file, setting defaults

E/HAL ( 1243): load: module=/system/lib/hw/audio.primary.encore.so

E/HAL ( 1243): Cannot load library: link_image[1916]: 1243 could not load needed library 'libaudio.so' for 'audio.primary.encore.so' (reloc_library[1331]: 1243 cannot locate '_ZN7android11AudioSystem8popCountEj'...

E/HAL ( 1243): )

E/AudioFlinger( 1243): int android::load_audio_interface(char const*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)

I/AudioFlinger( 1243): loadHwModule() error -22 loading module primary
[Nook Color Android Development] steven676:
Okay, that turned out to not be so difficult after all -- mostly ALOG stuff and dealing with the shift of legacy audio stuff into namespace android_audio_legacy. See https://gist.github.com/3125182 for the details (applies on top of the gingerbread branch for platform/hardware/alsa_sound).

New blobs posted -- http://www.ocf.berkeley.edu/~sluo/android/audio.primary.encore.so and http://www.ocf.berkeley.edu/~sluo/android/libaudio.so -- which can be used with the libmedia.so built via your regular build process.
[Nook Color Android Development] krylon360:
Will try these when I get to work
[Nook Color Android Development] fattire:
Tip your waitresses!

Umm, so everyone give steven676 about a thousand "thanks".

We've been messing with this for about 5 hours now and-- with him building just about every component that matters-- I now have (quiet, quiet) Angry Birds playing music.

There's' still a lot screwed up... volume is weird. I can't seem yet to play notification or ring music. It's ridiculously quiet. headphones aren't working. But this is the 3.0 kernel. This is jellybean.

And we have some very quiet sound.

Note: Add to libaudio.so above with the legacy symbols, you'll also need alsa.omap3.so. Here is my /system/lib/hw:

alsa.omap3.so

audio.a2dp.default.so

audio.primary.default.so

audio.primary.encore.so

audio.primary.omap3.so

audio_policy.default.so

If audio_policy.encore.so shows up in your build, get rid of it. Use the default. Also, audio_policy.conf is NOT needed as yet in /system/etc.
[Nook Color Android Development] meteorrock:
ooo hai there <fattire> lol this is me being random :3 Thanks for the work on the kernels guies. I gave out all of my thankies for the day so I will give out more tomorrow.

Try to recompile your kernel and see if it helps boost sound. Might also want to decompile dalingrin nook color tweaks to have a look at that code and try to somehow implement it into your kernel. Or change the value for the audio gain. Be careful here or you will break the app on the playstore.
[Nook Color Android Development] fattire:
More newz

Strangely enough, you're right. It's the 3.0 kernel of course. Keyodi's gonna look at the codecs and hoepfully we'll turn it up.

No need to decompile it. The source is here.

And... krylon has normal (that is, not quiet) sound going in the .32 build of Jellybean. And netflix sound even works :)
[Nook Color Android Development] meteorrock:
wow you guies are smart. Time for me to run off and play. LOL. :cool:
[Nook Color Android Development] krylon360:
yeah, that surprised the hell out of me, exp when I can only get about 2 secs of sound in ICS Netflix on .32

just listed to a whole episode of spoungebob. Key word.. LISTENED!

Now I have "Its a Krusty Krab Pizza, it's a pizza made for you and me" stuck in my head
[Nook Color Android Development] bigrat:
"It's a rock! A big, beautiful, rock. Oh, the pioneers used to ride these babies everywhere!" ;)

Nice work, guys.
[Nook Color Android Development] fattire:
To anyone building today-- a TON of changes on the 3.0 jb branch, the focus of our efforts. Look for all steven676's prebuilt libraries and tons of new stuff to support sound, as well as prebuilt kernels and wifi modules... it builds to the end, I just checked, though I won't actually flash it to test until tomorrow. I think krylon's got one last 3.0 build going tho.

It's been like 12 hours but we got sound :) Nite all and great job all 'round.

oh, did I mention that 3.0 comes up from sleep? And eyeballer checked in something so the backlight is built from source.. and works perfectly too.

We need to see what happened to wifi tho.
[Nook Color Android Development] krylon360:
your wifi still borked? My test build is done and uploading now. will flash here in a few. If wifi is broke on my 3.0 build, then it's this commit that did it: http://review.cyanogenmod.com/#/c/18930/ this was done in v8 which is what 3.0 uses.

my issue on .32 was after a factory reset it wiped out ipconfig.txt from /data/misc/wifi

restored to CM9, reflashed my CM10 build and wifi worked.

Update: no wifi.

http://pastebin.com/Un9PHVjf

I'll do reset --hard tomorrow on the v8 branch, though; im thinking this is more driver related. Keyodi? could you have a look?

Here's a video with sound

[YOUTUBE]vaCUJdXn4uc[/YOUTUBE]
[Nook Color Android Development] krylon360:
fattire, keydi, sluo, eyeballer,

and ayone else building at home.

DO NOT PUSH audio_policy.conf that steve posted earlier.

You'll be stuck in a nasty loop that looks like this:

http://pastebin.com/MJeRfhJf
[Nook Color Android Development] arrjaytea:
Absolutely drooling m8.
[Nook Color Android Development] fattire:
Incidentally, we've also noticed that the OPENGL version (currently turned on) is a little more slow/stuttery than non-opengl which is ridiculously smooth. Dunno why this is.

Also, if you remove /system/media/bootanimation.zip the boot is way faster...
[Nook Color Android Development] arrjaytea:
Here's my question: does anyone have a JB build running now that would function well as a DD for:

- Light reading (flipboard)

- Email

- Facebook

These are literally the only things I'd like to have running on my NC, but man - since JB dropped, using this thing on ICS versus my GNEX is paaaaaaaainful.
[Nook Color Android Development] fattire:
It's not really ready for any of that yet. No wifi. I mean, not in 3.0 yet, and yo udon't want terrible .32. I wouldn't subject you to that.

found a typo in device.mk but still doesn't seem to work. wifi modules not loading properly. I rebuilt them but my nc is out of battery now so I can't test it. Damn $1 usb cables...
[Nook Color Android Development] arrjaytea:
Cheers for the earnest response and hard work. :)

Doing what I can to get comfortable compiling my own as well as with the SDK generally so maybe I can become a bit less useless around here.
[Nook Color Android Development] krylon360:
Still on my phone, but looking at our init, we aren't insmoding our modules. Have a look at the blaze_tablet. Also may have figured out the debug error. Ill try that out later.

http://git.omapzoom.org/?p=device/t...it;h=9b1d8786c6b284acf2b41ac28bcd0a30901d1412
[Nook Color Android Development] krylon360:
well. git decided to delete my patched omap3 dir, and for some reason I cant get fattire's diff to apply. so I did my own.

remove the entry you made in your local_manifest to pull from omapzoom omap3 dir

use this instead.

<remove-project name="CyanogenMod/android_hardware_ti_omap3" />

<project name="Krylon360/android_hardware_ti_omap3" path="hardware/ti/omap3" remote="gh" revision="jellybean" />
[Nook Color Android Development] fattire:
Use th e one with history.

Actually use this one as it has history:

https://github.com/fat-tire/android_hardware_ti_omap3

So your local_manifest.xml should look something like:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<remote name = "gh"

fetch="git://github.com/" />

<remove-project name="CyanogenMod/android_hardware_ti_omap3" />

<remove-project name="CyanogenMod/android_hardware_ti_wlan" />

<project name="fat-tire/android_hardware_ti_wlan" path="hardware/ti/wlan" remote="gh" revision="jellybean" />

<project name="fat-tire/android_device_bn_encore" path="device/bn/encore" remote="gh" revision="jellybean" />

<project name="fat-tire/android_hardware_ti_omap3" path="hardware/ti/omap3" remote="gh" revision="jellybean" />

<project name="keyodi/ti-omap-encore-kernel3" path="kernel/bn/encore" remote="gh" revision="encore-omap3-3" />

</manifest>

NOTICE: If you previously used a local_manifest.xml with "jellybean-3.0" in the device repo, you will now need to update it to plain ol' "jellybean". What was "jellybean" is now called "jellybean-2.6.32". Sorry for the confusion, but "jellybean" is the one we're working on, which is 3.0. Hopefully this will simplify things going forward. So if you suddenly get an error reposyncing, that's why. Just change "jellybean-3.0" to "jellybean" and re-repo sync.

Another NOTE: Added kernel 3.0 source, because thanks to a new fix from CM, you can now build it on-the-fly. So we will :)

UPDATE: We have wifi, sound and even some video working (see upcoming post from Krylon ;) )
[Nook Color Android Development] krylon360:
Wifi fixed!

YouTube HQ and Non-HD work perfect and sound is crisp.

[YOUTUBE]-AXCtlGe_Nk[/YOUTUBE]
[Nook Color Android Development] jewnersey:
Very cool! You guys are amazing. I look forward to testing a flashable build. Keep it up
[Nook Color Android Development] meteorrock:
Yes! Awesome job guies. SOOOOOOOOOOOOOOOOOOOO AWESOME LE :victory:
[Nook Color Android Development] halrulez:
Couple rusty nails does the trick hu? =P
[Nook Color Android Development] krylon360:
Haha yeah, had to threaten it with hep c. Lol. Nah basement flooded and found those in between the walls. Lol
[Nook Color Android Development] afzalarsalan:
Skip
[Nook Color Android Development] BobbyBest:
Yeah, have been following the thread, but somehow missed the point where 'we have hardware-acceleration!'. I did get some pages before that we need HA for YouTube HQ...
[Nook Color Android Development] fattymcdirty:
is there anything flashable yet with the latest changes included?

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Nook Color Android Development] mrapollinax:
You'd have to check the nightlies. I'm not sure if the changes being discussed right now have been pushed into the source for the build. Otherwise you could just go through the posts and add the branches noted and make your own build.
[Nook Color Android Development] eyeballer:
I'm going to make the request again, and it's been pretty well respected so far which has been great.. but.. please ONLY post in this thread if you have something development related to add.

I understand everyone is excited and looking forward to this, but it's really $%*#ing annoying to have to wade through non-development posts when you're trying to refer back to a useful post. This means, no asking for zips, no asking for ETAs and no asking if xyz is working. We're trying to keep this thread up to date with what's working and even how to add it to your own build, so read, learn and try to build if you're impatient.

There is a user thread in general here: http://xdaforums.com/showthread.php?t=1392769 - please discuss anything and everything over there.

//steps off soapbox

Thanks :)
[Nook Color Android Development] krylon360:
Take the external dir from the nook tablet kernel source from Kuzmo and drop it in our kernel source. Then it will compile. We need to push it.
[Nook Color Android Development] eyeballer:
That won't work. fattire and I were trying to debug it last night but for some reason our wifi module isn't build correctly. Right now the best thing is to comment out the inline module build so it'll use the prebuilt, which should give working wifi.
[Nook Color Android Development] Divine_Madcat:
You heard the man folks. I consider this request as offical as anything else, and from now on, any non dev work will be deleted without notice (consider this the notice)..
[Nook Color Android Development] fattire:
Yah i've got everythng in the build working but the modules aren't tested and so I want to make sure it's right... in the meantime just revert the last few commits so that it's 100% prebuilt (the effort is to get as much built from source as possible) and everything should work.

This is just until we can get everything else back up. Oh, keyodi is out for about a week btw. My time will be limited as well.
[Nook Color Android Development] krylon360:
K ill see what I can do about the modules. I've got a feeling its the tool chain.

Sounds like someone got their N7 :-p
[Nook Color Android Development] fattire:
Well I just fixed everything, you'll need to add this to your local_manifest.xml:

<remove-project name="CyanogenMod/android_hardware_ti_wlan" />

<project name="fat-tire/android_hardware_ti_wlan" path="hardware/ti/wlan" remote="gh" revision="jellybean" />

I didn't want to add this stuff to the device or the kernel as it adds 75M to the repo and it will be hard to dig out later if we want to remove it. This is largely based off the jellybean-dev version of the modules, which is newer and different than even what we were using, but still seems to work for me.

The device itself is now updated as well, and I'm going to update a few posts back with the same info.

So the build should now be working and both kernel and wifi modules are being build from source. If you have issues, let me know.
[Nook Color Android Development] lekofraggle:
Hey everyone. I am sorry if this muddies the waters. I have a build question.

I had gotten ics to build, but when trying to get Jellybean to build, I get either...

build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/encore/cm.mk]]: "device/*/encore/cm.mk" does not exist. Stop.
Device encore not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_bn_encore
CyanogenMod/android_device_bn_encore already exists
Syncing repository to retrieve project.
error: revision jellybean in CyanogenMod/android_device_bn_encore not found
Repository synced!

If I ./get-prebuilts after I sync my repo. Or, I get

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

If I ./get-prebuilts before syncing my repo.

Any advice would be helpful. If you are all too busy, I will go back to the drawing board.

I am a few steps behind, but do want to try to help with development.

Thank you for all of the work in continuing to keep this beast alive.

~Leko

P.S. If this constitutes as too much noise, I will delete it.
[Nook Color Android Development] fattire:
Did you add the correct local_manifest.xml to .repo?

Also- you are on the jellybean branch of cm, right?

you sure you ran ./get-prebuilts from vendor/cm/whateveritwas..? that looks as though ./get-prebuilts wasn't run.

Absolutely not. This is exactly what this forum thread is for.
[Nook Color Android Development] lekofraggle:
Fattire,

Thank you for the support.

I think I am on the Jellybean branch.

repo init -u git://github.com/CyanogenMod/android.git -b jellybean

And, I did copy your manifest changes.

I copied them again just in case there was an extra space in mine.

I am running on OSX snow leopard and had a lot of trouble with gcc because Jellybean does not compile for me anyway on 4.2.

I found a way to install gcc 4.8

I wonder if I broke something troubleshooting that.

Thanks again.

~Leko

Edit: I tried to sync again after making sure I am using your updated manifest.

This was the error. Maybe I am not syncing jellybean.

error: revision jellybean in CyanogenMod/android_device_bn_encore not found

One more edit:

though I have many entries under the lunch menu,

if I just type brunch, this is all I get.

Breakfast menu... pick a combo:

1. full-eng

2. cm_grouper-userdebug

3. cm_maguro-userdebug

4. cm_toro-userdebug

5. cm_toroplus-userdebug

Maybe my local.manifest is not loading for some reason. prehaps I need to start from scratch.
[Nook Color Android Development] eyeballer:
Definitely sounds like you don't have the local_manifest.xml in the right place it's not being picked up. It should be in the .repo folder in the source dir.

Also see this http://source.android.com/source/initializing.html for some mac osx specifics.