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.
Related
Hello all, I am very sorry if the answers to these questions are posted else where but I just could not find them.
I am looking to upgrade my XDA II and this has caught my eye. Im trying to get it on Orange, so first does anyone know a release date for Orange?
Secondly I like this and especially the WiFi capability, internet access is very important for me. How good is the WiFi capability?
Probably lastly can I answer the phone without opening it all up, I would much prefer to be able to press a button and answer like I can with the XDA, the idea of opening, looking who is calling and answering with the whole lot open or closing and ignoring is a put off really.
So can anybody help, or can people recommend this device or would they suggest I go for a different device.
Many Thanks
James
If you are heavy Phone user then you wont be happy with JJ ....
1st its PDA and then comes Phone functions with it...
As everyone agreed in here, Phone users are not yet comfortable with it...
Another honest opinion about it is... TOO COSTLY FOR NOTHING.... so if u can wait for a while.
Not true!!!
It is very good for making calls too. Use a BT headset with caller ID like the Jabra BT800 or the SonyEricsson HBH-660/662 and you wont even touch your phone to make or receive calls. BT voice dial is simply fantastic.
As a PDA, its absolutely FAB!!!
Cost factor, i agree. It is tad expensive
Thanks for the repliies, I am not to worried about the cost, Orange reckon due to my history with them it could well be free.
It just worries me that it has to be opened before you can see who is calling, it is a shame there wasnt a button to answer or dial on the front.
Also these caller ID headsets, how do they work? do they just say the number to you or am I getting the totally wrong end of the stick?
Also any ideas on price of these headsets?
I have the i-mate JasJar version of the Universal, and I am very very very impressed with it. It's a very well rounded device, and sure, there are a few quirks, but they are very minor in my opinion.
You can definitely answer and hang up the phone without opening it. There are two buttons on the side for answer and hang up, so you don't actually need to open the phone to answer. Also, if you use an application like voice command, your phone will tell you who is calling.
I use the wifi at home and I don't have any problems with it. I do wish they would have put in 802.11g, but hey, it's only for internet, so you don't really need that kind of speed just yet.
As for the bluetooth headsets, some of them support the caller ID feature via a little screen on the headset. I have heard different people say that their headset displays only the number, but others have said they display name too. I think the Jabra BT 800 is one that displays only the number with the JasJar, and I think I have heard that the SonyEricsson headsets display the name too. I am not 100% sure though.
Headsets
Can you clarify whether or not you can voice dial from a bluetooth headset WITHOUT first opening up the phone. I have seen some people say yes to this questions, and others say no.
I am happy from what I have read so far that you can ANSWER a call via bluetooth headset without opening up the EXEC, but what I really need to know is about MAKING a call via the bluetooth headset without opening the EXEC.
Thanks in advance
Mike
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 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...
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.
I can't seem to get Microsoft Voice Command to announce the incoming caller ID to my bluetooth - it just beeps - anyone know a fix for this?
Thanks!
Youre not going to like the answer, but use the search in the HD2 forum.Many topics on that already.short answer is it don't work.
ya I was afraid of that because I'd already searched..hahaha....
How about any of the custom ROMS - know if it works on any of those????
I've noticed that it only works if you have an incoming call while already in a call. Other than that, it doesn't work properly.
For what it's worth, I contacted HTC about this, and here is the reply I received on 27April:
Hi, I’m Bill, and I will be glad to assist you today regarding Voice Command announcements through the Bluetooth headset on your HTC HD2 device from T-Mobile. HTC is aware of this issue. Currently announcements are not transferred over Bluetooth headsets. For example, when the phone is set to Announce incoming calls, the announcement comes through the phone speakers as opposed to the Bluetooth headset. We are looking for ways to correct this in future software versions. Thank you for contacting HTC Technical Support. Feel free to contact us again if you have any further questions.
bgkilian said:
For what it's worth, I contacted HTC about this, and here is the reply I received on 27April:
Hi, I’m Bill, and I will be glad to assist you today regarding Voice Command announcements through the Bluetooth headset on your HTC HD2 device from T-Mobile. HTC is aware of this issue. Currently announcements are not transferred over Bluetooth headsets. For example, when the phone is set to Announce incoming calls, the announcement comes through the phone speakers as opposed to the Bluetooth headset. We are looking for ways to correct this in future software versions. Thank you for contacting HTC Technical Support. Feel free to contact us again if you have any further questions.
Click to expand...
Click to collapse
Same issue with the Euro HD2 so I think we can safely say, due to their inability to rectify the issue before launching the US HD2 this is another HTC bug we wont see fixed.