General Discussion

• R

  Trial Key not working in Android library package
  • rhilse

  4
  0
  Votes
  4
  Posts
  111
  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
  179
  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
  1673
  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
  673
  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
  655
  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
  2346
  Views

  R

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

  Prevent reconnect regardless of disconnect reason
  • mkurtz

  17
  0
  Votes
  17
  Posts
  2729
  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
  431
  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
  2083
  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
  726
  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
  699
  Views

  

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

  Android Q Support
  • AlejandroHCruz

  5
  0
  Votes
  5
  Posts
  1041
  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
  498
  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
  998
  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
• A

  SweetBlue 3.0.3 - Proguard Issue with TemperatureUnit?
  • allen

  2
  0
  Votes
  2
  Posts
  739
  Views

  R

  What you did works, however, I would suggest using -dontwarn com.idevicesinc.**
• M

  Scans with screen turned off on Android 8.1 and above fail
  • mkurtz

  20
  0
  Votes
  20
  Posts
  3491
  Views

  R

  We're looking at around 2 weeks or so before we put out the official release.
• M

  Timeout
  • mgordon

  8
  0
  Votes
  8
  Posts
  1175
  Views

  M

  Yes, those trigger. We added those when we noticed that the times we set in taskTimeoutRequestFilter or DefaultTaskTimeoutRequestFilter weren't triggering.
• L

  Using SweetBlue in library
  • ldulcic

  2
  0
  Votes
  2
  Posts
  534
  Views

  R

  You can put it in a library if you want, you would just have to get a license for each app that it goes into. If you're looking to have many apps using SweetBlue, an Enterprise license may be more what you're looking for. If that's the case, email us at sweetblue@idevicesinc.com, and we can discuss your situation.
• S

  Pairing rejected by: ...
  • SparkyRih

  8
  0
  Votes
  8
  Posts
  1380
  Views

  S

  Well, it's mostly the connecting itself which is the issue... The scanning/finding is pretty consistent now...
• A

  BleTransaction.Auth() documentation
  • Activ84HealthEU

  2
  0
  Votes
  2
  Posts
  638
  Views

  R

  @Activ84HealthEU, I need a bit more info in order to help you. Does it actually ble connect to the device? (You may have to look at logcat). When the write fails in the transaction, what is the status()? That should at least give you a hint at what's going on. NOTE: When using any transaction, you MUST call either succeed(), or fail(). Otherwise, even if the write went through, it would just stall out and do nothing afterward (and the DeviceConnectListener onEvent will never get called, at least not for being connected).