graham – Page 3 – OpenSeizureDetector

Data Sharing – Grouping Events for Easier Editing

Those of you who use our Data Sharing system to contribute data to the Open Seizure Database will know that it can be a bit tedious to update every event (alarm or warning) to say if it was a real seizure or a false alarm.

To overcome this I have been intending for some time to group events so all events within a given period (3 minutes) are assumed to be the same event, and allow you to edit them together with the same information. This is actually quite a lot more difficult than it sounds, so I have been putting it off for some time :).

I now have an early test version and I would appreciate it if a few people would try it – it is not on Play Store yet, because I want to have it tested a bit more before I publish it.

If you would like to try it you can download V4.3.0a of the Android App from our source code repository at: https://github.com/OpenSeizureDetector/Android_Pebble_SD/blob/beta/releases/app-release-4.3.0a.apk

The main difference is that the Data Sharing screen (see image right) now has an option to Group Remote Events, which is activated by default, so you should see less events to edit, but in the background all of the events in the group will be given the same event type, sub-type and description.

Please treat it with some caution and check that it has done what you intended by de-selecting the ‘Group Remote Events’ and refreshing the data afterwards to make sure the changes are what you wanted.

Please report any issues on our bug tracker: https://github.com/OpenSeizureDetector/Android_Pebble_SD/issues

Thanks!

Graham (graham@openseizuredetector.org.uk)

PineTime Watch Performance

We have been using the low cost (~£35) PineTime watch for our ‘Production’ seizure detector for our son for over 1 year now. The report below summarises our experiences and our real-world observed seizure detection reliability.

See: http://www.openseizuredetector.org.uk/wp-content/uploads/2025/07/Seizure_Analysis.pdf for details

The summary for those who don’t want to read the whole thing is:

The PineTime watch has proven to be reliable (after initial teething troubles with connection reliability with one particular phone/watch combination).
The real-world seizure detection reliability based on movement detection is good with 85% detection reliability for tonic-clonic seizures, which is comparable to that observed for Garmin devices.
The heart rate alarm function has not been tested, but it is expected that the PineTime performance will not be as good as for Garmin devices.
False alarm rate remains high (of the order 2 false alarms per day), but this is comparable to that observed with Garmin watches.

Based on this, I would recommend that new users try PineTime first, as it is much cheaper than a Garmin watch, and only move to Garmin if they need heart rate alarms. If you are interested in trying it, please see the installation instructions here: https://openseizuredetector.github.io/pages-user/pine-time-installation.html

Graham (graham@openseizuredetector.org.uk)

UPDATE: Problem with Vivoactive 5 (and Vivoactive 6)

Three users have reported being unable to install OpenSeizureDetector on a Vivoactive 5 or Vivoactive 6 watch (and one that it works ok on a Vivoactive 5).

The symptom is that after you copy the GarminSD.prg file into the /GARMIN/APPS folder on the watch, and disconnect the watch from the computer, the watch says ‘Verifying Apps’, but the GarminSD app does not appear in the list of possible apps/activities on the watch. When you plug the watch back into the computer, the GarminSD.prg file has been deleted.

I have discovered that compiling the app using the latest Garmin toolkit gets it working on the newer watches….but then the same problem appears on my older Forerunner 245 watch.

So as a work around I have put two versions of the app in the releases folder for people to use: There is a v2.0.7 which works on older watches and a v2.0.7x which works on the newer ones.

Please let me know if you see this problem using these versions of the watch app.

Graham (graham@openseizuredetector.org.uk)

Problem with Data Sharing system Fixed

There seems to have been a problem with the Android App failing to upload data to the Data Sharing database since about the start of April.

It was caused by the change from Greenwich Mean Time (GMT) to British Summer Time (BST) (daylight savings time). It caused the Android App to display a brief ‘Failed to Create Event’ message, and then just stop uploading data to the data sharing system.

I have fixed this on the server today and it seems to be working again. Please shut down and restart the OpenSeizureDetector Android App to make sure that it re-sets correctly.

Sorry for the mess-up!

Graham (graham@openseizuredetector.org.uk)

Beta Test Version 4.2.12

I have just submitted a beta test version of the Android App (V4.2.12) for Google’s review so it can be released on Play Store. The purpose of this is to point new users to the installation instructions on the web site as there have been some critical reviews on Play Store lately because people had assumed it would work with certain watches, so they had not read the web site first.

The only changes in this version relate to the ‘install watch app button’ (this is hidden unless you have the Pebble data source selected, as it crashes for some of the other data sources) and I have added a ‘Help’ and a ‘Troubleshooting’ button to the start-up screen so users have somewhere to go if the app hangs during start-up. I have also added similar menu items to the main screen menu.

So there should be no noticeable difference for existing users – the beta test is just to make sure that I have not broken anything by mistake so I expect it to be very short before I make this the main version.

If there are any issues, please let me know
Thanks, Graham
(graham@openseizuredetector.org.uk)

Important Information for Pebble Watch Users

Apologies to the (2?) Pebble Watch users, but V4.2.11 which is the version on Google Play Store crashes because of a security error when using the Pebble data source. The problem is additional security checks on Android 14, and we are forced to target Android 14 to be able to list the app on Play Store.

The issue appears to be in the Pebble library, not OpenSeizureDetector so this is unlikely to be fixed unless someone updates the Pebble library.

Version 4.2.10 is unaffected by this problem (because it targets Android 13), so if you are using a Pebble watch, please install V4.2.10 from our source code repository:

I would recommend that anyone still using a Pebble watch transitions to the low cost PineTime watch, which will be able to use the Machine Learning algorithm which I hope to introduce in the near future.

Graham (graham@openseizuredetector.org.uk)

Release of Version 4.2.11 of OpenSeizureDetector

Version 4.2.11 of the OpenSeizureDetector Android App should soon be available for all users to upgrade on the Google Play Store.

This release fixes a few issues reported by users over the last few months. The main changes are:

Adds support for the low cost PineTime watch for all users.
Addition of a ‘Flap’ detector which will alarm on low frequency, high amplitude movements which our Son has been doing during his partial seizures lately – that has improved our overall seizure detection reliability to well over 80%, including the partial seizures, which is very good. Note though that it will increase false alarms, so is probably only suitable for night time use.
Fixed an issue where the Data Sharing system was using a lot of data.
Added a user-selectable delay before sending an SMS alert, so the user has more chance of catching false alarms before the alert is sent.
Added a ‘Send False Alarm Notification’ menu item so the user can easily notify carers that a notification was a false alarm.

Please let me know if you have any issues with the new version.

Thanks
Graham (graham@openseizuredetector.org.uk)

V4.2.11d Available for Beta testers on Play Store

Thank you to everyone who has been testing the Beta test version of OpenSeizureDetector – I have not had any significant issues reported and we have been using it for quite a few months now.

The main addition is a ‘Flap’ detector which will alarm on low frequency, high amplitude movements which our Son has been doing during his partial seizures lately – that has improved our overall seizure detection reliability to well over 80%, including the partial seizures, which is very good.

We have also fixed an issue where the Data Sharing system was using a lot of data, so I have just done an update to the beta test version of V4.2.11 to check we do not have a lot of issues, before I make this the default version for everyone.

Please let me know if you have any issues with the new version.

Thanks
Graham (graham@openseizuredetector.org.uk)

Alarm Volume on Samsung Phones

We use a (relatively) old Samsung A20e (Android 11) phone for OpenSeizureDetector. We have it permanently installed on a stand and charger in Benjamin’s bedroom and only use it for the seizure detector.

I have been a bit concerned for a while that the alarm volume on the phone is quite low – this is not a big deal for us because we use the Network Datasource option to alert us to alarms using different devices around the house….but it didn’t seem right – all the volume controls on the phone were set to maximum, and within the code, we ask for the alarm sound to be 100% volume…but still the OpenSeizureDetector alarms were quieter than email notifications etc….

I hunted through the phone settings to find the volume control for the alarm stream, but could not find it (on my Motorola phone it is one of the sliders that you can control like the ring tone and media volume controls..but not on the Samsung).

Eventually after looking through quite a few forum posts and searching the internet, I found that the trick to setting the alarm volume is in the Clock application settings – obvious :). To change the alarm stream volume I had to do the following:

Open the clock app (I had it open on the timer tab)
Press the three dots to open the menu to get to the clock app settings.
Click on the ‘Sound’ entry
This opens a dialog box where you can select the sound for the timer, but also the volume.
That volume control seems to alter the volume for all alarm stream sounds, including OpenSeizureDetector…. so set it to maximum.
We now have a very loud local alarm from Benjamin’s phone.

I think this is probably only a Samsung issue, but thought I’d post it in case I forget, or someone else is struggling with low volume. Some screenshots are included below for reference.

Graham (graham@openseizuredetector.org.uk)

Clock Timer Sound Settings Page – Note Volume control at the bottom!

V4.2.11 Available for Beta Testers

V4.2.11 of the Open seizure detector app is now available on Play Store for Beta Testers The changes are:

Target Android 14 (Play Store Requirement) – there should be no change from a user perspective
Add a setting to select the delay between an alarm being generated and an SMS alert being sent (user requested feature)
Add a ‘flap’ detector to the main OSD detection algorithm to detect low frequency arm movement (user requested feature)

Would Beta testers please check the rest of the app is working as before, then I’ll make this the default version on Play Store (will rename it v4.3 for publication).

Thanks

Graham (graham@openseizuredetector.org.uk)