yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] khaytsus:
Anyone having SOD's, try Green Power, Tasker, Setting Profile Lite, manually, whatever suits ya.. turn off wifi on screen off, like our CM7 SOD's.

I had 3 SOD's yesterday with Green Power turning off wifi, but turning it back on every 15m for 2m, today I set it to turn it off and leave it off when the screen is off and 0 SOD's today.
[Nook Color Android Development] foltz61:
Thanks for the info and the opportunity to learn fattire. My repo syncs keep getting stuck so, I think I'm gonna give up. 4 hours of trying with no results is frustrating.
[Nook Color Android Development] fattire:
How to make an update.zip...

So nemith and I worked a bit on the build of the "zip" files... Some me, but mostly him.

You'll need to use gerrit as I described a few posts above to get some patches that have been submitted but not yet accepted into the build system.

Instructions:

AFTER

(not before, AFTER) you repo-sync, do these steps:

$ cd ~/android/system/build
$ 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

Again, the $ is the prompt, not part of the command. These three commands must be run every time you do a new repo sync until the commits are accepted into cyanogenmod's repository, which will hopefully be soon. To see what these commands do, see:

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

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

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

So after you do this, when you build, instead of:

mka

try

mka bacon

And if it doesn't give you an error, you may get something that looks like this:

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

64928ef83e5ec68cd0b07e00ea9ebe85 update-cm-9.0.0-RC0-NookColor-KANG-signed.zip[

At the end of your build. Then, if you feel like risking everything (and as always, assuming all responsibility for the consequences), you can try flashing that zip (which is in $OUT) with clockworkmod recovery.

And please, for the moment, as part of our "learn to build" educational drive, don't distribute the zips! :) I have to say I'm amazed by the PMs and messages on IRC... literally dozens of people have been successful building this thing.
[Nook Color Android Development] fattire:
It's totally normal breakage due to the stuff from nemith not getting accepted yet. For now you can add them manually as described above.
[Nook Color Android Development] darkfalz:
then there are the ones that haven't been successful.

Do you think switching distros will change anything?
[Nook Color Android Development] fattire:
What are you using now?

Confirmed working:

* Ubuntu/Debian

* Arch (new)

People having Problems with...

* Arch (old)

* Fedora
[Nook Color Android Development] stevekent:
Thanks, I am trying that now....
[Nook Color Android Development] fattire:
I've updated the walkthrough instructions to reflect the newest stuff. Added the bit about the build that you need to add, and removed all the ugly stuff about adb sync system and all that. You can just flash the cm-update as per usual.
[Nook Color Android Development] inportb:
Right, so my little Makefile now makes bacon

make bacon

What that does is cherry-pick the three commits, build the bacon target, then link the update.zip to the top of your working directory.

Keep in mind that you still have to make sync, and all that. bacon is an alternative to build+snapshot+package. Snapshots do not work with make bacon.

I have a feeling that this would no longer be necessary soon, since the update.zip is generated automagically now; but I'm keepin' up ;)
[Nook Color Android Development] darkfalz:
Linux Mint 12.

Moving to Ubuntu.
[Nook Color Android Development] duuurp:
Well considering there are ~50 people viewing the build guide, I'd say fattire's experiment is working. More developers should take this approach! Make those flash addicts work for their fix! ;)
[Nook Color Android Development] fattire:
I really am heartened by the PMs I've been getting. A lot of people-- way more than I expected-- are actually trying this and succeeding... I would post excerpts, but I'd have to ask everyone first, and I'm lazy.

For those of you who are struggling, in the pit of dispair-- frustrated, confused.. trying a million things without success--

I feel and know your pain. Take a break. Go outside. Get some sunshine or a clean breath of air... get some sleep... this is the pain of learning :) It may feel like a dead end, but I've found that hoplessness sometimes turns into a breakthrough when you're at the edge of giving up.

Don't get overly pessimistic.. there's plenty of help waiting for you on IRC or on the forum.

Man, I should work for Hallmark.
[Nook Color Android Development] inportb:
Join us; it's fun :)

I usually idle as Pinako, fwiw.
[Nook Color Android Development] stevekent:
YOU ROCK!!!

