yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] unknown_world:
YES
[Nook Color Android Development] newellj79:
Can somebody refresh my memory on how to pull the proprietary files without using adb on a currently running rom?
[Nook Color Android Development] bowguy:
Newellj79:

Using the latest manifest posted by eyeballer will download them when you sync. No need to connect your nook and use adb.
[Nook Color Android Development] newellj79:
Thank you much. I'm building now. Here's hoping my touchscreen works... :)
[Nook Color Android Development] alienbiker99:
hrm not really sure how to set the build osx experimental in that post. any hints for that or manually adding modules? searched around and didnt find much
[Nook Color Android Development] xdp:
Is there a permanent location for the local_manifest file? The pastebin linked posted on the 11th doesn't seem to be working.

Edit: Nevermind, it's back.
[Nook Color Android Development] eyeballer:
Yeah looks like pastebin was down for a bit. I've mirrored here too: http://tinyw.in/pQYz

But quite simply it's the device from fattire's git, and the kernel from keyodi's. This weekend we will be merging things over to nookiedevs to consolidate things and make it easier for everyone to keep up to date.
[Nook Color Android Development] xdp:
Thanks!

So I installed Ubuntu 12.04 64-bit into a VM, download and ran andbot, ran init, then pasted the local_manifest into .repo. I'm assuming I was supposed to skip the 'andbot manifest' line. I ran 'andbot sync' and it finished without errors. I then skipped the proprietary files steps since it was mentioned that the new manifest pulls those. Then I ran 'andbot brunch encore'. I got the "dependencies file not found bailing out" message, it continued for a bit, and then stopped with "make: *** No rule to make target `vendor/cm/proprietary/Term.apk', needed by `/home/andbot/android/system/out/target/product/encore/system/app/Term.apk'. Stop.

make: *** Waiting for unfinished jobs....". I searched the thread for this problem and found various responses about missing vendor files, resyncing, etc. Did I miss a step?
[Nook Color Android Development] newellj79:
Hot damn! It built just fine and everything appears to be in working order. Thanks guys!
[Nook Color Android Development] sellers86:
cd ~/android/system/vendor/cm

get-prebuilts

That'll fix your error
[Nook Color Android Development] lekofraggle:
So I did switch back to the 3.x kernel. Thank you all, it is truly amazing.

I found an odd bug. Mp3s cannot be played. I noticed it first in the overdrive app. Then I realized the only sounds that could be played are the built in ones.

The log mentions a missing reference to media player and sure enough, even after adding player pro, play music and others, no mp3s play.

All the players crash.

Thanks again.

~Leko

P.S. I am using the newest manifest.

Sent from my NookColor using Xparent Cyan Tapatalk 2
[Nook Color Android Development] eyeballer:
Thanks.

Fixed: https://github.com/fat-tire/android_device_bn_encore/commit/077e5b4296507f0be544843b6e0ffbc2a736e78c
[Nook Color Android Development] siobhter:
That boot animation is trippy....
[Nook Color Android Development] votinh:
Homer,

2 questions for you.

1. Between step 4 and 5, I assume after creating the uSD card using verygreen's instruction, you meant plug the uSD into the NC, boot into whatever on emmc then reboot as step 5, am I right?

2. Can you make sure that we can drag both ROM and GApp in the boot at the same time? Using CM7, sometime, we have to do ROM first then repeat the process to install GApp later.

Thanks
[Nook Color Android Development] swaaye:
It is. Has a sort of '90s demoscene feel to it. Love it. Just needs some background mod music and it'll be perfect.
[Nook Color Android Development] alton987:
Thanks this worked
[Nook Color Android Development] votinh:
A question for all.

Using CwM or verygreen, the uSD's boot partition is about 115MB after creating.

The ROM itself is about 100MB, the new GApp for ics is about 65MB, how did you guy fit both files on the uSD??? I have to do one after another.
[Nook Color Android Development] MrPib:
I can't fit both, so I do one and then another (like you). I suppose it might be possible to resize the partitions using something like Easeus Partition Master, but it doesn't seem worth the effort to me.

EMMC installs have lots of room, and you can put both on there.
[Nook Color Android Development] votinh:
Thanks for confirming that, Pib.

"EMMC installs have lots of room, and you can put both on there."

You did it using ROM Manager? 'cuz using CwM uSD, it's the same issue.
[Nook Color Android Development] michaeljr10wv:
Install ICS first...then after it's installed...put gapps on the sd card...boot into ICS, and open rom manager. Select reboot into recovery...it will find the gapps zip and install it...

Took two days to figure it out...
[Nook Color Android Development] nguyen2011:
For some reason, mine getting error can't unzip gapps-ics-20111125-2.zip. Tried a couple time redownload, recopy, reboot to recovery but no luck :(
[Nook Color Android Development] Midnitte:
Try a different download of it, one of the ones linked earlier gave me the same error and constantly gave me a "insert disk" error every time i touched it on my desktop.

If that doesnt work, try renaming from gapps-ics-... to gapps-gb-ics-...

Can anyone flash CWM recovery successfully? I only seem to get the terminal-looking recovery from verygreen's sd agnostic, instead of the normal clockwork mod recovery
[Nook Color Android Development] MrPib:
It's been a while, but I'm *pretty* sure that I was able to copy both the CM7 image and Gapps onto a fresh card. But I switched to ROM Manager right after I got it up and running.

Edit: I recall writing an image to the card, and then expanding the last partition. The image probably had a roomier boot partition.
[Nook Color Android Development] Homer_S_xda:
I should have said booted the NC in recovery using the boot menu directly. I edited my original post.

Flashing both worked for me, YMMV.

Homer

---------- Post added at 12:29 AM ---------- Previous post was at 12:25 AM ----------

I have taken to doubling the size of the boot partition. In Windows, run your favorite partitioning software (I use Easeus Partition Master Home Edition) after burning Verygreen's 1.3 image but before letting it create the other three partitions.

Homer
[Nook Color Android Development] nukeruss:
Gmail works fine after I did a fresh install (factory reset and reinstalled ics). I used the 20111128 gapps and they work great. The only way that I got YouTube to work was to uninstall the ics version and then install the gb version. No sound though.
[Nook Color Android Development] rootfan:
Everyone, this is a must do. I don't know if any of you have figured out about this yet, but here it goes. go to the settings menu. go to about tablet. rapidly tap the android 4.0.1 sign until the android ice cream guy comes up. Now press on the screen with one finger. The android ice cream guy will zoom in, and it will eventualy play and ice cream droid animation:D
[Nook Color Android Development] jalexishg:
LOL. Been there done that, you can try that with GB as well.
[Nook Color Android Development] gotrubberducky:
There is also a way under settings>display>android dreams to set that (nyandroid) and rocket launcher as a screen saver. If you so wish to kill your battery.
[Nook Color Android Development] newellj79:
Seems like people are having a whole mess of problems I'm not. Full wipe, flash rom, flash gapps I posted a few pages back, and I have no problems. No fcs, no bypassing setup, and all gapps are working. I would certainly do a full wipe. Use TB to restore all your apps.
[Nook Color Android Development] msaraiva:
I second that. With the gapss i've linked a few pages back, everything is fine.
[Nook Color Android Development] votinh:
Crystal clear.

Thanks Homer, Pib
[Nook Color Android Development] michaeljr10wv:
Rename the file: gapps-gb-20111125-2.zip, after I did that it works...

Mike
[Nook Color Android Development] xdp:
Thanks! That worked and then the build was successful, finished in 100 minutes flat, not too bad. Flashed it and seems to be working well, I'm really impressed, awesome to see these guys giving this attention to the Nook. It's nice seeing the new UI on this device, it's kinda-sorta like having the Nexus 7 right here!

I searched the thread but couldn't tell for certain...is OpenGL rendering not being built-in with the manifest posted by eyeballer on the 11th? It's reporting my kernel as 3.0.8+, but I see there isn't a gradient in the Settings menu, and Chrome doesn't crash but all pages just display white, so I'm guessing it's not. I remember the OpenGL CM9 builds never got quite as smooth as non-OpenGL but I wasn't sure if that situation had improved with CM10. Are people turning that on in their builds with decent success?

Finally I noticed that Google Photos is missing in account sync, the only things there are Browser, Calendar, Contacts, and Gmail. This is with latest gapps from goo.im. Are others seeing this?
[Nook Color Android Development] xdp:
Thanks for the response. Is this an area that's still seeing progress or might it be as good as we'll ever see it on the Nook? Either way what we already have is extremely usable!
[Nook Color Android Development] jamesh0317:
Build time

I have successfully built JB about 4 times. No problems with the build, and the ROM runs just as it is supposed to. However, the build time seems really long. I figure that (1) it just is long, (2) It is long because I am building in a virtual machine (VMWare/Ubuntu 10.04), or (3) I am doing something wrong.

Here is how I build-

ccache -M 50G
export USE_CCACHE=1
cd ~/android/system
repo sync
source build/envsetup.sh
make clean
brunch encore

Here is the time that it takes:

real	458m41.484s

user	129m38.900s

sys	51m41.650s

Anything I should be doing differently?
[Nook Color Android Development] eyeballer:
Really just depends on your hardware..
[Nook Color Android Development] lekofraggle:
Xdp,

There is still development working on cm10 and hwa, but hwa is taking a back seat. I think it is pretty close to as good as we will get. I have been using it as a daily all weekend and there really are only a few hiccups.

On the plus side, if you manually install flash, it works with the hwa builds.

Jamesh,

I think you are doing things right. You are in the same boat as me, and I am working with even longer numbers. The issue is vm.

If you can allocate more resources to the vm, it will build faster.

But, too many and your computer will not work.

Good luck.

~Leko

Sent from my NookColor using Xparent Cyan Tapatalk 2
[Nook Color Android Development] lekofraggle:
joeuser846,

I am using flash version...

11.1.115.11

It seems to work. I just discovered it today, and I probably installed it on ics a while ago.

~Leko
[Nook Color Android Development] xdp:
What hardware are you giving the VM? I'm using Ubuntu 12.04 in VMware, I gave it 2 cores of my Core i5 and 8 GB of RAM and the build finished in 100 minutes. I believe the build time is affected drastically by the amount of available memory.

Thank you. I decided to try another build with OpenGL rendering enabled. I did 'andbot sync -j16', then uncommented that line you mentioned. However when doing 'andbot brunch encore', my build keeps dying very quickly, the first time after 7 minutes, and now after only 1 1/2 minutes. I don't see any particular error, it just stops. One time the last lines I saw were:

make: *** Waiting for unfinished jobs....
Note: Some input files use or override a deprecated API.

And another time it was:

Warning: you may need to install module-init-tools
See http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt
make[1]: Leaving directory `/home/andbot/android/system/kernel/bn/encore'
mdpath=`find /home/andbot/android/system/out/target/product/encore/system/lib/modules -type f -name modules.order`; if [ "$mdpath" != "" ];then mpath=`dirname $mdpath`; ko=`find $mpath/kernel -type f -name *.ko`; for i in $ko; do mv $i /home/andbot/android/system/out/target/product/encore/system/lib/modules/; done; fi
mdpath=`find /home/andbot/android/system/out/target/product/encore/system/lib/modules -type f -name modules.order`; if [ "$mdpath" != "" ];then mpath=`dirname $mdpath`; rm -rf $mpath; fi

