yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] fjevel:
If anyone else has problems getting the Nook to show up under <adb devices>, I found an easy workaround here:

http://anexinet.com/blog/index.php/...-bridge-over-usb-to-a-nook-color-under-linux/

I run latest nightly CM on the Nook and Ubuntu x64 11.10 on the computer.

-KJ

---------- Post added at 04:28 PM ---------- Previous post was at 04:24 PM ----------

Looks like you have lost network connectivity on you VM there... Check with a terminal and try to ping stuff / nslookup?

Here's the content of my local_manifest.xml:

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

<!-- note: no longer need to replace CM9 Trebuchet launcher with AOSP's Launcher 2 -->

<remote name = "gh"
fetch="git://github.com/" />

<project path="device/bn/encore"
name="fat-tire/android_device_bn_encore"
remote="gh"
revision="ics"/>
<remove-project name="CyanogenMod/android_prebuilt"/>
<project path="prebuilt" name="platform/prebuilt"
remote="aosp" revision="refs/tags/android-4.0.3_r1"/>
</manifest>

It works for me.

-KJ
[Nook Color Android Development] 911jason:
I posted that message from inside the VM and had no problem with internet connectivity in the browser. Could it still be the problem?
[Nook Color Android Development] fjevel:
It could if you've lost your DNS and the IP of the forums has been cached, but it sounds unlikely.

What do you get if you nslookup the address?

jevel@kjlN53SVubuntu:~$ nslookup github.com
Server:	192.168.10.1
Address:	192.168.10.1#53

Non-authoritative answer:
Name:	github.com
Address: 207.97.227.239

Here's what I get.

-KJ
[Nook Color Android Development] 911jason:
Same as you.

jason@jason-VirtualBox:~$ nslookup github.com
Server:	192.168.0.1
Address:	192.168.0.1#53

Non-authoritative answer:
Name:	github.com
Address: 207.97.227.239
[Nook Color Android Development] fjevel:
From your previous post:

github.com[0: 208.67.216.145]: errno=Connection timed out/s

Found a hint here:

http://fiji.sc/wiki/index.php/Downloading_and_Building_Fiji_From_Source

Seems like you might have firewall trouble.

-KJ
[Nook Color Android Development] anapospastos:
I used your local_manifest file and it does sync the code. Thanks.
[Nook Color Android Development] fjevel:
No problems. Alle credit goes out to fattire. It's from his document and his post in this thread.

-KJ
[Nook Color Android Development] 911jason:
Except that I had a 100% sync 2 nights ago behind the same router on the same setup. I had just screwed up and sync'd from my home folder instead of from the android/system folder. I would be more suspicious of my connection if about 10 other people hadn't posted in the past 48 hours that they were having the same error.

No big deal, I've given up for now... just worked all night so I'm going to go to bed and maybe try again later this evening when I get up.
[Nook Color Android Development] roger_n:
Jason when you wake up try the work-around here it fixed my sync issue. http://xdaforums.com/showpost.php?p=20875598&postcount=1050

Thanks Roger:cool:
[Nook Color Android Development] ZenoGia:
I am having real issues with the touch screen. I am getting no response whatsoever. I have even flashed back to stock 1.3 and it continues to be unresponsive. CM7 is the ONLY firmware on emmc that works fully, touch and all, but my thing is why would I want to look at the same OS that is on my phone, on my tablet? I have tired countless tries for the past 3 days but to no avail. I have even tried HC preview 3 and 4. I really want to give the ICS a go.

I do have the latest CWR 3.2.0.1

any Ideas

oh and I am no noob so yes i formatted everything e.g /data /system /boot, Dalvik. I have tried everything under the sun.

It is a new nook color that came with 1.3 pre-installed. Could this be the issue?
[Nook Color Android Development] redDEADresolve:
This is a development thread not a help thread. Please post in the correct thread.
[Nook Color Android Development] yujikaido79:
I tried both of these and still get connection errors and ends with fatal error

Fetching projects: 76% (186/244) github.com[0: 207.97.227.239]: errno=Connection timed out

fatal: unable to connect a socket (Connection timed out)

fatal: Unable to look up github.com (port 9418) (Name or service not known)

fatal: Unable to look up github.com (port 9418) (Name or service not known)

