Bangle.js: Notification can interrupt data uploads via App Loader/Web IDE Remote #3600
Labels
No labels
device mi band 7
activity post processing
activity/health
Android 12
Android 13
android integrations
architecture
Bangle.js
bug
changes requested
charts
deprecation notice
details not provided
developer documentation
device amazfit band 5
device amazfit bip
device amazfit cor
device Casio
device fossil
device garmin
device gtr 2e
device gts 2 mini
device h30
device hplus
device huami
device Huawei
device liveview
device mi band
device mi band 2
device mi band 3
device mi band 4
device mi band 5
device mi band 6
device no.1 f1
device pace
device pebble
device pebble 2
device pinetime infinitime
device request
device sony
device support
device watch 9
device xiaomi
discussion
documentation
duplicate
enhancement
feature request
Gadgetbridge
good first issue
help wanted
i am developing my own app can you help
icebox
intent api
internationalisation
invalid
needs work
network companion app
new device
no feedback
not a bug
notifications
one of the 1000 issues about disconnection
pairing/connecting
potentially fixed / confirm and close
question
research
security
seems abandoned
Solved, waiting for F-Droid release
suggest to close
task
user interface / UX
wear os
weather
wontfix
Zepp OS
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Freeyourgadget/Gadgetbridge#3600
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Leaving this to keep track of the issue found here: #3153 (comment).
Please confirm that;
Where did you get Gadgetbridge from?
I built it myself from source code
What is your Gadgetbridge version?
0.79.1-banglejs-6f717344e (includes #3478 and #3153)
What happened?
Reference:
#3153 (comment)
#3153 (comment)
Do you have logs?
Yes, shared above in there referenced PR, and privately to @gfwilliams.
What gadget do you use?
Bangle.js 2
What is your Android version/manufacturer flavor?
Android 14
If we set the device as busy while the webview is active, it should prevent external events from sending data.
However, one note: it has happened to me in the past on other devices that events triggered by the watch itself can cause this kind of issues, especially if that triggers a reply back from the phone (I don't think there's a lot of these events on the bangle, if at all).
We discussed previously if the webview could be persisted in the background: #3286 (IIRC it might already be able to to a degree. Edit: see https://forum.espruino.com/conversations/386264/#comment16988419)
If that came to be I guess the device could end up perpetually busy? 😛
Just a thought for now. It might be better to not focus on that other issue to start with..
I think even if the webview was open in the background, just setting the device as busy while the activity was actually active would be good enough?