![]() Be sure to save that file elsewhere, since you'll lose it if you re-image. TIP: I define the above as backlight_off and backlight_on in ~/.bash_aliases. ON: sudo -E sh -c 'echo 0 > /sys/class/backlight/rpi_backlight/bl_power' ![]() # disable automatic screensaver, app will handle thisīin/python3 ergo.py >stdout.log 2>stderr.OFF: sudo -E sh -c 'echo 1 > /sys/class/backlight/rpi_backlight/bl_power' # X11 gets the resolution wrong with the GL driver xsession file.Īdd this at the top of ~/.profile to start X when auto-logged’in: if thenĬreate an ~/.xsession file for X setup and starting the app: #!/bin/bash “Fake KMS” GL driver works well on my Raspberry Pi 3a, but unfortunately X11 gets confused of the screen resolution and needs a manual hint by running xrandr in the. And remember to enable the GL (not Legacy!) driver in raspi-config or Kivy will be nasty slow.Add After=getty.target in the section of to show fewer of the boot msgs on the TFT (and maybe boot a tiny bit quicker).Make sure splash screen at boot is disabled, raspi-config: System -> Splash at boot.Add disable_splash=1 to /boot/config.txt (not 100% sure this helps but it doesn’t hurt either…).Empty out /etc/motd, so it’s not shown when user is logged in. ![]() Couple of small tweak/optimizations to make boot faster/cleaner:.raspi-config: System -> Boot -> Console Autologin for user kapet (that should be automatically the case if sudo from that user).I’m using chilipie-kiosk as the concept for the basic setup, steps: The basic Kivy installation is described here. The system might even be shut down between it’s use, I’ll see about that later. This will run a fullscreen Kivy app and the screensaver should be steered by this app and not happen automatically. The setup needs to be a little different than the one described above. I have an (old) Watterott 2.8″ touch display I want to use on a Raspberry 3a. This “needs” (*ahem*) a Raspberry Pi with a small touchscreen as a local interactive controller. I’m working on a little something that I’ll share more about later. ![]() Side note: Chromium does not include Google’s Text-to-Speech system, and I could not get some system-side thing (e.g. If I remember correctly I also struggled a lot with getting Chromium to properly output sound to a USB-connected soundcard/speaker, but I don’t remember what I did to get it to work – I think it was about running pavucontrol while Chromium was playing some sound, and then fixing devices/volumes in there. I should consider a regular reboot, but this is running stable enough not to require that. To make the boot slightly faster and avoiding extra graphics the /boot/cmdline.txt includes logo.nologo and /boot/config.txt includes disable_splash=1 ![]() xscreensaver file for a simple blank screensaver: timeout: 0:01:00 Using xscreensaver because here it’s trivial to include in the LXDE autostart. Basically configure the raspi to autologin with graphical UI, then configure the user’s X session in ~/.config/lxsession/LXDE/autostart like this: -check-for-update-interval=31536000 -noerrdialogs -disable-features=TranslateUI -disable-infobars -incognito -kiosk The method I’m using follows what’s lined out here, or on various other pages. Intention is that this is “off” by default, turns on when the screen is touched, then allows interaction with a browser, and after some time of no use turns off again. Directly boot into a graphical screen and allow user interaction through a touchscreen. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |