3 ms·
The problem is that everyone who attempts this tries to start from scratch and then has the network effects problem, when what we really need is for someone to
by zrm 8y ago
The problem is that everyone who attempts this tries to start from scratch and then has the network effects problem, when what we really need is for someone to play GNU/Linux to Android's proprietary Unix.
Make something that will run the same apps, on the same hardware, but put the user in control of the thing. Then add all the interesting features you wanted to put in your independent system.
Which is easier in this case because it's possible to fork Android and start from there. The major problem seems to be the driver issue on mobile. The drivers are blobs tied to a specific kernel, which makes it hard for people to try out the new thing on their existing phone, which suppresses adoption and participation. And that's also the thing that prevents you from even upgrading your old phone to a newer version of vanilla Android.
So it seems like what we badly need is a solution for that.
- sorenjan 8y agoGoogle was smart and sort of protected itself from Android forks years ago, when they started putting more and more functionality in Google Play Services. Most apps need that to run now, and it isn't open source.
- zrm 8y agoReimplementing that still seems like a lot less work than starting from scratch.