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

background process notifications (downloads, uploads, updates, etc.) sync issues #202

Open
Cambi0nn opened this issue Aug 4, 2023 · 0 comments

Comments

@Cambi0nn
Copy link

Cambi0nn commented Aug 4, 2023

Android has notifications which update, especially for background processes like downloads en uploads (showing current percentage or MB's downloaded) and such. These notifications are generally undismissable on phone until they are finished.

When these notifications are synchronised to AsteroidOS using AsteroidOSSync, they have 2 issues.

Firstly, when I dismiss the notification on my watch, my watch will vibrate on the next update and re-receive the notification making it undissmissable on the watch. Perhaps it would be possible to not process the same notification within a short time span? Assuming a notification has some kind of id or other identifier, perhaps notifications with that identifier could be blocked for x amount of time?

Another bug is that while the screen shown when the watches wakes upon a notification does properly update with the notification's value. However, the screen you get when swiping left where you can look at old notifications and dismiss them is always stuck on the value it was when the notification was first received, without ever updating with the values. It would be nice if that one also showed the latest status instead of the first received.

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

1 participant