Related
I am looking for users with problems using the MS Voice Command on the T-Mobile Wing/Herald and their fixes or commments.
I have been using WM devices and MS Voice Command for many years. I have had a variety of devices all using voice command; but none have been worse at recognition and speed as my Wing has. How does everyone else with a wing feel about MS Voice Commands performance.
Problems I experience:
Slow response to initialization (1-2 seconds usually)
Slow finding a contact and confirming (2-4 seconds)
Most times with some background noise just gives up and makes that aweful beep.
Always asks to Please try again
Will not understand through bluetooth headset at all.
Commonly mistakes simple names for others i.e. (John Patrick)
Now the voice command can work pretty accuratly in a queit room other than the responsiveness, but I have had it installed on numerous devices and know how it should opperate and the tolerance to noise. I have overclocked my CPU to 273 and doesnt seem to help. I have tried increasing the page pool to 4mb which I have 23mbs for memory and still no luck. Ive even tried the combination of the two but doesnt seem to help. No other progams have been installed for test purposes to see if there is any conflicts and I have about 73 contacts, and sync very little content.
My previous device was a Wizard which respectively is very simular. It did work good with voice command 1.6 both on WM5 & WM6. I have had it installed on a Audiovox PPC4400 (WM2003), Treo 700wx, Blue Angel (WM5), and a Hermes (WM6); all the later devices worked best with no noticable delay or comprehension issues. The Herald will work with the same bluetooth equipment almost flawlessly, the wing will initiate the command but always fail to understand or will pull up something else.
I would like to know if I'm and isolated instance or if everyone has this problem.
Thanks
Jcostanza4
Works fine for me! However, I do speak in a Robotic tone.
Naw, I cant get that thing to do what I tell it.
YES!!!! MS Voice Command on the Wing is almost unusable for me. On my Wizard it was amazing -- fast and accurate. On the Wing frustrating, maddening and worthless.
I have experimented with standard versus overclocking, mic gain settings... everything I can think of. It seems to be a little bit better if I have Bluetooth turned off -- but just a little bit.
I have been reading these forums since the Wing was released and have been surprised that others have not commented on the problems with MS Voice Command on the Wing.
I sure wish there was an answer. Does anyone know what the problem is?
I agree with you, I dont know why more people haven't brought it up.
This is one of the biggest downfalls of the Wing for me. I love everything else even speed when overclocked and the page pool make it quite fast. But I just disable voice command completly because it is so unrelaible. I think it would more likely be along the lines of a hardware compatibility issue that the software would have to overcome or a fix in the OS; but I really dont know.
I wonder if the Herald guys get this problem or if its just an issue with the Wing OS.
Time will tell.
Jcostanza4-
It seems like it's just the crappy microphone on the bottom. It picks up EVERY noise around you and that confuses the voice command. I've noticed that if I use the wired headset that came with my wing it's almost always accurate.
Take a voice note in a semi-noisy environment and you'll see what I'm talking about. It definitely is not a noise canceling microphone.
Well... I can confirm that the audio quality of a voice note is clearly superior on my Wizard than on the Wing... considering that other people do not seem to be up-in-arms about MS Voice Command, I am coming to the conclusion that the microphone on the Wing is at fault.
Has anyone had problems reported with phone calls
Ive asked people if I sound faint or hard to hear and they say it sounds fine/normal. Also bluetooth mics also seem to have the same problems with comprehension when other Window Mobile devices with the same hardware work like they should. Ive tested the Hermes with WM6 on the same bluetooth car kit with MS VoiceCommand over bluetooth and no problems; I know certain bluetooth with VC works and some dont, the Wing seems to operate just like the hermes as far as initiation. This would bypass the poor mic theory on the Wing right?
jcostanza4 said:
Ive asked people if I sound faint or hard to hear and they say it sounds fine/normal. Also bluetooth mics also seem to have the same problems with comprehension when other Window Mobile devices with the same hardware work like they should. Ive tested the Hermes with WM6 on the same bluetooth car kit with MS VoiceCommand over bluetooth and no problems; I know certain bluetooth with VC works and some dont, the Wing seems to operate just like the hermes as far as initiation. This would bypass the poor mic theory on the Wing right?
Click to expand...
Click to collapse
I haven't used a bluetooth headset before on my wing but my wired headset works flawlessly almost every time. It could be that the bluetooth connection wasn't as strong or something (biased towards the wing not working when testing?). I still believe it's the microphone but I could be wrong
I havent really had too much problem with it, I'm using the PDAVIET rom and had to reinstall voice command once i had the rom, and it seems to work fine. Have you tweaked the mic gain?
Tweaking th mic gain.
dcmtnbkr said:
I havent really had too much problem with it, I'm using the PDAVIET rom and had to reinstall voice command once i had the rom, and it seems to work fine. Have you tweaked the mic gain?
Click to expand...
Click to collapse
Is your device a wing or a herald?
Im still using the stock T-Mobile Rom on the wing and Ive enable and disable the mic gain; shows no improvement that I can tell. Now the Wing comes pre installed with Voice Command and does not have a remove from the Uninstall Program options. I did once try to install 1.6 over it to see if i could get back the remove option and when I clicked reset to finish after installing it hard reset on me.
On your PDAVIET rom, does the vioce command launch instantly, respond quickly, and understand you to some degree or is there some trouble in any of these areas?
Thanks for the info
jcostanza4
me, too - very disappointing indeed
Yes, I just got the Wing a couple of days ago after giving my wonderful Imate Jam one too many love taps (the touchscreen has stopped accepting any input)...and I'm experiencing exactly the symptoms you listed with VoiceCommand. It actually does seem to do a little better through the BT headset, so the "poor mike" theory might be on the right track. But without the BT, it can't understand a damn thing--even in perfectly quiet environments--and takes forever.
I've been using the Jam with VC for over two years, and it is fast and damn-near flawless. Indeed, I've been a huge VC zealot; 'never been able to understand why WM-device reviewers don't even mention it but instead say things like "it's too hard to dial calls one-handed when driving." And for years already, while the best that other devices could offer was "voice tags" that users had to manually create, VC has, as you know, seamlessly worked with all my ~500 Outlook contacts. As far as I'm concerned, VC is the killer app that provides a huge part of the value of WM devices. If you ask me for the phone number of any of my friends, family or business clients, I couldn't tell you, 'cuz I haven't dialed them in years.
Now comes the Wing to set progress back five years or so. I have 12 days to make a decision about returning it.
mtn_lion said:
Yes, I just got the Wing a couple of days ago after giving my wonderful Imate Jam one too many love taps (the touchscreen has stopped accepting any input)...and I'm experiencing exactly the symptoms you listed with VoiceCommand. It actually does seem to do a little better through the BT headset, so the "poor mike" theory might be on the right track. But without the BT, it can't understand a damn thing--even in perfectly quiet environments--and takes forever.
I've been using the Jam with VC for over two years, and it is fast and damn-near flawless. Indeed, I've been a huge VC zealot; 'never been able to understand why WM-device reviewers don't even mention it but instead say things like "it's too hard to dial calls one-handed when driving." And for years already, while the best that other devices could offer was "voice tags" that users had to manually create, VC has, as you know, seamlessly worked with all my ~500 Outlook contacts. As far as I'm concerned, VC is the killer app that provides a huge part of the value of WM devices. If you ask me for the phone number of any of my friends, family or business clients, I couldn't tell you, 'cuz I haven't dialed them in years.
Now comes the Wing to set progress back five years or so. I have 12 days to make a decision about returning it.
Click to expand...
Click to collapse
I made all of my contacts store with first name, last name format and the recognition appeared to get a lot better. You shouldn't have to do that but it seemed to help so you could try it. I am temporarily trying the wing overclocked to 273mhz with a boost up to 286mhz and in a quiet environment I haven't had a problem with the voice recognition finding my contacts. I still have trouble with the "play" command and it's VERY difficult for it to understand my "yes" for some reason but contact recognition is good and speedy.
The yes response or correct doesnt pick up well for me either
I did notice this too, but I always forget that thats one of my biggest problems with dailing by name or number. Let's say its a bad mic, even with a headset wired/wireless does it seem to lag in speedy ness or accuracy?
I did mess with page pool on the Wing, I ran 4mb for about 2 months then moved to a 6mb and the device is overall faster than the 4mb or 12mb. The 6mb page pool defenitly responds quick when it can understand you; but 70% of the time it can understand and gives that very long pause before saying "please repeat". It does seam like voice command when enabled eats about 5mb or ram. I have 22.5mb on a soft reset and after using voice comand once it drops to 13mb and then goes to 17mb after about 3 minutes of no use.
I have not read anything from the Hermes users to show that they are having these issues. Could it be an OS problem that translates the mic to the program?
Jcostanza-
kraftey--Thanks for the suggestion, which makes sense, I guess...but I'm not willing to organized my contacts by first name, period. Call me a neo-traditionalist.
As I've posted in the overclocking thread, I can't get my Wing above 228 without the screen flickering.... Ideas?
jcostanza4--Thanks, too. Honestly, in a *perfectly* quiet environment, recognition is not bad, and using either BT headset or not, time from command to response is 5-7 seconds. That doesn't sound like much, but in actual use at work it's an eternity--and made much worse by all of the "Please Repeat"s, additional delays and/or failures.
I've got the pagepool set to 6MB, and I've mucked about with performance-related registry tweaks, but the 5-7 seconds and poor recognition in real-world environments is the best I've been able to get out of VC so far.
Im overclocking the Wing with Battery Status Ver. 1.04.203
I have the device set on dynamic mode so its 201Mhz on minimal load and 273Mhz on Max Load. Battery can last quite a while like this and I havent had screen issues. I hope this helps. I had issues with some other overclocking apps, and eventually tried this one and it worked. No complaints and Ive been using it for about 4 months.
Yes. The darn thing is frustrating. This was supposed to be top of the line. I paid around $250 for the PDA and I paid $100 for a top of the line bluetooth, and the voice mail keeps trying to call my Brother Jeff, regardless of what I say. I paid $140 for a Jawbone, and got the same poor performance. Just how much do I have to pay to get something that works.
Yes, jc, that helps. I had already moved to BS, but now I'll update it with the 1.04 beta. For starters, what OmapClock was calling "228", BS calls "247." With the "released" version of BS, I still get the screen flicker above "247." We'll see if it's any different after I install the beta. Thx.
I solved my Voice Command Problems!
I originally posted all the issues I was having with Voice Command 1.6 on my T-mobile Wing. I now have a working Voice Command to my standards, it works as it has on all my other devices; a little slow at times but not more than a second lag. Recognition is accurate and mic also seems to work better.
Here is the steps I used. (this was completely accidental, as I was trying to get TouchFlo working on the Wing)
I reflashed the T-Mobile Wing RUU found in the Herald wiki section or this thread http://forum.xda-developers.com/showthread.php?t=321717
Then Flashed the Original T-Mobile Rom with Touch Flow found here http://forum.xda-developers.com/showthread.php?t=329456
Then I Ran the Automatic 6mb page pool found here http://forum.xda-developers.com/showthread.php?t=324955
Then I installed Battery Status and overclocked my Wing to 273mhz.
I dont know if the RUU that was released was an update to the original rom, but my mic seems to work great now and recognize with about a 90% accuracy rate.
Please try this at your own risk, This may work for me and may not work for you. By all means I am no programer nor can I assist in a sticky situation.
I suggest reading each of the other threads I have listed before attempting. I will not be responsible if you brick your device. There is alot of information in each thread that is not posted on the first Topic like using ASerg Policies or how the page pool works or common problems.
Thanks-
Jcostanza4
Start > Settings > System > Microphone AGC
I don't use voice dial because I had all the same probs as the original poster. May want to give this a try before all of the steps mentioned in the post before me
for me it is working fine most of the time but not as good as it did with my wizard it is not slow and recognizes commands most of the time, I am using the pdaviet rom build 12 I changed the page pool to 4mb and clocked to 260 with bs , my problem though is that I can't get voice command to work by pressing the bluetooth headset button wich works fine on the wizard.
Does voice command come with WM6 or is it something you have to add to the Kaiser yourself? Anyone have any opinions, good or bad, about its functionality?
You have to purchase and install it yourself...
And then you have to make some minor tweaks.
Look at this thread: http://forum.xda-developers.com/showthread.php?t=333260
Is voice dialing working?
e.g., are commands/prompts routed to/from the headset (rather than thru the Kaiser's speakers like on the Hermes)?
Would love to know if the hacks can be avoided and if the product finally works as advertised...
My experience is that yes - the commands and prompts are indeed routed to my BT headset... However, I think a few folks have had other experiences for some reason..
It works for me though - without registry hacks.
goestoeleven said:
e.g., are commands/prompts routed to/from the headset (rather than thru the Kaiser's speakers like on the Hermes)?
Would love to know if the hacks can be avoided and if the product finally works as advertised...
Click to expand...
Click to collapse
It works if you have the Microsoft Bluetooth stack (most HTC devices, if not all). Doesn't work if you dont (Blackjack, for example).
i installed MS VC 1.6...and it will give name over headset.....
gnafin said:
i installed MS VC 1.6...and it will give name over headset.....
Click to expand...
Click to collapse
which version are you using mines doesnt announce over headset
duttythroy said:
which version are you using mines doesnt announce over headset
Click to expand...
Click to collapse
Same question here. Had to do this tweak to get it going.
did not work for me.....
anybody knows how to adjust the speed to the notification being read. female voice is just too fast when reading sms messages.
i just installed ms voice command on my att tilt and the sms and emails do not readout. i have all the settings set like my friends dash and it still does not work like his. his dash has WM6.
Mine works... so far.
I am not having any problems with the Tilt and original rom. But I am also using a BT stereo headset. I wonder how much that makes a difference. I will test some more and try and post the results.
i can use voice commands to access programs and make calls. it wont read out my sms or email. i tried using my wired headset and nothing. my BT is charging. i'll try it later.
sqadan said:
You have to purchase and install it yourself...
And then you have to make some minor tweaks.
Look at this thread: http://forum.xda-developers.com/showthread.php?t=333260
Click to expand...
Click to collapse
OK, this is really getting me frustrated. I had VC working fine on my 8525, but can't seem to get it to work on the Tilt. I don't have that registry key in the registry. All I have is: HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand and it's empty.
What is really driving me crazy is that I had used VC1.6BTFix.CAB fix when I first got my Tilt and could have sworn it worked, but a few days latter, it no longer worked and nothing (not even a hard reset) will fix it. When I do install that fix, I do get a path setting under the above key, but it's to a different app. Changing it to Voicecmd.exe doesn't fix it either.
Does anyone have any ideas?
Thanks,
jglev said:
OK, this is really getting me frustrated. I had VC working fine on my 8525, but can't seem to get it to work on the Tilt. I don't have that registry key in the registry. All I have is: HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand and it's empty.
What is really driving me crazy is that I had used VC1.6BTFix.CAB fix when I first got my Tilt and could have sworn it worked, but a few days latter, it no longer worked and nothing (not even a hard reset) will fix it. When I do install that fix, I do get a path setting under the above key, but it's to a different app. Changing it to Voicecmd.exe doesn't fix it either.
Does anyone have any ideas?
Thanks,
Click to expand...
Click to collapse
Jeff,
This is what I have done in the past with my 8525 and that registry key and it might work for you. Change the path to end with "VoiceCommand.exe" instead of "Voicecmd.exe." If I remember correctly, both programs are in that directory.
Give that a shot.
Brad
Park City said:
Jeff,
This is what I have done in the past with my 8525 and that registry key and it might work for you. Change the path to end with "VoiceCommand.exe" instead of "Voicecmd.exe." If I remember correctly, both programs are in that directory.
Give that a shot.
Brad
Click to expand...
Click to collapse
Thanks Brad. I read here that people have gotten it to work just by installing it on the Tilt with no hacks or registry edits, so I disabled the BTfix program, uninstalled it, rebooted and the darn thing works! I never tried it right out of the box since it was known that it didn't work on the 8525. I just assumed that it wouldn't work unaltered on the Tilt, but it does.
Hello,
HTC have publied a HOT FIX FOR BLUETOOH
"/12/2007
Bluetooth Hot Fix (for HTC TyTN II)
Dropped calls sometimes occur when Bluetooth is on. If you encountered the same problem, please download this Bluetooth Hot Fix and install it on your device.
Go to htc club an enjoy.
Downloaded it from HTc.cOM
Installation instructions
Follow the instructions below to download and install the hot fix on your device:
Make sure you have Microsoft ActiveSync® installed on your Windows XP PC or Windows Mobile Device Center on your Windows Vista® PC. You can find Microsoft ActiveSync from this link or Windows Mobile Device Center from this link.
Connect and synchronize your device with your PC via Microsoft ActiveSync® or Windows Mobile Device Center using the USB cable.
To download thehot fix, first select the check box below. Next, select thehot fix and the desired FTP site then click Download.
Copy the hot fix, which is a cab file, to your device.
To install the hot fix, tap the cab file and follow the on-screen instructions.
Here is the file:
http://rapidshare.com/files/77588898/TyTNII_BT_Hotfix.zip
Enjoy,
Nadavi
for tytnII, but how about att tilt? is it rom specific?
Hope this will work. Thanks for the tip.
private69 said:
Hello,
HTC have publied a HOT FIX FOR BLUETOOH
"/12/2007
Bluetooth Hot Fix (for HTC TyTN II)
Dropped calls sometimes occur when Bluetooth is on. If you encountered the same problem, please download this Bluetooth Hot Fix and install it on your device.
Go to htc club an enjoy.
Click to expand...
Click to collapse
This does not show up on the updates for my TyTynII (downloads are serial number specific) only in the generic downloads.
I think its best if you only apply this IF you suffer with any Bluetooth problem.
The old adage, 'If it ain't broke, don't fix it!'
Re: does this work on AT&T Tilt?
In the HTC 1.56 ROM, this file is a replacement for \Windows\TIInit_4_2_38.bts a.k.a. (OEM\OEMDrivers\TIInit_4_2_38.bts for chefs). There is nothing else in that cab (see upgrading forums thread for better description)
Edit: I was wondering if I kept quiet, how many people would have experienced a placebo effect and said that it works great and makes bluetooth 10x better on AT&T...
Summary
If you happen to be an AT&T Tilt user that has flashed to an HTC ROM, this fix will work for you. If you're running an AT&T ROM, or you have no idea what a ROM is, but you know your phone says AT&T on it, it does nothing.
Does this fix the issue were bluetooth is dropped after finishing a call ?
Thanks for letting us ATT users know that it doesn't do anything. Guess we don't have this issue But on a serious note does this actually fix anything besides a supposed call dropping? I don't have that issue but of course we all have tons of issues with BT quality.
I have install the update listed above on a Tilt running the RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship Rom and the Bluetooth quality has jumped 100%. My Bluetooth stereo headphones sound great.
Thanks for starting this thread.
Awesome, thanks! I was going to ask if anyone had drop call problems as it happened to me twice last night and I happened to have my BT headset on
sirooga said:
Thanks for letting us ATT users know that it doesn't do anything. Guess we don't have this issue But on a serious note does this actually fix anything besides a supposed call dropping? I don't have that issue but of course we all have tons of issues with BT quality.
Click to expand...
Click to collapse
I have a lot of crackling background on my BT headset. Did not have that on the 8525. Also, there seems to be less functionality supported in the Tilt implementations, regarding the BT, vs the 8525 (I was running a cooked ROM though on my 8525). What i mean by that, is that I was able to use the BT buton to activate the voice dial using the MS VM. In addition, hitting the BT button twice was getting me a redial. Not anymore. I wonder is this has to do with the AT&T ROM or not? Is this a genuine HTC issue?
kaluzu said:
I have a lot of crackling background on my BT headset. Did not have that on the 8525. Also, there seems to be less functionality supported in the Tilt implementations, regarding the BT, vs the 8525 (I was running a cooked ROM though on my 8525). What i mean by that, is that I was able to use the BT buton to activate the voice dial using the MS VM. In addition, hitting the BT button twice was getting me a redial. Not anymore. I wonder is this has to do with the AT&T ROM or not? Is this a genuine HTC issue?
Click to expand...
Click to collapse
Before I switched to Dutty's ROMs, I was running the stock Tilt Rom for a few days, and then the newer Tilt ROM for a week. Both of those AT&T Tilt Stock roms gave me no issues like you mentioned. I heavily use my BT headset (Jawbone), and use Microsoft Voice Command (I very seldom use the dialer as its easier to just speak and have the phone dial for me). Pressing once on my headset would always bring up MS VC so I could issue it commands, and pressing twice on my headset always did a redial.
Now that I'm on Dutty's 7b, I have the same behaviors there too. Not sure what to tell you (other than some BT headsets don't work well with WM6, but if you were using the same headset on your 8525 then thats probably not the case).
As always... YMMV
_Alex_ said:
This file does not exist in the AT&T Tilt ROM, so it's doubtful it will harm or help to install this.
Click to expand...
Click to collapse
I checked the AT&T's 1.60.502.3 rom and it does exist. I didn't check the stock AT&T rom so I don't know if it wasn't there. I did a file comparison with ExamDiff between HTC's fix (22,490 bytes), AT&T's 1.60.502.3 version (22,490 bytes) and HTC's 1.56.405.5 version (23,899 bytes). It appears AT&T's newest rom already has the fix so anyone using the following roms should not have to apply the fix:
AT&T stock 1.60.502.3
Kyphur's XDA Live
Dutty's AT&T Variants
Custel's Series
_Alex_'s 1.60
any of DK's roms (shameless plug)
Is rapidshare the only place to get this? I am behind a firewall.
jgermuga said:
Is rapidshare the only place to get this? I am behind a firewall.
Click to expand...
Click to collapse
Cab fix attached.
akadonny said:
I checked the AT&T's 1.60.502.3 rom and it does exist. I didn't check the stock AT&T rom so I don't know if it wasn't there. I did a file comparison with ExamDiff between HTC's fix (22,490 bytes), AT&T's 1.60.502.3 version (22,490 bytes) and HTC's 1.56.405.5 version (23,899 bytes). It appears AT&T's newest rom already has the fix so anyone using the following roms should not have to apply the fix:
AT&T stock 1.60.502.3
Kyphur's XDA Live
Dutty's AT&T Variants
Custel's Series
_Alex_'s 1.60
any of DK's roms (shameless plug)
Click to expand...
Click to collapse
Just realized this while doing some diffs and was going to repost. (Microsoft file find sux ) Original post edited...
mfrazzz said:
Before I switched to Dutty's ROMs, I was running the stock Tilt Rom for a few days, and then the newer Tilt ROM for a week. Both of those AT&T Tilt Stock roms gave me no issues like you mentioned. I heavily use my BT headset (Jawbone), and use Microsoft Voice Command (I very seldom use the dialer as its easier to just speak and have the phone dial for me). Pressing once on my headset would always bring up MS VC so I could issue it commands, and pressing twice on my headset always did a redial.
Now that I'm on Dutty's 7b, I have the same behaviors there too. Not sure what to tell you (other than some BT headsets don't work well with WM6, but if you were using the same headset on your 8525 then thats probably not the case).
As always... YMMV
Click to expand...
Click to collapse
Give this a read. I have MS VC 1.6 working just fine on my Jabra BT250 after following the instructions.
you can ignore the first part about removeing the cybertron dialer or whatever.
http://forum.xda-developers.com/showpost.php?p=998205&postcount=9
I'll try it. Thx for the tip. I am not sure if this only works for 8525/TyTn (I do have the TyTn II/Kaiser)
Edit:
Tried. Sorry, did not work. Oh well. will see, but for now I wil stick with the AT&T ROM.
Hi,
there is something weird about that fix:
when the cab is on the kaiser, you tap on the file to install it.
you believe it's installed but in program files , you may find
a "kai6492_hotfix" shortcut, you tap on it and the choices are install or exit
it's seems there an identity check to be sure it's on a kaiser
"module id is kais(required kais)"
then if "equal" "ok" then install
and soft reset needed
why two install required ?
the kai6492_hotfix is still in program files after that
and last VC1.6 was working on my bt headset(but the voice recognition succeded about only 10%,i think because of audio quality when i am speaking) but i could ear vc1.6 replies ou questions)
now it is not working anymore.
when i click on the button(headset) before it was launching voice command as the harware button (assigned to it) could do it
now the same button launches the phone dialer(as i was tapping on "call"(green phone)).
ps; since that hotfix, i haven't been able, any more, to install btIO-0.6-wm5 cab
Deleted cause not worth it....
I was amazed that I couldn't really find anthing related to MS VoiceCommand by searching, so here goes... (maybe i just suck at searching?)
I installed VC on my Tilt and it works great except that I can barely hear the voice prompts on my hands free. They are there, but very very faint. I know i saw somewhere about a bug where the prompts play through the phone instead of the handsfree, but mine are definately coming through the handsfree, just so quiet that it's basically useless. I tried selecting the option for the prompts to play through the phone but they still play faintly through the handsfree. Anyone have a solution for this?
If this has been covered then i appologize, but i searched "voicecommand" "voice command" and "voice command prompts" with little to no results.
Thanks
VC & Tilt
Aight, I've read through various post & replies, have not found one to match my problem either. I have a new AT&T Tilt, just upgraded from AT&T 8525, before that an AT&T 8125. Both, prior phones I had no problems w/ VC (1.5). Tried installing VC on to the Tilt (8925) and I get the "VC has encountered a problem restart VC & try again" message. Tried restarting, reinstalling same message. Can anyone shine light, please?
@YettaVR6 - You may be experiencing a bluetooth issue rather than a VC issue...try this page
http://forum.xda-developers.com/showthread.php?t=329270
If that doesn't work, search using google (link in my sig) and search for VC, BT, volume, fix. Try mixing the search terms and including more than one at a time separated by spaces. Also include kaiser to limit results to (mostly) kaiser links.
@nbcsubz - Nothing will get you flamed quicker than cross-posting...
I think you'll have to upgrade to 1.6 to get it to work with WM6. I have 1.6 and it works great on my Tilt with a stock ROM. You do have to move the Cyberon Voice Dialer app that is included 'out of the way' but it's easy and the instructions are here
Hello there dear XDA crew. All glories to you, our great comunity, and so, so...
I wanted to make a thread in here, that will bring all our experiences with VOIP on our beloved TRINITY. I just got the divice for this particular reason, and i cannon make it run Smooth and silky.
I read so many thread, dot find the best solution. Is it existing? Is it possible to use our Trinitys for nice VOIP calling with no problems...
I have seen few users fighting with this subject also, so please lets share our experience.
1. How to make a voip run smoothly?
2. What providers do u use, and u think the quality is the best?
Thanx a lot, and i hope someone could help to use my beloved Trinity with Voip.
Greets.
Aleph
Hello...
Does nobody uses VOIP on Trinity? Or maybe everything is explained allready in different places in the forum i just couldn`t find it.
What is the actual state of VOIP on trinity?
Can we make phone calls with the sound from the front speaker?
Please anyone who is using VOIP with Trinity, please share with me the info...
How to configure the Trinity, so Voip works fine with native dialer...
Is it possible? It should be.... That was the reason for me to buy the Trinity, so please help me can i make it running, or i should look for some other hardware, like Nokia N95, where Voip works so nice...
But i love my trinity though, and i want her sing form me the Voip serenade.
Plz, plz, plz - anyone can guide me in this VOIP world on Trin100?
Excuse maybe i am completely stupid and i do not know, that everything is working properly now.
Please do not ignore me, let someone who uses voip share with me his experience.
Thank you very much.
The wm6 standard voip will only output via speakerphone. If you want a good voip software that will output voip via the correct internal speaker, get AgePhone Mobile. Very good software.
chavonbravo said:
The wm6 standard voip will only output via speakerphone. If you want a good voip software that will output voip via the correct internal speaker, get AgePhone Mobile. Very good software.
Click to expand...
Click to collapse
Hmmmm. Do not believe in that so much. Maybe 1 year ago, but we are almost in 2009.
I am able to get the connections, via wifi, also via 3g. The sound comes from front speaker, but the sound quality is not so good, so i am looking for the solutions, how to make it the best. I download few cabs, but read many about some REGISTRY TWEAKS, which i do not know how to do...
BTW. I have tried AgePhone. It is not so very good as many of you say inside the threads about VOIP. Maybe you want to get customer for the 35$ product which is not so good.
Internal VOIP in WM6 should be possible now.
Please, anyone who really know about this subject, please give some input...
THX.
PS. Also about the providers, which you find that you have the best connections, and sound quality...
aleph01 said:
The sound comes from front speaker, but the sound quality is not so good, so i am looking for the solutions, how to make it the best.
Click to expand...
Click to collapse
oh, no.
today i have realised, that the sound comes from the back speaker, i was just thinking it is normal one...
so is this is true?
we cannot use voip on the normal phone speaker in WM6 in general? Or this is the issue of the trinity?
is this AEG is the really only sollution? should i invest and get this one?
and how it is possible that it is working in AEGphone and not working in WM6 native dialer? can anyone explain me that?
Damn. Will i get any answers here from you guys. Any clue? Maybe some link like:
-- hey stupid dummy here is everything written about that issue.
thx
No need to curse. If you;d spent the time you took to post several angry messages that noone is helping to search the forum instead, you would have found this topic:
http://forum.xda-developers.com/showthread.php?t=401608
This is the best you can get with WM6 native SIP stack, some people report they were able to use the regular speaker, but it's not always the case.
Well, thank you very much. I spent some time, i have found several threads, could not figure it out the final solution. I was looking around trinity field. Thank you for your help and time, that what i was waiting for. I will check that thred you linked me with. Once again thx a lot and sorry for noobizm and laziness.