yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] elite_gamer04:
Just recently setup a spare box as Debian, and wanted to try my hand and sync'ing and building CM10 manually myself, I followed the instructions to the 'tee' here:

http://teamhacksung.org/wiki/index.php?title=CyanogenMod10:How_to_build&oldid=11578 (Had some issues with the experimental auto script, so decided to do it manually)

Everything seemed to have worked, with no issues, I initiated the ./build.sh i9100, came back 2hrs later and got this:

target Dex: framework
make: *** [out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/noproguard.classes-with-local.dex] Killed
Package KERNELUPDATE: out/target/product/i9100/kernel-cm-9-20120817-i9100-signed.zip
rm: cannot remove `kernel-cm-10-*': No such file or directory
Copying boot.img...
Copying kernel modules...
Copying update-binary...
cp: cannot stat `obj/EXECUTABLES/updater_intermediates/updater': No such file or directory
Copying updater-script...
Zipping package...
Signing package...
Unable to access jarfile /home/EG04/android/system/out/host/linux-x86/framework/signapk.jar
Package complete: out/target/product/i9100/kernel-cm-10-20120817-i9100-signed.zip
md5sum: kernel-cm-10-20120817-i9100-signed.zip: No such file or directory
Elapsed: 201 min(s) 57 sec(s)

Thats obviously only the last few lines, and can go back and pastebin the entire build process if necessary. I went through the experimental build.sh to ensure I had all the required dependencies etc. Running Debian Wheezy 64bit if that helps, pulled propitiatory files from GS2 fine and using the following local_manifest.xml:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="jellybean">
<copyfile dest="build.sh" src="samsung/build.sh" />
</project>
<project name="teamhacksung/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="jellybean" />
<project name="teamhacksung/android_device_samsung_i9100" path="device/samsung/i9100" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
<project name="teamhacksung/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="jellybean" />
</manifest>

Any help would be greatly appreciated!
[Galaxy S II Original Android Development] GFXi0N:
Ok, as my knowledge is quite limited about this still, I attempted changing local_manifest.xml to this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="jellybean">
<copyfile dest="build.sh" src="samsung/build.sh" />
</project>
<project name="teamhacksung/android_device_samsung_i9100" path="device/samsung/i9100" remote="github" revision="jellybean" />
<project name="teamhacksung/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="jellybean" />
<project name="teamhacksung/android_kernel_samsung_smdk4210_new" path="kernel/samsung/smdk4210_new" remote="github" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="ics" />
</manifest>

Notice the line:

<project name="teamhacksung/android_kernel_samsung_smdk4210_new" path="kernel/samsung/smdk4210_new" remote="github" revision="jellybean" />

But when I compile my ROM, I still get kernel version 3.0.36..... I think I'm not doing it right.... am I?
[Galaxy S II Original Android Development] bluefa1con:
I think this should be

path="kernel/samsung/smdk4210"
[Galaxy S II Original Android Development] GFXi0N:
Yes, but this compiles kernel version 3.0.36, but codeworx's builds carry 3.0.16 (correct me if im wrong with the numbering) because it's based on source code released by samsung... and I was asking how to compile the ROM with the same Kernel version.....

Actually.... can anyone tell which ae the differences between using one or the other? And which is the most updated one? Because codeworkx might have been applying more patches to one than to the other version....

Isn't there any wiki page documenting this kind of things?

Thanks!
[Galaxy S II Original Android Development] rav4kar:
Entropy512 started _new for future kernel updates per his post at i777 thread.
[Galaxy S II Original Android Development] bluefa1con:
This way you will download the 3.0.15 based kernel sources and place them in the smd4210 folder and use for compiling
[Galaxy S II Original Android Development] PlanDreaM:
Weird question: How much space I need for downloading and compiling? I am limited here.

CM10/SGSII International
[Galaxy S II Original Android Development] madquack:
Straight from the horse's mouth: "The source download is approximately 8.5GB in size. You will need over 30GB free to complete a single build, and up to 100GB (or more) for a full set of builds."

Obviously your mileage may vary depending on the size of CCACHE, some people use between 50-100gb for it. I use 75gb for ccache but I have ubunutu installed on a 150gb partition.
[Galaxy S II Original Android Development] GFXi0N:
My ccache is set to 20 Gb but you don't use that much, my ccache folder is only 5 Gb... so, I don't think you need to set ccache to a very high value.....

