Develop Bugs

Compiling Android for the Epic.

Hey Guys,
I've noticed many other phones have guides explaining how to download and compile Android for their phones including proprietary drivers and misc files. I know CM6/CM7 and MIUI all are very clearly doing this but I was wondering if we could get any kind of documentation like that for the Epic? It doesn't have to include any super detailed coding information other then how to download AOSP, Samsungs required drivers, and build them into a "working" rom of some kind..
The drivers and kernels you guys have been using so far must be available via some kind of git command..
I'd love to be able to compile a ROM just to learn about it lol.
Think a quick and dirty write up for compiling a rom could happen? I think it would really help incoming developers and newbies alike.

+1 on this.

+1 as I would like a good starting point...
Samsung Epic using Team Viper's latest ROM and kernel

I'm glad to see some support for this. I sincerely hope a developer takes this seriously enough to help us out!

I'm answering my own question here
Check it out... it's how to build CM for the epic. Anyone interested in learning the process could probably follow this guide and accomplish it. Took it from the CM post in General.
http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Epic

Thank you! That is very interesting. I must try it!
Sent from my Shoe.... I mean my Samsung Epic

mxcoldhit said:
Thank you! That is very interesting. I must try it!
Sent from my Shoe.... I mean my Samsung Epic
Click to expand...
Click to collapse
I'm trying it now for fun... still downloading the source... the first repo sync takes a while, I believe it's a few GB's in size..
I don't believe this includes the kernel though... I'm sure it's posted somewhere for those interested in looking at it.. just gotta dig around.

TheDub said:
I'm trying it now for fun... still downloading the source... the first repo sync takes a while, I believe it's a few GB's in size..
I don't believe this includes the kernel though... I'm sure it's posted somewhere for those interested in looking at it.. just gotta dig around.
Click to expand...
Click to collapse
way to go, man. keep us posted...

yogi2010 said:
way to go, man. keep us posted...
Click to expand...
Click to collapse
Steps seem to be broken.. the ./get-rommanager and ./getgooglefiles -v HDPI or whatever both don't work because of broken web links.
Seems this hasn't been updated in a while..
I tried to go on without them following the directions but it doesn't work, says something about the vibrant? idk.. I think the directions would need updating to work properly.. at least the code was fun to look at.
Still hoping a developer can teach us how to compile lets say just 100% AOSP for our phones using our progress so far with the drivers.. i think the drivers need to be their own branch of code so all devs can use them for their own roms.. maybe it's already like this? Idk pretty new to rom compiling.

Porting Roms from *** To the Evo

I assume this is the correct forum otherwise please move this.
What is the best article(s) to read if you want to start learning how to port roms from other android phones to the Evo? I've been searching on here and on google and it seems most articles are either outdated or only talk about editing existing cooked roms so I finally broke down and posted this. Yes I do use Linux and I do program in Java and .NET and do have a bachelors in software development but I have just never looked into doing this type of work until now.
Thank you, any direction I'm pointed in is appreciated.

I'll direct to you the Q&A forum.

Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)

sirmx said:
I'll direct to you the Q&A forum.
Click to expand...
Click to collapse
Thanks sirmx, I did do a search there but again came up short.

ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Sounds good, what I'll do is go ahead and start one, nothing special maybe even ones that already been done just to get the experience under my best.

ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk

Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is if friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.

What about something A LOT simpler like adding the CRT animations to a ROM? any pointers? Any TUT you can point me to?

ThatSmartB0y said:
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
Click to expand...
Click to collapse
Oh I hear ya. Just throwing in my 2 cents. Found that having a clean updater-script is half the battle.
Sent from my PC36100 using Tapatalk

I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App

Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.

evomattnc said:
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well said. People love to flame anyways and XDA is famous among other Android forums for being so harsh. This thread helped me out big time, and it's especially nice to see Leoisright and myn in here giving up a few pointers, because I too was curious about porting. I never worked up the confidence to ask, just too worried about it being passed over or getting flamed because I'm young and curious.
Sent from my PC36100 using XDA App

Yah, Q&A never got me anywhere, i learned off of trial and error, still learning now.
EDIT:OP:IF you want you can ombine mine and leo's tuts together, to make this thread permanent.

Subscribed!!!!!!!!
Good stuff!
Sent from my PC36100 using Tapatalk

