Found another oddity with the beta. Every morning I come down and the screen is on. Ropieee is set to reboot at its default Tim everyday but isn’t the screensaver supposed to kick in after 10 mins? If I start to play something and then stop and leave it the screensaver kicks back in after ten.
All, I’ve pushed out an update to the beta channel. This involves touchscreen stuff only.
Anyhow, I’ve made a set first fixes for all the valueable feedback I received. It’s still not complete yet, but with these set of patches the base is getting in good shape.
This version introduces a settings screen. This screen is accessible by pressing the bottom right corner. I’ve not placed a button or anything there, to keep the screen rather ‘clean’. When you’re in the settings screen everything is rather self-explanatory. There’s a big save button and the screen will be left again by either pressing the text at the top or waiting for 10 seconds.
FIXED: screensaver does not stop when starting play via remote
FIXED: screensaver does not kick in on start up
IMPROVEMENT: introduce settings screen
IMPROVEMENT: possibility to change contrast
IMPROVEMENT: switch time format
IMPROVEMENT: limit text width on long titles/album
As usual these changes will be pulled in somewhere the coming hours.
I just purchased a 2nd RPi 3 with Allo Boss dac + Volt amp for the bedroom.
To be powered by RoPieee.
Will try to use this combo (2x 50 W) to power a pair of Dali Fazon Sat’s.
I may be adding an SVS SB-1000 later.
I am using Arch Linux Arm on my Raspberry Pi and use the following setup to run a full screen web browser. Once I install Arch Linux Arm: pacman -S xorg-server xorg-xinit xf86-video-fbdev xorg-xset matchbox-window-manager chromium
I use this custom systemd service file (/usr/lib/systemd/system/gui.service) to start up the browser at boot time, and to restart it automatically if it crashes:
[Unit]
Description = Starts Xorg as defined in /home/USERNAME/bin/gui.sh
After = systemd-user-sessions.service network.target
Conflicts=getty@tty7.service
[Service]
User = USERNAME
Group = USERGROUP
PAMName=login
Type = simple
TTYPath=/dev/tty7
ExecStart = /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /home/USERNAME/bin/gui.sh -- :0 -nolisten tcp vt7
Restart = always
StandardInput = tty
[Install]
WantedBy = multi-user.target
Which runs this script at /home/USERNAME/bin/gui.sh. The xset dpms command turns off the Raspberry Pi touchscreen after 60 seconds. And it wakes back up when tapped.
#!/bin/bash
export DISPLAY=":0"
xset dpms 60 60 60 &
matchbox-window-manager -use_titlebar no -use_cursor no &
/usr/bin/chromium --kiosk <URL TO EXTENSION>
Just to say that the first time round, the software was not installed, but these commands got me up and running. It’s now running on a RPi2, and looks very good. Great work!
Just updated to the latest beta version. Screen brightness adjustment is fantastic. I did a shutdown and reboot and the brightness settings are retained.
I’m looking forward to getting this loaded up when I get back from my holiday in a couple of days time. I’m wondering what happens if you have more than one core on your network with ropieee?