yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] fishears:
are you saying you got a hard-on? (sorry kids):o
[Galaxy S I9000 Android Development] wogfella:
Lawl.

Technological marvels excite me. What can I say ?

Next question - anyone had a go at building 4.2 yet and if so how is it ?
[Galaxy S I9000 Android Development] kasper_h:
Didn't try building 4.2/CM10.1 yet. Anyone else tried? Is there an easy way to move from jellybean to the mr1-staging branch for all projects at once?
[Galaxy S I9000 Android Development] fishears:
Just change jellybean to mr1-staging in manifest.xml in .repo?
[Galaxy S I9000 Android Development] kasper_h:
Would be my guess as well (probably also change it in /android/manifest/default.xml as well).

I was just interested whether someone already tried :)
[Galaxy S I9000 Android Development] fishears:
I know DerTeufel has a CM10.1 build
[Galaxy S I9000 Android Development] fishears:
I've started work on a CM10.1 build but it isn't going well :(

Amongst MANY other warnings I get stopped by this:

build/core/binary.mk:11: *** external/bzip2: LOCAL_NDK_VERSION is now retired.. Stop.
[Galaxy S I9000 Android Development] kasper_h:
I started yesterday as well. Doesn't work yet indeed.There is also a problem with the default downloaded galaxysmtd kernel source (it gets the jellybean branch and not the mr1-staging branch). I decided to wait a few days :)
[Galaxy S I9000 Android Development] fishears:
I've been able to get all the mr1-staging source checked out and I've made my partition changes to the mr1-staging kernel but the build errors are making my brain ache.

I've just spent the last 4 hours forking, branching, merging, cutting-pasting, crying...

Time for a break

EDIT: I think the key lies in Gerrit - there's a lot of patches in mr1-staging that are waiting for approval but will be vital to a successful build
[Galaxy S I9000 Android Development] kasper_h:
Exactly, saw that as well. That's why I decided to wait for a week... :)
[Galaxy S I9000 Android Development] matt73300:
Hi,

I've successfully built CM10 from mr1-staging branch

All what you need is to sync sources (android & device), to add few patchs from Gerrit (many are by pawitp :)), and remove overlay directory in device/samsung/galaxysmtd (it's the only solution I found for a bug)

After it's as for CM10 :)
[Galaxy S I9000 Android Development] rubervalrfl:
When I try to compile this by giving the following error:

build / core / config.mk: 160: *** TARGET_ARCH not defined by board config: device / samsung / galaxysmtd / BoardConfig.mk. Stop.
[Galaxy S I9000 Android Development] matt73300:
Yup, normal.

"arm" should be defined in BoardConfig. You should just cherry-pick this on device/samsung/aries-common

ensure you have the mr1-staging branch
[Galaxy S I9000 Android Development] rubervalrfl:
This branch that you showed me, as it refused in gerrit, ai think that this error as I finished today can sync already have caught the error.
[Galaxy S I9000 Android Development] matt73300:
Did you get an error ?

It works for me.
[Galaxy S I9000 Android Development] rubervalrfl:
This giving the following error if you can help:
[Galaxy S I9000 Android Development] aways:
do you want build cm10.1 ?
[Galaxy S I9000 Android Development] rubervalrfl:
yes
[Galaxy S I9000 Android Development] matt73300:
Have you fully synced mr1-staging repo (device AND system ?)
[Galaxy S I9000 Android Development] fishears:
he's missing pawitp's "Jellybean 4.2 Bring-up" commit

http://review.cyanogenmod.org/#/c/26954/
[Galaxy S I9000 Android Development] rubervalrfl:
I would leave here express my thanks to the User aways, the support you gave me, thank you so much, so finished compiling as I say was.

hugs

---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------

This one too?

http://review.cyanogenmod.org/#/c/27322/
[Galaxy S I9000 Android Development] matt73300:
Nop, it's not needed this.

But there is a lot of pawitp's commits who are needed to compile and fix error after build, especially for the sim card and mounts points and storage
[Galaxy S I9000 Android Development] rubervalrfl:
Ok thanks.
[Galaxy S I9000 Android Development] aways:
i have patched all on teamviewer
[Galaxy S I9000 Android Development] rubervalrfl:
And for that I am grateful, thank yourself.
[Galaxy S I9000 Android Development] myepicyear:
Did you use your existing Working_directory, or did you create a new one to set up the mr1-staging branch? Would you mind terribly giving me a quick summary of the steps you used to create a coherent repo for building CM10.1(as they relate to normal procedures: repo init; repo sync; etc..)? I'm very familiar with everyday building, so I don't need a hand-holder or anything. I just need a few hints to get my brain sparking. I've never done an experimental branch before, and I tried repo init -u git://github.com/CyanogenMod/android.git -b mr1-staging, followed by a repo sync, to see if it worked similarly. The repo sync went on for the normal length of time, and looked like it was pull down the normal load of files, however, once it was done syncing the work tree and everything, I went to the directory, and absolutely nothing was there. :eek:

I feel kind of silly.:o I usually figure out new things as fast as they're thrown at me, but experimental branches are all new. I just don't know how to gather it all together in a logical way. Was I right in making a new working directory for this, or should I have integrated it into my current CM10.0 working-directory?

Any help is appreciated. Thank you. :fingers-crossed:
[Galaxy S I9000 Android Development] rubervalrfl:
I suggest creating a new one, so there is no incompatibilities, the sync correctly closed, sometimes my closed, but with error then did again with repo sync-j1, ai got close and put the folders in places.

Try ai, anything we are here to help.

---------- Post added at 03:45 PM ---------- Previous post was at 03:26 PM ----------

Staff gave this error now someone would have a solution?

http://pastebin.com/bpPfHK22
[Galaxy S I9000 Android Development] kasper_h:
The cm.dependencies are still set to the jellybean branch: you should manually change that to mr1-staging (in local_manifest.xml), otherwise the kernel and the device-trees are still jellybean.

Then you need to cherry-pick all the changes by pawitp on gerrit.

Then it works.
[Galaxy S I9000 Android Development] rubervalrfl:
The local_manifest.xml is already changed but this cm.dependencis this where I'm looking but I guess not.
[Galaxy S I9000 Android Development] myepicyear:
Looks like Git's server has a partial outage, so that may be why. There have been problems for several hours, apparently. Thanks for replying.
[Galaxy S I9000 Android Development] rubervalrfl:
From nothing, we need al.
[Galaxy S I9000 Android Development] kasper_h:
Can you check the kernel and device tree to see whether the correct branch is checked out?
[Galaxy S I9000 Android Development] rubervalrfl:
The local_manifest.xml this way:

<? xml version = "1.0" encoding = "UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_galaxysmtd" path="device/samsung/galaxysmtd" remote="github" revision="mr1-staging" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="mr1-staging" />
<project name="CyanogenMod/android_device_samsung_aries-common" path="device/samsung/aries-common" remote="github" revision="mr1-staging" />
<project name="CyanogenMod/android_kernel_samsung_aries" path="kernel/samsung/aries" remote="github" revision="mr1-staging" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="mr1-staging" />
</ manifest>
[Galaxy S I9000 Android Development] kasper_h:
But if you go to /kernel/samsung/aries

and do git branch -r

Which branch is then in use?
[Galaxy S I9000 Android Development] rubervalrfl:
github/mr1-staging

m/mr1-staging -> github/mr1-staging
[Galaxy S I9000 Android Development] kasper_h:
That is odd. Having all mr1-staging branches + the gerrit commits of pawitp allowed me to build succesfully.

BTW, I also removed the overlay from the galaxysmtd branch...
[Galaxy S I9000 Android Development] rubervalrfl:
I did not, you removed the folder and did galaxysmtd sync again, then worked there?

But if I do I'll lose sync cherry-pick not going?

---------- Post added at 05:13 PM ---------- Previous post was at 04:47 PM ----------

The github this off the air.

Repository temporarily unavailable.
[Galaxy S I9000 Android Development] kasper_h:
I always pick cherries in local branches to keep them upon resyncing.
[Galaxy S I9000 Android Development] rubervalrfl:
I made the cherry-picks, so I do not lose the sync that I've ever done?
[Galaxy S I9000 Android Development] kasper_h:
I don't understand this.

What I do:

-repo sync

-go to folder where I want to pick a cherry

-start a local branch (git branch --track mackay github/jellybean && git checkout mackay) - I use the name mackay for my local branches

-pick the cherry

If I know do repo sync again, the picked cherry is kept.

If you pick cherries outside a specific branch, you will loose them when resyncing.
[Galaxy S I9000 Android Development] fishears:
Do you mean for repositories that you haven't forked? I've been using "git stash" to manage this event. Would you recommend that making a local branch is better practice? The obvious downside of my method is that I have to remember to do it ;)

I value your opinion
[Galaxy S I9000 Android Development] kasper_h:
I much prefer local branches over other options. Using the " --track xxx-branchname-xxx github/jellybean" part, you keep the branch connected to the upstream github branch (of course you need to use github/mr1-staging for cm10.1).

The advantage of a local branch is that it is easier to get back to total stock: just delete your local branch. I have sometimes completely screwed up a CM10-project. Then I just delete my local branch and start fresh.

Also, having multiple branches is easier (I have multiple devices I build for, and I have specific branches with device-specific stuff which I don't want to use when building for other devices).
[Galaxy S I9000 Android Development] rubervalrfl:
I would like to thank everyone, now I can compile successfully, so I'm ageitando things because my model is I9000B.

Hugs to all and good weekend.
[Galaxy S I9000 Android Development] rubervalrfl:
Personal something strange happened, the external sd not riding on this desktop, I saw that it was set in mr1, I have failed to be the correct patch? someone would link it there please?
[Galaxy S I9000 Android Development] rubervalrfl:
Any others with this error?

http://pastebin.com/mrNGcH4y
[Galaxy S I9000 Android Development] kasper_h:
Can you explain a bit more? There are some patches by pawitp up on gerrit that solve the issue that you can't see you ext.sd. on the phone itself.

No. Did you pick any patches for Settings?

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] rubervalrfl:
Come on, problem occurs when you connect the phone to the computer, not the sd appears external, internal sd appears tranquil.

I applied all patch this link:

http://review.cyanogenmod.org/#/dashboard/1381

would in any specific I left behind?
[Galaxy S I9000 Android Development] rubervalrfl:
Staff could, but gave me a run darn, I had to repeat the gerrit about 3 times, but managed to finish.

It now becomes a question, giving an error ta Bluetooth.

ja spent the gerrit patch it, there is a file inside the folder, which will be missing this?

external / bluetooth / bluedroid / Android.mk: 8: NO BOARD_BLUETOOTH_BDROID_BUILDCFG_INCLUDE_DIR, using only generic configuration
[Galaxy S I9000 Android Development] rubervalrfl:
Staff had 4 more additions in gerrit today?
[Galaxy S I9000 Android Development] wogfella:
Edit: deleted. Sorry. Damn beer
[Galaxy S I9000 Android Development] rubervalrfl:
Sorry, do not speak or write in English, I meant if the changes had 4 gerrti with today's date.
[Galaxy S I9000 Android Development] kasper_h:
There were a whole lot of patches merged:

http://review.cyanogenmod.org/#/q/status:merged+branch:mr1-staging,n,z
[Galaxy S I9000 Android Development] wogfella:
Sorry mate no disrespect. One too many beers while reading forums is no excuse. I apologise.
[Galaxy S I9000 Android Development] kasper_h:
Anyone tried building with this patch:

http://review.cyanogenmod.org/#/c/27063/18

For me it gives SystemUI FC due to an issue with the GPS tile.
[Galaxy S I9000 Android Development] matt73300:
Wait, that's a mr1-staging patch, you can not include it in jellybean 4.1.2 !

Did you want to build CM10.1 ?

If you need help you can ask me ;)
[Galaxy S I9000 Android Development] kasper_h:
Sorry for the confusion, I am indeed building for cm10.1 :)

I found the problem last night and the author of the patch solved the problem.
[Galaxy S I9000 Android Development] fishears:
I decided not to go near that patch when I looked at the number of revisions & the comments ;)

