I wrote a post(don't worry about actually reading it as it contains a lot of explanation about what ROMs are and I'm sure most of you here know that) earlier about the need for a collection of vanilla AOSP builds for as many phones as possible. Being that this is probably the biggest gathering place of Android ROM developers on the internet, it seems like the logical place bring this up.
Basically, while CyanogenMod and other AOSP based ROMs are nice, they're fairly well modified and are far from vanilla AOSP. That's great for people who want those specific modifications, but at the end of the day they aren't all that different from manufacturer Sense or Touchwiz ROMs from an AOSP point of view(even if they are better). While I don't have have any problem with these ROMs(I'll probably run CM7 on my phones once it's less buggy for me), many people would prefer to start with a vanilla AOSP ROM and add on just what they want or need.
I'm aware that there are some vanilla AOSP builds for some phones floating around out there, but they are pretty scattered and only cover a small fraction of phones. For many phones, an AOSP based ROM like CM is the closest you can get to vanilla Android.
I think a central repository of actual AOSP builds for as many phones as possbile would be very beneficial to the community. Maybe a ROM developer who ports AOSP to their device could post that vanilla build before adding in all his extras.
Just a thought, but something I think it'd be great for the community to look into.
Actually thats a nice idea.
I am a lover of stock android look.
I wish if we could make available AOSP roms for most phones.
It would be awesome !!
Related
What is the differenece between the two, also which one do you think is better.
Sent from my HTC One XL using xda app-developers app
It comes down to opinions some like sense some like aosp.... And aosp =android open source project
Aokp=android open kang project
Aosp...PA...and aokp are all stock android built directly from source
AOSP refers to Android as it comes straight from Google. Some also refer to this as "vanilla" Android. From there, manufacturers often add their own "skin" to the OS to help differentiate themselves from the competition. HTC has the "Sense" skin, Samsung has TouchWiz, Motorola has Blur, and so on. The differences can range from diverging from the "vanilla" color layouts and icons, to completely replacing some of the built-in apps (launcher, browser, music player, camera, etc.) with their own manufacturer-proprietary apps.
Really, if you are looking at custom ROMs, you should think of them as being "Sense-based" and "AOSP-based" rather than "AOSP". The spirit of the AOSP-based ROMs is to remain loyal to the AOSP or vanilla feel. But most AOSP ROMs include a huge number of customizations, extra features, that calling them "AOSP" is a big disingenuous, when they are better called "AOSP-based".
Also, some will refer to AOSP as "stock" Android, but this is confusing. By "stock", they mean as Android comes from Google. But in reality, you can also call the official ROM as it shipped with your phone as "stock" (such as "returning your phone to stock"). Since HTC never intended the phone to run without Sense, it makes it confusing to use the word "stock" for AOSP. Better to just call it AOSP.
What a person likes better is purely a matter of personal preference. Everyone has different aesthetic tastes, and expectations on features and performance. So don't let anyone tell you that one ROM is "better" than another, and don't expect to be told that either. It like asking somebody to tell you what your favorite color is.
redpoint73 said:
AOSP refers to Android as it comes straight from Google. Some also refer to this as "vanilla" Android. From there, manufacturers often add their own "skin" to the OS to help differentiate themselves from the competition. HTC has the "Sense" skin, Samsung has TouchWiz, Motorola has Blur, and so on. The differences can range from diverging from the "vanilla" color layouts and icons, to completely replacing some of the built-in apps (launcher, browser, music player, camera, etc.) with their own manufacturer-proprietary apps.
Really, if you are looking at custom ROMs, you should think of them as being "Sense-based" and "AOSP-based" rather than "AOSP". The spirit of the AOSP-based ROMs is to remain loyal to the AOSP or vanilla feel. But most AOSP ROMs include a huge number of customizations, extra features, that calling them "AOSP" is a big disingenuous, when they are better called "AOSP-based".
Also, some will refer to AOSP as "stock" Android, but this is confusing. By "stock", they mean as Android comes from Google. But in reality, you can also call the official ROM as it shipped with your phone as "stock" (such as "returning your phone to stock"). Since HTC never intended the phone to run without Sense, it makes it confusing to use the word "stock" for AOSP. Better to just call it AOSP.
What a person likes better is purely a matter of personal preference. Everyone has different aesthetic tastes, and expectations on features and performance. So don't let anyone tell you that one ROM is "better" than another, and don't expect to be told that either. It like asking somebody to tell you what your favorite color is.
Click to expand...
Click to collapse
I have always had the doubt of how do the AOSP based roms stand against Sense based roms in term of usability and stability? do thay function correctly and take full advantage of the One X hardware? It's not very clear (at least not to me) in most of the Rom's description.
korlinr said:
I have always had the doubt of how do the AOSP based roms stand against Sense based roms in term of usability and stability? do thay function correctly and take full advantage of the One X hardware? It's not very clear (at least not to me) in most of the Rom's description.
Click to expand...
Click to collapse
If you take time to read through the threads a bit, you will find that they are plenty stable, and used by many as daily drivers. Many people find them faster and more usable than Sense based ROMs. But that is very subjective.
And honestly, I can flash a ROM, and be fully configured with all apps and settings in about 20 minutes. Why not just pick a few that look good, and try them? You can read all you want, but it won't tell you for certain whether you will like the ROM or not. Only way to really know, is to try them yourself.
Since all of the bugs haven't been ironed out in cm..you will probably find more stability on sense roms on this device...but say on the HTC inspire sense is very heavy and aosp would give you better battery
a box of kittens said:
Since all of the bugs haven't been ironed out in cm..you will probably find more stability on sense roms on this device...
Click to expand...
Click to collapse
CM10.1 (Android 4.2) is in a fairly early phase, with some bugs. But CM10 (Android 4.1) has been very stable, for a very long time. As far as I know anyway, I'm almost entirely a Sense guy.
If you want to make an apples to apples comparison, there is no Sense based ROM that is Android 4.2 (they are all 4.1). So you are comparing a slightly buggy 4.2 AOSP ROM to one that doesn't even exist (Sense based 4.2). Or comparing the cutting edge to (literally) last year's model.
Again, it just goes back to the subjective nature of picking a ROM. There are probably hundreds of CM users here that will argue that AOSP performs better than Sense.
redpoint73 said:
CM10.1 (Android 4.2) is in a fairly early phase, with some bugs. But CM10 (Android 4.1) has been very stable, for a very long time. As far as I know anyway, I'm almost entirely a Sense guy.
If you want to make an apples to apples comparison, there is no Sense based ROM that is Android 4.2 (they are all 4.1). So you are comparing a slightly buggy 4.2 AOSP ROM to one that doesn't even exist (Sense based 4.2). Or comparing the cutting edge to (literally) last year's model.
Again, it just goes back to the subjective nature of picking a ROM. There are probably hundreds of CM users here that will argue that AOSP performs better than Sense.
Click to expand...
Click to collapse
Yes .. I realize cm 10 is very stable..sorry I don't know what I was thinking with that post
I have used many AOSP based roms as my daily driver, including CM, AOKP, Jellybam, and King Kang. They have always stable and reliable for me. In saying that, ViperXL (which is Sense based) is also very reliable. It comes down to flashing a few and seeing what you prefer.
There are enough roms now that we have a good choice. Please tell us about yours.
I am using Avatar ROM and it is great. The themes are very cool.
I'm on SHOstock now and I'm liking it. I'm on it mainly because of the hardware features that are not implemented in the other ROMs yet such as the hover preview in apps like SMS and the IR blaster functionality. I really want to move to an AOSP ROM, but I don't want to lose some of the stock features.
Task650's AOKP rom, and Goldeneye are the only ones I've tried so far.
I love the pure Android experience and have always loved AOKP based roms. The customization is endless. Not too mention, its very, very stable, and everything works fine. The Goldeneye rom is based entirely on the i9505 stock rom and this runs very well, as all the samsung crap is gone.
But if you're looking for speed and performance and a 100% lag-free device, go with task650 AOKP rom.
Sorry folks,
"favorite" roms and "best" rom threads are synonymous and thus are not allowed as they spiral into arguments about what is best for one vs another.
Users are expected to read and learn from all the development threads and reviewing the FAQ'a bout the ROM's themselves.
Thread closed
Hello, just got my Nexus 5 in the mail and I'm happy to join this community along with my previous device forum
But my question is what's the difference between CAF and AOSP? And how would I tell if a ROM is based on CAF or AOSP?
I did a little research myself where CAF is Code Aurora Forums and that CM is now based off of it. It's also what's behind Qualcomm's kernel work and whatnot. AOSP is android as it is now. It was formerly based off CAF but bridged off a while back then and the .libs are a lot different from CAF now. Right?
(Thanks @poondog for getting me started on this!)
But how would I be able to tell if a ROM is CAF or AOSP? Would that really impact what kernels I flash and such? (like CAF ROM only CAF kernel)
Also what would the advantages between the 2, if there are any?
Thanks a lot!
Sincerely,
072665995
bump
CAF=cyanogen 11 based roms, not all kernels work unless they state CM support in the OP which isnt many nowadays.
AOSP=the majority of roms in the original development section, also you will have a larger choice of kernels to play with.
its your choice some people have always loved CM i personally love AOSP but i have used CM in the past but with the N5 the majority of kernel development is with AOSP.
I think you could look into using multirom and test AOSP and CM at the same time but be aware of kernels not supporting CM just read the OP carefully to avoid problems.
i dont know if this helps, if not ill get my coat...
Noob question: Isn't cyanogen based off of AOSP anyway since they're both android?
paranoidsuperhero said:
Noob question: Isn't cyanogen based off of AOSP anyway since they're both android?
Click to expand...
Click to collapse
yes http://wiki.cyanogenmod.org/w/About
" So what is the difference between Android and CyanogenMod?
About 1-2 times a year, the vanilla Android operating system (known as AOSP, or the Android Open Source Project) is internally developed, then released to the public, by Google. They provide the source code to anyone who wants to download it. The CyanogenMod community, comprised of unpaid volunteers and enthusiasts from around the world, takes this newest Android code and "ports" it to dozens of new and older (aka "legacy") devices. At the same time, other CyanogenMod developers start adding features, fixes, and improvements that Google didn't include to the CyanogenMod code, which benefits all the devices. The CyanogenMod community has a whole infrastructure for people to build and test experimental versions, report bugs, and contribute back to the source code.
Sometimes features that started in CyanogenMod have appeared in newer version of "official" Android. And every time Android does a new "code dump" of their latest version, CyanogenMod benefits from Google's changes.
In this way, CyanogenMod is one (but not the only) community distribution of what started as vanilla AOSP. The Android community is vibrant, with numerous "modders" and "themers" and "performance enhancers" taking the source code and doing incredible things to it. Generally, there is a spirit of sharing knowledge and empowering people to experiment with controlling their devices, often giving old phones new life, and hopefully having fun in the process. "
Hello!
In the forums there are some really good ROM options. Because I like to be as slim as possible with the software on my phone, I prefer vanilla-like ROMs. In this case, there are two for the Moto G that seem very similar, and I would like someone to tell me the differences. One is the GPE ROM made by lost101. The other one is an AOSP build made by Alberto97.
I can understand that a difference are the apps included on each ROM. But as I can modify those after installing any of the ROMs, I would like to know if there are any technical differences between them (like drivers or internal code optimizations), something that goes beyond UI or apps. I would like the get the "fastest performance".
Any help is appreciated. Thanks!
I am not able to go into detail but I can tell you that the GPE one, since it's based on an official release by Motorola, is much more stable and trustworthy for me. I've tested countless roms and the optimized GPE one by lost101 is by far the best. Other roms are built from scratch by excellent devs, but they always end up having various problems for me... Apps that don't work the way they should, bloatware, missing or cryptic features...
Anyway, that is just my opinion.
Although I don't know why, GPE includes some proprietary frameworks and stuff, and therefore is pretty large and heavy. You might not feel it when using, though.
As for me, I'll recommend AOSP any day. Not even CM, if you want to be as light as possible.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
GPE is Motorola's version of AOSP with their own additions like proprietary drivers and apps. AOSP is the base of all Android ROMs so its as minimal as you can get
Thanks, everyone!
From your answers, I understand that the GPE version includes proprietary software from Motorola. I would suppose that these changes are for optimizations on performance and stability, so I think I will go with that as in the end the experience should be improved with those, right?
Considering how Cyanogenmod beats anything I've seen from budget OEMs (especially chinese OEMs who slap together all sorts of glitchy ROMs with annoying features), why don't they just grab CM sources and use that for their entire line instead of developing their own ROM from scratch? It's pretty obvious that people buy their phones for the price and not the "unique user experience" and Cyanogenmod is pretty awesome. The CM12.1 codebase has been pretty stable for a long time now so I'm sure it can be done.
Bump! This still weighs on my mind..