79,225
edits
Talk:Bluetooth Passthrough: Difference between revisions
Jump to navigation
Jump to search
→Compatibility list
No edit summary |
|||
| Line 14: | Line 14: | ||
: It's the hardware revision reported by the adapter. It's needed as an additional identifier (since the VID/PID can be the same pretty often). --[[User:Léo|Léo (leoetlino)]] ([[User talk:Léo|talk]]) 21:02, 11 October 2016 (CEST) | : It's the hardware revision reported by the adapter. It's needed as an additional identifier (since the VID/PID can be the same pretty often). --[[User:Léo|Léo (leoetlino)]] ([[User talk:Léo|talk]]) 21:02, 11 October 2016 (CEST) | ||
:: Um, why is it needed though? Just so we can have excess rows in this table? If they are hardware identical shouldn't they have identical other details (outside of perhaps range, due to different packaging). Though, now that I look at this in more detail, this seems like a big problem. For instance we have 7 rows of "0A12/0001" all with wildly different results indicated; worse even when all three IDs match (0A5C/21E8/0112, 0A12/0001/8891) there still seem to be differences reported. Do these id's provide no clarity about things, or should it be presumed to just be inconsistent reporting? [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 04:49, 23 January 2017 (CET) | |||
Also, what exactly is a perfect range? 15m? 20m? Maybe we should document that after the table, same for HCI Reset which I used in one of the entries - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) 20:48, 11 October 2016 (CEST) | Also, what exactly is a perfect range? 15m? 20m? Maybe we should document that after the table, same for HCI Reset which I used in one of the entries - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) 20:48, 11 October 2016 (CEST) | ||