I'm using a patch by kevdliuhttp://xdaforums.com/showthread.php?t=1999125 that does pretty much the same thing.

So is the patch you've used fully working now?
[Galaxy S I9000 Android Development] kasper_h:
The patch up on gerrit is now fully functional. It is also a much better implementation coding-wise than other solutions found on xda.
[Galaxy S I9000 Android Development] kosako17:
compilation over cm10.1 gives me this error..

In file included from device/samsung/aries-common/libcamera/SecCamera.h:27:0,
from device/samsung/aries-common/libcamera/SecCameraHWInterface.h:22,
from device/samsung/aries-common/libcamera/SecCameraHWInterface.cpp:24:
In function 'int open(char const*, int, ...)',
inlined from 'void android::CameraHardwareSec::save_postview(char const*, uint8_t*, uint32_t)' at device/samsung/aries-common/libcamera/SecCameraHWInterface.cpp:982:42:
bionic/libc/include/fcntl.h:66:28: error: call to '__creat_error' declared with attribute error: called with O_CREAT, but missing mode
make: *** [/home/kosako17/CreedROM/out/target/product/galaxysmtd/obj/SHARED_LIBRARIES/camera.aries_intermediates/SecCameraHWInterface.o] Error 1
make: *** Waiting to finish other tasks....
kosako17@kosako17-HP-Pavilion-dv6-Notebook-PC:~/CreedROM$

I have reinstalled ubuntu and done all steps from the guide, but always same error.

any idea please?
[Galaxy S I9000 Android Development] kasper_h:
How is everyone doing here :)

I got a question about local manifest. Yesterday repo updated and now it report local_manifests.xml to be deprecated and that they should be in a local_manifests folder. I made a folder local_manifests and copied my existing local_manifest.xml to this folder. But this resulted in the following error:

Anyone know's what I'm doing wrong?
[Galaxy S I9000 Android Development] rubervalrfl:
Run. / Extract-files.sh inside the folder /device/samsung/galaxysmtd, it connected with the SGS and debug mode enabled ok.

---------- Post added at 05:29 PM ---------- Previous post was at 05:21 PM ----------

Kasper_h Funny, I do not have this error, but on compensating deleted all my folders galaxysmtd HaHaHaHa .....
[Galaxy S I9000 Android Development] kasper_h:
I prefer the error over loosing it all... :)

Putting the local_manifest back to it's usual location makes syncing possible again, but gives back the warning that local_manifest.xml is deprecated.
[Galaxy S I9000 Android Development] fishears:
I'm just ignoring it ;)
[Galaxy S I9000 Android Development] kasper_h:
I do the same, but I heard the next version of repo will enforce the new local manifest location...
[Galaxy S I9000 Android Development] elitevet:
Well, looking at https://github.com/CyanogenMod/android_prebuilts_ndk

I might be missing android-ndk-r5 android-ndk-r6 android-ndk-r..

But how do I get it? 'rm -rf .repo/projects/prbuilts/ndk.git; repo sync ndk' maybe? 'Cause 'repo sync ndk' displays 100% and does nothing

==Edit===

:) parallelism,huh?

I guess I'll try resync ndk and if not, than just resync the whole stuff.

I did not have DNS problem, but I run out of disk space in the middle of sync, and it stopped. I added some vmdks and just run repo sync again. Apparently this was not enough...

==Edit 2 ===

Uhh... actually I came to understand I dunno how to get it... repo sync ndk goes for ./repo/projects/ndk.git NOT the ./repo/projects/prebuilts/ndk.git. That must be trivial, but I am clueless... How do I resync prebuilts?
[Galaxy S I9000 Android Development] kasper_h:
Maybe delete the ~/android/system/prebuilts/ndk/ dir and repo sync again?
[Galaxy S I9000 Android Development] Kshitiz_Indian:
I once messed up the kernel code in ICS and so I tried this by deleting the kernel folder. Later syncs won't pull up the kernel directory again, I have no damn idea why! >.<
[Galaxy S I9000 Android Development] kasper_h:
I once deleted a directoy (a full git directory) and on the next repo sync it got downloaded again...
[Galaxy S I9000 Android Development] elitevet:
Hmmm..

