This sounds more like a network problem, maybe something on your end or that one of the repos was temporarily unreachable (usually it's the postmarketOS repo for me in such situations). I recommend running sudo apk update in situations like this and reading through the output. Depending on which repo is unreachable (= if it's one of the alpine repos) it may be a better idea to delay upgrading.

It definitely has nothing to do with the device being dropped from main to community — both categories mean that the device is served by stable.

Hope this helps!

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.

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 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? ;-)

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 easy route is to just wait for the merge request that adds the device to be merged.

You can also try using the pmaports branch that is going to be merged to build and install it - but I am not aware of a guide that explains how to do that and have no expertise with this, sadly.

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.

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