Bluetooth Issue - Phantom Redial

[Force-1]

This drives me nut. Sometimes my CX-9 Bluetooth will dial a number all by itself. When it happens it's usually to the last number I dialed from my cell. For example, I was driving down the road today when my stereo muted, and I hear "hello". It's my wife, and I did not initiate the call, nor did she.

Another time I called our local 311 system. About 10 minutes later system mutes, and I hear "311 operator, can I help you". I said sorry, hung up, and it did it again about 5 minutes later!

This has happened on at least 10 occasions over the last 2 years. I know it's not the phone, as it occurred with my Palm, and now it's happening with my HTC Hero.

Anyone else experience this?

 

[ZoomFive]

This drives me nut. Sometimes my CX-9 Bluetooth will dial a number all by itself. When it happens it's usually to the last number I dialed from my cell. For example, I was driving down the road today when my stereo muted, and I hear "hello". It's my wife, and I did not initiate the call, nor did she.

Another time I called our local 311 system. About 10 minutes later system mutes, and I hear "311 operator, can I help you". I said sorry, hung up, and it did it again about 5 minutes later!

This has happened on at least 10 occasions over the last 2 years. I know it's not the phone, as it occurred with my Palm, and now it's happening with my HTC Hero.

Anyone else experience this?

If the headunit just mutes and you hear the person, it is likely that your phone initiated the redial and then the BT put it on. If your headunit initiated, you would have heard prompts before it initiates. You can test this by shutting the BT on your phone off and seeing if your headunit ever tells your "Phone not Avaiable" on its own. Where do you keep your phones? My little bro "butt dials" me all the time. First with his old phone and now his iphone/

 

[Force-1]

If the headunit just mutes and you hear the person, it is likely that your phone initiated the redial and then the BT put it on. If your headunit initiated, you would have heard prompts before it initiates. You can test this by shutting the BT on your phone off and seeing if your headunit ever tells your "Phone not Avaiable" on its own. Where do you keep your phones? My little bro "butt dials" me all the time. First with his old phone and now his iphone/

My phone is always in a case that's on my belt. The case covers all the buttons, plus I don't see how this could happen with my HTC since the dial pad and all buttons are "virtual", and the screen is always blank unless I unlock it. In order to make a call with my HTC I have to press the power button, slide my thumb down the screen, and go through at least 2 more motions to initiate a call.

 

[ceric]

Force-1,
It could be your phone. I have the HTC Touch Pro.

The programming (either Win Mob or HTC) is just dumb. Allow me to elaborate.
My HTC Touch Pro (AT&T) in holster in sleep mode (it is touch-based).
When you make a call or got a call, the stupid phone actually wakes up (why not handle the call and NOT activating the screen touch). Once the call is over, it does not "immediately" go back to sleep. (until the set time limit is reached) The phone is still in contact with the holster, therefore, creates a bunch of random "touche" events, which likely triggers the "redial" last call.
It has happened to me many many times. I finally found this out.

What do I do to deal with it?
Once I got a call or before I want to make a call, I have to take the phone out of holster and place it on the console.
Once the call is done, I put it back to sleep (and put it back into my holster if I choose to).

Even that, the Win Mob sometimes "wakes" up all by itself (synch-ing, or whatever?!). As I said, this is just stupid. Touch-based phones with random "uncontrolled awakening" is not a good combination. These guys who programmed the phone seem to be ignorant. Do they even use the phones they sell?

I hope this help. It may not be the CX9 Bluetooth's problem.

 

[Force-1]

Force-1,
It is your phone. Trust me. I have the HTC Touch Pro.
The programming (either Win Mob or HTC) is just dumb. Allow me to elaborate.

HTC in holster in sleep mode (it is touch based).
When you make a call, the stupid phone actually wakes up. Once the call is over, it does not "immediately" go back to sleep. (until the set time limit is reached) The phone is still in contact with the holster, therefore, creates a bunch of random "touches", which likely trigger the "redial" last call.
It has happened to me many many times. I finally found this out.

What I do?
Once I got a call, I have to take the phone out of holster and place it on the console.
Once the call is done, I put it back to sleep (and put it back into my holster if I choose to).

Even that, the Win Mob sometimes "wakes" up all by itself. As I say so many times, this is just stupid. Touch-based phones with random "uncontrolled awakening" is not a good combination. These guys who program the phone seem to be ignorant. Do they even use the phones they sell?

I hope this help. It is NOT the CX9 Bluetooth's problem.

Thanks! What's funny is it never happens in my Cadillac STS, which also has Bluetooth as part of the nav system.

 

[ceric]

Thanks! What's funny is it never happens in my Cadillac STS, which also has Bluetooth as part of the nav system.

Interesting...
Maybe the hand-shaking between the two BT units are different from STS to CX9. You can easily try it to verify my solution. Next time, before you make a call, take it out of the holster. While you make the call, see if the screen wakes up....