I did one build last night that was successful. Is there something else that needs done before subsequent builds? Or maybe bad code was submitted?
[Nook Color Android Development] Divine_Madcat:
I hate saying it, but again, i have cleaned the thread. Please keep this thread on topic with NOTHING but dev related posts. While the guys appreciate thanks, this is not the place to put it. Want to say thanks? Hit the thanks button. :)
[Nook Color Android Development] newellj79:
I'm thumbing my way thru git trying to figure out how to get the 1200mhz option back. As I look thru I see the Jellybean branch and the Jellybean 2.6 branch. I never looked while I had it installed to see what kernel was currently being used so I'm not sure which branch I should be looking at. I'd appreciate any help. I know it's over my head but it's fun to try.

edit... i didn't mean to quote madcat. sorry...
[Nook Color Android Development] meteorrock:
Look further down in the gingerbread branches. That OC kernel was developed by <dalingrin>. He should have his own repo for that kernel if you look. You will have to rework that kernel to implement it on JB. It was removed for development. His link on the git for that is here. https://github.com/dalingrin/nook_kernel

His page here on XDA is here. http://xdaforums.com/showthread.php?t=925451

That would be a good project for you. I wished I had thought of that. If you want you could take a look at it. Been super busy with school projects. Let us know how your progress is and check with the guys too up in IRC #nook color at freenode.net for confirmation. I got in trouble last time for starting projects without a go ahead, I guess there is a developers protocol they stick to, and at my age I am not sure how it works.

