Scan interval, passive versus active scanning, connection parameters, etc.
The HID example sends advertising packages every 25ms the first 30 secs.
I'm using a "standard" android based mobile phone and a "standard" notepad app as the receiver of the HID keyboard keys - so none of the mentioned parameters can be changes at that end.
The very first connect is done within a second - but the auto re-connect is always taking 20 secs.
Are you hard resetting? Soft resetting might have different results.
Have you tried running a debugger on the PSoC? Determing what the timing is on the chip might shed light on what is causing it to take so long.
Have you checked the supervision timeout setting on the PSoC? (That is the time until it times out with no received packets from the other side of the connection).
Yes hard resetting the CYBLE-222-005 (via the reset key on the Pioneer test board) - then it starts advertising, and the Android is responding after 20 secs. Checked with the TI CC2540 BT packet sniffer.
I'm running the program from the PSoC 4 Creator/debugger.
Since the BLE device is only advertising, it is NOT the one initiating the connection, that would be the Android phone. So, if it takes that long it is either the connection parameters (which you can't change) or the android phone is really slow in finding it...
Since you checked with the packet sniffer, then that means the BLE is actually advertising on the CYBLE. I'm not sure what more you could do from the CYBLE standpoint :/