Modern Android? More like Modern GNOME - it’s called adwaitapod and adwaita is the name of GNOME’s style. :-)

No, it’s just that when you use a mainline kernel, you’re just not reusing all the Android (often user-space) drivers that make cameras work on Android and due to that stuff, starting from drivers for the SoC camera interface to the camera sensor have to be re-implemented. Whether you are on glibc (e.g., on Debian/Mobian) or musl/Alpine does not really matter.

Also, Camera APIs and the whole “desktop Linux” camera stack (think of things like debayering, white-balance) is nowhere near as developed as what Android has (and that, IUC, Ubuntu Touch can reuse on Halium by plumbing things together).

A Pixel 3a may be a good choice. It’s older, but not huge—and it’s very well-supported in Ubuntu Touch (and Droidian, both use Halium/libhybris to re-use the Android kernel drivers), and also in postmarketOS (mainline Linux 6.9.3 as of this message).

On postmarketOS, camera support is not fully there—the front camera is somewhat supported. Also, Wi-Fi is still a bit annoying, calls only work with headset on postmarketOS, so I would say: Use Ubuntu Touch or Droidian for now, and maybe move on to postmarketOS once it’s a bit more solid.

It should be. With zram, I can use similar software even on a 2 GB RAM device somewhat comfortably, unless I open too many tabs in Firefox.

I’ve been told that PinePhone 2 is not happening this year. (If AllWinner will continue to supply A64 SoCs, it might take even longer.)

Regarding SoC, the likely/obvious candidate is RK3566 - but we’ll have to wait and see for the when and how. (I, personally, would love to see a PinePhone V - think PineTab V, but as a phone).

PineTime: It has nice companion apps on Mobile Linux, but I went back to my Pebble Time Steel - the always on display matters to me.

Yeah man, I think the article I initially read about PP Mobian situation was this one here just for reference if I am even remembering right – https://blog.mobian-project.org/posts/2023/09/30/paperweight-dilemma/

Someone stepped up (see https://blog.mobian.org/posts/2024/01/08/highlights-of-2023/ and afaik a-wai also mentioned this at fosdem (https://fosdem.org/2024/schedule/event/fosdem-2024-3290-towards-a-bright-future-with-mobian-/), also long standing issues like the out-of-tree-WiFi/BT driver are being worked on currently.

Regarding Beepy: I really tried, but … compared to that, PinePhone was easy to get to a somewhat works state in mid 2020. See https://linmob.net/enter-beepy-esc/#flaws

Depends, guessing from this conversation I’d assume there’s currently nothing to thank for.

And because of that: If you like Phosh, consider giving back:

• https://liberapay.com/Phosh/ and
• https://honk.sigxcpu.org/piki/donations/ are simple ways to do so :-)

Ubuntu Touch suggests that this will use Halium most likely, which is good for features, but … it’s not mainline.

Although: Thanks to Chromebooks, there are now a few Mediatek SoCs with okay mainline support. But while the Helio G99 seems quite similar to the Kompanio 520 at first glance, they are quite different, sadly.

This sounds a lot like the Flattr model - a service that had its moment in 2010/2011, but ultimately failed: https://en.wikipedia.org/wiki/Flattr

Payments are a challenge, with processing fees and taxes in an international context, small sums don’t work out well - there’s a reason why services like Liberapay push you to do bigger amounts at one time instead of small amounts at multiple points in time.

This may seem odd, but from a person that has a two-digit amount of phones: You know that it’s possible two own more than one phone at a time, e.g., a Linux Phone and a Game Phone? ;-)

Very much not. GNOME Shell Mobile was funded by the German Prototype Fund in 2022 IIRC, way later than Phosh was created (funded by Purism for their Librem 5). GNOME Shell Mobile will eventually be part of GNOME proper (meaning it’s Mutter, and GNOME Shell, patched to work on small devices), currently it’s a patch set on top of multiple GNOME components that’s packaged in postmarketOS and the AUR (if you consider AUR stuff packaged).

Phosh was created on based on wlroots (which is also used in Sway and other wayland-native window managers) and GTK3, as a Mobile Shell. Ironically, this way was pursued because Purism developers where told by the GNOME Shell people that an adaptation of GNOME Shell for Mobile would not be feasible.

Both rely on designs created by (at least then) Purism-employed designer Tobias Bernard IIRC, and thus may seem quite similar despite being based on a different tech stack, and both are hosted on GNOME’s Gitlab, using all the same apps.

Honestly - using Sxmo on a PinePhone Pro is about as hard-core as you can go beyong building your own thing from scratch.

Ubuntu Touch on Pixel 3a, or Sailfish X on a supported device or a Librem 5 with PureOS even is a lot less geeky and more approachable thing.

Officially, yes, but there’s also https://elagost.com/flatpak/ Also (shameless self plug): https://linuxphoneapps.org/apps/org.signal.signal/

I wonder how much additional work would be necessary to actually support A64, too.

But for now this is definitely good news to PineCube hackers/users ;-)

The Pixel 3a? As stated on https://devices.ubuntu-touch.io/ it’s the best port out there (and my previous experience with a OG Volla/GS 290 confirms this). Now is Ubuntu Touch perfect? No, and everything depends on your use-case (and because of no VoLTE support, the region you are in also matters). You can also try Droidian (https://droidian.org/) with a Pixel 3a, so given likely availability of a working, used device for less than USD/EUR 100 you can’t go wrong with it, IMHO.

Just look at https://devices.ubuntu-touch.io/

I have a Pixel 3a and it’s a really great port.

Writing this on my Librem 5 as a happy Librem 5 user, I struggle to find a good answer - maybe the Shift 6mq is an alternative (see the discussion on that in the equivalent to this thread in c/linux), as Shift have actively supported mainline development. The PinePhone is slower than the Librem 5, and the PinePhone Pro … I could not daily drive it, too many bugs and too short active use battery life. If you just don’t want to rely Purism shipping soon, you can always try a second hand Librem 5. Also: While I am quite happy, I am an enthusiast - YMMV.

Yes, the Librem 5 is expensive and Purism treat consumers poorly.

But, the comparison and the focus on pure specs make it seem that you don’t understand the appeal of the product, which is to run a GNU/Linux stack on a phone with a very-close-to-mainline kernel. Among the devices you compared the Librem 5 too, the only one that’s comparable is the PinePhone Pro (yes, the others support Ubuntu Touch, but they are essentially standard Android hardware featuring a Mediatek or Qualcomm SoC. The vendor kernel is then being used with a compatibility layer to run Ubuntu Touch on it.

The PinePhone Pro (as the only other mainline smartphone in your comparison) is significantly cheaper, but that’s in large part due to PINE64’s modus operandi: They supply hardware, and the community makes that hardware usable by supplying the software. This model has worked okay for the OG PinePhone, may be due to the Community Editions, where PINE64 partnered with distributions/software projects, but it has not worked so well for the PinePhone Pro. The PinePhone Pro also has - depending on how you want to spin it - a too power hungry SoC or a undersized battery. Thanks to standby, it can last a day, but you can’t really use it for much during that day then - e.g., browsing the web rapidly drains the battery. Also, without Purism’s efforts, there would be way less user space software to make use of the device.

The Librem 5 is not without flaws, it’s a really complicated hardware device (they were aiming for some FSF stamp of approval) - while the (socketed) 4G modem has GPS support, Purism also added a dedicated chip for that so that you can navigate while the LTE unit is “killswitched off”. The NXP i.MX8M only has Cortex A53 cores, and the GPU is not amazing, either (at the time when design decisions were made, it was the only GPU with decent blobless mainline driver support though), but at least the battery is large enough to make the Librem 5 a phone I can reasonably use as a daily driver these days.

Regarding the Liberty Phone: I hate the name, but given that this is just the Librem 5 USA with as much RAM as the SoC supports and a larger eMMC, there’s no technical excuse to delay that product, as these hardware changes are very, very minor.

I use Evolution for email (which … well, is somewhat doable with scale-to-fit), and it notifies me about contact birthdays.