I still don't understand how to get 3.0.16 kernel while compiling..... I'm investigating myself, though......

EDIT n: Ok, now I understood what you people mean....

After changing the local_manifest.xml, i get this error when syncing:

repo sync -j16
Fetching projects: 68% (215/315) From git://github.com/CyanogenMod/android_kernel_samsung_smdk4210
+ f351a1d...0527fde linux-3.0.y -> github/linux-3.0.y (forced update)
Fetching projects: 70% (221/315) error: Ref refs/remotes/github/linux-3.0.y is at 0527fde0639955203ad48a9fd83bd6fc35e82e07 but expected f351a1d7efda2edd52c23a150b07b8380c47b6c0
From git://github.com/CyanogenMod/android_kernel_samsung_smdk4210
! f351a1d...0527fde linux-3.0.y -> github/linux-3.0.y (unable to update local ref)
Fetching projects: 100% (315/315), done.

Any ideas?

EDIT1: I changed the local_manifest.xml to this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="jellybean">
<copyfile dest="build.sh" src="samsung/build.sh" />
</project>
<project name="teamhacksung/android_device_samsung_i9100" path="device/samsung/i9100" remote="github" revision="jellybean" />
<project name="teamhacksung/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="jellybean" />
<project name="teamhacksung/android_kernel_samsung_smdk4210_new" path="kernel/samsung/smdk4210" remote="github" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="ics" />
</manifest>

I will try to compile... the worst thing that could happen is a compilation error....

EDIT: It compiled and produced a ROM with kernel version 3.0.15 :)

Now, going back to Arch LINUX and see if I can fix the damn error I get.....
[Galaxy S II Original Android Development] alessa:
Good evening.

abbord of all let me compliment you for the perfect job you do and especially a big thank you to you all.

Now I have a specific request to do this a wonderful team.

I use on my gs2 cyanogen10 and I am more than satisfied, but I'm missing just one thing to be really close .... the compatibility with HDMI output.

Current I am the team does not give importance to this option, and I can understand, but if I do not really understand is why, now that v10 is almost perfect (I did seen nO BUG), why not begin to address problem, which even if it is not important to everyone, is still a lack in our soul and geek passionate hight tech, although it remains any lack.

if this function is not or can not use the owner of gs2, it must still recognize that even for those who use it, it becomes almost a capital importance.

far from my intention to criticize or judge your work, which can only inspire respect and admiration.

Thank you for taking the time to read this and I hope you have been able convaicre ...

thank you again and good job;)
[Galaxy S II Original Android Development] Entropy512:
This does not belong in Development, as it is not Development-related. If you want HDMI support, yell at Samsung for releasing a haxxed-up undocumented mess. Last time we tried to get HDMI fully working the end result was a device that didn't boot at all. What they use on their shipped devices doesn't match the Insignal reference sources at all.
[Galaxy S II Original Android Development] GFXi0N:
Ok, this is amazing...... compilation finishes as it's supposed to when I try to compile kernel 3.0.15 on Arch LINUX (3.0.36 gives me that weird error where the characters 99.98 are added to a folder and the compilation stops, bla bla...) So... I would like new thoughts on how to fix this, if any come to the big minds around here because I'm out of ideas :)

And a question for codeworkx :) :

Kernel 3.0.15 Vs 3.0.36 ... some people say the newer is better... but I would like to know from you... which one is recommended and which one is being more actively developed? (As I can see 3.0.15 has more recent activity)

Thank you very much

Now it has been only 175 minutes to compile the whole rom for the first time.... YAY!!
[Galaxy S II Original Android Development] :
gokhanmoral had removed all linux patches and just cherrypicked some. He's right, linux patches are 99% useless, and some can even break stuff, so removing them may let the kernel a bit/a lot more stable, just like Samsung stock Kernel.
[Galaxy S II Original Android Development] alessa:
ok thank you for this answer.

in fact, when I phone in my hdmi brance well I still picture and sound works ... strange.
[Galaxy S II Original Android Development] Testraindrop:
Hi Codeworkx/Entropy/DevTeam,

have you noticed that Sony released the Sources for their sensors?

http://developer.sonymobile.com/wp/...l-dash-developers-can-contribute-open-source/

Do you know if any of the sensors are the same as on Samsung devices?

Am I assuming right that the sensors aren't manufactured by Sony/Samsung etc. but by 3rd party Companys?

Maybe the code is helpful anyway if not...;)
[Galaxy S II Original Android Development] codeworkx:
Our sensor hal is also opensource. Selfbrewn. :D
[Galaxy S II Original Android Development] GFXi0N:
@codeworkx :

Sorry to insist, but why compiling 3.0.36 gives me this error:

ERROR: could not open directory /home/jonander/android/system/out/target/product/i9100/obj/KERNEL_OBJ/../../system/usr/lib/modules/99.98.3.0.36-CM-g7f5a4aa: No such file or directory

While compiling 3.0.15 compiles just fine

Could it be some error in the source code instead of a configuration issue?

It's Arch LINUX 64 bit..... if there is a way i can help tu hunt this bug down, I'd be more than happy to help

Cheers,
[Galaxy S II Original Android Development] pulser_g2:
The 99.98 bit likely shouldn't be there
[Galaxy S II Original Android Development] codeworkx:
must be something in the code.

happy hunting.

btw. official jellybean branch on cm github is 3.0.15. use this.
[Galaxy S II Original Android Development] smhtc:
Sure you have path with 3.0.36? 3.0.15 would be using 3.0.15 in path name, and maybe that path exists and so compiles ok, but not the 3.0.36 one.

Just suggesting..
[Galaxy S II Original Android Development] GFXi0N:
Now I'm compiling 3.0.15 and I left 3.0.36 because .15 is the one "to use"..... but the error is there.... and happens only when compiling .36 kernel.....

3.0.15 compiles just fine: No errors....
[Galaxy S II Original Android Development] codeworkx:
all repos are moved to http://github.com/Cyanogenmod
[Galaxy S II Original Android Development] madquack:
Someone should give you a million dollars. This simplifies **** so much. May I ask why the merger? Even if you guys are CM maintainers, does that mean Team Hacksung is kaput or are you guys just part of CyanogenMod now?

PS. Compiling on Ubuntu 11.10 is far faster than any other recommended distro, I don't understand why. Build time from make clean and clobber is barely 70 minutes, yet on 10.04 or 11.04 it is easily 250-260 minutes. Do certain distros play nicer with different hardware?
[Galaxy S II Original Android Development] Testraindrop:
They are already part of CM Team, I guess they merged it to have a unified base, easier to maintain.
[Galaxy S II Original Android Development] madquack:
Yea they've been part of CM for a while but I was simply wondering if team hack sung was dissolved..
[Galaxy S II Original Android Development] GFXi0N:
I'm confused... so now the local_manifest.xml should be changed but not all the lines, and point them to cyanogenmod git.... can anyone post an updated file?

I'm doing my research and trying.... but it won't just work changing all the teamhacksung repos and point them to cyanogenmod ones.....

For example... android_kernel_samsung_smdk4210_new does not exist under cyanogenmod... should we use cyanogenmod/android_kernel_samsung_smdk4210 instead?
[Galaxy S II Original Android Development] codeworkx:
teamhacksung is just our playground for experimental stuff till it's clean enough to go into the main repos.

we're part of cm.

right, everything from cyanogenmod.
[Galaxy S II Original Android Development] madquack:
That's what I thought. Thank you.
[Galaxy S II Original Android Development] kalgecin:
So we can remove the local manifest and compile like we used to in cm9? brunch i9100?
[Galaxy S II Original Android Development] GFXi0N:
So the wiki about how to build must be updated?

I'm a bit confused.... (Just when I set my machine to properly build, it goes and changes the way of doing so...)

EDIT: I changed mine to this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="jellybean">
<copyfile dest="build.sh" src="samsung/build.sh" />
</project>
<project name="CyanogenMod/android_device_samsung_i9100" path="device/samsung/i9100" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="jellybean" />
<project name="teamhacksung/android_kernel_samsung_smdk4210_new" path="kernel/samsung/smdk4210" remote="github" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="ics" />
<project name="CyanogenMod/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210" remote="github" revision="jellybean" />
</manifest>

