Re: MX-23 Rpi Respin -- Beta testing

Message

#101 Post by **Jerry3904** » Sat Dec 16, 2023 11:08 am

We could leave it as an explicit option in the Tips doc. It's less work and I'd be OK with it.

#102 Post by **Jerry3904** » Sat Dec 16, 2023 11:42 am

Netflix can't work with our ESR version. I tried downloading directly from the Mozilla site, but they have a single blob for all Linux and I couldn't get it to launch on the Pi 5. I'll check the documentation again, but have now just taken out the Firefox section altogether and let the user pursue it on his/her own.

#103 Post by **dolphin_oracle** » Sat Dec 16, 2023 1:51 pm

The Firefox on the betas is not esr. It’s rpi’s firefox.

Mozilla only provides x86 builds.

#104 Post by **Jerry3904** » Sat Dec 16, 2023 2:13 pm

Ah, the things I don't remember...

#105 Post by **Jerry3904** » Sat Dec 16, 2023 2:46 pm

Installed the RPi Firefox and the other two files--butNetflix won't show. That may explain why I was unable to find it any longer in the RPi Documentation.

#106 Post by **dolphin_oracle** » Sat Dec 16, 2023 2:50 pm

on the splash, the raspi-config splash enable works only with their own splash theme.

however, I can enable whatever plymouth theme you want. the current default of MXLiveLogo is a little heavy on the pi400, but it does work smoothly. futureprototype-mx is better.

if you want one we don't have, probably should zip up the theme folder and sent it. it should not rely on deleting/replacing any existing graphics, as that will cause a package conflict if there is an update. well, maybe not a conflict, but the changes will be lost.

#107 Post by **Jerry3904** » Sat Dec 16, 2023 3:31 pm

dolphin_oracle wrote: ↑Sat Dec 16, 2023 2:50 pm on the splash, the raspi-config splash enable works only with their own splash theme.

J: I found in my testing that it will work with a graphic theme (at least the single one I tried) renamed to and replacing pix/splash.png

however, I can enable whatever plymouth theme you want. the current default of MXLiveLogo is a little heavy on the pi400, but it does work smoothly. futureprototype-mx is better.

J: I don't know that off hand, but if you feel good about it then I say let's go with it

if you want one we don't have, probably should zip up the theme folder and sent it. it should not rely on deleting/replacing any existing graphics, as that will cause a package conflict if there is an update. well, maybe not a conflict, but the changes will be lost.

Thanks for the look.

#108 Post by **dolphin_oracle** » Sat Dec 16, 2023 4:00 pm

Jerry3904 wrote: ↑Sat Dec 16, 2023 3:31 pm
dolphin_oracle wrote: ↑Sat Dec 16, 2023 2:50 pm on the splash, the raspi-config splash enable works only with their own splash theme.

J: I found in my testing that it will work with a graphic theme (at least the single one I tried) renamed to and replacing pix/splash.png

only if their theme is already installed. the rpd-splash-theme (name?, i forget exact name) package is just a theme pack, but the active splash function in raspi-config doesn't do anything unless its installed. its not actually necessary to have rdp-splash-theme installed.

#109 Post by **Jerry3904** » Sat Dec 16, 2023 4:29 pm

Ok, didn't realize that. I think I might have installed it in an earlier trial.

We would certainly like to have an easy off/on for splash if possible IMO, especially since we don't have Boot Options available.

BTW: since we're going to be using blanking as a screensaver, I'm going to look again at that script I started once (if I can find it) before you incorporated dpms time into the MXFB Tweak. It would be nice for the user to have an option to change the time without having to go to the console. Might be something that @Melber could do a yad with.

EDIT: here it is, kind of clunky...

Code: Select all

# this script sets screen timeout value in seconds using xset for a given session. It was intended for use with Fluxbox and other Window Managers in order to override the default of 600. When placed in the Autostart file, it enables the user's value to persist across sessions

## the parameter TIMEOUT is set in $(HOME)/.config/screen-timeout.conf

source $HOME/.config/screen-timeout.conf

xset -dpms && xset s $TIMEOUT

exit

#110 Post by **Jerry3904** » Sat Dec 16, 2023 4:59 pm

however, I can enable whatever plymouth theme you want. the current default of MXLiveLogo is a little heavy on the pi400, but it does work smoothly. futureprototype-mx is better.

J: I don't know that off hand, but if you feel good about it then I say let's go with it

That said, the MX-23 animation would certainly be the best if it's not just deathly slow on the 400.