~~~~~~~~~~~

Right now I am not understanding why they do not want other developers to start an AOKP of this project on the nook color for the JB builds, all I can assume it is because people are too lazy to debug their builds, but that does not make too much sense either. I thought it was expected to debug your builds but IDK.

~~~~~~~~~~~~~~~

Update: Just researched this for you <newellj79> , its called Wirth's Law. Better look into debugging your build first with the team and look into developing that kernel after talking with the team. Check out that link here. I don't want my builds to get sloppy. That is probably the reason we are not releasing AOKP for JB just yet. http://en.wikipedia.org/wiki/Wirth's_law

So check out my thread here in cyanogenMod for learning how to debug our builds first, if you do not know how. http://forum.cyanogenmod.com/topic/50994-follow-along-with-me-trying-to-learn-how-to-code/
[Nook Color Android Development] jh1521:
Damn. I just spent about 5h setting up the SDK to compile JB for the first time, only to be greeted by this:

"prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: cannot execute binary file"

And then I realized that I spent all that time for nothing because I chose the wrong host system: 32-bit Xubuntu. :(

I just found out JB won't build on a 32-bit system.

Also, another question before I waste another few hours: do you absolutely need to use the Sun/Oracle Java, or is openJDK good enough? The build script complains, but I didn't get to find out if it really matters or not because of the error above.
[Nook Color Android Development] eyeballer:
It's a very simple revert if you look at the kernel commit history.

However, as mentioned previously, for now we'd prefer people stick to 1ghz and avoid OC just so we can bug test without OC being a factor. The 3.0 kernel is still in development and OC should only be used once we're confident it's stable.
[Nook Color Android Development] xdp:
Unfortunately I am SODing almost every time I turn the screen off today. Even with WiFi set to not stay on. How are others doing with SOD?
[Nook Color Android Development] mateorod:
Unless I have the USB plugged in, my Nook SODs at every sleep. I don't have a wifi chip, though, and shouldn't count as a data point. Does usb charging stop the SOD for you? (Edit: oops. I guess it would since AFAIK charging stops sleep. Whoops. Carry on...)
[Nook Color Android Development] thorin:
Haven't been able to build successfully for a couple of days now. Keeps failing in the overlay libs.

In file included from hardware/ti/omap3/liboverlay/overlay.cpp:20:0:
hardware/ti/omap3/liboverlay/overlay.h:56:35: error: 'HAL_PIXEL_FORMAT_YCbCr_420_SP' was not declared in this scope
hardware/ti/omap3/liboverlay/overlay.h:57:35: error: 'HAL_PIXEL_FORMAT_CbYCrY_420_I' was not declared in this scope
hardware/ti/omap3/liboverlay/overlay.h:58:35: error: 'HAL_PIXEL_FORMAT_YCbCr_420_I' was not declared in this scope
hardware/ti/omap3/liboverlay/overlay.h:60:42: error: 'HAL_PIXEL_FORMAT_YCbCr_420_SP_SEQ_TB' was not declared in this scope
target thumb C: overlay.omap3 <= hardware/ti/omap3/liboverlay/v4l2_utils.c
make: *** [/home/thanson/android/system/out/target/product/encore/obj/SHARED_LIBRARIES/overlay.omap3_intermediates/overlay.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from hardware/ti/omap3/liboverlay/v4l2_utils.c:28:0:
hardware/ti/omap3/liboverlay/overlay.h:56:35: error: 'HAL_PIXEL_FORMAT_YCbCr_420_SP' undeclared here (not in a function)
hardware/ti/omap3/liboverlay/overlay.h:57:35: error: 'HAL_PIXEL_FORMAT_CbYCrY_420_I' undeclared here (not in a function)
hardware/ti/omap3/liboverlay/overlay.h:58:35: error: 'HAL_PIXEL_FORMAT_YCbCr_420_I' undeclared here (not in a function)
hardware/ti/omap3/liboverlay/overlay.h:60:42: error: 'HAL_PIXEL_FORMAT_YCbCr_420_SP_SEQ_TB' undeclared here (not in a function)
make: *** [/home/thanson/android/system/out/target/product/encore/obj/SHARED_LIBRARIES/overlay.omap3_intermediates/v4l2_utils.o] Error 1

Any ideas? This is from a make clobber/repo sync/brunch encore

Thanks,

Thorin
[Nook Color Android Development] xdp:
Actually, no, I have it charging right now and just went to turn it on and it was dead. It was also dead this morning when I woke up. So it's still getting SODs charging on AC.

The other random problem I'm seeing is that it's charging incredibly slowly, plugged it in around 10% last night and this morning after 7 hours it was still less than 3/4 full.
[Nook Color Android Development] grayfoxmg1:
Only thing I can think of is that your Nook thinks it is charging off usb.

---------- Post added at 12:04 PM ---------- Previous post was at 12:04 PM ----------

But even still I would be charged after 7 hours.
[Nook Color Android Development] sellers86:
Looks like its because we are back to using CMs to/omap3. I'm at school and I haven't built with the new manifest so I wouldn't have the first clue on how to fix it right now.
[Nook Color Android Development] jh1521:
Okay, tried again on a 64-bit Ubuntu 12.04 installation. Using the Java6b32 from Oracle. After setting everything up, running

repo sync

source build/envsetup.sh

brunch encore

I end up with:

(edit) Did some reading, trying again after using vendor/cm/get-prebuilts

Still the question about Java remains. The only supported one is the Java 6 SDK from Oracle, but my understanding is that it's going to be EOL in 1 month, and (knowing Oracle) the downloads may disappear... then what? Will we become unable to setup a build environment anymore?
[Nook Color Android Development] eyeballer:
rm -rf hardware/ti/omap3/ then re-sync.

Also for those getting SOD, have you done a make clean/clobber?
[Nook Color Android Development] xdp:
In my case, I'm using the first build I ever did (pulled on 10/13), so all the files should be right. However, I since backed it up, flashed a new build with OpenGL enabled, and then restored my backup all without wiping data. Could that have caused a problem?
[Nook Color Android Development] krylon360:
open jdk works just fine, which, is what should have been installed when you set up your 12.4 build env
[Nook Color Android Development] jh1521:
Yeah, when I got to set my whole environment the second time I went straight for Oracle, didn't try openJDK anymore.

I got CM10 built, and it works albeit not as responsive as I would like (OpenGL enabled). However Netflix still doesn't work, and that remains a deal breaker for me.
[Nook Color Android Development] shane269:
How do I change the name of the output file to include a build time or other info?
[Nook Color Android Development] bitstra:
Hi all,

can somebody explain, how to insert USB host/OTG into the 3.0.8+ kernel? Or where to start with that?

thanx

bitstra
[Nook Color Android Development] unknown_world:
you don't need to backup anything.

you can reset the repo to it's orginal state

ex
[Nook Color Android Development] xdp:
I don't mean backup any files, I mean a backup on the Nook through recovery. I'm wondering if the backup/flash new build/restore process messed anything up.

My Nook is exhibiting very strange behavior now. Last night I plugged it in before bed. The screen didn't turn on so I knew it had SODed. I figured no point in turning it on now so I let it go. This morning I look at it and the screen is on but all black, you can just see the backlight. So I press the power button, screen goes out, then press and hold the power button and it turns on from scratch. Once it boots I see that it didn't charge at all overnight, same % as when I plugged it in, but it says Charging now.

It should be able to charge after a SOD right? Has anyone seen a charge after a SOD make the screen turn on but just to black like that? Might a brand new build fix these issues and would I have to wipe data before flashing it?

Edit: And another SOD just a few minutes later. Seem to happen especially often while charging.
[Nook Color Android Development] bowguy:
Try a clean install without restoring. I haven't had any of these issues for a few weeks. I am testing on a formatted SD card with my builds and use titanium backup to restore only my apps and apps data, not system.
[Nook Color Android Development] xdp:
Thanks, I'll try that.

This morning it started at 49%, and now at 1:45 it's at 96%, on AC. That seems as slow or slower than USB computer charging should be. Maybe my charger is dying.
[Nook Color Android Development] eyeballer:
What does it say in settings-battery? Is it showing as charging as AC? If it's not, unplug then re-plug.
[Nook Color Android Development] jh1521:
Moving my comments from the alpha1 thread to here because I'm experimenting with builds past the CM10 alpha1 at this point.

New build of mine from 10/20, without OpenGL this time. I noticed per the commit log that there has been an update to the PowerHAL. I will see if I still get SoD under the new build. I only got it once before, as I mentioned in the other thread, when the NC was allowed to sleep for many hours with an almost depleted battery.

Testing new signature with NC details too.

[edit] Without OpenGL the NC is somewhat more responsive, much of the lag is absent. Surprisingly, flash works quite well even w/o OGL. And it works in the default browser too, not just firefox. For instance the ads at the top of this page show up correctly. Netflix, as expected, does not work.

[Edit2] I do see quite a bit of screen tearing when scrolling quickly in landscape mode. I don't remember seeing much of that, if any, while running the previous build with OGL.

[edit3] I did have one instance of unexpected reboot. I had played X-COM2 in Dosbox Turbo for about an hour, exited the game, and exited Dosbox. Instead of going back to the tablet UI, it rebooted. I have been using Dosbox Turbo for some time and it never did that before.