08-16-2018, 04:29 AM
Hey Viridian, sorry to hear about the issues.
The first thing I'd try is our new update to systemd and see if the autorestart will just restart the service and get everything working as it should. To do this, go to ~/Freeplay/freeplayili9341 and pull from the repo with git pull. then if you ls, you should see some new .sh files. Run, in this order, uninstall.sh, fbcpSystemdConvert.sh, then setupZero.sh. This should convert everything, including the old fbcp driver, to systemd and could be the easiest fix for this issue since I suspect that your image is old enough that /boot/config.txt's HDMI mode is still set to 1024x768 and the resolution change can cause some problems for the new driver.
The first thing I'd try is our new update to systemd and see if the autorestart will just restart the service and get everything working as it should. To do this, go to ~/Freeplay/freeplayili9341 and pull from the repo with git pull. then if you ls, you should see some new .sh files. Run, in this order, uninstall.sh, fbcpSystemdConvert.sh, then setupZero.sh. This should convert everything, including the old fbcp driver, to systemd and could be the easiest fix for this issue since I suspect that your image is old enough that /boot/config.txt's HDMI mode is still set to 1024x768 and the resolution change can cause some problems for the new driver.