Tried it on an older Pixel with GrapheneOS.
Can’t zoom, can’t switch to wide-angle lens. Camera does not balance brightness by the focus point. Otherwise pictures look pretty much the same.
I suppose this was made for specific devices in mind?
Proxies started getting blocked (by some auth-account methods) last year, but libreddit/redlib dev was able to outsmart them multiple times. Now it seems like reddit is blocking IPs (and/or IP ranges). Running redlib from a residential IP still works, but I would not expect it to work from a VPS.
Tried it out a while ago, and found that I prefer GNOME’s UX and configurable shortcuts better, and that two side-by-side applications on my laptop is the most “tiles” I would realistically want.
I tried out postmarketOS + phosh on a PinePhone about a year ago. For my own needs, it worked fairly well, except (ironically) receiving calls. It was like driving an old car, everything was slightly jank, but worked, and could be tinkered with - see the entire review. I have to give credit that there has been impressive progress in mobile Linux since PinePhone’s release in 2019, and a lot of it was developed by unpaid hobbyists.
I don’t watch a lot of youtube, but DuckDuckGo browser (on Android and Windows, at least) has a Duck Player that removes all of the cruft around videos and is private afaik.
Biktor and Lynxis will be working on OpenIMSd, which aims to bring VoLTE (4G voice calls) to Qualcomm based phones (like the PinePhone)
This is fantastic news, and I wish them all the best. Reliable VoLTE/WoWiFi calls was my main (but obviously major) issue with the PinePhone.
Another FYI: Ubuntu Touch does not support VoLTE at all, thus it might be more difficult to use it in some networks and countries (for example, USA shut down 3G some years ago)
However, I was pleasantly surprised by the responsive UI, the browser, and Cinny (the Matrix Client)
Fossify Messages and QKSMS/QUIK (unmaintained but has worked well for years)
TBH I don’t even understand why Android Auto needs to exist in the first place.
The same (or even better) functionality can be achieved by using a standard video output (DisplayPort, HDMI) from the device to the in-car screen, while the touches on the in-car screen can be translated into USB mouse position and clicks on the device (unless there is a better touch protocol).
I know there are regulations about live video on in-car screens, but 1. That does not stop people from watching videos on their phones while driving and 2. Somehow that does not apply to maps?