4 ms·
Looking through their website I'm curious why what they're aiming for can't be accomplished with the Android Open Source Project (AOSP) or a fork of it, rather
by paxy 9y ago
Looking through their website I'm curious why what they're aiming for can't be accomplished with the Android Open Source Project (AOSP) or a fork of it, rather than trying to build yet another smartphone ecosystem from scratch?
- subway 9y agoAOSP still relies on a bunch of hacked together BSPs with nasty binary blobs and never-ever-gonna-get-mainlined device specific kernel patches.
- scintill76 9y agoThey could release open-source and mainlined versions of that stuff then. I guess they wouldn't because they probably consider Android incompatible with their other goals.
- subway 9y agoThe work they're doing is effectively that. There's nothing stopping Android from running on top of the kernel work they're doing. Think of their work as developing an open source BSP. It looks like much of the UI work is being punted to whatever phone ui the KDE and Gnome projects churn out. An Android userland will likely ship in parallel or shortly after. The bits AOSP handles are by and large boring and don't need to be futzed with.
- paxy 9y agoRandom BSPs don't matter considering they're releasing their own hardware, and can support that as much or as little as they want on top of AOSP.
- jhasse 9y agoReplicant then: https://www.replicant.us/ https://www.replicant.us/
- bo1024 9y agoA huge point of their approach is the hardware.