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?)

  • TheMightyCat@ani.socialOPEnglish
    3·
    8 hours ago

    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.