fatal: Unable to look up github.com (port 9418) (Name or service not known)
[Nook Color Android Development] mgs526:
By that logic, all the talk about compiling from source would need to go to another thread.
[Nook Color Android Development] roger_n:
ZenoGia, If your nook boots to CM7 you can try to install the update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs.zip on page 1 of this thread, that will give you an early build of ICS. You can also search or post your questions at one of the links below. If you like the sneek peek you can try building the an updated ROM yourself. Everyone on this thread has been very helpful and are a bunch good people, keep in mind some of us can get grumpy at times especially around the Holiday. ;) So don't get discourage I'm sure you'll eventually get your Nook up and running the way you want it.

Nook Color Q&A Forum: http://xdaforums.com/forumdisplay.php?f=1131

or

Nook Color General Forum: http://xdaforums.com/forumdisplay.php?f=862

One more thing for future reference never format "boot".

Roger:cool:
[Nook Color Android Development] yujikaido79:
I used the -f attribute to force repo sync to finish and it finished. Don't know if it will work but its building as I type this.

edit: Well I tired but the building ended within 10 mins with this

make: *** No rule to make target `vendor/cm/proprietary/lib/armeabi/libjackpal-androidterm3.so', needed by `out/target/product/encore/system/lib/libjackpal-androidterm3.so'. Stop.

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

guess I will have to wait..... until I can sync without any problems
[Nook Color Android Development] newellj79:
Did u run ./ get-prebuilts from /vendor/cm? That might take care of that.
[Nook Color Android Development] oppy:
I don't know if it'll make any difference, but I edited both manifest.xml and local_manifest.xml (the custom one from fattire) to include the git changes and I was able to complete a build for the first time in the last couple days.
[Nook Color Android Development] mmark66:
Zip size / build script

Hi,

after playing around with Fattires zip I tried to build my own zip. First I used Inportbs Makefile (see: http://forum.cyanogenmod.com/topic/...erhaps-debian/page__view__findpost__p__278391), but somehow I always got an error about modifying the API, so I stopped using the Makefile and followed Fattires google doc very closely (thanks so much for it!).

I am building on a freshly installed Ubuntu 11.10 64bit. After some troubles with adb not finding my device I was able to build my own zip, but after putting it on a SD card (Sandisk Class 4 16GB) using verygreens generic installer image it does not but run. :( After booting, the green cyanogen label is shown and then the screen goes dark, blinks after 10 sec or so and then the label is shown again. This goes on until the NC is powered off.

I noticed that the size of my zip file is quite a bit bigger than fattires (116270159 vs. 103620681). Any idea why this is the case? How big is your custom cm9 zip?

Due to the increased size I had to modify verygreens image, which originally has not enough space for my zip. I increased the size of the partition to 240 MB and confirmed with fattire zip that my modified image works (this way you can install cm9 and gapps in one go).

If someone is interested in the bigger sd card install image, you can get it here: http://www.mediafire.com/?slpytyvn591a7b7 (md5: 698d10b37d642acddf3a32ea660c1e44)

Also, I put all the steps required to build the image in a bash script, which you could get here: http://pastebin.com/8thvWj8Y

Please let me know if you find a point where I did not follow Fattires directions...

The script uses the fix for the broken/overloaded github posted above, but I got exactly the same boot loop when I tried this a couple of days ago with the original

Any idea why my zip does not boot properly? I am hesitating to flash it to the emmc before I cannot confirm that it runs from a SD card...

For the record, repo sync took around 55 min and mka bacon 34 min on my i5 2500k (@4GHz, 8 GB)

Mark
[Nook Color Android Development] Razor1973:
Great. I'm going to try that as soon as I get home today.
[Nook Color Android Development] fjevel:
Just built a successful KANG using the document from fattire together with bits and pieces from this thread and google.

I must say it was a really nice learning experience. A big thanks to dalingrin and fattire!

A few things I bumped into on Ubuntu 11.10 x64 that took a little sorting out:

Android does not support JDK v. 7 yet, you have to use JDK 6. I didn't see this anywhere in the documentation, and installed v. 7 at first.

After sorting that I really had problems getting the nook to register under adb. It took a little googling with trial and error before I found this:

http://anexinet.com/blog/index.php/...-bridge-over-usb-to-a-nook-color-under-linux/

Then I had a few "remote end hung up" errors while syncing the repo. This post took care of that. (First part that is...)

At point 4 in the draft, I messed up and tried to run the command under ~/android/system/vold/, which gave an error message which sent me in the totally wrong direction for a few hours until I read the draft closely again... ;)

I also accidentially removed the space in the command under point 4 between android_system_vold and refs/. It is supposed to be there apparently. Taking it out gives trouble... ;)

