UPDATE 13/03/2023: This might be caused by the Garmin Connect app sending notifications to the watch from the OpenSeizureDetector phone app – open Garmin Connect and select the Settings->Notifications->App Notifications menu item, and ensure that most (if not all) apps are disabled from sending notifications to the watch.
A couple of people have been in touch recently complaining about the watch buzzing a lot when using OpenSeizureDetector, even with phone alarms switched off.
I think this is signifying a problem with the bluetooth connection between the watch and the phone – the watch will give a short buzz if it fails to send a batch of data to the phone. The phone however will only complain about not receiving data if it does not receive data for about 30 seconds (in which case it goes into a FAULT state and gives annoying fault ‘pip’ sounds).
The real solution is to investigate why there are problems with the bluetooth connection – maybe the distance between the phone and the watch, or possibly a hardware fault on either the phone or the watch itself.
A workaround is to use the special ‘ben’ build of the watch app, which does not buzz and is deliberately difficult to shutdown (to stop our Benjamin fiddling and shutting the watch app down). The latest ‘ben’ build is Version 1.2, and is available here if you want to use it: https://github.com/OpenSeizureDetector/Garmin_SD/releases/tag/v1.2
Please let me know if you have this problem though, as we could do with working out what is causing it.
Thanks, Graham (graham@openseizuredetector.org.uk)