Hi Everyone,
I would like to learn Android ROM development, but do not know how it is done in Ubuntu.
I have build CM7 successfully on Ubuntu 11.10 and would like to proceed further to develop ROM, but do not know how to ? I mean I know if android apps is required to be developed, then ECLIPSE is used, but, if ROM is to be developed, then how it is done ?
I mean, is there any eclipse like IDE (Development Environment) exist to develop ROM ? Can anyone guide me or provide me link how to proceed further ?
I searched a lot in google, but could not find any site which gives details on it. What I am getting on search is only setting-up the envirnment and compiling the source code, but nobody deals with how to modify or develop further on ROM.
Any help on this regard will be appreciated.
Edit: I found it, we can use eclipse itself for the editing and I think to build the source code modified, we need to proceed in the same way. Below is the link:
http://wiki.cyanogenmod.com/wiki/Loading_source_in_eclipse
Thanks
gurung_vishwas1 said:
....I mean, is there any eclipse like IDE (Development Environment) exist to develop ROM ?....
Click to expand...
Click to collapse
Win-rar..
..if you know what i mean..
Related
How would one go about development of a custom rom for the Nexus one. Are there good resources, developers out there that can help?
Thanks - Dave
This is one of those things that just happens there are no steps and guide for being a developer, take a look at the stock rom and see what you can do.
You will be better off teaching yourself than having too much guidance. Plus trial and error happens when you play around with something..If you have your build envi setup that will help and you should be using linux on your pc, you can barely do anything major from windows.
Can look at this for an idea:
http://forum.xda-developers.com/showthread.php?t=566235
You dont need to use this ---> in your title--> this is better
Please try to post here,people use this section for winmo roms and other hacks
http://forum.xda-developers.com/forumdisplay.php?f=456
Hello developers,
I'm starting this thread because I'm interested in designing a development environment for the Samsung Galaxy Tab so that developers, like myself, can have an easy environment for modifying the Android OS. I'll be aiming this environment at all Android Devices but I want to start with the Samsung Galaxy Tab.
At the moment I don't have much of a structure for this project, nor much direction, so if anyone has any ideas for what tools etc I should include in this please let me know. If anyone wants to get on board with the project it would also be appreciated. Send me an email.
tool ideas:
- integrating the GCC and Javac compilers into the environment.
- integrating a way to generate make files and to build from these files.
- GUI for editing files from the kernel and application framework.
- easy to use way of setting up branches for projects with the Repo and Git included in the Android Source Code.
Count me in. I am getting a Tab tonight and I plan to develop for it. Currently, I have got the froyo source on my machine and want to integrate the open source code that Samsung released for this device.
Has anyone successfully built a custom ROM using the Samsung source code? Any help on this will be appreciated.
Awesome!
I've got Froyo working on the Tab, which I built from the source code from the android open source project website but it's just a generic build from the straight source, nothing special. not with the samsung code though. do you have any links for it?
I've put a small amount of stuff into the Dev Environment, most just shell files etc to make installing everything easier. One click sort of thing.
My first task though is going to be to try and fix the failure that is the Samsung display driver. Most noticeable are the 4 by 1 widgets that don't stretch across the whole screen.
After that I'm going to start work on a GUI for the environment and the iOS Emulator.
thoughts?
Whats wrong with Android SDK and Eclipse?
It's not the most straight forward thing. I'm looking to make something that includes its own libraries too. It's aimed at beginning developers mostly, so you can literally download one file which includes everything you'll need then start editting and then one click to compile and have it all work. Simplicity
I'm also interested in this... The SGT is my first android device, and my company will want android apps for internal and external uses... and a one click dev environment would be a most welcome option!
DevShroom said:
I've got Froyo working on the Tab, which I built from the source code from the android open source project website but it's just a generic build from the straight source, nothing special. not with the samsung code though. do you have any links for it?
Click to expand...
Click to collapse
Straight up AOSP? Could you have a crack at CM?
Anything you need, including testers, I'm in.
I have programmed some programs in android. If you need my help, i will be glad to help,
Sent from my GT-P1000 using Tapatalk
i'm currently setting up a new galaxy Tab ubuntu 10.10 VM but I always fail at installing java5-jdk, but when im ready i'm going to have a look at the CM and AOSP source and i !try! to port CM to the tab!
I am working on a custom rom , if you need any help do not hesitate
yann06 said:
I am working on a custom rom , if you need any help do not hesitate
Click to expand...
Click to collapse
are u building from source or are you modifing a stock rom?
DevShroom said:
Hello developers,
I'm starting this thread because I'm interested in designing a development environment for the Samsung Galaxy Tab so that developers, like myself, can have an easy environment for modifying the Android OS. I'll be aiming this environment at all Android Devices but I want to start with the Samsung Galaxy Tab.
At the moment I don't have much of a structure for this project, nor much direction, so if anyone has any ideas for what tools etc I should include in this please let me know. If anyone wants to get on board with the project it would also be appreciated. Send me an email.
tool ideas:
- integrating the GCC and Javac compilers into the environment.
- integrating a way to generate make files and to build from these files.
- GUI for editing files from the kernel and application framework.
- easy to use way of setting up branches for projects with the Repo and Git included in the Android Source Code.
Click to expand...
Click to collapse
I'll be interested in getting involved in a community driven project for the SGT. I'm a unix admin with lots of experience in the OS and system development field. Interested in what ideas you have on this.
Try using openjdk. It works for me.
Sent from my GT-P1000 using Tapatalk
Thanks everyone for the positive feedback on all this! it'll be good to have as many people on board as possible.
if you have troubles downloading the sun-java5-jdk there is a good tutorial on it on this site, it doesnt come as part of the repository by default so until you add it in sudo apt-get install sun-java5-jdk will not work.
atm i am only working with AOSP not CM, i am trying to set this dev environment up for a nice simple build and then i'll start working on more complex builds so we can start developing custom roms.
@paulshields - do you know much about linux/android drivers? i wanna fix the widget sizing problem on SGT but my driver knowledge is limited
Hi,
Apolgies if this is in the wrong place, but this is the only forum I would expect to get my answer.
I need someone to point me in the right direction please. I'm thinking of compiling an ASOP for personal use from source. I have looked at the google tutorials and even though Linux isn't my weapon of choice, being an IT systems engineer I do not feel following the tutorial will be too difficult.
However, is there a more specific guide for the desire?
The tutorial builds for the development handsets eg Nexus one. Is it just a case of supplying the correct drivers, RIL and editing the product code, or is there a bit more to it than that?
Any help / direction greatly appreciated.
You could start with building ROMs from Oxygen or CM source. That way you can familiarize yourself with the AOSP project without worrying about drivers etc. (DevNull source is completely stock AOSP with drivers for the Desire etc.)
Later on, when you know how everything works, you can start your own project.
If you want to start building AOSP from Google source, you might want to read the tutorials over at Google for a couple of times + checking the wiki's over at CM. They pretty much explain everything that there's to it.
If you're looking for a guide specific for the HTC Desire, then I think you're out of luck. Most dev's over here start off with the tutorials over at android.com and even with tutorials etc. at CM.
Is DevNull definitely 100% AOSP + drivers? If so, then it would be pointless compiling from source anyway.
I already ran that through dsixda, but the options there are quite limited.
What I had hoped I could do was make a tiny tiny AOSP. DevNull is pretty small though, so maybe it can't get much smaller.
rootSU said:
Hi,
Apolgies if this is in the wrong place, but this is the only forum I would expect to get my answer.
I need someone to point me in the right direction please. I'm thinking of compiling an ASOP for personal use from source. I have looked at the google tutorials and even though Linux isn't my weapon of choice, being an IT systems engineer I do not feel following the tutorial will be too difficult.
However, is there a more specific guide for the desire?
The tutorial builds for the development handsets eg Nexus one. Is it just a case of supplying the correct drivers, RIL and editing the product code, or is there a bit more to it than that?
Any help / direction greatly appreciated.
Click to expand...
Click to collapse
Hi Dan, for a start, the best place to start would be building a Cyanogen Rom from source as per Cyanogen's guide here. This guide is specific for the Desire
My suggestion is to build/modify this source first, since it's actively supported by a community. Once you get a fair idea, you could move on to the vanilla source..
Btw..Linux knowledge isnt crucial for building it, and you can easily follow the guide
Edit: Oops, just reallized that I just mirrored Pyr0wl's advice
I've tried out almost every ROM I could find for the VZW Galaxy Nexus. They all have their own pros, but none of them were really perfect for me.
I already know Java, so I know that should help me a lot. But I do have some general questions.
My main questions is, do I compile from source? Or do I use something like JRO03L? What exactly is JRO03L? I noticed a lot of ROMs were based off either AOSP or JRO03L, or some other ROM.
When people say their ROM is based of AOSP, does that mean they edited the source code directly?
What about drivers and stuff? Do phones even have those? How do I get them for my phone?
What percentage of ROM editing is done through source code modifying and what percentage is through Cooking?
Sorry for all the questions, I'm just kinda confused.
jtvd78 said:
I've tried out almost every ROM I could find for the VZW Galaxy Nexus. They all have their own pros, but none of them were really perfect for me.
I already know Java, so I know that should help me a lot. But I do have some general questions.
My main questions is, do I compile from source? Or do I use something like JRO03L? What exactly is JRO03L? I noticed a lot of ROMs were based off either AOSP or JRO03L, or some other ROM.
When people say their ROM is based of AOSP, does that mean they edited the source code directly?
What about drivers and stuff? Do phones even have those? How do I get them for my phone?
What percentage of ROM editing is done through source code modifying and what percentage is through Cooking?
Sorry for all the questions, I'm just kinda confused.
Click to expand...
Click to collapse
compile from source needs linux (mac osx only builds master branch);
aosp = android open source project
JRO03L, JRO03R: release tags. they mark a certain landmark in android development, normally leads to/are (pratically) the same as ota's.
yes, aosp-based roms edit source then build. why would we cook when we can build? makes no sense on a aosp supported device like ours.
on linux, just install android-sdk (includes fastboot and adb) and add it to your $PATH, and create udev rules for android devices (most distros provide this as a package). no need for drivers on linux.
http://forum.xda-developers.com/showthread.php?t=1386615
http://source.android.com/source/initializing.html
sent from my i9250
bk201doesntexist said:
compile from source needs linux (mac osx only builds master branch);
aosp = android open source project
JRO03L, JRO03R: release tags. they mark a certain landmark in android development, normally leads to/are (pratically) the same as ota's.
yes, aosp-based roms edit source then build. why would we cook when we can build? makes no sense on a aosp supported device like ours.
on linux, just install android-sdk (includes fastboot and adb) and add it to your $PATH, and create udev rules for android devices (most distros provide this as a package). no need for drivers on linux.
http://forum.xda-developers.com/showthread.php?t=1386615
http://source.android.com/source/initializing.html
sent from my i9250
Click to expand...
Click to collapse
Thanks for the links
And when I mentioned drivers, I meant for the phone hardware. Like, does android just magically work on all phones? or do some phones need something extra to work with AOSP?
Now, after I set up Ubuntu with the guides above, are there any guides to the basics of source editing? Like what do I need to do to install busybox? root android? theme?
I googled on how android 'worked' , so i can get a better understanding on how it operates, but all the results were pretty vague.
jtvd78 said:
Thanks for the links
And when I mentioned drivers, I meant for the phone hardware. Like, does android just magically work on all phones? or do some phones need something extra to work with AOSP?
Now, after I set up Ubuntu with the guides above, are there any guides to the basics of source editing? Like what do I need to do to install busybox? root android? theme?
I googled on how android 'worked' , so i can get a better understanding on how it operates, but all the results were pretty vague.
Click to expand...
Click to collapse
you need to use the right words in google to find what you need. start here, look under getting started http://source.android.com/source/index.html
simms22 said:
you need to use the right words in google to find what you need. start here, look under getting started http://source.android.com/source/index.html
Click to expand...
Click to collapse
Part of the questions you're asking OP, can be solved with information available on that link simms22 and I posted.
jtvd78 said:
Thanks for the links
And when I mentioned drivers, I meant for the phone hardware. Like, does android just magically work on all phones? or do some phones need something extra to work with AOSP?
Click to expand...
Click to collapse
obviously not, that's why i said "aosp-supported devices". devices that aren't aosp supported, need the same things we need, except in their case there's the matter of proprietary frameworks and drivers (called binaries), which we have available almost from the start.
jtvd78 said:
Now, after I set up Ubuntu with the guides above, are there any guides to the basics of source editing? Like what do I need to do to install busybox? root android? theme?
Click to expand...
Click to collapse
sure, guides @github or at any other repo. there's no better guide than being able to read source code and how the masters do it.
jtvd78 said:
I googled on how android 'worked' , so i can get a better understanding on how it operates, but all the results were pretty vague.
Click to expand...
Click to collapse
@source.android.com.
tip: you'll need to learn how to git. there's plenty of tutorials around the web.
I got everything set up from google's directions, but when I attempt to build from the source, I dont have the option to select toro.
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. full_grouper-userdebug
5. mini_armv7a_neon-userdebug
6. mini_armv7a-userdebug
7. full_wingray-userdebug
8. full_crespo-userdebug
9. full_maguro-userdebug
10. full_panda-userdebug
jtvd78 said:
I got everything set up from google's directions, but when I attempt to build from the source, I dont have the option to select toro.
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. full_grouper-userdebug
5. mini_armv7a_neon-userdebug
6. mini_armv7a-userdebug
7. full_wingray-userdebug
8. full_crespo-userdebug
9. full_maguro-userdebug
10. full_panda-userdebug
Click to expand...
Click to collapse
instead, do:
Code:
. build/envsetup.sh && lunch full_toro-user && make -j4 otapackage
done.
Thanks! One more question... where exactly is the finished zip?
it tells you where it is when it finishes building..
out/target/device/samsung/toro/
sent from my i9250
I have been learning how to work in the android environment for a little while now, and want to move onto learning how to create roms from AOSP rather than other peoples existing work. This would allow a lot more freedom. The current dream is to create a JB 4.1.2 rom from AOSP, then release it as a base rom to allow anyone else to rip it up just as they want. Once developed it could be used to show examples of how to use apktool and others to customise your own rom.
Potentially the process could be documented here so that other people could build there own. I don't know how many people still use this phone, but it would be a good learning process.
So is anyone else interested? Currently I know next to nothing so we would be starting from there
I
mcgi5sr2 said:
I have been learning how to work in the android environment for a little while now, and want to move onto learning how to create roms from AOSP rather than other peoples existing work. This would allow a lot more freedom. The current dream is to create a JB 4.1.2 rom from AOSP, then release it as a base rom to allow anyone else to rip it up just as they want. Once developed it could be used to show examples of how to use apktool and others to customise your own rom.
Potentially the process could be documented here so that other people could build there own. I don't know how many people still use this phone, but it would be a good learning process.
So is anyone else interested? Currently I know next to nothing so we would be starting from there
Click to expand...
Click to collapse
I'm up.. :thumbup:
MScorporation95 said:
I
I'm up.. :thumbup:
Click to expand...
Click to collapse
Awesome, as a progress report I have so far managed to download and install the sdk, with JB4.1.2 APIs. Next I'm going to read, this is going to be a nice slow burner.
mcgi5sr2 said:
Awesome, as a progress report I have so far managed to download and install the sdk, with JB4.1.2 APIs. Next I'm going to read, this is going to be a nice slow burner.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2091353
MameTozhio said:
http://forum.xda-developers.com/showthread.php?t=2091353
Click to expand...
Click to collapse
Super! Thank you
@mcgi5sr2
Thanks! Good idea!!! :victory:
I believe you already know about that, but just in case:
- Guide Ride-From a Newbie to a Dev: http://forum.xda-developers.com/showthread.php?t=2281656
- Complete Android ROM development and essential tutorials: http://forum.xda-developers.com/showthread.php?t=1661770
- Rickys Rom Kitchen 2.0/Android Everything Tool 10.0: http://forum.xda-developers.com/showthread.php?t=2200660
bratusm said:
@mcgi5sr2
Thanks! Good idea!!! :victory:
I believe you already know about that, but just in case:
- Guide Ride-From a Newbie to a Dev: http://forum.xda-developers.com/showthread.php?t=2281656
- Complete Android ROM development and essential tutorials: http://forum.xda-developers.com/showthread.php?t=1661770
- Rickys Rom Kitchen 2.0/Android Everything Tool 10.0: http://forum.xda-developers.com/showthread.php?t=2200660
Click to expand...
Click to collapse
Thanks Bratusm,
I am still dreaming of a Vanilla for as many Androids versions as I can muster, however I have been informed it is a complete nightmare for our device, so the first step I am taking will be learning to build CM10, if I can get anything like the stability Lloir and Maxwen got, I'll use that learning to go forward, either with a Slim build or another. I doubt I will release much work as it will fall short of what others have achieved, but I will be available to help others as I learn along the way. I am already thinking of adding a what is tutorial for the SlimRom I've messed with, along with a guide to apks compiling and decompiling. The idea is to make an easy route for anyone who wants to learn what I have so far, and then they can take it and smash up other peoples roms to there hearts contents just like me
mcgi5sr2 said:
Thanks Bratusm,
I am still dreaming of a Vanilla for as many Androids versions as I can muster, however I have been informed it is a complete nightmare for our device, so the first step I am taking will be learning to build CM10, if I can get anything like the stability Lloir and Maxwen got, I'll use that learning to go forward, either with a Slim build or another. I doubt I will release much work as it will fall short of what others have achieved, but I will be available to help others as I learn along the way. I am already thinking of adding a what is tutorial for the SlimRom I've messed with, along with a guide to apks compiling and decompiling. The idea is to make an easy route for anyone who wants to learn what I have so far, and then they can take it and smash up other peoples roms to there hearts contents just like me
Click to expand...
Click to collapse
:highfive::highfive::highfive:
bratusm said:
:highfive::highfive::highfive:
Click to expand...
Click to collapse
One step closer, just built my first CM10 from source, using Maxwens and Lloirs work. There is always hope that I will be able to pull off more. tbh I'll be sitting down with some pen and paper and drawing out a map of what the blazes everything is next!