Cheers. Glad it works. Obviously, you can fiddle with the timer there and use something other than 6 seconds… find the sweet spot where it works but you arent waiting around for it.
Also … if it ever somehow does start too soon you can still run it again
systemctl start syna3602-driver-workaround
Of course since we know it works … you could fine-tune the service as well … maybe better After lines or similar, or config it to retry X times, etc.
Yes … on second though … maybe try implementing the Conflicts,After,WantedBy params from phils here:
(and it might work without needing the sleep)