This issue isn't just affecting the Motorola Droid.
My day old HTC Desire on the O2 network here in England has just befallen this very same issue. I find myself here through an online effort to resolve it, and thought you should all know that my identical experience points to this being Android's fault - not the Droid's.
I'm running a HTC Desire, Sense UI and Android 2.1.
I can't hear any audio over anything but Bluetooth currently. Calls, music, radio, video, notifications, alarms and the loudspeaker... I've also confirmed that the recipient can't hear me during a call now either.
I unplugged the AUX cable from my car whilst the Spotify app was still active earlier today and it would seem that for all this devices inherent wizardry, the simplest of functions has brought it to its knees until I can figure out a way to turn the phone... back into a phone.
I've tried most of the clever and crude methods discussed here but my Desire is still sans audio. Curiously, this 'two ring', 'three ring' headphone conjecture seems to hold some weight. I discovered that by slowly connecting/disconnecting a mic-less 'two-ring' set of headphones I could actually get the Sense UI to depict a headset, despite not having connected one!
My initial layman thoughts are that Android is jumping the gun as to what you've connected and not waiting for the connection to be securely made before running an audio/calling profile, and then locking up.
My only option right now is to factory reset this thing and hope that the bug clears, but I am somewhat encouraged to read that it might not be the HTC Desire's hardware. So thank you all. I hope the info that I've shared above is equally as reassuring in your individual cases.
This needs to get back to Google. I think it's the OS, not the Droid.
My day old HTC Desire on the O2 network here in England has just befallen this very same issue. I find myself here through an online effort to resolve it, and thought you should all know that my identical experience points to this being Android's fault - not the Droid's.
I'm running a HTC Desire, Sense UI and Android 2.1.
I can't hear any audio over anything but Bluetooth currently. Calls, music, radio, video, notifications, alarms and the loudspeaker... I've also confirmed that the recipient can't hear me during a call now either.
I unplugged the AUX cable from my car whilst the Spotify app was still active earlier today and it would seem that for all this devices inherent wizardry, the simplest of functions has brought it to its knees until I can figure out a way to turn the phone... back into a phone.
I've tried most of the clever and crude methods discussed here but my Desire is still sans audio. Curiously, this 'two ring', 'three ring' headphone conjecture seems to hold some weight. I discovered that by slowly connecting/disconnecting a mic-less 'two-ring' set of headphones I could actually get the Sense UI to depict a headset, despite not having connected one!
My initial layman thoughts are that Android is jumping the gun as to what you've connected and not waiting for the connection to be securely made before running an audio/calling profile, and then locking up.
My only option right now is to factory reset this thing and hope that the bug clears, but I am somewhat encouraged to read that it might not be the HTC Desire's hardware. So thank you all. I hope the info that I've shared above is equally as reassuring in your individual cases.
This needs to get back to Google. I think it's the OS, not the Droid.
