<frown> While I'll admit that I expected you would need to
explicitly pair the device *initially*, I guess I am
surprised that you have to repeat this procedure, again,
when you "simply" move out of range.
You don't have to repeat the pairing (with PIN codes etc.). But it
seems the phone is not aware that the headset is in range until the
headset sends some sort of notification.
Or, am I misreading your statement: the device may
remain paired but this *session* is "broken"? I.e.,
you can "answer" the next call but can't "reconnect"
to the current?
I've never tried to go out of range during an ongoing call.
There is a small icon (a headphone surrounding the BT logo) on the
phone that shows that a BT headset is connected. If that icon is shown
when an incoming call arrives, the BT speaker beeps to indicate the
incoming call, and the call can be answered from the headset with a
short press of the button.
If the phone goes out of range, the headset icon disappears and does
not automatically come back when the phone comes back into range. In
this state, an incoming call cannot be heard or picked up from the
headset. What you can do, is to press and hold the button for a couple
of seconds to initiate the reconnect. That takes a few more seconds,
and then you can answer the call.
I know some BT hands-free units (which is essentially the same thing)
will reconnect automatically when the phone comes into range. I once
was in a conversation with a person who was walking towards his car.
As he got close enough, the audio was automatically transferred to the
HF inside the car, and we could not hear each other until he opened
the door and got into the car.