yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] shenye:
@sbice try this http://www.javahotchocolate.com/tutorials/setup-eclipse.html#64-bit
[Samsung Galaxy Nexus] beekay201:
@op, Thanks, but at least, check the howtos you link to, there's missing steps there.

I dont agree these kind of threads should be in dev section.
[Samsung Galaxy Nexus] ljwnow:
Why? It's great for people to learn.
[Samsung Galaxy Nexus] PaulW21781:
Agreed, the thing which fuels development is curiosity, and when people want to know how to do something, it helps to have links or topics dedicated to that specific area.

The OP's link is pretty much the same as this too (official Android building guide)

http://source.android.com/source/initializing.html
[Samsung Galaxy Nexus] dave_t321:
Has anyone managed to build the android-4.0.1_r1.2 branch with Ubuntu 11.10?

I know it works on the master branch and the r1 branch supposedly didn't support it but have the build tools been updated this one?

Just wanted to check before commiting to a massive download!
[Samsung Galaxy Nexus] shenye:
It's the branch I use for building VillainROM.
[Samsung Galaxy Nexus] PaulW21781:
The only thing to note with 11.10, is when you install all the build libraries, one of them is incorrect (no longer available in 11.10). Instead of installing lib32readline5-dev you need to install lib32readline-dev instead.

$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
x11proto-core-dev libx11-dev lib32readline-dev lib32z-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils
[Samsung Galaxy Nexus] dave_t321:
Perfect, ta muchly.
[Samsung Galaxy Nexus] beekay201:
If you didn't code it yourself, it doesn't belong in dev subforum. There's Q&A subforum for that.

/me sent this on a i9250 using tapatalk
[Samsung Galaxy Nexus] Romanbb:
Yeah -- there are a few fixes you need to do, here are a few main ones:

https://github.com/TeamKang/external_gtest/commit/869a8876632f5bd17bf181930a6535b5c5084b94

https://github.com/TeamKang/frameworks_compile_slang/commit/cb818131815e8a4e608e3329addbc791ff3a5d82

https://github.com/CyanogenMod/andr...mmit/387c70bd952c033453fc99da1672fa40af837376

I think there may be one or two more, just google the errors you get
[Samsung Galaxy Nexus] EddyOS:
Just a quick question...

I've just compiled a ROM using the guide, got the binaries, etc. etc. but the build.prop from the resulting ROM had LOADS of random entries in it for LTE phones? and it's all singray as opposed to maguro. Have I done something wrong?
[Samsung Galaxy Nexus] shenye:
Yeah you've compiled it for the wrong device. I forgot to update the lunch menu bit, cos they added the xoom and the nexus s onto the list. You want full eng maguro. I'll fix it now.
[Samsung Galaxy Nexus] EddyOS:
Just realised that, option 4 in the lunch menu isn't the GN - it's 8 ;)

Rebaking
[Samsung Galaxy Nexus] EddyOS:
OK, correct ROM built this time. Compiled it as .IMG files so I could then get it into the kitchen but once the ROM has been rooted, etc. it won't flash - I get a Status 7 error mentioning the boot.img

Any suggestions?

P.S. The 8 in your guide is smaller than the rest of the text ;)
[Samsung Galaxy Nexus] shenye:
Probably a bad repack of the boot.img?
[Samsung Galaxy Nexus] EddyOS:
Not too sure, took the boot.img from a known working 4.0.3 ROM and still get the same error:

assert failed: write_raw_image("/tmp/boot.img". "/dev/block/platform/omap/omap_hsmc.0/by-name/boot")

E:Error in/sdcard/update.zip

(Status 7)

Installation aborted.
[Samsung Galaxy Nexus] EddyOS:
Fixed, dsixda updated the kitchen to extract the boot.img before flashing (which is why it was failing before)
[Samsung Galaxy Nexus] MR H3LLMAN:
That's quite strange then. It can't find the boot.img OR radios period. And at the end of the build it lists those 3 as missing and says skipping install.
[Samsung Galaxy Nexus] t3xboar:
Thanks but i already knew that :p

the issue, once again is not -how- to compile... rather how to re-convert the

non

make command.. the one that spits out .img files INTO a prepackaged OTA.

if you use make otapackage = flashable zip yes.. but a

clean unmodified

one only. it doesnt make modified ones....

if you use make then it spits out .img files.. thats fine because this is the files that make snod use to edit (as far as my understanding goes). so I can run make snod, whip up modified roms, have it recompile in 5 minutes only my changes:

