Ah, you used AI. Too bad. We do indeed not permit such contributions for the reasons listed there. That means your images will continue to be separate from the pmOS project for the forseeable future, to bad.

Hey that’s awesome! We had https://gitlab.postmarketos.org/postmarketOS/charging-sdl for this use-case before but it kinda died. Are you going to upstream what you made so other devices can use it too? As you mentioned the PPP already, other devices could very much use it too ;)

I’m not actually the lead dev of pmOS btw. In fact, we don’t have any lead dev. We do have the core team though, of which I’m part of, but that does not make me a lead.

Not sure what to tell you, but the code is available on their GitHub organization. Both Nemo Mobile and AsteroidOS use it and have working window management and such because of it.

Btw I just read https://catcrafts.net/posts/fairphone-6-postmarketos-working-main-camera and the section “Meeting the lead pmos dev” jumped out at me. Ik ben dezelfde van Tweakers die je daar noemt ;) But I’m not the lead dev. In fact, there is no lead dev. There is the core team of which I’m part, but calling me a lead is misleading. Also you said “can be disproved with a 10s search” but I searched for at least a minute and didn’t see it. Sure I could’ve tried harder but then again, this was just something said under a Tweakers article, I won’t dedicate to much time to it ;). I understand that you didn’t like that I thought you weren’t upstreaming things, but now you’re calling me out as if I did something wrong while I honestly tried but just didn’t manage to find anything. I rather not have us calling each other something we’re not and I most definitely did my best not to.

Just a note, if with “window manager” you mean the actual software part that does “window managing”, that is already open-source. It’s Lipstick and has been FOSS since, I think the beginning? The relevant parts that are closed is the UI layer, Silica, which doesn’t show any signs of being open-sourced any time soon. Also various core apps are proprietary as well, I think just the browser isn’t.

Sure, but that does make it more proprietary than say AOSP. That said, although the rest is “bog-standard”, the whole middleware (the relevant FOSS bits of SFOS) is based on Qt 5.6 which is absolutely ancient. A bunch of it supports Qt6 due to work being done both by the Nemo Mobile folks and myself (need it for AsteroidOS), but SFOS itself is still stuck on Qt 5.6 for the forseeable future due to licensing issues.

And that’s a major issue imo.

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.

Source? I found the MR, https://invent.kde.org/plasma/kwin/-/merge_requests/8671, and nothing about that shows it’s for the Steam Frame. In fact, the video shows a colored passthrough camera mode while the Steam Frame (sadly) has a black and white camera only.

what a flatpac is and why people hate it,

Huh, most people actually like Flatpak, and for good reasons too.