yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Not sure why you guys are having such problems with build tools ... it works fine.

If a commit gets merged before we update tools, yes it'll error out. Just remove the commit from the script.

Log into your build box:

1. repo abandon auto

2. repo sync -j16

3. ./build.sh skyrocket-10.2

15-20 minutes later, you'll have a rom ready to go :) If something blows up in the script it's pretty much because of a merged commit. If something breaks in the build, then there's a missing commit or a code change that broke build. You have to do some troubleshooting to figure out which it is and go from there.

I just ran a build using the exact steps above and it worked fine. :D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Unjustified Dev:
I made a pull request to hercskytools for the i577 as it works just fine thanks
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Taking a crack at building here... I figured I'd go with CM10.1 first, then maybe to Slimbean after getting my feet wet. I know this isn't a VirtualBox thread, but hopefully I've explained my situation well enough, and someone can offer some advice. I really want to learn to build here :)

First off, I'm running Win7 x64 with an AMD Phenom II 965 quad core running at 3.6GHz, 8GB of RAM. I have an ASUS M3N72-D mobo, and have the latest available BIOS loaded (1510). I'm using VirtualBox, and running Ubuntu 12.04 32-bit. I did read that 64-bit is recommended, but it didn't say "required". I couldn't install the 64-bit version because the installer didn't find a 64-bit OS? :confused:

I followed the instructions in the OP to set everything up, and all went well. After installing/updating the SDK, I kept getting errors like this:

I found that with Ubuntu 12.04, I had to follow the OP instructions under "On newer versions of Ubuntu such as 11.10 you may need to do the following:"...

Then I actually got to the build part, and all seemed OK (I was prepared for extended processing times) until I got some warnings about signed/unsigned integer expressions, and a 64-bit error a minute or two into the build:

So I killed the VB, and loaded up my Ubuntu 13.04 64 bit ISO image to install and give it another go, but now VirtualBox won't even start with with a 64bit VT-x/AMD-V CPU, and I get this error message:

So off to the BIOS I go, checking that this is enabled (and it is), so after some researching on it, I tried turning this setting off too with the same results... Seems like it's a known issue in the VirtualBox search results I perused from 2-4 years ago...

I might try dual-booting a REAL Ubuntu install at some point, if I can't figure this out, but I use my Win7 box a lot for web dev and other stuff that I leave open for several days while working on it.

I have a couple of questions:

Is anyone else building using Ubuntu 12.04 on VirtualBox in 32 bit mode?

Has anyone successfully installed Ubuntu 64 bit in a VirtualBox machine on Win7 x64? If so, were there any special steps required?

Thanks!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Unjustified Dev:
A guy I know has it running on a Core i5 . I will see if he can tell me how he installed it also you need to be on 64 bit 32 bit wont work. Also you loose speed when using vm if your pc isnt the best like mine I have a dual core. If you need help partitioning just ask. Your Hard drive must have a reasonable amount of space. I have like 4 partitions on a 320gb
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Thanks. Do you mean need to be on x64 Ubuntu? I'd really like to run it in a virtual environment as opposed to dual-booting it.

My machine has plenty of horsepower for this (specs in my previous post)... :cowboy:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Replied. Feel free to pm me or ping me on irc tomorrow if you want to discuss further.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Dual boot it man ... Virtual will kill build times in a bad way.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
OK so im working on aospa 3.9x who's down to work with me on it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] lazer77:
Times like this where I wish I had the tools to do so :/
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
I'll keep you in mind bro if I get anywhere with it. I'd need a second opinion before I had a chance to release anyway.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] lazer77:
Thanks man. I'll def test anything that needs to be. If you get this far.. Keep theme chooser if you can lol. I think they removed it from official. At least it is for the Nexus 7 from what I've read.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
I think theme chooser borked out that's why they pulled it. As for me I'm a purist if I'm going to build it's going to stay how the devs designed it. I may do my own custom ROM some day but I've been threatening that since I got the rocket just after it was released lmfao.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
I did exactly that, and it won't even start to build, I had to remove 46451 and 46607 for it to even start building, but it fails anyway on libstagefright. Obviously your tree has something in it that works, that is different from github. Like I said, I'm done, I won't have any time to look at this until the weekend, if I get motivated again.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] lazer77:
I had a feeling it may have borked something. Haven't upgraded to 4.3 on mine yet so I really didn't know.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] berniesteven:
I can do some testing if you need another.

