yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] sednafx:
In terminal just copy and paste:

curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo

chmod a+x ~/bin/repo

Then Reboot the VM and run this in terminal:

cd ~/android/system

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

repo sync

Edit: yep make sure you have git installed
[Nook Color Android Development] psychoace:
I have a stutter so when I read your post this is all I saw. ok im sorry that is off topic. anyway if the sound is fixed I wouldnt mind doing a whole wipe for ics. I have not worried about rolling my own rom because I cant live without audio. if he doesn't have it thats fine as well. im patient
[Nook Color Android Development] 911jason:
Nope, didn't even realize there was something to install. Doing so now, thanks!
[Nook Color Android Development] MrColdbird:
Nothing else to add to this... :(

Thinking bout the missing video support... what exactly is ment by that?

I mean as long as a graphical output is possible on screen, software decoding should always work right?

Thinking bout running Mobo Player + Codec Packs on this baby once sound works.
[Nook Color Android Development] HacDan:
Hardware video decoding

I've never used Mobo player, but yes, software rendering will 'always' work. But, to get 28+FPS out of software rendering would be impressive. If I understand correctly, we don't have drivers that are updated for ICS, let alone 3.X kernel(if that even makes a difference?). Maybe Mobo can do it in software, but as I said, I've never used it.
[Nook Color Android Development] oppy:
Might want to re-read this. There are several packages you need to install.
[Nook Color Android Development] 911jason:
You're absolutely right. Thanks!

EDIT: This one doesn't show up in Synaptics for me -- lib32readline5-dev -- the one without dev shows up, so I installed that one. Hopefully it won't matter.

P.S. I told you guys I was a newb! =)

---------- Post added at 07:30 PM ---------- Previous post was at 06:37 PM ----------

Fetching projects: 100% (243/243), done.
Checking out files: 100% (5365/5365), done.out files: 11% (601/5365)
Checking out files: 100% (421/421), done.ng out files: 20% (87/421)
Checking out files: 100% (24603/24603), done.ut files: 20% (5022/24603)
Checking out files: 100% (19043/19043), done.ut files: 0% (148/19043)
Checking out files: 100% (195/195), done.ng out files: 27% (53/195)
Checking out files: 100% (23382/23382), done.ut files: 0% (20/23382)
Checking out files: 100% (2994/2994), done.
Syncing work tree: 100% (243/243), done.

Woohoo! Progress!

---------- Post added at 08:02 PM ---------- Previous post was at 07:30 PM ----------

Uhhhh... I think I royally screwed up.

I'm pretty sure I did the REPO INIT and the REPO SYNC without changing out of my HOME directory. I now have a Vendor folder in my Home folder. Please tell me it's a simple matter of dragging that folder to android/system/ ?!

Also, because this process was split between last night/this morning and this afternoon, I couldn't remember if I did this before the REPO INIT & SYNC:

curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo

So I just did it and it seemed to take those commands without problem. Am I screwed now and need to re-start from the beginning? Or can I drag the vendor folder to android/system and continue on? Are there any other folders that I need to move if so?
[Nook Color Android Development] jschill31:
Hello to all,

I have been away for a good week now and I see many new users are working and most are building. With so many users having issues with the java/memory issue ("java -Xmx2048m" in common.py to "java -Xmx1024m") why is this not officially changed? I ran into this personally a week ago and made the manual change but in order to sync all new changes I know I will need to change it back and then change it again when my build breaks. My vague understanding of this simple change affects how much machine memory is dedicated to java building. If my understanding is true, making the 2048 change to 1024 official it may add a little time to get the final output zip. Wouldn't it be more important to ensure all can complete the build than worry about how long it takes? It is not a big deal to change and then re-change this line but why continue to have it this way if it causes so much grief? I apologize if my understanding is way off on this but I just finished reading page after page of issues caused by this line of code. It just makes sense to me that this change is officially adopted if at all possible. I am a humble student of this project and do not mean any disrespect, honest.

Cheers
[Nook Color Android Development] EverythingNook:
Every time i switch an app from portrait to landscape (or vise versus) the app crashes, any help?
[Nook Color Android Development] wakeboarder8156:
Try fixing permission in rom manager if you haven't already. My apps wouldn't open but once I fixed permissions they open and function perfectly
[Nook Color Android Development] EverythingNook:
Thanks, but it didnt work.
[Nook Color Android Development] wakeboarder8156:
Apparenlty I can't repo anymore, terminal says its an invalid command. I have done the following countless times and was able to repo the Galaxy Nexus source code but for some reason I can't get CM.

UBER noob here so talk dumb to me please!!!
[Nook Color Android Development] fattire:
Is it possible that "repo" isn't in your path of executable directories?

If you have "repo" in ~/bin, you may need to add it via this command:

PATH=$PATH:~/bin

meaning, "set PATH equal to the previous contents of PATH, but also look in ~/bin for an executable command as well..."

You can make this command 'permanent' for every Terminal session by adding it to ~/.bashrc <-- this gets run every time you open a new terminal.

And in other news....

Helpful Tip! Put the command time in front of any command and it will tell you how long the command takes to finish.

So for example,

time mka encore

will report the total time it takes to build (assuming it doesn't break in the middle)

And another helpful tip... it would appear the classic cyanogenmod command, "brunch", is now working for encore, so you can use that instead of "mka encore" or "make -j#".
[Nook Color Android Development] mrapollinax:
How far down the rabbit hole have I gone? I looked at the "merged" change list for CM/ics and actually thought is was awesome that someone commented out the WiMAX port of the API since that was aborting my more recent builds....

wondrous!
[Nook Color Android Development] rabshear:
I am compiling with Mint. Since it is based on Ubuntu, just use the same method that Ubuntu users are following.
[Nook Color Android Development] khaytsus:
Anyone else experiencing hard locks? I got one last night, one today.. I had experienced no reboots or hard locks prior to this.

What happens is I unlock, tap an app to launch and both times I could see it draw the highlight around the app icon then the screen freezes. adb is dead, can't get into it, etc.. I left it for around 3-4 minutes, Android is not restarting itself, I have to hit power for 8+ seconds to power off.

First guess on this sort is the kernel, but no kernel changes since at least 12/23, didn't look at modules etc.. And usually unless it's a kernel OOPS, Android will eventually reboot itself.
[Nook Color Android Development] wakeboarder8156:
I have done that. I redid every command roughly 10x trying to get it to work. I'm about to delete the VM and redo it
[Nook Color Android Development] jschill31:
Hello,

I repo'd and built last night and both the CM and Android versions of Trebuchet were working perfectly. Upon a reboot today it seems that neither seem to launch? No app drawer button, no widgets and no way to open anything including settings? Very strange goings on here, but prior to the reboot everything except sounds seems to be working for what I tested. Still no Angry Birds but other games now work that did not. It is nice to see the internal memory show up under storage. I have a couple ideas to try, if anyone else has an idea on the launchers please respond.

Cheers

Update: Evidently there was some garbage in Dalvik cache that needed to be cleared? Can't explain this one....

OK, now this is pissing me off. Every time I re-boot the tablet I need to go into CWM and clear Dalvik in order for either launcher to function. Does anyone understand why or what is going on with my build, this is the first build of many that has had this issue. Last nights sync was the first I had done in about a week.
[Nook Color Android Development] inportb:
I think it's because this is part of the build system for all of CyanogenMod, and it's more efficient to dedicate more memory (and suppress garbage collection). The buildbot certainly has the resources, so I guess it's up to us to tailor the script to our needs.
[Nook Color Android Development] jschill31:
I did not realize that, makes sense but is going to continue to keep popping up. Thanks for the reply.

Cheers
[Nook Color Android Development] HacDan:
It will only continue to pop up if you don't have 2048MB of free system memory to dedicate to the build.
[Nook Color Android Development] sednafx:
Have a question in reference to how often a user should sync/build. I have been checking these two git repos:

https://github.com/fat-tire/android_device_bn_encore/commits/ics

https://github.com/bennetb01/proprietary_vendor_bn/commits/ics

Should I only need to resync/build if commits have been made to these repos? I understand these are just encore specific repos. Are there other I should be monitoring commits to?

I am trying not to put a load on the CM/Google server for a sync if no changes have been made etc.
[Nook Color Android Development] MrColdbird:
Im using Mobo for all my movies running at the usual PAL resolution...

Running Mobo in full software decoding mode and my Nook can hadle the 25~29fps it should, its why Im asking afterall...

It works so nicely on my CM7 Nook that Im wondering what exactly this missing "video support" is.
[Nook Color Android Development] HacDan:
You are not alone sir. Could you jump on #nookcolor on freenode? RedChops, myself(hacdan) and tedrona12 are all having the same exact issue.

If not you could post some info about your build setup? What versions of libraries you're using, what base OS you're building from, etc. Thanks in advance =)
[Nook Color Android Development] cybertimber2007:
Any logcat?
[Nook Color Android Development] andrewddickey:
I keep getting this and staying stuck at 99%

andrew@andrew:~/android/system$ repo sync
Fetching projects: 56% (137/244) fatal: Unable to look up github.com (port 9418) (Name or service not known)
github.com[0: 207.97.227.239]: errno=Connection timed out
fatal: unable to connect a socket (Connection timed out)
error: The requested URL returned error: 403 while accessing https://android.googlesource.com/platform/external/webrtc/info/refs

fatal: HTTP request failed
Fetching projects: 99% (242/244)

And having the same port error at 55-56%

I have all my firewalls disabled.

I started trying to sync at 10:00 this morning and it's now 4:00. Getting a bit tired. I keep stopping once it hangs, then restarting.

Ubuntu 11.10 in VirtualBox utilizing 60GB storage and 2GB of RAM

Any help?
[Nook Color Android Development] khaytsus:
Well, the URL is in fact 403. However, I'm having no problems. Only thing I can think of is that perhaps it's a mirror that you keep hitting. However, it appears to come from system/external/webrtc

Only other thing I can think of is make sure you don't have an old repo file you're using... I had trouble initially and turned out I was building in /media5/ics/ and following instructions, but because of my path I wound up running an old file in my ~/bin/ dir
[Nook Color Android Development] fattire:
Name or service not known looks like a dns error... but I assume you can connect to github.com via other methods, so that's probably not it, especially since the next line has it connecting (and timing out) to 207.97.227.239

port 9418 is the port git listens on... it connects and gets a 403 error via https... which is a "forbidden" error... trying to connect to https://android.googlesource.com/platform/external/webrtc/info/refs -- incidentally just trying w/a browser gets me the same error...

are you using any special additions to your local_manifest.xml?
[Nook Color Android Development] boggsie:
With friends like these ...

Actually, this made me laugh. Obviously sarcasm from Midnitte.

Best regards,

-boggsie
[Nook Color Android Development] renegade37918:
cant wait for this for my nook and just got a nook for my daughter for christmas good luck happy dev'ing
[Nook Color Android Development] luigi90210:
if you think its that easy than go make your own ics rom, its comments like these that will make devs like dalingrin leave our community because of cocky kids who think they know everything(i dont care if your not a kid but as of right now your a kid for posting that comment)
[Nook Color Android Development] dxxvi:
Oh.........
[Nook Color Android Development] rootfan:
Dalingrin is someone who enjoy's deving, and android very much, and most likely tends to mess with android as a hobby quite frequently. He is obviously a very talented developer (not just anyone can be:rolleyes:) and has spent a lot of time to get to where he is. You do not learn how to do what he does in a few hours, or days.
[Nook Color Android Development] motitas:
can we please let the comments that need ignoring be ignored and just get back on topic here? I think everyone needs to:

1) wait... seriously it's not that hard.

2) If your that impatient, get busy and learn how to build it yourself.

3) Accept the facts about what is said regarding bugs, just because the bug isn't a bug on a similar device doesn't mean it isn't on the nook color.