That should sum it up nicely. Hope it helps others in my situation.

The KANG is really good, so keep up trying if you hit problems. Someone probably has had the same problems and are able to help you!

-KJ
[Nook Color Android Development] yujikaido79:
thanks I think i must of missed that part, been building so far so good.
[Nook Color Android Development] MrColdbird:
Building worked fine. Nice prototype but the missing sound is a deal breaker still.

I'm positively surprised though.
[Nook Color Android Development] yujikaido79:
How long did it take for you to build yours I am almost going on 4 hours.. building inside a VM. I think I need a faster computer though .
[Nook Color Android Development] Homer_S_xda:
Best I can say is someone mentioned flashing fattire's sample zip and then immediately flash your build. It seems to work for me as well. There must be a file or setting that gets put in from fattire's zip that does not get overwritten (and also does not exist in) the current build. I think typically clockwork overwrites /system and /data but I think in Verygreen's 1.3 modified version it does not, since it is meant to be a updating mechanism.

Homer
[Nook Color Android Development] fjevel:
Built mine on my laptop with a quad core i7 2 GHz and it took about 45ish minutes I believe. Didn't time it, so might have been a little more or less...

Was surprised to see that it never used more than 2.9 GB of memory, though. Was expecting it to gobble as much as it could on a 64 bit system.

-KJ
[Nook Color Android Development] MrColdbird:
It took me about 40 mins building on my 3.3 ghz i5 2500k.

Did it in a 4gb Ubuntu VM.
[Nook Color Android Development] anapospastos:
It is for sure amazing to run ics on my nook and especially when Im building it myself. Thank you so much devs :).

I noticed that If I make a clean installation, without any user data, the initial setup dialog keeps crashing so it's not possible to continue into ics.
[Nook Color Android Development] MrColdbird:
Just use the gapps without initializer. Then use gmail or some other google app to associate a google account with ics.
[Nook Color Android Development] anapospastos:
What do you mean without initializer?

A serious problem I'm facing is that I can't restore to my previous setup of my nook. I made several times nandroid restore but every time I boot into 2.3.7 my apps do not exist. I tried to flash the Cm 7.1.0 zip and then to "advance restore" only my data img via the cwm but still the same result. Is anyone who faces something similar?

edit: it seems that the backup is corrupted
[Nook Color Android Development] danba:
I think the USB Audio Driver for ALSA audio.o is missing in the current stock kernel of Android 4.0.

Audio.o is present in the modded kernel of the Nook tablet which allows FiiO E7 & Nook to interoperate:

https://github.com/dalingrin/nook_kernel/tree/encore-32/sound/usb

http://xdaforums.com/showthread.php?t=1105497

http://xdaforums.com/showpost.php?p=16229673&postcount=587

Audio.o is not present in the 4.0 kernel:

https://bitbucket.org/paulobrien/android_kernel_galaxynexus/src/bc4f9b72a51d/sound/usb

“USB Audio Support

USB audio systems such as speakers normally comply with the USB audio class specification. If your audio device does not comply with the specification, it will not work with Linux at this time.

You need to turn on the Sound card support kernel option, which is in the Sound section. You will then be able to turn on the USB Audio support option in the normal USB section.

If you elected to use modules, you need to load the module called audio.o.”

http://www.linux-usb.org/USB-guide/x319.html
[Nook Color Android Development] smiley4017:
Can you please through the people who has been trying to get this to work a bone and update the preview download. No matter what I do I can't get this to work, and it feels like I'm being punished for being stupid. Thank you all for all the help you have provided in this thread, and I'm going to keep trying.
[Nook Color Android Development] inportb:
There was some interest in a prebuilt VM with a complete build system, so all you had to do was sync and build. Here's something similar: a chroot environment that comes with all the tools, which you could use on a fresh installation of pretty much any modern Linux distro. I tested this using a netbook with a 1.6GHz Intel Atom processor and a server with a 4*3.3GHz Intel Core i5 processor, both running some kind of Ubuntu, ia32 and amd64. I hope this helps those who have not yet been successful.

Download: http://dev-host.org/users/inportb/683/andbot (andbot.run)

Instructions: https://github.com/jyio/andbot

This is not suitable for use directly on Windows or Mac OS. If you don't use Linux, please set this up on a virtual machine with Linux. For help, post/PM here or ping Pinako on Freenode. Enjoy!

Also, I took gapps-ics-4.0.3-v2.zip and ripped out a lot of unnecessary stuff. I usually install gapps-ics-4.0.3-small.zip -- but there's also gapps-ics-4.0.3-noinit.zip if you don't want OneTimeInitializer.apk in there.

/update:

If you downloaded AndBot before Jan. 8th, 2012, you need an upgrade :D

Simply start a fresh AndBot session and run, within AndBot:

curl http://dl.dropbox.com/u/1213413/cm9/andbot-upgrade.sh | sudo sh

Future updates should be easier, since AndBot now uses the Debian package management system.
[Nook Color Android Development] wakeboarder8156:
I typed brunch encore and the command executes but it takes 5 minutes and ends without errors. Do I need to run some other command that's not on the walk-thru?
[Nook Color Android Development] bdcrim:
Thanks for this. Is it ran from the home folder?
[Nook Color Android Development] inportb:
Run it in any folder, but home's a good place. When it extracts, it should make a new folder inside named andbotfs. Make sure you have some 25GB free in there when you're ready to work. Or you could move andbotfs to a bigger partition.
[Nook Color Android Development] yujikaido79:
Yeah I agree it would be nice.. I thought my would build successfully but after 8 hours of building in virtual box with 2gb of ram and on amd phenon X4 2.2 I have realized how slow my pc is. Also it ended with an error and got a zip that wouldn't install. Perhaps I will try building again when I update my system.
[Nook Color Android Development] bdcrim:
Check your PM Inbox if you dont mind. Thanks.
[Nook Color Android Development] mmark66:
Thanks a lot!!!

Finally I am able to use my one build from a SD card. So if you have a problem getting your zip to boot from a SD card, try to start fattires image first and than without wiping the card copy your zip to the boot partition and boot into recovery mode (by holding power and the n button).

So the question arises, what is different in Fattire's zip that his zip boots from a SD card and one build after his instructions doesn't?
[Nook Color Android Development] fattire:
FWIW this was just checked in:

http://review.cyanogenmod.com/#change,11353

It's a workaround for now.
[Nook Color Android Development] michaeljr10wv:
thank you...it's finally syncing :)

michael
[Nook Color Android Development] mmark66:
Difference in zip content

Comparing the contents of Fattires original zip and a zip file I build after his instructions (which does not boot if flashed to a SD card with Verygreens image), reveals that the following files are missing from my zip:

/system/app/Launcher2.apk

/system/bin/sh

/system/bin/recovery

/system/etc/permissions/handheld_core_hardware.xml

/system/fonts/DroidSans-Bold.ttf

/system/bin/applypatch

/system/etc/permissions/android.hardware.telephony.gsm.xml

/system/lib/libaudioutils.so

/system/app/MusicFX.apk

/system/fonts/DroidSans.ttf

(+26 sound files not listed)

Any idea why those are not included in the zip files we build?

Mark
[Nook Color Android Development] 911jason:
So with this fix, do we use the modified XML file from yesterday or the original?
[Nook Color Android Development] Homer_S_xda:
This one looks interesting: /system/etc/permissions/handheld_core_hardware.xml

I wonder what that one does?

Maybe spoke too soon? This file: /system/etc/permissions/tablet_core_hardware.xml is present and mine still requires the original to be flashed to SDcard first.

Homer
[Nook Color Android Development] Nburnes:
Anyone else get a tiny keyboard when using the browser? O.o
[Nook Color Android Development] fahadayaz:
I have a tiny one anyway. :P
[Nook Color Android Development] khaytsus:
I did several ICS builds to my SD card, no updates, fresh installs. No problems. And when I installed to EMMC, I did it with my latest build of ICS, never had the original fattire build on it.

I doubt this is the 'fix', something else..
[Nook Color Android Development] mmark66:
Hmm,

interesting. What's the file size of the zip you build? Can you check if any of the files listed in my post are present in your zip file? Also, did you use Verygreens generic SD installer or another way to get your zip onto the SD card?

Thanks,

Mark
[Nook Color Android Development] pioneersohpioneers:
I'm having the same problem. Is resetting the directory the way to solve it?

Also, I can't use git in ~/android/system. I get "fatal: Not a git repository (or any of the parent directories): .git"

Is this SOP? Should I have to reset all my individual git changes (~/android/system/system/vold, ~/android/system/bionic,... etc) before I can repo sync again?

Lastly, FatTire, you're the man. I finally am able to compile some zips and my nook is running ICS amazingly. There're a few problems, but no more than the ICS build I'm running on my Dinc2, and I built this ROM!
[Nook Color Android Development] oppy:
Good question. I got the idea by googling.

Now I can't compile - got another error:

*** Some files have been added to ALL_PREBUILT.
build/core/main.mk:536: *
build/core/main.mk:537: * ALL_PREBUILT is a deprecated mechanism that
build/core/main.mk:538: * should not be used for new files.
build/core/main.mk:539: * As an alternative, use PRODUCT_COPY_FILES in
build/core/main.mk:540: * the appropriate product definition.
build/core/main.mk:541: * build/target/product/core.mk is the product
build/core/main.mk:542: * definition used in all products.
build/core/main.mk:543: *
build/core/main.mk:544: * unexpected postrecoveryboot.sh in ALL_PREBUILT
build/core/main.mk:545: *
build/core/main.mk:546: *** ALL_PREBUILT contains unexpected files. Stop.

I did try to reset ~/android/system/system/vold just for the heck of it. Didn't seem to help.

This is frustrating at times, but I still love it! :D
[Nook Color Android Development] michaeljr10wv:
So, I finally got it to sync last night. It's building now...Ive seen a few errors, but it keeps building...is this normal?

Also, I'm doing this on a laptop....amd turion duo core 2.1ghz with 2GB ram...how long do you think it will take to build?

Thanks,

Michael
[Nook Color Android Development] mmark66:
Just a short update: Even if I copy all those file to my SD card after I used Verygreens SD installer to install a zip I build the NC does not boot. Only if I flash fattires zip first and then go into recovery and install my zip in a two step process my zip is able to boot from the SD card.

Very strange?! Something else seems to happen during the installation which is missing from my zip file. Any ideas?

Mark
[Nook Color Android Development] :
Yeah. I had the same problem. I suspect it has to do with the SD installer. I know my zip was like 120mb or so... it had issues fitting into the first partition made by the installer.. I ended up resizing the partitions but I think that might have caused problems because it never booted correctly.
[Nook Color Android Development] inportb:
Errors would stop the build process; did you get warnings instead of errors?

Hm... sounds like a 3~6 hour build, if you're doing nothing else.
[Nook Color Android Development] michaeljr10wv:
Thanks,

Must have been warnings...the build process didn't stop...

Ok, guess really 3-4 hours....

Mike
[Nook Color Android Development] rabshear:
It's fairly obvious that this thread has caused the github servers to become overloaded. So, my question is, how is the affecting the REAL developers? Are they having trouble syncing the repo? While I have learned some things by reading this thread, I have only been able to sync ONE time successfully and that was in the very beginning before everyone jumped on board. In retrospect, I would have preferred to not learn this way. Why don't we leave the building up to the real developers and find another way for people to learn how to build ROMs?
[Nook Color Android Development] redhawk79:
build errors

I tried to build last night after a fresh repo sync and got this output: http://pastebin.com/mYihk6SF

Anyone know what the problem is here. I'm obviously missing something but I don't know what it is or how to get it?
[Nook Color Android Development] gbohm:
i sometimes builded for the sgs.i know that this is offtopic . alot of people will only follow the instruction step by step to get a newer version.

i like the intention of the devs but i think this gives a huge unnececcery burden on the provider side and wasts a huge amount of energy ( not only on your pc but on every ip router and so on) and sadly time. i am a developer myself (delphi windows pcs) but i found the development in cm(kernel etc.) extremely difficult so if one doesn't have a good background in c or java i don't see any reason why he should build it by himself. of course some benefits deeper understanding of android and linux in general could be argued...
[Nook Color Android Development] oppy:
Not only that, but it hopefully makes some of the whiners realize how much work the devs put into new ROMs.

I couldn't disagree with naysayers like rabshear more. If you want someone to develop an app for you, find a professional and pay him/her to do it. Those of us that view this as an opportunity to learn something will still be here doing so. :rolleyes:
[Nook Color Android Development] rabshear:
How am I a naysayer? I'm only making the observation that this MUST be impacting the developers' ability to develop. Yes, I want someone to write a ROM for me. I am not a programmer. Just a hobbyist. There are better ways to learn to build roms that having everyone beat on the LIVE server. That's all.
[Nook Color Android Development] gbohm:
i don't think it has that huge of an impact i allways had problems syncing especially the first sync can be a problem.