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. "
Related
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 !!
I'm back in the android world again and bought a Samsung phone thinking that since they seem to be the most popular droids that they would have the best Cyanogenmod support.
While there is plenty of attention on developing for Samsung phones, the main hangup on creating a stable ROM seems to be the closed source proprietary drivers only available to the stock ROM.
So my question is if there is a phone out there that uses open source drivers or runs Cyanogenmod with no sacrifices. Is this true of the Nexus phones maybe?
Thanks for any input
Answering my own thread in case anyone else is interested.
A Cyanogenmod phone not only exists, but it's cheap and has a lot under the hood!
http://oneplus.net/one
I've used a few other androids before with custom ROMs, and a major obstacle to stability seems to often be the fact that manufacturers typically don't include open source drivers, which leads to reverse engineered open source drivers being developed on xda, which often aren't as good as the binaries that can only be used with stock based ROMs.
Since the OPP ships with cm11, does this mean that it uses open source drivers that will work well with any open source ROM?
I'm not dev, but my guess is not entirely. Qualcomm is extremely protective of it's IP, which is why the Nexus 7 2013 source got pulled momentarily I think. This device run their SOC do I assume it'll use their drivers.
But as you can see there are a good number of roms for it already, so it's still a dev friendly device. They released their kernel source so it's useful for making AOSP roms and regular CM11, but certain features from CM11S is not available. CM isn't fully open source either from what I understand.
If the device was running pure AOSP with no Google services and using Texus Instruments OMAP chips, then it'll probably be more open.
But probably don't take what I say seriously.
eksasol said:
I'm not dev, but my guess is not entirely. Qualcomm is extremely protective of it's IP, which is why the Nexus 7 2013 source got pulled momentarily I think. This device run their SOC do I assume it'll use their drivers.
But as you can see there are a good number of roms for it already, so it's still a dev friendly device. They released their kernel source so it's useful for making AOSP roms and regular CM11, but certain features from CM11S is not available. CM isn't fully open source either from what I understand.
If the device was running pure AOSP with no Google services and using Texus Instruments OMAP chips, then it'll probably be more open.
But probably don't take what I say seriously.
Click to expand...
Click to collapse
Well I appreciate your honesty lol you've given me some interesting things to research. In the future I may be avoiding Qualcomm devices, I'm sick of having to decide between stability and crappy ui and features, vs the awesome of cyanogenmod or other community Roms with unstable reverse engineered drivers.
Hardware manufacturers have got to quit messing with android so much, Samsung makes great hardware but pretty crappy software, I'm tired of having to choose.
My next phone will either be an OPP or a Nexus 5 I think. On that magical day that I have cash to blow....
eksasol said:
I'm not dev, but my guess is not entirely. Qualcomm is extremely protective of it's IP, which is why the Nexus 7 2013 source got pulled momentarily I think. This device run their SOC do I assume it'll use their drivers.
But as you can see there are a good number of roms for it already, so it's still a dev friendly device. They released their kernel source so it's useful for making AOSP roms and regular CM11, but certain features from CM11S is not available. CM isn't fully open source either from what I understand.
If the device was running pure AOSP with no Google services and using Texus Instruments OMAP chips, then it'll probably be more open.
But probably don't take what I say seriously.
Click to expand...
Click to collapse
TI OMAP left the mobile market for SoC.
Well I appreciate your honesty lol you've given me some interesting things to research. In the future I may be avoiding Qualcomm devices, I'm sick of having to decide between stability and crappy ui and features, vs the awesome of cyanogenmod or other community Roms with unstable reverse engineered drivers.
Hardware manufacturers have got to quit messing with android so much, Samsung makes great hardware but pretty crappy software, I'm tired of having to choose.
My next phone will either be an OPP or a Nexus 5 I think. On that magical day that I have cash to blow....
Click to expand...
Click to collapse
You can't avoid Qualcomm, they pretty much own the market share when it comes to SoC. They're not bad people, their SoC are undoubtedly the best on the market. And there aren't many phones at all that offer other system on chips. The only others being NVIDIA Tegra but they're not really on phones anymore, Samsung Exynos is on international devices... if you buy a international Samsung Note/S5 then chances are it won't support U.S. LTE bands (unless you live outside of the U.S./NA).
At the end of the day, the factory images are there. And yes the N7 were pulled but its back and has been there for awhile.
The real difference is that aosp is built and tested on Nexus devices and CM uses aosp (google) to build there platform from.
So any other device is for lack of better words is a port from android nexus development aka android built for and test on nexus.
So in a way the one plus is just like any other non nexus device. You can't just repo sync a Google aosp repo and build for this phone. Without changes being made to make it work.
Not knocking the One it's a really nice piece of hardware.
Hey Folks,
I had no Samsung Device for ages but i got a brand new Galaxy S9+ in Gold for a nice Price and couldn't resist anymore. Now is the Question, is the Exynos Variant worth the Bootloader Unlock? I'm a Friend of AOSP / GSI Development and would like to contribute for My Device some Work. But how good is the Treble Support? Are GSIs working fine? Any Bugs or Features that i would miss compared to the locked stock OS? The ONE UI seems to be pretty nice and i'm very happy with My S9+ how it is. But i would also like a OS without all the Samsung Stuff and some Optimizations on top. All Opinions are Welcome!
Edit:
So i just decided to unlock My S9+ Duos and i'm already working on a Stock OS Project (Sadly since AOSP isn't that good rn). Anyways, the Samsung OS is pretty good. I will debloat it hardly and add Google Apps besides some heavy background optimizations on the System. That will be something new for Samsung Users... Stay tuned!
Edit2:
Project will be called GOSP (Galaxy Open Source Patch). Aiming on Debloating Samsungs Firmwares besides adding Google Apps, new Features and optimized System Configurations for better Performance, Quality and Battery Lifetimes. It will be open on GitHub for contributions and everyone is welcome to work with Me on a unified Stock ROM Project for all Galaxy S9 and S10 Variants (Also the coming Ones and Note 9/10 Devices).
The First Time that i haven't unlocked my Bootloader right after getting My Device. If no One explains Me the Pro and Cons am i keeping it locked. I don"t trust This Samsung Pseudo Security Stuff aka Knox and Counters... IT's like i said For Years. Samsung is just the better Apple. Can't wait to Hear News about Tizen lol
Not a lot is happening on the AOSP side of things, just a los 16 project that seems to be stable enough for daily use. There are a few very nice stock based roms like soldiers or ambasadii. Go and have a look on the cross development forums. For me personally there are pros, I like my device bloatfree and my kernel modified for my usage. But the cons are that there is not a big community (strange for a newer Samsung device.......), not much treble sGSI support at all, and a very small chance of getting a large number of different AOSP roms in the near future. Hope I helped
Haxomen said:
Not a lot is happening on the AOSP side of things, just a los 16 project that seems to be stable enough for daily use. There are a few very nice stock based roms like soldiers or ambasadii. Go and have a look on the cross development forums. For me personally there are pros, I like my device bloatfree and my kernel modified for my usage. But the cons are that there is not a big community (strange for a newer Samsung device.......), not much treble sGSI support at all, and a very small chance of getting a large number of different AOSP roms in the near future. Hope I helped
Click to expand...
Click to collapse
I'm wondering how @phhusson is working with Treble since he made various patches on his AOSP GSI Development. Do we use Stock Vendors with the GSIs? Hows the Pie Status? Many GSIs are out there who get many Updates over the Time including Phhussons Changes on the AOSP Base so i would push My Efforts in this Direction...
I've read that Hardware composing isn't working and that the Iris Scan isn't implented in AOSP. Is there anything besides that left? It looked to me that Phhusson fixed most of the Issues so far!? I'm really about to unlock My Baby... (Still hate Exynos lol)
Miustone said:
I'm wondering how @phhusson is working with Treble since he made various patches on his AOSP GSI Development. Do we use Stock Vendors with the GSIs? Hows the Pie Status? Many GSIs are out there who get many Updates over the Time including Phhussons Changes on the AOSP Base so i would push My Efforts in this Direction...
I've read that Hardware composing isn't working and that the Iris Scan isn't implented in AOSP. Is there anything besides that left? It looked to me that Phhusson fixed most of the Issues so far!? I'm really about to unlock My Baby... (Still hate Exynos lol)
Click to expand...
Click to collapse
I dont know how he is working, but sGSIs for out device are crap, and that is a good way to say it. There is no thread for the new LOS 16, but the HWC bug is solved in the new builds. Yeah the issues are fixed but the stability, battery life and other things are bad for my taste
Haxomen said:
I dont know how he is working, but sGSIs for out device are crap, and that is a good way to say it. There is no thread for the new LOS 16, but the HWC bug is solved in the new builds. Yeah the issues are fixed but the stability, battery life and other things are bad for my taste
Click to expand...
Click to collapse
I'm really sad that i can't get a Snapdragon Samsung Device in Germany but i Think ill unlock the Bootloader, make a Backup and try out some Things. Stock seems to be Very Good actually. Maybe do i something in that Direction Again. But also possible that i work on Treble... I just need a Day or Two to decide that.
Shouldn't hurt to start a new Project for such unbeloved Device. The Overall Hardware i Superb. But i never worked with Exynos. That will be a intersting Trip...
Alright, i will do a Stock Project aiming on Debloating the Samsung Stuff out of Stock Devices and optimizing of the overall System Quality. Or how i call it: "Patching".
Required will be a Stock Samsung OS or ROM and My Patch does the Rest. Included will be also new and hidden Features and a Google like Expierence with essential System Apps from Google. Think i will use My last AROMA Utility for it which includes AROMA File Manager and other Goodies...
Can't wait to see what i can unleash on Samsung Devices..
One UI is really far away from AOSP. Hard to implent Pixel Features and such... Not even Well Beeing from Google will be shown in the Samsung Settings.
Think i will give Linage OS from the first of this Month a Shot and See how it Runs...
Thank you for your involvement!
If you want to contribute to s9+ exynos community, you could also port the gcam from pixel. There are some ports, but they are bad, and discontinued.
https://forum.xda-developers.com/galaxy-s9-plus/themes/gcam-port-galaxy-s9-s9-exynos-t3814539/
Have a good day!
danimiu3 said:
Thank you for your involvement!
If you want to contribute to s9+ exynos community, you could also port the gcam from pixel. There are some ports, but they are bad, and discontinued.
https://forum.xda-developers.com/galaxy-s9-plus/themes/gcam-port-galaxy-s9-s9-exynos-t3814539/
Have a good day!
Click to expand...
Click to collapse
The Samsung Camera is actually pretty good. But i will take a look...
Is anyone willed to help me testing btw? Project will be called GOSP (Galaxy Open Source Patch) and i'm open for any Devs who want to join and contribute...
I do…. So much! I remember when i was 12 years old and I flashed roms on my old Samsung Galaxy S Plus, bricked it, installed Cyanogenmod on it and used it for a couple more years, and I remember loving it so much. Cyanogenmod was fast, clean, no nonsense, customizable and direct. I know we have lineageos but it’s just not the same, there are no customization options like on Cyanogenmod.
I guess I’m the only one lol
I am not sure if there will ever be a LineageMOD.
I miss the MOD part of Cyanogen.
If I can make it work on this device why not include it?
Where as Lineage is more..
If it was not available on the device it can not be included.
I understand and support the path Lineage is on.
I do not agree with limiting a device due to upstream rejection or other custom modifications.
Lineage is still a custom rom.
For reference.
Requirements for an official build.
Lineage - [GitHub] - Charter
Cheers.
True, but the thing i love so much about LineageOS is because it feels so official lol.