Hi Colin, > # hcidump -t -X -V This dump looks truncated. Is this all the output or did the trace start generating tons of SCO packets that you snipped? There might be BT commands/replies in the mass of SCO packets that got snipped too. Also, you need to set the already-running bluetooth daemon into debug output mode. You can do this with: sudo kill -SIGUSR2 [pid of bluetoothd] Then the daemon log will be way more useful - please repost that daemon log. Also, there's no need to include pulseaudio output because I virtually guarantee it's just "the messenger". I noticed the time stamps in the trace and log aren't for the same interval. The hcidump trace and the daemon log should be for the same events/time interval, ok? Regards, Peter Hurley -- 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
