seems like the April patch doesn’t fix this bluetooth issue.
Hi All
we are battling with the Android 10 BLE issue sind Jan 2020 and now we found the same issue at a brand new Samsung Galaxy S20 ! So there seems to be a bigger bug inside all 10+ devices ! All Note8 work 100% !
Greets Arno Schindler
Please open a tech support request and they need a dumpstate/btsnoop log to send them https://developer.samsung.com/dashboard .
Would you please share the log with us so that we can escalate to them?
N.B: Please find the guide to get dumpstate log shared by development team as below.
[GUIDE]
How to get dumpstate/btsnoop log
- Settings > About device > click ‘Build number’ several times
- Settings > Developer options > check the box for ‘Bluetooth HCI snoop log’
- And then reproduce the issue
- Right after reproduced > *#9900# on dialpad > run dumpstate/logcat > copy to sdcard
- Please transfer the all files in Log directory
Thank you for your cooperation,
Ron
Samsung Developer Program
Hi
Logs for S20 BLE fail send to the Support , hopefully it takes not again 4 Months until its fixed !
regards Arno Schindler
I sent them logs for A40 5 days ago and they asked for logs from Android 9 to compare with. So I replied that I don’t have access to a device that hasn’t been upgraded. No answer from them since then.
Hi Samsung developmen …
is there ANY!!! progress in fixing the BLE bug in your OS for S10 and S20 +++ ?
5 days ago we transfered the log files and nothing happend until today
all Samsung Note 8 Phones are working perfect , all IOS Phones and Tablets from Apple are working also fine !
Greets Arno Schindler
Hi Samsung development …
Next week is gone without any reply on Emails or messages or here in the Forum …
it would be very nice to see any reaction that we know how we can deal with your bug .
regards Arno Schindler
Hi samsung development,
This bug is really critical from some applications/mobile controlled devices out there. What can we expect in terms of time to fix? What can we do? Your phones are a huge part of the market and we are waiting for your update since january…
Thanks for your reply
Côme de Cerval
Dear Samsung devs, can you please provide information from your side on what are you current bottlenecks? It does not seem to be a BT module hardware issue since it was working in previous Android version and there are other makes with the current Android version where this is not an issue.
+1
Bug is still existing even with new S20 devices.
Note 8 on my desk is working without problems. New Huawei phones with Android 10 are working too.
This Thread was created in January an we have absolutely no information and now its June!
Would be nice if we could get a status update. It seems like Samsung doesn’t care about this problem.
HI everyone! Did any get any feedback from Samsung devs? We have the same issue using S10+ and using ESP32. I will ask our developers team to post our findings here
Hello Samsung development and all developers around the world
Here the statement from our development department :
Under Android 9 and 10 before Update June 2020 when you want use the BLE mode there was a warning message that the user must allow that the actual user position can be used by the app , that message is GONE AWAY in the latest update !
So now the good news … the data direction from the BLE Hardware to the Samsung Phone allows now full size MTUs of 180byte !
Bad news is that from the Phone to the BLE Hardware is still reduced data MTU of 20 byte !
So your bugfix was 50% successfully , now please do the rest !
Please tell them that they JUST only have to fix the problem with the data direction from the Samsung Phone to the BLE devices !
Greets Arno Schindler
English doesn’t matters bro, you may convert the language using any translator and understand the concept, I also doing the same.
Feeling happy for seeing like minded people in this community, Cheers!
Hi All
Nearly 6 months and no real fix for the BLE Problem … is there anybody able at the Samsung development department … to fix that MTU Problem ???
regards Arno Schindler
Having the exact same issue, only keeping the MTU at 23 didn’t work either, it keeps disconnecting.
With the negotiated MTU, I’m using 256 in this case, if you reconnect and immediately send the buffered message it works for that one, before going back to the non-working state.
Hi everyone,
Any update on this major issue?
Estimated date of fix, working workaround, something?
It’s been there for a while…
Regards
Côme de Cerval
Any news regarding this very important issue. This has definitely affected our product in a very very serious way. Please come up with a solution asap.
Regards
Per
Hi All , nothing improoved since March Update …
The data direction from the BLE Hardware to the Samsung Phone allows now full size MTUs of 180byte !
Bad news is that from the Phone to the BLE Hardware is still reduced data MTU of 20 byte ! And thats absolutly slow !
So dear Samsung development … your bugfix was 50% successfully , now please do the rest !
Please tell them that they JUST only have to fix the problem with the data direction from the Samsung Phone to the BLE devices !
Samsung development contacted us and they wanted from us an Bluetooth broadcast spy recording that they can analyse the problem , unfortunatly the BLE data connection breaks up directly when you try to send more then 20bytes MTU size from the Phone to the connected BLE device !!
perhaps anybody else can provide the brodcast data recording ??
also PERHAPS everybody with this PROBLEM should create Service Tickets on mass , hopefully they start mooving to fix the bugs !
Greets Arno Schindler
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.
Thanks