yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] 911jason:
Thanks... I feared as much. I've tried MAKE SYNC a few more times and it keeps getting fatal errors. Maybe I'll try again in the morning.
[Nook Color Android Development] zequav:
Same here, got it to build in gentoo. make 3.82 works.
[Nook Color Android Development] Stale_bread:
If you did that, I would love you forever.

Linux hates me :)
[Nook Color Android Development] 911jason:
I keep getting this error during the "make sync" process...

Fetching projects: 25% (61/243) fatal: Not a git repository: '/home/jason/android/system/.repo/projects/external/jsilver.git'

It continues to fetch projects after that, but is it a problem?

================== EDIT (2) ===================

Okay nevermind, I re-read the instructions and found the part about corrupted repositories and needing to delete them. Done, now it skipped that error but it keeps hanging at 99% with a few errors:

jason@ubuntu:~/android$ make sync
cd /home/jason/android/system; repo sync -j16
Fetching projects: 46% (112/243) 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)
error: The requested URL returned error: 403 while accessing https://android.googlesource.com/platform/external/pcre/info/refs

fatal: HTTP request failed
error: The requested URL returned error: 403 while accessing https://android.googlesource.com/platform/external/srtp/info/refs

fatal: HTTP request failed
Fetching projects: 68% (166/243) error: The requested URL returned error: 403 while accessing https://android.googlesource.com/platform/external/qemu-pc-bios/info/refs

fatal: HTTP request failed
Fetching projects: 99% (241/243) github.com[0: 208.67.216.145]: errno=Connection timed out
fatal: unable to connect a socket (Connection timed out)

Any thoughts or suggestions?
[Nook Color Android Development] msaraiva:
Shouldn't it be +1 informative?

Wow, meta-moderation on XDA...we've come a long way. :P
[Nook Color Android Development] 911jason:
While googling my problem with github, I came across this post in the XDA Captivate forum:

Can I somehow change inportb's batch file to utilize this fix?
[Nook Color Android Development] khaytsus:
And make very sure not to touch ANY other settings in there, or the launcher will FC forever. Not sure which option does it, but both times I've played with options it dies constantly. If you just set it to auto rotate it's fine.

Not sure what you're suggesting here, except changing git to http... The repos would not be those, etc.. and -j40 is insane for repo sync, and we actually suggest more like -j2, otherwise the server stops accepting connections from you. That itself is easy, edit the Makefile and look for the sync portion and change the -j16 to -j2
[Nook Color Android Development] Jaostar:
Hello,

I've a problem at the end of the build, while creating the update zip.

The signjar.apk call results in an error. I've seen that the [input.jar] file for signapk.jar ( the /tmp/tmpiJhySP) is missing...

I've no Idea what went wrong...

(ps : JAVA_HOME is set, and path is right too)

here are the error messages:

running: java -Xmx2048m -jar out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpiJhySP out/target/product/encore/cm_encore-ota-eng.root.zip

Could not create the Java virtual machine.

ERROR: signapk.jar failed: return code 1

make: *** [out/target/product/encore/cm_encore-ota-eng.root.zip] Error 1

jao-VirtualBox system # java -Xmx2048m -jar out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpiJhySP out/target/product/encore/cm_encore-ota-eng.root.zip

java.util.zip.ZipException: error in opening zip file

at java.util.zip.ZipFile.open(Native Method)

at java.util.zip.ZipFile.<init>(ZipFile.java:127)

at java.util.jar.JarFile.<init>(JarFile.java:135)

at java.util.jar.JarFile.<init>(JarFile.java:114)

at com.android.signapk.SignApk.main(SignApk.java:454)

Any Ideas ?
[Nook Color Android Development] roger_n:
Try changing "java -Xmx2048m" in common.py to "java -Xmx1024m" if that fails try "java -Xmx512m" located in system/build/tools/releasetools/common.py

Let me know if this resolves your problem.

Roger:cool:
[Nook Color Android Development] HacDan:
I have no idea what make sync is, but you could probably lower your j16 to j4 and it should download fine. Looks as if you've got too many connections open.

If that's not it, are you on wifi? Possibly a flaky signal?
[Nook Color Android Development] mrapollinax:
I had toyed with this as well. However you'll see that the WUBI.EXE install file allows a maximum installation size of 30GB. You'll need at least 40GB but probably something around 60GB of space. You would be better off downloading Virtual Box or VMPlayer and running a virtualized instance. With either you will be able control the size of the virtual partition.
[Nook Color Android Development] keyodi:
you have to make a couple of changes to the /system/vold/DirectVolume.cpp in order for the /emmc to show up:

https://github.com/CyanogenMod/andr...cc57803f1e9aafd8ed6d8e93067d#DirectVolume.cpp
[Nook Color Android Development] :
If you're using WUBI... You should be able to mount your windows partition (presumably it would have the free space available) and just use a directory in that mount as your working folder... I'm not sure what kinda impact that may have on speed of the process though.
[Nook Color Android Development] Jaostar:
Yep! Changed it to 512 immediately to be sure, and it worked!

Thx
[Nook Color Android Development] inportb:
Yep... stuck. You must kill it (press ctrl+\) and retry.

Now that looks like a flaky network. It might help to wait a while before retrying, with lower concurrency (I have seen cases of people getting restricted for hitting the servers too hard).

I'm concerned that the Windows filesystem might not be powerful enough... but i's worth a try.
[Nook Color Android Development] 911jason:
Did that several times... at least six or seven over the period of 8 hours. With at least one break of 4 hours or more.

This URL gives me a 403 error when I type it into a browser, even now. https://android.googlesource.com/platform/external/pcre/info/refs

I don't think it's a flaky network since like I said this was the same error over and over for about 8 hours, all the while my internet was fine for other browsing. How can I change the concurrency in your process? I tried the "make sync -j3" as was suggested in fattire's walkthrough, but it didn't seem to change anything and I still saw -j16 once the script started running. Is that something that I can edit in the makefile?
[Nook Color Android Development] inportb:
Ah yes, a result of my inexperience with makefiles :3

Please try make sync J=3 to pass the concurrency argument on.

Alternatively, you could cd system then ../bin/repo sync -j3
[Nook Color Android Development] 911jason:
I just did that, but the first line that shows up is this:

cd /home/jason/android/system; repo sync -j16

EDIT: and I'm still getting the 403 error on that https://android.googlesource.com URL.
[Nook Color Android Development] inportb:
While I could not reproduce this,

$ make sync J=3
cd /home/andbot/android/system; repo sync -j3

you should be able to get the job done using

cd system; ../bin/repo sync -j3
[Nook Color Android Development] 911jason:
Even though it showed the -j16 I still let it go and what do you know, it finished fetching projects for the first time... now it's syncing work tree (37%). I'll let you know how it goes. Thanks!
[Nook Color Android Development] oppy:
This is the error I'm getting.

ValueError: malformed recovery.fstab line: "/system ext4 /dev/block/mmcblk0p5 NULL ext2"
make: *** [out/target/product/encore/cm_encore-ota-eng.derek.zip] Error 1

Am I correct in thinking it's partition-related? Anyone have an idea for a workaround?
[Nook Color Android Development] fattire:
Did you cherry-pick the 3 commits into the build repo, a la:

git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_build refs/changes/61/11161/1 && git checkout FETCH_HEAD

git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_build refs/changes/62/11162/1 && git checkout FETCH_HEAD

git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_build refs/changes/63/11163/1 && git checkout FETCH_HEAD

Until these are merged into main cyanogenmod, you have to manually do this. The process for merging btw is that someone who isn't building for nook needs to make sure that adding it won't break anything for the other devices.. then someone with merge privileges (cyanogen, drkmobs, etc.) will need to merge it in. At that point it becomes official and there will be no need to do the above.
[Nook Color Android Development] oppy:
Yep, but I did get errors:

derek@DOLAPTOP-LINUX:~/android/system/build$ git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_build refs/changes/61/11161/1 && git checkout FETCH_HEAD
From http://review.cyanogenmod.com/p/CyanogenMod/android_build
* branch refs/changes/61/11161/1 -> FETCH_HEAD
M	tools/releasetools/common.py
HEAD is now at 12fe2ca... Extract uboot image creation from core/Makefile
derek@DOLAPTOP-LINUX:~/android/system/build$ git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_build refs/changes/62/11162/1 && git checkout FETCH_HEAD
From http://review.cyanogenmod.com/p/CyanogenMod/android_build
* branch refs/changes/62/11162/1 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by checkout:
tools/releasetools/common.py
Please, commit your changes or stash them before you can switch branches.
Aborting
derek@DOLAPTOP-LINUX:~/android/system/build$ git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_build refs/changes/63/11163/1 && git checkout FETCH_HEAD
From http://review.cyanogenmod.com/p/CyanogenMod/android_build
* branch refs/changes/63/11163/1 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by checkout:
tools/releasetools/common.py
Please, commit your changes or stash them before you can switch branches.
Aborting

Maybe I was barking up the wrong tree with the partition idea?
[Nook Color Android Development] 911jason:
So I think I just finished the sync...

Fetching projects: 100% (243/243), done.
Checking out files: 100% (4700/4700), done.ut files: 31% (1501/4700)
Checking out files: 100% (1794/1794), done.out files: 28% (513/1794)
Checking out files: 100% (62/62), done.ing out files: 16% (10/62)
Checking out files: 100% (787/787), done.g out files: 15% (124/787)
Checking out files: 100% (4876/4876), done.out files: 2% (140/4876)
Checking out files: 100% (745/745), done.g out files: 19% (146/745)
Checking out files: 100% (407/407), done.ng out files: 49% (202/407)
Checking out files: 100% (24603/24603), done.ut files: 43% (10674/24603)
Checking out files: 100% (19043/19043), done.ut files: 0% (16/19043)
Checking out files: 100% (420/420), done.ng out files: 42% (180/420)
Checking out files: 100% (2051/2051), done. out files: 37% (760/2051)
Checking out files: 100% (1204/1204), done. out files: 5% (71/1204)
Checking out files: 100% (63/63), done.king out files: 3% (2/63)
Checking out files: 100% (23382/23382), done.ut files: 0% (4/23382)
Checking out files: 100% (2994/2994), done.
Syncing work tree: 100% (243/243), done.

rm -rf /home/jason/android/system/external/openvpn
jason@ubuntu:~/android$

Am I right? What's that openvpn at the end?
[Nook Color Android Development] racks11479:
OK, so I managed to compile on my OSX Leapord at work after some trouble shooting. Thanks fattire for the suggestions. And I come home and do a repo sync, lunch, make and i get this error on my Ubuntu 11.04. Never had it before. Don't know what went wrong.

Any suggestions would be greatly appreciated. I tried googling the same error with no solution. Is there something I need to change in 'encore_ota_from_target_files'?

Thanks,

Racks
[Nook Color Android Development] fattire:
This looks like a repo sync or in your case the git fetch error saying that some changes have been made manually to the common.py file in /build, so it can't pull new changes on "top" of those. In other words, you're trying to patch an already patched file.

Suggestion-- return everything to "normal" by doing this:

git reset --hard

This will undo any manually-made changes to the repo and return it to the state of the last good commit. Then at that point try doing those git fetch commands.
[Nook Color Android Development] fattire:
That rm -rf line is actually something I recommend you add manually-- it's just deleting the external/openvpn part of cm9 that is currently broken.
[Nook Color Android Development] fattire:
Did you manually do those three commands I referenced above? If not, the build will break around the area it did for you... it's trying to create an update.zip but choking on the recovery.fstab file. nemith fixed this, so if you want the fix, you gotta grab 'em for now.
[Nook Color Android Development] oppy:
Okay, I'll give that a try. I did edit common.py to change that memory setting to 1024. Will I need to re-edit each time I do a repo sync?
[Nook Color Android Development] racks11479:
yes, ran through the whole process a couple times. Gonna try a make clobber and start over.

Thanks!

-Racks
[Nook Color Android Development] guv.:
I just compiled a build with those changes, works great.
[Nook Color Android Development] fattire:
Some kind of title goes here.

Yeah-- but here's a quick way to do it.

cd to the directory, then make the changes you want to existing files, save the changes, then do this:

git diff > mychanges.diff

So that will save just your changes to a file. (try git diff by itself in a git repository sometime-- you'll see the "diff" (or difference) of files from the last commit to now.) All the ">" does is redirect what would have gone to the screen into a file for safe keeping. (If you're new to Linux, remember the ">" -- you can redirect any output into a file with it. Try "ls -la" by itself, then try "ls -la > example.txt". I'll leave it to you to discover what "<" does.)

Then, let's say you git reset --hard to "undo" your changes. And let's say three weeks go by and you repo sync to get the latest stuff, and you pull in those build patches from nemith... etc...

The next time you want your changes to be re-applied...

git apply mychanges.diff

Go ahead and try it...
[Nook Color Android Development] racks11479:
Success! Forgot I edited the common.py last night. Saw your suggestion for the other poster. Did the 'git reset --hard' and ran the 3 git fetch commands and all is well. Will do as suggested above as well to save a .diff for future changes.

Thanks fattire, you sir are awesome!

-Racks
[Nook Color Android Development] :
Fattire, you sir are a saint among men.

Not only are you developing for this platform... You're actually taking the time to teach the community how to build (with quite thorough explanations).

The 'thanks' button just wasn't enough.

Thank you.
[Nook Color Android Development] 911jason:
Okay, I give up. Deleted my Ubuntu partition and I'll just wait (im)patiently for the next update.zip to be posted.

Thanks for those who tried to help, I appreciate it!
[Nook Color Android Development] unsivil_audio:
+1 for now.
[Nook Color Android Development] khaytsus:
If anyone is missing apps that require Phone calls, this will work (but could have other weird consequences, like apps that try to make phone calls crashing... Who knows, report back).

Probably will need to reboot for the market to use the new permission. Possibly clear market cache, but I did not have to do this myself.
[Nook Color Android Development] crono141:
I hate to interrupt the build from source party, but how is development progressing? What issues have been solved? What still needs work? How close is the sound issue to being solved?
[Nook Color Android Development] Samiam303:
If it doesn't work try clearing the dalvik cache. I had to do so to get the market to work properly.

Build it and find out!
[Nook Color Android Development] afzalarsalan:
As of today what do I need to manually merge in to the source code in order to build the most up to date version.
[Nook Color Android Development] mrmark93:
Not all of us out here have the ability (time/resources/skill) to build. Some of us are content to wait very patiently for when projects are 'ready' for 'prime time' as it were. Sometimes little updates about features, success's, setbacks and failures are great to hear.

I do appreciate all the work being done, and having read several pages of methodology of building environments, git repo's, and the various malaise of trying to build in a Mac environment, I've learned a lot about that process, and hope to put it to use when I have more time available. It would be nice, as well, to hear things about the topic of this thread. If all those that are building this are sworn to secrecy, or if I'm out of line, I apologize in advance for asking.
[Nook Color Android Development] Lynehammike:
Hi Crono,

It is a little difficult to filter the development and build problem posts.

From the Commits/twitter/posts so far:

- sound is still not working, there doesn't seem to be any mention of it, so I guess it is a while off.

- rotation has been fixed - so the new builds flip between landscape and portrait properly.

- still no video, and like the sound - no real discussion of any progress.

- a lot of the recent Commits seem to be focusing on stability of the ICS on the Nook.

So if you decide to download the required 25gigs, commit to learning, and are patient enough to debug and rerun the build: you will end up with a more stable version of the Alpha with better rotation and usb mounting capability.

I think this is in line with fattire's comments on the second post of this thread, so I am guessing that he will continue to keep it up to date.

Michael.
[Nook Color Android Development] MedLine:
it builds! you guys rock!! can't keep up ... i'll catch up with you after the finish line.
[Nook Color Android Development] Jaostar:
Hi!

I just have some little questions concerning audio :

Who is actually working on it, and how can I help?

Also, what other hardware is known to use the Ti DAC3100?

I'm a developer and already (once) wrote drivers (QNX) for some machines used in rubber industry... I'm willing to help but not sure if my skills are good enough.
[Nook Color Android Development] mrapollinax:
I didn't see this in the rest of the thread but when I build I get the error that it couldn't be 'signed' and the build process stops. What steps do I need to take to correct this?
[Nook Color Android Development] 911jason:
Reposted below...
[Nook Color Android Development] Jaostar:
have a look at post #894, it may help as much as it did for me ;)
[Nook Color Android Development] newellj79:
Actually I believe fattire said he fixed sound a while ago now. He just hasn't pushed the code yet. This is my understanding anyways, apologies if incorrect.
[Nook Color Android Development] oppy:
Worked like a charm:

Package complete: /home/derek/android/system/out/target/product/encore/update-cm-9.0.0-RC0-NookColor-KANG-signed.zip
55382748bd7b02f1062c32508f4efb36 update-cm-9.0.0-RC0-NookColor-KANG-signed.zip

Woohoo! Thanks for the guidance! :D
[Nook Color Android Development] mrapollinax:
aaaaaaaaaannnnnnnnd built! thanks!
[Nook Color Android Development] tj!2k7:
Thanks dalingrin and fattire for getting this ball rolling, and for helping the community become more self-reliant. =)

In attempting to navigate my way through the choose-your-own-adventure of attempting to build ICS, I keep dying at the following spot:

If I run lunch , none of the items listed start with "cm-encore-".

After running . build/envsetup.sh && brunch encore , I inevitably get

ERROR: signapk.jar failed: return code 1
Could not create the Java virtual machine

Also, on another note, when I ran ./setup-makefiles.sh from within ~/android/system/device/bn/encore, nothing happened...?

Not sure where I went wrong... did the proprietary files not copy over properly perhaps?

Thanks.

=== Update ===

All I really needed to do heed the suggestion a few posts up... this is why I hate posting questions... ugh, I feel like a dope.

which lead to:

Changing to java -Xmx1024m did the trick.
[Nook Color Android Development] oppy:
What I did in this case was run . build/envsetup.sh && lunch , then selected encore (which was #5 IIRC) and it worked fine.
[Nook Color Android Development] racks11479:
Did up setup repo correctly?
[Nook Color Android Development] 911jason:
As far as I can tell, I did every step until that point correctly. How would I know if I setup repo correctly? (That's not sarcastic, by the way!) ;)
[Nook Color Android Development] inportb:
I guess you'd check to see if it's the same as https://dl-ssl.google.com/dl/googlesource/git-repo/repo

There are some older versions floating around that do not work anymore.
[Nook Color Android Development] racks11479:
take a look at this post, he was mentioning the same errors as yours, seems to be missing some dependencies.

http://xdaforums.com/showpost.php?p=20577452&postcount=678
[Nook Color Android Development] Dj-Gutz:
You should probably talk to them on irc or something

But that's the most progress I've seen pushed to git

https://github.com/unforgiven512/android_device_bn_encore/tree/audio
[Nook Color Android Development] Samiam303:
Since a bunch of people have been asking -- I hope this isn't supposed to be a surprise or anything but fattire said in IRC last night that he has audio done and working, he just needs to finish testing it and push it to the repo. It should be available soon.
[Nook Color Android Development] MrColdbird:
Thank god. Ive been longing for audio support for so long.

I will name my first kid fattire.
[Nook Color Android Development] psychoace:
I will name my kid mrcoldbird so I can always remember to never give my kid a dumb name like fattire. The name only works if you don't have to call an actual human being that
[Nook Color Android Development] cybertimber2007:
fattire et al:

Can you take a break and look into this? http://xdaforums.com/showthread.php?p=20781484

They kind of beat me to one of my ideas, an easy to use Cyanogenmod compiler... though my biggest idea was a VM that all ready set up for compiling (minus a small repo sync, aws it would already be pre-synced), and i'm still thinking about it for the nook color.
[Nook Color Android Development] michaeljr10wv:
A VM ready to sync would be GREAT..ivr tried unsuccessful several times.

Mike
[Nook Color Android Development] MrColdbird:
It's where I stopped reading. Awesome. ;)

To tell the truth I'm super horny for coming audio support (if the rumor is true...).
[Nook Color Android Development] inportb:
I've been doing this thing within a chroot. I could package it up for all the Linux users if necessary...
[Nook Color Android Development] bedoig:
That's where I stopped reading...

Lol. Sorry, off topic. Ban me now!
[Nook Color Android Development] 911jason:
Anyone???

-------------

Okay, with Fattire's encouragement, I setup Ubuntu again, this time in a VirtualBox. I've got ADB working this time, woohoo! However, now when I get to the part where I install the repository, I am getting this error and cannot move past this point:

jason@jason-VirtualBox:~/android/system$ repo init -u git://github.com/CyanogenMod/android.git -b ics
Traceback (most recent call last):
File "/home/jason/bin/repo", line 690, in <module>
main(sys.argv[1:])
File "/home/jason/bin/repo", line 657, in main
_Init(args)
File "/home/jason/bin/repo", line 189, in _Init
_CheckGitVersion()
File "/home/jason/bin/repo", line 214, in _CheckGitVersion
proc = subprocess.Popen(cmd, stdout=subprocess.PIPE)
File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1239, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
[Nook Color Android Development] ioos:
911jason, do you have git installed?