There’s instructions regarding VoLTE setup on the wiki: https://wiki.postmarketos.org/wiki/OnePlus_6_(oneplus-enchilada)#VoLTE

That said, the one close-to-mainline phone Qualcomm SoC that’s reliable for calls according to multiple accounts is the Google Pixel 3a.

Even then, it’s hard to make blanket statements whenever it comes to VoLTE: It may work with the device for some one else, but as carriers are involved, it also depends on whether your specific carrier allows the specific device to use their VoLTE services.

(Given the fact that VoLTE is just VoIP, this feels really sad and unnecessary, but … phone companies have always sucked, haven’t they?)

Or just go to https://linmob.net/

many, many broken workflows

Sounds like many, many opportunities to contribute constructive feedback 😉️

I am once again happily asking for logo submissions to replace that current abomination - contributions welcome, contact details at the bottom of every page on https://linmob.net/.

i was dissapointet that there are soo few apps (speach linux phone app ecosystem)

If that’s your take-away from my talk, then I really messed up. Things are developing well, IMHO. Yes, Android, even “FOSS Android”/AOSP or just F-Droid do have more apps, but F-Droid has been going since 2010 (and it’s just so much easier to buy a device that runs an F-Droid compatible OS, it’s not even funny).

It’s also available on Flathub and packaged in some relevant distros - it’s one of the far too few apps that are available on Ubuntu Touch, Sailfish OS, postmarketOS, Mobian, Droidian - a true #LinuxMobile marvel.

Select Halium devices do (e.g., FuriLabs FLX1, Jolla C2, Xiaomi Poco X3 NFC with Ubuntu Touch), but the issue is that it (AFAIU) also depends on whether the carrier agrees which IMHO gives these companies more power than they should be legally allowed to.

On mainline, there’s 81voltd now (said to work on Pixel 3a, OnePlus 6(T} etc): https://gitlab.postmarketos.org/modem/81voltd

First, I’d recommend going with the 6 (no T), which has a headphone jack, which can be helpful - and on these devices is your only option for wired headphones, as USB-C dongles don’t work yet.

Audio is unreliable, yes, not just for phone calls, also for things like podcast playback in my experience - at some point during use, my wired headphones just don’t show up anymore. A reboot fixes this, I still want to look at ‘milder fixes’ (unloading of kernel drivers, service restarts), but in months of daily driving I have not got around to this yet.

How can I daily a device with these audio issues? Well, I have always hated unscheduled calls, and force people to deal with it now. Also, if things don’t work: Reboot, call back, works.

Author here.

It’s just a report on what we managed to accomplish for LinuxPhoneApps.org, a project that

lists apps for Linux Phones like the PinePhone or Librem 5, that run Linux distributions which do not have a proper (de)centralized app store yet.

