Add support for empty and logo screensaver modes to reduce (OLED) screen burn-in

[basraven]

Add support for empty and logo screensaver modes to reduce (OLED) screen burn-in

• Introduces ScreenSaverType enum with NORMAL (slideshow) and EMPTY_SCREEN (black screen) options.
• Adds screensaverType user preference to control the screensaver type.
• Adds screensaverShowLogo user preference to show or not the logo on the screensaver.
• Implements the empty screen logic in DreamView.
• Update DreamHost logic for the new settings.
• Add the new settings on the Customization screen.

Issues
Fixes #3256 #3269 #1888

@nielsvanvelzen For some reasons the default screensaver from the Chromecast with Android doesn't work, hence these screensaver changes. Met vriendelijke groet!

[nielsvanvelzen]

If you don't want the screensaver to show up you can just disable it. I don't see any point in the black screen mode.

[basraven]

@nielsvanvelzen Thanks for getting back on this, appreciate it!
From a usability point, if you disable the screensaver, then your screen will burn in because for the Google Chromecast with Android TV the native screensaver doesn't take over (tested on multiple devices). So right now we provide only 2 options:

1. No screensaver as you suggested, with the menu burning in the Jellyfin menu in your (OLED) tv
2. Through the screensaver where the logo burns in the TV.
   Neither aren't ideal

Bonus points of having an empty screensaver over one with image content: it's better for the environment because your screen consuming less energy. It's actually the option I use myself now (I already compiled a version for myself at home).

Overall it's a quality of life feature that I'm very much enjoying that I wanted to share here with the rest of the community.

[nielsvanvelzen]

If you disable the screensaver in our app the system screensaver is allowed to run. If it does not show up that means you either have disabled the screensaver of there is some bug in your system. At the very least, not something that should be a concern for our app to deal with.

[basraven]

If you disable the screensaver in our app the system screensaver is allowed to run.

I've tested this on multiple devices because in theory you are absolutely right, that is the expected behavior. On many apps like Netflix or HBO it actually does, but on the official Jellyfin app (installed from the Google Playstore) it does not. I created this fix exactly because of this odd behavior that is specific to Jellyfin.

[ethaldeman]

If you disable the screensaver in our app the system screensaver is allowed to run.

I've tested this on multiple devices because in theory you are absolutely right, that is the expected behavior. On many apps like Netflix or HBO it actually does, but on the official Jellyfin app (installed from the Google Playstore) it does not. I created this fix exactly because of this odd behavior that is specific to Jellyfin.

I have observed this behavior on my onn 4K. Dispite disabling the jellyfin screensaver, the system screensaver does not run. However system screen saver does run on other apps.

[nielsvanvelzen]

That would be a bug then, perhaps within our app. But that would need to be tracked in a GitHub issue and not worked around like this.