Report saved Bluetooth PIN settings to Companion apps
This commit is contained in:
1 parent
85fd38290b
commit
2a6d59474d
7 files changed
+248
-4
No files matched your search
@@ -1038,6 +1038,12 @@ Byte values are authoritative; names are aliases. When reading firmware source,
|
||||
| `0x1C` | `RESP_CODE_DEFAULT_FLOOD_SCOPE` | Default flood-scope data. |
|
||||
| `0x1D` | `RESP_CODE_CLI_REPLY` | Text returned by `CMD_RUN_CLI_COMMAND`. |
|
||||
|
||||
In `RESP_CODE_DEVICE_INFO`, bytes 4–7 are the saved Bluetooth PIN setting
|
||||
as a little-endian `uint32`: `0` selects the default/random policy; a nonzero
|
||||
value is the saved custom PIN. After `CMD_SET_DEVICE_PIN` succeeds, querying
|
||||
device info returns that saved choice immediately. The active pairing PIN
|
||||
and the device's pairing screen change after reboot.
|
||||
|
||||
### Asynchronous push types
|
||||
|
||||
| Value | Firmware name | Description |
|
||||
|
||||
@@ -737,6 +737,10 @@ a fixed pairing PIN, then `reboot` to activate it. `set pin 0` restores the
|
||||
default/generated PIN policy. A PIN saved through the Companion protocol also
|
||||
takes effect after reboot. See the [PIN command reference](cli_commands.md#set-the-bluetooth-pairing-pin-companion).
|
||||
|
||||
The app's Bluetooth settings show the saved custom PIN or Random choice as
|
||||
soon as it is saved. The pairing screen continues showing the active PIN
|
||||
until reboot, when the saved choice takes effect.
|
||||
|
||||
On T1000-E, a USB data host automatically pauses Bluetooth, including an
|
||||
existing phone connection. Unplug USB to resume Bluetooth after 500 ms; a
|
||||
saved off setting stays off. A wall charger without a USB data host does not
|
||||
|
||||
Reference in new issue
Block a user