|
|
|
|
|
by kapad
1876 days ago
|
|
I recently tried setting up an Android phone with LineageOS without any gapps. Google's integration into the Android libraries that are used to build almost all the apps out there is so deep that a lot of apps that I use regularly wouldn't even launch on the phone. Basically, by controlling the API that apps target when they are built, Google has attacked the AOSP from 2 sides. First is from the developer side of things. App developers need to jump through many hoops to make an app that would fall back to working with Google's services running on the phone (LineageOS without Gapps and using some fake gapps implementation to keep the API from breaking). The second attack that Google has made to the AOSP is from the end user's perspective. They have made it harder and harder to use AOSP without Google's services. Since it's so hard for user's to setup and use a phone without Google's services, they almost never take that option. (I personally, reverted to the OnePlus' Oxygen OS and ditched LineageOS). The end result being that user's just don't want to leave Google's Android garden and explore the wilderness of AOSP without Google. |
|