Hi Jaikumar, > Looking at this a bit further, I see a discrepancy between the code in > function hci_conn_complete_evt and hci_sync_conn_complete_evt. > Is this intentional or a bug ? Like I said below, using > hci_conn_complete_evt (when the AG doesn't support eSCO) results in > the connect() never returning because the socket state is not updated. I still have no idea what's your problem. It doesn't matter if the remote side supports eSCO or not. The sync setup commands can be used even for setting up SCO channels. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
