yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] pioneersohpioneers:
Hey guys, I've fixed a small issue with the boot animation in the latest builds of ICS. If you're not getting a fullscreen boot animation, do this:

I edited the first line in desc.txt in /system/media/bootanimation.zip to be "1280 600 24". I did this after building the ROM and then I just opened the zip with archive manager. Hope this works for y'all !

Anyone know where to find this in our repos?

Also, quick question... Is there a difference between opening our ROMS and deleting APKs from /system/app and deleting the apk from ~/android/system/packages/apps in our repo?

Thanks!
[Nook Color Android Development] gbohm:
just building a rom is not an achievement just because you can sync git and copy some commands into terminal you can't apprechiat the work of a dev....

if you are a dev yourself and really look at some commits and try to understand what and why they tried this you will see what i mean
[Nook Color Android Development] Nburnes:
Everyone has to start somewhere man.
[Nook Color Android Development] gbohm:
yeah and you are absolutely right if you want to start developing you should allways try to build for yourself no doubt in that but if you just want a new version and some basic knowledge a zip and reading should be enough downloading 50gb hundreds of time isn't really great.... economically and environmentally
[Nook Color Android Development] oppy:
Probably true, but the fact that most internet traffic is wasted is hardly a new concept.

I suppose one can argue the relative merits of fattire/dal/devs decision to encourage others to compile their own builds, but, in the end, it really wasn't my or your decision to make. I find it interesting.
[Nook Color Android Development] Homer_S_xda:
I resize the first partition: /boot, *before* letting Verygreen's 1.3 install the first time. That way, the other three partitions have not been created.

There has to be a difference between Fattire's sample zip and the one currently built from the source. I know that Vg's 1.3 updates and does not wipe, as you can use it to update nightlies for CM7 with no issue or loss of data.

To summarize:

Fattire's sample installs using Verygreen's 1.3 and a current build can be installed over it. Either case leads to an ICS preview install that boots from SDcard.

If you take a fresh Vg's 1.3 and the same current build, you end up with a boot loop.

I know that Fattire said it has not been tested from SD, however, I was thinking we could help each other figure out the reason and perhaps feed that back to the devs.

Homer
[Nook Color Android Development] xdp:
Sorry but I have to agree with gbohm here. Building a ROM is NOT developing. If anything, people learning this process might DEvalue the work of a dev in their mind, because they think, check this out, I've only been at this a few days and I'm already developing! If you are a developer, you probably went to school for it, or if not, you learned development on your own via various other means. I don't think anyone learns to develop out of someone teaching them how to paste commands into a terminal to build. The gap between that and learning Java/C++ is pretty huge.

With that said, I still think it's cool fattire is getting people to understand processes better. A lot of XDA is just mindless bickering and nonsense, so some technical discussion is at least an improvement on that. But, I disagree with not releasing a new zip for all this time when others could be enjoying the devs' hard work, and I don't think people should confuse building a ROM with actually developing software.
[Nook Color Android Development] mrapollinax:
There may have been another ulterior motive to breaking down the build process here. Namely the fact that for those who have been complaining about the lack of development on the NC from the devs in terms of a flashable ROM have pretty much died down. Right now the statement is this: "Yes there is development going on but it is really early in the development cycle, but if you really want to have a flashable ROM here is how you build what we have right now..."
[Nook Color Android Development] inportb:
>I don't think people should confuse building a ROM with actually developing software

I don't think there is any confusion involving the concepts of ROM building and software development. Rather, I think ROM building is a prerequisite. While you could technically develop software from scratch, for the sake of writing code... most software development is done on existing bodies of code, to be run on actual hardware. You cannot call yourself a developer unless you could take your code from source to binaries.

Moreover, learning works in a peculiar way... one usually starts from the most superficial processes (downloading existing source and making sure it builds), then tests the waters (making small modifications and making sure it still builds), and finally jumps in (doing what he/she actually wants to do to the software).
[Nook Color Android Development] xdp:
Building is not really a pre-req...it's more like an afterthought. A developer doesn't learn to build software and then learns how to code. He/she learns how to code, and then the building is just a necessary step you have to get done, just like you have to learn to use your IDE or set up other things. I will agree, however, that learning can start with just making small changes and building. That is a way to learn a new codebase, but not really a way to learn software development in general, which requires a lot more education in theory and design.
[Nook Color Android Development] alton987:
I don't understand why a zip isn't posted in the general thread. That way know one has to support it and keeps junk out of the Dev thread. (sorry just added junk)
[Nook Color Android Development] MrColdbird:
I think its a clever move from fattire still...

He basically just created a cloud-based powerful building bot... consisting of the users that is. :D

If you consider that the CM Building Bot is down and has been for a while I do think its a good move...

As for me... I belong to those that will try to add minimal changes and rebuild... and maybe, figure out some nice gadgets that could be cool to have.

If there's a few more people like that then fattire's approach already beared fruit.

Afterall CM is a community approach, isn't it.
[Nook Color Android Development] jromney:
I successfully complied a build on New Year’s Eve. It was a mountain to be climbed twice, but the final result was a huge sense of accomplishment.

The statements that people are not developing vs. building are moot. The greatest achievement of this project is that more people are starting to explore, understand and use Linux.

Fattire, thanks for giving me the inspiration to get back into Linux.

Viel Spaß!
[Nook Color Android Development] anapospastos:
After building, into the $OUT folder I got two zips, the first is "update-cm-9.0.0-RC0-NookColor-KANG-signed.zip" and the second "cm_encore-ota-eng.<my_username>.zip". What's the difference between these? The 2nd is always, don't like this word but ok, 1,3mb bigger.
[Nook Color Android Development] douginoz:
The way I see it is that the NC needs fresh developers to invest time in porting ICS to it. The Honeycomb ports dried up and before ICS was released it didn't look good for any devs to come back after such a long absence. I was 80% sure that nobody would port ICS to the NC.

Fattire's idea ensured that a new generation of developers could rise out of almost nothing. In all probability, most of the people that have downloaded the gigabytes of files and spent hours learning the commands and compiling will cease doing so as soon as ROMs are released. But a few people will remain and carry on development. And bugs will probably be resolved faster because there will be more guys out there that are knowledgeable about the NC and can help resolve things.

Having said all that, at some point a critical mass or tipping point has to happen where these guys start releasing their own ROMs. This is exactly what happens with all ROM development for phones - a few guys work together initially to get a basic understanding, then people start releasing ROMs.

Those releases should be in their own threads and NOT in this thread - this is a DEV thread, not a ROM thread. And anyone that releases a ROM will have a pretty good idea of what they're getting into because there'll be a rush of questions and n00b problems that will demand (politely) help.

So it's not a question of "if", it's a question of "when" someone will release a ROM. It seems to me that, out of the many guys that have downloaded and compiled what's available, there's only so many guys that are going to get into serious development. So there would be little point in waiting any further since relatively few new guys are going to jump on the bandwagon - and those that do will already be several weeks behind and probably not really contribute anything.

Judging from this thread, I'd say that time is rapidly approaching. Relatively few new guys are coming on board from scratch now, and there seems to be a good core of guys that are working on it. And most seem to only be investing the time simply to get a compiled version they can flash themselves and aren't really contributing anything. So at some point it doesn't really progress matters by not allowing guys to release their own ROMs, and as a few have pointed out, it becomes a bit silly for people to be hammering githubs, downloading gigabytes, and spending hours of CPU time compiling things.
[Nook Color Android Development] xdp:
douginoz, I mostly agree with you, but I think what I and a few others here are trying to say is that a new generation of developers, probably not even one or two developers, will not rise out of this attempt to teach people how to compile the ROM themselves. The steps necessary to do that vs. the actual coding work necessary, integrating drivers, kernel work, etc., are not similar at all, and learning your way around Linux/github/terminal windows does not naturally lead to software development in any sort of fashion. If at all, that would only happen from this process sparking someone's interest and leading to years of learning, not becoming a dev in a few weeks or even months. So, I can agree with you that we've reached a point of diminishing returns with this teaching thread, but I don't even think it's creating any new actual developers like you seem to.
[Nook Color Android Development] marlonbr:
HOLY SH*T I COMPILED AND FLASHED THIS MOD*F*CKA!

Thanks guys, this is awesome!

I don't have the skills to help on low level stuff and reverse engineer drivers but will try to contribute once CM9 takes form as a role.

Since I'm playing with this on my work, I waited a day to get my nook from home to get the proprietary stuff before compiling and only then I noticed I couldn't use ADB on that sneakpeek1. Suddenly I saw a comment to get the proprietary stuff from elsewhere on gdocs. Well, after that all went great!

I have two suggestions that I've commented on the ics-nookcolor-build-roughdraft gdocs document.

See you at REPO SYNC! :D
[Nook Color Android Development] crnkoj:
hey guys just to report back (i edited a few comments into fattires docs aswell), i managed to get it working on an ~amd64 gentoo machine, its pretty much straight forward, most of the compile tools are anyways on the system already, the only thing to be aware of is that you must either use sun java 1.6 or icedtea6 and not icedtea7. if anyone needs some help with it on gentoo just ask here or im often on the #nookcolor channel (gmt+1 timezone)
[Nook Color Android Development] Homer_S_xda:
What SDcard platform are you using and did you make any custom changes to it? Also, any steps you do in your build that are different from Fattire's walkthrough?

Homer
[Nook Color Android Development] apewall:
Edit:Removed
[Nook Color Android Development] andrewddickey:
This is driving me nuts. I've started over 3 times from scratch. I've tried using both my network connection at work, and through tethering via my phone. No dice.

Fetching projects: 54% (132/244) fatal: Unable to look up github.com (port 9418) (Name or service not known)

It stops at 54-56%....every....single....time......

Then it will sync up to 99% and hang until infinity. Only when I used my phone tether the first time, did I get

Traceback (most recent call last):File "/home/andrew/android/system/.repo/repo/main.py", line 366, in <module>_Main(sys.argv[1:])File "/home/andrew/android/system/.repo/repo/main.py", line 346, in _Mainresult = repo._Run(argv) or 0File "/home/andrew/android/system/.repo/repo/main.py", line 137, in _Runresult = cmd.Execute(copts, cargs)File "/home/andrew/android/system/.repo/repo/subcmds/sync.py", line 443, in Executeproject.Sync_LocalHalf(syncbuf)File "/home/andrew/android/system/.repo/repo/project.py", line 975, in Sync_LocalHalfself._InitWorkTree()File "/home/andrew/android/system/.repo/repo/project.py", line 1758, in _InitWorkTreeraise GitError("cannot initialize work tree")error.GitError: cannot initialize work tree

I've been re-trying since last Friday.

Help. Please.

And I also have all firewalls disabled. Using Ubuntu 11.10 in VirtualBox.
[Nook Color Android Development] darkfalz:
If it's hanging at 99%, change the number on connections down to 1 or 2 (repo sync -j1). That's what I had to do, and it worked fine.

And as for the error about work tree, there is a file you will have to edit (I think it's called "common.py", should be able to find out by searching the thread) to change the amount of RAM that is used. The answers are in the thread somewhere, you'll have to dig for them though.
[Nook Color Android Development] andrewddickey:
Tried sync, sync -j1.....everything. Only got to the tree once. Ill look it up.
[Nook Color Android Development] alershka:
I just ran the andbot and I got an error

Could not create the Java virtual machine.

Error: signapk.jar failed: return code 1

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

I saw someone report a similar error earlier (pre-andbot) and they were told to make the following change:

Try changing "java -Xmx2048m" in common.py to "java -Xmx1024m" if that fails try "java -Xmx512m" located in system/build/tools/releasetools/common.py

I'm not sure how to do that in andbot.

Any thoughts?
[Nook Color Android Development] eyeballer:
Did you read the andbot readme? https://github.com/jyio/andbot/blob/master/README.md

Look towards the bottom after mka bacon. Try that first.
[Nook Color Android Development] darkfalz:
I just realized that my second bit of info was incorrect. The bit about changing the RAM was actually for the error that was posted right after yours, regarding not being able to create a Java virtual machine. So my mistake there.

However, I did get the tree error at one point on my Linux Mint VM, but when I installed Ubuntu, it actually worked fine.
[Nook Color Android Development] inportb:
eyeballer says the truth. Also, keep in mind that andbot is equivalent to a build system that you'd set up yourself, so you could follow the other recommendations in this thread if you want to.
[Nook Color Android Development] Stale_bread:
i want to build it so bad.

i have installed ubuntu on 6 different computers.

non have worked. all have had different errors.

the first time i tried on mac i had it almost working. the only problem was that the sync never finished. but now, my mac is throwing tons of error just in the

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

this is what i get:

Traceback (most recent call last):
File "/Volumes/CyanogenModWorkspace/android/system/.repo/repo/main.py", line 366, in <module>
_Main(sys.argv[1:])
File "/Volumes/CyanogenModWorkspace/android/system/.repo/repo/main.py", line 346, in _Main
result = repo._Run(argv) or 0
File "/Volumes/CyanogenModWorkspace/android/system/.repo/repo/main.py", line 137, in _Run
result = cmd.Execute(copts, cargs)
File "/Volumes/CyanogenModWorkspace/android/system/.repo/repo/subcmds/init.py", line 285, in Execute
self._LinkManifest(opt.manifest_name)
File "/Volumes/CyanogenModWorkspace/android/system/.repo/repo/subcmds/init.py", line 173, in _LinkManifest
self.manifest.Link(name)
File "/Volumes/CyanogenModWorkspace/android/system/.repo/repo/manifest_xml.py", line 102, in Link
self.Override(name)
File "/Volumes/CyanogenModWorkspace/android/system/.repo/repo/manifest_xml.py", line 95, in Override
self._Load()
File "/Volumes/CyanogenModWorkspace/android/system/.repo/repo/manifest_xml.py", line 262, in _Load
self._ParseManifest(False)
File "/Volumes/CyanogenModWorkspace/android/system/.repo/repo/manifest_xml.py", line 273, in _ParseManifest
root = xml.dom.minidom.parse(self.manifestFile)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/dom/minidom.py", line 1914, in parse
return expatbuilder.parse(file)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/dom/expatbuilder.py", line 924, in parse
result = builder.parseFile(fp)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/dom/expatbuilder.py", line 207, in parseFile
parser.Parse(buffer, 0)
xml.parsers.expat.ExpatError: syntax error: line 1, column 0
[Nook Color Android Development] HacDan:
And all 6 of them would have worked to build with =) There's an error in your local_manifest.xml file, make sure it's identical to the one linked in fattire's google doc.
[Nook Color Android Development] jschill31:
Hello all,

It has been a week since my last build and I see many things have changed... As always I have searched the thread but encountered a new error that has me dead in the water. Any pointers would be great, here is the error:

Target ram disk: out/target/product/encore/ramdisk.img

/bin/bash: line 1: 26636 Broken pipe out/host/linux-x86/bin/mkbootfs out/target/product/encore/root

26637 Illegal instruction | out/host/linux-x86/bin/minigzip > out/target/product/encore/ramdisk.img

make: *** [out/target/product/encore/ramdisk.img] Error 132

