- cross-posted to:
- android@lemdro.id
- android@lemmy.world
- cross-posted to:
- android@lemdro.id
- android@lemmy.world
cross-posted from: https://programming.dev/post/17508868
When Google, along with a consortium of other companies, announced the open-source operating system we call Android way back in 2007, the world was paying attention. The iPhone had launched the same year, and the entire mobile space was wary of the rush of excitement around the admittedly revolutionary device. AOSP (Android Open Source Project) was born, and within a few years Android swallowed up market share with phones of all shapes and sizes from manufacturers all over the globe. Android eventually found its way into TVs, fridges, washing machines, cars, and the in-flight entertainment system of the Boeing 787 Dreamliner.
You must log in or register to comment.
AOSP is basically unusable by itself now.
Ancient applications that were abandoned long ago, hardware incompatibility, outdated drivers, lots of stuff from shifted to Play Services that are missing or borked in AOSP now, etc.
Shit, most of the time notifications don’t even work.
Google got what they wanted from AOSP. They bought it, they got everyone onto it. And then they started killing it and shifting everybody to use play services and be more beholden to Google. You can never trust big tech.
Typical EEE, yes.
We still do have custom versions of AOSP, such as lineage OS and graphene OS. However, with the difficulty to install them, most people will choose not to, but the people who really want their privacy and open source will go through the hassle of installing them.
graphene OS. However, with the difficulty to install them, most people will choose not to
GrapheneOS is ridiculously simple.to install. EnableOEM unlocking, boot to fastboot, connect to PC. Then you press four buttons (wait for the buttons to say they’re done) on a browser. Super simple.
Granted, it’s harder than picking up your phone and using the OEM install, but that doesn’t make GrapheneOS difficult to install. The days of using exploits, flashing a custom recovery, flashing a zip, then flashing another for Gapps, maybe one for a kernel, etc…those days are over if you’re using a Pixel with GrapheneOS.
Since this innuendo keeps getting reposted, it’s worth restating:
AOSP has been and still is a resounding success for everyone.
Perhaps insufficient experience with the pre-AOSP status quo might be clouding the author’s judgement.
When AOSP was first released, it included all necessary app. Now many of them have been replaced by Google’s proprietary app.
There is also the Play Services, necessary for many third party apps. I know an open source compatible lib exists, but it’s not the same as not needing it at all.
Yes you can use a fully Open Source Android system, but it’s getting farer and farer from a “standard” Android install with all the Google proprietary stuff.
