You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am encountering strange behaviors when using this plugin on Android across different devices. On most phones it works perfectly, and on some other phones I get failures right after (or during) connection (Samsung Galaxy s10e).
@keerl good catch! i think this has been like this since the beginning of time. Did not even know it existed!
Fixed in 3.0.28
EDIT: @keerl i still kept the default as TRANSPORT_LE. Seems like the best choice JuulLabs/kable#61
I am encountering strange behaviors when using this plugin on Android across different devices. On most phones it works perfectly, and on some other phones I get failures right after (or during) connection (Samsung Galaxy s10e).
I have been able to track this down to the
connectGatt()
function and the problem has to do with selecting thetransport
param. Currently this option is hard coded toTRANSPORT_LE
(https://github.com/nativescript-community/ble/blob/master/src/bluetooth.android.ts#L1721) where the other options areTRANSPORT_AUTO
andTRANSPORT_BREDR
(https://developer.android.com/reference/android/bluetooth/BluetoothDevice#connectGatt(android.content.Context,%20boolean,%20android.bluetooth.BluetoothGattCallback,%20int)).I experimented with my Galaxy s10e and found that things only work when I set the transport to
TRANSPORT_BREDR
orTRANSPORT_AUTO
.Is there a reason that this is hard-coded for
TRANSPORT_LE
and notTRANSPORT_AUTO
?The text was updated successfully, but these errors were encountered: