mobile

• How many times did you saw your developers releasing new ROMs or new version?


• For sure many times, and then you asked yourself how is this guy doing all these stuff?
  Well, i'm telling you that maintain a ROM is almost nothing than create a ROM.

Usually there are 4 kind of ROM developers:

1. Those who Create ROMs and got a public repo with all the stuff included (forked repo or their own ones)


2. Those who port a created ROM for an other device (device which is not supported officially) by adapting kernel sources, propietary files and vendors....


3. Those who maintain a ROM for a specific device which is not officially supported but he is taking the modified files from the 2 kind of develoopers in order to succed the compilation process


4. Those who maintain a ROM for a device that is officially supported by the team or organization but the user also has the goal to help the users and know what he is publishing on the forum

We all know that the Bosses of all are Cyanogenmod, OmniROM, AOSPA and after them there are the secondary ROMs which can be: PAC-MAN,Slim,AICP and so go on....
But why someone can create and you not? (By someone i mean a team or even a single person)

That's because your are thinking from a different perspective.
Let me show you:

For sure you are thinking that "Oh my god there is too much coding for me i can't do all these stuff alone"

Belive me i was also thinking in the same way but looking here and there i learnd how to do many things that for example 2 years ago was something unknown for me cominng from a different planet. But trust me here i will explain you all you need to know about how to create a ROM for yourself and then compiling it for a device (Not necessary an organization for how many devices but a small one just to get familiar and to help you starting from there)


So in this guide i will not show you how to compile a new ROM because i assume that you already know this, but i will show all the common things that can be changed and even also added in a ROM by eliminating also the CM name as much as possible by including your ROM name instead and also showing you strategies which may help you.

1. Knowledge and experience in compiling ROMs


2. Github knowledge (Usually you should know this if you compiled a ROM for a device)


3. Basic knowledge about XML, Java, C (At least know how to work on it not NOOBS on this OK?)


4. Good computer running Ubuntu (14.04/14.10/15.04)


5. High quantity of storage for all the file which you will gonna use.


6. SmartGit which it will help you very much

*******************************************WIP**** ******************************************
For the fact that the Guide will be very long and i'm doing all this alone it will take some time to complete it all,so be patient but i will leave here the staus for every part of the guide:

1- Introduction (First post) (Completed! )
2- SmartGit Part (Work in progress)
3- Repo part (Work in progress)
4- android_build (Not started yet)
5- Framework (Not started yet)
6- Packages (Not started yet)
7- vendor (Not started yet)
8- F.A.Q (Not necessary in this moment)