made adjustments
This commit is contained in:
parent
d9e3e1dd21
commit
c0e90597c7
1 changed files with 6 additions and 1 deletions
|
@ -93,7 +93,10 @@ The settings reset firmware has Bluetooth disabled to prevent the two sides from
|
|||
|
||||
## Unable to Connect to Device
|
||||
|
||||
Some devices and operating systems may have additional security/protocol settings that they require be met before allowing a bluetooth peripheral to pair with them. If your keyboard is visible to your host but you are having trouble connecting or no input is registered, this might be the cause. You can try enabling some of ZMK's [experimental bluetooth settings](../config/bluetooth.md) to resolve the issue.
|
||||
Some devices and operating systems may have additional restrictions that they require be met before allowing a bluetooth peripheral to pair with them. If your keyboard is visible to your host but you are having issues trouble connecting or no input is registered, this might be the cause. Some of ZMK's [experimental bluetooth settings](../config/bluetooth.md) may suffice to resolve the issue. In particular:
|
||||
|
||||
- Disabling PHY 2Mbps ([`CONFIG_BT_CTLR_PHY_2M`](https://docs.zephyrproject.org/3.5.0/kconfig.html#CONFIG_BT_CTLR_PHY_2M)) helps to pair and connect for certain wireless chipset firmware versions, particularly on Windows (Realtek and Intel chips) and older Intel Macs with Broadcom chipsets.
|
||||
- Enabling passkey entry ([`CONFIG_ZMK_BLE_PASSKEY_ENTRY`](../config/bluetooth.md)) helps for certain Windows computers (work-managed ones in particular). This may also manifest in not sending keystrokes.
|
||||
|
||||
## Issues While Connected
|
||||
|
||||
|
@ -142,3 +145,5 @@ If this doesn't help, try following the procedure above but replace step 3 with
|
|||
|
||||
- Restart the Windows device
|
||||
- Open "Device Manager," turn on "Show hidden devices" from the "View" menu, then find and delete the keyboard under the "Bluetooth" item
|
||||
|
||||
Some Windows devices may also require passkey entry, described under [Unable to Connect to Device](#unable-to-connect-to-device).
|
||||
|
|
Loading…
Add table
Reference in a new issue