General Discussion

• 

  Bonding with autoBondFixes set to true deletes all Bluetooth devices from Sony phones
  • AlejandroHCruz

  10
  0
  Votes
  10
  Posts
  510
  Views

  

  Thank you, I'll be able to confidently test without the autoBondFixes now.
• 

  How does ConnectionLostPlease.persistIf work compared to autoconnect?
  • AlejandroHCruz

  2
  0
  Votes
  2
  Posts
  104
  Views

  R

  When a connection has been deemed to be lost, the onConnectionLost() method is called. This interface must return a ConnectionLostPlease to inform the library what to do (persist in trying to get reconnected, or stop trying). Usually, you can achieve what you want without having to implement the logic there, and instead use the DefaultDeviceReconnectFilter. If you never want it to stop trying to connect, then set the timeout value for Interval.INFINITE. I would use infinite on the long term reconnect. Something like so: config.reconnectFilter = new DefaultDeviceReconnectFilter(2, 0, Interval.secs(1), Interval.FIVE_SECS, Interval.secs(3), Interval.INFINITE);
• E

  App crashing when SweetBlue dependency is added
  • EarlyWild

  2
  0
  Votes
  2
  Posts
  177
  Views

  E

  Issue solved... make sure to add Java 8 compatibility to project. compileOptions { sourceCompatibility JavaVersion.VERSION_1_8 targetCompatibility JavaVersion.VERSION_1_8 }
• M

  Cannot get read/notify when connected to more than two devices.
  • mcgkc55

  3
  0
  Votes
  3
  Posts
  308
  Views

  M

  Thanks for getting back with me. It appears I get the same results using the Toolbox app, but did notice something interesting. My flow using Toolbox app after having connected to two devices Turn device 1 on. Wait for button to turn green and say "Disconnect". Usually takes about 5-10 seconds I'm able to get notify values Turn device off. Wait for button to turn white and say "Connect" ========= Turn device 2 on. Wait for button to turn green and say "Disconnect". Usually takes about 5-10 seconds. I'm able to get notify values Turn device off. Wait for button to turn white and say "Connect" This is pretty consistent. I can do this multiple times with the same result, but sometimes when I turn a device on, it's button will not turn green even after waiting for over a minute. But as soon as I turn on another device (two devices are now on), both devices will connect and buttons will turn green. When a third device is added, the only way I can get a device to connect and turn green, is to turn on another device too. This is pretty consistent with results I'm seeing with Sweetblue in our app. We try to connect to devices use a ReconnectFilter val deviceReconnectFilter = object : DeviceReconnectFilter { override fun onConnectFailed(connectFailEvent: DeviceReconnectFilter.ConnectFailEvent): ConnectFailPlease { return ConnectFailPlease.retry() } override fun onConnectionLost(connectionLostEvent: ConnectionLostEvent): ConnectionLostPlease { return ConnectionLostPlease.retryIn(Interval.secs(3.0) ) } } So our app is continuously trying to connect to devices it knows about. When device is turned on ConnectionEvent is triggered and we start getting data. When the device is turned off, onConnectionLost is fired and we start continuously trying to reconnect. Is there another way we should be trying to handle continuously being connected to a device?
• M

  multiple calls per second for onConnectionLost of DeviceReconnectFilter
  • mcgkc55

  2
  0
  Votes
  2
  Posts
  247
  Views

  R

  No, it's not supposed to fire that much. Looks like you found a bug, thanks for pointing it out. We'll make sure to get this fixed for the next release.
• B

  Background scan times out on S10 (maybe other Samsungs)
  • blawlor

  2
  0
  Votes
  2
  Posts
  326
  Views

  B

  It turns out that the answer was unexpectedly simple and related to Android 10: https://stackoverflow.com/questions/58428763/android-10-not-working-with-ble-bluetooth-scanning Thanks to the folks at SweetBlue for helping me out on this one.
• R

  Trial Key not working in Android library package
  • rhilse

  4
  0
  Votes
  4
  Posts
  527
  Views

  R

  Managed it to make it work. What you need is the application id, not the package name. Very confusing.
• 

  Best practices for saving battery life
  • AlejandroHCruz

  4
  0
  Votes
  4
  Posts
  576
  Views

  R

  To be honest, it's been a while since I've dug deep into the numbers for connection interval. I would think 100ms would be good, just make sure to test like crazy :).
• 

  Interacting with device that's already connected to the OS
  • AlejandroHCruz

  10
  0
  Votes
  10
  Posts
  2350
  Views

  

  @caeduk interesting, I didn't know that you can do that if you scan without filters. We can probably look into their source code and find more hints i.e. see under which conditions they trigger that notification to ask the user if they want to debug the connection
• E

  Are there any sample projects that besides the SweetBlue v2 toolbox found on github?
  • Eheartlyanderson

  3
  1
  Votes
  3
  Posts
  1005
  Views

  V

  There is nothing in sample apps. Any possibility of it in being released in future ?.
• 

  Disconnection issues while bonded on Huawei & Honor devices
  • AlejandroHCruz

  11
  0
  Votes
  11
  Posts
  1403
  Views

  

  Thank you for your replies. It is interesting that you got different results than me. On my undersanding, turning off the Bluetooth adapter definitely terminates the connection and thus the device can be used again for further scanning/connection. I've been trying out a bunch of different things. Sometimes, when the device is stuck on this state, I am able to retrieve the device from the regular getDevice(String macAddress) method. And then I can establish a connection, verify the BONDED state, read the standard Device Information Service, and even enable some BleNotify. However, I am not able to negotiate the MTU as the operation fails with a REMOTE_GATT_FAILURE due to “no resources”. I'll activate autoNegotiateMtuOnReconnect and try again tomorrow, maybe you have some magic in there or I'm doing something wrong. Other than that, I think I'll use the getDevices_bonded() function, filter for the device, and unbond it. Then connect again. That seems to work on the Toolbox V3 app and does not retrigger a bonding notification for some reason.
• 

  Explicit disconnect triggers automatic reconnect?
  • AlejandroHCruz

  15
  0
  Votes
  15
  Posts
  3470
  Views

  R

  Undiscover will disconnect, but will not explicitly unbond.
• M

  Prevent reconnect regardless of disconnect reason
  • mkurtz

  17
  0
  Votes
  17
  Posts
  3831
  Views

  R

  @caeduk Please post a new topic with specific steps to reproduce the issue you're having so we can investigate it on our end.
• 

  Native state doesn't match reported state
  • AlejandroHCruz

  3
  0
  Votes
  3
  Posts
  714
  Views

  C

  I found your post here https://forum.sweetblue.io/topic/12/explicit-disconnect-triggers-automatic-reconnect and I was actually able to make it work, but it's tricky
• B

  Increasing speed on an OTA transaction
  • benp

  18
  0
  Votes
  18
  Posts
  3074
  Views

  

  @benp thanks a lot, will check it out!
• B

  Bluetooth connections servered by the OS get the power back to SweetBlue
  • Bjoern_ilockit

  5
  0
  Votes
  5
  Posts
  1097
  Views

  B

  @alejandrohcruz said in Bluetooth connections servered by the OS get the power back to SweetBlue: Are you enabling the autoConnect parameter? Also, from what I've seen, Android OS does not reconnect to bonded devices, except for A2DP ones… However, if that is happening, maybe you could disconnect/unbond when you notice that the device is stuck or when your service gets killed? Hope Hey, the autoConnect parameter is not enabled. Yes I can do disconnect/unbond the device, the problem is that the user has to open the app, because we don't get any response in the background when the Android OS controls the connection and kills our app. Currently we have a little workaround in our device that kicks the smartphone after 2 seconds in a set up state, because we found out when Android OS tries to reconnect, it get stuck in this state. So we can handle it from our device and get the control back. Edit: Is there a chance to disconnect to a device when the Android OS has the control of the connection ? Like to use the native Android LE methods ? Because if you use the SweetBlue disconnect or shutdown methods the connection is still there..
• 

  Link the source code of v3 to Android Studio
  • AlejandroHCruz

  2
  0
  Votes
  2
  Posts
  978
  Views

  

  Hi, any updates or plans on this? It would still be very meaningful. Thanks!
• 

  Android Q Support
  • AlejandroHCruz

  5
  0
  Votes
  5
  Posts
  1446
  Views

  

  Hi, any updates on the Android Q testing? The APIs are now final on the Android SDK. Thanks!
• 

  InvalidApiKeyException on Unit Tests
  • AlejandroHCruz

  2
  0
  Votes
  2
  Posts
  768
  Views

  R

  Alejandro, If you are using a different package name for testing, then you will need a debug key linked to that package name. Email us at sweetblue@idevicesinc.com with the package name, and we'll send you a debug key.
• M

  SweetBlue & Xamarin
  • mkurtz

  6
  0
  Votes
  6
  Posts
  1442
  Views

  B

  We are using sweetblue v2 with xamarin. I needed to basically create a java wrapper interface around the bledevice methods which required callbacks/listeners. The bindings compilation had issues with the generic type java features being used with the listeners, so I just call to my java wrapper object from c# which has simple listeners and the binding generation has no issues with. I've attached our wrapper's source code for you to use, it filters the scans without needing to call back into c# too which was a huge performance improvement.sweetbluewrapper