Is it ok?
[Galaxy S II Original Android Development] codeworkx:
no, the wiki is fine.
[Galaxy S II Original Android Development] kalgecin:
So we can continue syncing as the wiki says from teamhacksung git and won't be missing anything ?
[Galaxy S II Original Android Development] codeworkx:
the wiki never said to sync from ths.
[Galaxy S II Original Android Development] Spiralzz:
http://db.tt/DhP5o4W3

Was using tapatalk when my phone froze. Had to reboot (didn't take out the battery).

I am on stock kernel, stock settings and have been using the same apps since a week (did a full wipe just about a week ago).

I uploaded the last_kmsg to dropbox.

Edit: Oops. I'd completely forgotten, I had increased the GPU steps a few builds back(would that have caused the freeze?) Have returned to stock. Will see if my phone freezes again. Sorry.
[Galaxy S II Original Android Development] GFXi0N:
Why when building a ROM do I still get the CM9 bootanimation? Isn't it supposed to be in the CM repos?

The rest of the ROM works just great on my phone....
[Galaxy S II Original Android Development] Spiralzz:
Got another freeze, this time with stock settings as well. http://db.tt/PUdCNIYn

Also had a kernel panic, but when I tried getting a last_kmsg, said that there was no file...
[Galaxy S II Original Android Development] TheSpaceManatee:
Hello everyone.

Well this is my second time trying to compile from source, but first time from i9100 :/ Everyone has to start somewhere right? Thank you all in advance. Well I'm stuck at this stage:

create ~/android/system/.repo/local_manifest.xml using this content:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="jellybean">
<copyfile dest="build.sh" src="samsung/build.sh" />
</project>
</manifest>

I tried the: create ~/android/system/.repo/local_manifest.xml using this content command and got an error.

So I decided to manually add the file in .repo. I used Ctrl+H to see the hidden file and then I added the local_manifest.xml file manually. When I "repo sync -j16" I got a long line of code and the last line had an error something about manifest.xml. I need some help and would appreciate any attempts to help me!

Thank you all once again! :D
[Galaxy S II Original Android Development] kalgecin:
Asking for help while saying "I got something like" is, I'm sorry, plainly stupid from a point of view or person trying to help. You need to provide exact errors. Copy paste to pastebin and link here.
[Galaxy S II Original Android Development] finnq:
Bootanimation is still in review.

//tapatalked / i9100 / CMX
[Galaxy S II Original Android Development] ross_ctr:
Seem to be having a problem syncing repos. It gets as far as project 311/314 and then just stops dead, no errors or anything. Any ideas?

Cheers

Edit: Sorted now, just took a while for it to do anything. Carried on after about 20mins.
[Galaxy S II Original Android Development] bombaybadboy:
Small bug on build bot builds. FC on installing apks from storage excepting unknown source settings
[Galaxy S II Original Android Development] Testraindrop:
Works fine here, checked with BBS 1.10 XDA.

Check your apks.

Btw. wrong thread, without Logcats the Devs can't do anything about it, so post it in the User thread.

Edit: More info on that:

During a conversation with bombaybadboy we found the exact pattern to reproduce it:

-buildbot builds only

-"allow install from unknown sources" has to be unticked from settings (!)

-try to install an apk from storage

-dialog that its not allowed

-press "go to settings"

->FC

I will try to get a logcat as soon as I can and will edit this post.

Edit 2:

I believe this commit will solve this bug, so no need for logcats :D You guys are really good :)

http://review.cyanogenmod.com/#/c/22169/
[Galaxy S II Original Android Development] elite_gamer04:
Rebuilt my 'CM10 Build' machine yesterday, followed the fantastic guide posted in OP (manually, I like to learn) to the 'tee' but have ran into the following error where it seems to have aborted during the build process:

make: *** [out/host/linux-x86/obj/EXECUTABLES/mksnapshot_intermediates/src/accessors.o] Killed
build/envsetup.sh: line 1605: 8428 Killed schedtool -B -n 1 -e ionice -n 1 make -j -l $load "$@"

The whole output of the process can be found here as it may help the gurus decipher my problem: http://sebsauvage.net/paste/?ba01c4bdf889183c#QWWcuIofqQxaXfe4lv3PNG+WPt22y/CKAGOIKjCOjYQ=

It also most certainly didn't take 47mins, more like 2-3hrs when my PC became responsive again haha. Any help would be greatly appreciated!
[Nexus 7 General] airforce207:
Google now was there and worked well, it disappeared by itself. Whatever I try, it doesn't show up the "Google now" menu any more. Does anybody know how to get it back?
[Nexus 7 General] leebo:
At the risk of stating the obvious, have you tried swiping the screen from the bottom up?

It would go under RTFM.
[Nexus 7 General] airforce207:
I did swipe from the bottom up. Only Google search bar shows. In the setting on the right bottom, there is no "Google now" option. I read manual many times and couldn't find out.
[Nexus 7 General] Westfire:
Try opening the Voice Search app in the app drawer and then going to settings. Does it show bow?
[Nexus 7 General] airforce207:
Finally I found a way around. Sign up and add a new Google account, and it is back immediately under both accounts. Thanks guys.
[Nexus 7 General] big samm:
All you needed to do was turn off Google now and turn it on again, works for me.

Sent from my Nexus 7
[Nexus 7 General] airforce207:
The problem is that it even didn't give me turn on/off option.
[Galaxy S II General] gu1dry:
First, because I can & I want to rob someone of doing this :P
[Galaxy S II General] Entropy512:
nooooooo! I can't have my fr0st p1st!
[Galaxy S II General] c3l5o:
I'm going to try this after the nandroid backup finishes.

Props on you and the other devs involved. :)
[Galaxy S II General] Jiangyi:
And now the I9100 users get their serve of Jelly Bean goodness. :)
[Galaxy S II General] Sharpen3d:
Awesome! Downloading now, going to test on sc-02c.
[Galaxy S II General] Spiralzz:
Awesome! I went twice to the title just to make sure it is for GT-I9100... :P cant believe it... :D
[Galaxy S II General] androidindian:
incredible work by teamhacksung, codeworkx and xplodwild! :D
[Galaxy S II General] perepelica:
Is gapps from 0429 from cm9 is suitable for cm10?
[Galaxy S II General] override182:
Nandroid in progress :) Love you codeworkx, xplodwild and the whole team hacksung. BIG WIN!

GAPPS for JB ( gapps-jb-20120717-signed )

http://goo.im/gapps/gapps-jb-20120717-signed.zip
[Galaxy S II General] Jiangyi:
No, use the JB one from 20120717.
[Galaxy S II General] marcellocord:
oops. The show will begin ;)

gonna test it and post my review here.
[Galaxy S II General] Garuxa:
Finally, the CM10 thread for our SGS2

Thanks developers :D

Enviado desde mi GT-I9100
[Galaxy S II General] #illidan:
You'll guys are the best! Thanks for all your hard work & for putting up with Samsung's piss poor & pita work to get us JB. You'll guys are heroes.

NO!!

+1:p
[Galaxy S II General] gbyrne2011:
Stuff of Legens

You guys are the stuff of legends.. Here you have a working version and Samsung are only testing it, lol..

Well done lads, well done :D
[Galaxy S II General] ashtrai:
Does anyone know whats working and whats not?
[Galaxy S II General] D4rKn3sSyS:
I could have done it. I'd rather think what to post here

As expected, you guys supporting our device, I hope I can do more contributions to device tree this time. I did sumbit patches to gerrit but just a few were to S2 on ICS, As I do mostly framework or gui stuff, wich is my area of knowledge :).

Thanks for developing on S2 even after you tasted omap godness, and have newer devices.

Btw, Noob users asking if they should do fullwipe or things like that in 3, 2 ,1.

EDIT: Ok, they're now spamming dev thread :/
[Galaxy S II General] marcellocord:
http://goo.im/gapps/gapps-jb-20120717-signed.zip

GoogleApps.
[Galaxy S II General] Okur90:
You, sir, continue being a legend.:thumbup: Could you please list known bugs for noobs and experts who dive nose in to experimental stuff?

Sent from my Galaxy S2
[Galaxy S II General] jthatch12:
+1