yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] adrynalyne:
AOSP sticks in a generic fingerprint based upon build numbner and ID. Maguro is not in the market fingerprint system. Nothing is wrong with yakju's fingerprint...if you used it originally. Keep in mind Build ID is another thing that some apps will look for. Simply replacing the build.prop from yakju won't fix it without removing existing market data, I don't think. Did you clear data on the market after replacing? Do a data wipe?
[Samsung Galaxy Nexus] irisgl:
OK, let me say what I did. I tried different things. After replacing the build.prop on the phone I cleared the cache, data and stopped googleservices, cleared the data and stopped the Market. Ran the Market and after receiving the connection error rebooted the phone. It didn't help.

Then I changed the system.img. I've put yakju build.prop into out/product/maguro/system/ folder and did 'make snod'. Flashed the image (all flashes with fastboot flashall using -w option) and it did not help also.

Then I changed the build id and other parameters in mk files in order to generate as close to the yakju build.prop as possible. I even changed full_maguro to yakju and build the system image for yakju-user containing exactly the same fingerprint as yakju one. The only difference was test-keys instead of release-keys. It didn't work also.

Than I replaced out/product/maguro/system/build.prop to the yakju one (in order to get rid of test-keys in the fingerprint), make snod and it didn't work.

It's a reason why I asked do I need finally to sign the build with release keys to make it working?

Then I synced the master version which is I beleive IMM76D (4.0.4.0.4.0.4) into the separate folder and did the same tricks with it. It didn't help.

What else?
[Samsung Galaxy Nexus] beekay201:
I believe you need something like this

in your build.prop. if it still doesn't get you there, then the apps don't support ICS or maguro itself.

Anybody seeing this when turning off wifi (on master branch)?

It "lags" pretty bad, to the point that i can manage to, after switching the toggle off, back out of the settings menu, open it again, and still see the toggle ON.

I don't understand why this last part is even here:
[Samsung Galaxy Nexus] adrynalyne:
BT and wifi are the same chip.

I am.curious how you got around the graphical glitches on open master?
[Samsung Galaxy Nexus] beekay201:
Graphical glitches? :confused:

If after turning off wifi, I try to connect again to the same network:

but it doesnt connect at all. I have to forget the network and reconfigure it for wifi to connect again. or reboot.
[Samsung Galaxy Nexus] adrynalyne:
Yeah, check the market.

There are graphical glitches on OpenMaster. (I know it not me because others have tried ;))

Wish I had an answer for your wifi ills, but I am not sure.
[Samsung Galaxy Nexus] beekay201:
Oh, that. Yeah, I've been facing that since 4.0.2>4.0.3, i know what you mean. Never did manage to find out why that happens.

Not using google services now, bare aosp only, i forgot about it.

Seems to me that background color is switched to black, but text remains black.

Sent from my i9250
[Samsung Galaxy Nexus] shenye:
Yeah...I can see that being the issues that's causing errors :P
[Samsung Galaxy Nexus] EddyOS:
Still not working, getting same error, even though the update-script is now:

assert(package_extract_file("boot.img", "/tmp/boot.img"),

write_raw_image("/tmp/boot.img", "/dev/block/platform/omap/omap_hsmmc.0/by-name/boot"),

delete("/tmp/boot.img"));

Change it to this (as per Paul O'Brien's MCR) and it works:

package_extract_file("boot.img", "/tmp/boot.img");

run_program("/sbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");

delete("/tmp/boot.img");
[Samsung Galaxy Nexus] TulpiX:
I got it to compile thx for the tutorial

i chose to compile to get an .img file

but i have a question:

how would you add files to or delete files from (or directories) the .img file ?

