-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Very slow service discovery #17
Comments
As I was writing the issue it populated and works now. Is that process slow to load? |
Just relaunched and it took nearly 4 minutes to expand services. |
Does toolBLEx enumerate over all the characteristics? This tracker is slow to respond to a single query (upwards of 4 seconds). Maybe that 4 seconds is stacking with hundreds of calls? nrf Connect on Android seem to load the list fine so I'm not sure. |
After some more testing this does seem to be limited to this device, likely caused by a very low clocked/powered processor causing delayed responses. Even with the cache it seems to take the same 2-4 minutes each time to enumerate through everything and start interacting with services. |
Hi,
Yes it does. By default toolBLEx is not only scanning services and characteristics (that's kind of required anyway) but it pulls data from each readable characteristic. You can try a "simple" scan with the scan button drop down menu, where you can select what you want to do (services and data or services only). It should make a difference. The cache is only used by the UI, it won't speed up subsequent connections to a device.
May I ask how many characteristics that device has?
I guess nrf connect doesn't pull data so it is faster in your case. Reading data by default seems like a good choice for a Bluetooth analyzer, but maybe there should be an option to set the preferred choice. |
Here's the list from bluetoothctl So yeah the slow response does seem to be the bottleneck with that many. I agree reading values is great for analyzer defaults. An option to skip reading would indeed be great to have. Thank you!
|
It doesn't look like that there are that many characteristics, maybe that's more about how much data must be pulled for each one of them (but that's not included in the cache at the moment). Did you try a "services only" scan to see if reading the characteristics is the problem? I've added a bit more info so users can see if the services are still "discovering" or fully "discovered". |
Services Only discovery just took about 2 minutes. Having that label looks great. |
Describe the bug
Connected to a Bluetooth tracker that supports Immediate Alert to beep. Clicking the expand on the service shows nothing.
Expected behavior
According to the example screenshots, should be drop down to read/write.
To Reproduce
Steps to reproduce the behavior:
Screenshots
Your environment
Please describe the environment you are using:
The text was updated successfully, but these errors were encountered: