Bluetooth¶
Each fact ends with its kind and its source:
documented, read in firmware 1.5.1's sources, or seen on the device.
A firmware bump can break the second kind, so its links pin tag 1.5.1.
A keyboard of its own¶
The app starts the firmware's HID profile with its own name, address and key file, so the stock Remote's bond stays as it was.
The name is Claude Remote, written over the whole advertised name:
the profile's own field takes a prefix under 8 characters
(documented: hid_profile.h),
and the advertised name holds 18 bytes
(firmware 1.5.1's sources: furi_hal_version.h),
the first of them its AD type
(firmware 1.5.1's sources: gap.c),
which leaves 16 characters.
Claude with the device's name ran to 21, so the name is Claude Remote alone
(seen: ble-transport, task 3.1).
The address is the device's own with mac_xor applied
(documented: hid_profile.h;
firmware 1.5.1's sources: hid_profile.c).
The app's 0xC1A0 is neither the stock Remote's 0
(firmware 1.5.1's sources: hid.c)
nor BadUSB's 0x0002
(firmware 1.5.1's sources: bad_usb_hid.c).
The bond goes to /ext/apps_data/f0_claude_remote/.bt_hid.keys
(documented: bt.h),
and the stock Remote's key file keeps its MD5
(seen: ble-transport, task 4.2).
The app advertises whatever the device's Bluetooth setting, as the stock Remote does
(firmware 1.5.1's sources: hid.c),
though the documentation asks to turn Bluetooth on
(documented: Controllers).
Pairing¶
Pairing starts from the computer's Bluetooth settings
(documented: Controllers),
and the firmware draws the Verify code dialog, with Cancel and OK, over the app
(firmware 1.5.1's sources: bt.c),
so the app has no screen for it.
The link reads as up only once pairing completes
(firmware 1.5.1's sources: gap.c),
so Reconnecting... shows until OK.
The open Apps browser blocks pairing.
The browser is a dialog of the dialogs service
(firmware 1.5.1's sources: loader_applications.c),
which shows one dialog at a time
(firmware 1.5.1's sources: dialogs.c),
so Verify code waits behind it.
Launched over the browser, the app showed no dialog, the Mac's request failed after 30 s, and closing hung
(seen: ble-transport, task 4.1).
Launch from the desktop.
After a drop¶
The firmware advertises again after a disconnect
(firmware 1.5.1's sources: gap.c),
so the app holds no reconnect code.
Disconnected from its settings, the Mac reconnected by itself in 866 ms
(seen: ble-transport, task 4.3).
The app stops advertising 60 s after its opening, a drop or the press that starts over,
and that press starts it again
(documented: furi_hal_bt.h).
The 60 s are the firmware's own fast phase, every 80–100 ms, before every 1–2.5 s
(firmware 1.5.1's sources: gap.c),
where a connect took 28 s and once timed out at 31 s
(seen: ble-transport, task 4.5).
Stopping cuts a connection in progress
(firmware 1.5.1's sources: gap.c),
waits until the radio is idle
(firmware 1.5.1's sources: furi_hal_bt.c)
and reports the link down itself
(firmware 1.5.1's sources: bt.c),
so Reconnect stopped ignores link reports until a press.
A pressed key stays in the profile's report until a release clears it
(firmware 1.5.1's sources: hid_profile.c),
so Ctrl+Q, held for voice, would go out with the next key after the link returns.
A drop during voice therefore releases it at once, with no link:
the report clears whatever the update answers,
since a failed update only logs
(firmware 1.5.1's sources: gatt.c).
Leaving¶
The app ends the link as the stock Remote does:
disconnect, 200 ms for the second core to write its storage, the default key path, the default profile
(firmware 1.5.1's sources: hid.c;
documented: bt.h).
With the setting on, the desktop then shows the Bluetooth mark,
and the device's own key file keeps its MD5
(seen: ble-transport, task 4.7).