yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Jamison904:
Not sure why it can't find it. Let me look for something real quick. Oh and you are running 64bit right? Ubuntu 12.04?

Try these:

sudo apt-get install git-core gnupg flex bison python rar original-awk gawk p7zip-full gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev pngcrush schedtool xsltproc

sudo apt-get install g++-multilib lib32z1-dev ia32-libs lib32ncurses5-dev lib32readline-gplv2-dev gcc-multilib g++-multilib

and

sudo apt-get install libc6-dev x11proto-core-dev libx11-dev libgl1-mesa-dev mingw32 tofrodos python-markdown libxml2-utils

sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so

Do all these and let me know what you get. Thanks
[T-Mobile, Samsung Galaxy SIII] Dano79:
Crap im running 12.10 64 bit the 3rd command installed a bunch but all the others I get errors still no go. Thanks for the help and for these guides. Im also dual booting with unbuntu on its own partition. Could that be an issue since its not a real install like from a iso
[T-Mobile, Samsung Galaxy SIII] Jamison904:
12.10 should be fine. 12.04 is the most supported out of all distros. When the others finish does it say already installed? Did you use the andadb.sh from the setting up a development environment section? If so most of these will all ready by installed and you will be good to go and can move on to the next step :cool:

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] Dano79:
I just installed java to use the kitchen to build a rom. Running andadb script now

---------- Post added at 07:57 PM ---------- Previous post was at 07:16 PM ----------

Sweet I got it syncing now thanks
[T-Mobile, Samsung Galaxy SIII] Jamison904:
Awesome. Good deal bro. Let me know how it goes

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] Dano79:
Crap I just ran out of disk space I need to stretch my partition out more then start over smh
[T-Mobile, Samsung Galaxy SIII] DsturbD:
i had to do the same, install java from the software center to get the kitchen to work, wouldnt start using your java Jamison
[T-Mobile, Samsung Galaxy SIII] greatwhovian:
Cygwin

Can I build ROMs on Cygwin or do I have to download a Linux OS in order to build ROMs. I tried with Cygwin but get some errors while repo sync is performed.
[T-Mobile, Samsung Galaxy SIII] Jamison904:
I don't think you can. Never tried myself. I know for sure you can by dual boot and use Linux or use virtual box. Google it and let us know what you find buddy. :cool:

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] DsturbD:
i used cygwin once, it worked, but takes a little longer. if your serious about doing your own rom (even if you just want it for yourself) then i would dual boot. i used a 750g external esata hard drive for my ubuntu install and boot it from the bios, didnt have to mess with the windows 7 install on the main hard drive or change the boot loader on it (installed the linux boot loader on the external drive)
[T-Mobile, Samsung Galaxy SIII] Dano79:
Working today gonna try to sync a build again when I'm off should have enough disk space
[T-Mobile, Samsung Galaxy SIII] Jamison904:
What size are you using? Just one build folder can be up to 30 gigs.

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] Dano79:
I have 168 gigs to play with that should do it. I installed linux with wubi long time ago on its own partition volume was 30 gigs just for running linux forgot about the volume size and in the middle of the sync I got the error message saying running out of disk space. So had to abort gonna check CL for a external drive or old lappy just to run linux
[T-Mobile, Samsung Galaxy SIII] greatwhovian:
Thanks man. I tried once to build Cygwin but I think I got a corrupt folder while syncing. I just erased everything and started from scratch and everything's good so far.

I read on a forum that it couldn't be done but I'm very uptight and optimistic:D!

