I've read other posts regarding Bluetooth Issues with the Lumia 920 and the HTC 8X. It does not seem to be specific to a phone brand. Maybe it is an OS (Firmware Issue)?
It also does not apply to just cars of a certain brands. This has been tested with In-Car Bluetooth of a Ford Focus, a Mercedes Benz, a Honda...; and also after market "Visor" Bluetooth Handsfree devices like the BlueAnt S4.
This is on the Samsung Ativ S WP8 with the latest updates. Telus Flavour.
a) In Handsfree Mode, call drops - phone freezes. Bluetooth cannot be used again until a Battery Pull. A Reboot (via Reboot Hold Button) will not work.
b) This is a more exact description of what happens....
"I received the Bluetooth handsfree visor device (BlueAnt S4) on Monday. Unfortunately it behaves the same as the others (His Car's In-Car BT Handsfree). Today I was driving up to Jasper, I was on the phone and it was working properly. I lost the call due to poor cellular reception. When I called back after getting reception back, the phone screen says dialing?, then is says connected?, but I have never heard the phone ring and the person on the other end cannot hear me nor can I hear them. They then called me back, I touch the device to receive the call, the phone reads, connected?, but once again there is only silence. I quickly grabbed the phone, disconnected Bluetooth and was able to talk to the person. After finishing the call, I re-enabled blue tooth and tried to call the office, the same thing was happening, I had to disconnect Bluetooth to use the phone. I then shut off the phone, removed the battery and rebooted the phone. Blue tooth connected properly and I am able to use the handsfree.
It appears that if you do something out of the ordinary such as have a dropped call, or answer a second incoming call without hanging up on the first, the Bluetooth no longer functions. It is as if the phone has never closed the previous call and will not communicate any longer with the blue tooth device properly."
We are about to deploy WP8 to a few hundred users in our company. 2 users out of 15 in our Beta Test Group are experiencing this issue. Without this solved, we won't be going WP8...
Somehow, someone hopefully will tell me what is wrong and provide a fix
It also does not apply to just cars of a certain brands. This has been tested with In-Car Bluetooth of a Ford Focus, a Mercedes Benz, a Honda...; and also after market "Visor" Bluetooth Handsfree devices like the BlueAnt S4.
This is on the Samsung Ativ S WP8 with the latest updates. Telus Flavour.
a) In Handsfree Mode, call drops - phone freezes. Bluetooth cannot be used again until a Battery Pull. A Reboot (via Reboot Hold Button) will not work.
b) This is a more exact description of what happens....
"I received the Bluetooth handsfree visor device (BlueAnt S4) on Monday. Unfortunately it behaves the same as the others (His Car's In-Car BT Handsfree). Today I was driving up to Jasper, I was on the phone and it was working properly. I lost the call due to poor cellular reception. When I called back after getting reception back, the phone screen says dialing?, then is says connected?, but I have never heard the phone ring and the person on the other end cannot hear me nor can I hear them. They then called me back, I touch the device to receive the call, the phone reads, connected?, but once again there is only silence. I quickly grabbed the phone, disconnected Bluetooth and was able to talk to the person. After finishing the call, I re-enabled blue tooth and tried to call the office, the same thing was happening, I had to disconnect Bluetooth to use the phone. I then shut off the phone, removed the battery and rebooted the phone. Blue tooth connected properly and I am able to use the handsfree.
It appears that if you do something out of the ordinary such as have a dropped call, or answer a second incoming call without hanging up on the first, the Bluetooth no longer functions. It is as if the phone has never closed the previous call and will not communicate any longer with the blue tooth device properly."
We are about to deploy WP8 to a few hundred users in our company. 2 users out of 15 in our Beta Test Group are experiencing this issue. Without this solved, we won't be going WP8...
Somehow, someone hopefully will tell me what is wrong and provide a fix