yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] shishir95:
I need serious help with this. I've been trying to compile this all day and I can't even get past the repo sync command... It seems to ALWAYS with-out fail get stuck at: "Fetching projects: 99% (310/313)" It used to succeed without the local_manifest.xml file, but obviously I need that file to get my device specific folders all in order, other wise the blank folders will not sync from the repo with their associated .sh files. Can anyone point me in the right direction? I've followed literally every bit of directions I've found and nothing so far.

Specifics: Ubuntu 12.04 x64 running inside of VirtualBox with all of the required switches and stuff turned on. 2GB of RAM and a 60GB Virtual HDD allocated specifically to that process. It's not much, but I can't dual-boot it right now. People have gotten builds to work on VMs so this shouldn't be a problem at all. I've used the Team Hacksung script to prepare my build environment, but I've installed the libraries and everything manually prior to that and it still didn't work. I'm using "repo sync -j3" if that makes a difference. I find it's the most stable number of simultaneous jobs, as the default -j16 tends to hang quite a bit on random parts of the process. I've configured VirtualBox to use a bridged adapter as opposed to a NAT since the NAT had some sort of time-out that was interfering with the sync process. I've also used the instructions on the Android Dev site to change my ipv4 settings. I can't remember off the top of my head specifically what those fixes accomplished, but apparently they fixed or attempted to re-mediate an issue that popped up "rarely" revolving around compiling on Linux. Didn't seem to help at all, but it's enabled anyway.

Several google searches lead to just re-initiating the repo and syncing until the problem fixes itself, which doesn't seem to occur with me since I've spent a few days on this with no change. I'm just so jealous of everyone with access to the latest fixes and builds merged into the repos while I have to sit here and wait for either codeworkx or entropy to publish a build... Besides how am I supposed to contribute if I can't even get the source downloaded

God nevermind I'm just impatient. Worked this time... somehow. If anyone else is getting the same problems, just take the amount of time you THINK you need to do ANYTHING on a virtual machine and multiply it by 5 and you'll have a reasonable estimate.
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
Have you tried "make clean" then try repo sync again? IDK about your network issues... I use VMware. But just of note, I did have mine fail out earlier today, but I just tried it again and it's fine. :silly:
[AT&T Samsung Galaxy S II SGH-I777] shishir95:
It's chugging along just fine right now, but I'm not taking anymore chances and will definitely clean after building. It seems like the safest way. Will anything bad happen if I don't, or is it just housekeeping?
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
Just housekeeping. :)

I'm OCD about make clean. Don't ask. :rolleyes:
[AT&T Samsung Galaxy S II SGH-I777] KevinChaos:
Every once in a while, my phone will disable data under mobile network settings by itself. Is anyone else experiencing this?

Edit: wrong thread. Damn you xda app.
[AT&T Samsung Galaxy S II SGH-I777] msgfromside3:
I have the same vm setup and I have not seen the issue so it must be external issue.

I am wondering how long the build usually takes from the physical machine though. I left it build last night but it was still going after 7 hours so I had to pause so that my wife can use the computer while I am working. Hopefully it does incremental build once I have a full build.
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
My God. 7 hours? Are you sure you have hardware virtualization enabled? My little 12" notebook with an i5 only takes around an hour and a half.
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
Yea you can build on device if you have Linux running on it, so on a tegra 2 for example with only a gig of ram in an hour or a little over. Granted with virtualization you need more HP on a PC but they have more HP so really it shouldn't take that long. Are you building with the -j flag -j so a quad core could do -j16... I'm not totally sure about the number maybe 12 but I'm pretty sure its 16 just Google it
[AT&T Samsung Galaxy S II SGH-I777] shishir95:
It's been a couple of hours... maybe 5 or 6 that I've been building. It's interrupted a few times but has picked up where it left off so I'm not entirely sure why it's taking so long. Just restarted it from where it left off with the -j16 flags. Maybe this'll help a little. Any one else with slow build experiences have any idea what I can do to speed it up?

