Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Component used: androidx.bluetooth
Version used: 1.0.0-alpha02
Devices/Android versions reproduced on: all
As a feature request, knowing the negotiated MTU of a
sessionin the GattServer code would be very helpful for me. My application hosts a gatt server and some of the clients that connect to us use multiple read requests with a read offset always set at 0. This requires chunking of the packets, however there is currently no way to know how much data has been read by the other device. Currently, I am able to send a large payload as a response toGattServerRequest.ReadCharacteristichowever, if the other side requests a zero offset, the library never finishes because the read never "completes". My goal is to either a) know the MTU such that I can properly chunk the data outside of sendResponse, or b) get some sort of return value from send response that tells me how much data was actually sent.Given that the stack forces an MTU exchange anyway, it would be great if that data could be made available to the GattServerSessionScope or as a type of GattServerRequest along side ReadCharacteristic and WriteCharacteristic.