thx
[Samsung Galaxy Nexus] scratch42069:
I'd also like to know how to go about modifying after everything has been built. I currently have 4.0.3 pulled and built on 20/12/2011 and as far as I know it built successfully because it didn't error out and everything appeared in the out folder.
[Samsung Galaxy Nexus] xHausx:
I can see you're point with Q&A but when it comes down to it the whole point of this site is to share stuff you've created with others. Q&A is more for people to ask questions while development is for those who want to share something they've done. Although, I do wonder why the OP didn't host it on XDA instead? :p
[Samsung Galaxy Nexus] gabrielperroni:
Great Tutorial!
[Samsung Galaxy Nexus] melterx12:
I can't seem to find the radio binaries for the VZW Galaxy Nexus, does anyone know where I can get them?
[Samsung Galaxy Nexus] RogerPodacter:
You mean modifying code? Once you compile the stock AOSP code, now you can go into whatever file or driver etc, make the code change and compile and it will only compile the new change making it much quicker to compile. I'd there was a problem with your change you may error or get warnings.
[Samsung Galaxy Nexus] TulpiX:
I think he meant the same as i did.

Not modifying code but if you have a compile .img file, how do you add or remove files or directories from it ?

or more global where do you go from there ?
[Samsung Galaxy Nexus] nprussell:
I can't believe Shen kanged my guide and claimed it as his own. -_-

(I'm just trolling)
[Samsung Galaxy Nexus] scratch42069:
That's exactly what I wanted to know, thank you. I didn't want to have to rebuild the entire 4.0.3. pull for something minor. I'm also glad to know my build is most likely good because there were no errors during compile.
[Samsung Galaxy Nexus] shenye:
Not sure, I have sent a message to an AOSP dev to see if there should be or if it will work without them.

EDIT: Seems there are still licensing issues between Samsung and Verizon that need to be sorted before the CMDA/LTE binaries get released.
[Samsung Galaxy Nexus] gferen:
great tutorial. one question maybe is not for this section.

if i want to compile any other version of android? lets say 2.3.7 for example.

i am noob in this things :)
[Samsung Galaxy Nexus] shenye:
you want to initialise the repo for the 2.3.7 branch. So instead of 4.0.3_r1, you want 2.3.7_r1
[Samsung Galaxy Nexus] :
i like this tutorial but can this be mimic for the sk4g?
[Samsung Galaxy Nexus] gferen:
so this should be command

repo init -u https://android.googlesource.com/platform/manifest -b [B][I]android-2.3.7_r1[/I][/B]
[Samsung Galaxy Nexus] shenye:
Yes, if you can find the repo for the source code for it.
[Samsung Galaxy Nexus] :
Ok what is the repo (sorry about being a noob) I have jdk6 installed and ubuntu 11.10 also
[Samsung Galaxy Nexus] shenye:
You need to sync up the repository for the correct source code.
[Samsung Galaxy Nexus] :
which would be found ? (thanks in advance)
[Samsung Galaxy Nexus] adrynalyne:
They aren't just resource changes. There are actual skia commits that can be reversed. The last time I messed with it was on 4.0.3 though, and there have been a GRIP since then.

