Month: September 2019

I just got myself a Vivoactive 3 watch because that is the device I am recommending people use, so I thought I should have one myself.

I spotted a couple of issues with it – the ‘key’ button on the side exits the app without showing the confirmation dialog as it should, and the battery level dispaly field is partially obscured by the clock. Issues here: https://github.com/OpenSeizureDetector/Garmin_SD/issues.

Has anyone spotted any other issues that I should fix at the same time?

Thanks, Graham

(graham@openseizuredetector.org.uk)

I think I have a solution to the problem that some users were finding if they upgraded Garmin Connect to a version that is more recent than 4.19.1, where the watch would not send data to the phone.

For those who are interested in the technicalities, it was a security improvement that Garmin implemented that meant that all http requests had to be encrypted (https). Now the communication between the watch and the phone is unencrypted, so it stopped working. It only happened on the most recent versions of Android where Google implemented this change – which is why I can’t reproduce it because I never buy the latest phones.

There was a bit of uproar in the Garmin developer forum, and Garmin have implemented a fix in the most recent version (4.22.1). Unfortunately they gave an exception that allows unencrypted connections between the watch and the phone, but not other web sites.

Unfortunately that did not cure the issue for us. This is becasue GarminSD sends the request to http://localhost, and the exception is to http://127.0.0.1. Now I thought they were both the same thing, but aparently not.

So to cure this I have produced V0.5 of GarminSD that sends requests to http://127.0.0.1. This works ok on my phone with Garmin Connect V4.2.2.1. All this means though is that I have not broken it, because it was working ok for me for starters. So please will some of you who were affected by the issue try installing V0.5 of GarminSD from the source code repository, and using it with the latest Garmin Connect from Play Store? And let me know if it works of course!

(Remember that when you copy GarminSD_v0.5.prg onto your watch GARMIN/APPS folder, you have to name it GarminSD.prg (ie no version number) – it should show V0.5 on the display as it starts so you know it has upgraded correctly)

Thanks,

Graham (graham@openseizuredetector.org.uk)

I have just uploaded V3.1.9 of OpenSeizureDetector to Google Play Store – it should go live in a few hours, unless I get into another protracted debate with Google over permissions…..
The changes in this version are:

• Now requests READ_PHONE_STATE along with SMS permissions. This was because some phones failed to send SMS messages without this permission
• Fixed the issue with Garmin Seizure Detector not producing warnings but going straight to alarm state – you now get a warning and if the seizure-like movement continues for another 5 seconds it gives a full alarm.
• Added fault pips for missing heart rate data if the heart rate alarm is active.

The change to the Garmin Seizure Detector should be particularly useful for those users who are finding this a bit too sensitive and giving too many false alarms.

Although it should update automatically via Google Play Store, if you want to try it earlier you can download it from the project github repository here: https://github.com/OpenSeizureDetector/Android_Pebble_SD/raw/master/app/release/app-release-3.1.9a.apk

As always, please let me know if you have any issues with this update.

Graham (graham@openseizuredetector.org.uk)