Hi Mike, Luiz, > I think I've figured out why I didn't see the SEP error print out. > The function resume_a2dp calls a2dp_sep_lock. The only place this > ever gets unlocked is in a suspend call. If a2dp_resume returns an > error code, the sep remains forever locked. And it seems, the SEP > will no longer let acquire happen on future A2DP connections, > requiring bluetoothd to be restarted for this to work. I'm experimenting similar issues right now on hfgw. Could it be because the endpoint is crashing after acquiring? Frédéric -- 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
