The Springboard is the main tingbot ui, basically the app launcher carousel with status bar/settings.
I have only had a short look at it after receiving my Tingbot, but I think the best way to tinker with it might be to just access it via ssh.
If you use Linux, most file managers can access it when you type something like ssh://pi@raspberrypi/ in the location bar. Otherwise, most FTP programs can access it as 'sftp'.
Don't forget to make a backup in case you break stuff.
I don't know (no TingbotOS flashed at the moment ) the best way to restart it, but would try to just run and exit an app (please correct me).
@khromov Hi, I'm not using a "real" tingbot app – instead I set up a "normal" raspbian on my tingbot made to work with the Tingbot display.
It seems the instructions on how to set that up (first link in the original post) got merged with instructions on how to set up retropie, but if I remember correctly, it's mostly the "Tingbot Overlay" stuff still mentioned there.
Maybe (untested! please only use on an installation you consider replaceable!) my ancient script on the tingbot slack still works: https://tingbot.slack.com/files/U1E85V4Q6/F2LE7Q0RX/prepare_lcd_raspbian_sh.sh
Once that is set up, you can try the nodejs and tingbot-node installation as described on https://github.com/jgibbon/tingbot-node to get the button controls and brightness running. Test it with some of the examples on the same page and let me know if it still works.
In the code from the video, I run chromium from node js as follows:
This would be a great feature: have a kind of screensaver, which could be configured to turn off the screen after inactivity, and as soon as you touch the screen or push any buttons, it would wake up the screen !
In the meantime, @GeoffOs, you could use the new /etc/tbbuttonsd.conf and configure two new combos, the 1st one to turn off the screen by calling a tingbotapp with only screen.brightness = 0 and the 2nd one to turn on the screen by calling a tingbotapp with only screen.brightness = 100.