make: *** Deleting file `out/target/product/encore/ramdisk.img'

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

I assume there are files in my $OUT that need to be cleaned. Any help would be grand and greatly appreciated.

Cheers
[Nook Color Android Development] fahadayaz:
Wow, you're quite an inspiration, I must say. As you were starting off your post my mind thought to post the exact video you posted, as a response. Imagine my surprise when you linked to it just as I was thinking of it. It just goes to show that your focus is one that is shared by others.

I think the mindset that we own our devices, and should be able to do as we wish with them once purchased, is an important one and you're making a great point to support that, I feel. If I'm honest, I consider it a noble "quest" and am glad I have been keeping up on this journey.

edit: sorry for the long post! :P
[Nook Color Android Development] gerwinscheeve:
Read carefully :) Thanks for the .
[Nook Color Android Development] fattire:
I hope there's something inspirational there, and it wasn't too much of a ramble :)
[Nook Color Android Development] fahadayaz:
Looks like a single full stop/dot will make a lot of nook owners happy. :)
[Nook Color Android Development] gerwinscheeve:
There sure is some inspirational stuff there. Thanks for that.

Installed. Works like a charm. Small problem that it only ran in landscape.

You have to go to Trebuchet and under general select auto-rotate and all is well.

Once again many thanks.
[Nook Color Android Development] alershka:
Thank you guys. I had a severe brain fart and lost sight of the fact that andbot just automates everything that fat_tire laid out.

I changed the java setting then started a build. It went really fast, like 15 minutes. Does it pick up where it left off? I did not get a chance to look at it because I had to run to work but I will look at it tonight. I am running Ubuntu in a virtual machine with 3 cores of my 3.2 ghz 4 core processor dedicated to the VM and 4 gb of memory. I expected a build time in the 1 hour + range based on what I read before.
[Nook Color Android Development] khaytsus:
Yeah, used this on my wifes computer, per a thread in the General forum I believe.. EaseUS Partition Master Home Edition

Burn the card, launch that app and then extend the first partition. I never could "figure out" how to do it manually, although in reality in this very thread there is information on how to format it manually. Really it's the partition location, not the format. Has to start at Cylinder 63, not at 0.

I suspect you're on Python 3, someone else said they had that problem. Make sure Python 2 is being used.
[Nook Color Android Development] crono141:
Can I assume that sound is still not working in the latest build/source/git/whateveryoucallit? :)
[Nook Color Android Development] khaytsus:
Correct, sound is not yet pushed into the repo.
[Nook Color Android Development] therkr:
@fattire

I got it. ;)

(Though I'm stuck with finals currently and will only build after maybe sound is working.)

Thanks everyone who put efforts onto the CM9 port.
[Nook Color Android Development] nukedukem:
Thank you for sharing your knowledge fattire. I have learned some great tools for customizing my android experience. Your tips have made experimenting with my Nook (and XOOM!) a much richer and rewarding experience. You are a gent and a scholar!
[Nook Color Android Development] bytte:
The Dalingrin kernel mutitouch patch to encore-32-ics cyttsp-i2c.c https://github.com/dalingrin/nook_k...da7c1a/drivers/input/touchscreen/cyttsp-i2c.c seems to break fast scrolling (flicking) in some apps (adobe reader) but not others (XDA App) when loaded on CM7.1.0 stable.

Is that to be expected?
[Nook Color Android Development] rabshear:
About the sound not working...Maybe I'm crazy, but I have sound. Maybe not many people read carefully enough to find the right ROM.
[Nook Color Android Development] fattire:
I'm guessing you must be crazy.
[Nook Color Android Development] nukedukem:
Question fattire - after compiling a custom kernel, where in my source folders would I place it so that it is added to my builds? And will the wifi driver be compiled against the new kernel automatically during the ROM building process or will I have to compile a wifi driver against the new kernel outside of the normal environment and add it to my sources?
[Nook Color Android Development] fattire:
Put it in:

android/system/device/bn/encore/prebuilt/boot/kernel

If the wifi driver is no longer compatible due to your changes, it will need to be added as well, also in prebuilt...

From that location it will be added to the build and copied to the right places.

Note that for compatibility with nook tweaks, the kernel is actually copied twice into the file system (see the device.mk file for where). The same kernel is copied 2x, which is a bit of a waste, because we're currently not using two different kernels. Two kernels were used previously-- one with 32 and one with 16-bit color. The 16 bit color kernel looks AWFUL on ics, with lots of banding and ugliness, so I just decided to make both kernels the same until I can determine that removing both of them wont' screw up nook tweaks. I don't think it will actually... I asked dalingrin and he wasn't sure how it behaved if those kernels aren't there when you try to switch 'em. Probably just says "nope nope" and that's it...

Anyhoo, I'll look into that today and make sure it's "safe" to remove these kernels, and if so, we can make the .zips kernel-size*2 smaller.

thanks for reminding me re that.. it kinda got lost in the shuffle.
[Nook Color Android Development] xdp:
Thanks fattire...I got it... :)
[Nook Color Android Development] Arbelzapf:
Too bad. This was actually one of the first things I tried to get some more performance out of the rom I built yesterday.

I was already wondering what's the story behind the 16bit mode not working, so thank you for answering before I even asked :D
[Nook Color Android Development] inportb:
Yes, it does. Did it succeed? You might take a hint from the color of the command prompt after it exits.