-
Notifications
You must be signed in to change notification settings - Fork 52
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
Notifycation syncronisation improvements #368
Comments
This depends on device. For example PineTime (InfiniTime) doesn't have any interface to discard notification/phone call from the phone. Current implementation sends Immediate Alert Service with Level None to device to indicate, that phone is not ringing anymore. See harbour-amazfish/daemon/src/deviceinterface.cpp Lines 193 to 207 in b73d53b
However, It causes just another notification in case of the PineTime. I am not sure about behavior of other devices. I was working on some changes of it in scope of #289, but it still needs some debugging. I can probably split it into multiple pull requests to improve code base first and add features later. |
This is the case on Bangle.js, in a latest PR I did something for call notifications, but I don't know yet how to handle this. Phone notification call stays until discarded on the watch. |
Sure, will do but I not sure when I can test, I must take the time to get back my environment working before |
I think notifications should be synchronized between the watch
and device.
For example when a call is accepted on the phone the call notification
doesn't end.
Some notification like those that don't spawn a notification banner
spawn also show on the watch even thou they don't show up in the
events view or outside the app the spawn in.
Removing a notification on one end doesn't remove it from the other end.
The text was updated successfully, but these errors were encountered: