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

  • NightFantom@slrpnk.net
    link
    fedilink
    English
    arrow-up
    3
    ·
    13 hours ago

    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 😅

    • TheMightyCat@ani.socialOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      8 hours ago

      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.