So I want to install a custom rom but I am confused as to which I should use. I've read different roms and I've seen that they have different rom "bases" like cm 10.1, aokp, aosp, and PA(does it have a different rom base?). Just a question, what is the differences among them? Please help so I can decide which to flash.
Hmmm, good question, well most of the ROMs here are build off of official ROM source and thats what it means by base and the difference between them is almost everything from ui to features and stuff like that and to know which ROMs you like try flashing the the official ROMs like AOKP, CM, AOSP, and PA and then once you find the base you like then flash the other ROMs that are customized versions built from that ROM base
Sent Via Nexus 7
All of these ROMs are built from AOSP; that's Android Open Source Project. It's where Google officially releases the source code. All custom ROMs on this type of device will be built on AOSP. If a ROM says it has CM or AOKP base, that means they built it off the source code for that ROM (which is initially built off AOSP) and added their own tweaks or whatever.
Sent from my Nexus 7 using Tapatalk HD
Related
This is my first nexus device,
i often hear how great AOSP, and AOKP is. being pure google experience.
So AOSP is pure google, and the most famous one is cyanogen team which makes cyanogen mod.
AOKP is based on cyanogen works and they add more stuff to their kang roms.
i'm seeing some roms in development thread labeled as aosp.
isn't the nexus7 stock rom considered aosp?
what's going on?
The ROMs on nexus devices are AOSP. Cyanogenmod is compiled from aosp. But with changes.
ROMs labeled AOSP will be based from 'pure android'.
Hope this answered your question
I have just rooted my newely aquired Nexus 7 land want tot install a custom ROM. At least i think i do. Can someone please explain to me what the difference is between the stock nexus 7 and an aosp rom.
I have always had custom ROMs installed on my S3 and there the difference is pretty clear. Here it seems like stock and aosp are the same. So maybe a stock based ROM like cleanrom would be a good choice?
Don't forget AOKP!
I would also like this clarifying in laymans terms, as AOSP and AOKP pickle me !
hoekzemaar said:
I have just rooted my newely aquired Nexus 7 land want tot install a custom ROM. At least i think i do. Can someone please explain to me what the difference is between the stock nexus 7 and an aosp rom.
I have always had custom ROMs installed on my S3 and there the difference is pretty clear. Here it seems like stock and aosp are the same. So maybe a stock based ROM like cleanrom would be a good choice?
Click to expand...
Click to collapse
Yes, AOSP is Google unmodified rom (base for other vendors like HTC .. etc)
Nexus 7 is Google device = AOSP rom
AOKP rom and Cyanogenmod is an open source replacement firmware for smart phones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices. (wiki quote)
Great. So installing Paranoid Android would basically give me Nexus 7 stock with some added features.
Exactly what I was after.
So, @neXus PRIME wants to make a locked bootloader-compatible ROM, aside from his wonderful AOSPA port. Now it's your choice, so choose the ROM you want carefully.
Huh one choice...
But one is not enough .-.
I know, but my hard disk space is not enough.
I have currently PA and aokp sources.
I am planning to replace aokp sources with the one you guys pick here. I can do a third too but then i will have to delete ccache space... But that is not good.
I'd like to see MIUI get updated to the latest version and see how that runs on our device because the MIUI interface itself looks pretty slick, and if possible a port of multirom would be a nice thing as well (if possible: don't know if our device is using fstab or rc)
noahvt said:
I'd like to see MIUI get updated to the latest version and see how that runs on our device because the MIUI interface itself looks pretty slick, and if possible a port of multirom would be a nice thing as well (if possible: don't know if our device is using fstab or rc)
Click to expand...
Click to collapse
I agree too
Like Paranoid Nexus, there is the chance of chosen rom to work with unlocked bootloader?
I can choice easier if I know which rom has what kind of features.
Actually MIUI seems like a good idea, plus it's a bit different when compared to the AOSP bunch.
Yeah MIUI would be cool, but if not i would love to see carbon or pacman on LBL.
@neXus PRIME
i appreciate your hard work buddy
instead of which rom you compile,i think we need advanced custom kernel like doomkernel...i'm currently using pacman 4.4.4 and none of cutom kernel present on forum does'nt works
Can we have avatar rom!
Avatar, Chameleon, AOSBam, Sonic.....wtf.... so many kangerzzz
But why is PURE AOSP winning out???
Don't know why but vanir being a ubl ROM is really fast and smooth, is it in the ROM or the optimisations by the dev??
In the feature code, ahe has mentioned many compiler optimisations, isbit because of them or the ROM????
I would have said Slimkat if bagyusz doesn't update it, but as of now i don't know if he will.
An update to the latest MIUI would be lovely, locked or unlocked BL is a matter of secondary importance for me
Apart from that Carbon, Vanir and PACman on a stock/stock-based kernel would also be nice
neXus PRIME said:
Avatar, Chameleon, AOSBam, Sonic.....wtf.... so many kangerzzz
But why is PURE AOSP winning out???
Click to expand...
Click to collapse
I think that some peoples want to have the android L version. Also they choosed Pure AOSP. This day, Google push the sdk of the android l version.
For android kitkat based, you can do MIUI Rom or if you want an AOSP, you can choose the AOKP.
The problem with android L is we'd have to check the LBL kernel modules we have work on it otherwise its another big job to update (if its even possible).
No L possible. End of story. Just vote the available choices
Well, when I was adding AOSP to the poll I didn't even think of Android L. Maybe I should have written it more precisely.
And yeah, there is a lot of work to do to make L work on LBL. The first thing that's coming to my head are Adreno drivers from 4.3(we are using them in KitKat, so it's not clean and fully working by any means). The second thing is power saving mode in L: we don't know if that's a kernel or OS feature... And there are many things that may result in a complete incompatibility between our kernel and Android L, and changing ramdisks won't help in that case.
Aren't the sources for L coming out in September? Why even talk about it now, wait till the Cyanogen team start to push the first nightlies, then we can put Android 5.0 in the conversation
I've been mucking around with Android for a while but basically stay with a ROM and what it comes packaged (or recommended) with.
Recently I've been looking around at Custom Kernels and I see they offer different options and functionality, but I lack some basic information:
I am guessing that the Kernel and ROM have to be compatible?
Is, for example a Kernel like Blu Spark or Lighting (all for OP5 and Nougat) compatible with all OP5 Nougat ROMs or is it ROM by ROM?
I looked over the pages for both Kernels and also for xXx Freedom OS and didn't see any information concerning compatible ROMs or compatible Kernels, is there any place/list that shows the compatibility of ROMs and Kernels?
Any information, or guidance to where I can find it would be appreciated.
Very simple.
There are 2 types of kernels. One which only works on an OOS based (custom) Rom, and one which will only work on a LOS or AOSP based Rom. Most custom kernels will work on every LOS or AOSP based ROM. But... There's one negative thing about flashing custom or OOS based Kernels. You will never know how the Kernel and/or ROM will behave. There's no 100 percent guarantee if a custom Kernel or ROM are made for each other. Even if a Kernel which comes with the ROM is no guarantee for working properly. There's no such thing as "Stable" even with ROMs. Because stable doesn't exist in a Dev World. It will always be a never ending story.
Long story short, search for yourself an satisfying combination. If you found one combination you like, stick with it and motivate the Custom ROM Developer and or Kernel Developer.
Edit: as you can read i cannot give a proper answer to your questions. The reason why a Custom ROM Dev doesn't show a list in their OP for working Custom Kernels, is mainly based on the fact that they don't like if a user flash another Kernel that didn't came with their ROM. Mostly to avoid non related ROM issues. Besides that, if you made a decision to flash a Different kernel, along with their ROM, you're on your own.
Sorry for being off-topic.
Each kernel needs to be build for each rom. Well not each rom. Each rom based on the top three. OOS, AOSP, and LOS. As each has their own kernel.
If you use LOS 14.1 or RR, then youll need a los kernel. If you run stock OOS. Freedom or xXx, youll need an oos based kernel
Not all devs build their kernels for los or aosp. Me as an example. I only have mine built for OOS and It wont work on los or aosp (well it may but you are 99.999% likely to run into a lot of problems)
I hope that clears it up a tad bit
lekiaM said:
Very simple.
There are 2 types of kernels. One which only works on an OOS based (custom) Rom, and one which will only work on a LOS or AOSP based Rom. Most custom kernels will work on every LOS or AOSP based ROM. But... There's one negative thing about flashing custom or OOS based Kernels. You will never know how the Kernel and/or ROM will behave. There's no 100 percent guarantee if a custom Kernel or ROM are made for each other. Even if a Kernel which comes with the ROM is no guarantee for working properly. There's no such thing as "Stable" even with ROMs. Because stable doesn't exist in a Dev World. It will always be a never ending story.
Long story short, search for yourself an satisfying combination. If you found one combination you like, stick with it and motivate the Custom ROM Developer and or Kernel Developer.
Edit: as you can read i cannot give a proper answer to your questions. The reason why a Custom ROM Dev doesn't show a list in their OP for working Custom Kernels, is mainly based on the fact that they don't like if a user flash another Kernel that didn't came with their ROM. Mostly to avoid non related ROM issues.
Click to expand...
Click to collapse
@lekiaM You provided a great answer and thank you. I did notice that some developers (xXx NoLimits) provide the option to select various Kernel during the install. I pretty much expected that matching a Rom to Kernel was a crap shoot to certain degree. I am going to try a few out and see how it goes.
One final question, if a Kernel offers functionality that is not offered in the original Kernel, how do you go about taking advantage of the added functionality?
Will the Kernel add those selection to the settings or will I need a different app to access them? I was thinking in particular of the don't wake on plug/unplug. I utilized some ROMs (CM) that had this feature in the setting, I use Freedom OS now and don't see that in the setting, but I see that the Blu Spark Kernel offers access to that function.
Zombie said:
Each kernel needs to be build for each rom. Well not each rom. Each rom based on the top three. OOS, AOSP, and LOS. As each has their own kernel.
If you use LOS 14.1 or RR, then youll need a los kernel. If you run stock OOS. Freedom or xXx, youll need an oos based kernel
Not all devs build their kernels for los or aosp. Me as an example. I only have mine built for OOS and It wont work on los or aosp (well it may but you are 99.999% likely to run into a lot of problems)
I hope that clears it up a tad bit
Click to expand...
Click to collapse
It does thanks. Prior to selecting some ROMs to try, I read that AOSP required a specific ROM so I steered away from it, for now. Until I am able to become a little more familiar with the entire subject.
noncomjd said:
It does thanks. Prior to selecting some ROMs to try, I read that AOSP required a specific ROM so I steered away from it, for now. Until I am able to become a little more familiar with the entire subject.
Click to expand...
Click to collapse
An aosp based rom will install and run like any other rom you decide to flash. It comes with the stock kernel built in
Each rom has their advantages and disadvantages. Currently Im running xXx 4.0 which is OOS based with extra features and then of course my own kernel for better performance and battery
@noncomjd Good question. And honestly I've been wondering that too (most of the time) i could gave you a simple answer on that, but i wont.
A Kernel can interfere with the ROMs behavior (for example manipulate the vibration, sounds, led light strength, button behavior and so on.) But a Kernel has their limits too and also the Kernel Dev in question. Besides that , i did saw some very strange things a Kernel Dev can do to manipulate a ROMs behavior. But i wont go further in that.
Answer to your question:
Yes. A good kernel dev can overwrite or add some tweaks in the ROM itself (you won't see it while flashing, but believe me after that, some things in settings are missing or added in the build.prop) . But as i earlier said it has their limits. A good Kernel Dev is aware of their capabilities. And they mostly play save. If a kernel Dev mentioned or added a feature or something in their changelog, than the feature is there. But to enable or disable that feature, you mostly need an 3rd party app(like a Kernel Manager) to activate or deactivate their added feature.
You need a kernel tweaking app in order to change kernel settings.
You can change those settings even if you run the stock kernel, but it won't offer as much features.
There are many kernel tweaking apps available and some kernels even provide their own apps.
Thanks all for some great information. Have a good base to set out exploring a little more.
If we want to run a rom he can't (directly) we have to wait untill someone made it specifically for us. Thats fine i got it very device have its own kernel and rom integration. But if a person is using the same exact tree as official one do then why it is difficult to run stock apps directly w/o proting them.
Is it because of some legacy or copyright problem. One can build a rom on its own w/o having a team(like los, rr, paranoid).
Why porting is necessary? I would like to know that too
Sent from my Moto G4 Plus using Tapatalk
Cause you dont have updates
I am not a code/programme guy,
But what i have learned is, these different ROMs (Stock, AOSP based, Lineage based) have 0 (zero) interchangeability to their stock apps (except common apps). These may be because they use different codes?
For example, lineageSU addon will work only on lineagebased ROMs. Moto apps will work only on stock.
This looks like this apps are coded in way that it run only for specific ROM/device,
If you want such apps you need to modify it..
About ROM,
There are 4 sources/trees, 1)vendor 2) device 3)ROM 4)kernel.
Vendor, kernel, device tree can be used same for any ROM,
but ROM source is different for each ROM, which defines what is base of that ROM. You cannot build stock based ROM, you can only debloat,deodex, and modify stock ROM...
So, on different ROM, you need to modify apps to run...
@DgnrtnX I recommend to read that article about blob's so you get a better understanding why there's so much effort needed to "port" apps for example: https://www.xda-developers.com/came...opers-make-hardware-work-without-source-code/