Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BluetoothGatt: android.os.DeadObjectException #56

Open
PeterKucera opened this issue Oct 5, 2020 · 0 comments
Open

BluetoothGatt: android.os.DeadObjectException #56

PeterKucera opened this issue Oct 5, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@PeterKucera
Copy link

Expected
For creating a connection, I am using method connect() with autoConnect flag set to true. This is setup once and it is expected that after setting up this "autoConnect", there is no other action required and Android OS BLE stack will notify the app, once remote device becomes available, and this call will never time out.

Actual
Sometimes, I can reproduce following behavior:
App is capable of connecting to device, but when app attempts to write bytes, it results in following exception: "BluetoothGatt: android.os.DeadObjectException"

To Reproduce
Steps to reproduce the behavior:

  1. call connect method with autoConnect flag set to true
  2. Wait a few hours
  3. After reconnection, writing to device will always result in "BluetoothGatt: android.os.DeadObjectException"

Note: Even restarting the BT module will not solve the issue. What will solve the issue is reinitialising BlueFalcon library.

Smartphone (please complete the following information):

  • Device: [Samsung Galaxy A5]
  • OS: [Android 7]
  • BlueFalcon version: [0.7.2]
@Reedyuk Reedyuk added the bug Something isn't working label Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants