Develop Bugs

[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'm glad to finaly see some dev support.... but...

There seem to be lots of ROM options coming to fruition, but they all seem to be half baked and development is slow. Why not have the Dev's team up and make one awesome ROM? It is getting hard to choose between things like a working GPS or a working camera(for example only).

sp00nix said:
There seem to be lots of ROM options coming to fruition, but they all seem to be half baked and development is slow. Why not have the Dev's team up and make one awesome ROM? It is getting hard to choose between things like a working GPS or a working camera(for example only).
Click to expand...
Click to collapse
Well first of all what do you term as slow ? Samsung gave us ICS in 8 months with major bugs, withdrew it and then released it again after 2 months. Whereas the devs here had already resolved those bugs.
Again CM10 is a tough one as this is the only device with CM10. The target was end of the year but look at it we already have CM10.1 as well. So the devs here are faster than the team at Samsung who get paid for it..
As the base is the same drivers and source written for CM10, all the ROMs based on it will have the same bugs.
GPS and camera are no more an issue. I've been using the camera on my CAMP rom and no issues. Also past 2 days I've driven for 600 kms and no issues with GPS and everytime it locks under 30 secs and works very well.
For me the only major bugs left are
1. Keyboard backlight - known solution
2. Sym key - known solution
Rothorick is working on the above two and will surely come up with a fix soon. The term half baked is not something you can use for ROMs being used as daily drivers!!!
Sent from my SGH-I927

Just be glad we get anything at all. We only have one main dev and only a few others helping the process. These roms WILL get finnished but only in due time. Just take some time to relax and be patient. I have faith in dman and all his hard work is greatly appreciated here. Its the holidays let dman have his time to himself.
Sent from my SGH-I927 using xda premium

sp00nix said:
There seem to be lots of ROM options coming to fruition, but they all seem to be half baked and development is slow. Why not have the Dev's team up and make one awesome ROM? It is getting hard to choose between things like a working GPS or a working camera(for example only).
Click to expand...
Click to collapse
Errrr..... current CM10.1 has everything but bluetooth and the keyboard backlight. And dman is cracking the whip on bluetooth right now.
Also, the way you word the question betrays a misunderstanding in the process. Most of the ROM developers don't have the knowledge and experience to troubleshoot hardware compatibility problems. We have dman, that's about it. The rest of us, at best, only know enough to gesture furtively in the correct direction or unearth an important path or config file. So, fixes are implemented by dman and rolled out in his sources and ROMs, and his sources are then used by other people to build their ROMs.
---------- Post added at 02:38 PM ---------- Previous post was at 02:34 PM ----------
ninthsense said:
For me the only major bugs left are
1. Keyboard backlight - known solution
2. Sym key - known solution
Rothorick is working on the above two and will surely come up with a fix soon. The term half baked is not something you can use for ROMs being used as daily drivers!!!
Click to expand...
Click to collapse
You give me way too much credit. I only figured out half of the keyboard backlight problem -- the other half necessarily must come from dman as I don't know where to begin on getting the Android core to poke the sysfs.
As for the keyboard, we have a kludge for the Sym key. I'm working on a proper solution, as well as a fix for the voice search and dotcom keys, but in both cases, because we need changes in core classes, it's more a matter of open-source politics than technical troubleshooting.

roothorick said:
---------- Post added at 02:38 PM ---------- Previous post was at 02:34 PM ----------
[/COLOR]
You give me way too much credit. I only figured out half of the keyboard backlight problem -- the other half necessarily must come from dman as I don't know where to begin on getting the Android core to poke the sysfs.
As for the keyboard, we have a kludge for the Sym key. I'm working on a proper solution, as well as a fix for the voice search and dotcom keys, but in both cases, because we need changes in core classes, it's more a matter of open-source politics than technical troubleshooting.
Click to expand...
Click to collapse
Yup, the special hardware keys are a issue in CM on every slider phone. Hope you get a proper solution to this, so we don't have to fool around with framework-res and keyboard files

ninthsense said:
Yup, the special hardware keys are a issue in CM on every slider phone. Hope you get a proper solution to this, so we don't have to fool around with framework-res and keyboard files
Click to expand...
Click to collapse
It literally comes down to submitting patches to CyanogenMod and AOSP and hoping they see the need. We could just make builds with the patch, but we can't call them CyanogenMod or AOSP then.
Could we compile a list of devices that need extra keycodes? It'd definitely bolster our case to say "these 42 phones are directly affected by the issue solved by this patch", plus I can be more thorough.

roothorick said:
It literally comes down to submitting patches to CyanogenMod and AOSP and hoping they see the need. We could just make builds with the patch, but we can't call them CyanogenMod or AOSP then.
Could we compile a list of devices that need extra keycodes? It'd definitely bolster our case to say "these 42 phones are directly affected by the issue solved by this patch", plus I can be more thorough.
Click to expand...
Click to collapse
Can you elaborate on the the code change you are planning to submit. We can still have a patch on top of CM or AOSP, just like we have so many proprietary files from samsung.
Sent from my SGH-I927 using xda app-developers app

ninthsense said:
Can you elaborate on the the code change you are planning to submit. We can still have a patch on top of CM or AOSP, just like we have so many proprietary files from samsung.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
We need to change certain core classes like KeyEvent and a few others (there's a list in the comments in KeyEvent.java) as well as a few other places to connect the keycodes to their correct behavior. And it needs to be done in a way that works globally for all phones, not just the Glide. Which is, more than anything, a matter of convincing devs bigger than any of us that we know what we're doing, we didn't break anything, and it's a necessary change.

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.

[ROM][WIP] Carbon ROM 4.3 Unofficial 9.15.13 4.2 BL

As good a place as any to post this.
Pio-masaki.com is being shut down due to a Cease and Desist order sent against the host by Google and homeland security. I have no idea why, however until this is sorted out, and to avoid any possible or further legal issues, the site is down for a period of time that can be a day or forever. This includes any and all ROMs, kernels, gapps packages, for any and all devices, that were hosted on pio-masaki.com.
I apologize in advance for this as I know some ROMs are only available at pio-masaki.com, but it is out of my hands, the host has to consider their own safety, and has my 100% agreement and backing in taking down the site until the matter is resolved.
As this is a very large matter, and one that has us incredibly scared, I'm retreating from android for the time being, until I know what it was that I did that was illegal, and may return once this is cleared up and blows over.
After this is cleared up the hosting for pio-masaki.com may still remain offline as the hoster has some personal issues with me at this point and may or may not continue to host for me, should we resolve our differences it may return.
If by some chance Google or whoever sent the C&D notices this, I urge you to contact me as I was responsible for what was hosted, and would genuinely like to know what the issues are so we can get them resolved immediately.
I will be making similar postings or editings to any other ROM threads that link to pio-masaki.com.
As a favor I built Carbon ROM for a friend, and as it mostly works, he suggested I put it up for all of you guys to use, which I'm doing now :good:
Please refer to this thread http://forum.xda-developers.com/showthread.php?t=2137013 for a better understanding of the ROM and what it can do and features, otherwise here is some options it has:
-PIE!
-HALO
-Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature.
-Lockscreen theming
-CM skinny battery is back!
-Volume key lock on silent mode option
-Backup tool - if you're flashing a new version of Carbon and already have the required version of gapps installed, it will be backed up and restored during install. This applies to system apps and custom host files as well. Please note that you should only dirty flash from Carbon to Carbon. It's ok if it's another version or a nightly - just not over other roms. Super handy for you crack flashers. Make sure you've got the most recent Gapps though, and if you're flashing from a factory reset, you'll still need to install it after install of course.
-Long pressing the "clear recents" button clears the cache
-AOKP's awesome new navbar settings
-NFC polling mode for when you want to keep your screen off and scan tags
-MMS and call "breathe" feature. Makes the notification icon fade in and out.
-Mute dings when changing volume
-Disable/enable CRT effect on screen on/off.
-3rd party keyboard bug fixed
-deodexed again
-stability and speed enhancements
Who is Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Change Log
7.18.13
Initial release build, corrected non operational WiFi
8.06.13
Updated source, dock should now be fully funtional
9.15.13
Updated to 4.3
Built with CM's device tree and kernel source
As my tester no longer has this device, this is completely untested, reports are welcome!
THANKS, CREDIT, PROPS
Team Carbon
CyanogenMOD
AOKP
Google
Linaro
diesburg - for testing and suggesting releasing so you guys enjoy it also
Drgravy - 4.2 builds based on his device/vendor tree and kernel binary, and whoever else is included in the making of those.​

Notes, info, warnings
First and foremost, I do NOT own this device, I don't even own an Asus device, and not counting the N7, never have. I am building this blind and rely only on feedback from testers and users. As such, please remember this as you decide to yell about broken stuff.
This isn't a primary development device for me, I'm always willing to offer support on anything I release, but please don't expect daily builds. Weekly, perhaps, but it's mostly as I have the spare time to.
4.2 Bootloader only, I can not be held responsible if you flash this on any other bootloader and whatever happens, happening.
Information concerning updating and installing the correct bootloader and recovery can be found at the following:​[GUIDE]Upgrade TF300t to Jellybean 4.1 or 4.2, root, recovery & remove bloatware by krabappel2548 - please remember this is for the 4.2 Bootloader ONLY, please follow instructions for updating to 4.2 bootloader and recovery!
[GUIDE] How to install Universal Naked Drivers by tobdaryl - for setting up your PC to get going so you can root/flash/recovery/ROM your device.
[VIDEO Overviews and How To's] ASUS Transformer Pad 300 (TF300T) by AllAboutAndroids - for those who need or prefer video style instructions, swing by here and watch what they have to offer.
I'd be happy to add any additional information as it's needed, as I don't own the device I'm not real familiar with it and whats available information and utility wise. These looked like very informative threads to help users who may need a little guidance to getting ready to use Carbon on their device.
BUGS
BT does not work Rebooting will have BT working.
Some keys on the keyboard do not work
Whatever else?
​

Where can I get this?
You can visit pio-masaki.com, it's under the TF300T header, builds are always dated, and if multiple builds of the same date are made, they will include sequential build numbers, such as B2, B3, etc.
For those who don't want to go find it, here you go:
http://www.pio-masaki.com/index.php?dir=TF300T/Carbon/
Hosting for the site is made possible by diesburg for the best user experience and speed.
FAQ
Q. BT doesn't work!?
A. Reboot, BT should fire up as normal after the first reboot.
Q. HALO isn't appearing after I enabled it in settings, what gives?
A. Go into any UI besides Tablet UI (phablet, whatever you want to call its default UI mode) then reboot, enable HALO in settings, then pull down the statusbar and tap the circle icon, HALO will then appear. You can then go back to Tablet UI if you wish.
Q. I want to throw money at you / throw my daughter at you / bear your children! How can I do this?
A. Money can be freely donated (freely donated meaning in no way required or expected, however loved and appreciated as it's my only income and diapers are expensive) by clicking the donate to me link under my name to the left. Also please consider donating to diesburg for the hosting he has paid for. For throwing daughters around, maybe seek therapy, she may not like it. For children bearing, my wife wouldn't care for it, so get that out of your head. I also accept devices (old/broken/new/wet/bricked/whatever).
Kernel source: https://github.com/CyanogenMod/android_kernel_asus_tf300t
Device tree used: https://github.com/CyanogenMod/android_device_asus_tf300t

Fancy seeing you here
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta

As he posted above, when I tested, BT won't turn on. Some shortcut keys on the dock don't work. Both battery meters and the dock battery seem to be working. FYI, if you switch the UI mode to tablet mode or something, it requires a reboot for it to take. I think there may be a couple small issues with Halo. Enable halo and download any file from any site using the browser and you should see what I saw.(Hard to explain, but the download progress in the status bar never goes away, jacks your whole status bar)
And keep in mind what pio_masaki said, he doesn't have this device. So if you need help with something in the rom, how to or something, he may not be able to help, I will help as much as I can since i actually have the device. Please don't bomb him with ETA's . His main priorites for development of ROM's are for devices he owns and AFAIK, that will not change, he will release new builds when he does and until then, wait patiently.
Sent from my TF300T using Tapatalk

wigginst said:
Fancy seeing you here
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta
Click to expand...
Click to collapse
HAHA hey I didn't know you had one of these, you traitor!:highfive:

Just got it. Wife has the thrive now (still running fine now).
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta

wigginst said:
Just got it. Wife has the thrive now (still running fine now).
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta
Click to expand...
Click to collapse
I need to sell the excite and get one of these :beer:

I have really liked it so far and has a good development community.
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta

Just want to throw a reminder out... this is for 4.2 bootloader.... if you're on 4.1 you will have to upgrade.... if you have any doubt about what you are doing with the upgrade process and flashing the new recovery, please, for the sake of your own tablet, read, read, read, until you are sure about what you are doing. If you need help with upgrading the bootloader and flashing new recovery, let me know and we will post links to threads that have directions.
Sent from my TF300T using Tapatalk 2

cool to see this here going to dl and flash this
I'll let you know how it goes

pio_masaki said:
I need to sell the excite and get one of these :beer:
Click to expand...
Click to collapse
that would be a dream come true....lol....
Sent from my TF300T using Tapatalk 2
---------- Post added at 05:45 PM ---------- Previous post was at 05:18 PM ----------
Ok, just want to report that after one reboot, bluetooth turns on now. On initial install and first boot it wouldn't. I have nothing to test it with ATM though to see if it actually pairs with something.
Sent from my TF300T using Tapatalk 2

I am going to try this right away. Great to see a brand new ROM for our devices!

Man! I just flashed Jellybam v9.2 and nooww it gets released I tried building this before, but it didn't work! -_- what did you have to do to get this to build correctly. I added the device tree and vendor tree, updated the vendorsetup.sh and added a carbon.mk to the device tree, but it didn't build correctly.
Sent from my TF300T using xda app-developers app

andrewnelson23 said:
Man! I just flashed Jellybam v9.2 and nooww it gets released I tried building this before, but it didn't work! -_- what did you have to do to get this to build correctly. I added the device tree and vendor tree, updated the vendorsetup.sh and added a carbon.mk to the device tree, but it didn't build correctly.
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Likely the carbon.mk wasn't correct then. I build it for a few devices so I'm used to the way carbon builds so it didn't take much ton get it going here, drgravy's trees were 99% set already.
I'll put the trees I used up, I don't usually put them up until it works. Sometime tonight for whoever wants to tinker with the remaining issues.

pio_masaki said:
Likely the carbon.mk wasn't correct then. I build it for a few devices so I'm used to the way carbon builds so it didn't take much ton get it going here, drgravy's trees were 99% set already.
I'll put the trees I used up, I don't usually put them up until it works. Sometime tonight for whoever wants to tinker with the remaining issues.
Click to expand...
Click to collapse
Gotcha! Makes sense. Yeah I'd like to see how you got it to work with the carbon.mk. I'd like to build it for my phone too. Thanks
Sent from my Inspire 4G using xda app-developers app

andrewnelson23 said:
Gotcha! Makes sense. Yeah I'd like to see how you got it to work with the carbon.mk. I'd like to build it for my phone too. Thanks
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
I run carbon on all my devices lol. Sadly I have to build it myself since none are supported by the team.

pio_masaki said:
Likely the carbon.mk wasn't correct then. I build it for a few devices so I'm used to the way carbon builds so it didn't take much ton get it going here, drgravy's trees were 99% set already.
I'll put the trees I used up, I don't usually put them up until it works. Sometime tonight for whoever wants to tinker with the remaining issues.
Click to expand...
Click to collapse
if you put up a frameworks_base I may submit a pull request to get the dock functions working

Drgravy said:
if you put up a frameworks_base I may submit a pull request to get the dock functions working
Click to expand...
Click to collapse
Its on their github, carbondev. I'm sure its broken because the asusdec and something else didn't get along with the framework yet, unlike cm there's no real dock support in Carbon. Now that WiFi and I suppose BT are working it looks like only the dock stuff is left.

Gr88 to see pio posting stuff for our tab
His builds are quality :thumbup:
Will d/l and report back.
DNA | ⓣⓐⓟⓐⓣⓐⓛⓚ | TF300T

[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$