Bluetooth Discovery Vs Connection
So in my quest to obtain a constantly updating RSSI value, I have been forced to resort to this inefficient method. I've tried using bluecove 2.1.1, but it's given me some library
Solution 1:
Exactly or better, you can only get the RSSI value during a device discovery scan. My MSc research thesis was about that topic. This is because an RSSI value during an active connection is not reliable (due to the nature of the RSSI value itself) and hence Google Android engineers did not expose it through the API.
Advantage of this:
- You don't need an active connection and hence no pairing is required
- Since there is no "piconet" involved, the number of devices you scan is possibly infinite
Disadvantages
- Other bluetooth devices need to be discoverable (this is an issue, especially if you want to find other Android devices which have a max discoverability interval)
- Continuous device discovery scans are a heavy process -> costs a lot of battery
The problem however with constantly executing a device discovery is that it consumes a lot of battery on the mobile device...
Post a Comment for "Bluetooth Discovery Vs Connection"