Related
Hello
I have an XDAIIi and am using skype. Ive found that skype outputs to the main pda speaker, not the phone speaeker, and the quality is not a good as the phone one and of course everyone can hear your conversation.
Is there anything I can do or do we have to wait for skype to support this (if they even can?)
Are there any other applications that manage to use the phone speaker?
Thanks for any feedback
Brian
Hi Brian,
I have a Skype with my XDA2i as well & if someone calls me, my XDA's earpiece was the default. If I want to use my XDA's speakerphone (handsfree or where everybody can hear the caller), all I did was to press & hold the "call" button (they also call this as "send" button, the one you press when you answer a phone call) for around 3 seconds. If I want to deactivate the speakerphone, I press the same button for about 3 seconds.
Hold & pressing "call" button for about 3 seconds will activate/deactivate speakerphone. If you still have the XDA2i user manual, kindly check page 48.
I hope this will help you.
Oneil3
you mean your skype can actually work with the earpiece or you mean normal telephone call works by default with the earpiece?
Vmirage & Brian,
I'm so sorry & it was my mistake. I did not realize what I'm typing a while ago. No, you cannot use XDA2i earpiece while on call, the default is the speakerphone (PDA's speaker). Instead, I use my XDA's earphone to have a privacy while on Skype's voice call.
I got mixed up with a normal call & the Skype's voice call.
Again, my apologies.
Oneil3
Have you tried this?
From the authors website
Please, don't even try to run it on other PDAs - it's absolutely pointless
Click to expand...
Click to collapse
So no I didn't bother
try your BT headset, as IIi support audio gateway. just press the answer button on your BT headset & the sound will be rerouted.
unfortunatly I don't have a headset and really just want to use the phone as normal
Are they compatible?
I've changed the registry to use the voicecmd.exe file instead of the inbuilt Voice Dialer (which I must admit, I never tested with the Jabra!)
But when I press the Jabra button, I hear a noise in my ear but it doesn't seem to activate anything on the MDA Pro itself...
What am I doing wrong?
Have you got the lid closed? If the screen is closed it doesn't work.
This is mad.
If I press the button on my Jabra, I now hear that the voice path is activated but saying "help" into the Jabra mike doesn't do anything. No "mike" icon on the device (lid is open) and nothing happens.
However, with this voice path open, if I then press the voice command button on the device, everything works through BT. I hear the woman and can speak to her.
However, pressing buttons on each device seems a very silly way of doing it.
I should be able to press JUST the headset button, right?
I use the same hardware without issue
I find some commands dont work so well over bluetooth - but call seems to work OK!
I find the built-in mike is better to practice with first THEN try with the headset
I use DIAL <name> at HOME or on mobile etc and this seems OK
My only ***** is than on both BT and the device the VC voice is too low!!
While I remember to 200 Headset supports two profiles - I find the basic one works better with VC (that way you dont accidentally redial if you double tap the button!)
Found the problem. I reinstalled the VC software with no joy, so checked the reg entry. I was missing the space between "Voice" and "Command", so no wonder it wasn't working...
I would have expected an error of some kind instead, maybe... but at least it is solved now.
I changed the registry successfully and on my first attempt used the headset to activate MS VC. Trouble is once the call has ended it appears that the 'gateway' is not closed, therefore you cannot make another call via your headset button until the device is 'warm booted'.
Is there any fix out there that will address this problem. Does it have anything to do with the BT vs Widcomm stacks.
Thanks :?
I find if I hang up using the headset button (Scala 500), even if the other party has already cleared down, the audio gateway closes and the next press of the button on the H/S reacivates audio and fires up VC again.
Are you clearing the call from the h/s or just letting the other party clear down to release the call?
Dox
MS Voice issues with Bluetooth headset
to be honest I've not really noticed. At times I would clear first, others it would be the person I called.
All I know is once the call has cleared I'm left with an open 'gateway' If I restart the headset it's still 'open'. It's only when I soft reset that it clears the headset.
It could obviously be different across different headsets, but with the Scala, audio stays on after a VC command, and I need to press the button once to close it, and a second time to get the VC prompt back. Something like this...
Press...
<Mic Symbol>
"What is the battery level?"
"The battery level is 23%"
Press... (to close audio gateway)
Press...
<Mic Symbol>
After a call, I usually press the button just in case, and I don't recall it restarting the VC prompt, so I assume it's closing the audio gateway. Maybe it's just my timing and i'm closing it as we say "goodbye", so I always force the call to close down, even if the other party is doing the same?
There have been a few "VC doesn't work reliably" threads, so maybe it does, as long as the h/s behaves as MS expected. If you don't use the h/s, just the phone VC button and mic/speaker, is VC okay then?
Dox
That's the way it works for me with T-Mobile Vario & Jabber 250 HS.
What I would like to be able to do is disable the Jabbers own ring tone as it masks the incoming caller announcment, and I appear to get the
phones own ring tone played in the headset anyway.
Also is there any way to make just the voice louder?
I think the VC announcement voice is a normal system volume (system), and the phone call is the in-call volume (right) sliders on the volume dialogue that pops up when you tap the speaker icon on the today title bar. I don't know of a way to increase the VC annc over the ring tone.
I did find on my Qtek that there's a hidden system .wav file in /windows called LB.wav which appears as an alarm and is a really loud 'boing' sound. I copied it to /windows/loudboing.wav with Total Commander, removed the system/hidden flags and use that as an alert. I guess, in reverse, you could use a sound editor to reduce the level of the ring tone .wav file and then turn the system volume up so that the VC annc (if that's what you want to increase) is comparatively louder than the ring tone...
Dox
qtek 9000 MS voice commander 1.6 handsfree voiceenable !
It doesn't work , but now http://www.jetwaremobile.com/index.htm I have this ?!!!
But the voice down in my pocket PC. I want that Handsfree is only "ON", not "OF" after click?...
qtek 9000 MS voice commander 1.6 handsfree voiceenable !
It doesn't work , but now http://www.jetwaremobile.com/index.htm I have this ?!!!
But the voice down in my pocket PC. I want that Handsfree is only "ON", not "OF" after click?...
I've recently been having a play with the Voice Tag function on my Wizard. I can call any of my contacts by voice, and I can perform a plethora of functions on my phone by voice (helped by the added hardware button functions that Pocket+ provides). Now i'm wondering if I can do even MORE by voice, i.e. a spoken password, dialing by saying each number, that kind of thing?
Yeah,
Dump the cheezy Cyberon Voice Dial and get Microsoft Voice Command or Cyberon Voice Commander.
Both allow you to access PDA functions such as launch programs, access calander etc.
Additionally they allow "Dial 444 555-1234"
In my opinion MS Voice Command is better.
I've played with Cyberon Voice Commander because it will read e-mail and text messages but I've found it to be useless. Also Cyberon has too much of a delay from activation to ready for voice input for my tastes.
Oh yeah, neither of these requires "Voice Tags", they work by recgonizing your spoken voice!
Cyberon Voice Commander costs about $20,
MS Voice Command is about $40.
Both can be purchased at Handango.com
Now ... call me silly, but wouldnt it be a slight security risk shouting your password at your device to unlock it ?
Danny-B- said:
Now ... call me silly, but wouldnt it be a slight security risk shouting your password at your device to unlock it ?
Click to expand...
Click to collapse
Maybe that's why none of these products supports it!!
I have given up on MS Voice Command. It works well, as long as you dont use it with Bluetooth.
It dials once or twice, but then stops responding to the Bluetooth command button. The only way I can get it to work is to press the bluetooth button twice to redial the last call, quickly hit the button again to cancel the call, and then, sometimes, the long press will initiate voice command again.
Jumping through hoops like this make the program pretty worthless to me. To dial numbers in the car is all I need if for, and that is where it doesnt work. I will stick with the voice tags.
jimmyhauser said:
I have given up on MS Voice Command. It works well, as long as you dont use it with Bluetooth.
It dials once or twice, but then stops responding to the Bluetooth command button. The only way I can get it to work is to press the bluetooth button twice to redial the last call, quickly hit the button again to cancel the call, and then, sometimes, the long press will initiate voice command again.
Jumping through hoops like this make the program pretty worthless to me. To dial numbers in the car is all I need if for, and that is where it doesnt work. I will stick with the voice tags.
Click to expand...
Click to collapse
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Press once activates the phone over bluetooth (sometimes anyway, sometimes nothing happens at all), pressing again does nothing. Believe me, I have tried EVERYTHING. I was messing with it for two hours doing every combination I could think of. The only thing that works is a double press for redial, end the call right away, then I can activate VC again(sometimes). And the cycle repeats.
On the other hand, built-in voicetag dial works everytime, and I dont have to activate the bluetooth first. One long press prompts for voice dial EVERY TIME.
So I beg to differ, it is an issue with voice command.
JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Same for me. Sometimes the recgonition isn't the same over bluetooth, but I never have to try more than twice. I use my VC for everything.
jimmyhauser said:
JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Press once activates the phone over bluetooth (sometimes anyway, sometimes nothing happens at all), pressing again does nothing. Believe me, I have tried EVERYTHING. I was messing with it for two hours doing every combination I could think of. The only thing that works is a double press for redial, end the call right away, then I can activate VC again(sometimes). And the cycle repeats.
On the other hand, built-in voicetag dial works everytime, and I dont have to activate the bluetooth first. One long press prompts for voice dial EVERY TIME.
So I beg to differ, it is an issue with voice command.
Click to expand...
Click to collapse
So how do you account for it working consistantly fine for some, and others not?
BTW, my VC is loaded on the device, not on a storage card.
VC Usage Vs. VS VC Memory Usage
I've had VC on and off of my 8125 since I bought it in April.
The main problem I have with MSVC is whether its use (or lack there of) validates the amount of memory it uses.
For someone that makes calls primarily off of his recent call list, I find that the usability benefit does not outweigh the memory usage.
Wish there was a way to disable / enable the functionality, as to release that memory for other applications.
JNGold said:
So how do you account for it working consistantly fine for some, and others not?
BTW, my VC is loaded on the device, not on a storage card.
Click to expand...
Click to collapse
Believe me, I am not an expert on this, I am just trying to figure things logically. But I would bet it has to do with the fact that you are probably using a different bluetooth handsfree device than I am. Maybe that was what you were referring to when you said it was a bluetooth issue. Or maybe it is the fact that you have a different model of phone.
What I am saying is that it cant be the bluetooth software on my phone, because the cyberon voice dial works fine over bluetooth, where the MS voice command does not.
And I have voice command on the phone also. All my programs are. I only keep music and videos on the storage card.
And voice command works great when using on the phone itself. I am amazed at how well and how quickly the recognition works. It just doesnt respond well to my Nokia car kit. And maybe that is the problem.
My wife's car has the same bluetooth kit as my car, I am going to try it in her car one of these days to see if I have the same problems there. She has a Nokia 6682, and her bluetooth voice dialling works great.
And also, does VC really use that much memory? If so, I think may take it off the phone. (I use it a little when not in the car) But if it is considerable, then I agree that it is not worth it.
the problem is that without any BT headset i can't get the microsoft voice command to work.
i installed it, dedicate the button. the problem is that when i press it the mic sign appers, i hear the bip and if i say "HELP " it does absolutly nothing.
NOTHING
it just stands there, then another bip comes and the mic sign disappears .
what should i do?
did you turn your mic auto-gain off like the instructions said?
problem solved.
don't know how ...soft reset and bam ! it worked.
the problem is that it hardly recognizes 0 ( zero )
well...i think the old voice dial would do the trick for me...
Keys to success:
1. Load in main memory. (Yes, it's a hog, but to me it's worth it.)
2. Be patient. Sometimes it takes a moment or two to activate.
3. Make sure your volume is not muted. (I admit it, I often walk out of a meeting and get frustrated with why it isn't working... oh, volume is off.)
4. Experiment. Watch the phone while you are playing.
Here are my results with Motorla hs850 .
1. Usually I push once to open the gateway and a second time to activate VC. (Note, I only wear my headset when I need it.)
2. Sometimes the gateway is open for whatever reason and I'll get an immediate bong. So after the first press, I give it a second to see if it will come up.
3. Otherwise, I may get into three presses. One which I think is opening the gateway but is actually opening VC before the bong sounds. A second which I think is activating VC but apparently is closing it. The third press usually then does the trick, but sometimes I'll even have to go to number 4.
So my strategy is:
1. Push button.
2. Wait a slow count for response.
3. Go back to #1 until success is achieved.
I have a Cingular 8125 (2.17 ROM, I believe) and recently got a Motorola HS850 BT headset. It's setup and works great, but I want to know if there is a way to reprogram the call button on the headset so that when you hit it instead of opening the Voice Dial on the phone it can instead open Voice Command (which I use for everything else.) I tried poking around on the boards and didn't see anything specific, any help (or just knowing it's not possible) would be greatly appreciated!
Thanks!
Doug
Found it
I found the answer with a little more searching. It turns out to be a registry entry for Voice Command - and it DOES work with Bluetooth (even though MS' description says it does not.)
Just change this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\Path
change the value from \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe
Soft reset the phone and voice command will work when you hit the connect button on your phone.
Credit to HowardForums where I found it: http://wiki.howardforums.com/pocket...ice_Command_via_Bluetooth_(HTC_WM5.0_Devices)
I heard that it does not close the audio gateway however when you are done with the call...
is this true?
thanks a lot man, this was buggin the hell out of me! quick forum search and i found ur post. thx for doing the leg work
I placed a call with it and when the call was done used the button on the headset to terminate the call...it seemed to work okay.
i just tried it and it seemed to work just fine. the only thing i don't like, and it probably has to do with my headset, is how long i have to hold down the button for...but i can deal with that, so that i don't have to take out the phone!
I guess that the issue is with the regular voice dialer, you can just press the button to dial out, and when the caller hangs up, the audio gateway closes, you dont have to hit the button to close it.
I'm gonna give this a shot to see if I like it.
I did notice that it seems like I have to hit the call key twice in order for it to recognize the key press....maybe the first is to close the old channel and the second opens a new one? I don't have enough knowledge to say for sure, but there is no visual indication on the phone that the voice channel has not been closed.
That's probably what's happening. If you forget to close the voice channel after your call, you'll run down your headset's battery faster. I can tell that the channel is open because I can hear very faint hissing.
Of course, the point is moot for me because on my device (like many others) this trick only works until a call has been placed and ended. After that the button no longer triggers voice command. :-|