bluetooth: Look into normalizing the displayed signal strength using advertised TX power |
||||||||
Issue descriptionIf we get a TX power through any of the iBeacon, Eddystone, or standard AD formats, we could use it to normalize the RSSI we display in the chooser into a path loss. We'll still need to show the RSSI without normalization for devices that don't advertise a TX power. We should prioritize this by the fraction of devices that send us a TX power at all. UMA link for googlers https://goto.google.com/bluetooth-rssi-normalization-uma
,
Oct 16 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 19 2017
,
Oct 19 2017
,
Oct 19 2017
,
Oct 19 2017
,
Oct 22
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 24
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by scheib@chromium.org
, Oct 15 2016