Yeah I want to thank the devs that have stopped by so far and gave tips, already using them . Hopefully most of them drop In at least once and leave one tid bit that would make this thread awesome!
Sent from my PC36100 using XDA App

Ha, you taking applications for an apprentice myn?
myn said:
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

Yes I was afraid to post this at first which isn't good, you shouldn't be afraid to ask questions but I get that sometimes the same questions have been answered 100 times prior so I understand the quick to judge portion of it. But I want to thank everyone who has contributed tips, advise and places to start. Thank you.

Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
So I've been looking at beyond compare, did you use this from everything and just edit all the non evo files to match existing evo ones from within windows?

[VMWare] Android AOSP/ROM Developer Environment

Dear community,
I made a AOSP developer environment for VMWare Workstation 8 or latest VMWare Player (free).
You can easily compile AOSP ROMs without having to set the whole thing up.
You can use this VMWare image as a base to build AOSP ROMs. Imade it for those having trouble getting it to work or maybe if you don't have time to set it up properly. Well if you are downloading this you might have a good reason!
This kit is Google Nexus ready! You can easily compile a AOSP ROM without knowing a line to code.
This VMWare image is:
- ICS ready
- Gingerbread ready
- Fully updated
- Ubuntu 10.04 LTS
- Eclipse SDK + ADT
- Android Kitchen
- Froyo and lower is not supported.
PASSWORD: root
Download link:
Part 1 - Stable v1
Part 2 - Stable v1
Part 3 - Stable v1
Image is extracted, where do I start?
Continue from this link
Donation
Donations are always welcome!

Really really really thanks to you

Great idea. Only one issue.
Any chance we can get some other mirrors?

Oh come on, you asking for donations for this? you looking to buy a nexus and need help?
"Compile a rom without knowing a line of code?" Things can get messy with building you know.
How about informing people what branch is the repo tracking, or what commits will they have to get to sucessfully build..like oprofile (if not on master branch), gtest, slang..not to speak how to use gerrit or git..
It's great you spent time putting all this together, uploading it.. but there's really more to it than just linking to source.android.com.
Also, one last thing, why did you pull gingerbread tree when this is a sub forum/thread for galaxy nexus, which is ICS native?

FYI, Google says that to build AOSP in a VM, at least 16GB of RAM is recommended.

Chirality said:
FYI, Google says that to build AOSP in a VM, at least 16GB of RAM is recommended.
Click to expand...
Click to collapse
I managed fine with 4gb on my work machine, for some reason though Virtual Box wont build it on my laptop at home
Going to try this method, op thanks for this do I need all three links? or is that three mirrors?

Huge thanks, will definitely help lots of people get started in ROM development.

spences10 said:
I managed fine with 4gb on my work machine, for some reason though Virtual Box wont build it on my laptop at home
Going to try this method, op thanks for this do I need all three links? or is that three mirrors?
Click to expand...
Click to collapse
On your work machine, are you doing the build on the bare metal or in a VM?
I've kind of suspected that Google may be overstating things a bit when they said 16GB minimum for a VM, but never had a chance to test it out myself...

Can you please upload to Megaupload or Multiupload please??

It's not hard to set up an environment....a quick google will give you about 5 commands that you can run and you're ready to start syncing with the AOSP repository. And tbh, I personally prefer VirtualBox over VMWare.

Chirality said:
FYI, Google says that to build AOSP in a VM, at least 16GB of RAM is recommended.
Click to expand...
Click to collapse
I assigned 4GB and 8 cores to my virtual machine and it was done in less than half an hour on a 2630QM
More mirrors are coming. I am currently working on making the VMWare image smaller in general!
I will possibly take out most applications which are not related to development. I might also take out libreoffice and other big softwares as most of you can install libreoffice etc on your host machine.
I promise I will make everyone happy here! But understand why it's taking so long. I am currently having exams in university. You have to understand that comes first!

djjonastybe said:
Dear community,
I made a AOSP developer environment for VMWare Workstation 8 or latest VMWare Player (free).
Click to expand...
Click to collapse
This would be useful if you didn't have to wait 12 hours (literally) to download it. Can't donate or download when 12 hours is the price tag. It's too much time. Get the files up on a faster file share and I'll download and donate for sure. It's a great idea and I appreciate it, but 33k a second xfers isn't going to cut it for me

djjonastybe said:
I am currently having exams in university. You have to understand that comes first!
Click to expand...
Click to collapse
I totally understand that one! Thank you for this and hope your exams go/went well!

Superb! thanks a lot

Doesn't it say to use 16gb of ram+swap?
Sent from my Galaxy Nexus using xda premium

dfube said:
Doesn't it say to use 16gb of ram+swap?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No, I build it on my machine with 4GB of ram (and no swap due to an error ). Haven't tried it in VMware or Virtualbox though, but you don't need 16 GB of ram.

Amazing!
Sent from my Galaxy Nexus using xda app-developers app

bk201doesntexist said:
Oh come on, you asking for donations for this? you looking to buy a nexus and need help?
"Compile a rom without knowing a line of code?" Things can get messy with building you know.
How about informing people what branch is the repo tracking, or what commits will they have to get to sucessfully build..like oprofile (if not on master branch), gtest, slang..not to speak how to use gerrit or git..
It's great you spent time putting all this together, uploading it.. but there's really more to it than just linking to source.android.com.
Also, one last thing, why did you pull gingerbread tree when this is a sub forum/thread for galaxy nexus, which is ICS native?
Click to expand...
Click to collapse
+1 :good:

I Hope Someone BUILDS This Open Source ROM for SPRINT.... (Chameleon OS)

I hope some devs will take on the task and bring Chameleon OS to Sprint devices like the s3 or Note2. I'll be donating to the cause.
www.Chameleonos.org
Sent from the Mars Rover.

Prolly wouldn't be to hard if a dev was interested as they already have it for vz and att s3's...I also wouldn't doubt some of our more advanced users around here could get one of those 2 versions working on a sprint phone.

If there's source code, it's totally possible. Using the cm10.1 branch as a base, that is.
Sent from my SPH-L710 using Tapatalk 2

Thats a yes. Sounds cool from what I read, could be easily ported since its based on CM as well and the d2vzw has it
Since we originally based ChameleonOS off of CyanogenMod, any device that has official support for CM 10.1 will be easy to convert so that it builds for ChameleonOS
Click to expand...
Click to collapse
I'll try to port it over from the d2vzw, but would need some testers. Someone run this command for me and upload the file it gives (my s3 suicided)
Code:
mount > /sdcard/d2spr.txt
Also this one:
Code:
cat /proc/emmc > /sdcard/d2spr_proc.txt
Thanks

Why? It's CM10 and that's it from what it looks like. Nothing special.

MikeyLee said:
Why? It's CM10 and that's it from what it looks like. Nothing special.
Click to expand...
Click to collapse
A lot of roms resemble each other, but that doesn't mean it shouldn't be used or seen as something "special."
AOKP didn't seem special, neither did PA, but that's in the past now
Sent from my SPH-L710 using Tapatalk 2

MikeyLee said:
Why? It's CM10 and that's it from what it looks like. Nothing special.
Click to expand...
Click to collapse
Read the details on the site
But as always, each is entitled to his/her own opinion

I'd like to try this. Read it briefly and it sounds a bit like JBSourcery. Ran only that when I had my GNex.
I'd test but I live in the sticks with only 3g to download, and I'd only be able to mesa with it at night.

Certainly count me in as a tester. I was about to flash the other versions just to play around. My s3 has become more of an testing device anyways.
Sent from the Mars Rover.

CNexus said:
Thats a yes. Sounds cool from what I read, could be easily ported since its based on CM as well and the d2vzw has it
I'll try to port it over from the d2vzw, but would need some testers. Someone run this command for me and upload the file it gives (my s3 suicided)
Code:
mount > /sdcard/d2spr.txt
Also this one:
Code:
cat /proc/emmc > /sdcard/d2spr_proc.txt
Thanks
Click to expand...
Click to collapse
The second command says 'no such file or directory exist'.
Sent from the Mars Rover.

JohnnyEpic said:
The second command says 'no such file or directory exist'.
Sent from the Mars Rover.
Click to expand...
Click to collapse
Thanks, but just got everything i needed over here: http://forum.xda-developers.com/showthread.php?t=2224232
I'll start the port today, if you wanna test just PM me because I don't have a functional S3 at the moment

PM sent.
Sent from the Mars Rover.

Some unknow person contacted me some minutes ago....
I´m downloading the sources atm
I compiled chameleon os for some devices before and there should be no problem
CNexus said:
Thanks, but just got everything i needed over here: http://forum.xda-developers.com/showthread.php?t=2224232
I'll start the port today, if you wanna test just PM me because I don't have a functional S3 at the moment
Click to expand...
Click to collapse
Why do you need thos files? Everything´s up at cyanogenmods github, thought.

I'd like to test if you can be patient while I download. Will leave up to you, just PM if you'd like.

I need those files so I can change the updater-script mount points appropriately, if necessary. I can't compile it from source because my S3 isn't functional and so I wouldn't be able to pull the proprietary blobs from it, and my computer takes forever to compile too...

CNexus said:
I need those files so I can change the updater-script mount points appropriately, if necessary. I can't compile it from source because my S3 isn't functional and so I wouldn't be able to pull the proprietary blobs from it, and my computer takes forever to compile too...
Click to expand...
Click to collapse
I have a tip for you
---> https://github.com/TheMuppets/proprietary_vendor_samsung.git
Its the repo where the cm / hacksung team is storing every up-to-date proprietary blobs

fuss132 said:
I have a tip for you
---> https://github.com/TheMuppets/proprietary_vendor_samsung.git
Its the repo where the cm / hacksung team is storing every up-to-date proprietary blobs
Click to expand...
Click to collapse
Wow, hax
Whelp, looks like it's time to set up the ol' build environment again
EDIT: So my computers messed up. Some hardware issue causing kernel panics. If anyone wants to compile from source, be my guest, but I'll be porting it over (or at least trying).

First port attempt uploading now.
PM me if you'd like to test (unless you already have), I would be infinitely thankful.

Give me a few days. I'll give this a go at porting.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.

Ok. Now that this has touched a bit of spark of interest, should one of you like to start a thread in the dev section, be my guest. I believe this could gain traction in the development section.
Sent from the Mars Rover.

[Q] Developing Help

Ok guys im a total noob at developing, im pretty knowledgeable, with custom roms and kernels, but i want to start compiling my own roms from source, now i understand its not something to just jump into, but i was just wanting to get some advice for a beginner. i have osx mavericks, now im sure i can compile on osx but i not sure if its the best place to start, but if so how would i, what would i use to compile, are there any tutorials? if it isnt the right place to start should i get ubuntu, and if so, where do i start on that lol? basically just looking for someone to get me on the right path, i have some great ideas for a rom but i just have no idea what im doing. so please help me out guys, also one more thing, what about windows? thanks again guys. i really appreciate it.

The android hackers toolkit is featured on google play store this week. It gets into abd:
Sent from my SGH-M919 using xda app-developers app

Android_Monsters said:
The android hackers toolkit is featured on google play store this week. It gets into abd:
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
yeah that doesnt really get into creating a custom rom, i know pretty much all of what that book teaches, im looking for how to create and build custom roms from source, not really adb

GuyFawkes0317 said:
yeah that doesnt really get into creating a custom rom, i know pretty much all of what that book teaches, im looking for how to create and build custom roms from source, not really adb
Click to expand...
Click to collapse
If you follow almost any of the "Compile <whatever> ROM from source" threads here in XDA, you can get a pretty fair idea of how to set up your build environment and the very basics of building the ROM. From what I've seen, most tend to stick predominately to Linux compiling, but I do believe I've seen some guides for Mac. If you can't find what you're looking for on XDA, go to CyanogenMod's website; it has good tutorials for how to build straight CM10.x, which is what I would do to begin with. Since the S4 is officially supported and should compile right through problem free if you have your build environment correctly set up. Remember though, it takes upwards of 6-7GB disk space to download the source and just one build can take upwards of 20+GB.

Right, well thank you for that, I'm looking to compile an aokp rom and other suggestions
Sent My Badass Galaxy S IV Running AOKP

I would highly recommend you use a Linux build environment to build aokp roms. Just Google "compile aokp xda" and there's a guide that shows you how to do everything fr beginning to end. You can also go to infamousdevelopment.com and check out Jamison's guides on how to compile aokp. If you don't have a decent PC I wouldn't even bother honestly lol
---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------
lordcheeto03 said:
If you follow almost any of the "Compile <whatever> ROM from source" threads here in XDA, you can get a pretty fair idea of how to set up your build environment and the very basics of building the ROM. From what I've seen, most tend to stick predominately to Linux compiling, but I do believe I've seen some guides for Mac. If you can't find what you're looking for on XDA, go to CyanogenMod's website; it has good tutorials for how to build straight CM10.x, which is what I would do to begin with. Since the S4 is officially supported and should compile right through problem free if you have your build environment correctly set up. Remember though, it takes upwards of 6-7GB disk space to download the source and just one build can take upwards of 20+GB.
Click to expand...
Click to collapse
Aokp takes up more than that. Think it was 15-20GB of source and a build takes up another 25-30 and that's not even including ccache lol

GuyFawkes0317 said:
Right, well thank you for that, I'm looking to compile an aokp rom and other suggestions
Sent My Badass Galaxy S IV Running AOKP
Click to expand...
Click to collapse
I just suggested to build CM because it should build flawlessly straight after a sync on a correctly set up machine. Basically what I was driving at was pick something that officially supports our device for your very 1st test-run build; that way you aren't chasing down little errors and attributing improper environment settings/packages/etc for errors in the code.
marcoxx626 said:
I would highly recommend you use a Linux build environment to build aokp roms. Just Google "compile aokp xda" and there's a guide that shows you how to do everything fr beginning to end. You can also go to infamousdevelopment.com and check out Jamison's guides on how to compile aokp. If you don't have a decent PC I wouldn't even bother honestly lol
---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------
Aokp takes up more than that. Think it was 15-20GB of source and a build takes up another 25-30 and that's not even including ccache lol
Click to expand...
Click to collapse
15-20GB for AOKP source? Really?? Not saying you're wrong or anything, but that just doesn't sound right at all.

lordcheeto03 said:
...15-20GB for AOKP source? Really?? Not saying you're wrong or anything, but that just doesn't sound right at all.
Click to expand...
Click to collapse
Nope its about right. I think CM is closer to 30GB. Its the ONLY reason i don't develop AOSP ROMs/Kernels. Trust me, i wish i had the bandwidth to download all that. I think i calculated it to be approximately a month for ME to download I hate my internet Wish i had LTE at my home.

elesbb said:
Nope its about right. I think CM is closer to 30GB. Its the ONLY reason i don't develop AOSP ROMs/Kernels. Trust me, i wish i had the bandwidth to download all that. I think i calculated it to be approximately a month for ME to download I hate my internet Wish i had LTE at my home.
Click to expand...
Click to collapse
CM source is less than 10GB last I synced my repo. The "out" directory nudges upwards of 20GB+; but the source alone, not including the (source directory)/.repo which is just your source all packed up, is <10GB. Actually, (source directory)/.repo/projects is what you end up downloading. I'm going to bed now, but I'll double check those sizes tomorrow afternoon. I can understand how taking the contents of the whole directory with no completed builds shows up ~20GB, but you aren't downloading that much. I can download CM source on my home connection (~250KB/s) overnight.

lordcheeto03 said:
CM source is less than 10GB last I synced my repo. The "out" directory nudges upwards of 20GB+; but the source alone, not including the (source directory)/.repo which is just your source all packed up, is <10GB. Actually, (source directory)/.repo/projects is what you end up downloading. I'm going to bed now, but I'll double check those sizes tomorrow afternoon. I can understand how taking the contents of the whole directory with no completed builds shows up ~20GB, but you aren't downloading that much. I can download CM source on my home connection (~250KB/s) overnight.
Click to expand...
Click to collapse
An entire source tree, which is what you need, is close to 30GB. You may have downloaded prebuilt stuff. Or only bits and pieces. I do recall reading somewhere there was a way to only get certain things which limited the size, but actual source is very large.

I'll grab the size tonight. I use the project manifest on cyanogenmods github, and although I only have two device trees, I know for a fact that it's WAY less than 30GB.
Just checked... My CM10/.repo/projects folder is 9.1GB.
Sent from my SGH-M919 using XDA Premium 4 mobile app

Alright so I've got everything setup and running great, the only problem I have is when I try and get cherry picks, I get an error that reads as "fatal: not a git repository (or any of the parent directories): .git" any ideas why this might be happening
Sent My Badass Galaxy S IV Running AOKP

also getting this, any thoughts?
[email protected]:~/aokp_jb$ . build/envsetup.sh && brunch jfltetmo
including device/generic/armv7-a-neon/vendorsetup.sh
including vendor/aokp/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/aokp/vendorsetup.sh
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[vendor/aokp/products/jfltetmo.mk]]: "device/samsung/jfltetmo/full_jfltetmo.mk" does not exist. Stop.
** Don't have a product spec for: 'aokp_jfltetmo'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
[email protected]:~/aokp_jb$