Login
You're viewing the techdon.dev public feed.
  • Jan 5, 2026, 7:57 AM

    I've been out of the loop for a couple of years on Linux phones. I'm poking around on blogs and Mastodon posts, but I figured I'd just ask:

    Whats currently (as of January 2026) the most functional, stable, boring phone + OS combination?

    Edit: I have been so thrilled with the conversations! Thank you all for sharing projects, experiences, knowledge, and links! I'm also following a lot of new folks :) This post is at 400+ boosts, so no need to continue boosting :)

    #linuxmobile #linuxphone

    💬 5🔄 415⭐ 164

Replies

  • Jan 5, 2026, 8:17 AM

    @jbowen I'm not sure what the answer is, but I suspect it strongly depends on your position on privacy, so it might be worth clarifying where you stand on that. (like, in one interpretation of this question the answer could be a stock Pixel, if one considers Android as Linux, but I'm assuming that's not what you were going for)

    💬 0🔄 1⭐ 7
  • Jan 5, 2026, 8:48 AM

    @diazona Fair point. I'm typing this on a Pixel 10, stock Android, seriously considering GrapheneOS (I've played with it in the past and was too scared to take the plunge for my daily driver).

    Privacy is quite the rabbit hole. With this question it's secondary to the user experience of running a "vanilla" Linux kernel with @phosh or some other mobile UI.

    I guess one way to think about it is comparing the experience of Linux on a phone to Linux on a laptop.

    Are we in a 1998 level of usability?

    💬 0🔄 0⭐ 7
  • Jan 5, 2026, 9:14 AM

    @jbowen I have a Pixel Pro with GrapheneOS and you don't have to be afraid. The only thing that doesn't really work is Google Pay. And IMO it has the best UX/privacy combination at the moment. I also have a OnePlus 6 with PostmarketOS and GNOME/Phosh and although I really like Linux, I can't imagine it as my daily driver now. Out of those non-Android OSes I think SailfishOS on Jolla phone is the most polished option. But it isn't completely open. @diazona @phosh

    💬 0🔄 2⭐ 19
  • Jan 5, 2026, 7:22 PM

    @sesivany @jbowen @diazona @phosh
    I tried PostmarketOS with Phosh last year on a Oneplus 6 and a 6T- the device that's supposed to be the best in terms of price, fuctionality and stability.

    And while some things are there I can't recommend it unfortunately, I couldn't even make phone calls reliably.

    Needs a bit more time in the oven I'm afraid.

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Jan 5, 2026, 8:27 AM

    @jbowen as far as I am aware there are no mainline linux phones that reliably make calls. There are a number of devices that are very close to having most features working, Oneplus 6, Fairphone 4/5 and Pixel 3a for example.

    2026 will be a really interesting year for #Linuxmobile as camera tuning improves and device support becomes more complete.

    I'm interested to learn more about how mainline linux devices can implement push notifications to wake the device.

    💬 1🔄 2⭐ 4
  • Jan 5, 2026, 9:00 AM

    @dubstar_04 @jbowen At least the Librem 5 and Pinephone do (I'm using the Liberm 5 for half a decade for that now), both are mainline devices. I don't have first hand experience with a Pixel 3A regarding phone calls but there are people in the Mobian channels using it as their only phone (including phone calls): phosh.mobi/about/features/#fn: (in this case with suspend disabled).

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 1🔄 3⭐ 2
  • Jan 6, 2026, 8:08 AM

    @MissBehave @jbowen @agx @dubstar_04 I can confirm Pixel3A /PostnarketOS phonecalls work fine But I reverted to using iPhone for calls anyway, unfortunatelly. Reason is I can't / lack skill to make incoming calls ringtone AND call audio work at the same time. In-call volume controlls don't work so I have to decide beforehand if I want hearable ringtone and absolutly unacceptably loud call audio, or unhearable ringtone and ok call audio 🙃

    💬 0🔄 0⭐ 1
  • 💬 0🔄 0⭐ 0
  • Jan 6, 2026, 9:49 AM

    @dubstar_04 @MissBehave @jbowen @agx @postmarketOS Hey! Have tested it now and it freakin WORKS on v25.12 I mean ringtones and call audio are still on the same "earpiece and speaker" volume control but physical volume up/down buttons on Pixel3A now work both in and out of the phone call. So all you have to do now is to crank vol down a bit with a button before you answer the call Whoa My 1st sim card goes back to where it belongs now 😎️🤟️ And I guess work is in progress for separate vol controlls

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 2🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Jan 6, 2026, 7:46 PM

    @agx @dubstar_04 @MissBehave @jbowen @postmarketOS Ok I have read your audio roles post slowly now, and simply speaking, not to waste your time, is there some walkthrough for dummies? Or say people not familiar at all with linux configuration deamons and stuff? Or should I just wait till next release (I guess) for this to be integrated ...? ;)

    💬 1🔄 0⭐ 0
  • Jan 6, 2026, 7:48 PM

    @agx @dubstar_04 @MissBehave @jbowen @postmarketOS I do fail at basics (I guess) like "Note1 if you run wireplumber 0.5.13 ..." -> I have no idea which wireplumber I am running nor how to check it. Nor how to install media-role-nodes.conf. So I cloned feedbackd.git but running that "meson setup -Dmedia ..." line from feedbackd directory -> gives me meson: not found Dead end :)

    💬 0🔄 0⭐ 0
  • Jan 6, 2026, 9:07 PM

    @ati1 @dubstar_04 @MissBehave @jbowen @postmarketOS Distros have ways to check versions of packages, e.g. on Debian it is `dpkg -s <packagename>`. They also have means to install build dependencies. So if you use your distros command to install the build deps of wireplumber it will pull in meson and you can build the package.

    These commands differ between distros so it's best to read up on that.

    It's perfectly fine to wait for the next round of releases too though.

    💬 2🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Jan 5, 2026, 12:17 PM
    @dubstar_04 @jbowen

    #linuxmobile "Camera tuning" ? No sir, we are not doing camera tuning at the moment. We are in "it would be cool to have camera drivers", "major pieces of infrastructure are missing" and "oh, people would like to record video?" phases.

    For "boring phone", OnePlus 6 + phosh should work.

    And yes, people are working on cameras (including me, we can talk at Fosdem), but we are not yet in the tuning phase.
    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Jan 5, 2026, 3:11 PM
    @dubstar_04 @jbowen Camera _sensors_ drivers are working on few models, yes. (Like 4 models). And of course you have talks. But as I said, what is missing is much _much_ more than tuning. AF is one example. Drivers for ISP and hardware encoders, libcamera based application stack for taking photos, and anything at all to record video.

    Then we can do libcamera based video recording, and then.... probably hw acceleration for encoding and then...
    Then we can do tuning.
    💬 0🔄 0⭐ 0
  • Jan 6, 2026, 11:23 AM

    @pavel @dubstar_04 @jbowen I'd disagree on most points here:
    1. By now we have quite a few more models with at least one working camera. On the qcom side alone we have: Pixel 3a, OP6, Fairphone 4+5, Poco F1, some other xiaomi devices that I forgot - and a few more devices that should be close, like the Pixel 3 and shift6mq. And we can expect the number to raise further, with previously problematic parts like c-phy now working.

    ...

    💬 1🔄 0⭐ 0
  • Jan 6, 2026, 11:30 AM

    2. For AF there's a working WIP branch for the swISP, so we can expect progress here as well (plus multiple actuators having working drivers now).
    3. We already have a working software stack for photos and videos, via Pipewire and Gstreamer. Just start Snapshot or Kamoso. (surely still missing quite a few features)
    4. Drivers for ISPs will stay out of reach on many devices - that's why we have the swISP, which is about to turn into a gpuISP by default (likely in the next libcamera release).

    ...

    💬 3🔄 0⭐ 1
  • Jan 6, 2026, 11:39 AM

    5. Hardware video encoding is already available and working on devices like the OP6. In Snapshot you can turn it on in the settings - it's only disabled by default because of stability issues/bugs (e.g. on the Pixel3a), another area where we can expect improvements in the near future.
    ...

    💬 1🔄 0⭐ 0
  • Jan 6, 2026, 11:43 AM

    6. With the gpuISP tuning steps like color correction are essentially free regarding performance. I already have a first test set of tuning matrices for the IMX363 applied on my Pixel3a (running libcamera with latest gpuISP patches) - it currently makes the result worse, but you can expect some comparison images soon where this changes :)
    Fairphone even gifted a FP4 and FP5 to the libcamera maintainers so they can start doing this kind of tuning.

    💬 0🔄 0⭐ 0
  • Jan 6, 2026, 11:47 AM

    TL;DR: the time to start playing with tuning is now - and in fact that's what we're doing already :)

    💬 1🔄 0⭐ 0
  • Jan 6, 2026, 12:09 PM

    P.S.: here's a quick video shot with Snapshot on an OP6 with pmOS edge + libcamera gpuISP, with hw-encoding enabled. There's still a lot to be desired quality-wise - most importantly AF, sensor tuning - but the basics for fullHD video capturing are increasingly in place (edit: the v4l2 encoder certainly also needs improvements).

    Image attached toot
    💬 2🔄 1⭐ 0
  • Jan 6, 2026, 12:27 PM

    @rmader the @libcamera matrix room is an exciting follow right now. I love it when you share updates, thank you. Cameras is one of the things I'm most excited for this year in mobile linux.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Jan 6, 2026, 1:22 PM
    @rmader 1. Agreed. 2. Well... more work is needed, like actually merging the stuff in, right? And then we'll have to do _tuning_ of the AF algorithm. And probably someone needs to do PDAF. I tried in clicks machine, but again, more is missing than tuning. 3. "Missing few features" as in "will need complete redesign"? :-). This will get longer reply. 4. Agreed. Another missing piece. I'm eagerly waiting for gpuisp to hit the tree, but it is not there yet. 5. Ok, I was not aware of this one, it is good to see progress. (But again, more than tuning is needed). 6. Good to see that. Does gpuisp already do lens shading correction? That one is a bit important. Plus it should really output YUY2, because that's what encoder needs. Plus there's more work there, for example we'd want controls for manual focus, manual exposure; plus it needs to resize and not crop. But that's all work that should happen after it hits the tree.

    Thanks for video. I guess we can agree that it needs working AF first, and then we'll see what else is needed? :-).
    💬 0🔄 0⭐ 0
  • Jan 7, 2026, 11:42 AM

    @pavel Re 4: Looking really good now 🤞
    5. Yeah, I'm betting on a positive feedback loop here - the more stuff works, the more motivated people are to help fixing the remaining issues.
    6. AFAICS lens shading, denoising and YUV formats are high on the list for the next steps after the main gpuISP implementation has landed. And I fully agree that YUY2/YUV420 and NV12 would be great to have. Not having the later currently causes an extra conversion/copy when recording in Snapshot.

    💬 0🔄 0⭐ 0
  • Jan 6, 2026, 1:32 PM
    @rmader 3. Lets take about this one, because I don't believe it is as simple as "just start Snapshot".

    Gpuisp will need to include sensor tuning, correct? It is needed for video capture. And for still image capture, we'll need to capture full-size raw image, bypassing gpuisp, correct? That will get us bayer image.

    But now we'll need to transform that bayer image into high-quality jpg. What is the proposal to do that?

    Anyway I'm playing with libcamera-based photo taking here -- https://gitlab.com/tui/libcamera/-/commit/7c3c0d04c026d3a4a030fb7882095c028cd4ee8e -- but there's a lot of work to be done :-(.
    💬 0🔄 0⭐ 0
  • Jan 7, 2026, 11:58 AM

    @pavel Hm, why would you not use the gpuISP for taking still pictures? Sure, you can further improve quality with that in the long run - and the upcoming version of libcamera will allow you to choose between gpuISP and raw - but for starters I'd argue it's fine to just use the gpuISP.

    💬 1🔄 0⭐ 0
  • Jan 7, 2026, 12:23 PM
    @rmader Well... the thread began with "more than tuning is needed", and this is decision which will lead to redesign later. We'll likely want to use same tuning for gpuISP and then for hq-still-photo-component, and hq-still-photo-component does not exist at the moment :-).

    And "why not use gpuISP at the moment". Well, besides quality, gpuISP only has one output. We need that output for preview. And that means we have photos in BAYER.

    Being able to feed libcamera with BAYER data, and saying "Librem 5 back camera took this BAYER, please convert it to RGB in high quality" would be good.
    💬 0🔄 0⭐ 0
  • Jan 7, 2026, 1:00 PM

    @pavel Re "Well, besides quality, gpuISP only has one output. We need that output for preview" - the way how e.g. Snapshot works right now is that it uses the same buffers for preview/viewfinder as well as encoding video or still images.
    A proper multi-stream architecture will certainly be nice long-term - but I don't see why we wouldn't just implement that in the gpuISP when we get to that point (so it can have multiple outputs).

    💬 1🔄 0⭐ 0
  • Jan 7, 2026, 1:11 PM

    @pavel P.S.: encoding RGB/YUV to jpeg (or any image/video format) is something best left to the clients, IMO. Those already have plenty of options to do so, such as using #gstreamer, #ffmpeg or other libraries.

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Jan 5, 2026, 9:05 AM

    @rmader The 3a isn't a device I have, but I'm willing to try to get one :)

    Do you mind if I ask if you're using PostmarketOS on a Pixel 3a as a daily driver? If can you both send and receive texts and calls reliably?

    💬 1🔄 0⭐ 0
  • Jan 5, 2026, 10:47 AM

    @jbowen unfortunately I don't use it as a daily driver yet and thus can't say much about the reliability, sorry :(
    What I can say, though, is that it'll (most likely) be one of the first devices with somewhat calibrated cameras in the coming months (already playing around with that here).

    💬 2🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Jan 5, 2026, 7:40 PM

    @rmader @jbowen We've had a "somewhat calibrated" camera on Librem 5 for years now - it needs to be redone more rigorously as the calibration shots used weren't perfect, but at this point this will be fine-tuning rather than drastic improvement.

    I've personally never cared much about the selfie cam though, and I'm not aware of anyone else calibrating that one so far, so it's still something left to do.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 1
  • 💬 0🔄 0⭐ 0
  • Jan 5, 2026, 10:12 AM

    @jbowen @pilum I'm on a Fairphone 4 and it's my daily driver. Honestly basically a fairly standard Android experience I think, with the caveats that I do most things through a browser and don't use a banking app.

    💬 2🔄 0⭐ 0
  • Jan 5, 2026, 10:43 AM

    @VincentTunru @jbowen @pilum plus one (Fairphone 6 + /e/OS), I'm coming from a degoogled Pixel 5 (Calyx OS, similar to Graphene OS which I want to experiment with also on the old phone). You will really want Aurora or similar to access the Play Store for "normie" things like banking apps and non-FOSS software in general (it's built-in on /e/OS out of the box) but it works really well. The Fairphone 6 has its own camera app which also came to /e/OS with the latest update and it really makes the phone camera capable/on par with mid-tier phones in that regard also.

    💬 0🔄 0⭐ 0
  • Jan 5, 2026, 5:21 PM

    @VincentTunru @jbowen @pilum I use an /e/ Fairphone 4 I bought from Murena as daily driver, and three banking apps that work just fine (all of them installed using Murena's own appstore which uses an anonymous google play session somehow)

    💬 0🔄 0⭐ 0
  • Jan 5, 2026, 9:49 AM

    @jbowen I'd lean towards Jolla C2 (Sailfish OS) as a true functioning (with full glibc) device (Uses rpm packages). It's also quite large if that's any concern/bonus. Also it's from a Finnish company (Not US/China) if that's important to you.

    TL;DR No NFC, No biometric auth, camera app is best described as "basic" but on the C2 (and some other devices) you get the Android subsystem to aid transition, and it will run "true" Linux/aarch64 apps e.g. fosstodon.org/@sxa/11416087631

    💬 0🔄 0⭐ 1
  • Jan 5, 2026, 11:00 AM

    @sxa I'm using a Pixel 10 Pro XL :) <3 larger phones :)

    I've seen chatter about Jolla/SailFish having proprietary components. Do you have any insight/comment on that topic?

    (I'm still scrolling through responses and haven't started investigating that yet)

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Jan 5, 2026, 11:15 AM

    @jbowen Thanks @sxa ! I've not read all the replies (there are many!) but always happy to opine on the topic of #SailfishOS.

    It's been my main phone OS for many years.

    To directly answer your question: Sailfish OS is GNU/Linux, but has some proprietary middleware/UI components. E.g. the Android App Support is closed source. Jolla has recently accelerated its efforts to open other parts:

    forum.sailfishos.org/t/open-so

    Separately, this page may be helpful as a launch point:

    linuxonmobile.net/

    💬 2🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0