That’s an option, https://linuxphoneapps.org/apps/dev.geopjr.archives/ can also read zim files, but I’ve found it to be a bit clunky - still, I recommend giving it a try.

See https://linuxphoneapps.org/categories/conference-companion/ - both Confy and Kongress are decent. And then there’s a relict from N900 times: https://flathub.org/en/apps/at.priv.toastfreeware.ConfClerk

The color picker unfortunately is a wider issue, it’s a standard component of IIRC libadwaita that’s just used in Gajim.

use JMP.chat to be able to call/text anyone in my contacts. On the Linux side that’s not really doable although with WayDroid it’s workable.

Just to make sure (and sorry for asking): Have you tried Dino for this usecase?

OS updates are paywalled (subscription)

This, at least for the C2, has changed https://forum.sailfishos.org/t/long-term-sailfish-os-updates-free-of-charge-for-all-jolla-c2/23491 (likely because it’s conflicting with EU law), and they’ve instead introduced a Voluntary Subscription.

Honestly, I rather pay for my OS than paying for it with my data / privacy or living in an ad-infested garbage fest.

Edit: and their mix up with some Russian business (not sure about the current status of it) also doesn’t help instill confidence.

That’s history, see https://forum.sailfishos.org/t/sailfish-community-news-30th-november-jolla-reborn/17473.

This. Also, most AppImages are x86_64 only. If they don’t explicitly say it’s for aarch64/arm64 you are going to also need some fun architecture translation (box64, fex, …) to make the thing run. At that point, it’s in many cases easier to try building from source IMHO.

PS: Good luck on Wayland can also be added, given probonopd’s (AppImage inventor) stance on Wayland. I’d advise to not waste time with AppImages on #MobileLinux.

+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.

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. :-)

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 don’t think reporting the USB ID thing to Plasma is useful and will go far - for 99% of users (that use some kind of Android/AOSP) the modus operandi is fine and helpful. With many Android devices and OSes requiring you to do something on the device after plugging it in, testing does not seem to be feasible to me.

There’s no need to add the edge repo, as the latest release of mobile-config-firefox should be in v23.12 by now (it’s been updated there since my last post). The command I posted does not add the repo, but only uses it for the one package without adding the repo permanently.

I recommend trying to use KDE Connect (or scp, rsync … another network based way) to send the screenshot from the phone to your other computer instead.

MTP/other file transfer protocols do not (yet?) work with mobile Linux, so this failure is to be expected. It only shows up for connection, because if your device ran Android, it would be an option — AFAIK, Plasma acts this way because of the USB ID of the device.

Also, regarding your main issue: While you can report this to Mozilla, please be aware that Firefox is being “patched” to better work on mobile by https://gitlab.com/postmarketOS/mobile-config-firefox. I suggest you to install the latest, not yet in postmarketOS 23.12 mobile-config-firefox package from edge first by running:

sudo apk del mobile-config-firefox
sudo apk add mobile-config-firefox --repository http://mirror.postmarketos.org/postmarketos/master

While it may not fix every issue possible, it should improve the experience.

Generally yes, but I am just a dumb tech blogger, so what do I know 😀 . I checked the issue tracker, and this issue seems related - I also see that crash, and it might extend beyond upgrades and thus be the source of what you are seeing. If you also see that crash of that service, maybe just upvote the existing issue first or if you can chime in/help out, do that before opening a potential duplicate :-)

As flatpak apps show (correct?) your situation is not different from what I would expect. I installed 23.12 on one of my devices and see a similar behavior. Generally, assuming you did start with a Phosh image or used pmbootstrap and chose phosh as UI (and did not, say, start out with Plasma Mobile and then switched over to Phosh, which can cause weirdness), I think we can safely say that this not just an issue on your end. This is very likely a general issue on 23.12 and edge currently.

Why isn’t it fixed already? It sure seems to be difficult, and most “long termers” (extrapolating from my own behavior) likely have given up on using front-ends like GNOME Software or KDE Discover and have become fluent enough with apk and flatpak on the terminal and thus don’t contribute to a solution.

deleted by creator

It did work on edge at the time of that post (March 2023), and IIRC it may have worked in stable 23.06 (the release right after that post) - I don’t have a device still running that to confirm. It since broke again, and it’s currently broken in stable and testing (it’s definitely broken for me in edge in both Plasma Mobile (KDE Discover) and Phosh/GNOME Mobile (GNOME Software). So don’t go to edge because of this, especially not right now.

Nice!

While we‘re at it: do you know if there is any way to get alpine apk visible in gnome software? Its driving me nuts that flatpak is visible and apk which is a lot of stuff can only be installed through cli.

It’s a long standing issue, for context I recommend reading https://blogs.gnome.org/pabloyoyoista/2023/03/05/gs-and-pmos-a-bumpy-road/

Without any further configuration, might as well as add that to your edited paraphrased quote.

Please correct me, but AFAIK, necessary configuration of flatpak (e.g., configuring remotes) depends more on the distribution than the architecture (as long as the architecture is supported at all, that is - so x86_64 or aarch64 AFAIK).

Your lengthy explanation of flatpak doesn’t seem to be postmarketos related.

Sure? https://gitlab.com/postmarketOS/pmaports/-/merge_requests/4820 And does it hurt to mention differences in software support between x86_64 and aarch64? I would see your point if I had talked at length about Snaps. ;-)