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
Hi, I've been using your example for a simple peripheral running on a Raspberry pi 3.
After some changes I have managed to make my app work, but I have a problem that is very annoying: the clients can consume the charactersitics, but cannot disconnect. The only way to disconnect the clients from the generated peripheral is either turning off bluetooth on the phone or restarting the app on the raspberry.
At first I thought this was a problem in my client code, but after checking all the client side code and making some changes it still does not disconnect.
Is it possible that this code cannot manage disconnections?
Thank you in advance
The text was updated successfully, but these errors were encountered:
The last time y checked, it was working. The only thing that I did was updating the bluez driver in the raspberry pi. But this was some time ago. Update your Bluetooth drivers and give it a tryEl 18 dic. 2020 16:47, ArMouReR <[email protected]> escribió:
Facing the same issue with iOS app, have you found any solution ?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
Hi, I've been using your example for a simple peripheral running on a Raspberry pi 3.
After some changes I have managed to make my app work, but I have a problem that is very annoying: the clients can consume the charactersitics, but cannot disconnect. The only way to disconnect the clients from the generated peripheral is either turning off bluetooth on the phone or restarting the app on the raspberry.
At first I thought this was a problem in my client code, but after checking all the client side code and making some changes it still does not disconnect.
Is it possible that this code cannot manage disconnections?
Thank you in advance
The text was updated successfully, but these errors were encountered: