MITM Bonding issue with Android L

[Now]

Hi, we'd like to use nexus 7 II(android 5.1.1) to connect nrf51822, but cannot connect if nrf51822 uses whitelist.

step 1. we send advertising packets without using whitelist, and uses MITM. Nexus 7 II can do the bonding.

adv_params.type        = BLE_GAP_ADV_TYPE_ADV_IND;
adv_params.p_peer_addr = NULL;
adv_params.fp          = BLE_GAP_ADV_FP_ANY;
adv_params.interval    = APP_ADV_INTERVAL;
adv_params.timeout     = APP_ADV_TIMEOUT_IN_SECONDS;

step 2. then we send advertising packets with whitelist info, nexus 7 II cannot connect to us, even we did bonding before.

adv_params.type        = BLE_GAP_ADV_TYPE_ADV_IND;
    adv_params.fp          = BLE_GAP_ADV_FP_FILTER_BOTH;
    adv_params.p_whitelist = &whitelist;
    advertising_init(BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED); 

But iPhone5s is okay on step2.

Is it google's issue? or we can do something for it?

-Thanks, Bill

[Now]

Hi Hung, thanks for your suggestion. We've clear the database while doing the test, and we'll check if bt address saved in whitelist. When Nexus 7 fails to reconnect, it can find nrf51822 on its scan list and press connect button.

BTW we find a weird behavior:

1. if we clear our nrf51822 database and use nexus 7 to do its first bonding. it's okay for nexus 7 to reconnect while using whitelist advertising.
2. if we delete bonded data in nexus 7, and then re-bonding again. it can't reconnect while using whitelist advertising. The weird thing is nexus 7 can reconnect if we use advertising without whitelist.

looks like data mismatch when we use whitelist advertising.