Nevermind I found a fix. Tell VirtualBox to use all four cores instead of one lol
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Yep its -j16. I didn't use the flag the first time I pulled the repo and it took overnight to finish. Did a brand new setup last night and with -j16 it only took a couple hours to do it.. Now if I could only get around the hangups Mac OS X has and actually build it haha.
[AT&T Samsung Galaxy S II SGH-I777] kool2zero:
can you run the -jn command with build.sh? I know when I built for the nexus one ages ago, it used a brunch command
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
I don't think so. The flag is a make argument so you would need to add it to the line that calls make in the build.sh script. I'm used to the good old configure/make process so I'm still wrapping my head around it myself. It doesn't help that one guide tells you use brunch, one tells you build.sh and the CM wiki actually gives you a make command to use..
[AT&T Samsung Galaxy S II SGH-I777] shishir95:
Yep. Just used it.
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Awesome that will come in handy when I get home hehe.
[AT&T Samsung Galaxy S II SGH-I777] shishir95:
Okay guys now I'm having another problem. Whenever I connect my phone to my laptop via USB after installing my KANGed CM10, I get a force close for android.process.media and a logcat shows an IllegalArgumentException being thrown at com.android.providers.media.MtpService... anyone else experiencing this? MTP was working in the build Entropy512 posted in the General forum. Did I mess something up? Seems like my sdcard isn't getting mounted no matter what. Neither the internal nor the external. Gallery isn't showing anything either.

EDIT: Turns out I was right. All of the logcats i've pulled are making it clear the phone has no idea what /mnt/sdcard is. Any idea on how to fix this? I'm pretty sure it's local to my build
[AT&T Samsung Galaxy S II SGH-I777] kool2zero:
took 64 minutes my my virtual machine on my work laptop
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
Well if you copied entropy's code verbatim and then built it, there are few things that could go wrong. First the proprietary files you pulled could be bad... though unlikely or its hardware. Check with the sdcard removed or with a different freshly formated one. Is point you to init.rc/goldfish or vold.fstab to make sure everything is mounting properly. This is all assuming entropy is committing which I believe he is.
[AT&T Samsung Galaxy S II SGH-I777] diabolicalangle:
I can confirm this on the build I built today (took 2.5 hours yikes)

Edit:.famous media scanner bug
[AT&T Samsung Galaxy S II SGH-I777] Fusion777:
Got my CM10 build working & running on my phone. Looks & runs great, not sure if I screwed up something though because the AOSP tethering screen is no longer available. Did I botch it up, or was it removed from the build? I didn't see anything in the BBQLogs...
[AT&T Samsung Galaxy S II SGH-I777] kool2zero:
Got this error while syncing this morning:

Fetching projects: 100% (313/313), done.
error: Your local changes to the following files would be overwritten by checkout:
i777/i777-vendor-blobs.mk
Please, commit your changes or stash them before you can switch branches.
Aborting

error: vendor/samsung/: TheMuppets/proprietary_vendor_samsung checkout 7660d005c6dae55cf43b5f1ad938b28980f283dc

I made no changes other than build, i also ran "make clean".
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
All make clean does is clears all precompiled files and rebuild them. See make is smart enough to see only changes when compiling and can reuse those files... however it isn't perfect, that is why some make clean. However, make clean does not return the downloaded files to stock. There is a chance that some files got corrupted on DL. Go to the browser got and DL only that file and replace it in your working directory, see if that fixes it.

Alternatively you can stash it and that will return you to stock as well. This would be the more proper way of doing it...

Run:

Git stash

Git stash drop

Don't use rebase
[AT&T Samsung Galaxy S II SGH-I777] msgfromside3:
I had the same issue. That was what I did to address it last night. I am interested in knowing why it happened, though.

BTW, back to 6 hrs for the build time, it took 2.5 hours to build from my laptop VM, so there must have been something wrong with my desktop VM. My desktop has better hardware and I didn't do anything special for both setup other than adjusting CPU and RAM. Maybe I missed something from BIOS - I haven't paid much attention as it is for the family use.

PS: Yeah, I was wondering how come Android takes longer than "make world" for FreeBSD 8 years ago. :)
[AT&T Samsung Galaxy S II SGH-I777] alejobog:
Entropy

you can change the phone.apk to display like this:

or so:

to make this space more functional, thanks
[AT&T Samsung Galaxy S II SGH-I777] MotoMudder77:
i got a mess on my laptop, anyone know the cause of this error at the end of my sync?

Fetching projects: 100% (310/310), done.
fatal: This operation must be run in a work tree
error: revision refs/heads/jellybean in CyanogenMod/android_device_samsung_galaxys2 not found
[AT&T Samsung Galaxy S II SGH-I777] stone_ship:
Can you post (or link to) the patch?

Might want to try that out in a build one day...
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
Well ginger was a lot smaller. Since ics ... well technically honeycomb, android had been very large.
[AT&T Samsung Galaxy S II SGH-I777] monkey hung:
.sad
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Since you didn't provide a patch, I can't. Submit it to gerrit, that is core code that is not device specific.

If it's a feature request - it does not belong in this thread, and also I'm a device maintainer. I don't mess with the core UI.
[AT&T Samsung Galaxy S II SGH-I777] sjwaste:
Great writeup, thanks!
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
I took care of it Nick - VeNuM
[AT&T Samsung Galaxy S II SGH-I777] onlychevys:
Quote:from XGX5309 For those interested, I've made a self-contained guide on how to compile CM10 for the GS2 i777/i9100. It's an amalgamation of drakester09's tips, along with steps from TeamHacksung and some I've added for convenience. From installing Ubuntu to making a flashable zip...

http://pastebin.com/EPbEtUjC

In the "local_manifest.xml" file created in the .repo folder in your tutorial can I change the teamhacksung to teamchopsticks if compiling for a hercules t989? Will that work? Great write up!!
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
Sorry, no. There's actually no commit under "teamchopsticks" Github for Jellybean on the Hercules. There's activity for the Skyrocket though, so maybe they'll start on the Hercules soon?

Teamhacksung doesn't cater to the Qualcomm devices. Only Exynos and Hummingbird (and an odd Epsilon Tegra kernel ?).
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I think he's trying to do a bringup of the Galaxy R. While it's possible at some point one of us will grab a Qcom device, it's highly unlikely.

Epsylon3's experiences with the Galaxy R remind us of why we don't touch Samsungs with alternative processors... You get typical Samsungisms PLUS all sorts of extra weird **** due to it being an architecture they're not familiar with.
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Just curious, when you run the ./proprietary-files.sh script, where does it actually store those files within the android/system tree??

Ive got my VMWare Ubuntu all setup and going but its not playing nicely with the whole 'cut and paste' and device sharing between my Mac and Fusion.

I got the entire environment ready to go, but when I connect my phone to USB, even though Ive told Fusion to pass it to Linux, adb cant see my phone to save its life to pull the files from it. I can still do it on my Mac, but from what I can tell, it puts them in both /devices/samsung as well as /vendor/samsung.

I copied both of those directories over (had to FTP to my Mac to get it to copy) and replaced the original ones, but when I try to sync the repo now I get errors. When I copied them over, Ubuntu couldnt copy any of the SVN files inside all the .git folders so I figured resyncing would put those back but nope..

Running into all kinds of errors during compiling so can anyone tell me any tricks to getting adb to see my phone inside VMWare???

Im assuming it works for everyone else??
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
I'm not using Fusion or OSX, but on the Workstation version you have this on the bottom right hand corner of your VM window. If you mouse over the icons it tells you which is what. You want to find one that says "Samsung Modem". Right click on it and let VMware capture that USB port I/O.
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
Its been a while since i actually did it but there is a target folder with the prop. files in it. honestly the easiest way... and the way i learned is to open up the .sh and read it. actually understand what it does...
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
~/android/system/vendor/samsung/i777
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Yeah that was my first step but all the directory names are variables so I just grabbed the vendor one hehe.

Mr XGX - yeah those buttons are at the top of the fusion window. I can get the phone connected via USB fine but no love on adbs end. Ill have to play with it more when I'm home from work. The integration between the Mac and VMWare is already being flaky so I may have messed something up when I set up the VM.. Go figure my WinXP VM works perfect but not my lovely Ubuntu!
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Arrgh this Android environment is tough hehe!

So I deleted the two folders I copied over from my Mac yesterday (devices/samsung, and /vendor/samsung) and resynced..

When it was done, since I still had the /vendor window opened, I noticed it had remade the samsung folder. Looking at it and comparing it to the folder on my Mac, it looks like this already pulled the proprietary files from github for me??? Is this possible??

Its got all the same contents as the one from my Mac which was pulled from my i777.

Still cant get my phone to be seen by adb on Ubuntu so I decided to build anyways, since it looks like its all there.

Im hitting this error repeatedly now:

"/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: cannot execute binary file".

So a little bit of research into the error and I ran across another JB thread with the same problem.

http://xdaforums.com/showthread.php?t=1762641

Apparently (and maybe you guys that made guides for building should update it) JB requires a 64bit host to build.

I screwed up and installed the 32bit Ubuntu (thinking this was the right version for a first gen pseudo 64bit Mac Pro).

So now apparently Ive got to start all over again. Although I dont get why my Mac, even though it failed in building, never ran into this error.

Sure I have 64bit Xeons in here but my Snow Leopard is 32bit, and my EFI is 32bit as well so I cant even run a 64bit kernel if I wanted to.. Never saw it on my Mac but in Ubuntu it pops up almost instantly after starting a build..
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
Well it switched over to 64bit back in GB I want to say. When ICS rolled around you could do it with 32 but you had to make a complete hack job of your box.... but it was do able... idk about jb
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
64-bit should be a given. Personally, I haven't run anything less than 6GB of RAM since ~2007, so 64-bit is the only way I can utilize my hardware. The thought never ran through my mind to add that little detail to the guide. lol. :silly:
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Yeah, I have 8 and I'm seriously thinking of adding 4-8 more just for filesystem caching during builds. My system hits swap way too often when I'm running builds.
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Got 64bit all setup, got rid of that klunky Unity and am off and running!

And go figure, this time my copy/paste/drag/drop is working perfectly between OS X and Ubuntu.

I mustve really screwed up the VMWare Tools install last time or something although I dont know how you can.

Either way here we go. Just finished the jdk install so time to grab the platform-tools and begin the grind of redownloading the repos!

Crossing my fingers that adb will see my phone this time!

(I should just turn my dual core G5 into a PPC Ubuntu box.. At least its got 8GB of ram in it)
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
It really does help. I have 16GB in my desktop. I have 4GB setup as a RAMDisk for random things and the rest is OS RAM. I think the main thing that helps with builds though is an SSD. Paging a platter drive during a compile slows things down almost to a standstill.

Oh... PPC. :/
[AT&T Samsung Galaxy S II SGH-I777] drakester09:
SSDs are absolutely recommended for this.

Also 64-bit is a must for a JB firmware compile - according to JBQ, learned this the hard way when I mistakenly set up a x86 VM and tried to build.
[AT&T Samsung Galaxy S II SGH-I777] sjwaste:
Make sure you gave that virtual disk a lot of space. I started with 30 gigs for a Ubuntu 12.04 VM and ran out of space mid-build. I had to bump up to 50. Resizing takes forever, so do it now before you start if you have to.

The VMWare tools are a pain in the ass to install if you're less experienced, actually. They rely on some of the build packages - you should have the kernel headers and build-essentials installed, possibly bison as well. Actually, the best time to install the VMWare Tools is AFTER you set up your Android build environment.

I'm building right now... Macbook Aluminum (2008) @ 2 GHz and 4 GB RAM. I don't have room for the VM on my SSD, so it's on my slow stock HD. Should take a few hrs, I'd have to think.
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
Yea, VM size needs to be a minimum of 50GB IMO. I usually do about 80GB... gotta have a little breathing room.

As for VMware Tools, I've never had an issue with them, but they aren't exactly user friendly.

If I build on a HDD it usually takes ~120-135 minutes on an i5-2520. Mainly because I'm always building from scratch (make clean). If you have prebuilts it shouldn't take that long.
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Uh oh. I ran out of 20gb on the 32bit one so I made this one 30. Better get out my gparted CD hehe. Might as well do it now. Repo sync is taking forever I probably could've just copied the .repo folder from my Mac by now!
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
yea for sure the recomended setup is 8-16GB of ram and a ssd.. the difference is massive. most modern to not so modern processors can handle it just fine that isnt as big a factor... also usually the source is 30GB (? irrc) and then 50 for ccache... so 80 is really what you should be running. oh plus os.. maybe 5gb barebones.. but really 100 gb would be full breathing room. im not sure how much of the ccache you use at a time though
[AT&T Samsung Galaxy S II SGH-I777] Tjsherod:
So I've done multiple builds but whenever I try to flash them I get the status 7 error. I tried changing the updater script, the build.prop, everything. I'm on the Dream kernel but I can't even flash the stock cm kernel cause I get the status 7 error. Could somebody help me out? I would greatly appreciate it.
[AT&T Samsung Galaxy S II SGH-I777] shri_chanakya:
OK. i followed the instructions and build is created pretty fine. However when I flash it media scanner never works and errors out. Any idea if this is bug in the main branch or am I doing something wrong?
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
Personally, I usually delete the entire conditional statement off the beginning of the installer script.

There are known issues with Media Scanner ATM.
[AT&T Samsung Galaxy S II SGH-I777] MotoMudder77:
That just made my day. I thought my HP G7 laptop w/ i3 and 4gb was a pile for taking 120 min for fresh.

although halfway through I lost my touchpad, and was so unresponsive. :eek: So i guess it still is.

And also for the status 7 error, couldnt they just format system in recovery, heard it somewhere, never seen an answer.
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
LOL. Anything Core 2 Duo (Penryn) or newer should be relatively fine. Any i-series will be well more than ok for compiling.

When you lose responsiveness, I guarantee it's because you have a HDD. Look at the HDD activity light when it's unresponsive... probably on constantly.

As for "status 7" problems, those are so well documented in this forum... ;)
[AT&T Samsung Galaxy S II SGH-I777] Fusion777:
Can't seem to get the 5ghz WiFi fix working for my build. When I modify the two nvram files with ccode=US and reboot, WiFi hangs on trying to turn on. Interestingly when I revert the files and reboot again, WiFi remains hung. Has anyone else run across this?

Sent from my Nexus 7
[AT&T Samsung Galaxy S II SGH-I777] Tjsherod:
So I had a little idea, please comment on this, and the idea is an automated build script that we would put on our computers and everyday at, for example, 10 P.M., and it would do the repo sync command and if there was anything new it would automatically build the new rom. How could you be able to do this?
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
i hate to burst your bubble.. but its called jenkins and the CM team already has it covered haha. but i suppose if you wanted to do it yourself it wouldnt be very difficult at all. and the only reason to have this is if you are submitting changes to your own personal branch and at that point... just build it yourself... also you wouldnt need to sync bc all the changes originate form your pc.

jenkins.cyanogenmod.com

but if you were so inclined... I would use cron since it has a tidy daemon running and then have it call a script which runs the 2-3 commands. and since scripts run sequentially you wont have a problem.
[AT&T Samsung Galaxy S II SGH-I777] zas0006:
I have a question I tried to ask in irc but my router decided to tank before I got an answer. If I want to cherry pick a few commits, do I just use the git command on the gerrit page and that's it or do I need to be in a certain directory first or what ? I have gotten to where I can build cm10 in Ubuntu with no problem but I want to learn more and thought I would start there.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
You need to use repo start to begin a new branch on whatever project you're messing with, then run that git command within the project

e.g.

repo start blah kernel/samsung/smdk4210

cd kernel/samsung/smdk4210

<paste git command from gerrit here>
[AT&T Samsung Galaxy S II SGH-I777] ddominator:
Should we use the smdk4210 or the smdk4210_new kernel source from the team Hacksung github?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
_new is not ready yet - especially for N7000 and I777 because I have been busy with tethering.

It's also missing a whole bunch of common patches - _new is the future, but right now it's behind the old until we finish patching it up
[AT&T Samsung Galaxy S II SGH-I777] zas0006:
Build Issue

deleted.