Notifications laggy on chromebook

[nal...@workbenchplatform.com]

I have a device that sends notifications very frequently.  On my Mac I get the notification associated with the action in my javascript immediately, but on chrome os the associated notification is delayed.  It seems like the longer I leave the device connected, the longer the delay.

For example, the controller is constantly sending notifications and I am logging them. On my Mac, if I press the "A" button, I immediately see the data being logged that indicate that the "A" button was pressed.  On the Chromebook, when I press the "A" button there is about a 1 second delay from when I press the "A" button to when I see the data being logged.  This delay seems to grow as the connection stays open.

I'm not sure if there is anything I can do to get around this on the chromebook?

[Giovanni Ortuño]

Would you mind opening a bug about it? Some logs would also be good. I'll bring it up with Chrome OS folks.

--
You received this message because you are subscribed to the Google Groups "web-bluetooth" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web-bluetoot...@chromium.org.
To post to this group, send email to web-bl...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/web-bluetooth/05d2ce0a-c209-4e39-9014-6589b2650ed6%40chromium.org.

[nal...@workbenchplatform.com]

I'll open one tomorrow when I can get a copy of the logs.

My code for this specific device struggled with this bug too, but I think I've mostly worked around it https://bugs.chromium.org/p/chromium/issues/detail?id=681309&q=component%3ABlink%3EBluetooth%20&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified

I'm afraid that it may have something to do with how often oncharacteristicvaluechanged is called for this device.  The device I'm using is a Parrot FlyPad, incase you happen to have one.  Other devices that I work with only cause oncharacteristicvaluechanged to be called when something actually changes, and those devices don't seem to have any issues with latency or with notifications stopping after some period of time.

[Giovanni Ortuño]

Thanks. Also, please try the latest dev build. I know the Chrome OS team has recently landed many improvements to the Bluetooth drivers.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/web-bluetooth/4f2cdc9c-7d4b-49ed-836d-fedf5b6bed97%40chromium.org.

[nal...@workbenchplatform.com]

I reported it here https://bugs.chromium.org/p/chromium/issues/detail?id=826716

Unfortunately, the logs don't look too helpful.

The lagging seemed to be slightly better in the dev build.  But over time the lag went from nonexistent to very noticeable.

The notifications still abruptly stop after a few minutes, so I guess that isn't worked out yet, but I'm not sure if it is related to this issue.