I do trust them, they're great people, but I don't like the proprietarieness of it :(

Sadly SFOS is largely (UI, core apps) proprietary.

Sadly SFOS is largely (UI, core apps) proprietary, including that Android support layer.

Sadly SailfishOS is more proprietary than AOSP, with it's UI and several core apps being proprietary and no indication of ever open-sourcing them.

We did, but the deadline for that has passed ages ago sorry.

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.

https://source.denx.de/u-boot/u-boot is the upstream source code, https://gitlab.postmarketos.org/tauchgang/u-boot is taking that and building pre-built images for it.

That's not a supported setup or possible atm.

I appreciate the effort, but this is sadly a waste of effort. Google will not listen to this, they have nothing to gain from it and the people that care about this are not with enough people. The only real solution is moving away from Android and AOSP entirely, Plasma Mobile exists and on distributions like postmarketOS it's an actual big-tech free platform that the users control rather than a big corporation.

My Valve Index only has black and white cameras. And what other headset are you talking about? They never made more.

You say that but so far nothing points to it being developed for that device. It seems to mostly be a personal project by the developer, especially because this is the first time a bunch of KDE developers seem to see the code. The author of the MR even updated the MR to mention they do not work for Valve. That doesn't mean it isn't useful for that device of course, it very much makes sense to run on there. But again, the black and white cameras of that device makes this mode less interesting.

Or KDE's built-in Flatpak permissions settings. But yeah I guess, it's mostly needed for applications that haven't adopted to the new Portal API's yet which is the better solution, but this works for now until applications have updated.