autoConnect() takes too long to connect with device
See original GitHub issueHi, so I’m using your library and what I do is I create connections with BLE peripheral periodically.
For first implementation I used connect()
and it worked very well. Connection was made very fast. Then bug was found - if user toogled bluetooth on/off, bluetooth cache stack was cleared and then connect()
did not work anymore. I went through your documentation and found that autoConnect()
can be used and with this implementation toogling bluetooth on/off still worked, which was a blast. But then reports came in that sometimes autoConnect() takes up to 10 minutes, which is big delay for our logic.
Question is, is there something that we can do? Is there a possibility to fix bluetooth toogle on/off cache clearing for manualConnection()? Or is there a way to reduce autoConnect() delay to minimum?
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (10 by maintainers)
Top GitHub Comments
You can call autoConnect for several peripherals, but there can be only 1 outstanding connectPeripheral call. The library doesnt prevent you from doing it. It only prevents multiple connects to the same peripheral…
Any news on this issue?