yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
That guy? What a troll ... over 50 pages of people talking about this and helping each other out is hardly useless. He can piss off and ignore the thread if he doesn't like it.

I guess some people just like to complain about things and start useless arguments. Keep up the work brosef, this thread has started several new ROM's that people are currently using and has been an invaluable resource to many.

Regardless of where it lands, people will still use it as a reference.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Hey my man i stumbled across this thread a couple of months ago when i first started i was just building cm10 then now with the help of you guys and this thread I'm maintaining 8 ROMs and learning how to customize them mainly from this thread as a matter of fact i started building for the e4gt even though i don't have the phone because i knew this thread was here.. that dude even states in his pm that he doesn't build anything so he shouldn't be bashing this thread. keep up the awesome work thanks

Edit: if anything i think you should put something together for xda university
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Thanks for the support. I know better than to think one douche represents everyone. The idea for XDA U is a good one but since this thread is specific to SGH-I727 (and its variants) I'm not sure it would be accepted. If anyone wants to team up in an effort to try and make this set of tuts more universal, I'm down to work on that. Maybe we could collaborate with speed-bot since he started his first.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Man I'm down i know you say its specific to the i727 but to be honest here it's the most universal tool I've come across on this forum. I'll help any way i can
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] tommyjt24:
Thanks but no thanks

Well I never said I didn't find this thread useful and I'm not trolling, I have more useful things to do with my time. I'm trying to learn just like everyone else and help where I can. I just thought a wiki site would be easier to maintain and update so that when something needs to be updated, it can be updated, it is not owned by one individual, but rather the group of people that know what they are doing. There are a lot of good ideas on here but some are lost in the hundreds of comments.

a wiki could be broken into several useful parts:

1) machine set up (with sub topics Ubuntu 11.10, 12.04, latest)

2) Set up for ROM

2a) CM10

2b) PA

2C) ASOP

2D) etc

You still need the thread or some means to update\ask questions when something goes wrong.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Like I said last night, read your own post. It's one page back if you have already forgotten. If you have such positive motives, why do you come off like a jerk? And then have the nerve to tell me I'm the one with the attitude? I don't appreciate that crap, and no one else does either. One more time for the cheap seats: This is about making this thread better for all who want to use it. If everyone wanted to move it to another page or site, it would just be done that way. I was asking for ideas about how to make it better and more efficient HERE. And also for the record, you never said ANYTHING positive or useful, other than to recommend starting it somewhere else. You made it sound as though you know exactly what you're doing and this thread is full of unuseable instructions, so why don't you put up or shut up? Go and start a wiki and show how to do it right.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
It's your idea, put together a wiki page. Don't be a jerk here, though. These guys worked very hard to put this together and help the community. A lot of good has come from this thread.

Lastly, don't troll or be condescending around here. There are more experienced trolls and they're just itching to come out from under the bridge.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Hear, hear! What's illnevertell calling himself these days? But he only trolls the morons, he isn't one as well.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] blackwing182:
sorry but you just need to shut and go troll elsewhere, if you want something done at your style, do it your own and respect the threds, you can sugest but not demand, its like an ETA and you know what hapoen to these people here in xda.

leave it to your mind

---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------

BTW its a ****ing junior member -_- lets get back on topic, And to the op, if i was you i will be reporting him till it geta banned or what ever a mod wants to do with them.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
I personally want to thank you guys for this thread, as im sure a lot of people already have. This is a great place for people who want to understand and create (which i thought was the purpose of xda). This isnt some easy copy/paste how to thread, its a start for people who dont know. So keep this thing going in a positive direction and nothing but good will come of it. Keep up the awesome work. :thumbup:

---------- Post added at 03:36 PM ---------- Previous post was at 03:35 PM ----------

I miss that guy
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
You skipped a step. After seeing some of the recent posts though, I'm feeling less inclined to point out the specific step. Rest assured though, it's a very simple, one-line command.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
HUH. Now it all comes clear. He had an issue and didn't get feedback on it and decided to diss the thread. Well, I will apologize that you didn't get an answer on your issue(although it was friggin xmas eve), but still think the comments were unwarranted. And to say that the instructions don't work because you don't use them correctly is actually funny. I can't tell you how many times I had to be shown what to do because I had inadvertently skipped a step. M45 was one of the ones who had to hold my hand on at least a few occasions; he'll tell you. These instructions have been used countless times over the last 5 or 6 months, and when the process fails for you, 99.9% of the time, it is user error. I myself am actually famous for user error around here and it's my thread! Either way, the best bet is to go through the instructions again, and locate your missed step. Good luck on a successful build and no hard feelings. Happy New Year everyone!

BTW: The term apk. issue is also being discussed here: http://xdaforums.com/showthread.php?t=2059939

