HID Keyboard - Problems After Disconneting and Downloading

RE: HID Keyboard - Problems After Disconneting and Downloading

MANGO — Wed, 25 Feb 2015 05:43:55 GMT

Thank you for noticing me about the disconnection reason. Both "forget the device" and Bluetooth off

gives reason number 0x13 (timeout reason). Looks like there's no way to tell which one is which

when they both fall into BLE_GAP_EVT_DISCONNECTED.

Thank you for reminding me Petter.

RE: HID Keyboard - Problems After Disconneting and Downloading

MANGO — Fri, 20 Feb 2015 23:03:08 GMT

When I test with Nexus 5 (4.4.2), it is fine.

However when I test with Galaxy Note 3 (4.4.2), it sometimes doesn't work properly.

RE: HID Keyboard - Problems After Disconneting and Downloading

Petter Myhre — Fri, 20 Feb 2015 15:24:20 GMT

On Android as well? I didn't catch that. I tested it on my Samsung Galaxy Note 4 (4.4.4) and Samsung Galaxy Note 2 (4.4.2), and it works. Can you please test again?

RE: HID Keyboard - Problems After Disconneting and Downloading

MANGO — Fri, 20 Feb 2015 09:19:44 GMT

One more thing, without using this,

err_code = bsp_button_is_pressed(BOND_DELETE_BUTTON_ID,&(init_data.clear_persistent_data));
APP_ERROR_CHECK(err_code);

how can I delete it regardless of the button press?

What other function do I have to call?

Edited : I see. Although the same problem seems to appear when I test with Android devices,

I'll ask to th Apple dev page. Thank you.

RE: HID Keyboard - Problems After Disconneting and Downloading

MANGO — Thu, 19 Feb 2015 11:16:10 GMT

Thank you for checking the Bluetooth mark.

The not working situation cannot be explained yet?

Also, whether I select "Forget the device" or Bluetooth off,

the HID peripheral falls into disconnect event.

However there is no way that the peripheral to tell which was selected(forget device/bluetooth off)

from the phone?

RE: HID Keyboard - Problems After Disconneting and Downloading

Petter Myhre — Wed, 18 Feb 2015 11:39:43 GMT

The ble_app_hids_keyboard application can handle 7 bonds (DEVICE_MANAGER_MAX_BONDS 7).

When you press "Forget This Device" you will erase the bonding information on the phone, but it will still be on the peripheral. If you don't delete it on the peripheral I'm not entirely sure what will happen, either will add a new bond and work, or it will believe it is already bonded and not work.

Downloading the code will not erase the bonding information, so after 7 or 8 downloads you will have 7 or 8 bonds stored (if you bond every time), since 7 is max I think this is when you get the issue.

The bonding information can be erased by checking "Erase Full Chip" in Options for Target->Utilities->Settings->Flash Download or by pressing a certain button on startup:

// Clear all bonded centrals if the "delete all bonds" button is pushed.
err_code = bsp_button_is_pressed(BOND_DELETE_BUTTON_ID,&(init_data.clear_persistent_data));
APP_ERROR_CHECK(err_code);

Edit 19.02: Removed a Bluetooth symbol mistake.

Edit 20.02: I have been able to reproduce this; I think it is an iOS bug. The peripheral actually adds a new bond, and it is sending key presses, but iOS is not responding to them. We will investigate further, but you should report this to Apple. I will edit this answer if there are any updates from our side.

There is a reason that comes with the BLE_EVT_DISCONNECT event, but it is the same reason if you turn off Bluetooth or press Forget this device, so you can't separate them.

If you always delete the bonding information there is really no reason to store it persistently, anyways, you should look into dm_init(). Please add this as a new question if anything is unclear.

One more thing, you shouldn't use directed advertising with iOS since it is changing it's address every 15 minutes.