My code runs on Quest 2 (Android 12.0 and OS version 56) and subscribes to the Gatt Cadence characteristic of a cadence sensor.
The Cadence notifications typically arrive once per second. However some notifications can take up to 5 seconds to arrive. In that case all 5 notifications arrive at once. This makes it impractical to control a biped character using an exercise bike on the Quest 2.
To verify that this is not a problem with my app, I've installed Nordic Semiconductors nRF Connect app on the Quest 2. It exhibits the same behavior as my app. Notifications often come in groups.
However when the nRF Connect app is installed on IOS (my IPhone 13). All cadence notifications come in separately, about one second apart.
The OVRMetrics tool shows CPU Utilization at only 25%, so the Bluetooth Stack should not have a problem keeping up with notifications that come in one second apart.
I tried submitting this as a bug report but it seems there is no way to submit technical bugs through the website. Technical bugs are referred to this forum. This is discouraging since my only other post to this forum has not received any replies in 3 months.