Either here or there, you should be able to track down a solution to your problem. Have a good one..
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
A reply like this is what makes this thread so great. Even trolls can find an answer here! And m45 has helped most if not all of us.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
What's really cute is I am having the same problem as he was now; it seems to be a widespread issue based in the changes taking place with the CM10 git. I see some commits that may be the solution, or the problem, I'm not sure. I am choosing to wait out the merges rather than cherry-pick and possibly end up more frustrated than I already am. So, even though I have no patience for anyone dogging out the thread, I DO understand the frustration and will post any solutions I find(unless somebody else beats me to it).

BTW: I'm overhauling the thread today, and it may look like Jackson Pollock painting in the process. I could use some help with updating the tuts. Can I get some of you guys to chime in with verification of the various tuts? Also, any additions or new instructions will be welcomed. PM me with anything you think is helpful, even if it's for another device.

UPDATE: Most of the initial work on the OP is complete; comments are welcomed. I posted a new build of Blinky's Revenge AROMA installer at the bottom of post #3. Check it out....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] tommyjt24:
Building CM10

so wait did I miss a step or find something that just wasn't merged in to cm10 yet? My understanding was the change needs to be merged into the cm10/jellybean branch to update the location of the files.

You know I went back and read my comments, as I'm tired of being called all these irrelevant names. I don't see why you think I was dissing this thread? You asked for feedback and I provided something, perhaps it is the wrong direction as the wiki feature on at least xda, sucked (no version control) or really lack of any control. The only thing I can think of you might have took the wrong way was when I said "lack of maturity" which wasn't geared towards this thread or any one person in particular but rather the Android OS and the constant changes it goes through.

I also wasn't expecting feedback right away, hence why I was looking for the answer, and provided it assuming I didn't miss a step and that there is an issue with the CM10 files.

Lets stop with the bickering, name calling, etc and get back to building! :highfive:

I used the xda university thread for setting up a Ubuntu 12.10, machine you might want to add that as a note that they will work to set up your machine to build skyrocket assuming you need or want to be on the latest version, 12.10. http://xdaforums.com/showthread.php?t=2060017
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Yep that's pretty much what it came down to; insult my maturity all day long, but not the thread. A lot of work has been put into this, most of it by people with a lot more knowledge than me. i guess we just call it a misunderstanding. Maybe the punctuation threw me.:D As far as the build, i think my PAC build was borked by trying to update my manifest with CM10.1 remotes. I dumped my entire directory after changing this and removing that. Resyncing everything and then adjusting my manifest and syncing again made my build run all the way through. But, i don't know if it is an PAC18 or PAC19, (just finished)Most of the time, additions and changes to CM are what bork the PAC build, so i assume the work on git is having some effect. Be cool

UPDATE: PAC v19.0 built without incident.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] badboyblue:
Sorry, I posted question in the wrong topic. :D

Mod please delete this post. Thanks
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
If you're using circles, you're stuck with opaque for now
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] My_galaxy:
I get a sintax error doing my aroma any ideas

Thanks if you like it
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Go back over the updater script with a fine tooth comb. I had multiple syntax errors that CvD chased down to a few commas and semi colons.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] shahulakthar:
Just to save this page:)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] My_galaxy:
OK my aroma is working now but is not installing my apks it flash the ROM but not the apks

Thanks if you like it
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Save your install log, pull it from the phone via adb immediately before rebooting after installation. Check for errors. Also pull your aroma prop files to be sure they are being setup correctly.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I've been out of town for the last two weeks until last night and didn't have a computer with me. As the time I made my reply to you I was assuming you missed the step to run the /vendor/get-prebuilts script, as I wasn't able to easily browse around on gerrit/github (no wifi/poor data signal most of the time) and I apparently didn't read your post close enough. It looks like they changed the URL to the source repo for the terminal emulator though, and had not updated the get-prebuilts script to reflect that change. It was merged 2 days ago though.

https://github.com/CyanogenMod/android_vendor_cm/commit/17bdcfdaffe4246ade13964f005a29095d34e3eb

If it still isn't working, then perhaps, the jellybean branch still needs to be updated the way it was done in cm-10.1 for vendor/cm/config/common.mk:

https://github.com/CyanogenMod/android_vendor_cm/commit/af96ba264deb820cb895a98c959216d1ba7e1348
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Working on an AOKP build for the N7 and came across this:

build/core/tasks/kernel.mk:68: **********************************************************
build/core/tasks/kernel.mk:69: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:70: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:71: * BoardConfig.mk file *
build/core/tasks/kernel.mk:72: **********************************************************
build/core/tasks/kernel.mk:73: *** "NO KERNEL CONFIG". Stop.

My local manifest looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="kernel/asus/grouper" name="faux123/Nexus-grouper" remote="aokp" revision="jb_mr1_exp" />
<project name="CyanogenMod/android_device_asus_grouper" path="device/asus/grouper" remote="github" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_asus" path="vendor/asus" remote="github" revision="jellybean" />
</manifest>

The kernel.mk file does have the above code stating no no kernel config. This one is new to me. Typically, when building CM or PAC, once you specify your kernel in the local manifest, you are ready to go. Not here. I haven't built AOKP before, so I'm a little stumped. Does anyone have experience with this and could lend a hand? I'd appreciate it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
It's saying you need to add that variable in /device/asus/grouper/BoardConfig.mk.

For example, for the Nexus 4 it's this

https://github.com/CyanogenMod/android_device_lge_mako/blob/cm-10.1/BoardConfig.mk

TARGET_KERNEL_CONFIG := mako_defconfig

Not sure why that wouldn't be there already if it's breaking the build.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I added that code in the mk. file. No change. I'm researching how to get what I need on my own, but it is slow going. I can't find that file for the grouper, even on CM( i am trying to incorporate Faux123s kernel). I'll keep at it and if I figure it out, I'll give a shout. If anyhting comes to you, let me know. Thanks man....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Black_Prince:
Any help is appreciated...

target thumb C++: libpixelflinger <= system/core/libpixelflinger/buffer.cpp
target thumb C: libpixelflinger <= system/core/libpixelflinger/codeflinger/disassem.c
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: initialization from incompatible pointer type [enabled by default]
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: (near initialization for 'disassemble_di.di_printf') [enabled by default]
target thumb C: audio.a2dp.default <= external/bluetooth/bluedroid/audio_a2dp_hw/audio_a2dp_hw.c
target thumb C: audio.primary.default <= hardware/libhardware/modules/audio/audio_hw.c
target thumb C: audio.primary.t1 <= device/samsung/i9100g/audio/audio_hw.c
target thumb C: audio.primary.t1 <= device/samsung/i9100g/audio/ril_interface.c
target thumb C: audio.usb.default <= hardware/libhardware/modules/usbaudio/audio_hw.c
device/samsung/i9100g/audio/audio_hw.c: In function 'set_preprocessor_echo_delay':
device/samsung/i9100g/audio/audio_hw.c:2482:5: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]
device/samsung/i9100g/audio/audio_hw.c:2483:5: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]
cc1: some warnings being treated as errors
make: *** [/home/shree/aosp/out/target/product/i9100g/obj/SHARED_LIBRARIES/audio.primary.t1_intermediates/audio_hw.o] Error 1
make: *** Waiting for unfinished jobs....
system/core/libpixelflinger/codeflinger/GGLAssembler.cpp: In member function 'int android::GGLAssembler::scanline_core(const android::needs_t&, const android::context_t*)':
system/core/libpixelflinger/codeflinger/GGLAssembler.cpp:1110:5: warning: assuming signed overflow does not occur when assuming that (X + c) < X is always false [-Wstrict-overflow]
stop..
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] tommyjt24:
Quick question on builds, so I have my cm10 stable build, if I compare it to cm10 stable official, there are a few hex differences in some files like the apk, but others are vastly different. Is that normal for Android roms? It is the files that are way different that have me paranoid!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rachanta:
building jb-mr1 aokp rom for i9100

I am an absolute newbee and want to build an aokp jb-mr1 rom for my i9100.

I have successfully done:

repo init -u https://github.com/AOKP/platform_manifest.git -b jb-mr1

repo sync

When I do:

. build/envsetup.sh && lunch i9100-userdebug

I get:

build/core/product_config.mk:211: *** No matches for product "i9100". Stop.

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

** Do you have the right repo manifest?

What do I do? Is there a good tutorial for me. I am below rookie level.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Need more info; I can see what device you are trying to build for, but not what style build it is.....

To be honest, I've never done a side-by-side comparison of official vs. what we build. But, I don't believe you'll have any issues, unless you did some strange additions that you aren't sure of.

Look in post #1 for the AOKP tutorial and follow those instructions. Then report back. As it happens, I am working on an AOKP build right now and have this particular error:

bmp7777@bmp7777-HP-Pavilion-dv7-Notebook-PC:~/aokp$ lunch aokp_skyrocket-userdebug && mka bacon
build/core/config.mk:216: *** No TARGET_CPU_ABI defined by board config: . Stop.

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

Although we've had this tut up for quite a while, this is my first attempt at building for it. Anyone with prior AOKP experience want to chime in on my error?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Such as?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
I'm getting this warning on repo sync with slimbean: warning: local_manifest.xml is deprecated; put local manifests in local_manifests instead

Do I need to create a local_manifest file or folder? It still sync's so far.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I've been trying to build slim for the last two days and that error is least of my troubles. When i got that error, i found that i had two local manifests. I deleted one and seemed to be good with the other. Still can't build.

Every type of build is failing out. CM gives this:

remote: aborting due to possible repository corruption on the remote side.

PAC fails out for no libaudioalsa.so. AOKP can't find proprietary_vendor. UGH. Does anyone have successful builds being produced today, and if so, how do you overcome the issues? CvD, I see you are up and running. Did you experience any hassles with CM? How did you get past them?

My Slim build is failing for this now:

Syncing work tree: 98% (294/299) error: revision jb in TheMuppets/proprietary_vendor_samsung not found
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
You can ignore it for now. The next version of repo will force you to store local manifests individually in the local_manifest directory. For now it is just a warning.

BMP -

I'm not having any issues on CM10 related to the repo :) Now issues I've caused, well ... that's a different story.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
Look at Muppets github and make sure the local_ manifest has the same address, If I remember right there manifest says jb, as compared to Muppetts says jellybean and makes a difference.

Thank you cvd, I figured it was something along those lines. I"m still getting good builds so far.

---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------

Last post was a reply to you bpp
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
You mean to tell me that I'm the only one building today that is getting this:

bmp7777@bmp7777-HP-Pavilion-dv7-Notebook-PC:~/cm10$ repo sync
remote: Counting objects: 613542, done.
remote: Compressing objects: 100% (191994/191994), done.
remote: aborting due to possible repository corruption on the remote side.
fatal: early EOF
fatal: index-pack failed
remote: Counting objects: 613542, done.
remote: Compressing objects: 100% (191994/191994), done.
remote: aborting due to possible repository corruption on the remote side.
fatal: early EOF
fatal: index-pack failed
error: Cannot fetch CyanogenMod/android_frameworks_base

error: Exited sync due to fetch errors

????? over and over.....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I'm not getting any errors .. ran a sync last night and this morning for CM10 without issue.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Could it be a connection issue? I have u-verse and it is notorious. But, I've never seen errors like that before. It typically fails out for time-out. Hmph...:mad:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
I could be wrong but it sure looks like a connection problem to me. Depends on where it times out at for what error you get. I had a problem close to that and that was the problem for me.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Anyone come across this error when building Slim?

make: *** [out/host/common/obj/JAVA_LIBRARIES/guavalib_intermediates/javalib.jar] Error 41
make: *** Waiting for unfinished jobs....
external/openssl/crypto/bio/b_sock.c: In function 'BIO_get_accept_socket':
external/openssl/crypto/bio/b_sock.c:707:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
external/openssl/crypto/bio/b_sock.c:708:20: warning: signed and unsigned type in conditional expression [-Wsign-compare]
make: *** wait: No child processes. Stop.

I've never seen this one before. Anybody know what to do for something like this?

UPDATE: Found in the first post of MY OWN THREAD that it's a guava error with a patch available. Only thing is, where does the patch go? I guess I need to build this stuff more often to confirm everything....

UPDATE #2: Found it. The tut isn't specific enough, but here it is:

slimrom/external/guava/guava/src/com/google/common/collect/maps.java

Lines #228 & 229 need to be changed to this:

public static TreeMap newTreeMap(
@Nullable Comparator
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
I had that trying cm 10.1 for the d2att. Pissed me off cause I'm starting to try this out. Synced up aokp 4.1 just Fine right after I tried that. I want to build aokp 4.2 but It's not on their lunch menu. Trying to figure out how to build local_manifest. XML for d2att. I want to learn all this but I want to know the Why.....not just the how.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Black_Prince:
Hey mate for creating local_manifest.xml go to ~/aokp/.repo/gedit local_manifest.xml

CODE

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<remote name="cm"

fetch="https://github.com/CyanogenMod/" />

<project path="kernel/samsung/t1" name="android_kernel_samsung_t1" remote="cm" revision="jellybean" />

</manifest>

CODE

(hey dont include word code ;) and find device tree and kernel for ur device on CM and create the file)

Now i have prepared for my i9100g device kernel for example...

first if your device is if not supported by the team then you have to manually add the device tree and kernel to sources so that compiling can be done for your device...

so you have to add local_manifest.xml to ur repo to download the deice tree and kernel...

the working tree for your project will be created so that correct compiling will be done otherwise erros as there wont be device tree and kernel source ...like Do you have the right manifes!!!Error in kernl building!!!

also you have to edit ~/aokp/vendor/vendorsetup.sh for adding you device to lunch menu ...see other code in the file for example...add_lunch_combo full_i9100g-userdebug...

so i think you got ur answer Why and How...?