SGH-I727 - Peace
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Hmmm .. weird ... i'm using this with the github cm-10.2 branch.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
I don't get it either. If I get time, I am going to completely remove my tree and start from scratch using your instructions and see where I get.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] soccerfan6789:
Experiencing this error when I try to build 4.3...(PAC-Man for hercules)

make: *** [/home/shariq/PACman/out/target/product/hercules/pac_hercules-ota-eng.shariq.zip] Error 1

Full log: http://pastebin.com/kKmmfgBV

Anyone had similar problems before?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Here's my build of PAC for cm-10.2 if anyone wants to play around with breaking their phone.

pac_skyrocket_4.3-alpha.build.0_20130806-124954.zip - 198.91 MB

If your phone commits harakiri, I accept no responsibility.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
That seems to have done it. I had to manually run a breakfast and edit the celox file, but it built successfully and I'm running it now. I think the build readme should be updated because it is not complete, at least it didn't work for me as documented.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
LOL ... this.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
nothing wrong with that readme
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
Nothing wrong with it, aside from the fact that it doesn't work. I had to manually edit the celox-cm-10.2.sh script to remove 3 cherry picks that would not apply, and I had to manually run breakfast cm_skyrocket-userdebug for build.sh to work. Aside from that it's perfect. I'm not knocking Team Chopsticks, I have benefited hugely from their work, and I can't thank them enough. However, saying that it is as simple as running those commands in sequence is a bit of a stretch, it took me almost a week to make it work, not 15-20 minutes, and I'm not exactly unfamiliar with the process.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
They can't be on top of the script 24/7 to automatically update it after merges have applied. Just edit them out in the script, and continue as normal. It's really not hard at all.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
It actually is that simple - that's the point.

The only thing that ever changes is the actual gerrit commits in the script - which we obviously cannot be up to the minute on. The rest of the script works perfectly well in a normal Linux build environment every time.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
I understand that the cherry picks are going to change. But saying the script works every time is not necessarily true, as I said, it doesn't work for me, on a Fedora 16 server that previously had no issues building CM10, and nothing substantial on that server has changed since then. Anyway, it works now, with some hand holding, so I'm happy about that.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I'm still trying to help out on this XYAOSP rom with no avail. The device source is 9 months old for it. However the rest of the rom is up to date. Frameworks ect...When I try to bring the up to date cm10.1 hurc folder I get stupid errors because there manifest has a huge/mangled source list like so.

<manifest>
<remote name="aosp"
fetch="https://android.googlesource.com/"
review="https://android-review.googlesource.com/" />
<remote name="xy"
fetch="https://github.com/XYAOSP/" />
<remote name="cr"
fetch="git://github.com/CarbonDev/" />
<remote name="aokp"
fetch="git://github.com/AOKP/" />
<remote name="pub"
fetch="git://github.com/" />
<remote name="slim"
fetch="git://github.com/SlimRoms/" />
<remote name="sm"
fetch="git://github.com/SaberMod/" />
<remote name="mk"
fetch="git://github.com/mathkid95/" />
<remote name="vr"
fetch="git://github.com/VanirAOSP/" />
<remote name="cm"
fetch="git://github.com/CyanogenMod/"
review="review.cyanogenmod.com" />
<default revision="refs/tags/android-4.2.2_r1"
remote="aosp"
sync-j="" />
<project path="build" name="android_build" remote="xy" revision="jb-mr1">
<copyfile src="core/root.mk" dest="Makefile" />
</project>
<project path="xylon" name="buildscripts" remote="xy" revision="jellybean" >
<copyfile src="build-xy.sh" dest="build-xy.sh" />
</project>

