Hello,
a friend of mine have some troubles with his TP and a Blaupunkt Radio with build in handsfree.
The Bluetooth pairing was completed without any problems.
When a calls comes the radio mutes and switch to handsfree - thats ok
The caller can hear your voice over the handsfree microphone, but you can't hear the caller. It is the TP build in speaker used, not the handsfree speaker.
The TP has the headset symbol shown in the upper right corner of the dialer.
Second the radio don't switch back to radio when the call ist ended the Bluetooth Connection stays up. Only deactivating/activating of Bluetooth at TP closes the connection and the radio switch back.
I hope somebody can help me...
Thanks!
I had this problem with my TYTN using shaps rom. you ave to turn on the hands free on the first incoming call and then further calls are OK. (right menu and turn on hands free)
this has to be done every time you get in the car though.
Its a pain i never found a fix. I havnt used this on my Touch Pro yet.
With Pioneer DEH55BT all working fine.
Thanks for the workaround... Perhaps it works for my friend, i will test it in the afternoon.
But another radio is no solution,it have to be this!
Try installing jetware mobile, it improves the bt connection but I don't know if it will solve your problem.
Related
Hello there.
Here is my problem:
My Magician has the earphone broken due to a hardware incident, so I decided to use it with a BT headset. So, I bought a Plantronics Explorer 340 BT headset which works great, apart from some BT disconnection issues. When I get a call (when it rings, it does not connect to the headset), from time to time, the BT of my phone disconnects, thus leaving me with no sound for the BT headset.
Are there any patches (besides the one from the ext roms called BTHUSB_PATCH_AKU26.CAB) that could make my BT connection last while receiving a phone call?
Thank you.
Hi all,
I have a problem with MS Voice Command 1.6.
It 'sorta' works right now ... when I press the button on my BT headset (Motorola H700) it initiates the voice command on the Treo. However, the 'beep' is played from the treo speaker, not the BT headset. When I spoke the voice command, I must also speak to the Treo mic, not the BT headset. This sucks when you are in a noisy environment.
When the call is connected, it does go through the BT headset so that's good. But it's just when you want to initiate a voice command, you have to speak to the mic on the phone. All the announcements also come through the phone's speaker only, not the BT headset.
Has anybody found a fix to this?
Thanks in advance
Try deleting the headset and reacquiring it via bluetooth. I had to do this a couple of times before this corrected
Hmmm I've done it quite a few times already ... but I can try it again.
Mine does this too. If there is no fix, I will have to go back to the at&t one.
Removing and re-adding BT headset doesn't work. After doing some more homework, it seems like the problem is Treo 750, among a # of other phones (like Hermes) uses a BT stack that is incompatible with MS's and that is the reason why.
Searching on the Hermes site there IS actually a workaround which fixes half the problem.
To make long story short, after trying to fix recommended by that site, now I can speak to the BT headset to issue voice command.
Meaning, when I press the BT headset button, I hear the VC chime from my headset, not from the phone's speaker. And when I issue voice command I also speak to the BT headset, not the phone's mic.
What it doesn't fix, is notification STILL comes through the phone's speaker and not the BT headset, even with all the correct settings under MVC.
But I'm ok with that ... I can live with this.
number16 said:
Removing and re-adding BT headset doesn't work. After doing some more homework, it seems like the problem is Treo 750, among a # of other phones (like Hermes) uses a BT stack that is incompatible with MS's and that is the reason why.
Searching on the Hermes site there IS actually a workaround which fixes half the problem.
To make long story short, after trying to fix recommended by that site, now I can speak to the BT headset to issue voice command.
Meaning, when I press the BT headset button, I hear the VC chime from my headset, not from the phone's speaker. And when I issue voice command I also speak to the BT headset, not the phone's mic.
What it doesn't fix, is notification STILL comes through the phone's speaker and not the BT headset, even with all the correct settings under MVC.
But I'm ok with that ... I can live with this.
Click to expand...
Click to collapse
you have a link to this fix???
Please help! I tried to search for an answer to my problem, but while it seems there have been issues aplenty with WM and BT, I couldn't find a similar case.
So, how it goes: I have my Sony Ericsson HBH-DS980 Bluetooth stereo headset connected to my TP, when I receive a call. I pick up the call with the headset, and everything goes smoothly for a couple of minutes, but then suddenly I can't hear anything from the earplugs. I check the phone, and it shows that BT is on, but doesn't have the icon indicating that a headset is connected. I check my headset, and it's powered up. The call has been transferred to the phone. I restart my headset, and the TP discovers the headset, after which I can redirect the call to the headset. After a few minutes it all happens again!
It's extremely frustrating! Can anyone help, please?
I'm using standard 1.90.401.1 WWE ROM.
aBE-One said:
Please help! I tried to search for an answer to my problem, but while it seems there have been issues aplenty with WM and BT, I couldn't find a similar case.
So, how it goes: I have my Sony Ericsson HBH-DS980 Bluetooth stereo headset connected to my TP, when I receive a call. I pick up the call with the headset, and everything goes smoothly for a couple of minutes, but then suddenly I can't hear anything from the earplugs. I check the phone, and it shows that BT is on, but doesn't have the icon indicating that a headset is connected. I check my headset, and it's powered up. The call has been transferred to the phone. I restart my headset, and the TP discovers the headset, after which I can redirect the call to the headset. After a few minutes it all happens again!
It's extremely frustrating! Can anyone help, please?
I'm using standard 1.90.401.1 WWE ROM.
Click to expand...
Click to collapse
today i jus encounter this prob a few times,,,i didnt restart bt...i jus like it rest a while then thne icon indicated headset is connected then i clck transfer again
Hey guys
I recently bought a Chatterbox XBi2 bluetooth headset that supports A2DP and Handsfree, and using MSVC the mic is activated on the phone, not the headset.
I am able to play music through it, and I can answer calls in the default configuration.
The default behaviour for the main button is to run redial.exe, and none of the remap posts I tried (reg keys/dll's/etc) worked, so I just copied voicecommand.exe over redial.exe, and this does work as it should. (MSVC voice launches and comes over the headset).
The problem is, the mic that is activated is the mic on the phone, not on the headset.
This is driving me nuts, as this headset is completely useless to me without MSVC.
Can anyone help???
thanks
Cory
EDIT: I have a touch diamond
I've been searching my ass off to no avail, someone must know something to point me in the right direction.
thanks
I am the happy owner of a HTC Topaz.
I ride a motorbike, and have recently bought a bluetooth crash helmet with built in speakers / mic which works a treat for answering and making calls and also for listening to TomTom navigation instructions from my HTC Topaz.
However, I have yet found a solution to allow me to listen to the built in radio via bluetooth. Because HTC requires the plug-in headset to act as an antena the radio doesnt work without it.
However when I plug in the headset, i get instant radio reception but then the sound is routed to the plug-in headset , rather thean the bluetooth speakers.
My logic tells me that there must be some way to use the plug in headset as ONLY an antena allowing the sound to be routed by deafault to the bluetooth headset. Surely this is software driven?
I am not a software Guru, but keen to learn and frustreted that there doesnt seem to be a yet obvious solution to this problem.
Any help would be appreciated.
T
Why 4 threads?