Both the ACI_EVT_TIMING and ACI_EVT_CONNECTED events include timing values, but currently they're only copied into the passed in aci_stat structure for ACI_EVT_TIMING.
So the timing calls like lib_aci_get_cx_interval_ms(...) return 0 after the ACI_EVT_CONNECTED is received and only report a proper value if you actively change the timing using lib_aci_change_timing(...) or lib_aci_change_timing_GAP_PPCP().
This small change copies the timing values for ACI_EVT_CONNECTED, just as is currently done for ACI_EVT_TIMING, so that the user can later retrieve the initial timing values received when the connection was established using lib_aci_get_cx_interval_ms(...) etc.
Both the ACI_EVT_TIMING and ACI_EVT_CONNECTED events include timing values, but currently they're only copied into the passed in aci_stat structure for ACI_EVT_TIMING.
So the timing calls like lib_aci_get_cx_interval_ms(...) return 0 after the ACI_EVT_CONNECTED is received and only report a proper value if you actively change the timing using lib_aci_change_timing(...) or lib_aci_change_timing_GAP_PPCP().
This small change copies the timing values for ACI_EVT_CONNECTED, just as is currently done for ACI_EVT_TIMING, so that the user can later retrieve the initial timing values received when the connection was established using lib_aci_get_cx_interval_ms(...) etc.