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.

Sign up for GitHub

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

Jump to bottom

Notifications are not received if bluetooth connection is lost and then restored #2113

Closed
WizardStan opened this issue Dec 15, 2021 · 7 comments
Closed

Notifications are not received if bluetooth connection is lost and then restored #2113

WizardStan opened this issue Dec 15, 2021 · 7 comments

Comments

@WizardStan
Copy link

Summary

When the bluetooth is unnaturally interrupted and then automatically restored, the watch stops receiving notifications.

Environment

Bangle.JS 2; Up-to-date as of December 14th.
Android phone running Gadgetbridge.

Steps to reproduce

  1. Install Android app (v0.04) and Gadgetbridge Debug app (v0.01)
  2. Install Gadgetbridge on Android phone (v0.63.0).
  3. Pair watch with phone through Gadgetbridge phone app.
  4. Open GB Debug on watch.
  5. Receive a notification (eg, send yourself an email) and verify the expected JSON appears on the debug screen.
  6. Walk away from the phone, out of bluetooth range, until the bluetooth is disconnected. Verify connection has been lost in the Android app.
  7. Walk back to the phone and wait for connection to be restored. This may take a minute or two.
  8. Open GB Debug on watch.
  9. Receive a notification (eg, send yourself an email)

Expected behaviour

New notification JSON appears on the debug screen.

Actual behaviour

Debug screen continues to display "waiting for message".

Frequency

100% reproducible.

Additional notes

This has to be done when the bluetooth is unnaturally disconnected and automatically reconnected. Manually turning the bluetooth off and on again does not produce this issue, and in fact doing so will serve as a workaround, restoring expected notification behaviour.
This may be related to #2112
@johan-m-o
Copy link

Can confirm.

Bangle.js 2 2v10.247.
Gadgetbridge 0.63.0 on an Android 11 custom ROM (OnePlus 5T).
Android integration 0.05.
Messages 0.12.

It's not necessary to turn Bluetooth off and on to get it working again though. It's enough to disconnect and connect in the Gadgetbridge app.

@gfwilliams
Copy link
Member

More info on this forum post: http://forum.espruino.com/conversations/370937/

@WizardStan WizardStan mentioned this issue Dec 15, 2021
Closed
@WizardStan
Copy link
Author

I was just noticing that this hadn't happened to me in about a week now and thinking maybe the upgrade to gadgetbridge 0.63.1 had fixed it. I have walked away from my phone on multiple occasions to have it disconnect and then returned to once again start receiving messages. Even left it at home while I was out shopping yesterday and within a minute of returning home I got an email which displayed on my watch. Seems I was no longer able to reproduce the problem at all. So problem solved, I thought.

Today I upgraded to 2v11 (and upgraded all apps at the same time) and I'm back to being able to reproduce the problem 100%. I have to turn bluetooth off and on again (or disconnect/reconnect through gadgetbridge) in order to get messages to start flowing again. And now that steps are being properly tracked in both the watch widget and gadgetbridge phone app, I can confidently say that the communication failure is bidirectional: no steps are counted on the phone while in this connected-but-non-communicating state.

So this is to say, I upgraded to 2v11 and the problem persists, but it may not actually be as 100% reproducible as I'd originally thought.

@gfwilliams
Copy link
Member

Just a thought - but when you connected to Gadgetbridge did you choose to 'Pair' or 'Not Pair'. It's possible that the pairing info got lost upon update to 2v11 and that kicked off these issues...

@WizardStan
Copy link
Author

I do not remember, but it's back to working as expected and not able to reproduce the issue.

@WizardStan
Copy link
Author

I have not experienced this in months, at least not since upgrading to 2v12. I'm going to close this under the assumption that something tangentially related was fixed that resulted in this getting fixed as well.

@gfwilliams
Copy link
Member

Great - thanks for updating the issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gfwilliams @WizardStan @johan-m-o