But now im stuck with modified 5x .img files, and i want to take those modified ones and use them to make the flashable zip ! how?? lol... :D
[Samsung Galaxy Nexus] MR H3LLMAN:
I'll be on to this step later tonight so I'm looking for and answer as well now haha. What exactly does make snod do?
[Samsung Galaxy Nexus] t3xboar:
by all accounts it will compile only the changes you made, into the already sucessfull compile, previously done.

seems that it takes my system image, compiles whatever i changed, and spits out a new system.img.

so instead of taking 2-3 hours for minor changes, it will take 5 minutes
[Samsung Galaxy Nexus] MR H3LLMAN:
Wow. Reeeeeeaallly glad to have learned that one.
[Samsung Galaxy Nexus] MR H3LLMAN:
Alright, after quite a bit of digging, I bring you this:

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images

This is straight from Cyanogenmod's Wiki. It is Describing the process of unpacking, editing and re-packing the images. I think you will find this useful to SOME degree :D

On that note, would anyone be willing to expand upon this tutorial to include packaging boot and modifying and rezipping and so on?
[Samsung Galaxy Nexus] dave_t321:
If you're building from source why do you want to make modifications after compiling?

Surely the best way of making changes is to change the actual source code?

As mentioned above, as long as you don't "make clean" before you try to compile again, it won't re-do the whole lot, only the stuff you've changed. Should only take a few minutes (ymmv).
[Samsung Galaxy Nexus] t3xboar:
add in gapps package or pieces of it?? and SU and root?? you cant compile gapps from my understanding its a pre-packaged flashable zip... that is either included into the final package or a standalone. Hence the need to put it into the /out/.../apps and remake after... (if you have a different way of doing this then please let us know!)

and if you dont do make clean..hmm.. does that mean it works if you run the make otapackage, do edits, the re-run make otapackage (without doing make clean) it will take 5-10min to redo the changes and spit out a flashable zip ????

Thanks for clearing that up if you can.
[Samsung Galaxy Nexus] MR H3LLMAN:
On an unrelated note from the repacking I do believe I figured out my problem. My mkbootimg command isn't working properly. Can anybody tell me if there is something I need to do to make that functional?
[Samsung Galaxy Nexus] dave_t321:
Yes. Google "ccache", that makes rebuilds much faster too.

For the other bits, Superuser and the su binary are open source. Get it from the guy who made it:

https://github.com/ChainsDD

For gapps have a look at setting up a vendor tree. Some references to get you started:

https://github.com/peteralfonso/platform_vendor_pete/

https://github.com/AOKP/vendor_aokp

You could use the vendor tree to copy a prebuilt superuser.apk instead of building it from source if you wanted. su needs to go in system/extras though. You'll see where the old one is.

https://github.com/cyanogenmod is always a good reference too.

You may or may not need to do this to make it all work:

https://github.com/CyanogenMod/andr...dc0185ab98621f327ef62b/core/product_config.mk

https://github.com/CyanogenMod/android_build/commit/c40f78e8a8c7aaded661d54fb830b48f7dda26ec
[Samsung Galaxy Nexus] t3xboar:
Hmm thanks dave! lots more info to pour over.

I'll give this a try after, stick around in case some problems arise :p

should be good though, much appreciated! ;)
[Samsung Galaxy Nexus] beekay201:
well.. I believe my otapackages all have (most of times!) stock ramdisks included. Never encountered that issue before, about nothing like that. Will read further on your particular issue, maybe I can help out more.

From what i understood, he wants to use a custom ramdisk, hence the need to use TARGET_PRODUCT_BOOT, something like this, I'm not sure right now what makefile it's on and if this is indeed the correct variable to make, I'll try to search for it when I can, and edit this post with an update if needed.
[Samsung Galaxy Nexus] MR H3LLMAN:
Thanks in advance! I've tried everything I can think of or find...
[Samsung Galaxy Nexus] raiderep:
I'm taking a Linux class in college and it gave me the confidence to try this again. Before all my trials seemed like cut and paste with no knowledge of what the commands are actually doing so I always lost interest and got overwhelmed. Armed with this new skill set (still in it's infancy) I am syncing my repo right now to my Linux only laptop. Thanks for this guide and go android!

Sent from my Nexus S 4G

Edit: Took 1.5 hours to sync, building now....

...and still building 3 hours and counting...
[Samsung Galaxy Nexus] Serious_Beans:
No private recovery resources for TARGET_DEVICE crespo

make: *** No rule to make target `out/target/common/obj/PACKAGING/public_api.txt', needed by `out/target/common/obj/PACKAGING/checkapi-last-timestamp'. Stop.

Anyone know how to fix this?
[Samsung Galaxy Nexus] raiderep:
So my first build ended up finishing in 5 hours with no errors but I did something wrong. It booted up but was that off orange color theme and the launcher force closed endlessly but its good experience. I think I left out the part about cloning and extracting from my device. Second build worked fine and took 1.5 hours less, I used make -j4 otapackage, not sure if that is why it went faster or not. I also extracted from my device and cloned a github and its working great so far. No gapps but I used cm9 latest and think I'll use it all day tomorrow for further testing.
[Samsung Galaxy Nexus] sonicxml:
It probably went faster because the -j_ allows you to use multiple cores/threads when building it. The convention is to do the number of cores in you computer (or if its hyper threaded whatever it gets hyper threaded up to) +1 so if you had a quad core with no hyper threading it would be -j5
[Samsung Galaxy Nexus] raiderep:
OK thanx, I read it was twice the cores you have and my laptop is dual thus the -j4. Either way it worked a little faster and boots, still using it after rooting and adding gapps. Time to learn how to add fixes in now, message app wont download mms and browser won't dowload either, all known issues with workarounds I just need to see how they were fixed. This is pretty cool running an os built on my lappy :cool:
[Samsung Galaxy Nexus] beekay201:
I have a quad core, and I use -j8.

edit: you can also pass the -j1 argument to 'repo sync', let's make sure we don't hammer our machine just to resync trees. also, i think the default is -j8, cyanogenmod defaults to -j4, and i was told/read that 'repo sync' also hammers the remote side as well.
[Samsung Galaxy Nexus] beekay201:
make installclean

repo sync -j1

edit: On another subject, anybody sucessfully built SEAndroid support? Seems i can't clone git://git.selinuxproject.org/~seandroid/ to get some of the required projects, as there have been commits on gerrit that i would like to try.
[Samsung Galaxy Nexus] chocop:
Gran tutorial;@/
[Samsung Galaxy Nexus] MrTechnikron:
question

how can you add custom settings and mods that other people have made to the rom? obviously giving them credit.
[Samsung Galaxy Nexus] balban:
The best guide for this is the one on source.android.com. I suggest don't use any other guide.

Don't forget to extract vendor binaries *before* doing the build. That means the Samsung and IMGTEC binaries. This will save you time.
[Samsung Galaxy Nexus] Perka:
Hi followed your guide and started a build for crespo and it ran for 30min or so and I got this error.

http://pastebin.com/VQDBXMyD

what did I do wrong?
[Samsung Galaxy Nexus] 4ftermath:
So essentially, if I followed these steps exactly, I could end up with my own stock 4.0.3 odexed ROM?
[Samsung Galaxy Nexus] mbroeders:
Indeed! Follow these steps and you'll have your own rom up and running in no time :)
[Samsung Galaxy Nexus] foureight84:
How do you include gapps during compile? PRODUCT_COPY_FILES seems to be a deprecated feature; make throws an error.
[Samsung Galaxy Nexus] beekay201:
BUILD_PREBUILT is what you need

from

Android.mk
[Samsung Galaxy Nexus] dave_t321:
You could also revert this:

https://github.com/android/platform_build/commit/6886410210277294165dd9de95c7a56ce62547ac

Not really sure why it's enforced in the first place but it seems to work for me..
[Samsung Galaxy Nexus] foureight84:
Do you know which specific apk file is responsible for adding the google option under account & sync?
[Samsung Galaxy Nexus] MrTechnikron:
i built my rom but i dont know were to find it and get it out.

i think i found it in the root directory but i cant take it out. can someone help me?
[Samsung Galaxy Nexus] foureight84:
Another weird problem I came across. After building my custom device, I run lunch customdevice then emulator, it runs fine and is actually pretty fast. But I have no internet connection, no 3G emulation.

I assume this is because I used

TARGET_NO_KERNEL := true

in my custom device's BoardConfig.mk

I did a rebuild with reference to the goldflish kernel directory in prebuilt/android-arm/kernel/ that is, moving that directory to vendor/company/customdevice/kernel but make errors out halfway through the build with this message:

Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
5 warnings
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

