I couldn't think of a good title for this and it may be misleading.

I've only owned one headset (Sony HBH300) with 3 HTC Phones (6600, 6700, 6800). They all worked fairly well and was my baseline for behavior.

On the HTC phones my headset was always connected. I leave my headset in the car. When I get back in the car I just click the button on the headset and make a call. If the phone rins I answer it. With some ROM's on some HTC phones. I had to wake the phone before I could click headset to call out.

I bought my wife a Sprint LG Fusic and Plantronics 330 headset. It didn't come close to this behavior. I was not sure if it's the phone or Headset. Then I tried her on a Motorola V3xx with same headset. It worked reliably but seems fairly dumb. You have to "reconnect" headset everytime it goes out of range. She also leaves headset in the car. Now I moved her onto the Motorola Q and it behaves pretty much the same as the V3xx Razor. Have to manually reconnect.

Manually reconnecting for calling out isn't so bad for calling out. You don't need to touch the phone. Just hold button in on headset for a like 10 seconds and it reconnects.

But reconnecting manually for an incoming calls is difficult or impossible. I push and hold while it's ringing. Sometimes it works. Sometimes it makes the phone answer but headset not connected. Sometimes it hangs the call up and then headset it prompted for Voice Command (I think I started a 3 way call).

This whole "reconnect" thing seems very visible on all phones except the HTC. On HTC I just answer it like I would as if I just finished a call 1 minute ago or have had the two seperated for a weekend. The Q even has a beep tone to notify you headset has "disconnected". And a Timer showing how long it's been connected. And if you leave "Standard audio on" it seems like the headset is active 100% time and not asleep.

This whole behavior and understanding it I think has a lot to do with battery life.

So how do you use you headset?

Namely if your headset has been out of range, then goes back in range and a call comes in. What do you have to do to get on the headset?

I had similar issues with the iPhone and Sony headset. Nothing seems to come close to what HTC phones do. And bluetooth seems to have little to no impact on battery life.

It appears to be related the combination of phone and headset. I use the H500 with the Q and it will reconnect every time if it is a brief out of range without any button pressing. If it has been a longer time, then simply pressing the button to reactivate the headset will reconnect the headset.

You may want to experiment with a different headset for the Q.

Rob.

Even as a call is coming in? If I reconnect before call comes in it will work fine. But is this "connected" state chewing up battery?

For example if say I leave phone and headset in car overnight with it in "connected" state will the battery be dead? It's as if it's in a full "active" state when it's "connected". If I left the HTC phone and headset together for 3 days after a fresh call say, it will still have charge. I'm not trying to comparing battery here performance. I think the model used is different.

Part my question is do other phones work differently. There is no concept of connected or disconnected state in the HTC phones. It's paired or not paired and if it's in range it will ring in my ear if not it will ring in the phone. It's as if it polls constantly to see if the headset is there and if it is, it uses it. It also has no concept of a headset profile vs a normal profile. Yet even in this "polling mode" it doesn't seem to consume battery.

After a whole bunch of calls I have it sorted out.

Problem was I was confusing a long button push on the headset for Voice Command activation with what's need to reconnect headset.

A quick Tap for out going or incoming works (whether it is in a disconnected state or not). If it's disconnected it just takes longer.

On out going I was pushing and holding listening for the Voice Command beep prompt thinking that was a reconnect headset beep. So when doing that on an incoming call it got all mixed up.