I have a Raspberry Pi with a touchscreen, and HiFi Berry Amp 2, as well as a couple of encoders, buttons. It is powered by a 12V 3A power supply to the Amp 2.
When I start the system the touchscreen does not always come on. Particularly first thing in the day, from cold. (If it is off for a while). The issue is solved by simply restarting - then it nearly always works. Also usually if only powered down for 1/2 an hour or so.
Is there a command to start/restart the touchscreen process that I could try mapping to a button action? Or other options to try like changing the order of the boot processes?
I do not think it is possible to start the touchscreen via SSH (?)
If you are using the Touch Display plugin the easiest would probably to disable and re-enable the plugin from the UI using a browser on another device (e.g. smartphone).
Thanks for the suggestions - I will try that anyway when I get a chance - tomorrow. (It currently switches on every time … this only seems to happen when the device has been off for quite some time).
Follow-up: Restarting the display plugin did indeed not work.
Comparing Xorg.log between no touchscreen and successful boot, there is a difference:
FBTURBO(0): Virtual size is 640x480 (pitch 640) vs
FBTURBO(0): Virtual size is 800x480 (pitch 800)
Then later in the successful boot version there are lines relating to the input device (touchscreen)
So it looks like the touchscreen is not detected during boot. In Raspberry Pi forums there are posts about possible power issue. (Though when the device successfully boots, I do not see any other power issues)
I’ll try adding boot delay or adding a separate power input for the touchscreen.