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.

Undiscover will disconnect, but will not explicitly unbond.

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

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

@benp thanks a lot, will check it out!

@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..

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

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

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.

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

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

@CTirendi has this been published on the maven servers yet?

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

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

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.