Originally Posted by airheadpenguin
This is the exact issue I have with my Droid. It looks like an existing Droid bug but who knows maybe Sena has a louder voice in the bug triage process than we do. Anyhow I've found that turning off and back on the headset or software disconnecting it from the phone end and reconnecting usually fixes this problem.
Yeah, turning the headset off fixes it but it also does sound likely that it is an issue with the Droid.
That's good news though since we get lots of software updates on the phones.