Month: June 2019

A user has reported OpenSeizureDetector Garmin Seizure Detector failing after upgrading to Version 4.20 of the Garmin Connect App.

It does not happen on all phones – it works fine on my Samsung J5, but did not work on his Sony Sony Xperia XZ2. He cured it by downloading the previous version (4.19.1) from the ApkMirror web site.

Please let me know if you experience a similar issue so I can work out what the problem is.

Thanks!

Graham.

There is a problem with sending SMS messages on some phones. If you have granted the ‘Send SMS’ permission but still get ‘Failed to Send SMS’ errors, please let me know which phone you are using so I can make a list of the ones affected.

I have a fix for it in a draft version of V3.1.8 of OpenSeizureDetector, but it is not available on Play Store. If you need to use it do the following:

• Download the V3.1.8 .apk installation file from our source code repository here and install it on your phone.
• Go to the phone settings screen and select Apps->OpenSeizureDetector->permissions. You should see a ‘Telephone’ permission is present, but not selected – select it.
• Now you should be able to start OpenSeizureDetector, accept the ‘Send SMS permissions’ and test the SMS function from the menu.

I will look at how I can get this into Play Store, but it is a ‘Dangerous’ permission as far as Google is concerned, so it is likely to be difficult!

Graham.

I have published V3.1.7 of the Android App to the Google Play Store. Main changes from V3.0.x are:-

• Added Timer to give user opportunity to cancel SMS alarm before it is sent.
• Made the Cancel Audible button inhibit SMS alarms as well as audible beeps.
• Added Mute function from Gramin watch Menu button.
• Added heart rate to data log.
• Added fall detection algorithm to Garmin/Fitbit data source.

Please report any issues you have with this new version

Graham (graham@openseizuredetector.org.uk)

I am going to be doing some comparisons of various seizure detection algorithms, so needed some statistics to use to compare. While the detection reliability for real (or maybe simulated) seizures is an obvious one, I thought the other one should be False Alarm Rate (ie number of false alarms per day).

I just pulled off the last month’s of log files from Benjamins Pebble Watch based seizure detector and analysed them. It gave the following graph:

At the start of the month I thought we were getting more false alarms than usual and eventually I realised that after I changed phones I had not re-set the Alarm Ratio Threshold setting from the default 50 (more sensitive) to 54 (less sensitive) that we were using before – I changed it to 54 on 16 May.

The False Alarm rate was 1.4 alarms per day up to 16 May, and 0.9 alarms per day afterwards. We get a lot more warnings – of he order 7 warnings per day after the change.

I’d be interested to know how this compares to other users’ experience – please let me know at graham@openseizuredetector.org.uk or on our facebook page.

I have been a bit quiet for a while because I have been looking into how to develop an improved seizure detection algorithm – in particular looking at improving the false alarm rate for seizure and fall detection. I have started a separate page on this site that I will keep updated as it progresses – please get in touch if you would like to help!

See: http://www.openseizuredetector.org.uk/?page_id=1241 for details

Graham (graham@openseizuredetector.org.uk)