I got the cyanogen-prebuilts-ndk tarball from https://github.com/CyanogenMod/android_prebuilts_ndk/downloads

and the dirs inside look like whats missing, but what about all those paxheader files? Where, d'heck do they go? :silly: I feel the mighty RTFM's steps making the ground shake...

==meanwhile...

I did:

cyanobacter@cyanobuilder:~/android/system/.repo$ mv projects/prebuilts/ndk.git/ /tmp/ndk.git.OLD

cyanobacter@cyanobuilder:~/android/system/.repo$ ll projects/prebuilts/ndk.git/

ls: cannot access projects/prebuilts/ndk.git/: No such file or directory

cyanobacter@cyanobuilder:~/android/system/.repo$ ll projects/prebuilts/

total 32

drwxrwxr-x 8 cyanobacter cyanobacter 4096 Aug 7 00:08 ./

drwxrwxr-x 27 cyanobacter cyanobacter 4096 Aug 6 01:10 ../

drwxrwxr-x 9 cyanobacter cyanobacter 4096 Aug 5 21:40 eclipse.git/

drwxrwxr-x 4 cyanobacter cyanobacter 4096 Aug 5 09:40 gcc/

drwxrwxr-x 9 cyanobacter cyanobacter 4096 Aug 5 21:40 misc.git/

drwxrwxr-x 9 cyanobacter cyanobacter 4096 Aug 6 00:22 qemu-kernel.git/

drwxrwxr-x 9 cyanobacter cyanobacter 4096 Aug 6 00:22 sdk.git/

drwxrwxr-x 9 cyanobacter cyanobacter 4096 Aug 6 00:22 tools.git/

cyanobacter@cyanobuilder:~/android/system/.repo$ repo sync

Fetching projects: 94% (293/311) remote: Counting objects: 8232, done.

remote: Compressing objects: 100% (1811/1811), done.

remote: Total 8232 (delta 6292), reused 8232 (delta 6292)

Receiving objects: 100% (8232/8232), 21.44 MiB | 99 KiB/s, done.

Resolving deltas: 100% (6292/6292), done.

From git://github.com/CyanogenMod/android_prebuilts_ndk

* [new branch] jellybean -> github/jellybean

Fetching projects: 100% (311/311), done.

Syncing work tree: 100% (311/311), done.

cyanobacter@cyanobuilder:~/android/system/.repo$ ll projects/prebuilts/

total 36

drwxrwxr-x 9 cyanobacter cyanobacter 4096 Aug 7 00:13 ./

drwxrwxr-x 27 cyanobacter cyanobacter 4096 Aug 6 01:10 ../

drwxrwxr-x 9 cyanobacter cyanobacter 4096 Aug 5 21:40 eclipse.git/

drwxrwxr-x 4 cyanobacter cyanobacter 4096 Aug 5 09:40 gcc/

drwxrwxr-x 9 cyanobacter cyanobacter 4096 Aug 5 21:40 misc.git/

drwxrwxr-x 8 cyanobacter cyanobacter 4096 Aug 7 00:17 ndk.git/

drwxrwxr-x 9 cyanobacter cyanobacter 4096 Aug 6 00:22 qemu-kernel.git/

drwxrwxr-x 9 cyanobacter cyanobacter 4096 Aug 6 00:22 sdk.git/

drwxrwxr-x 9 cyanobacter cyanobacter 4096 Aug 6 00:22 tools.git/

BUT:

cyanobacter@cyanobuilder:~/android/system$ ll prebuilts/ndk/

drwxrwxr-x 4 cyanobacter cyanobacter 4096 Aug 5 21:40 ./

drwxrwxr-x 9 cyanobacter cyanobacter 4096 Aug 6 00:22 ../

-rw-rw-r-- 1 cyanobacter cyanobacter 684 Aug 5 21:40 Android.mk

drwxrwxr-x 3 cyanobacter cyanobacter 4096 Aug 5 21:40 android-ndk-r4/

-rw-rw-r-- 1 cyanobacter cyanobacter 2227 Aug 5 21:40 CleanSpec.mk

drwxrwxr-x 2 cyanobacter cyanobacter 4096 Aug 5 21:40 .git/

:crying:
[Galaxy S I9000 Android Development] pmos69:
Well, if you manage to recover without re-initing the repo, please post how you did it :)
[Galaxy S I9000 Android Development] kasper_h:
Very odd :S
[Galaxy S I9000 Android Development] elitevet:
I am an odd guy. Then again, I had sync stopped in the middle due to no diskspace.

*Sigh* repo init....
[Galaxy S I9000 Android Development] GFXi0N:
Anyone has a guide for doing the same but under arch Linux 64 bit? The guides I found are either outdated or thought for building cm9

Would be really appreciated
[Galaxy S I9000 Android Development] pmos69:
You only need to know/find out what are the equivalent packages to install (step 1) and remove if installed (Java in step 2).

The rest should be the same.

BTW, those packages are the same for CM9.
[Galaxy S I9000 Android Development] DROCSID:
Indeed the same, as for Linux Mint x64 I took the same packages as described.
[Galaxy S I9000 Android Development] gangstaboy13:
ok guys what about this error. cant fix it=.=

SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
[: 1: Linux: unexpected operator
[: 1: Linux: unexpected operator
[: 1: Linux: unexpected operator
[: 1: Linux: unexpected operator
LZMA arch/arm/boot/compressed/piggy.lzma
/bin/sh: lzma: not found
make[4]: *** [arch/arm/boot/compressed/piggy.lzma] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make[2]: *** [zImage] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/jaap/android/system/kernel/samsung/aries'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
[Galaxy S I9000 Android Development] stbenz:
[: 1: Linux: unexpected operator
[: 1: Linux: unexpected operator
[: 1: Linux: unexpected operator
[: 1: Linux: unexpected operator

Looks like an error in a shell script.

LZMA arch/arm/boot/compressed/piggy.lzma
/bin/sh: lzma: not found

Looks like you don't have lzma installed.
[Galaxy S I9000 Android Development] GFXi0N:
Linux mint is based on ubuntu... Of course it's going to be the same than following an ubuntu guide....

Arch is another thing though....
[Galaxy S I9000 Android Development] DROCSID:
Ahw chips yeah, Arch is no Debian, to early need some coffee! :victory:
[Galaxy S I9000 Android Development] gangstaboy13:
OK compiling again with lzma;)

Thank you!

EDIT:

thanks man the error doesn't appears anymore!

EDIT2:

SUCSESSFULLY COMPILED!!! THANKS ALL!!!!!!!
[Galaxy S I9000 Android Development] rycus86:
Hi!

I can't get adb to work on a VirtualBox with Ubuntu 12.04. My host OS is Win7 Pro.

Did anybody manage to attach adb to a phone connected this way?

Thanks in advance!
[Galaxy S I9000 Android Development] kasper_h:
I always get this error during kernel building (both kernel building as part of CM9 compiling as well as building separate kernels). It doesn't seem to cause any problem, but I am still interested in the origin of the issue.

Can you connect to the phone at all with VirtualBox. I used VMWare player in the past and had to select whether the connected USB devices would be connected to my Win7 system or my VMWare-system.

If adb doesn't work, I have a script to extract the necessary files from a downloaded CM10-build, so that you don't need to have a working adb (or a phone with CM10 installed).
[Galaxy S I9000 Android Development] elitevet:
I use VMWare workstation but this might be relevant:

When I first connect the Phone, the VM shows it connected, but ADB says "no device". I then use the VM menu to disconnect the device (connect it to host instead of guest) and then connect it to guest again. ADB works OK after that
[Galaxy S I9000 Android Development] rycus86:
Thanks for the reply.

After browsing some forums I understand that VirtualBox has issues with Samsung phones and their USB drivers. After connecting the phone to the box it hangs like it's busy doing something than the phone disconnects, so I don't think it's going to work. :(

However I found this article that overcomes this problem by downloading the files in Windows instead of Ubuntu in VirtualBox:

http://andsec.blogspot.hu/2012/04/building-cyanogenmod-9-from-source-for.html

I did not try it yet however, just sharing...

If you could give me your script that extracts the files from a build that would possibly be the best for me. :)

Thanks!