DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
CVPCS Landmark
- Thread starter rob22202
- Start date
justinthegeek
Member
i've done some research, but i still don't get what "vendor-device set up" means. how exactly does it effect end users or the devs themselves?
That's it, just start a panic if it isn't released today now! I can see it now... "Well I heard from my brother's best friend's sister's mailman's third cousin twice removed that we were to have a new Sapphire build on the forth, but here it is the 5th and still nothing!"
:icon_censored:
**************
Well it looks like I am the one who looks bad here now since 1.0.0 *WAS* released today. oh well
Last edited:
I wont get to in depth, but here is the jist of what it is. A device/vendor set up is pretty much the bare bones of a ROM set up. Cyanogenmod pretty much has been the only one (before sapphire) to build a ROM from the ground up based on Android's AOSP. He has device/vendor set ups that other people can use as a base for their AOSP rom and then modify it.
Sapphire came out with its OWN device/vendor set up which mean it gives users an alternative to build from. Feature wise sapphire has most everything Cyanogenmod has to offer give & take a few things, but Sapphire does less modifying of the Android core thus leaving the stock quickness, and feel to it. Cyanogenmod heavily mods the android source, and for some people this can create unwanted effects or slow-downs.
Its just another great option in a line of many AOSP ROMs, like mentioned everything I said isn't "technically" correct but it will give you a idea of what it is without posting some of the more confusing technicalities of it.