• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Problem: having issues reconnecting to bluetooth headset after disconnect

I've been using bluetooth headsets with my Vibrant for a while with no issues. Lately (past month or so) I've had a lot of problems getting headsets to connect.

I have a few headsets - Plantronics Voyager Pro, Etycom Etyblu2, a few cheaper ones. I'm mainly using the Etyblu2 right now. Once connected the headset works fine. But if I try to connect it after having the headset off for a while, it wont connect - the headset will not connect to the phone when tapping the power button. The phone will not connect to the headset, neither by connecting to the etyblu2 entry in the bluetooth menu, or by doing a "scan devices".

I just disabled bluetooth, waited 10 minutes, and reenabled it and it reconnected right away. What the heck?

I noticed something - when the phone is working, I can press the "scan devices" button and it'll say "scanning devices", and show the devices in my house (including my laptop). When the phone is glitching, clicking on the "scan devices" button does nothing (the 'scanning devices' doesn't show) and it only shows my remembered/paired devices, but nothing else in the house. Seems like bluetooth at that moment is not functioning correctly.

Anyone have ideas why this is happening? Anyone see similar problems? I know to disable & reenable bluetooth to get it working, but I'd really like to fix this problem if I can.

Thanks!

Samsung Vibrant
Teamwhiskey Bionix-V (Froyo 2.2), stock kernel.
 
As a followup, I've been noticing some patterns.

If the phone's BT has been on a while, then the headset will not reconnect. I turn the phone's BT off, then on, then turn the headset on - nearly always reconnects quickly.

Twice today I've been on a call talking on my headset, and the audio switched over to the phone. The headset was still connected, the battery was fully charged, and neither made the connect/disconnect BT sound. But I had to turn the headset off/on to reconnect. Weird.

I wonder if this is all due to my etyblu2, or the vibrant, or the teamwhisky froyo build I'm using (bionix v). I'd love to get a new headset, but not if I'm still going to get the same problems.

Anyone else have any bluetooth experiences, good & bad? Am I the only one struggling with this?
 
Back
Top Bottom