-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix maximal supported MTU on Android 13 #808
Conversation
… since Android 13
Hi, |
looks like this change was already done 3 years ago... |
oops...i meant 1 year ago....so might indeed be new to Android 13 |
@dariuszseweryn what do you mean by backwards compatible? this change won't make it incompatible with previous Android versions. If you have that 2 byte difference on you mind and you'd like to keep the value Sadly Java |
I'm thinking of deprecating the static value and introduce a function instead. |
@dariuszseweryn great, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello, I revisited your PR and added some small suggestions to Javadoc and after that I will happily merge your change :)
rxandroidble/src/main/java/com/polidea/rxandroidble2/RxBleConnection.java
Outdated
Show resolved
Hide resolved
…ection.java Co-authored-by: Dariusz Seweryn <dariusz.seweryn@gmail.com>
@dariuszseweryn great, thanks! |
Released in version 1.17.0 🎉 |
Hello @dariuszseweryn,
since Android 13 the real maximal supported MTU by Android is 515.
Even though in Android source code the GATT_MAX_MTU_SIZE is still set to 517, the data buffer size GAT_MAX_ATTR_LEN is now capped at 512 bytes.
It leads to the situation when Android allows you to negotiate MTU 517, but it drops all the packets with data larger then 512 bytes
Here is the commit where google engineers did this amazing change