Hi,
I’ve noticed different behaviors when connecting a iAP2 enabled Bluetooth Classic radio module using an iPhone 6 (MG472QL/A) or an iPad 2 (MC769TY/A).
The following module's logs tell that when iPhone 6 (iPad 2) calls the module, the iAP1(2) is negotiated.
Please note that the two devices are updated to the very same version of iOS (9.2)
So, there are two possibilities:
a) the iPad 2 hardware does not support iAP2, and the module falls back to iAP1
b) the module works differently with an iPhone and an iPad
Please, can anybody exclude or confirm one of the two hypothesis ?
Regards,
Gabriele
>>>>>>> Connecting iPad 2 …
RING 0 70:de:e2:73:1e:dc 3 HFP 0
HFP 0 CODEC NEGOTIATION
HFP 0 BRSF 1007
RING 1 70:de:e2:73:1e:dc 6 IAP 0
HFP 0 STATUS "service" 0
HFP 0 STATUS "call" 0
HFP 0 STATUS "callsetup" 0
HFP 0 STATUS "battchg" 3
HFP 0 STATUS "signal" 0
HFP 0 STATUS "roam" 0
HFP 0 STATUS "callheld" 0
HFP 0 CHLD (0,1,1x,2,2x,3)
HFP 0 READY
IAP 1 OK IAP1 <<<<<< iAP1 is negotiated
>>>>>>> Connecting iPhone 6 ...
RING 0 78:d7:5f:9d:72:24 3 HFP 0
HFP 0 CODEC NEGOTIATION
HFP 0 BRSF 1007
RING 1 78:d7:5f:9d:72:24 6 IAP 0
HFP 0 STATUS "service" 1
HFP 0 STATUS "call" 0
HFP 0 STATUS "callsetup" 0
HFP 0 STATUS "battchg" 2
HFP 0 STATUS "signal" 4
HFP 0 STATUS "roam" 0
HFP 0 STATUS "callheld" 0
HFP 0 CHLD (0,1,1x,2,2x,3)
HFP 0 READY
HFP 0 NETWORK "I TIM"
IAP 1 OK IAP2 <<<<<< iAP2 is negotiated