Database Info

[Q] Linking eclipse with source code and virtual device

This question is more directed towards developers, but anyone who knows feel free to contribute.
Recently i have downloaded the android source code on ubuntu and the SDK, got virtual device running and adb for my g2x. My question is now that i have the source code in my "WORKING_DIRECTORY" how can i link eclipse to the source code, and run my source in virtual device.
To sum up the question im looking for guide on creating own custom rom, it would be nice to be pointed in the right direction

Do u want to build the from from stock or CM sources
Sent from my LG-P999 using XDA App

Thanks for responding, i also have a nexus s, id assume its easier to work with nexus stock code then translate some of my work to the cyanogenmod for my
g2x, whatever is easier the get me going and understanding the concepts, So to answer the question working from stock

[Q] How to add new device/project to CM build?

Hello all,
I've forked a CM9 repo for the HTC One X and am able to successfully compile and build but I'd like to add my own repo to the build process. I'm not quite sure how everything works together yet but it seems that the default.xml may be the place where I need to make the change. Is that true? If not, how can I go about adding my own source to my CM9 workspace in order to compile and build a ROM based on my source changes.
Thanks!

Building Rom - project carbon

Hi I'm interested in building ROMs for our tf300. I've tried building ROMs before both on my desire HD and this last weekend for the tf300t, but I've always run into problems: especially when I wanna build a ROM for a device that isn't officially supported.
For instance, I would like to unofficially build carbon ROM for the tf300t.
I know how to setup the computer in Linux and its all setup. I know how to repo init. I know how to repo sync.
Now for the hard part. Correct me if I'm wrong. In order to build an unofficial ROM I would need to pull the device tree and vendor tree, right, and put them into the repo that I repo synced earlier? Then I would need to update the local manifest to include those device and vendor trees?
I have several questions about it.
First, where can I get the device and vendor trees? It seems as if drgravy has some good trees, maybe I can use those?
Second, would those device and vendor trees have the 4.2 BL support or is that a different change?
Third, would I need to change the repo to build a proper kernel for the tf300t or would the device tree or vendor tree include the kernel source? Any help would be awesome.
Also in replying to this please don't just post a link. I've read a lot about the process, I just had some specific questions.
Thanks
Sent from my Transformer Pad TF300T using xda app-developers app

[Q] Can I upload the nexus binaries to github for my rom?

Hey there!
I started a new project for a new ROM based on AOSP with some friends and wanted to know if I am allowed to upload the vendor binaries from here: https://developers.google.com/android/nexus/drivers?hl=de#hammerheadktu84q to my github for including it in the build?:silly:
Couldn´t find an answer in the license myself but I saw that it has been uploaded already in some git repos.
Thanks for your help again!

yes

Why wouldn't you be able to?

How to compile aosp source code for specific devices?

Hi guys, I'm a total noob to android custom roms, so please don't abuse me if I've just asked something very obvious to devs...
Please don't reply giving links to the aosp project, I've already seen them.
Assume I have the system needed to build from the source code.
How do I exactly configure the toolchain for a particular device(say moto g xt1032)?
Do I get configurations with the 9gb download, or do I have to download it separately? And will I be able to successfully compile a working ROM for that device?
I just wanted to know more before diving into my new project.