A user reported having problems with the bluetooth connection between the watch and the phone failing after a while on a fairly new phone (Android 13)
I experienced something similar overnight on my test system using a Samsung A20e phone (Android 11) and my Vivoactive 3 watch – the only way I found to get it working again was to switch the bluetooth off and on again on the phone. This makes me think it is an issue with Android rather than Garmin software (and I am confident it is not OpenSeizureDetector doing it).
This is quite a worry because two failures overnight is an unacceptable reliability.
Update 22/09/2022: I used an old phone (Samsung J5) and a VenuSQ watch for 24 hours without issue, so it must be a specific hardware or software issue. I am currently testing my normal Phone (Samsung A20e) with the VenuSQ to see if that shows the same problem.
Update 23/09/2022: My Samsung A20e has worked fine with the VenuSQ now for 24 hours, so the issue may have been specific to my Vivoactive 3 watch.
Has anyone else experienced this problem? If so, which phone, watch etc. were you using? Please get in touch (graham@openseizuredetector.org.uk, or comment on the post about this issue on facebook.com/openseizuredetector).
Thanks,
Graham.