Re: [web-bluetooth] API which provides the negotiated MTU is required (#383)

I think it's sane that the system automatically negotiates the highest MTU the Bluetooth stack can handle at the beginning of the connection.

Android is currently broken both in its API and its implementation and doesn't follow the Bluetooth spec. It says the following about Exchange MTU:

> This subprocedure shall only be initiated once during a connection.

However, every app can call `requestMtu` with its own MTU value and the stack will happily send out a new `ATT_EXCHANGE_MTU_REQ` with the app-supplied value every time `requestMtu` is called.

GitHub Notification of comment by Emill
Please view or discuss this issue at using your GitHub account

Received on Monday, 10 February 2020 10:09:30 UTC