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.
How to add cm12 theme engine to a rom please someone help me how to port it to other rom as paranoid android lollipop version and many other roms have it so please help me by telling how please............ many other also want this feature to be implemented to other roms
someone please help
I am no themer, but if a ROM properly supports the CM theme engine, it should already work on their rom. Inly difference really should be some of the icons. If they made their icons default to the secondary color scheme in your theme, it should automatically be colored.
If you know how to cherry-pick features on github and how to build a rom, you can easily add it. Just take help from any dev and they would be more than happy to help you but nobody will have the time to teach you how to use github and build roms, cherry pick features.
You'd need to build from source and add the correct commits.
Transmitted via Bacon
Do not post "Thank you" type responses.[SIZE=+3]ALL ROMS EVER (Intro to be added)[/SIZE]
[SIZE=+2][INDEX][/SIZE]
[SIZE=+2]Helpful Information[/SIZE][SIZE=+1]Welcome, this thread has been created to encompass everything you may need for your android device. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread, or create your own thread in the Q&A forum. Do not use this as a general help thread.
Since most ROMs are MM now I will split ROMs in this thread into 2 sections, MM and EOL.
This thread probably isn't going to help anyone. If it does help you, however, please tell me the usage in a post!
Please tell me if I made any mistakes in the categorization, and add on new ROMs as they come out/those which I forgotten to add.
Lastly, Stock-Based ROMs will not be added unless it is being ported to other devices eg. Xperia ROM ported to XOSP to other devices[/SIZE]Click on a Link below for More Info
MM ROMs
Toolchains
EOL ROMs
Kernels
Useful links any general index should have
http://forum.xda-developers.com/showpost.php?p=65849943&postcount=34
*Forum Rules | New Users Guide | XDA Tour | Report PostsPlease look for a similar INDEX thread when visiting another device forum.
If you would like to create an [INDEX] please Click Here.
A special thanks to everyone who contributed to the production of this INDEX
Please note: This is and will be, an ongoing WIP
MM ROMs
*Mainly* CM-Based:
CyanogenMod
Temasek's CM
PAC ROM (And their cute but old website copyrighted 2014)
AICP
BeanStalk ROM
BlissPop ROM
AOKP
Resurrection Remix
XOSP
crDroid
CyanPop
OctOS
Marsh
MoKee
LiquidSmooth (+Slim base)
FlexOS (This is relatively obsolete as compared to Team Flex's AOSP-based Flayr OS)
OwnRom
TeslaOS (Not to be confused with Tesla by GZR)
*Mainly* AOSP/CAF-Based:
Dirty Unicorns (And CAF)
Pure Nexus
Cyanide L MM (Apparently it isn't Cyanide M) (Un-merged with Fusion from VrToxin)
OmniROM
Tesla by GZR
Slim
YAOSP
SlimYAOSP (Repo Init THIS first)
Nameless ROM
Broken ROM
Chroma ROM
MoKee
UberMallow (Previously OptiPop)
CandySix
FlayrOS
Exodus ROM (Quite confused as to which manifest to link to)
Validus by GZR
TipsyOS
OrionOS
Screw'D AOSP
AOSiP
ZephyrOS
BenzoRom
Beltz Rom (AOSP with DUI)
Cardinal AOSP
Citrus CAF
Evervolv
CopperHead OS
Toxic OS
All Purenexus and Slim mods from the guys at http://forum.xda-developers.com/slimroms/general/rom-builders-collective-t2861778
Toolchains
Guide for using below TC
UberTC (And Github) (For Pre-Built TC refer to BitBucket)
Linaro
SaberMod (Pre-Built TC at their website)
Hyper Toolchains
DragonTC
Christopher83's custom TC builds
Archi's Toolchains (Change the branches to change TC)
EOL stuff
VrToxin (Apparently some internal strife)
Fusion (Merged with Cyanide to VrToxin, then VrToxin died)
Archidroid/Archikernel (Should be getting a revive soon since Archi got an OP2)
Perseus Kernel (IDK why it died, too long ago)
Minimal OS (IDK why it died. Wanted to build this in particular because LP Minimal is awesome but suddenly github activity stopped)
Paranoid Android (RIP will miss you guys. They got "bought over" by OnePlus to dev OxygenOS)
F-AOSP (IDK why it died.)
Yank Kernel (I think he just gave up or something)
[*]80% of Dirty Unicorn (Went over to some Russian company) (Hi Mazda/Alex Cruz)
Euphoria OS
RadonX
Nexus Experience
Custom Kernels
AK Kernel
Lightning Kernel
Agni kernel
Arter97's Kernels
Boeffla Kernel
Franco Kernel
ElementalX
Phasma Kernel
Kylo Kernel (Same as above...???)
Some random modded kernels mostly in Nexus forums I didn't bother to add
RIP people.
A filler and awareness post.
See you in heaven. I know you are in a better place now.
TonyStark
FlashVetrin
Please add on. So far I only know of those two ^^
Garbage Link Collector
Another Link Collector (But not structured so Garbagely)
A ROM Building Guide for you to build ANY ROM on this list
XDA New User Guide
How to shake off "n00b" status
How to get Moderator's attention (Don't waste their time unnecessarily though )
Requests to Mods (All users welcome)
Logcat (MEOW)
Commonly used acronyms on XDA
How to become RC/RT
Signature Code Sharing
Archi's Optimisations (And for MM)
Index Project
Ask Away Project
Anti-Piracy/ContentGuard
NEED-TO-READ 1
NEED-TO-READ 2
Special thanks to:
@Trafalgar Square
@sd_shadow
@kuzibri
@zelendel
And everyone else at the Index Thread!!
Temporary to-do:
CarbonROM
others?
limjh16 said:
Last one
Click to expand...
Click to collapse
I would add descriptions and differences between rom types
https://en.wikipedia.org/wiki/List_of_custom_Android_firmware
http://android.wikia.com/wiki/Category:Custom_ROMs
http://lifehacker.com/5915093/five-best-android-roms
Sent from my KFFOWI using XDA Labs
limjh16;65315332
said:
CM
AOSP
Others
Kernels
Dead ROM/Kernels
Useful links any general index should have
[/INDENT][/INDENT]
*Forum Rules | New Users Guide | XDA Tour | Report PostsPlease look for a similar INDEX thread when visiting another device forum.
If you would like to create an [INDEX] please Click Here.
A special thanks to everyone who contributed to the production of this INDEX
Please note: This is and will be, an ongoing WIP
Click to expand...
Click to collapse
Hi,
sofar, so good. Would it be an idea to also add an item which devices are supported and which not? I would remove the item "Dead ROM/Kernels", they are of no use for your thread and may cause confusion.
kindest regards,kuzibri
Here is a big list of porting and compiling rom guides
[Guides][Updated] All Guides @ One Place By Hpsgill by Hpsgill
kuzibri said:
Hi,
sofar, so good. Would it be an idea to also add an item which devices are supported and which not? I would remove the item "Dead ROM/Kernels", they are of no use for your thread and may cause confusion.
kindest regards,kuzibri
Click to expand...
Click to collapse
That item is meant for stuff like AOKP where its dead, but for those who want kitkat then they can refer.
sd_shadow said:
Here is a big list of porting and compiling rom guides
[Guides][Updated] All Guides @ One Place By Hpsgill by Hpsgill
Click to expand...
Click to collapse
Will have a look and add to useful links section.
This thread is gonna take really long to get updated I am very busy with school haha...
limjh16 said:
This thread is gonna take really long to get updated I am very busy with school haha...
Click to expand...
Click to collapse
Why did you choose to start such a thread, which is very time consuming, when you are so busy with school? If I were you, I would restrict your available time to make an index thread of your own devices (i9305 or SGS3-LTE). I can understand your wish of creating the thread that's in your mind, but you do need/have the time to create and maintain it, which is IMHO almost impossible when you are also at school. If you still want to create this ALL ROM EVER thread, ask help from other members to help you, cause you cannot do it on your own. Nevertheless, if you still want to continue with this ALL ROM Ever thread, I'm willing to help you where ever I can. :good:
kindest regards, kuzibri
kuzibri said:
Why did you choose to start such a thread, which is very time consuming, when you are so busy with school? If I were you, I would restrict your available time to make an index thread of your own devices (i9305 or SGS3-LTE). I can understand your wish of creating the thread that's in your mind, but you do need/have the time to create and maintain it, which is IMHO almost impossible when you are also at school. If you still want to create this ALL ROM EVER thread, ask help from other members to help you, cause you cannot do it on your own. Nevertheless, if you still want to continue with this ALL ROM Ever thread, I'm willing to help you where ever I can. :good:
kindest regards, kuzibri
Click to expand...
Click to collapse
I didn't expect my first term of school to be so hectic, I created this before my term started. It's alright, I'll just leave this here. Not like anyone except you and sd_shadow comes here... but I'll try to update once a week.
To be honest most won't bother as not all roms are available for all devices.
Also don't put any fair in what someone else thinks of a rom. Their opinion almost never really matters.
zelendel said:
To be honest most won't bother as not all roms are available for all devices.
Also don't put any fair in what someone else thinks of a rom. Their opinion almost never really matters.
Click to expand...
Click to collapse
Hmm true... But I created mostly for me cuz I was just going around xda finding a ROM to build so I thought this thread would help.
limjh16 said:
Hmm true... But I created mostly for me cuz I was just going around xda finding a ROM to build so I thought this thread would help.
Click to expand...
Click to collapse
No sure where it would help but ok. Going around building roms from other groups will not last long. More and more teams are closing their source and not letting others use it.
So if your worried about building then I would start my own project and start from scratch with it. Aosp not CM
zelendel said:
No sure where it would help but ok. Going around building roms from other groups will not last long. More and more teams are closing their source and not letting others use it.
So if your worried about building then I would start my own project and start from scratch with it. Aosp not CM
Click to expand...
Click to collapse
Well I just started learning how to build so idk how to start off my own ROM project... But I am interested...... Teach me please...?
limjh16 said:
I didn't expect my first term of school to be so hectic, I created this before my term started. It's alright, I'll just leave this here. Not like anyone except you and sd_shadow comes here... but I'll try to update once a week.
Click to expand...
Click to collapse
Hi,
it's no problem that it will take longer that you thought initially. I agree with @zelendel regarding this: "So if your worried about building then I would start my own project and start from scratch with it. Aosp not CM" Cyogen Mod is a world on it's own and accepted as a fully functional OS. Regarding the fact that only sd_shadow and I, besides zelendel now, only visit your thread, is logical because it's a WIP.
kindest regards, kuzibri
Hi Folks,
I'm trying to port B2G to my moto g3. I was referring to this doc (https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Porting_B2G_OS/basics). However some of the things mentioned in this doc are not clear to me. Could you please help me with the below issue.
I'd like to build the AndroidKernel from source. So where should I include the below lines? Is it in this file?
https://github.com/LineageOS/android_device_motorola_osprey/blob/cm-14.1/rootdir/etc/init.target.rc
HTML:
on early-init
start ueventd
import /init.b2g.rc
Also if I understood correctly. building the kernel from source doesn't require to unpack , edit the init.rc file and repack the kernel from the device. Could you please confirm this?
Thanks,
Arun
Hi Arun,
I totally understand your frustration with this. You'd like to contribute to the Servonk project but first you need to port B2G to your phone or buy a new phone. Since the only other supported phones are the Z3 compact and Nexus 5, both of which are still relatively expensive secondhand, you want to use your Moto G3 which means first porting B2G to it.
So, I think there are two options you have:
1. Port direct from the AOSP code
2. Port from the CM12 code.
As Gerard said in telegram, porting from CM to B2G was never finalised so may actually require more work. However there may actually be more people here who can help you since people seem more familiar with CM than AOSP (in general, I know some people are very knowledgeable in both).
I see you've posted in the AOSP 7.1.1 kernel thread. Unfortunately, for the Servonk project you currently need a Lollipop based build, so 5.x AOSP kernel or CM12.x.
It might be worth asking a mod to move this thread into one of the development sub-forums.
As you know, this is the limit of my knowledge, but I really hope you find some success, if would be great if you could contribute to the Servonk project.
Your last option is to use the desktop build of Servonk, based on Glutin instead of Gonk, but I understand that you really want to get Servonk working on your phone.
Best of luck
My Question Is How Will the Custom Rom Made From The Aosp Base??
I Really want to learn the Android Custom Rom Development.(Again I'm Telling That I'm Not asking about complier or bulid the rom). I'm asking about the source and how it is made.
I Want To Be a core member.
Giving a Guide To This Question Is Highly Appreciated!!
Thank You Guys
(t.me) is a good place, they use SDK and Android Kitchen etc.
JaswanthTeja said:
My Question Is How Will the Custom Rom Made From The Aosp Base??
I Really want to learn the Android Custom Rom Development.(Again I'm Telling That I'm Not asking about complier or bulid the rom). I'm asking about the source and how it is made.
I Want To Be a core member.
Giving a Guide To This Question Is Highly Appreciated!!
Thank You Guys
Click to expand...
Click to collapse
Custom ROM sources require that the stock source code be made available to the public by the manufacturer/carrier of the device. If the stock source code for a specific device has not been made available to the public, developers can not create custom ROM source code for that specific device. Developers use the stock source code to create the custom ROM source code and then ROMs are built using the custom source they created. I think that is the answer you were really looking for. You want to know how the source code itself that the ROMs are built from is created. You aren't asking about the fruit that comes from the tree, you are asking where the tree that bears the fruit comes from. Am I right?
The only way to get custom ROMs on devices that do not have stock source code made available is to port custom ROMs from a similar device with the same architecture that does have available source code and custom ROMs made for it.
OldNoobOne said:
(t.me) is a good place, they use SDK and Android Kitchen etc.
Click to expand...
Click to collapse
I don't think that is what they are asking.
Droidriven said:
I don't think that is what they are asking.
Click to expand...
Click to collapse
Yeah, I Want To Know About Android Arc
JaswanthTeja said:
Yeah, I Want To Know About Android Arc
Click to expand...
Click to collapse
I answered the question. If you specifically want to know how developers convert stock source code into custom ROM source code, you probably will not find that answer here. Most of the people here work with the stuff that the LineageOS team creates from stock source code after the custom ROM source code has been created, they are not part of the process involved in creating the custom source code. It is like being a construction worker, the construction worker does not create the material that he uses to build a house, someone else creates the materials and then he uses what they created to build a house. Google and the LineageOS team create the material, the developers here use what they created to build the ROMs here.
You should try going to github or the LineageOS website to ask your question.
Droidriven said:
I answered the question. If you specifically want to know how developers convert stock source code into custom ROM source code, you probably will not find that answer here. Most of the people here work with the stuff that the LineageOS team creates from stock source code after the custom ROM source code has been created, they are not part of the process involved in creating the custom source code. It is like being a construction worker, the construction worker does not create the material that he uses to build a house, someone else creates the materials and then he uses what they created to build a house. Google and the LineageOS team create the material, the developers here use what they created to build the ROMs here.
You should try going to github or the LineageOS website to ask your question.
Click to expand...
Click to collapse
cool