I don’t want to use Osmc or LibreELEC. What I’m going for is something like Android TV (tried using LineageOS but that didn’t work out for me).

I was interested in something like Plasma Bigscreen but most of the tutorial is about 4 years old and point to using an old image.

I installed the Debian package. After that, I logged in and set Automatic login, and switch the session to Plasma Bigscreen (x11). After applying and a reboot, it launched Plasma Bigscreen but some widgets (like the audio, KDE Connect) froze when clicking on them.

What do you recommend? I prefer to use a Raspberry Pi.

    • @AndrewZabar
      2•1 month ago

      You could also always nativefier it and make it like a webapp. I have some sites setup like that on my machine.

      • @chronicledmonocle
        2•1 month ago

        Does that offer any advantages over the kiosk mode functionality? Looks like that repo was abandoned in 2023 and marked as archived.

        • @AndrewZabar
          2•1 month ago

          What repo? Use npm to get nativefier, the one from regular apt etc. are not current, they’re copies of older versions. Dunno why someone did that.

          • @chronicledmonocle
            2•1 month ago

            The GitHub repo of the maintainer shows that the project is archived and dead.

                • @AndrewZabar
                  1•1 month ago

                  Well it does what it’s supposed to do, so who cares.

                  • @[email protected]
                    1•1 month ago

                    If you look at the repo, the very first line in the readme links to an issue that briefly explains why you should care.

                    Unmaintained software comes in two categories:

                    1. The software is done. It does exactly what it was meant to do and it was written in a language and in such a way as to be pretty future proof. Examples are some basic code libraries or command line utilities.
                    2. The software had to be updated all the time to keep up with changing environments and security problems, so the dev got sick of it and dropped it. Or a better solution came along so the developer felt free to finally drop the burden.

                    Nativefier falls in the second category and the second clause. Don’t use it.