I broke the openseizuredetector app web interface in V3.1.13. I now have an updated version (V3.1.14) which I think fixes the issue – if you are affected by the problem please will you try this version by downloading it form the source code repository here: https://github.com/OpenSeizureDetector/Android_Pebble_SD/raw/master/app/release/app-release-3.1.14.apk
If you have any trouble, just uninstall it and re-install the version from Google Play Store.
Thanks
Graham.
Alas I must report that I broke the OpenSeizureDetector web interface as part of the changes in V3.1.13 that cured the errors on the Garmin watch screen……Fortunately, I don’t think many people use it because only one user has complained, phew!
I have a fix for it (it is trivial – the problem is that now that the server tells the client that the data is being sent as JSON rather than text, the browser is ‘helpfully’ converting the JSON string into a javascript object for us. That means that my code that turned the string into a javascript object now crashes…..).
But I let Android Studio update on my computer and now it won’t build the app unless I remove support for Android 4, so I will not rush to push out the solution until I have given users chance to respond to my earlier post asking them if they use Android 4…..
Graham.
If anyone is using OpenSeizureDetector on an Android 4.x device, please let me know as soon as possible!
The reason being that I think Google is forcing me to drop support for Android 4.x – or at least the only way I have managed to re-compile the App since updating Android Studio etc. is making the minimum android version Android 5.0.
Acording to Play Store, there are 3 people using Android 4.x. I know that I am at least one of them (I use an old tablet as a video monitor that runs OpenSeizueDetector Network DataSource to provide wifi based alarms). Because of my privacy policy of not collecting any information about users, I can’t get in touch wit the other users, so if it is you, please let me know!
Thanks
Graham (graham@openseizuredetector.org.uk)
I have just released V3.1.13 of the OpenSeizureDetector Android App – it should appear on Play store in a couple of hours. The changes from the current version are:
To fix the -400 errors you will also need V0.8 of the Garmin Watch App which can be obained here: https://github.com/OpenSeizureDetector/Garmin_SD/tree/master/WatchApp
Please update to these latest versions – it is much easier for me to help with any issues users have if we all use the same version.
Note that I recommend that you disable automatic updates of the OpenSeizureDetector Android app, because if you don’t, it tends to update in the middle of the night, and that shouts down the app, which is not something you want to happen – best to choose when you want it to update!
As usual, please let me know if you find any issues with this release.
Graham (graham@openseizuredetector.org.uk)
I think I have fixed the -400 errors problem. It needs an update to both the phone and watch apps. Please would those of you affected try it out for me, by installing the verion 3.1.12 of the phone app, and V0.8 of the watch app – links below.
As a free gift for those of you using the Forerunner 735 and are missing the battery indicator off the bottom of the screen, this version also puts the battery indicator onto the heart rate line on the display so you should be able to see both.
Phone App: https://github.com/OpenSeizureDetector/Android_Pebble_SD/raw/V3.1/app/release/app-release-3.1.12.apk
Watch App: https://github.com/OpenSeizureDetector/Garmin_SD/raw/master/WatchApp/GarminSD_v0.8.prg
Please let me know if you spot any issues with it. If you have a problem, please just reinstall the latest version from play store, and v0.7 of the watch app, which should get you back toa working state.
Thanks, Graham (graham@openseizuredetector.org.uk)
A few users have recently reported that they see “ERR -400” on the Garmin watch display rather than the seizure detector status (OK / WARNING / ALARM).
I have had a look and I think it is a mistake in my code that used to be accepted by the watch, but now it is rejecting it saying that the response from the phone is invalid. It will be a recent update to the Garmin Connect App that has done it. (For those who like the techy details, the watch is expecting the response from the phone to be JSON, but the phone is sending it with a text/html header – strictly I should fix the phone app to send the correct header, but that has the potential to break other things….)
The seizure detector function is still working – the only thing that is missing is the OK / WARNING /ALARM status string on the display.
I will include a fix for this in the next release of OpenSeizureDetector – I just need to decide whether to finish off the remote data logging capability and include that in the release, or do a special release for this.
If anyone thinks that it is not working though, please let me know!
Graham.
I’m looking for a bit of help from someone that knows about hacking web sites…..Would anyone like to try to break into my web site for me? (Reasons below).
Thanks,
Graham (graham@openseizuredetector.org.uk)
I am working on a web based database to record data from openseizuredetector watches. Two main benefits to this:
My worry with it is protecting users personal data, so I have tried to make the new system as secure as is feasible – which is why it has taken me so long to get working. Before I roll out a change to the android app to enable logging of this data (with users’ consent of course!), I’d like people to try to hack into it to check it is secure…..