I just wanted to keep the skia commits and use OpenMaster. However, if you revert enough, you just end back at IMM76L. I was hoping you had a magical fix for me :(

Oh well.

Regarding wireless...you have checked AOSP gerrit for wifi changes and tried tracking down which one might be causing you issue?
[Samsung Galaxy Nexus] GalaxyNexusPH:
Proprietary binaries

I extracted the marguro proprietary binaries. Where should the vendor folder go? Its in the root of my source folder. Is that correct?
[Samsung Galaxy Nexus] adrynalyne:
Yep.
[Samsung Galaxy Nexus] beekay201:
it has changed locations
[Samsung Galaxy Nexus] mwalt2:
I'm having trouble getting ccache setup for the jelly bean source. There are no ccache directorires at prebuilt/linux-x86/ccache/ccache after I downloaded the source. I get a no directory error when running 'prebuilt/linux-x86/ccache/ccache -M 50G'. Does anyone know why? I have added the export use and export path to my .bashrc and source'd it.

edit - haha, good timing bk201doesntexist :D
[Samsung Galaxy Nexus] anton2009:
Can someone help me out? I'm trying to build JB myself and my android version keeps showing up as 4.0.9.99.999.9999.99999. Is that normal?
[Samsung Galaxy Nexus] adrynalyne:
You are on master AOSP. Checkout the actual branch.

repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r1

repo sync
[Samsung Galaxy Nexus] anton2009:
Awesome. Thanks!

---EDIT----

Also another question. Why is it in the OP that it states to only initialize one repo. I have both the master AOSP and 4.1.1 branch within the same directory. If i try to build from this directory, will my build be messed up? Because when I synced just the 4.1.1 branch, and tried to make, it spit out a bunch of errors while when I compiled with the master AOSP it ended up with a build. So I decided to repo init and repo sync 4.1.1 within my original master AOSP directory. Is it bad to build from a directory which contains both master and 4.1.1?

---EDIT----

Yep. Nevermind. That didn't work either. Idk what I'm getting stuck on.
[Samsung Galaxy Nexus] sloppy1:
unable to get jdk6

ive tried this apt-get install sun-java6-jdk but its not getting it is there another way of getting it im new to linux,running version 10.04 any help would be most appriciated ,,, thx
[Samsung Galaxy Nexus] s2d4:
Did you use sudo?
[Samsung Galaxy Nexus] sloppy1:
was already in su sudo -i

---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------

i followed these steps sudo -i

Then type in your password. From this point forward, all of the commands in this guide assume you have root priviliges (saves typing sudo *superuser do* before everything!)

Next, we need to add a repository so that apt-get knows where to look for Java JDK:

add-apt-repository "deb http://archive.canonical.com/ lucid partner"

After that, you'll need to update the repository with the following command:

apt-get update

Now that your repository has been updated, you can proceed with installing the required packages to make building Android from source possible. The first thing you're going to need is the Java Development Kit 6:

apt-get install sun-java6-jdk6 it cannot find
[Samsung Galaxy Nexus] mattalter:
This worked for me

http://superuser.com/questions/394770/installing-sun-java6-jdk-with-apt-get-on-ubuntu-10-04

sudo add-apt-repository ppa:sun-java-community-team/sun-java6

sudo apt-get update

sudo apt-get install sun-java6-jdk

sudo update-java-alternatives -s java-6-sun
[Samsung Galaxy Nexus] beekay201:
it seems /system/recovery-from-boot.p doesn't exist on my system anymore; at least on a eng variant build flashed through fastboot.

can't find the file itself, and just tested flashing a recovery, start android from bootloader, reboot android again into recovery, custom recovery is still there.

although if otapackage is built, recovery-from-boot.p is there:

it's funny that i never noticed this. :D
[Samsung Galaxy Nexus] no.one.writeme:
Hi there!

I had the exact same problem because the sun-java6-jdk6 has been removed from the ubuntu repositories.

Luckily I have a Lmde ( Linux Mint Debian Edition ) and made use of the java-package available in debian to generate a java-jdk to install in 10.04 Lucid build environment.

Here's what you could do:

-Have a LMDE install in a virtualbox

-In that environment do:

-- apt-get install java-package fakeroot

-- download java-jdk from oracle

-- fakeroot make-jpkg <java-binary-package-name>.bin

- apply the resulting file in 10.04 Lucid build environment

- do update alternatives

-- update-alternatives --config java

-- update-alternatives --config javac

-- update-alternatives --config javaws

- confirm that the installation is ok with: java -version

I suggest that you also enable the backport repositories so that you can install the lts-backport-oneiric 3.0.0-23 kernel.

With it you get better hardware support.

Hope this helps!

Best regards.
[Samsung Galaxy Nexus] sloppy1:
ill try this,thx
[Samsung Galaxy Nexus] mattalter:
Help with copy of file from root

I have finished compiling it. But the zip is in the root folder. How to I copy it out of there.

I have tried using gksudo nautilus but I sitll don't have permission to copy the file?
[Samsung Galaxy Nexus] beekay201:
Why didn't you build as a normal user?

Open a terminal, 'sudo cp /root/android_tree/out/target/product/maguro/full_maguro-ota-root.zip /home/your_username/'

After that finishes, 'sudo chown your_username full_maguro-ota-root.zip'

Should be good now to work as normal user.

Sent from my i9250
[Samsung Galaxy Nexus] patric.f:
Hi,

I'm trying to compile on a FreeBSD machine but I get this error:

[patric.f@bsd ~/android/]$ lunch

You're building on FreeBSD

Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. full_grouper-userdebug
5. mini_armv7a_neon-userdebug
6. mini_armv7a-userdebug
7. full_wingray-userdebug
8. full_crespo-userdebug
9. full_maguro-userdebug
10. full_panda-userdebug

Which would you like? [full-eng] 9
make: illegal option -- -
usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
[-d flags] [-E variable] [-f makefile] [-I directory]
[-j max_jobs] [-m directory] [-V variable]
[variable=value] [target ...]

** Don't have a product spec for: 'full_maguro'
** Do you have the right repo manifest?

Trying to build for Galaxy Nexus GSM, do I miss some software or anything?

I had some trouble extracting the binaries, I had to manually extract them like this:

tail -n +276 extract-samsung-maguro.sh > samsung.tgz

And the extract the archive for all the binaries. I then placed the 'vendor' directory in the root directory of the JB source, ran 'lunch' and got that error..

What's wrong here?

Thanks for any help here.
[Samsung Galaxy Nexus] mattalter:
Thanks I got it copied.

---------- Post added at 12:20 PM ---------- Previous post was at 12:17 PM ----------

Ok, so I have a base aosp build. Its missing some things I know.

Gapps, which I found and leaning how to inject into my build

Camera, which does not work.

Is the camera just a permission wipe issue to get it working?

Thanks

Matt
[Samsung Galaxy Nexus] HumanXv2:
Can this be done without a hassle on ubuntu 12.04 or would 11.04 better? Im fixing to install one or the other on a spare partition on my hdd
[Samsung Galaxy Nexus] :
I just built 4.1.1 for toro on 12.04 x64. Only problem I had was installing JAVA. I installed it this way:

- Download oab-java.sh from https://github.com/flexiondotorg/oab-java6

chmod +x oab-java6.sh
sudo ./oab-java6.sh

Then run:

sudo apt-get install sun-java6-jdk
[Samsung Galaxy Nexus] adrynalyne:
For those who care, I just built Android 4.1.1 with gcc 4.7. No modifications were needed.

http://pastebin.com/YjsDrLj0
[Samsung Galaxy Nexus] HumanXv2:
Im up and running on 11.04 and have done the tutorial step by step but when add the repo for the source it doesnt work

curl http://android.git.kernel.org/repo > ~/bin/repo gets me BASH blah blah/blah is a directory

pretty much anything after those steps will not work
[Samsung Galaxy Nexus] molesarecoming:
so to build it on 11.04 r1 needs gcc-4.4? im sitting on it for two days in row, havent managed to get it either compiling or running, i gave up on 12.04 after getting weird proguard errors in the end and installed 11.04. now im reading again that people experienced build issues. when i use the workaround via 4.4 will this have any bad sideeffects, less optimized code for instance?

i just feel like the further down the foodchain the more crappy ubuntu gets. 10 was terrible, 11 bearable, 12 ok. i so wish i could build it on win7, linux makes me nuts. :(
[Samsung Galaxy Nexus] beekay201:
Needs camera binary.

Anybody feeling the higher drain?

Sent from my i9250
[Samsung Galaxy Nexus] cougar618:
Can someone point me in the right direction? I got it to compile and install, but camera is broken (seem this several times in this thread), I don't know where to get Gapps for JB (and if possible, I'd like to include it in the ROM) and from what I've seen, I'm assuming there's a GPS binary I'd need as well. I was hoping someone could point me in the right direction, where do I get these binaries, and how would I get gapps installed by default.

On a related note, it only took me 7 tries to get this to work - 3 tries was trying to save the out/ to an NTFS part. one was me trying make -j, which crashed 30 min in, the 6th, I got it working but then learned about the binaries I didn't include.
[Samsung Galaxy Nexus] sjoerd0301:
Hey guys gotta question,

Nobody was able to answer it, so i trie it here...

Q:

How to build a rom for a device that is NOT in the google source tree? The gsm version of the htc shooter(shooteru) in my case got the device tree from Cyanogenmod git. But it is not recognized in the repo, it keeps telling me that the device is not found in the manifest file. What to do now?
[Samsung Galaxy Nexus] adrynalyne:
For those seeing compiling errors on stock Jellybean (and it worked fine for ICS on the same OS and compiler version), take a look at the tree you are on. You need to be on 4.1.1 branch.
[Samsung Galaxy Nexus] HumanXv2:
c@c-MS-7599:~/bin/repo$ sudo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r1

init: invalid option: -u

Try `init --help' for more information.

c@c-MS-7599:~/bin/repo$ sudo init https://android.googlesource.com/platform/manifest -b android-4.1.1_r1

init: invalid option: -b

Try `init --help' for more information.

c@c-MS-7599:~/bin/repo$ sudo init

init: missing runlevel

Try `init --help' for more information.

c@c-MS-7599:~/bin/repo$

???
[Samsung Galaxy Nexus] adrynalyne:
repo init -u

You need to use the repo program to pull the files. sudo is for elevated permissions.
[Samsung Galaxy Nexus] HumanXv2:
c@c-MS-7599:~/bin/repo$ sudo repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r1

sudo: repo: command not found
[Samsung Galaxy Nexus] adrynalyne:
Head back to the OP for instructions on how to compile. Looks like you missed a step.
[Samsung Galaxy Nexus] HumanXv2:
I dont have anything to compile. all this problem is trying to get the repo installed. 2 days now =(
[Samsung Galaxy Nexus] beekay201:
This is how you install repo:

From OP, like adrynalyne told you:

Just saw your post earlier:

you're try to get repo from somwhere that doesn't exist anymore. If you paste it into your browser's adress bar, you'll see that it goes to a NOT FOUND host, redirected to a Google server, which then displays

This is what you need to do:

from http://source.android.com/source/downloading.html

If people didn't take one source of information for granted, you would have found this out already, instead of knocking your head against the keyboard for days.
[Samsung Galaxy Nexus] HumanXv2:
I done that exactly as it says and I get the same thing

c@c-MS-7599:~/bin/repo$ sudo curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo

bash: /home/c/bin/repo: Is a directory

c@c-MS-7599:~/bin/repo$

i take off the > ~/bin/repo and it acts like it does something but when I enter the init line I get repo isnt a command and something about runlevel

I have added everything to path
[Samsung Galaxy Nexus] adrynalyne:
Ok, you are getting into a really bad habit here.

STOP with the sudo. You are going to screw up your permissions left and right.

Don't install local apps (like repo) with sudo. Don't compile AOSP with sudo.

That said, do this:

rm -rf /home/c/bin/repo

Then run the command again.
[Samsung Galaxy Nexus] HumanXv2:
Permission Denied...

Thanks for helping me btw
[Samsung Galaxy Nexus] beekay201:
You have a folder named repo inside folder ~/bin. Rm -f it like adrynalyne said.

This is why sudo is a bad idea. It seems to me that some people were mislead to believe that it solves everything, thus everything should be run with sudo. I prefer switch user, or substitute user (some call it that), when escalated permissions are really needed.

Again, probably because you used sudo before to create that dir.

Do

then you can
[Samsung Galaxy Nexus] HumanXv2:
c@c-MS-7599:~$ rm -rf ~/bin/repo/

c@c-MS-7599:~$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo

bash: /home/c/bin/repo: Permission denied
[Samsung Galaxy Nexus] adrynalyne:
Looks like you need to repeat the above steps we gave, but this time, kill off ~/bin as well.

Then recreate it without sudo:

mkdir ~/bin
[Samsung Galaxy Nexus] HumanXv2:
Thanks a whole lot guys=)

probably a dumb question but on the colorized output part does it matter what color?
[Samsung Galaxy Nexus] adrynalyne:
No, personal preference.
[Samsung Galaxy Nexus] adrynalyne:
So is repo all squared away now?
[Samsung Galaxy Nexus] beekay201:
I hope so :)

Thank you for a well done troubleshooting, adrynalyne. ;)

Sent from my i9250
[Samsung Galaxy Nexus] adrynalyne:
Thanks for posting the chown info! :)
[Samsung Galaxy Nexus] HumanXv2:
yep its downloading now, thank you very much guys. I usually stop messing with linux when it starts giving me grief and log back into my win7 partition which aggravates me in other ways but I'm bound and determined to learn linux so I can use it daily. Can this all be easily transferred to my laptop after it gets done so I can mess with it at work?
[Samsung Galaxy Nexus] adrynalyne:
Yeah, but once moved over to your laptop, you must chown the entire source tree.
[Samsung Galaxy Nexus] CdTDroiD:
Anyone got alternative command for installing sun java 6? Doesn't work anymore and having issues building with openJDK. Why did I have to reinstall Linux lol
[Samsung Galaxy Nexus] Know-Fear:
follow this guide for java install.

http://ubuntuguide.net/install-sun-java-6-jrejdk-from-ppa-in-ubuntu-11-04

worked perfectly for me.
[Samsung Galaxy Nexus] veeman:
Is it possible to install Java 6 on 12.04? I've tried the ones posted in this thread but none of them work. I always get this.

Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.BcxNrSMcSG --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver hkp://keyserver.ubuntu.com:80/ --recv 3E756CF119B127D4DA40A186B725097B3ACC3965
gpg: requesting key 3ACC3965 from hkp server keyserver.ubuntu.com
gpg: key 3ACC3965: "Launchpad lffl" not changed
gpg: Total number processed: 1
gpg: unchanged: 1

EDIT: Never mind guys. I found a way to install. Followed the guide here. Link
[Samsung Galaxy Nexus] HumanXv2:
Okay I followed everything and got it downloaded and compiled. stuck at bootloader screen, no big deal. I was poking around the folders and looked at the build prop and it says 4.0.1 when I pasted the link for 4.1.1 r1...
[Samsung Galaxy Nexus] CdTDroiD:
Lol bugger. Must have entered it wrong at some point unfortunately. Try sync repo again and see how far it goes
[Samsung Galaxy Nexus] HumanXv2:
I did it again and it is showing the same things while downloading....new branch says ics-aosp then under that it sayd new tag android-4.1.1 r1
[Samsung Galaxy Nexus] CdTDroiD:
What version does it say just before you build?
[Samsung Galaxy Nexus] HumanXv2:
honestly I never noticed any build number # at that time. about half way through i came and sat down to watch it scrolling down the screen and noticed the ics-aosp part. I didnt think anything of it since other people have been doing from the op and I was sure someone woulod have mentioned it. I just did repo init -b android-4.1.1_1 and it looks different downloading this time around. This is my first time messing with this so I guess I'll make mistakes, but thats how you learn
[Samsung Galaxy Nexus] CdTDroiD:
For sure man, can be a pain in the ass but after the first few times its nothin no other way to learn properly
[Samsung Galaxy Nexus] HumanXv2:
I got the source downloaded(again) where do I look to make sure it is 4.1.1? I havent seen anything to say either way yet
[Samsung Galaxy Nexus] adrynalyne:
Check build/core/build_id.mk.
[Samsung Galaxy Nexus] HumanXv2:
Its right this time as far as I can tell.

Are the XML files present in source form where I can make UI changes before I compile it?