Will let you know what I find out.
[T-Mobile, Samsung Galaxy SIII] Dano79:
Had sync running but seems to be at a dead stop and my led light on my computer is not blinking guess it's hanging up on me.
[T-Mobile, Samsung Galaxy SIII] aamir123:
Does the kitchen automatically fix permissions for you? I have had bootloops that were then fixed by fixing permissions in recovery. Is there any way I can fix permissions in the kitchen itself?
[T-Mobile, Samsung Galaxy SIII] Jamison904:
No. The kitchen will zipalign all the apks but that is about it. Once you install a ROM, fixing permissions is more of the users responsibility. Now you can write into the install script to fix permissions while installing the ROM itself but you will need to Google how to do this since that is more advanced. I am not going to post the code and how to implement this as I do not want someone who has not read through all the guides and doesn't have a better understanding to attempt this and brick their device or someone else's.

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] aamir123:
Thank you! Also I noticed that the rom zip that is created doesn't have an md5 sum? Is this also something that has to be manually put into the script? When flashing thru twrp recovery I note the md5 sum not found dialogue.
[T-Mobile, Samsung Galaxy SIII] Jamison904:
This would beause you made it.The md5 sum is generated by our servers that we use to host the files. You can just turn this off in settings so it doesn't check for it.
[T-Mobile, Samsung Galaxy SIII] IXChicharitoXI:
Awesome thread
[T-Mobile, Samsung Galaxy SIII] pvchip3:
Jamison,

What do you use to sign your zips?
[T-Mobile, Samsung Galaxy SIII] Jamison904:
I have a set of scripts that I use... but the android kitchen has the option to do this for you. Look under the options.

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] DsturbD:
hey Jamison, under the "how to compile aokp" section, what if i want to compile cm10.1? what changes do i make to the manifest file? would all the other steps be the same?
[T-Mobile, Samsung Galaxy SIII] Jamison904:
Actually there are a lot of differences... but being the awesome team they are they have a detailed how to build for all the supported devices. Here is the one for our phones - d2tmo http://wiki.cyanogenmod.org/index.php?title=Build_for_d2tmo

Good luck bro and let me know if you need help with anything.

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] DsturbD:
of course :) thanks man, appreciate the link.

i was the 2000th person to access that page, i think i'll call my first rom CM2000 :cool:
[T-Mobile, Samsung Galaxy SIII] theminigame:
how often is it recommended to "make clobber"? every build?
[T-Mobile, Samsung Galaxy SIII] Jamison904:
No. I only make clobber if a cherry pick had gone wrong or some manual tweak jacked up the build. Also another great command for this is

git reset --hard

This will clean everything back to the last commit. Since you are most likely only building straight from source and not adding to your own like I do, this command will set it back to the last commit that was added when you did a repo sync.

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
It's not really needed until you make a major change or something that might cause the whole build env to change (i.e. changes to the build repo & frameworks sometimes) or when a change relies on something else to be updated/recompiled (can happen a lot in some of the hw repos). It's not really necessary, but it's a good practice to clean everything up once in a while (sometimes the most mind-boggling bug is fixed with something as simple as making clean). If you're worried about your builds taking to much time to complete, I would suggest using ccache (and possibly just cleaning out your out/../device folder, rather than cleaning everything when needed). I build on a stupid laptop with 3Gb of RAM and can get a build done in ~1 hour using ccache and only cleaning out the target device directory in out (I get ~2 hours if ONLY using ccache):

rm -rf out/target/product/*

(note: I've been doing an occasional build for d2att; so if you use multiple targets and only care to clean one, you can replace the star with whatever device you want to clean)

This will leave most of the common things intact so they won't need to be recompiled from scratch next time around. That coupled with a bit of ccache can help push your machine to its building potential. :good:
[T-Mobile, Samsung Galaxy SIII] BlownFuze:
Jamison, awesome guide - thank you.

I could use a little guidance or help with a stock Samsung ROM. Not sure where else to ask, so I'm starting here. I run infamous on my sg2, so I know you've worked hard on getting the jb that Samsung released, working with the whole "preload" partition. Samsung finally released jb for the note - and low and behold - they've included the preload with it as well. And I'm kind of stuck.

The kitchen won't unpack the tomb.img for the I717, so deodexing leaves me with 6 odex files behind in /system/app.

I mounted tomb, and grabbed the 6 apks - and here is where google has failed me.

Is it plausible that I can just throw those apks in /system/app, finish the deodexing, and compile the ROM without the preload partition?

I know, I know, you're wondering why I don't just try it and see what happens - learning and all that fun stuff. Lol.

Well, I can't figure out where Sammy scripts the creation of the partition and setting up the symlinks. I'm hoping if I can find that info, then I can remove any scripts or lines within, that have to do with preload and the symlinks for those 6 apps, and give this a whirl.

Thanks for any links or suggestions in advance, that can get me in the right direction. :fingers-crossed:

Nevermind, I got it. :)
[T-Mobile, Samsung Galaxy SIII] Jamison904:
Sorry... Completely missed this. You updated the kitchen didn't you. Good to go. New guides coming tomorrow! :D

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] BlownFuze:
I was using the latest kitchen, and I dont bug the retired man to update for a device. Lol

I just went ahead and put everything in /system/app and removed all the symlinks I could find. Flashed it and everything is working great.

Now just waiting for source to drop... thanks again for this thread man - helped me tremendously on my linux build. :thumbup:
[T-Mobile, Samsung Galaxy SIII] Jamison904:
Good deal man. You might run into system partition space issues that way... no biggie though. Also writing up a kernel how to. :cool:

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] BlownFuze:
Awesome, looking forward to the kernel how to. :good:
[T-Mobile, Samsung Galaxy SIII] goater1220:
Hey Jamison will this help me to modify the script to get that sd card hack to work on 4.2.2 roms
[T-Mobile, Samsung Galaxy SIII] tsunami2312:
waiting patiently for the How to cherry pick" brahhhh:laugh:
[T-Mobile, Samsung Galaxy SIII] DsturbD:
Cherry-pick How-to

1. go to the AOKP gerrit (this is the page that lists Open projects and is the one you want to be on)

2. search for a project you would like to add to your base and click it. for example on the first page there is one for blacklisting unknown phone numbers. click the name under Subject and it will open the project page (as of this writing, this project has been merged, see the Status section in the top left of the page, you don't need to pick merged projects)

3. now there is a section called Download about halfway down the page. to the right of that you will see some tabs (checkout, pull, cherry-pick, patch) click cherry-pick and the text you want to add will be under it, just go to the end of that line and click the little clipboard icon and it will copy it to your clipboard. for this one, the code looks like this

git fetch http://gerrit.aokp.co/AOKP/packages_apps_Phone refs/changes/15/8315/1 && git cherry-pick FETCH_HEAD

4. since this patch affects the phone app, you need to cd to the packages/apps/Phone directory of your source and paste that line in at the terminal and hit enter

5. then do a build. the cherry-pick should be added to your code and be functional.

Notes

a. next time you do a repo sync, you will have to add all the cherry-picks back into the code so keep track of what you are adding and what works and what doesn't

b. you should also go back to the gerrit site and leave a comment that it works (after you have tested your build and flashed it on your phone)

c. once a project is merged into the code you no longer have to cherry-pick it and you have helped make AOKP (or CM) better and have contributed to open source.

CONGRATS!

thanks to Jamison for pointing me to the CM Wiki where this info is from and feel free to add it to your how-to in post 5 and make any changes you see fit
[T-Mobile, Samsung Galaxy SIII] Jamison904:
That's what I am talking about! Awesome job bro! Feel free to add to it and update when you feel like you want to put more. I am going to link it permanently. Good deal... now I can move on to the kernel how to!

Here are the links to the CM and AOKP code reveiw where you will cherry pick from:

AOKP: [url]http://gerrit.aokp.co/#/q/status:open,n,z[/url]
CyanogenMod: [url]http://r.cyanogenmod.com/#/q/status:open,n,z[/url]

(added screen shots to help out, don't mind the the names.... lol)
[T-Mobile, Samsung Galaxy SIII] Jamison904:
Kernel how to has been written and posted! Time for some fun guys!!! Please read before starting!!!

Kernel how to link.
[T-Mobile, Samsung Galaxy SIII] BlownFuze:
I'm trying to compile for cm10.1... is it ok to post an error here for some help? Not sure what I'm missing and google hasn't been helpful for this one.
[T-Mobile, Samsung Galaxy SIII] DsturbD:
did you follow this guide on CMs wiki? i have followed this to a tee and have compiled and installed many CM10.1 builds on my phone

http://wiki.cyanogenmod.org/index.php?title=Build_for_d2tmo
[T-Mobile, Samsung Galaxy SIII] BlownFuze:
Thanks for the reply and the link, I checked it out.

I'm actually building for my note - the only difference there, is the repos for quincyatt. So, I "think" I'm pretty good on the setup, but I've been at it for 2 days now - adding missing files and other stuff that makes the build stop, and restating the build - but this last stop has me stuck. lol
[T-Mobile, Samsung Galaxy SIII] Jamison904:
Sure man, Whatcha got? If it is huge post it on pastebin and link it here and we will take a look. Yeah working the errors is the fun part. You should of seen me setting up and building AOKP for the note 10.1 (n8000/10/13). Porting to unsupported devices you get a lot of errors.

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] BlownFuze:
Thanks man - it wasn't very big. It was 2 things... but I decided to go ahead and start over. lol - wiped out everything but the .repo folder and I'm re-syncing now.

One was something along the lines of: Proguard: /home//out/target/common/obj/APPS/Calendar_intermediates/proguard.classes.jar error unexpected eof

The other was: arch/arm/mach-msm/Kconfig:1751:warning: defaults for choice values not supported

I figured I'd start over because when I went back through to verify what I have installed on here - I noticed I didn't have gcc-4.7, and I'm running xubuntu 64bit. I'm trying to figure out as much as I can on my own, without bothering too many people. Lol. So the least I can do is make sure I have things installed that I need. :good:

Ok, I do need help. :(

Still got stuck on the same thing:

Proguard: /home/jstonge/cm101/out/target/common/obj/APPS/Calculator_intermediates/proguard.classes.jar
ProGuard, version 4.4
Reading program jar [/home/jstonge/cm101/out/target/common/obj/APPS/Calculator_intermediates/classes.jar]
Reading library jar [/home/jstonge/cm101/out/target/common/obj/JAVA_LIBRARIES/android_stubs_current_intermediates/classes.jar]
Error: Can't read [proguard.ClassPathEntry@2747ee05] (unexpected EOF)
make: *** [/home/jstonge/cm101/out/target/common/obj/APPS/Calculator_intermediates/proguard.classes.jar] Error 1
make: *** Waiting for unfinished jobs....
[T-Mobile, Samsung Galaxy SIII] Jamison904:
It is having issues building the calculator. Have you added anything else (cherry picking?) Try this, navigate to packages/apps and open terminal and do: git reset --hard then try to build again. This will reset them to the last commit. There is a big chance that there is something in the package that isn't compatible with your device as well. You will need to modify this manually if it is the case. Let me read some and I'll let you know what I find. Google proguard and cm10 and see what you find.

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] Octane70:
Like i said before your tutorial on compiling a Kernel is top notch James. Good Job!

Vary easy to use everybody, I have used a couple others, but this just makes it easy.
[T-Mobile, Samsung Galaxy SIII] Jamison904:
Thanks bro! Are you dropping your T989D kernel today?

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] BlownFuze:
No additions or cherry picks, trying to keep my first effort as simple as possible.

When I log back in to my Linux box, I'll try the hard git reset. The only thing I came up with on my searches, was possibly trying to update proguard, which would hopefully give a little more info on the error. Didn't want to mess with that yet though. I'll do the git reset and maybe re-install the sdk. I'm at work now, and normally I have time to mess around, but there's a launch tomorrow - so I'm kind of busy today. Lol

Thanks for the help man. :cool:

Here's my manifest, so you can see what I've been syncing:

<manifest>

<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-10.1" />

<project name="CyanogenMod/android_device_samsung_quincyatt" path="device/samsung/quincyatt" remote="github" revision="cm-10.1" />

<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.1" />

<project name="CyanogenMod/android_device_samsung_quincy-common" path="device/samsung/quincy-common" remote="github" revision="cm-10.1" />

<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.1" />

<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />

</manifest>
[T-Mobile, Samsung Galaxy SIII] gypsy214:
Jamison you made the Kernel guide with screenshots. thats easier for people to understand it better..., Thank you for your time putting all this together.
[T-Mobile, Samsung Galaxy SIII] Octane70:
Yea, if i get some time. I wanted to make sure the script support was functioning and it was insecure. The ramdisk was already insecure, I am was wandering if it would of done that in the rom kitchen when I built my rom.

Matt's test roms working good, nice and smooth.
[T-Mobile, Samsung Galaxy SIII] Jamison904:
Rock on! Stoked for you guys!! Yeah going through the options in the kitchen would of done this for you. Let me know when you post it! Also if you want I can help you with the install script... or you can ask Matt since he has access to a computer. They don't even let me check my Gmail here...lmao

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] Jamison904:
Yes sir! This way people aren't confused and can follow it easily. :D

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] BlownFuze:
I finally got it to build with no errors - !victory! But that included re-installing xubuntu. lol

I started by pulling out the calculator and a few other apps - but still got proguard errors.

So, I updated proguard to 4.9 - same errors.

I yanked my whole repo directory, pulled fresh from the server - same proguard errors.

Something was messed up somewhere, but there is no info out there in regards to proguard errors. I've had no issues with the kitchen or decompiling and re-compiling apks, so I figured 3 days of searching for the proguard needle in the haystack was enough.

I was on xubuntu 12, so I said to hell with it, and fresh installed xubuntu 13. Updated everything, installed all the extras, and bam - good to go. I guess I'm on my way now. Lol
[T-Mobile, Samsung Galaxy SIII] Jamison904:
Good deal man. Yeah I don't know how many times I have started over from scratch. I have to redo Ubuntu every 6 months for one reason or another...lmao

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] DsturbD:
cool that you got it working on xubuntu, would rather run that myself, but always had issues, put ubuntu 12.04 on and its been great so far
[T-Mobile, Samsung Galaxy SIII] BlownFuze:
Thanks to both of you for the help, the guide, and the links. I flashed my build last night - and everything worked. /fistpump

So now I'm ready to tackle an AOKP build. Lol... slow and steady, and I'm learning a ton as I go.

[MENTION=4518483]Midnight_Rider[/MENTION]:

I love xubuntu with xfce - slim and fast. Between this guide by Jamison, your link a few posts back, and this guide on setting up ringtail: http://xdaforums.com/showthread.php?t=2224142 , I made sure I had all my dependencies in check.

The only issue I came up with (the first issue I came across when I started on 12 actually, and carries over to 13), that is specific to not using gnome or unity for your desktop, was a connection error when I tried to do my first repo sync. "WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring blah blah blah/pkcs11: No such file or directory "

This is caused because of a module: gnome-keyring-pkcs11.so - it doesn't load for all desktops. Fixing it, is just a simple edit to: /etc/xdg/autostart/gnome-keyring-pkcs11.desktop

4 or 5 lines down in that file, is: OnlyShowIn=GNOME;Unity;

So I added xfce and xfce4 to that line and rebooted - bam repo issues toast. Just add whatever desktop you're using. Mine looks like this now (incase someone's search brings them here):

OnlyShowIn=GNOME;Unity;xfce;xfce4;

Other than that, everything is running nice. :D
[T-Mobile, Samsung Galaxy SIII] DsturbD:
that's awesome man! glad to hear it and thanks for that tip...i may just try xubuntu again. but now i'm getting used to having the close and minimize buttons on the left LMAO
[T-Mobile, Samsung Galaxy SIII] BlownFuze:
Lol - nothing like those little idiosyncrasies from distro to distro.
[T-Mobile, Samsung Galaxy SIII] Jamison904:
No kidding. Work really messes me up because of this... Hate windows

Sent from my dark hole called an office.
[T-Mobile, Samsung Galaxy SIII] goater1220:
Hey Jamison or anyone, I'm stuck I think. I attempted to start set up on this and for some reason option 4 in andadb.sh wont work for me. Also I installed option 5 by mistake. When I go into file system under media it says galaxy nexus. I tried to delete it but it wont let me, I did try to change permissions I cant even do that. Can someone please help?

Thanks So Much For This Guide Jamison!!!