Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning and alarm delay settings not honored #160

Open
lundstrj opened this issue Mar 25, 2024 · 7 comments
Open

Warning and alarm delay settings not honored #160

lundstrj opened this issue Mar 25, 2024 · 7 comments

Comments

@lundstrj
Copy link

Running 4.2.4a (from source) paired with PineTimeSD 0.6, I noticed that the warnings and alarms were not delayed as per my settings.

Please see the attached screen recording. looks like I'll have to find an alternative way of sharing the video.

@seaside1
Copy link

Google Drive?

@lundstrj
Copy link
Author

https://drive.google.com/file/d/1Wko6EySaXmE-V3-SKdlNF_3fVw6FJ7L6/view

Please note how the accelerometer graph spikes as I start giggling the watch.
OSD then enters an alarm state (you see this briefly on the screen).
During all of this there are warning beeps and alarm beeps going off even when OSD is not displaying ALARM or Warning.

Later in the video I show the 40 seconds delay for warnings and the even longer delay for alarms, which do not appear to be honored by OSD.

@lundstrj
Copy link
Author

I've since moved from 4.2.4a to 4.2.4b and now just plain 4.2.4 as of a few minutes ago.

Wearing the PineTime and typing these messages is causing OSD to issue auditory warning beeps but still displaying OK on screen (on both the PineTime and in OSD). If I stop typing, the beeps stop after a little while.

@jones139
Copy link
Member

That is very odd, thanks for reporting it - I'll see if I can make it do that - I can see there being a 5 second lag, but it sounds like you are talking about something more significant than that.
It will have to be tomorrow though I'm afraid, sorry!

@jones139
Copy link
Member

jones139 commented Apr 8, 2024

I haven't forgotten, it just hasn't got to the top of my list yet, sorry!

@lundstrj
Copy link
Author

lundstrj commented Apr 8, 2024

I have the delay set pretty high in order to reduce false positives. I figure the upsides to me sleeping is greater than possibly responding to a seizure 30 seconds quicker.

I don't recall what I had the delay at but I think it was at least 30 (possibly 40) seconds. once I started shaking the watch, the audible response came much sooner than that.

I also 100% get what it is like to want to do more than I end up delivering. Please, no extra trouble for me (I am running the BangleJs now and fortunately it is a smooth experience). Of course, it would still be nice to reach similar stability with the PineTime.

@pmithrandir
Copy link
Collaborator

Hi,

Just to say that you have the AI alarm active... maybe that's the one giving you too many false positive(it was for me).

Delaying is one solution, but maybe just switching that one off will also reduce the false positive.

Pierre

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants