I have a problem and have't been able to find any information on it. I have a TMoUS HD2. I had an original Jawbone lying around so I paired it and it works perfectly. I decided to pick up a Jawbone 2. I paired it, but it developed a problem. While outgoing calls are no problem, I cannot answer calls with it, nor can I initiate voice dialing with it. Incoming calls are routed through the handset. I deleted the pairing, and re-paired it to no effect. I also tried the original Jawbone again and it again worked fine. What I don't understand is why it initially worked properly, then developed this problem (with no changes to the phone).
Any ideas?
me too
Same problem with Proplantronics headset, new to me handset formerly T-Mobile just loaded this ROM:-
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
If I find the answer I will let you know.
mcc2905 said:
Same problem with Proplantronics headset, new to me handset formerly T-Mobile just loaded this ROM:-
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
If I find the answer I will let you know.
Click to expand...
Click to collapse
well, it was probably me. I was answering with the handset rather than the earpiece. it didn't matter with the old one, but it does with this one. chalk it up to unfamiliarity with the newer unit. either that or the phone woke up in a better mood today.
sorted
Yes, thanks for that, pressing the call control on the headset is the answer, also found the autoanswer option which should also fix it. Lots of stuff seems to be hidden away on 6.5.
Still learning after all these years.
mcc2905 said:
Yes, thanks for that, pressing the call control on the headset is the answer, also found the autoanswer option which should also fix it. Lots of stuff seems to be hidden away on 6.5.
Still learning after all these years.
Click to expand...
Click to collapse
Glad my fumbling around with this thing was able to help someone.
Related
I am very sorry in advance if this issue has been raised elsewhere on the site, but after spending quite some time searching for an answer by both the forum search and google search, I am going round in circles and haven't found a solution.
I have a UK Tmobile Vario 2 (Hermes) running its original Rom (I have been too scared to flash it in case I break the phone as I don't really know what I am doing) and I have a Motorola S705 A2DP headset. I love the feature on VC 1.6 which reads out new text messages in full but can't find any way of routing the audio for this feature through my bt headset. The incoming call notification works through the headset but every time an SMS comes through it pauses A2DP, reads it via the phones loudspeaker, then diverts sound back to the headset again?!?
I went on the WIKI and found the Voice Command section. I tried installing the patch/program it suggests and did the tweaks it said to the registry , but it didn't make any difference on this problem.
I just wondered if this is an unfixable problem, or if there is anything I can do to get it working because this feature would be incredibly useful to me (I ride a motorbike and to get texts read through my headset when riding would be excellent).
Thanks in advance for any help guys. Sorry again if I am raising a known issue, if I am, if you could point me in the right direction it would be much appreciated.
have you tried this? i know this .cab file worked on my jawbone but i dont/have not used VC 1.6.
bapski said:
have you tried this? i know this .cab file worked on my jawbone but i dont/have not used VC 1.6.
Click to expand...
Click to collapse
Thanks Bapski, I have just installed it but unfortunately it hasn't helped thank you anyway though, it was definitely worth a try
Well, I have had a good read through the threads on Voice Command and all the fixes for the headset button but it seems nothing yet solves the problem of routing the SMS notification through the headset which is a shame, it would have been so useful.
Well, hopefully, when I get my nice new Kaiser upgrade (whenever that may be ) .. I will have more luck with the bluetooth audio
Don't buy a phone with a MS BT stack because they will never fix the problem..MS has known about this for so long its just sad..The next phone I get will have a widcomm bt stack.
Yeh, got to say that the bluetooth hasn't been particularly great ... especially when trying to get it working on A2DP.
If only I hadn't stumbled across VC 1.6 I would be none the wiser and wouldn't even know it is possible to have SMS messages read out oh well
it doesnt work dont even bother, I loved it on my wizard, but there is a hardware problem with the heremes or whatever the problem is the last revision of the BT stack doesnt fix it and its never worked. all the patches and fixes only work for awhile then just stop and rquire a cryptic series of hacks to make them half work again. your better off buying a thai slave to read your messages to you.
I hope someone is able to help me.
Okay I have the Wizard, upgraded to Wizard Mobile 6.
Shortly after, all my bluetooth devices (car kit, headset...) had their microphones die. In other words nobody could hear me when speaking through any kind of bluetooth.
I then flashed the Radio ROM to a different version, and bluetooth was repaired. But now the problem has returned for no reason.
Why does my Wizard's bluetooth audio in keep failing, yet its speaker works fine and I can hear other people?
Is there a recommended update to the Bluetooth Stack I can try?
CJSnet said:
I hope someone is able to help me.
Okay I have the Wizard, upgraded to Wizard Mobile 6.
Shortly after, all my bluetooth devices (car kit, headset...) had their microphones die. In other words nobody could hear me when speaking through any kind of bluetooth.
I then flashed the Radio ROM to a different version, and bluetooth was repaired. But now the problem has returned for no reason.
Why does my Wizard's bluetooth audio in keep failing, yet its output works fine and I can hear other people?
Is there a recommended update to the Bluetooth Stack I can try?
Click to expand...
Click to collapse
I do have exactly the same problem. After flashing XDA Mobile 6 Release 3, microphone has worked for couple of days, and then suddenly died. Interesting, microphone is working with Notes but not with phone. I went back to
XDA Mobile 6 Release 2 for some other reasons (read: 2MB more free memory for critical application) but the problem with Bluetooth microphone remains. Radio is 2.25. Any advice?
--
Pogo
There are also at least 3 people at the Wizard Mobile 6 thread with the same issue. Very surprised none of the experts here have been able to propose a fix. Makes the phone virtually worthless if you can't use it in the car etc.
As a workaround, I have found if you mute then unmute the phone volume, the issue is sometimes temporarily resolved for a short time. It always comes back though
I have been asked to join this thread. Per a PM:
We love the ROM you have provided, and are very thankful, however it was not until installing it that this issue arose. It does not seem fair to leave a number of people with a phone that is unusable for 'phone calls'.
Click to expand...
Click to collapse
(Bolding added by me)
I don't know what to tell you. If the rom doesn't work for you, then don't use it... Don't tell me its "not fair". I use MS Voice Command, and XM6r3 and have never seen this issue with my Bluetooth headset (Jawbone). I've also tested this out with a Plantronics Explorer 210 headset that I have and it has not problems with XM6r3 either. My A2DP headset (Spider) also works fine on XM6r3 with MS VC. I've stated this in the past when people have said they have BT issues on my rom. Sorry, but I can't reproduce it, so its hard for me to fix something that isn't broken for me.
Try this... Do a hardreset on your device (take a backup first if you want), then leave it as the base rom with NOTHING extra added. Run that way for a few days (how ever long it has taken before) and see if the problem happens again. If it doesn't then its not my rom but something being added to it (probably screwing with the registry someplace). If it does happen, then as I've stated before, I've seen a number of BT devices be flakey on WM6 (especially car kits). Try a different rom then. If someone with the problem can pin it down, I'll be happy to do what it takes to fix this issue if its something in the rom that is causing it.
Thanks mfrazz. What wasn't fair was not the bug, but that you had not responded to previous mentions of it, i.e. not fair to leave us with it. We love the ROM and put a lot of our life in your hands in a way, as we rely on our device so much for work and play. Hope you understand.
Now then, I have already tried a hard reset and the problem never occurs, until WM6 is put back on. Sure, 'use another ROM' is all very well, but we love yours - again, hope you appreciate the sentiment. If you're in a relationship, are you the kind of guy who tells a girl who loves you, 'find another boyfriend', or do you try to make it work
SO, I am wondering if this is related to the glitch you mention where sometimes when switching out of vibrate mode, the ring tone becomes muted. For that, your solution is to play the ringtone again, then it becomes unmuted.
Similarly, our Bluetooth devices mic's are being muted, and if we mute then unmute them again, then they become unmuted. A link that helps point you in the right direction?
Please note, this is not certain bluetooth devices being 'flaky', this is ALL devices. 4 at the latest count, including rock solid Nokia CARK7W car kits and Jabra headsets.
Some people put it down to MS Voice Command, which I have never installed. What does that program do, do you know, to cause the bug? Again I hope that might help point you in the right direction.
Please don't dump us Let's try to fix what is wrong in this relationship
BT problem solved?
CJSnet - not sure if you have resolved this. I was having the same problem and noticed people with reTouched dialer were not, so I loaded that dialer and the problems went away. I am using a Plantronics Voyager 510. Seems the problem might be with the standard dialer.
Hope this helps
CJSnet said:
There are also at least 3 people at the Wizard Mobile 6 thread with the same issue. Very surprised none of the experts here have been able to propose a fix. Makes the phone virtually worthless if you can't use it in the car etc.
As a workaround, I have found if you mute then unmute the phone volume, the issue is temporarily resolved for a short time. It always comes back though
Click to expand...
Click to collapse
Thanks, I'll give that a try. However WM6 has pretty much finished the Wizard for me, and I'm hoping to get a TyTN II soon as a replacement. Shame.
I recently got a Samsung WEP500 to go with my Cingular 8125. It works great except for one problem: The WEP500 only has a single, big multi-function button. Pressing this button just once while the phone is idle will cause the phone to redial the last number. This is a pain because the button is really easy to accidentally activate when putting the earpiece in or when you just have it in your pocket. It's gotten to the point where I'll call my voicemail just to have that as the last dialed number, so I wont pocket-dial someone I know.
Is there a way to disable the redial functionality of a bluetooth hands-free headset? I'm running a pretty stock Cingular build, with the default ROM of 2.0.25.11 for both OS and radio, which is of course WM5.
I'd be most appreciative for any help. Thanks!
+1
Would be nice to leave my BT radio on all the time.
I am also having the same problem with my Bluetooth. Still waiting for a solution.
WEP500
I aslo have same problem.
Have you tried turning the headset off when putting it in your pocket?
I NEED this too. I have the Scala Rider Q2 for my motorcycle and a single press on the button re-dials ther last number I called, whereas if I hold it, it turns on the radio.
I often find myself trying to listen to my music and end up speaking to someone...
Thanks for the idea of calling my voice mail BTW, never thought of that.
I know this is an old thread, but just in case someone is still interested in this, you may try solving it the way i did for my HTC Polaris. I have no idea if Wizard got similar bluetooth stack or even if WM5 got an option to load audio gateway at commands extensions in general, but, well, it worth a try.
http://forum.xda-developers.com/showthread.php?p=5355333#post5355333
Disable Bluetooth-initiated redial.
Hi I´ve tried your cab file om my HTC touch cruise WM6 with a sony-ericson bluetooth headset device but it did´nt work.
Do You have a alternative solution or maybe an updated cabfile?
I used to use MSVC 1.6 on the Tytn2 on WM6.5 (see sig) and the confirmation notifications when you called someone always used the bluetooth headset. Since running it on the Leo MSVC seems to use the loudspeaker on the handset instead of the bluetooth headset even though every setting is marked as "Announce notifications using Bluetooth hands free only"
Anyone else having this issue as I did a search and couldn't find anyone.
Edit: Just had it working once but then the other end couldn't hear me when the call connected. Then I tried again and it had reverted back to not working.
I went to Bluetooth settings, Advanced, Audio and ticked the box then rebooted the phone...
I have this same problem! Its annoying... you want to make a call and the prompts/confirmation come from the phone... Please, can someone figure this out?
Bumping thread as it should be resolvable
Starfury said:
Bumping thread as it should be resolvable
Click to expand...
Click to collapse
IT isn't... I have done more research..
The Leo (and the TouchPro2) use a Widcomm BT stack as opposed to the usual MS stack. Sadly, this means the BT won't play nice with a lot of different apps/equipment. This isn't something that can be swapped out easily as NRG has pointed out. Touch Pro 2 users are still facing the same problems even though that phone was released much earlier. Some however have reported some success when using certain custom ROMS... how its working with some ROMS and not others is still a mystery it seems
I would watch the ROM Development thread carefully to see if a ROM what works with our MSVC shows up....
Hello,
Is there a workaround... ?
Thanks in advance for any info,
Jean-Jacques
I have the same problem. I'm using an old phone when I need to use hands-free. After spending a lot of money on my HD2, I'm not impressed.
I there a particular combination of headset and software that does work, especially for voice dialing?
have you tried this?
I would, but I don't know if I even have voice command on my phone.
http://forum.xda-developers.com/showthread.php?t=634494
DrATty said:
I there a particular combination of headset and software that does work, especially for voice dialing?
Click to expand...
Click to collapse
Does not work with my helmet bike with scala-rider Q2, but does with does with Philips SH9000 stereo headset...
Mono/Stereo seems to matter.
Any workaround would be veryyyy appreciated
Jean-Jacques
Workaround
Hi,
for this following workaround seems the only way to get it runnin:
My BT-Headset has the ability to be set as a Stereo-Device. When I establish a connection to this Stereo-Device, I can use it (my BT Headset) to give Commands and recieve "answers" from the VC. In case I want to start a phone-Call, my headset changes the connection automatically from "Stereo-Device" to "Handsfree-Device" and back, after finishing the Call.
This may be the Reason, why someone here already got it running with a BT-Stereo-Headset.?
Sorry for my bad english...
Got the phone on the second day it was available. Upgrade from the Touch HD. Nice phone in general. The problem I ran into was Microsoft voicecommand would not announce incoming calls through the bluetooth headset no matter what changes and adjustments tried it would only announce through the phone speaker. I had this working on the Touch HD fine. Spent the entire day with T-mobile tech support which was not very helpful on matters of anything technical. Then called HTC tech support and spent about an hour and a half trying to get it to work. The answer HTC gave me was my headset was not compatable. I have three different bluetooth headsets none of which they could get to work. I asked the tech what headset HTC tested with this phone and I would gladly purchase that brand. His answer was he did not know. My answer, this does not function on this phone and was not tested. Has anyone else tried to get bluetooth caller id working and if so what were your results. I have since returned the phone till this is resolved if ever.
has anyone tried caller id announce incoming calls on their bluetooth? Am I the only one having this issue. Could someone please test this on their HD2 and let me know if it works for them.
Thanks
It has been a problem on the european hd2's also. Since HTC started using the widcom bluetooth stack none of the existing voice control apps (such as MSVC) are working properly. If you search around you will find a few threads about the same problems with bluetooth headsets.
Thank You very much for your answer. I was hoping that was not the case. I waited for this phone to come out and bought it right away. I use mostly basic functions, phone, voice dialing, appointments etc it was a shame I had to return it the extra features were nice to have and the screen is beautiful. Does anyone know if they are working on an answer for this???
polera257 said:
Thank You very much for your answer. I was hoping that was not the case. I waited for this phone to come out and bought it right away. I use mostly basic functions, phone, voice dialing, appointments etc it was a shame I had to return it the extra features were nice to have and the screen is beautiful. Does anyone know if they are working on an answer for this???
Click to expand...
Click to collapse
Try here, good info on this subject. I would like to hear my ringtones in my headset but this is the best answer I have found to this. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=654165
Guadm, Thanks for the link. I will give it a read and see what's up. I wish someone could figure what is causing the conflict with caller announce not going through the bluetooth. I got everything else going to bluetooth except caller ID.
polera257 said:
Guadm, Thanks for the link. I will give it a read and see what's up. I wish someone could figure what is causing the conflict with caller announce not going through the bluetooth. I got everything else going to bluetooth except caller ID.
Click to expand...
Click to collapse
you are welcome. I am waiting for Blue Ant's T1; it announces the caller by name, and that's good enough for me if I cant get the ringtones.