Next time, try following;
systemctl stop toholed.service
Remove toholed for 1 minute and reconnect
systemctl start toholed.service

For me this is matter of life and death

I was thinking could this be caused by hardware connection break between toh and phone, which might get the proximity sensor to reset, and thus loose configuration (and it will not generate interrupt from proximity clear and therefore not wakeup the display), but restart should reconfigure it. Unless the display controller itself gets so messed up that it refuses to show anything.

Updated HW has better reset circuitry, and i have to make some detections to the daemon to see is the display and proximity/ALS sensor still in good mood.

(And repeating me - journal could be very helpful)