My quest to 100% feature completeness continues!
Today i bring before you… The working microphone!
Now everyone is going to ask:
Does this mean working calls?
I asked the same thing, and with maybe a bit too much excitement i inserted my SIM card.
But the answer is no, neither audio nor mic work in calls.
It seems having them work in userspace is not enough.
So it seems that that requires additional work (coming soon!)
To give updates on my previous posts aswell.
For all 3 (GPS, NFC, audio) patches have been submitted, i’ve had contact with the freedesktop and maintainers on the LKML and they have requested changes, and a v2 is out for all. But don’t expect them to reach phones anytime soon.
GPS:
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/470: maintainer requested some renames, adressed and waiting for review.
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1463: stuck as draft until libqmi patch lands
NFC:
https://lore.kernel.org/all/20260705190621.128257-1-jorijnvdgraaf@catcrafts.net/ Sashiko AI review found a bug in my code and maintainer requested small change, both addressed in v2.
audio:
https://lore.kernel.org/all/20260705033743.305783-1-jorijnvdgraaf@catcrafts.net/ maintainer requested significant changes, addressed in v2
https://lore.kernel.org/all/20260704192857.88366-1-jorijnvdgraaf@catcrafts.net/ awaiting review
https://lore.kernel.org/all/20260705033830.305907-1-jorijnvdgraaf@catcrafts.net/ RFC patch resulting from requested changes, i think this one might get quite the tail…
Audio is turning into quite the story, way more then i expected.
When having a working patch ive learned the work is far from over.
I was thinking of maybe hosting my own downstream kernel with all my fixes, if there is demand for it.
(also open letter to the mods if these posts are becoming spam and if its turning too much into my personal blog?)
Great work! You should set up some way to receive donations for this. I would love to see this phone being functional as a daily driver.
Your work is so very much appreciated. I might end up buying a fp6 thanks to you and the PMOS project.
Thank you for this!
God’s weakest soldier vs Satan’s strongest mobile OS
Thanks for your effort. I hope this eventually trickles down to the FP4 🥺
I’d love to daily drive mine on pmOSI am unfamiliar with the hardware on the FP4, if it’s a similar chip it may help, but if it’s completely different hardware i want to be honest and most likely it won’t.
As sunshine noted what does help is building up the linux phone ecosystem, the more users -> the more developers -> the more support the more users -> the more developers and repeat
I hope this eventually trickles down to the FP4
It should at least bring more of the community over.
There are at least 9 pmos posts on r/fairphone.
Fairphone 3: mobile data and sms work.
Fairphone 5: all the sensors work
Thank you!!!
@TheMightyCat Keep up the good work.
open letter to the mods if these posts are becoming spam and if its turning too much into my personal blog?
No way, you’re making the best posts here! Keep it up!
Then I’ll keep making them!
i for one think what you’re doing is awesome, thanks
neither audio nor mic work in calls.
Take a look at
callaudiod, MAYBE that’s its fault.Edit:
PmOS could have moved from callaudiod to a wireplumber plugin.What annoyed me greatly is that for some reason pmos ships with both pulse and pipewire but only use pipewire for video and pulse for audio? Spend a while figuring out why audio wasn’t showing up with pipewire when it wasn’t even being used
On the majority of devices that do have working call audio, it works with PulseAudio only. The Wireplumber plugin @MrSoup@lemmy.zip mentioned is only part of the equation, there is more work to be done.
You can already switch to PipeWire for audio just fine if you want to try it out though.
Do you take donations?
Thank you really! But im just a guy trying to defeat big tech in my free time :)
If you want to donate, please do so to linux projects like KDE and PostmarketOS
They definitely deserve a few euros their way!
Thank you very much! Truly!
But if you have spare euros you want to donate them to serious linux organizations that maintain your distro, DE, or any other software you use.
If you really want to give it to me specifically then please make a donation to KDE in my name.
I just sent 50 euros to KDE’s SEPA account. Thanks for your efforts ;)
Wow! thank you!!!
Man I cant wait for this to be ready for my phone.
Fairphone 6 is brought up to (20.5/28) 73% functionality! We’re getting close!
This is great coming from a Linux and FOSS enjoyer. PostmarketOS is not an appealing name for an OS though lol. Although the name makes sense for its purpose.
Although the name makes sense for its purpose.
Well I would want to push back on that.
“PostmarketOS” implies it’s something flashed on well, postmarket devices. Not new or fresh from the factory.
Fairphone already sells devices coming fresh with e/OS, how great would it be if one could just purchase a linux phone with PostmarketOS and it just arrives without having to unlock the bootloader or flash?
That is the path to mass market adoption.
PostmarketOS is not an appealing name for an OS though lol.
There are plans to replace the current name.
Do they accept suggestions? I would like it to be called Skagloodle.
We did, but the deadline for that has passed ages ago sorry.
I am being temporally discriminated.
How about LMOS? Linux Mobile Operating System
How about LORE. As a nod to Data’s brother Lore (who obvs are both androids). Could stand for smth like Linux Operated Revived Electronics
Should be called Android2, just to fuck with everyone involved
I actually like the name. Easy to understand, difficult to missspell, easy to google (insert favourite searching machine here).
Completely agree
At some point I would love if you wrote a guide on how you got started, things you learn along the way, pitfalls to watch out for. Not only around getting everything working, but how to upstream it to the kernel.
I know in a previous post you asked for help on contributing to the kernel, and now you already have PRs! That step has always intimidated me so seeing how you approached it would be super helpful
Well do i have good news!
https://ani.social/post/33637344
Some kernel specific things i learned since then:
Check lore.kernel.org before starting on something, it may have already been done.
When working with a downstream kernel like the one on the fp6, Check if upstream may have changed, this is what happend with my audio v1 patch.
This is what the maintainer replied with:
you no longer need to care about what the profile specifies. The aw88261 driver properly participates in format negotiation now. The “firmware” register list binaries are therefore nearly irrelevant. Please don’t add any more of this force-32-bit nonsense! We’ve just gotten rid of it on the Fairphone 5 and other kodiak devices.
But that 32 bit nonsense was the way to do it in 7.1, their patch getting rid of it was only on 7.2, so now im checking upstream beforehand and backporting relevant patches to 7.1.
Read the process documentation very carefully, otherwise you look like my netdev v1 patch and a fool who can’t read, since then i have been critically AI reviewing my patch series on etiquette and process specifically, which gives me alot more peace of mind before sending.
I did see that post previously, but thank you for linking it!
The info on the kernel is exactly what I had in mind!
I’ve got a pixel 4a lying around to tinker with, and the touchscreen is not working. Any chance you could give me pointers on how to get started on fixing that?
My experience is in programming / data science / data engineering, so not too close to embedded systems / hardware 😅
If you mean the touchscreen isn’t working because of a hardware issue I’m afraid im also out of my knowledge here.
If you mean it doesn’t work because there is no driver for it the biggest tip i can give is look at android. If there is a perfectly fine android driver right there up for grabs don’t reinvent the wheel.
doin the lord’s work, son