The whole manifest is here.... https://github.com/XYAOSP/platform_manifest/blob/jb4.2/default.xml

Notice how they have github and cm as separate entries. When I try to add device/samsung/hurcules in any way in roomservice I get sync errors. The rest of the manifest does provide for hurcules in every way so a local shouldn't be necessary but there hurc specific trees are way out of date so it breaks. I have tried making a full cm based local (4 device, 1 vendor, 1 kernel) and editing out those in manifest but they are in some way not compatible. That's why I've tried to keep it simple by just adding the device. Breaks sync. The dev did add to there dev/hurc folder this ukg.mk which I imported to the device folder but no luck.

So the roomservice entry has to look like this because of the way manifest is formatted but it still can't sync android/device/samsung/hurcules.

When I try to remove local, repo sync just the manifest to completion, then clone the hurc into device then try to lunch it, I get no devices (hardly). There is of course a hurc entry because I made one but it fails before the kernel finishes. I have definitely reached the end of my knowledge on this for soccerfan.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] soccerfan6789:
Its cool man. I'm just about done with Xylon as well. I'll move on to a different ROM. You did know the source is Ultimatumkang not necessarily XYOSP. That's outdated. It's not much better for Hercules anyway :/

You have truly been helpful man. Thank you for your efforts and your determination even though you don't even have the device. Once again, thanks
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Xylon, XYAOSP...lol, I tried them all. Your welcome I'm just frustrated that I came to the same conclusion as 2 weeks ago.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] :
FACING THAT ERROR:

[QUOTEherna@herna:~$ cd /media/herna/ROMs/4.3

herna@herna:/media/herna/ROMs/4.3$ . build/envsetup.sh

including device/generic/armv7-a-neon/vendorsetup.sh

including device/generic/goldfish/vendorsetup.sh

including device/generic/mips/vendorsetup.sh

including device/generic/x86/vendorsetup.sh

including device/huawei/u8800pro/vendorsetup.sh

including device/huawei/u8860/vendorsetup.sh

including vendor/cm/vendorsetup.sh

including sdk/bash_completion/adb.bash

including vendor/cm/bash_completion/git.bash

including vendor/cm/bash_completion/repo.bash

herna@herna:/media/herna/ROMs/4.3$ lunch cm_u8800pro-userdebug

build/core/product_config.mk:242: *** device/huawei/u8800pro/cm.mk: malformed COPY_FILE "vendor/huawei/u8800pro/proprietary/". Stop.

Device u8800pro not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).

Traceback (most recent call last):

File "build/tools/roomservice.py", line 76, in <module>

result = json.loads(urllib.request.urlopen(githubreq).read().decode())

File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen

return _opener.open(url, data, timeout)

File "/usr/lib/python2.7/urllib2.py", line 410, in open

response = meth(req, response)

File "/usr/lib/python2.7/urllib2.py", line 523, in http_response

'http', request, response, code, msg, hdrs)

File "/usr/lib/python2.7/urllib2.py", line 448, in error

return self._call_chain(*args)

File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain

result = func(*args)

File "/usr/lib/python2.7/urllib2.py", line 531, in http_error_default

raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

urllib2.HTTPError: HTTP Error 403: Forbidden

build/core/product_config.mk:242: *** device/huawei/u8800pro/cm.mk: malformed COPY_FILE "vendor/huawei/u8800pro/proprietary/". Stop.

** Don't have a product spec for: 'cm_u8800pro'

** Do you have the right repo manifest?

][/QUOTE]
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Ok this is using cm10.2: The following was preceeded by an s load of these omx_vdec.cpp errors again....

