Postmarketos is struggling to get the audio working for the Fairphone 5, i have noticed fairphone is working with the ubports community to get Ubuntu touch working, whilst postmarketos is left in the dark? This is an amazing OS (superior than Ub touch) and this will expand the options available to the fp5 users?
Please help this amazing community
Welcome to the Community Forum.
A curent & long-time Fairphone employee is already part of postmarketOSās Core Contributors which I take it is the most inner circle of postmarketOS. I would think that should ensure there is already a degree of support.
Well i have been looking into the development of the audio, and the work has stagnated. There has been no more work into the only issue holding this OS back from being a daily working rom. I personally think there should be more than 1 employee allocated with helping this brilliant OS.
BTW im not having a dig at the work that has previously been done. Its great that we do have UB touch as an OS option, but i feel like postmarketos should be running fine by now. Especially something as important as microphone and audio support
Just thinking out loud: the Bootlin company once did a crowdfunding to add Allwinner VPU support to the Linux kernel: https://www.kickstarter.com/projects/bootlin/allwinner-vpu-support-in-the-official-linux-kernel
That raised $31k to sponsor one dev to develop this fulltime. Not sure how open Fairphone would be towards such an approach.
Now thatās thinking outside-the-box! I am also curious about this.
I would definitely add funds to a project like this
In this case we could try asking.
@lucaweiss ā¦ Any insight on what possibly could help to resolve the FP5 audio situation?
In short, itās not working due to unknown reasons. If Iād know, it might already be fixed since a while. Speakers and microphone are quite different topics, but both have some issue that I havenāt been able to fix. The same applies to Fairphone 4 fwiw, I assume itās a similar problem for both devices.
Thank you for trying to get the audio sorted. Is there anything Qualcomm can assist with on this matter?
In theory yes, they have some interest in upstream support for the various SoCs but in practice they donāt really care about SM7225 since itās not one of the high-end SoCs or used in some IoT board of theirs.
Itās really upsetting that this project has seem to hit a brick wall. There must be someone out there who knows why itās not working 
Any ticket/issue to follow this audio issue ?
Some kernel logs that seems to be relevant
[ 74.944481] hdmi-audio-codec hdmi-audio-codec.4.auto: HDMI: Unknown ELD version 0
[ 74.944876] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC error (-22): at snd_soc_dai_hw_params() on i2s-hifi
[ 74.944947] DisplayPort Playback: ASoC error (-22): at __soc_pcm_hw_params() on DisplayPort Playback
[ 74.944961] MultiMedia1: ASoC error (-22): at dpcm_fe_dai_hw_params() on MultiMedia1
[ 74.945078] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC error (-22): at snd_soc_dai_hw_params() on i2s-hifi
[ 74.945111] DisplayPort Playback: ASoC error (-22): at __soc_pcm_hw_params() on DisplayPort Playback
[ 74.945123] MultiMedia1: ASoC error (-22): at dpcm_fe_dai_hw_params() on MultiMedia1
[ 74.945177] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC error (-22): at snd_soc_dai_hw_params() on i2s-hifi
[ 74.945208] DisplayPort Playback: ASoC error (-22): at __soc_pcm_hw_params() on DisplayPort Playback
[ 74.945219] MultiMedia1: ASoC error (-22): at dpcm_fe_dai_hw_params() on MultiMedia1
I guess the only people out there who could work this out are Qualcomm employees and they are might not even allowed to help if their management does not request it.
This is the current situation with SoCs for mobile phones. Everything is proprietary and it is almost impossible to reverse engineer all these chips.
To make it a bit more usable despite this issue, does someone was able to successfully make a phone call using a bluetooth device as the sound input/output ?
I configured a bluetooth handset, but it seems that ācallaudiodā still want to have the internal input/output. Any known way to force callaudiod to skip this check and use the device configured in the system?
Have you tried asking the AI ?
I asked the AI for advice on TWRP encryption and Waydroid on SailfishOS, and I was amazed at how quickly this new technology could read a long log file, spot the main issue, and suggest a correction. 
I did try that (as a stab in the dark), but it wasnāt much help
@oli.sax, I think youād need a huge context window to give enough of the relevant sources and logs to an LLM that it could make a useful determination.
Iām curious: what makes PostmarketOS better than UT in your opinion? Is it the aesthetics? Or the usability? Or is it the fact that it runs directly from Linux drivers rather than Android drivers through Halium?
Which user interface would you recommend? (Gnome Mobile, Phosh, Plasma Mobile or SXMO-DE-Sway?)
@oli.sax, if of any use, those are the reasons I think so, alongside how, because PMOS is based upon Alpine, it uses musl over GLibC, which should utilise less RAM (which matters on my FP4).
Itās easily the most powerful, since it exposes a āDocked Modeā which allows you to utilise KWin as you would on a desktop, irrespective of whether youāre actually connected to anything. However, Iāve found it to be slow and unstable:
In my honest opinion there are quite a few reasons (for me). The choice of user interfaces, plasma and phosh are amazing. The amount of devices that is supported is brilliant. It feels a more āpureā Linux os. And it runs much faster in my opinion.UT canāt recognise my 512gb sd card and pmOS can. And I would love to run postmarketOS as a daily driver (when audio is working) and move away from android as I donāt like the direction it is going in (for power users and tinkerers).
Love to all.
UTās interface is still in 2000 but postmarketOS with Phosh or Gnome Mobile (sorry, i donāt know whatās the difference) is the best UX Linux mobile design.