yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] roger_n:
I tried using your latest Makefile with the beagleboard option and was unsuccessful I had to revert back to your original file. I captured some of the errors if you're interested again thanks for making the build process as painless as possible.

---------- Post added at 07:31 PM ---------- Previous post was at 07:26 PM ----------

Do you have a notification on the nook that show "USB debugging connected" if no try wiggling the usb cable I have to put something under my cable for a good connection my port is getting worn.
[Nook Color Android Development] J-ROCK:
Do you have a notification on the nook that show "USB debugging connected" if no try wiggling the usb cable I have to put something under my cable for a good connection my port is getting worn.[/QUOTE]

USB debugging connected is on and it seems to have a firm connection and no luck. Ive been trying for 3 days with no luck.
[Nook Color Android Development] roger_n:
The last thing I can think of is have you tried "sudo ./adb devices"? Off the top of my head I can't think of anything else to try if I do I'll post it.

USB debugging connected is on and it seems to have a firm connection and no luck. Ive been trying for 3 days with no luck.[/QUOTE]
[Nook Color Android Development] J-ROCK:
@roger_n no luck yet.
[Nook Color Android Development] roger_n:
Silly question you are using the cable that came with the nook charger? I'm pretty sure it's not the same as a generic cable its wired differently. :confused:
[Nook Color Android Development] J-ROCK:
well with the original cable it doesnt work but with my G2 cable im able to mount my sd.
[Nook Color Android Development] smiley4017:
How did you fix this. I am having the same issue.

Thanks for any help.

Gary
[Nook Color Android Development] foltz61:
I'm getting it also. Does anybody elses mention commits? Specifically common.py from releasetools which we all probably had to change. This is my first re-sync so, I'm not sure what to expect.
[Nook Color Android Development] iDidItAll4theNookie:
Yeah, my mint install is on and old 40GB HDD (who says Maxtors don't last?). Can't fit that on my install, and I am hesitant to pay today's prices on hdds. I'd have a hard time with the download size anyway with my ISP. I, too am curious why there's so much to download for what end up as a 100mb zip. I know the install ends up being higher, but not 26gb.
[Nook Color Android Development] Nburnes:
Just re-synced again. With the Beagleboard patches keyodi was kind enough to point out and at 1.2GHz this thing really flies. The fancier animations are laggy, but that is to be expected at this point. Term Emu has also stopped hating me, which is nice.

For web browsing/Pulse/reading use, this is easily a daily driver for me.
[Nook Color Android Development] jschill31:
Hello,

There is a file that I had to modify when compiling on Ubuntu which i believe you are going to need to do as well. I was having a an issue much like a few who are using vm on a PC. It seems to be a memory issue involving how much is dedicated to Java. To fix I oppened up common.py (full path: android/system/build/tools/releasetools) and scanned through the code. A few pages back give the exact line to look for if you are using vm to compile but if you are using Ubuntu then look for a line that in Pink that says something like "java -Xmx2048m -jar" and change the 2048 to 1024. I want to say it was 3/4 down the document but it was 3am and I was half asleep. Once I made that simple change I saved and did the mka bacon command again and it finished the build.

Hope this helps, wish I could remember the exact line.

Cheers
[Nook Color Android Development] Bawb3:
Okay finally got it to run a build! :-)

It didnt make an update zip though, I ran the 3 commands that were supposed do that after my last repo sync.

I got the following error at the end of the build

1 error

make: *** [out/target/common/obj/APPS/DownloadProvider_intermediates/classes-full-debug.jar] Error 41

However it looks like everything is in the out folder, just no update.zip
[Nook Color Android Development] motitas:
well I meant how long did the build take? and for that last command you should've done "make -j2 bacon" since you have a dual core setup. thanks for all the info! Im not building on my lappy tho.. 27 gigs is too much for this ssd.
[Nook Color Android Development] zequav:
fattire, do you recommend a make clobber between builds? I remember having to do it when compiling CM7.0.x in order to have some changes applied (don't understand why, since make should take care of that).
[Nook Color Android Development] mrapollinax:
I'm having a similar error but it is with the following:

***[out/target/common/obj/PACKAGING/public_api.txt:3203] Error 5: Added public field android.app.DownloadManager.Request.NETWORK_WIMAX

***[out/target/common/obj/PACKAGING/checkapi-current-timestamp] Error 38

I'm guessing something is changed with the api reference but I'm not sure how I can update that on my end.
[Nook Color Android Development] :
I'll have to double check. I don't believe that my working directory became anywhere near 26gb. If the working directory does get that large, it would have to be a result of the build process... not the download.

The files to download during the sync end up being something like 6.5gb. I think a big reason for this is that you're not just downloading the Nook Color's code. When you repo sync you're syncing to the entire Cyanogemod repo and as such it pulls down the code for all the supported devices.

It seems like it would be more efficient if there was a way to just pull the base android framework and the device code for whatever device you were trying to build. But that would probably require each device to have it's own repo. I'm not

all that great with git repos though.
[Nook Color Android Development] motitas:
during the build process many files are inflated and then deleted, that's why I asked how much this process writes in total to the disk. I have an SSD and I don't wanna be damaging it like that. Anyways, just got a touchpad for Christmas.... Gave the nook to my dad. I'll probably still keep up with development though.
[Nook Color Android Development] :
Yeah, sorry... My reply was directed toward the person I had quoted, who was concerned about the size of the download. It looked like he thought the download was ~26gigs.

Sorry for the confusion.
[Nook Color Android Development] unsivil_audio:
Repo is down? Can anyone confirm?
[Nook Color Android Development] jlt220:
Gapps

has anyone had luck with Gapps, each one i have tried has ended with "Unfortunately, setup wizard has stopped"

thanks
[Nook Color Android Development] newellj79:
Repo is good as of 936pm eastern.
[Nook Color Android Development] smiley4017:
I made the changes to common.py. Tried every combo down to 512 still does not work. same error

fatal: reference is not a tree: 22259cf87f92883807c8171202a7e875558814c3

Syncing work tree: 100% (243/243), done.

device/bn/encore/: leaving ics; does not track upstream

error: device/bn/encore/: fat-tire/android_device_bn_encore checkout 22259cf87f92883807c8171202a7e875558814c3
[Nook Color Android Development] Samiam303:
Just popping in to announce that I'm successfully building the rom on OS X 10.7 without having to install an old version of xcode. I'm going to try to write up a Lion walkthrough detailing what steps I followed to get it to build. I'm really appreciative of all the work that's gone into this -- it's really amazing to get ICS onto the nook so fast.
[Nook Color Android Development] fattire:
Awesome.. If you get a walkthrough going, let me know and I'll point to it from my doc.
[Nook Color Android Development] Nburnes:
Are you using ones for ICS? http://goo.gl/aBi5m
[Nook Color Android Development] nukedukem:
That's good news. I had seen that Google made some code changes recently for the latest Xcode. I'm curious if the qemu stuff still gives you errorrs?

Edit: Errorrs? WTF is that. Can anyone tell me how to get the old larger keyboard back on my nook? :-)
[Nook Color Android Development] Homer_S_xda:
I got the build built, assumption here really as I got a .zip out the end. Fattire's first preview worked fine from Verygreen's 1.3, but this one seems to not work. It appears to "flash" fine but the result is a boot loop. Is there something different in the way the script is written between the two that makes Verygreen's approach break? Or is it just my build that is broken?

Homer
[Nook Color Android Development] jlt220:
I thought I was but I will try those instead, thanks
[Nook Color Android Development] oppy:
I haven't actually been able to complete a build, but I think I'm now at the point where I understand why. My Nook is setup to dual boot and I'm getting partition errors when the build is trying to complete. If someone knows how to account for the partitioning scheme I'd appreciate it. I'd like to keep the stock ROM on the secondary partition if at all possible.

Also, I'm definitely learning a lot, so thanks to Dal, fattire and the rest of the guys for helping out!
[Nook Color Android Development] b30sam:
I had the same issue to.

What I did was to first flash the zip given in post # 2 and then flash the zip compiled by me. That worked...
[Nook Color Android Development] khaytsus:
Doesn't matter, it formats /system, clears /cache etc

I went straight from CM7 to ICS I built, but make sure you do a factory reset when you do that. For updating from build to build clearing cache should be sufficient (and AFAIK done by the zip itself..)
[Nook Color Android Development] therkr:
There you go....http://www.xda-developers.com/android/nook-color-gets-ics-season-gets-a-little-brighter/
[Nook Color Android Development] zequav:
I'm curious, where do you take these from? What's the difference between these and the _v2 you posted before? These ones obviously have less google apps, but also the ones that are there are binary-different.
[Nook Color Android Development] HacDan:
I'm guessing these are the beta versions of the GAPPS CM9 will be using, although I can't say as if I've looked at the file. The thing is, you can download most of the GAPPS from the marketplace which would most likely explain the lack of apps in the ZIP that was posted.