In file included from hardware/qcom/display-caf/libexternal/external.cpp:31:0:
/home/wantowan2/bs/out/target/product/skyrocket/obj/KERNEL_OBJ/usr/include/video/msm_hdmi_modes.h: In function 'void MSM_HDMI_MODES_INIT_TIMINGS(msm_hdmi_mode_timing_info*)':
/home/wantowan2/bs/out/target/product/skyrocket/obj/KERNEL_OBJ/usr/include/video/msm_hdmi_modes.h:214:43: error: narrowing conversion of 'i' from 'int' to 'uint32_t {aka unsigned int}' inside { } is ill-formed in C++11 [-Werror=narrowing]
cc1plus: all warnings being treated as errors
make: *** [/home/wantowan2/bs/out/target/product/skyrocket/obj/SHARED_LIBRARIES/libexternal_intermediates/external.o] Error 1

I can't seem to find patches for this...?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
I think what I mean is......it's there a way to continue a build from where it left off, after it breaks, or does one have to rebuild from the beginning? I'm always an hour + in when it breaks.

sent from somewhere upon the beanstalk
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
just rerun the build without cleaning, syncing, etc. Just hit mka bacon again. But if you change anything at all, you will have to start the build over. (Obviously ccache helps a lot here once you finally get a good build)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] :
ERROR, can somebody help me?

s/LINKED/libjni_latinime.so)

host SharedLib: libESR_Shared (/media/herna/ROMs/4.3/out/host/linux-x86/obj/lib/libESR_Shared.so)

host StaticLib: libzipfile (/media/herna/ROMs/4.3/out/host/linux-x86/obj/STATIC_LIBRARIES/libzipfile_intermediates/libzipfile.a)

host SharedLib: libSR_G2P (/media/herna/ROMs/4.3/out/host/linux-x86/obj/lib/libSR_G2P.so)

target StaticLib: libapplypatch (/media/herna/ROMs/4.3/out/target/product/u8800pro/obj/STATIC_LIBRARIES/libapplypatch_intermediates/libapplypatch.a)

preparing StaticLib: libc_nomalloc [including /media/herna/ROMs/4.3/out/target/product/u8800pro/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a]

make: *** No rule to make target `/media/herna/ROMs/4.3/out/target/product/u8800pro/obj/STATIC_LIBRARIES/lib_driver_cmd_wext_intermediates/export_includes', needed by `/media/herna/ROMs/4.3/out/target/product/u8800pro/obj/EXECUTABLES/wpa_supplicant_intermediates/import_includes'. Stop.

make: *** Waiting for unfinished jobs....

target thumb C: wpa_cli <= external/wpa_supplicant_8/wpa_supplicant/src/utils/edit.c

external/wpa_supplicant_8/wpa_supplicant/src/utils/edit.c: In function 'history_add':

external/wpa_supplicant_8/wpa_supplicant/src/utils/edit.c:183:7: error: 'str' undeclared (first use in this function)

external/wpa_supplicant_8/wpa_supplicant/src/utils/edit.c:183:7: note: each undeclared identifier is reported only once for each function it appears in

make: *** [/media/herna/ROMs/4.3/out/target/product/u8800pro/obj/EXECUTABLES/wpa_cli_intermediates/src/utils/edit.o] Error 1

target StaticLib: libc_nomalloc (/media/herna/ROMs/4.3/out/target/product/u8800pro/obj/STATIC_LIBRARIES/libc_nomalloc_intermediates/libc_nomalloc.a)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
You building with Linaro? Open external/oprofile/common.mk, scroll down to the bottom, change both of the "HAVE_LIBBFD := true" variables to "HAVE_LIBBFD := false" so it looks like this:

ifeq ($(HOST_OS)-$(HOST_ARCH),darwin-x86)
HAVE_LIBBFD := false
common_host_cflags += -DMISSING_MREMAP
common_host_ldlibs_libiconv := -liconv
else
ifeq ($(HOST_OS)-$(HOST_ARCH),linux-x86)
HAVE_LIBBFD := false
endif
endif
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
Open hardware/qcom/display-caf/common.mk and remove all the -Werror flags inside that file. This is a dirty fix but it'll get it building.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
I ran another bone stock CM10.2 build last night, and to my surprise, audio works. This was the only major bug I'd experienced previously with 10.2, the bluetooth crashing has practically disappeared, I've only had one instance in 6 days of it crashing. There seem to be some occasional issues with play services, but other than that, I'm super happy with it, it can only get better.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jd1639:
And you where going to give up. Way to go!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
A full wipe of the folder and resync is I think what fixed it. I must have screwed something up in my flailing around trying to fix it. I still contend that the instructions are not quite perfect, but with one minor change, it worked for me. Now to figure out why my automated build didn't work.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
Guessing it needs to be said... What is wrong with the instructions? What fix? Just saying they are wrong over and over doesn't fix it or identify potential errors.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
I think the tools are working great and easy to understand!! And thanks for them too. I cannot build 4.3 because my i717 device side files don't seem to be merged for the new version, but I keep trying though :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Me too all but this one and I can't find it on garret
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
If one of them fails just remove it from the celox.sh and carry on.

sent from somewhere upon the beanstalk
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
For me, if I follow them from the start, verbatim, and try and use the build.sh script, it fails until I manually run breakfast cm_skyrocket-userdebug once. After that, it's fine. I've mentioned this twice already in this thread, but apparently I'm the only one who has this problem, so it's probably not worth any further mention.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
Carbon JB 4.3 Skyrocket

Hey guys I was able to build Carbon JB 4.3 with a little hackery and several patches from gerrit. Focal is working for pic taking not vid, so is wifi, and audio has some minor issues but working. I am unable to verify calling because my SIM card from my HTC One does not fit.

I got the ok from a couple of TeamCarbon members to post this here, keep in mind this build is not supported by them so don't expect any flash at your own risk.

EDIT: Can someone verify that voice calls are working?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] EQ811977:
[MENTION=1503795]RogerN[/MENTION]...voice calls are working! Thanks!!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] evazion:
You flash 4.3 Gapps right
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] EQ811977:
Yes the ones I used are 7/29/2013
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
Cool thanks for the feedback and for everyone testing use the 4.3 gapps from the 29th.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
There were a bunch of CM10.2 commits tonight from Team Chopsticks, running another build right now using my automation. If it works, I'll start hosting them nightly, like I did for CM10, until official builds start coming out.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] desalesouche:
hi all , please give me some help to finish build...:)

http://pastebin.com/nbeX1BUW
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Snoop05:
Today morning i build first CM using Your and CM's guide.

Working, fast&fluid - just like official CM.

Next i will try to optimize builds with Linaro toolchain. Anybody did this already? I will be really thankful for any help. :good:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Snoop05:
I had HTC Desire HD - ROM and KERNEL was built with Linaro and it was smoother, and ePSXe got more FPS than Skyrocket - and DHD is solo-core device with Adreno 205

edit: synergye did this ROM
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
Which build script process is dying on you, and what step, and what error?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
For them Team Chopsticks readme here: https://github.com/TeamChopsticks/hercskytools/blob/master/README.md

From the start, if I do:

mkdir cm-10.2
cd cm-10.2
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
Modify your .repo/local_manifest.xml
repo sync
vendor/cm/get-prebuilts
build.sh clean
build.sh prepare
build.sh skyrocket-10.2

It breaks on the vendor/cm/get-prebuilts part, see http://xdaforums.com/showpost.php?p=44256475&postcount=4167

If I manually run breakfast cm_skyrocket-userdebug then redo it, it works. I bet if you removed the 'vendor/cm/get-prebuilts from that section and put it in the manual build section, everything would work. I think that's where the confusion lies, as the build.sh does a vendor/cm/get-prebuilts.

---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------

Failed on audio policy. I know there are a bunch of commits, and some cherry picks in that area, looks like there is a bit of a mismatch in terms of what is committed and what needs to be cherry picked or not. I'll let that settle before trying to build again.