Author: graham

Thank you to everyone who commented on whether they would like phone call alerts, similar to those provided by Embrace or SeizAlarm. Quite a few users said they would like to have phone call alerts to supplement the SMS alerts. This is technically possible to do (I have a working prototype), but what it is likely to do is open up an audio connection between the user’s phone and the carer. This is fine in an emergency, but in a false alarm situation, there are privacy issues because the user may be doing something to cause the alarm that he/she would rather the carer did not hear, so I am a bit wary of publishing it…..

I think (please correct me if I am wrong) that the main reason for wanting phone alerts is a better notification – you get repeated ringing for a call, but only a single notification sound for an SMS, which is easier to miss. And I have a solution for this which avoids the privacy worries.

• The carer runs an app which monitors incoming SMS text messages to detect a special code which says the message is from OpenSeizureDetector.
• If the code is not found in the message, it is ignored.
• If the code is present, the app starts to make a repeated beep sound indefinitely, and displays a screen with an ‘Accept Alarm’ button on it.
• The beeping stops when the carer presses the ‘Accept’ button.

I think that this solution gives the improved carer notification using SMS, without the need to open a call – they can dial the user’s number if they want to check if it is a genuine seizure or a false alarm.

The new app that the carer needs on his/her phone is called the “SMS Annunciator” (if you have a better name suggestion, please let me know!). The version for testing is available from the source code repository here.

There is also a new version of the main OpenSeizureDetector App (V3.5.0a) which includes the inclusion of the required code in the text message so that the SMS Annunciator will respond to it. The test version of the main app is here.

Screenshots

Instructions for Testing

• Upgrade the user’s phone to use the test version of the OpenSeizureDetector app.
• Check that it still works as normal – if there are any issues, just uninstall it and re-install the version from Google Play Store. (There are quite a few changes behind the scenes because I have also introduced support for a BLE (bluetooth) data source that I am testing with a BangleJS watch, so I may have broken something…).
• Enable SMS alerts and check that these are also sent as they were before (but note that there is a 6 character code on the end of the message that was not present previously).
• Have a carer install the SMS Annunciator on their phone.
• Opening the SMS Annunciator app should briefly show a fairly blank screen, with a prompt to accept permission to read SMS messages. The blank-ish screen disappears when the permissions have been accepted, then a Green OpenSeizureDetector icon should appear in the status bar.
• Initiate an SMS alert by either shaking the arm wearing the watch, or using the ‘Test SMS Alert” menu item on the user’s phone.
• When the SMS arrives on the carer’s phone, it should make a loud ‘beep-beep-beep’ noise repeatedly, and a screen should appear that has a big red ‘Accept Alarm’ button.
• Pressing the ‘Accept Alarm’ button should stop the beeping (until the second OpenSeizureDetector SMS arrives and sets it off again).
• The ‘Stop’ button on the screen allows the SMS Annunciator to be shut down so it will not alarm when SMS messages arrive.

Please report any issues to graham@openseizuredetector.org.uk or the Facebook page.

I have been discussing the way OpenSeizureDetector raises alarms when a seizure is detected with a potential new user. He is used to the SeizAlarm system that runs on apple devices and raises the alarm by initiating a phone call (as opposed to wifi or SMS text message in OpenSeizureDetector.

I can see that initiating a phone call would be useful, because you get multiple rings rather than just a little beep for a text message arriving, so I am thinking about implementing it. There are a few potential issues though:

• Privacy – the simplest way of doing it will be to just have the users phone telephone the carer. This will leave an audio connection open when the carer answers. That is fine in a genuine emergency, but if the user does not notice that the alarm has been initiated there could be privacy concerns with the carer hearing things he/she is not supposed to hear.
• The solution to the point above would be to play a pre-recorded message rather than open an audio connection, but I don’t know how to do that at the moment.
• Google – given the difficulty I had in persuading Google to keep OpenSeizureDetector on the Play Store with the ‘Dangerous’ permissions to send SMS messages, I don’t fancy adding making a phone call without user intervention part of the main app – what I would propose to do is make a separate app that would be installed manually from the source code repository, and the main app would just ask it to make the call – so the main app does not need any extra permissions.

I would welcome users thoughts – would you like phone call alerts (I have to ask because it is not something that is useful for the way we use OpenSeizureDetector, so how far up the priority list it goes depends on how many users would like the feature).

Comments to graham@openseizuredetector.org.uk or the OpenSeizureDetector facebook page please.

Thanks!

Graham.

At work today I gave a talk on OpenSeizureDetector at our department’s seminar. It covers the motivation behind the project, the various seizure detection methods that have been tried, and an overview of the challenges of going from a technical solution to a deployable system for end users.

The slides are here if anyone would like to read them: https://github.com/OpenSeizureDetector/Presentations/raw/master/01_CfAI_Seminar_Aug2020_Issue_1.pptx

Or a PDF version which is much smaller but does not contain the embedded videos: https://github.com/OpenSeizureDetector/Presentations/blob/master/01_CfAI_Seminar_Aug2020_Issue_1.pdf

Graham (graham@openseizuredetector.org.uk)

I have just published Version 3.2.1 of OpenSeizureDetector on Google Play Store.

The main change is the addition of a Spanish translation (thank you, Cesareo Mario Guajardo Murillo!). It also contains some minor improvements to the main display text layout.

It should become available for installation via Google Play in the next few hours. If you have any issues with this release, you can install the previous version by downloading the .apk installation file from the Github repository.

As usual, please let me know if you have any issues with this release.

Thanks, Graham (graham@openseizuredetector.org.uk)

I found the problem with OpenSeizureDetector failing with Garmin Connect V4.31.

If you update to V0.9 of the GarminSD.prg watch app (https://github.com/OpenSeizureDetector/Garmin_SD/raw/master/WatchApp/GarminSD.prg), then it should work with all versions of Garmin Connect, so it is safe to upgrade Garmin Connect to the latest version.

For anyone interested the problem was a malformed url, so it should never have worked in the first place – I was sending data to http:127.0.0.1 but to be a valid url it should have been http://127.0.0.1. It is just that the previous versions of Garmin Connect were more forgiving and let me get away with it. It would have been nice for it to give us a ‘Malformed URL’ error rather than ERR-0, which means ‘Unknown Error’.

Sorry for the inconvenience!

Graham (graham@openseizuredetector.org.uk)

The new version of Garmin Connect (v4.31) breaks openseizuredetector.

**** If your Garmin Connect has not upgraded, switch off automatic updates for Garmin Connect ****

If it has upgraded you will see ‘ERR 0’ on the watch display and openseizuredetector will not work.

To fix it you need to install garmin connect v4.30 from the apkmirror.com web site and install it. (You seem to need the apkmirror installer app to do that now)

Instructions to follow…..

Please let me know if you have problems (or find 4.31 works for you)

Graham@openseizuredetector.org.uk

A couple of users have been interested in generating an alarm based on rate of change of heart rate because they have observed that increased heart rate is either a sign of an impending seizure or of a seizure itself.

I have generated a beta test version of the Android App that implements this functionality (V3.3.0a). If you would like to try it, you can download it from the github source code repository. If it gives you trouble, you can uninstall it, then install the latest public version from Google Play Store.

The way this alarm system works is it calculates an average heart rate over a given period (HR Rate Window). This is specified as the number of data points, which will normally be 5 seconds, so a window length of 12 corresponds to 12×5 = 60 seconds.

It then compares each heart rate measurement to the average and takes the difference. If the difference is greater than a specified threshold (HR Rate of Change Threshold) – say 10 bpm, it considers that an alarm condition. The main app screen now displays both the current and average heart rate so you can see how far it is off alarming.

If it detects an alarm condition for a given number of data points (HR Rate Duration) it raises an alarm with beeps and SMS text messages etc. It goes straight to Alarm, no warning first in this version.

The settings for this are visible if you select ‘Advanced Mode’ in the main settings screen, and select Seizure Detector Settings. You need to enable the Heart Rate alarm as well as the HR Rate of Change Alarm to use it.

Please let me know how you find it – I have guessed the default settings based on data for one seizure provided by a user, so it is not likely to be suitable for everyone – I am sure I could set it off if I run up the stairs. Please also share any settings that you find work for you, then I can decide where to set the defaults for the proper release.

Thanks! Graham (graham@openseizuredetector.org.uk)

I have had a few users getting in touch lately with issues that should really have been covered by documentation – I am very bad at getting around to writing documents!. Tonight I have updated the following:

• Troubleshooting Instructions: https://www.openseizuredetector.org.uk/?page_id=1324#Troubleshooting
• Data Log File Format Specification: https://www.openseizuredetector.org.uk/?page_id=801#Data_Log_File

If users spot any other issues with the documentation, please let me know……or better still if anyone is bored during lockdown and would like to update it or translate it, that would be great!

Thanks, Graham (graham@openseizuredetector.org.uk)

V3.2.0 of the OpenSeizureDetector Android App has just been published on Google Play Store, so you should see update notifications shortly.

The change from the V3.1.x versions of the app are that we have introduced multiple language support. Currently we have Swedish, German and Russian translations. Thank you to the following users who have contributed translations:

• Juergen Huebers – German Translation
• Pavel Losevsky – Russian Translation
• Andreas & Marie Ekstrom – Swedish Translation

It would be great to add other languages (I had a user asking about Spanish earlier today), so if you or someone you know could help with more translations please let me know (graham@openseizuredetector.org.uk).

I do not think this release should break anything. It removes support for Android V4.x, but I think I am the only one who is still using devices running Android 4….
If it does stop working after the install though, you can get the previous version back by downloading it from the source code repository here.

Please let me know if you find any problems (graham@openseizuredetector.org.uk) – I envisage there being quite a few tweaks to the translations as people use it, so I will just do a releases of V3.2.x as issues are identified and resolved.

I hope everyone is keeping well in these difficult times?

I wondered if anyone who speaks multiple languages finds themselves bored while locked in, would you mind translating some text for OpenSeizureDetector?

I have modified the code so that the app user interface and basic settings text can appear in your local language rather than English. But to make this work we need to translate my English Text into your local language. If you would like to do this, you need to get a copy of a file called strings.xml from the source code for the upcoming Version 3.2 of OpenSeizureDetector.

You then need to edit it in your favourite text editor (or windows notepad if you do not have a favourite), and change the text values into your language.

For example you would change

<string name=”Cancel”>CANCEL?</string>

to

<string name=”Cancel”>ABBRUCH?</string>

If you do that for the whole file, and email it back to me (graham@openseizuredetector.org.uk), then your text will appear in the app user interface when you install V3.2.
Note that we have a first go at a German version here [Thank you, Juergen] (but there are some bits of English in it where I have added new strings, so still some work to do on it).

If you are starting to work on a language, probably best to comment on this post on the Facebook page so others know you are doing it, just in case two of you do the same one.

Thanks!

Graham (graham@openseizuredetector.org.uk)