Hi Carey, > Update the default BLE connection parameters. > > Commit c49a8682fc5d298d44e8d911f4fa14690ea9485e introduced a bounds > check on connection interval update requests, but the default min/max > values were left at 24-40 (30-50ms) which caused problems for devices > that want to negotiate connection intervals outside of those bounds. > > Setting the default min/max connection interval to the full allowable > range in the bluetooth specification restores the default Linux behavior > of allowing remote devices to negotiate their desired connection > interval, while still permitting the system administrator to later > narrow the range. > > The default supervision timeout must also be modified to accommodate > the max connection interval increase. The new default value meets the > requirements of the bluetooth specification and the conditions in > the hci_check_conn_params function. > > The downside to modifying the default supervision timeout is that > it will take longer (about 10 seconds) to detect a link loss condition. > > Fixes c49a8682fc5d: (validate BLE connection interval updates) I decided to revert c49a8682fc5d and we need an overall better solution for handling connection parameters. Regards Marcel
