Thank you so much
Thank you so much
I think scanning is not the problem for us, only the longer message after MTU changed is failed to be sent and the connection is cut off.
Anyone who is interested in tracking this problem, you can also look at https://developer.samsung.com/dashboard/support/19306,
I will keep update on the link above, but you need to sign in then you can view.
FYI. The link you posted goes to the dashboard, which is unique for each user. That ticket can be seen by you and the Samsung employees with access to Zendesk, but other developers cannot see it.
Here the reply from Samsung developers:
According to the log analysis, there have been many attempts by the application ‘eu.lukeroberts.lukeroberts’ to configure MTU size to 184 or 23. Link loss occurred after MTU has been changed in case of MTU size 184 only.
Our development team suspects that the remote device have encountered problem when MTU size has been changed to 184.
According to the Bluetooth specification, the link loss occurs because the packet is not received from the data channel for a specific time between the BT chipsets of both terminals. Therefore, it should be checked from your side why BT chipset did not send ACK packet to the data channel.
Please capture air log if possible. If you don’t have any air sniffer then you should check the source codes of the remote device to process MTU negotiation event pkt.
Samsung Developer Program
Currently we are still working on finding correct sniffer for us to get more bluetooth communication log, and then we can carry on.
Do you know when I turn on
“Enable Bluetooth HCI snoop log” in the Developer options screen,
Where can I find the btsnoop_hci.log* ?
Is there anything useful in this log file to analyze this problem?
Thanks for suggestion. Unfortunately, passing
connectGatt does not solve issue. It’s true I also tried
I’m also experiencing the same problem with Galaxy S10+ (SM-G9750, Android 10, OneUI 2.0) other Galaxy S10 devices, while connecting to ESP32 chip. Requesting MTU causes 100% disconnect (Reason 0x8 - Timeout), while sending large data blocks over BLE. Only workaround we have found for now - is not to request MTU at all, but it makes data uploading too slow.
Your experience is a little different with us, the request of changing MTU to larger can be successful, only when you send the data is bigger, the connection will be cut off.
Anyway, our. temp workaround is also not requesting large MTU, we are working to provide more logs to Samsung to make it fixed.
Same problem here.
Several galaxy 7 and 8 phones tested and no issues.
Galaxy S10 fails with disconnect after sending large amounts of data.
Same problems with Redmi 6A Phone.
A fix would be nice!
It seems looking at a ble sniffer and the logs in this thread that the first large data packet is sent and ACK OK and then this packet is repeated many many times in quick succession until the ble stack panics and drops the connection… but I am not an expert in this, just what I have seen.
We have the same problem for Android 10 Samsung phones. There is no problem with Android 9 Samsung phones or other Android 10 devices like Pixel. We lowered the message size but data transfer is really slow right now.
Any updates here?
We can confirm the exact same issue. Setting MTU > 23 followed by a write event causes a disconnect due to the timeout because the phone hardware never sends anything…
A few other findings we can read with MTU>23 and like everyone else this only happens on Android 10 Samsung devices.
@dan1580253621 any response yet? We can confirm the reason the phone is not getting an ack is it’s not sending anything. I think we’ve collectively tested this on enough devices to be 100% sure this is a Samsung issue. We get the ack from pixel device and from s10 running non Android 10.
Happy to help however we can but if supports idea of help is … the phone sent the payload and your hardware didn’t respond… then this is a waste… are they hearing us when we say it works on EVERYTHING ELSE but your device.
Thank you for your update, and actually I open another ticket on the https://developer.samsung.com/dashboard
And Samsung developers have replied to me, they can reproduce this problem, and they can make sure that Samsung phones didn’t receive any ACK from the remote device, but they didn’t know the ACK is not sent by the remote device or the Samsung phones lost the ACK for some reason, they need me to grab the air log for them, then they can look into this problem.
You can read the reply I copied above, so the current problem is that I can’t get the air log because the WFH made me not able to work with my remote device team.
So if you can provide bluetooth dumpstate/btsnoop log and the air log which is the log from your remote device, I will chase them with your log and let them to take a look.
Dan the remote device is not sending an Ack because it doesn’t receive anything at all from the Samsung phones. Once you change the MTU>23 and attempt to write it fails because the Samsung is not actually sending the data.
I’m going to try to reproduce this issue between 2 Samsung devices today just to prove the points.
If Samasung can reproduce this then why do we need to do anything at all? Can they not diagnose there own issues? I’m happy to help,but pretending this is our remote devices fault is a joke. There’s atleast 5 of us in here with same problem and I bet there’s 5 more that haven’t traced it down yet.
Unfortunately in my case we have live field devices and customers being impacted with no work around.
The temp workaround is not making MTU > 23, then the writing can work well.
There is some mistake about my expression, they just analyse my log, but not try to reproduce the problem.
If you think, you have enough log, you can submit another ticket on
I think more tickets will make them to take more care about this problem.
Understood - I’m working to create logs and will submit them tomorrow. That workaround is only valid if you don’t depend on a higher MTU…which we absolutely do.
New learning today: Any MTU setting between 24 & 512 results in only allowing for a payload of 20 characters. You can set the MTU to 24 and send 20 characters all day. you can set the MTU to 512 and send 20 characters all day…but if you try 21 characters in either example the phone will “NOT” send the payload, but it think it does send it…then the timeout happens and the connection is closed.
I honestly don’t think the logs will show this glaring issue, but I will capture the logs tomorrow and upload it.
How quickly do they look and respond to the tickets @dan1580253621 ?
Generally support will reply within 24 hours but on this issue it has to go to another tier of support and total turn around time could be different.
If you can send me the ticket number in a private message, I’ll ask that this be given some priority as it is a hot topic on this discussion board.
Samsung Developer Program
Agreed about being able to set the MTU and then still send the usual smaller payload and the phone disconnecting when you try and send more characters, same behavior here.
Cool, thank you for your time and effort.
If there is any update, please let me know, we are still eager to resolve this problem.
I also sent my data and it is still under investigation. They know that an issue exists and many developers already sent them trace.
Lets see if we got a patch soon