07-18-2019, 12:19 AM
(This post was last modified: 07-18-2019, 01:21 AM by TheOldPresbyope.)
(07-13-2019, 11:40 PM)Tim Curtis Wrote: Isn't the slow startup due to the remote having to re-connect after coming out of sleep mode? The initial button press is probably lost because it serves only to wake up the remote and reinitiate the BT connection.
For example if my Mac Air is sleeping and I key in my login password the first keypress is lost and just serves to display the login screen. I end up having to reenter my password after the login screen appears.
Hi, Tim.
It looks like you were right.
I contrived an experiment which shows that when I click the Satechi Remote to "wake up the connection" it takes 3+/- seconds (more likely - than +) for the message to appear in syslog showing that udev has done its job. Other experiments suggest that the Python script starts running much less than a second later whether from udev I call my helper script or use the systemd machinery I've contrived since.
it's annoying because with a 3 second delay a user is likely to keep clicking impatiently. Even I do
It works fine once awake.
I'm going to move this to a github repro so modifications will be easier to track.
Regards,
Kent
Post edit: appears to be closer to 2 seconds, but still...
