On Wed, May 7, 2014 at 12:06 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: >>> RSSI property is inquiry RSSI and this should be stated here especially >>> that we plan to add connection RSSI property soon. >> >> Does connection RSSI really need to be a separate property? Why can't >> the same property be used for both? It's the same device after all. > > the problem is that they are different. They get measured differently. One is essentially tight to the Inquiry TX power and the other to the TX power of the connection. Results will be different. This has always been the problem with Bluetooth’s RSSI. Mapping the RSSI you got Extended Inquiry Result to Read RSSI is not possible. > LE Devices aren't ever in a situation where they are Advertising during a Connection though, right? So either the RSSI + TX Power are relevant to Inquiry (when Connected = false) or relevant to Connection (when Connected = true) Since the Connection RSSI on a Classic device is always just deviation from the golden range, the RSSI field isn't even that interesting in those cases. Scott -- Scott James Remnant | Chrome OS Systems | keybuk@xxxxxxxxxx | Google -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
