General Discussion

• 

  Disconnection issues while bonded on Huawei & Honor devices
  • AlejandroHCruz

  2
  0
  Votes
  2
  Posts
  43
  Views

  R

  @AlejandroHCruz , are you sure it's just Huawei and Honor devices? This sounds suspiciously like the android bond bug, where it leaves a connection open after the first bond. See https://sweetblue.io/docs/Android-BLE-Issues under connection issues (last bullet point). There is a workaround in the library, but it is very clunky, and heavy-handed. The "fix" is to bond, then unbond, then connect, and disconnect. From then on, bonding works properly. I know how crazy this sounds. If you'd like to try it, you will have to update the BondFilter like so: public class MyBondFilter extends DefaultBondFilter { @Override public ConnectionBugEvent.Please onEvent(ConnectionBugEvent e) { return ConnectionBugEvent.Please.tryFix(); } } BleManagerConfig config = new BleManagerConfig(); config.bondFilter = new MyBondFilter(); BleManager mgr = BleManager.get(activity, config); I'm curious if using this fixes your problem (it should also make it so if the app closes, the connection gets killed).
• 

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

  8
  0
  Votes
  8
  Posts
  1137
  Views

  

  Hi, I'm jumping back into this thread with more information and a couple of questions: The Nordic's nRF Connect app can detect when I connect the BLE peripheral on my own app and directly interact with it. Which is pretty cool. Also, when you open up their application and you click 'connect' on a bonded device that is already connected (using my own app), their app connects the services and is able to interact with the peripheral device. Q1: How could I achieve the behavior described by point #2? Either manually (user interaction required) or automatically? i.e. when I open up my app, it should detect bonded devices that are connected and enable them to be used right away by the user.
• 

  Explicit disconnect triggers automatic reconnect?
  • AlejandroHCruz

  15
  0
  Votes
  15
  Posts
  1554
  Views

  R

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

  Prevent reconnect regardless of disconnect reason
  • mkurtz

  17
  0
  Votes
  17
  Posts
  2000
  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
  212
  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
  1217
  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
  379
  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
  490
  Views

  

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

  Android Q Support
  • AlejandroHCruz

  5
  0
  Votes
  5
  Posts
  696
  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
  289
  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
  668
  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
  510
  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
  2571
  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
  862
  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
  398
  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
  1060
  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
  442
  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).
• S

  Radio strength?
  • SparkyRih

  5
  0
  Votes
  5
  Posts
  839
  Views

  S

  `Well, the Sweetblue library does already make a big improvement on connection time, and the amount of phones even being able to connect... I'm mostly worried about the phones that sometimes don't connect at all, but so far, I've only seen that on a Sony in my small test team... Too bad the guy doesn't want to test again to see if my latest fixes work for that issue :S
• S

  NullPointerxceptoin in library?
  • SparkyRih

  2
  0
  Votes
  2
  Posts
  466
  Views

  R

  Unfortunately those line numbers are WAY off. If you're using proguard, please add these lines to your proguard file: -keep class com.idevicesinc.sweetblue.** { *; } -keepattributes SourceFile,LineNumberTable,Signature,*Annotation*,EnclosingMethod -dontwarn com.idevicesinc.sweetblue.**
• 

  Unbond behavior on App termination
  • AlejandroHCruz

  4
  0
  Votes
  4
  Posts
  760
  Views

  R

  That shouldn't matter (where you set the config). However, if you want it to apply to all devices, I would just set the options in the BleManagerConfig when instantiating the BleManager instance. (BleManagerConfig extends BleDeviceConfig mainly for this purpose). Try doing this, and see if you get any different results.