

I get (and share) the purist hate on saOS’s non OSS UI, but to get linux phones up and running you need app support1 and market adoption (people buying phones) to make it a viable switch from the walled gardens for more people to use it, to get more hardware made and so on. Chicken and egg deal, bootstrapping. As such anything that gets people in front of linux phones should be embraced at this point, as long as it can run linux native code2 . When the snowball is rolling, then push for full OSS.
Don’t let perfect be the enemy of good (enough for now).
1: There’s plenty of linux apps but few are designed for small touchscreens. Android emulation often takes us back to non open source anyway, even as it helps adoption.
2: and preferably can be re-flashed with something better later, which is becoming rare as bootloaders get locked down.




Neither have I, sounds like a good project in itself if it doesn’t exist. ‘Drivers for xyz, reverse engineering something’ is part of the problem, phones usually (nearly always best I understand) have proprietary blobs of firmware to a greater or lesser degree and it’s a moving target different between manufacturers and most often models. Qualcomm modems are particularly egregious for patent reasons. US trade deal enforced global DMCA laws make reverse engineering legally tricky. Hence the desire for linux specific hardware platforms.