---------- Post added at 03:47 PM ---------- Previous post was at 03:44 PM ----------

Did you use http://blog.alsutton.com/2011/12/20/compiling-android-master-on-mac-os-x-lion-with-xcode-4/ patches to get around the OS X SDK error message requiring Leopard SDK to be installed?

**EDIT** Successfully compiled a zip on OS X Lion as well with XCODE 4. Working well with the patches above. I had to manually apply them, but the zip worked out fine. Only issue is the DSPManager is force closing, but I'm guessing that is due to a lack of drivers for the DSP. Gonna start playing with the code base now that it successfully builds.

**EDIT2** Spoke too soon. Apps that have Dalvik cache built up don't survive a reboot. Seems as if the cache is ending up corrupted. Anyone else have this issue or did my build not go so well? Keep in mind everything works until I reboot.
[Nook Color Android Development] redDEADresolve:
Progress report? I'm want to build CM9 but I only have an underpowered Netbook. I'll put in the time if things are usable.
[Nook Color Android Development] ioos:
As long as you can get by without sound, it's very usable. It might take 6+ hours to build the first time, but subsequent builds will be much faster. Make sure to use

export USE_CCACHE=1.
[Nook Color Android Development] newellj79:
I thought i remembered seeing a post with a adb command line to access the stock launcher settings. I can't seem to find it though. Maybe I'm imagining it. If not can somebody help me out. Nothings wrong, I just want to see whats in there. :)
[Nook Color Android Development] jschill31:
Here you go: adb shell input keyevent 82 Best to make sure you are on the home screen before executing the command.

Cheers
[Nook Color Android Development] Kev8124:
It's just 'adb shell input keyevent 82' . Just keep in mind your tablet needs to be on the homescreen since it mimics the Menu keypress.
[Nook Color Android Development] ioos:
Woo-hoo! I finally got it to build on Arch Linux. I had to change the "python" symlink to point to python2 instead of python3. I also had to install openjdk6 which removed jdk (7). Make is a version too new, but it worked fine after the initial warning.

Time to banish Ubuntu from my machine!
[Nook Color Android Development] smiley4017:
I'm at a loss.

OK, I may just reformat my hard drive and start the whole process over. I must have screwed up somewhere. I'm still getting this, even after changing the memory down to 1024.

Fetching projects: 100% (243/243), done.

Syncing work tree: 4% (10/243) fatal: reference is not a tree: 22259cf87f92883807c8171202a7e875558814c3

Syncing work tree: 100% (243/243), done.

device/bn/encore/: leaving ics; does not track upstream

error: device/bn/encore/: fat-tire/android_device_bn_encore checkout 22259cf87f92883807c8171202a7e875558814c3

I'll give it another day, but it doesn't look like anyone can help.

Thank you for everything you all have done so far.

Gary
[Nook Color Android Development] 911jason:
Never used Linux before, but decided to give this a try... can I use the current version of Ubuntu for Windows?
[Nook Color Android Development] HacDan:
I had the same error, you need to change into the device/bn directory and manually

git pull
[Nook Color Android Development] smiley4017:
How do I do that
[Nook Color Android Development] inportb:
What's Ubuntu for Windows?
[Nook Color Android Development] MrColdbird:
Ive been asking several times before and as I can't see any audio related changes on the GIT I was wondering...

Is anyone working on getting Audio going?

It's the only reason this ain't a daily driver for me yet as I just love listening to my music while browsing the net.
[Nook Color Android Development] unforgiven512:
You might just want to do:

rm -rf device/bn/encore/

and then repo sync again.
[Nook Color Android Development] 911jason:
I posted that while I was downloading this:

http://www.ubuntu.com/download/ubuntu/windows-installer

Guess I was thinking it was going to run in some sort of Virtual Machine, not that I really even know what that is. Turns out it was just the installer that ran in Windows, now I have a dual-boot, which is fine.

However, I am already feeling like I'm way over my head. Going through fattire's guide, which lead me to the CM wiki, I see that I need to install the Android SDK, which also says I need to install the Java Development Kit, which as far as I can tell isn't available in a "deb" file. So I googled that and people are talking about having to compile the rpm or tar.gz file to create a deb file.

Boy this is intimidating!
[Nook Color Android Development] iDidItAll4theNookie:
I think what that does is create your Linux install inside the windows file system (no partition changes, it just makes a virtual partition, of sorts) and just adds another entry to the XP/Vista/7 bootloader. You can "uninstall" the distro at any time from within windows with little issue.
[Nook Color Android Development] andrewddickey:
www.virtualbox.org/wiki/Downloads

I used VirtualBox to set up Ubuntu so I can still use Windows without having to partition my hard drive. It also enlarges the virtual partition as it expands so you don't have to adjust the size all the time.
[Nook Color Android Development] HacDan:
Ya YMMV. It did work for me within OS X.

In regards to 'how you do it' you would open up your terminal of choice,

cd device/bn

and then manually run

git pull
[Nook Color Android Development] inportb:
The only thing you need from the Android SDK is adb, which does not require Java. If you want, you can try my copy. Put it in /bin or ~/bin or somewhere else convenient and chmod it to 0755.

There's no need for that [rpm or tarball] either, since sun-java6-jdk is available as a deb in a PPA. If you're using the latest Ubuntu, you have to take care to add the maverick repo, instead of oneiric.

If you haven't started yet, you might find an alternative build system useful. I'd recommend making bacon at step 6a.

The first few times could be intimidating... but don't worry about it! Jump in, and use the forum and IRC channel for help. Good luck!

It's in the pipeline; wait for it~
[Nook Color Android Development] 911jason:
Thanks inportb, I figured out the JDK install and have gone ahead and installed Eclipse and the Android SDK as well. The only problem I ran into was with the ADT Plugin for Eclipse, it gave me errors on the install, but since it probably isn't even necessary I didn't bother to troubleshoot them. I figured I can always do it later if I decide I really need Eclipse. I just wanted to install everything so I wouldn't have to find out mid-build that I was missing something important.

I'll use your alternate build and let you know how that goes.
[Nook Color Android Development] inportb:
You only really need the SDK (and possibly Eclipse) if you're making Android apps; if you're making the OS itself, all you need is adb (and only once, to grab proprietary files off your CM7 Nook). Good luck and think happy thoughts involving bacon!
[Nook Color Android Development] fattire:
+1 insightful
[Nook Color Android Development] 911jason:
I'm already running the initial ICS build from the 2nd post in this thread. I won't need to re-install CM7 before I can proceed will I?
[Nook Color Android Development] guv.:
Is it possible to access the internal 5GB partition somehow?

Gesendet von meinem NookColor mit Tapatalk
[Nook Color Android Development] 911jason:
Tools installed fine, but that 2nd command gave me this:

jason@ubuntu:~$ sudo make apt
make: *** No rule to make target `apt'. Stop.
[Nook Color Android Development] fattire:
I think it's accessible via "/emmc", but if it isn't we should fix that.
[Nook Color Android Development] guv.:
Yeah I allready tried that. /emmc shows up as empty for me and I can't create files there either.

Gesendet von meinem NookColor mit Tapatalk
[Nook Color Android Development] inportb:
I actually only tried this with CM7, though it would not be too late to reinstall CM7 when you discover that it does not work.

Using this?
[Nook Color Android Development] roger_n:
Make sure you are in the directory that has the "Makefile" from inportb then type "sudo make apt"
[Nook Color Android Development] 911jason:
Ding Ding Ding.... winner!

;)

Thanks... I feel dumb now, though.
[Nook Color Android Development] roger_n:
Ha ha it happens to all of us. :D
[Nook Color Android Development] HacDan:
Anyone?

Just moving it here incase it is/was missed because I only edited it.
[Nook Color Android Development] fattire:
the "mm" command...

So someone or other PM'd me and said they felt like reading this thread was like being in an Android class. I don't know if that's a good thing or a bad thing, but why not waste a few moments with another quick "lesson" for those of you building-- this one inspired by a convo I just had in IRC..

Someone just asked me if a broken build has to start over from the top when you type "make bacon" or "mka bacon" again-- the answer is no, the "make" build system is smart-- it looks at which source code files have changed since the last time it was building and will (in ideal cases) only re-compile stuff that's new and needs it. So, unless you've done a "make clobber" to wipe out all progress on your build (and erase the $OUT directory too), a broken build should pick up where it left off once you fixed whatever it was that made it break.

The "mm" command

So let's say you're noodling around the source, and you're looking at the stuff in

android/system/packages/apps

Which are a bunch of apps that are built for CM9. And so you're fooling around, and changing stuff in one of the apps, maybe Trebuchet or Email or something. Maybe you're adding a feature, or doing a translation, or just goofing off. And you want to see what the results of your change are...

And let's say you want to build the stuff for this project-- not make all of Android. You don't care about the system going and building other stuff. Just this. How's it done?

The answer is the "mm" command-- "make module"

Think of it as make, only for a particular module or modules (as denoted by the Android.mk files in many of the source code folders).

So to go back to that Trebuchet (the CM9 launcher) example-- if you cd into that directory:

cd ~/android/system/packages/apps/Trebuchet

then change some stuff. Then you want to build just Trebuchet.... you can use the "mm" or "make module" command.

mm -j4

And it will build the module(s) in the current directory (and subdirectories-- in this case, Trebuchet.apk and TrebuchetLauncherRotationStressTest.apk).

Note that the mm command will only work after you've done the ". build/envsetup.sh" command from ~/android/system and after you have selected your build product target via "lunch".

If the build results in a new binary, it will generally put the result in $OUT wherever it would have in a normal "make" or "mka" build. In the case of Trebuchet.apk, it goes in $OUT/system/apps where you can install it (adb install $OUT/system/apps/Trebuchet.apk or whatever). If you can read the Android.mk and any other .mk files it invokes, you can get a sense of what it's going to build, but usually it's the stuff in the directory (and "lower").

If you want to make the module from scratch, add the -B tag:

mm -j4 -B

and it'll rebuild ALL the files for the module, not just the ones that it thinks are newly changed or added. In other words, it's a total rebuild of stuff in the directory.

That's it! Hope this helps save time. If I was imprecise here, someone correct me.

Also, there's an "mmm" command too, but I'll let you investigate it on your own!
[Nook Color Android Development] 911jason:
How do I know when the MAKE SYNC step is done? There's a blinking cursor at the end of this:

Fetching projects: 98% (239/243) Receiving objects: 29% (5843/19495), 564.36 remote: Total 19495 (delta 10829), reused 18973 (delta 10307)
Receiving objects: 100% (19495/19495), 1.81 GiB | 580 KiB/s, done.
Resolving deltas: 100% (10829/10829), done.
From git://github.com/CyanogenMod/android_prebuilt
* [new branch] gingerbread -> github/gingerbread
* [new branch] gingerbread-release -> github/gingerbread-release
* [new branch] ics -> github/ics
* [new tag] cm-7.1.0 -> cm-7.1.0
[Nook Color Android Development] les02jen17:
That's it! I've had it! I can't stand not being able to have an updated ICS flashable zip, so I've decided. I'm going to install Ubuntu on my computer and build it myself. I don't know anything about Linux or Ubuntu, let alone building an ICS Android OS from scratch so please bear with me. I have a couple of questions:

My computer has the ff. specs:

2.93GHz Intel Core i3

1GBgb DDR2 RAM

Is the above specs sufficient?

My internet connection is 2mbps, DSL.

Also, I have 2 hard disk drives and I have them in partitions. I believe I can just install Ubuntu to one of them, right?

Please help me out and bear with me. I wanna learn how to build this thing. I totally support the drive to not post flashable zips 'cause aside from encouraging everyone to build, it just shows how responsible the devs are. My thanks goes to dalingrin, fattire and all the devs working on this. You're all awesome!

Tapatalkin' it from my rooted NookColor running CM7 MiRaGe [KANG] [7.2 RC] overclocked @ 1.2 GHz
[Nook Color Android Development] HacDan:
When

Fetching projects: 98% (239/243)

is

Fetching projects: 100% (243/243)

AND it returns back to a shell prompt. Exactly like before you typed in

repo sync

---------- Post added at 03:13 AM ---------- Previous post was at 03:11 AM ----------

The largest issue with building ICS is space. You're looking at ~26GB of space just to download the source and build. Specs of the CPU will be just fine.

In regards to your partions, yes, you could install Ubuntu on to one of them and that would work just fine. But as I said, you're going to need an ample amount of space to build.