+1 for Gapless. My library is not nearly as large, but it’s still plenty quick (no noticeable delay) with my 1 digit gigabytes library and IMHO the best native feeling media player on Phosh/GNOME Mobile.

It also does the Album -> Artist -> Song thing (which made me notice that I still have not fixed every error in metadata I managed to add to a part of my Library by blindly applying musicbraiz suggestions via Tagger, but that’s just a me thing).

It’s pretty much “real”. You can install every package in the repos via apt, and they should work. Caveats can apply with regards to stuff that needs extra adjustment for accelerated graphics or new kernel features.

It’s not a font … and it says LINMOB (for LINux on MOBile).

I drew it in GIMP ages ago (15 years maybe?); and did not have the time to come up with a new logo since. (I am not super happy with it myself - but it’s not a priority, there’s way more important stuff I don’t have time for).

That said: Contributions welcome! (at https://framagit.org/linmob/linmob.frama.io)

This is great, even if at least one app in that collection is only available for x86_64, which makes it hard to actually run on a phone ;-) They also updated the Device Support section of metainfo guidelines: https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/#device-support . Looks like some apps on the KDE side still need proper metainfo to show up: https://invent.kde.org/teams/flathub/issues/-/issues/34

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.