Tried moving a fresh build goldfish kernel as well. I'm not entire sure if I am even doing this correctly. Reading on some posts I saw that people have also referenced TARGET_PREBUILT_KERNEL with the make call and pointing it to the goldfish zImage. I can't get that to work either :(

I really appreciate if you guys can give some points. I'm fairly new at this and I've tried following the kandroid guide (which i think is a mirror of the guide google had up on how to build aosp for a custom device) but it's way too hairy to follow and trace what exactly I'm doing wrong.
[Samsung Galaxy Nexus] Perka:
Hi, how do I run the rom in emulator?

Also I cant make sdcard for emulator.

Any help is very welcome.

Thx.
[Samsung Galaxy Nexus] MS.:
"/root/ICS_SOURCE/out/target/product/maguro"

If you've used build command "make -jX otapackage" then in above mentioned directory you'll find "full-maguro-ota-eng.root.zip" package. All .img files will be there is well.
[Samsung Galaxy Nexus] MS.:
Please delete.
[Samsung Galaxy Nexus] GrandMstrBud:
Doesn't work

E: Malformed line 54 in source list /etc/apt/sources.list (dist parse)

I get that in the first set of steps every time
[Samsung Galaxy Nexus] MS.:
It works, i've compiled ROM this morning and now using it. Be more detail: on what step exactly you get that error? Which distro you're using? Show us your sources.list (or at least line 54).
[Samsung Galaxy Nexus] GrandMstrBud:
ubuntu-10.04.4-desktop-amd64.iso installed with VMWare. I go to the terminal and type sudo -t and then my password. I then type

add-apt-repository "deb http://archive.canonical.com/ lucid partner" and no error there it goes back to the command prompt. And when I type apt-get update that's when I get the error of E: Malformed line 54 in source list /etc/apt/sources.list (dist parse).
[Samsung Galaxy Nexus] MS.:
It should be: sudo -i

Can you show me what's on that line 54? Perhaps there's some typo is well.

Anyways, i believe you'll get stuck at problem that i had (on 10.04.4) - Sun Java JDK. After issuing command "apt-get install sun-java6-jdk" and i was getting something like "package has no installation candidate" or something like that. After doing some research i found an article saying that Sun Java has been removed from repositories due to some licensing crap. I'm not too sure if it's true, but i've spent few hours last night on this with no results. I tried to install Open Java JDK (that is on Canonical repos), but then i stuck after command "source build/envsetup.sh". There was error saying that i use incorrect version of Java.

That was enough for me, so i just downloaded Linux Mint 10 (64bit) which is based on Ubuntu 10.10 and then all process went smooth (well, with minor issues but these were easy to fix).

PS. i've done this on actual PC, not VM.
[Samsung Galaxy Nexus] GrandMstrBud:
That's what I meant sudo -i. I don't think it was a typo because copied and pasted and as soon as I do the I type "apt-get update" that's when I get the error.
[Samsung Galaxy Nexus] MS.:
Ok, let's try the other way. Open Terminal and copy-paste this command and enter your password when asked:

gksudo gedit /etc/apt/sources.list

Basically this will open sources.list file in text editor. Now hit CRTL+A buttons on your keyboard (this will select all text).

Open any web browser you have installed (Firefox?) and go to http://pastebin.com/

Click on "New Paste" field and press CRTL+V buttons (this will paste previously copied text).

Click on "Submit" and share the link with us. We really need to see that line 54 on your sources.list file :)
[Samsung Galaxy Nexus] GrandMstrBud:
Here you go

http://pastebin.com/66ZmCaJk
[Samsung Galaxy Nexus] MS.:
Ok, that's last 8 lines of your sources.list file:

deb http://archive.canonical.com/lucid partner
deb http://archive.canonical.com/lucid partner
deb http://archive.canonical.com/ lucid partner
deb http://archive.canonical.com/ lucid partner
deb http://archive.canonical.com/ lucid partner
deb http://archive.canonical.com/ lucid partner
deb http://archive.canonical.com/ lucid partner
deb http://archive.canonical.com/ lucid partner

Do again:

gksudo gedit /etc/apt/sources.list

Now scroll to the very bottom of that list and you'll see above shown lines. Delete them all (your list is much longer, delete only last 8!) and paste this one:

deb [URL]http://archive.canonical.com/[/URL] lucid partner

Save file and:

sudo apt-get update

Should be good now, try to follow this guide where you have stopped. Let me know if you'll get stuck where i got (on installing Java).
[Samsung Galaxy Nexus] GrandMstrBud:
That all worked now up to step 4 which looks pretty confusing I will admit. I think I'm going to call it a night because it will probably take an hour to download. So will this even have gapps in with it? I apologize I have not read each and every post but most of them and seen this asked but don't think it was answered.
[Samsung Galaxy Nexus] MS.:
Step 4 is very easy. Basically you'll have to download two files (i'd post direct links but not too sure which version of GN you have) and extract them with archive manager (it comes with Ubuntu by default). You'll get another two files with .sh extension. That's it.

The longest step is nr3, as you'll have to download over 6 gigs of source code. BTW, in this guide step3 tells us to type

repo sync

But on other guides i saw

repo sync -jX

Where X is amount of CPU cores yo have. I haven't tried that but if it could speed up step3 i'd be very happy.

GAAPS won't be included here. A few pages back bk201doesntexist posted some explanation on how to include them. To be honest i never bothered myself with that and simply used the ones from CM9 as they're pretty much up to date.

After flashing your new ROM you'll find out that the camera isn't working and good few other issues :rolleyes: But, later on that. Let's see first if you can go trough last step - compiling.
[Samsung Galaxy Nexus] GrandMstrBud:
root@paul-ubuntu:~/ICS_SOURCE# source build/envsetup.sh

-bash: build/envsetup.sh: No such file or directory
[Samsung Galaxy Nexus] foureight84:
EDIT: NVM that's strange. chmod +x build/envsetup.sh ?
[Samsung Galaxy Nexus] GrandMstrBud:
root@paul-ubuntu:~/ICS_SOURCE# chmod +x build/envsetup.sh

chmod: cannot access `build/envsetup.sh': No such file or directory

root@paul-ubuntu:~/ICS_SOURCE#
[Samsung Galaxy Nexus] Sleuth255:
When you did your "repo sync" were you in the ICS_SOURCE directory?
[Samsung Galaxy Nexus] GrandMstrBud:
Last night. I went through the steps and did it again and same error
[Samsung Galaxy Nexus] MS.:
sudo -i

cd /root/ICS_SOURCE

source build/envsetup.sh

If you followed this guide and made no typos it has to work.
[Samsung Galaxy Nexus] GrandMstrBud:
I thought for sure I was in the ICS_SOURCE directory. Doing a repo sync again and now it's downloading. So who knows maybe I wasn't. This is pretty confusing I'm a windows user and when it comes to command line I am not good at all.

Looks like it's about to start compiling. I seen the post about putting in gapps and that's far over my head. This will probably take a while so I'll check back.
[Samsung Galaxy Nexus] GrandMstrBud:
It looks like it finished but I have no idea where the file is. I did a search for it and it didn't find it. The file name is full_maguro-ota-eng.root.zip

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

done.

root@paul-ubuntu:~/ICS_SOURCE#
[Samsung Galaxy Nexus] MS.:
gksu nautilus

Then navigate too: /root/ICS_SOURCE/out/target/product/maguro/

There you'll find freshly cooked ROM: full_maguro-ota-eng.root.zip
[Samsung Galaxy Nexus] GrandMstrBud:
There she is. After all that I feel like I should flash my phone to it. I am sure glad I'm not a programer or developer. Thanks for the help and I'm sure my questions seemed pretty dumb. So are the official updates that come via OTA do they have the gapps built in?
[Samsung Galaxy Nexus] MS.:
No no, you're alright. Sometimes it's easier to understand my wife then Linux :D

Emm, i don't think you can use OTA's when using AOSP ROM. But i'm not 100% on this as i always update my phones manually.
[Samsung Galaxy Nexus] GrandMstrBud:
Just for the fun of it I went to try and create a build for the Nexus S and followed the guide and got the correct binaries and went to compile and it didn't go through and do it's thing.

Which would you like? [full-eng] 7

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=4.0.3

TARGET_PRODUCT=full_crespo

TARGET_BUILD_VARIANT=userdebug

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

HOST_ARCH=x86

HOST_OS=linux

HOST_BUILD_TYPE=release

BUILD_ID=IML74K

============================================

root@paul-ubuntu:~/ICS_SOURCE#
[Samsung Galaxy Nexus] MS.:
Have you tried to clean building environment before compiling ROM for different device?

sudo -i
cd /root/ICS_SOURCE
make clean

BTW, have you flashed previously cooked ROM on your Nexus?
[Samsung Galaxy Nexus] GrandMstrBud:
Right now I'm running CM9 nightly with no issues. I more less did this to learn how so I have not flashed the newly created one. I'll try to clean that and see how it goes. This gives me a little learning experience and passes time when at work. Oh BTW it's building now. Have you flashed the OTA that it creates? I kind of want to try it but I'm sure I'll stick with CM as I love their ROM's.
[Samsung Galaxy Nexus] beekay201:
you misunderstood him; what he was asking was if OTA updates have gapps included.

I can't comment on that, never did receive an OTA update neither do I want to. (not sure what the fuss is all about OTAs anyway)

---------- Post added at 06:31 PM ---------- Previous post was at 06:15 PM ----------

after lunch, you need to pass

'make -jX otapackage'