Total compile time: 32m37.656s

AND IT WORKS!!!
[Nook Color Android Development] jschill31:
Hello,

If the kernel supports rotation now why is the ro.sf.hwrotation=270 line still in the build.prop?

cheers

Edit: Something is just not adding up about the kernel being able to support the rotation? Either I completely am missing something or I am not getting any kernel changes when I sync. Fattire, your way earlier post referencing how to fix the wacky screen glitch when going from portrait to landscape says that in order to correct this we need to remove the build.prop line above and switch to a different kernel. Is this new kernel not part of make process after syncing? Is it part of the files we pull from our Nook, hence a CM7 kernel? For some reason I have made this my mission to figure out, please expand more on how to fix the screen glitch as well as the small images in the recent apps launcher. Also in earlier posts I have referenced that I am experiencing several strange crashes with the Trebuchet launcher. It would seem that these only happen once I add gapps. I have used several different versions, some of which I know work perfectly. Has there been one specific set of gapps that you find work the best and could a link be added to the op? I think it would help in the long run as more build and help to tweak the build as well as cut down on bugs not caused by the rom itself.

Cheers
[Nook Color Android Development] nukedukem:
The fix posted was for people who are running the zip in the op. If you are syncing and building from source you don't have to do a thing.
[Nook Color Android Development] jschill31:
Hello,

Thank you for the response but if that is the case nothing is changing on my end after I sync and build? I have built successfully each night since Sunday, almost have all the commands memorized which is what I am gunning for. Both the kernel and the build.prop continue to stay the same. I do not think I am successfully receiving updates from Fattire's repo due to taking the second option (clone) from the first published instructions. I ended up doing this:

mkdir -p device/bn

cd device/bn

git clone git://github.com/fat-tire/android_device_bn_encore.git

mv android_device_bn_encore encore

Since I am new to this I was unsure exactly how to create a file as indicated and paste the "pastebin" code. Is it possible to somehow delete my first clone and do the process over and get the new repository? Since I am currently able to build and look forward to adding more devices I don't want to break anything and have to start completely over. Sorry for all of the questions everyone, I know it is adding to the pages but I don't just want to complete this build. I am hoping to actually grasp the entire process hopefully helping others along the way.

Cheers
[Nook Color Android Development] nukedukem:
jschill31 - since you aren't using the local manifest file, every time you repo sync you need to git-clone fattire's repo as well or you won't get the updated files. You can either redo this:

cd device/bn

git clone git://github.com/fat-tire/android_device_bn_encore.git

mv android_device_bn_encore encore

That should give you the newest files from fattire, or you could create the local manifest file and every time you repo sync it will automatically pull those files for you as well. If you want to add the manifest file I could help you set that up too.
[Nook Color Android Development] xdp:
Very cool to hear, however, do you still plan to release a new zip in the near future? Christmas is approaching and everyone will be busy...maybe in that lull between Christmas and New Year's? :)
[Nook Color Android Development] jschill31:
That would be outstanding, I am just not versed on the Linux commands yet.

Thanks!
[Nook Color Android Development] zorvalth:
As much as I agree with fattire for pushing people, +1 for a new zip for Christmass
[Nook Color Android Development] Midnitte:
Fattire needs presents too though =p, I'm all for a zip for new years though =p
[Nook Color Android Development] jschill31:
Good morning,

Evidently the prior instructions and new instructions have left me with an error pointing to something needing to be deleted. Here is the error, any idea what needs to be removed?

build/core/main.mk:322: implicitly installing apns-conf_sdk.xml

build/core/base_rules.mk:166: *** device/bn/encore/hwprops: MODULE.TARGET.EXECUTABLES.hwprops already defined by device/bn/encore/android_device_bn_encore/hwprops. Stop.

jim@jim-desktop:~/android/system$

My guess is it is something left over from my first clone of fat-tire git. I would also think there will be other traces like this if I get past this first error. Should an entire folder be deleted?

Cheers
[Nook Color Android Development] fattire:
Yeah this is the result of using BOTH the local_manifest.xml as well as manually cloning the repository to android_device_bn_encore.

the solution is simply

rm -rf device/bn/android_device_bn_encore

because you have the same thing in device/bn/encore

only the latter is getting automatic updates when you do a repo sync and the former isn't (you have to do it manually by cding to it and then saying "git pull origin ics")
[Nook Color Android Development] jschill31:
Ah, makes perfect sense. Building away now...again and hopefully with your added repo this time.

Happy Holidays!
[Nook Color Android Development] zequav:
Works ok for me. Just flashed the generated update-cm-9.0.0-RC0-NookColor-KANG-signed.zip

Just one thing: when flashing there is a message "Random offset: 0x53". Don't know what it means.

(edit) OK, I found it: http://xdaforums.com/showthread.php?t=1362200
[Nook Color Android Development] roger_n:
New Makefile?

inportb, First I want to thank you for making the build process so simple. I have a question in regards to your new Makefile which includes "bacon". I've been using your original Makefile "w/o bacon" and it creates update.zips just fine. What is the benefit of using the new Makefile is it even required?
[Nook Color Android Development] fahadayaz:
Well, searching the makefile for the words bacon brings up this section

cd ${SYSTEM}/build; \
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

Fattire, I'm wondering, does this not make step 4 in the walkthrough redundant?
[Nook Color Android Development] foltz61:
Missing Instructions

Ok. I gave up on the repo synce last night after 4 hours of failed syncs. I decided to try again this morning and was successful with the sync. I couldn't get adding the local_manifest.xml before the sync to work last night so, I was using the option B method of adding the "encore (nook) device folder for ice cream sandwich" after the sync. Problem is that the instructions changed last night. So, can anybody help me add what I need? I'd hate to have to run the sync again after so many failed attempts.

Thanks.

Edit:

Just started over. Repo sync errors out right from the start adding local_manifedt.xml. Researching.....

Edit 2:

Got it now. Don't ask. Should we start a newbie thread for build questions so this thread can stay clear?
[Nook Color Android Development] redDEADresolve:
How is everything working for you? Does Sound work?
[Nook Color Android Development] roger_n:
fahadayaz, I noticed the 3 files being fetched before I made the post, my question is are they necessary if I was successful creating update.zips with inportb's Makefile prior to the bacon change? I've never had a failed build so I don't want to change anything that may risk breaking the build process..
[Nook Color Android Development] rhester72:
This. Without sound, to be honest, I fail to see the point of an updated "public" zip.

Rodney
[Nook Color Android Development] tsukaza:
Linux Ubuntu 10.04

I am getting this error during make build