That an app was added does not necessary mean it is new or anything, just that it was added to LinuxPhoneApps.org’s app list. It may be years old (and may have worked on #LinuxMobile for a long, long time, but we just missed it before. And the again just refers to the previous quarter ;-)

Here’s the wiki page: https://wiki.postmarketos.org/wiki/Nothing_CMF_Phone_1_(nothing-tetris)

The FLX1 did not have DP alt mode either, unless I am totally mistaken. All external display concepts for the FLX1 were/are to require sth like DisplayLink. So all that’s lost are file transfer speeds over USB.

From what I could gather, they wanted to make more of the original FLX1, but could not get the a manufacturer to do that. I am actually not too unhappy with this one, the orginal FLX1 was too big and heavy for my liking.

In theory, you should just see the same apps in Discover and in GNOME Software, assuming they both can access/install native Alpine and flathub apps. (And I recall they did at some point in time, but breakage unfortunately happens, and I mostly use the terminal to install and remove things…)

With Ubuntu Touch apps it’s different, the Open Store is its own thing. I want to look into whether adapting this to postmarketOS when I can find the time.

Regarding few apps: Yes, it could be more, yes, there are gaps, but we’re doing somewhat okay: https://linuxphoneapps.org/

Glad that works for you! With my bank (comdirect.de) I can use a mobile website, and if I were to use something AOSP- or Halium-based, I could also use their PhotoTAN app, which, as the name implies, needs a working camera in Waydroid (on my OP6 with pmOS, the cameras work via libcamera, but not in Waydroid), so I have a small gadget for all these TANs.

My main worry with the “let’s just use Play Store/Aurora store and the run that apk”-approach is that it does not really send a visible signal to banks that they need to keep considering customers that don’t use Android proper.

It also always means that the next update (e.g., after some consultancy or some audit happened) may not work any more, meaning, access may be revoked at any time. Complaining to customer service or in Play Store reviews may have an effect, but it will still hurt. I think I would feel a tad safer if a banking app lived on FDroid… but sill.

I hope this gets my point across.

As someone who spent some time on the topic (result), it’s not that every new app is adaptive. Even if someone uses the nice new widgets of libadwaita (or previously libhandy (GTK3)), that app is not necessary running well on mobile if width-reqests demand a higher minimal width or content is just too wide.

The same is true for QtQuick Components or Kirigami, which are the equivalent for adaptive Qt apps.

That said, yes, many new apps developed with these technologies work fine OOTB without the developer even knowing; and if they are too wide or tall, fixing that is usually rather simple and not a full rewrite/redesign.

Not directly, here’s what we have:

https://linuxphoneapps.org/categories/maps-and-navigation/

Of these, at least PureMaps does turn-by-turn - as a no-car-person that last drove in meaningful way when paper maps where a thing, I am the wrong person to ask about car navigation stuff.

Additionally, there’s the OrganicMaps desktop flatpak (not a great experience, only good for seeing where you are) and zooming around. Fortunately, a work on a mobile-friendly Kirigami app for OrganicMaps has been funded by nlnet.

Also, runnning some web Maps in a browser (e.g., via https://linuxphoneapps.org/apps/dev.heppen.webapps/) is always an option (e.g., for browsing Google Maps for an open restaurant nearby).

Just 2ct’s on the banking thing (sorry if it sounds rude, but I just can’t hear it anymore):

Just forget banking apps of you don’t want to stay on iOS or proper Google Android forever and ever and ever, even AOSP-based OSes struggle with that (a lot).

Go to a bank that still has a proper website and allows some kind of hardware device for TAN (and tell them that this is why you are leaving/joining) - we need to show market demand for alternative solutions or else these will disappear completely over time.

We also need to make regulators/politicians understand, that taking part in life must be possible without owning a device blessed by Google or Apple. We really need laws here.

Regarding Android apps: I hope that https://gitlab.com/android_translation_layer/android_translation_layer will make a difference here going forward. A Wine-like approach is just so much less of a resource hog.

Regarding the Camera on the PinePhone Pro: It somewhat works by now, if not on every OS. Be it with libcamera or Megapixels 2, we’re getting there. I suppose it’s just that nobody told the Wiki.

Having had both a Pinebook and a Pinebook Pro and two PinePhones and a PinePhone Pro at some point in time (I co-hosted a PINE64 podcast for a bit), I don’t follow. If your point is that the PinePhone (Pro) have never been a great for everybody, I think the same is true of Pinebooks (Pro), they’re definitely are among the worst laptops I have ever had. Various just as cheap ARM-based Chromebooks (especially the ASUS C101p) I’ve had were/are just so much better.

The PinePhone really helped with development of existing Linux on Mobile projects and caused the creation of some additional ones, as evidenced by the massive number of projects on https://pine64.org/documentation/PinePhone/Software/#software-releases.

The Community Editions helped projects like UBports or postmarketOS financially. Some people even daily drive the device (despite being slow, I’ve found Sxmo and Sailfish OS to be acceptable, with Phosh coming in third).

While I don’t recommend it anymore for anyone who wants to use GTK based stuff on it, I’d view it as a success (I don’t view the Pro as a success though, even though I believe they should have cancelled the A64-based PinePhone, not the Pro - a PP2 was IMHO overdue around 2023/2024). With better Quality Control, better relations between PineStore and the wider Community and a different default OS (putting the heavy Plasma Mobile on it was just nuts, and Manjaro definitely is not my favorite distro, to say the least) for the Beta edition, it could have been an even bigger success.

Yes, it didn’t work for everybody, but as getting to a working laptop is so much easier than getting to a working phone (think of calls: the device has to manage to wake up at any moment (and fast), audio routing must be switched, echoes must be cancelled etc.) with the sky-high user expectations attached to phones (and the shitload of semi-hostile phone carriers across the world), I regard the PinePhone as quite an achievement.

+1 for the Surface Go 2. I use on of these with NixOS GNOME, and it’s lovely. For Pen use I like Rnote. You could also use Plasma Mobile on it. The Go 3 is not really better, so don’t get it unless it is in the same price range, and avoid the 64 GB eMMC model.