Hi Michael
I assume that this questions is for Bluetooth HID over Classic.
I haven't seen such behaviour and there's nothing in the Bluetooth spec that would explain this.
On "power saving measures", the main one is sniff mode. By default, sniff mode is turned off in the stack/the examples.
Some examples turn it on, e.g. the HID device ones. You can try to not turn it on there:
- remove the flag LM_LINK_POLICY_ENABLE_SNIFF_MODE from gap_set_default_link_policy_settings
There are also the hid_ssr_host_max_latency and hid_ssr_host_min_timeout fields that end up in the SDP record
Please see Appendix J: Sniff Subrating Example in the HID Spec v1.1
https://www.bluetooth.com/specifications/specs/human-interface-device-profile-1-1-1/
It might be that these values, which are handled by the HID Host, can be used to optimize sniff mode (e.g. keep it on, but get a good latency as well)
Please check what other devices use for these and compare to the ones you're using currently.
Best
Matthias
> --
> You received this message because you are subscribed to the Google Groups "btstack-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
btstack-dev...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/btstack-dev/f693fdec-50c2-4e55-90ea-818645c757d1n%40googlegroups.com.