This is a very gracious offer your making. I think the last guy was a bit harsh... Anyways, I think the magnitude of this project is too big for someone who hasn't developed a ROM before. Dalingrin has lots of experience with android and the nook color, he has the knowledge to do this. I suggest maybe you learn a bit about android, have fun messing with roms for whichever phone you have, and then take on future projects. You clearly have the drive to star deving so why not start from step one? good luck to you :D
[Nook Color Android Development] mjb413:
dal, I think people have asked before and I just missed it. Do you have a donate link somewhere? Wanted to at least buy you a cup of coffee or beer (whatever your preferred is).
[Nook Color Android Development] mrapollinax:
Download "Nook Tweaks" from the market. In the app there is a place where you can donate to dal as well as config and take advantage of the kernel tweaks he provides.
[Nook Color Android Development] dreamhunterr:
Some insights on hardware acceleration. Quite an interesting read.
[Nook Color Android Development] iDidItAll4theNookie:
I will sit and wait patiently for CM9. I think watching the development unfold is half the fun anyway. Sorta like waiting for your baby to be born. If the CM team just dumped a new ROM on us the day after source was released, we'd all take it for granted instead of appreciating the results for the tough work that they are.

Let's lose the sense of entitlement for CM9. It's a gift from some really kind strangers. :)
[Nook Color Android Development] motitas:
That's so true, I remember the cm7 development for the nook and how every time we got over a hurdle people got so excited. And then we had mad-murdock make us the tablet tweaks bar, the most useful thing ever :)
[Nook Color Android Development] gordon1hd1:
Join the fun with the NT!

hi dalingrin, I am a long term fan of your work on NC. Just being selfish here, hehe. But I am wondering that if we get the Nook Tablet forum together to donate you a NT, will it be possible to lure you away from the Touchpad and the NC, to come join the fun at the NT forum?
[Nook Color Android Development] Divine_Madcat:
I hope not...besides.. i think B&N killed alot of the NT fun anyway..
[Nook Color Android Development] gordon1hd1:
Well hopefully once we make a break through with Kexec or 2nd-Init on the NT, we can bring some of the fun back. But I agree with you, B&N locking the boot-loader on the NT is a major buzz kill.
[Nook Color Android Development] liam.lah:
The other dude was being a bit of a douche. However It's unlikely a project would be handed to someone who has no work to show. I would suggest you find something to work on that people would need. An independent or complimentary project that gets both gets your name around and shows you know what you are talking about when it comes to android development projects. Then you would be able to come into a thread, offer to take the reins of a project and have the confidence of both developers and users that you could get the job done.
[Nook Color Android Development] dalingrin:
No, I doubt it. I will have the Nook Color, Touchpad, and the Verizon Galaxy Nexus. I have enough on my plate =P

If I get another tablet anytime soon, it will probably be the Transformer Prime or something like it. I really like the idea of having a real keyboard dock to go with the tablet. If I were to get the Transformer Prime, I'd probably spend my time trying to make a system like this for CM9+: http://www.youtube.com/watch?v=ezvAs759rbg

I'd also really like to get a vanila Linux distro working well for the Transformer Prime also.
[Nook Color Android Development] foltz61:
I like that order :). Thanks for your time and hard work.
[Nook Color Android Development] mjb413:
I just got my Transformer (1st gen not prime) and I absolutely love it. The keyboard dock is fantastic and works quite well. Nice to have the usb ports. I got the black friday best buy deal for $250 tablet and $100 dock. The prime should be pretty amazing.
[Nook Color Android Development] Zorkman:
Hi Dxxvi,

I would suggest you get in touch wilth dalingrin or fat-tire and tell them what your interesets and skills are.

They will then be able to tell you if there is a part where you can focus on or help.

You don't have to do it all on your own you know ;-)

I think unforgiven512 and keyodi are also helping out for example
[Nook Color Android Development] newellj79:
Wow, that looks nice. I'm hoping you decide to get the prime. Hoping best buy fills all the orders too. :)
[Nook Color Android Development] andrewddickey:
I'm logged in to github right now.

Nope. Didn't add anything to the local_manifest.xml

Left as is from gedit ~/android/system/.repo/local_manifest.xml
[Nook Color Android Development] HacDan:
Logcat

http://pastebin.com/a7vq0fCg. Assuming he IS having the same issue a few of us are in IRC. Which, by his post, he is.
[Nook Color Android Development] 911jason:
This is almost identical to my setup (I'm running 100GB storage and gave the VirtualBox 4GB of RAM) and I'm getting the same error and results.
[Nook Color Android Development] ajrty33:
help :(

Fetching projects: 100% (244/244), done.
Traceback (most recent call last):
File "/home/jon/android/system/.repo/repo/main.py", line 366, in <module>
_Main(sys.argv[1:])
File "/home/jon/android/system/.repo/repo/main.py", line 346, in _Main
result = repo._Run(argv) or 0
File "/home/jon/android/system/.repo/repo/main.py", line 137, in _Run
result = cmd.Execute(copts, cargs)
File "/home/jon/android/system/.repo/repo/subcmds/sync.py", line 443, in Execute
project.Sync_LocalHalf(syncbuf)
File "/home/jon/android/system/.repo/repo/project.py", line 999, in Sync_LocalHalf
lost = self._revlist(not_rev(revid), HEAD)
File "/home/jon/android/system/.repo/repo/project.py", line 1773, in _revlist
return self.work_git.rev_list(*a, **kw)
File "/home/jon/android/system/.repo/repo/project.py", line 1918, in rev_list
p.stderr))
error.GitError: platform/abi/cpp rev-list ('^1f7abe1dd3a3d37f7c852aa877c576f3cdb4a042', 'HEAD', '--'): fatal: Not a git repository (or any of the parent directories): .git

me@me:~/android/system/build$ git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_build refs/changes/61/11161/1 && git checkout FETCH_HEAD
fatal: Not a git repository (or any of the parent directories): .git

I cannot get past these errors. I've searched and searched and reinstalled java and build packages and done everything I can think of.

I'm running 64 bit Ubuntu 10.10 with Java6 JDK.
[Nook Color Android Development] sednafx:
+1 10 char
[Nook Color Android Development] yujikaido79:
I am getting the same issues, I am running Ubuntu in virtual box, 11.10.
[Nook Color Android Development] Apothegm:
My desktop is at home building right now, after installing Ubuntu and giving myself a Linux crashcourse this evening. I have to say, thank you fattire, for making me get off my ass and do this. :)

Also, when running lunch, the options that appear... is that the full list of devices cm9 will currently build for? meaning, with proprietary files from my p999 could I build ics for it with just that number changed after lunch? (Sorry if this has been asked, I was looking around for it and couldn't find it.) I'm assuming the answers no, or I would see the kangs in the g2x forum, but it doesn't hurt to ask.
[Nook Color Android Development] jschill31:
Hey guys,

I actually had to flash back to my CM7 rom in order to use my tablet tonight. With the holidays I have relatives in town wanting to look at pictures of my 9 month old. I didn't pull a logcat before reverting back due to time constraints. I plan on dinking with it during work in the morning. Not sure that a logcat is going to help any since neither launcher seem to completely load? I know I have a huge memory leak and I think that is what is going on. There is just not enough resources for the launcher to load. As far as build machine goes working with Ubuntu 11.10 32bit and standard Java 6 libraries, hope that helps. Wow, I did jump on #nookcolor and I do not have a clue how to even type a message.... Sorry, I am a middle aged geek who has never used IRC.

Cheers
[Nook Color Android Development] Midnitte:
Its just like using aim or gtalk; otherwise, you might want to check out http://www.ircbeginner.com/ircinfo/tutorials.html
[Nook Color Android Development] fahadayaz:
booting troubles

I'm having a bit of trouble booting the NC now for some reason. I sucessfully compiled a build and thought I'd get ROM Manager to flash it so then it can wipe the dalvik-cache too (just in case I get the problem some others have been having). Unfortunately, the device rebooted but didn't boot into recovery.

So I tried holding down power and manually doing it. Long story short, it seems that I can't even get into recovery. If I hold power to turn the NC it will automatically come back on. I can't actually turn it off now. I can't get a logcat since it never gets to a point where adb can see the device.

What can I do?

EDIT: I can actually get to the "boot menu" screen. i just can't boot either into recovery or the normal boot screen.
[Nook Color Android Development] sednafx:
I had something similar happen. I used a bootable CWR sdcard to restore my previous working nand. But I am sure there would have been an easier way.