Everything works as advertised in the program except for this!
Can anybody else out there confirm that they have this working or is it a known problem?
I have an Xperia X1.
Thanks.
By now, some of you hopefully have tried to see if this works, no?
It's a known problem
http://forum.xda-developers.com/showthread.php?t=451089
Related
I have this problem. When unit is in powersafe mode, when I press main buttom on my BT headset, device doesn't wake up. That makes impossible to use voice dialing while device in the the sleep mode.
I've tried:
GG Telecom
HBH-610
HBH -608
Moto H500
Anyone else?
As I only use the headset in the car its not a problem as I always charge in the car so the unit is always on. I have noticed though that it does not wake the device. I think I-mate make a refernce to it somehere as a fix pending
I have exactly the same issue. In other posts it has been mentioned that people have replaced teh built in voice dial facility with Microsoft Voice Command. I wonder if the same problem persists when using MS Voice Command?
yes its true blue tooth does not wake up our wizards. but considering before when most of us had jams and we where trying to hack our way to bluetooth dialing . this should be a small hill to climb. all we have to do is wait for one of the developers from this site to get one of these beauties and we should be ok
Voice Command 1.5 does not wake it up either. Plus it causes other weird stuff to happen like keeping your bluetooth connection up until you power off your headest or restart the bluetooth service on the handheld. Moreso depends on which headset you have.
BTW, Latest T-Mobile ROM fixed this porblem. Voice dialing works now and wakes up device.
I have a solution to the bluetooth wake up
I have created a fix for this problem. Thus far it works with the default Voice Speed Dial and can be modified to accomodate something else like Voice Command or other.
I have only tested this on a Qtek 9100, but am sure it will work with other Windows Mobile 5.0 devices if they have the same problem.
This will require the Microsoft Compact Framework 2.0 to be installed. Aside from that it is a single executable and registry entry that will fix the wakeup problem.
I developed this myself so if anyone is interested please let me know.
I will not be giving this away, but anyone intested can let me know and I will work out details and modify program for you to accomodate whichever application you are using for voice dial.
Thanks
I have a solution to the bluetooth wake up
I have created a fix for this problem. Thus far it works with the default Voice Speed Dial and can be modified to accomodate something else like Voice Command or other.
I have only tested this on a Qtek 9100, but am sure it will work with other Windows Mobile 5.0 devices if they have the same problem.
This will require the Microsoft Compact Framework 2.0 to be installed. Aside from that it is a single executable and registry entry that will fix the wakeup problem.
I developed this myself so if anyone is interested please let me know.
I will not be giving this away, but anyone intested can let me know and I will work out details and modify program for you to accomodate whichever application you are using for voice dial.
Thanks
This problem does not exist in newer roms.
No need for any fix - simply install a new rom.
I have heard
I have seen the posts. However I am still unable to get an update for my Qtek 9100 WWE. I don't know where to get the updates. On the xda-developers FTP site I don't see any update for WWE except for T-Mobile UK which is not for me. I bought this phone here in the US (not from a carrier) with the typical first release versions. For me all is well aside from the bluetooth wakeup which I have read has been fixed with newer ROM updates. This would be more intended for people in my same situation. If you know where the update can be obtained I'm sure you will help a bunch of other people trying to get the Qtek 9100 updates for WWE. Also I have read that that T-Mobile update on the FTP doesn't have a radio update and also doesn't have AKU2 which is what I am awaiting Microsoft to release.
So I got my hands on a newer version of VC and it work really well on my xv6800 except that its does not announce callers. Isn't VC supposed to do that?
Any idea how to get it to work?
I think mine works, but the voice in general for announcements is VERY quiet! I wish audiopara would also get this loud as well.
Sorry, but I can only tell you thats is extra quiet... Did you ensure that the proper options are checked in the config?
I believe that all the proper options are checked, but I'll look again to make sure. I don't think that the options are independent. I mean if I have notifications going to my BT for appointments and the like, I would think that all notifications would follow the same path. Still, I will definitely check again.
One thing odd is in some of the older versions of Voice Command there was a separate program that was called Voice Command BT which had some setting for bluetooth. I don't see that with this version of Voice Command, but again, I am getting some of the notifications through BT, so I'm sure it has the ability to communicate with the BT.
Can you tell what version of VC it is. I have had mostly success with it but the latest DCD Rom seems to have issues especially if I install the pay for package that I paid for. If I cook it in it seems to work most of the time. Sometimes I have to reboot to get it to recognize my commands.
Voice Command after MR1 update
After I updated using the MR1 release, voice command seemed to work better than ever. What I noticed though is that now it will not announce incoming calls. Announces everything else, but refuses to work on calls. I ended up installing a ripped version (19214) and just need to perform the bluetooth volume regedit.
I have a paid version that I bought 2 years ago to use with my 6700.
It did NOT work at all with the MR1 update or with the 6800 before the update.
I looked online and found a version 19209 and tried that one. All works perfectly!
except one thing. It will not read sms msgs anymore, but I can live with that. Notifications works (except sms), confirm works through bt, it is loud enough to hear who is calling....
Hi there,
I installed the VoIP hack for WM6.1 to get the VoIP feature, so that worked, can use Voxalot over HSDPA/WiFi etc now. But.... Guess what... GPS is not working anymore.
So I found a few files that should enable GPS and VoIP, but still GPS is not working. TomTom say 'no GPS device found'...
Anyone here got VoIP and GPS working on his/her Xperia? Would you please tell me what files I should use?
Argh, that's happened to mine too. Just when I thought I was done with hard resets!
Yeah... hehe... But still, anyone got a solution for this?
i have the same problem! ARGH! im gonna brake my xperia in half, im tierd of hard reseting all the time. have anyone solved the problem yet?
This seems worthy of a *bump* since it's an X1 only problem that doesn't seem to have gotten any attention anywhere at all yet; and also VOIP would be cool.
In addition to the bump, I've followed the instructions from this topic and I got VoIP to work WITH GPS. Howeverrrrr.. As I've posted overthere, unlike the 'normal' suggested cabs, the sound now comes from the external speaker, which of course sucks. I want it to come from the internal speaker.
When you use a Bluetooth headset there is no problem at all, but who wants to walk around with one of those all day long? Was wondering if anyone had a fix for that...!
Hello,
I've got a lot of problems with Voice Command + LEO + BT Headphone.
Voice command speaks on the Leo (Do you want to call Mr TITI at work?) instead of speaking in headphone.
Do you have similar problems??? In France we all have it.
Do you have a solution?
Thanks in advance.
Hi, I have the same problem: some times it use the headset, some times the phone pseaker....
I have other problem with VC 1.6.21725:
- as Mail are read perectly, I have no SMS read.
- Call announcment are not thrown every times I have an incoming call...
Any help?
Is there anymore development for VC? or is it discontinued to Tellme?
same problem here....
does anyone have a solution yet? how to make Leo let voice command speak via bluetooth? Not through the the device? I searched the hole Forum. Any tips and hints that where given didn't work for me. So, if someone have an Idea please post.
Thank you.
Joshua
Same thing happens with Cyberon VSD I am using. Hope someone finds a solution. This didn't happen both in my Omnia and Topaz.
There are a lot of threads here discussing this problem... do a search if you want to research it.
Basically, it is because the HD2 uses the Widcomm BT stack instead of the usual MS one... it will not play nice with many apps (and some hardware) which may have been written with the MS one in mind. This is not an easy thing to fix by just cooking into ROMs too. THe guys with the Touch Pro 2 have this same issues longer than us HD2 owners cause of the same stack... and they still have no solution.
Our only hope is that Widcomm updates their stack to play nice... or more importantly, MSVC or CSVD issues an update that will play nice with the Widcomm stack. Last update to MSVC was shown on Handango site as 20th Nov 2009.... I would like to hear from anyone who has tested this with our units.
Seems to have no issues to our problem
Looks like it's a problem of certain BT headset devices.
Look here http://forum.xda-developers.com/showpost.php?p=5318249&postcount=31
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.