I have a task right now to evaluate the RTT of a bluetooth communication on android, however since L2CAP is no longer supported on android I have to calculate the RTT using RFCOMM, which to my understanding is basically a reliable implementation much like TCP for bluetooth.
My question is does RFCOMM use the same threeway handshake as TCP (SYN/SYN-ACK/ACK)?
If it does, would the RTT from a bluetooth client to a bluetooth server be roughly the time it took for a connection to be established multiplied by 2/3 ( because RTT is just time taken for SYN/SYN-ACK and the time taken for a connection is SYN/SYN-ACK/ACK )?