*** no rule to make target `vendor/bn/encore/proprietary/egl.cfg`, needed by `out/target/product/encore/system/lib/egl/egl.cfg'. stop

Thanks
[Nook Color Android Development] bled82:
Ok so im pulling out my hair , I have setup a Ubuntu 10.10 vmware build machine and the problem is the after getting adb working it will not see the nook color or more over it does not show a device id see attached screen shot , ran lsusb twice first time without the nook connect and the second is with the nook connected , looks like i need to some how set the device manufacturer settings on the device? Any help would be great this is the first rom I have tried to build and so far it has be a good learning process.
[Nook Color Android Development] tsukaza:
I think part of the Makefile modify the environment to handle the nook device IMO.
[Nook Color Android Development] fattire:
The reason I removed option (B) from the instructions was that some people were confused by the choice and doing option (A) *AND* option (B) instead of one or the other. And I figured it was better to just say the best way to do it rather than be ambiguous.

If you synced without it, it's not a problem. Just add the file and then re- repo sync and it'll pull in the encore device tree that you need.

One advantage to using the local_manifest.xml instead of manually "git clone"ing the file is that repo sync will automatically update the device tree in the future. When you git clone (which was method B), you have to manually go back and do a "git pull origin ics" every time you want to update the repo.
[Nook Color Android Development] J-ROCK:
I got this error towards the end of my repo sync:

error: Exited sync due to fetch errors

am I doing something wrong here?
[Nook Color Android Development] jschill31:
Hello,

One thing that I know would help me out is if you explain exactly how to create the local_manifest.xml file. I only know a handful of Linux commands and that is why I chose the second option to begin with. Somehow it would appear that I did create this file anyway without knowing it since I am having redundant command errors now. After 6 successful builds I seem to have tweaked my system. I am not even sure how to show hidden files on Ubuntu 11 to see what exactly is in my local_manifest.xml and what needs correcting. I have always learned better by figuring out how to fix something that is broke. :)

Thanks again for everyone's help

Happy Holidays
[Nook Color Android Development] inportb:
@J-ROCK: yes. you should retry until you get a successful sync :)

(sometimes you might see errors in-between, but it should be good as long as it finishes okay)
[Nook Color Android Development] bled82:
Could you provide the steps for this? please ! :confused:
[Nook Color Android Development] J-ROCK:
THANKS! But now I get this in the beginning

fatal: Not a git repository: '/home/jriani/android/system/.repo/projects/abi/cpp.git'

and it stops now. ??
[Nook Color Android Development] inportb:
The way I see it, my Makefile is only a stopgap solution so that we could have update.zip instead of having to use adb sync. The benefit of using the new Makefile is that you could make bacon (after you sync, of course), which means generating update.zip in the "official" way. If you choose to make bacon, note that it currently does not work with snapshots. Now that the "official" technique generates update.zip, I see my method will soon be unnecessary, and I'm happy about that :)

That is correct; `make bacon` using my Makefile ensures that the cherry-picking is performed just before building, so that everything falls into place. But be careful: if you are following FatTire's tutorial strictly (without my Makefile) step 4 is very much necessary. This might be a point of confusion, since my script hides some of the details from you (to hopefully simplify the build process).

Right. In this case, you'd delete the offending repository and sync again, because it is corrupt. To do that, write:

rm -r /home/jriani/android/system/.repo/projects/abi/cpp.git

... but be VERY careful with the rm command, because it is all too happy to delete things. Copy and paste the path to make sure you don't type anything wrong, and that you don't press enter mid-path and delete what you don't want to delete ;)
[Nook Color Android Development] J-ROCK:
@inportb thanks that fix that issue now Im getting another one geez!

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] inportb:
I'm not familiar with that error, so I'd wait for more knowledgeable users to comment. Did you manually clone FatTire's GitHub repository?
[Nook Color Android Development] J-ROCK:
yes I originally did.
[Nook Color Android Development] fr0zenblood75:
OK well I'd like to build this for my nook but I'm worried that my computer won't handle it. Its a laptop with 4gb ram a 1.8 ghz intel core 2 duo CPU with some fan issues. Itl think it will most likely die in the process if it over 5 hours long right ?
[Nook Color Android Development] tsukaza:
Resolved the egl issue, I did not get the proper files from the nook.

Reran make vendor fixed it :rolleyes:
[Nook Color Android Development] fattire:
perhaps the easiest way is to use the "gedit" text editor as follows:

gedit ~/android/system/.repo/local_manifest.xml

then paste the contents in-- making sure to avoid adding any extra stuff--

then save.
[Nook Color Android Development] khaytsus:
Fedora 14 (64 bit) is fine..
[Nook Color Android Development] jschill31:
Thanks once again, I believe I was trying to use a text editor I must not have loaded? I will switch to the gedit which I know works, that is what I used to create the USB rules. One very helpful user also PM'd me and clued me into how to show hidden files...I was to proud to ask.:(

Cheers
[Nook Color Android Development] J-ROCK:
Can you share your USB rules text?
[Nook Color Android Development] b30sam:
Has anyone done a successful compile with Linux Mint ?
[Nook Color Android Development] lincore:
Build kernel from sources?

Hi, Fattire.

Do you have plans to add 'building kernel instructions' to your awesome walkthru?
[Nook Color Android Development] jschill31:
gksudo gedit /etc/udev/rules.d/51-android.rules

SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", MODE="0666"

Save

chmod a+r /etc/udev/rules.d/51-android.rules

Sometimes a reboot is needed

Plug in the Nook

mkdir -p ~/.android && echo 0x2080 > ~/.android/adb_usb.ini && adb kill-server && adb devices

I am doing this from memory so I may have something wrong...it is certainly close to this. Try it, I am away from my station now. Hopefully my memory is working...:)

Cheers
[Nook Color Android Development] keyodi:
follow the instructions here for how-to build the nook kernel, except modify git checkout -b devel origin/encore-32 --> git checkout -b devel origin/ics-fattire
[Nook Color Android Development] fattire:
Funny you should ask. I haven't updated this since the early, EARLY days of 2011-- but if you kind of take it with a grain of this-is-a-year-old salt, you might find this wiki entry helpful:

NookColor:_Build_the_Original_Kernel

Right now the nookdevs site seems to be down, here's a cached version.

If you've built cm9, you've already got a lot of the requirements-- mkimage, the cross-compiler, etc. These instructions are old and used the barnes and noble-provided source code for version 1.0... that's probably not the one you want to use either, unless you're just messin' around.

But if you're just looking for basic info, some of this might still apply. When the site goes back up, feel free to make it more up-to-date.
[Nook Color Android Development] fattire:
Oh yeah, that's probably better :)
[Nook Color Android Development] MrColdbird:
As Christmas Holidays are finally here I will tackle compiling this baby myself...

In a very special way too... on a fresh 8GB Ubuntu Minimal Server VM, a true challenge indeed...

Wish me luck.
[Nook Color Android Development] Nburnes:
8 GB of space? The source pulling and building is 15+GBs
[Nook Color Android Development] MrColdbird:
Base Minimal System starts out with 180MB Size and full Android SDK is about 3.4GB... Network Share does the rest. :)
[Nook Color Android Development] inportb:
That's 8GB of RAM :cool:

Also... I wouldn't build on a network share; there's going to be a lot of file access.
[Nook Color Android Development] keyodi:
Beagleboard patches

Fattire found these patches early on in the ICS dev, but we just recently realized their benefit.

Without patches: Quadrant score: ~1100

With patches: Quadrant score: ~1450

Overall, responsiveness does seem to be better with the patches. Below are the steps for updating your source.

$ cd ~/Downloads (or any other folder path)
$ curl http://rowboat.googlecode.com/files/Beagleboard_ICS_patches.tar.gz > Beagleboard_ICS_patches.tar.gz
$ tar -zxvf Beagleboard_ICS_patches.tar.gz

next

$ cd <android source path>/bionic
$ git patch ~/Downloads/Beagleboard_ICS_patches/bionic/0001-Add-omapfb-header-file.patch

then

$ cd <android source path>/hardware/libhardware
$ git patch ~/Downloads/Beagleboard_ICS_patches/hardware/libhardware/0001-call-OMAPFB_WAITFORGO-ioctl-to-wait-for-empty-buffer.patch

rebuild source Note: if git patch doesn't work, then try git am

Let us know whether you notice any improvement...
[Nook Color Android Development] roger_n:
Thanks for the explanation inportb but can you shed some light on what you mean by (note that it currently does not work with snapshots.)
[Nook Color Android Development] cybertimber2007:
Oh really?

Can you PM me any useful information you have? I'm a big fedora user (since I'm RHCT/RHCSA certified) so I'm more keen on using Fedora to build this.

Also would like to take a crack at getting it to build on Fedora 16 ;) Hey we're all learning here so why not xD
[Nook Color Android Development] khaytsus:
Nothing special, including me using the default OpenJDK.. Already had all the dev stuff installed, only thing I had to install was zlib-devel. I'd already followed this to set up SDK (not necessary to build Android, but probably has similar dependencies I might guess...)

http://fedoraproject.org/wiki/HOWTO_Setup_Android_Development

AFAIK some folks have had trouble with 16.. Not sure why, I don't have a 16 on hand yet except a few test VMs.
[Nook Color Android Development] darkfalz:
I tried on Mint, but no luck. Switched to Ubuntu and it worked fine.
[Nook Color Android Development] khaytsus:
Bionic? Should one substitute Encore here? Or am I being obtuse with Bionic being a phone name :)

Checkout from 4pm 12/23: 2061 (1100Mhz, ondemand)

And compile barfs...

Perhaps I did it wrong, there's no such thing as "git patch", tried normal patch.... Should I use git am instead?