zlacker

>>todsac+(OP)
At best, the Pinephone is buggy software on low priced but mediocre hardware. It has always been like this, and it is not going to change. There is nobody willing to spend the millions of dollars it would take to make it otherwise.

Meanwhile, AOSP is fully working, open source Linux-based phone software that runs on lots of modern hardware from a variety of manufacturers. Distributions like GrapheneOS have put huge effort into de-googling, privacy and security. Cameras work. SMS works. Phone calls work. There are lots of apps. I hear there are even a few phones that can do wireless charging!

Why waste any more mindshare on the Pinephone?

>>skymer+bp
AOSP is still a google-controlled project that requires a ton of blobs, whereas the Pinephone (and other linux compatible smartphones like the Librem 5) has an entire ecosystem of healthy linux distros (from Mobian to Archlinux) running as close as possible to mainline linux.

> GrapheneOS have put huge effort into de-googling

They are doing great work but they're still depending on google for maintaining Android (Can GrapheneOS do anything against a feature pushed by Google in Android 13/14 and so on? Nope).

> Cameras work

You still lose all the post-processing stuff which account for a good portion of perceived picture quality.

>>dbeley+Br
The blobs are required by hardware OEMs, not by google themselves. You'd have the exact same issue when trying to run pmOS on the same hardware; it actually crops up throughout the embedded ecosystem. Pinephone and Librem 5 are quite exceptional wrt. minimizing the amounts of hardware-specific blobs that they require.

>>zozbot+4t
Yeah indeed I should have specified that the whole "mainline linux compatible" is mostly because the Pinephone and the Librem don't use Qualcomm (or worse Mediatek) SoCs.