Related
Hello everyone,
I have generated this post to get some feedback from those of you who may have upgraded your BAs from WM2003SE to WM5.0. I have been following all the updates rather close. All I can say is that Mamaich and Tuatara are 2 absolute heroes in my book. The latest (for those of you who are not sure of what verison of the rom is out there) TuMa v1.3 seems to be the cream of the crop at this point.
Anywho, what I would like to get from this post is feedback on the following (all of these are to be compared to WM2003SE, so keep that in mind when replying):
*Speed of the device
*Overall stability
*Issues (other than the infamous BT disconnect). BTW, we are counting on you for this, Mamaich and Tuatara. 8)
Keep in mind that I want to try to get a good comparison between the OS's. Please remember that the point is to inform people who, very much like myself, does not know squat about programming, but has some knowledge about certain things and want to upgrade to WM5 just because he/she can Personally, my SX66 works like an absolute charm with WM2003SE, but I am really curious as of the new capabilities of WM5 (and at the same time, I do not want to turn it into a brick with a sliding keyboard--- :? . --- --- --- R.I.P. MPx200 (after attempting to upgrade to WM5)
Anyway, any feedback on this will be greatly appreciated.
Thanks guys and may xda-developers live forever!!!!
Personally, I can't see many extra features of WM5 for what I use it for. The only difference for me in all honesty is the fact WM2003 is so ugly when you've used WM5.
Bluetooth is worse, not just the d/c problems but not as feature-full as yet. I miss being able to browse peoples devices etc.
The device becomes really lagged when you use Wi-fi and Media Player
Media Player has trouble with MP3's (not actually tested with wma) for the first minute or so while it buffers.
However, saying all this, I wouldn't go back. Despite WM2003's profound ugliness, the recent TuMa 1.3 works a treat and really feels secure, even securer than I felt with WM2003. The speed is excellent too, except when using Wi-Fi or using Media Player. TuMa 1.3 is also reeeaally easy to patch to your operator, all you need to do is open a command window (Start > Run > type cmd > navigate to the folder > then SetOperator <type your operator value next to it>.
Quite frankly, if you are even slightly eager to try it, you still wont really feel content until you do despite matter what we say. Just go out and try it and you shant want to go back!
Hope this helps!
Leo
now WM5 pack3.1 is very fast,i like it
My opinion is that the Bluengel gets very slow with WM5.. I'm considering to go back to WM2003 again...
My opinion is that the Bluengel gets very slow with WM5.. I'm considering to go back to WM2003 again...
is the keyboard repeating issue resolved?
alex_zou said:
now WM5 pack3.1 is very fast,i like it
Click to expand...
Click to collapse
what pack 3.1????
I guess he meant v1.3. He just got it backwards, By the way, thank you all for the good feedback. Keep it coming though!!!
Hi,
The V1.3 rom is good and it's quite fast but I have had too many problems with the phone side to keep using it. These are the problems that I've peronally had which Have Forced me to go back to 2003:
1) Recieving phone calls. When some calls me it goes through to the voice mail but if they hang up and call me again it comes through.
2) Making phone calls. When I dial someone the call is immeadtly ended then I dial again and it take about 20-30s for the call to be dial and then it end the call after 1 min
3) When i run an application and close it the running tasks tells me it's still running.
These all seem to specific to my device as there are mayeb 1/2 other people with these problems(phone), one of whom has also gone back to 2003.
Just my 2 pence worth.
Thanks
satpal
I agree WM5 is cuttier and more steady. As of the new TuMa 1.3 upgrade, I've never seen my device so glad to run a ROM yet
IT'S REally feature-packed, even when I won't use all of the features. It felt very strong, stable and FAST!! (I don't notice the slowliness some others say, moreover it feels faster than with 2003), more than any other ROM I've tried to date. WOW WHAT A JOB!!
I'm having a problem with the phone where I can not get any sounds from the phone making, nor receiving calls. I can not hear or be heard using the loudspeaker. Using the Bluetooth headphone works, though. But, bluetooth is sooo weeak on this device (my impression) that for me is not really worth it. I was using a Nokia phone (80something) and the Bluetooth stack felts very strong and stable and, at the very least, you could hear the sound clearly, without the scratchs and noises I'm used to sort in a bluetooth conversation using my BA.
That's why I revert my BA to WM2003, to check if the problem was because of WM5 but, now, the problem persists, and I don't have so many other options...
Just a thought: if you wanna better Bluetooth thingie, don't go WM5: M$ stack is a crap... lacks everything...
it's definitelly worth trying... I like the usability and keyboard navigarion better... in 2k3, it is impossible to even close a simple gprs popup without touching screen where as in wm5 you can simply press right arrow key and enter to close it... there are plenty of small things which make it more usable for day to day usage
plus It gives you the courage to upgrade to a more steadier device with wm5 pre installed... like I bought universal after using BA for couple months
[edit] the WM5 version I tested was 1.3 TuMa.
My QTEK 9090 really didn't like WM5.
I love the look and feel, and particularly the MSN integration, but had to go back to 2003SE.
Do tell me if I missed anything that would fix the issues below and allow me to go back to WM5 :-
1 - SLOOOW. Some apps more than others, for example reading an SMS takes 5-6 seconds to open a 30 character message.
2 - Phone. Keypad very slow. Audio cuts out halfway through a call, seemingly at random.
The second point is what forced me to downgrade. If my smartphone is not a phone, then it's no use to me.
The last test I did with WM5 was using the 1.13 radio ROM. I've since updated it to 1.15. Has anyone seen any WM5 improvement with higher radio versions on PH20B hardware? I ask because I've been through the reflashing process so many times, I realise I am pushing my luck and will end up with a brick sooner or later.
I am trying to decide if this nuisance is tolerable enough in order to enjoy bluetooth stereo on my Plantronics 590s.
Regardless of ROM: all of Cingular's w/ A2DP CAB add-on or
any of Summiter's with A2DP included..... I am having to re-align my screen almost daily. If I leave off the A2DP add-on CAB using any of the Cingular ROMs I can't remember ever having to re-align!
Does Summiter use the CAB which I believe is named zoki's or A2DP.hack? I have installed both and even though they appear to be the same size...same file I have background hiss with one, but not the other???
Am I being too anal?
i have the same problem and can agree that it is a PITA! It makes me at times want to get rid of the phone.
I had this same problem and dealt with it for several months... I finally upgraded to the newest factory 8125 rom, and checked to see if the screen would come out of alignment again before installing ANY programs.... it did... I had to RMA my phone as Cingular and HTC did not have any knowns on this issue... I received my refurbed phone over a month ago now and the problem has completely disappeared... I have tons of programs (including A2DP add-on) on the phone again, and I have NEVER had to realign since... it feels like a brand new phone again... sounds like you will have to RMA your phone...sorry, but it's defintely worth it....
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.
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
HI all,
I have setup MS Voice command on my Fuze to announce the name or phone number of the person calling on in coming calls. On my Tilt, it would announce the name either thru the speaker or my BT headset. With the Fuze, it will not. Is anyone else having this problem.
Also, with my Tilt, my ring tones would play thru my BT Headset and it will not on the Fuze. I don't know if this are related. I am using the BT headset on both.
Thanks
billf.
Yes, I'm having this same problem, and it is making me consider returning my Fuze and sticking with my tilt. Unless HTC or someone comes up with a fix within the next 2 weeks, my Fuze is going back. The only other bug I have noticed is that auto-correct does NOT work for the keyboard. It's supposed to automatically add in apostrophes for words, such as "can't, don't, won't" etc. Also, the word suggestion never shows up when I type, like it did on my Tilt. Of course it gives you suggestions with T9 turned on, but that's not the same as word suggestion. It would provide suggestions based on previous typing habits, and even predict entire phrases it thought I was going to type. Anyway....if someone figures out how to fix these problems, please let me know ASAP! Thanks.
I just noticed this tread. I too am having the same problem with it not announcing. My Tilt did it just fine and I have the Fuze VC set up exactly the same way as my Tilt, but all I get is my ringtone and no announcement.
Check your settings. I think you have to announce notifications using bluetooth hands free if available. and uncheck "only durning free time"
I think that may work.
starstreak said:
Check your settings. I think you have to announce notifications using bluetooth hands free if available. and uncheck "only durning free time"
I think that may work.
Click to expand...
Click to collapse
That is the way I have it set up. No go. What is weird is that my ring tone plays over the bluetooth headset, but the computer generated voice doesn't speak.
it has to be a bad version or something.
also..last night i tried to install the cab i've used for over a year on top of the at&t version thinking it would overwrite the necessary files. no go. it corrupted the phone and had to hard reset to fix.
venelar said:
it has to be a bad version or something.
also..last night i tried to install the cab i've used for over a year on top of the at&t version thinking it would overwrite the necessary files. no go. it corrupted the phone and had to hard reset to fix.
Click to expand...
Click to collapse
I'm glad that you decided to be a "guinea pig!" Because I was going to try this today! I was going to re-install the .CAB that came from my Tilt. But I'm glad to see if that doesn't work. In order to find a solution, do you think I should call AT&T or HTC? Which one would give me the solution? Because I only have 25 days left before my Fuze is non-returnable.
Hmm I never tried it yet on the fuze with my BT. I'll try it and report back.
Ok crap. Yeah. It doesnt "voice" announce. I never noticed it because I can dial from headset and even number dial from headset and it'll work. I can hear it repeating the number back.
BUT its not like its not working... If I remove the announce incommming calls, it makes my phone ring, but in my earpiece I hear a tone to tell me I have a phonecall. When I enable announce incomming calls, my phone vibrates and I hear my ringtone in my ear, and faintly I can hear that "tone" I heard before. So it sounds like the voice side of things isnt working.
Ok tried one last thing before my BT headset died. Doh!
When it died, my phone announced the caller. So it does work. Its just not working from the BT headset, you hear a bell sound or something.
Also, I just noticed my cars BT doesn't show battery of the phone. When my Tilt was on the car BT, it would show the battery remaining.
MS Voice Command
Check out the MS Voice Command guide on WinMo-Experts. There might be an answer to your problems in there.
http://www.winmo-experts.com/viewtopic.php?f=11&t=2
Thanks for the link. I dont think it solved anything we're getting. Since Fuze has it built in, I dont think we can overwrite the files.
starstreak said:
Thanks for the link. I dont think it solved anything we're getting. Since Fuze has it built in, I dont think we can overwrite the files.
Click to expand...
Click to collapse
Guess I didn't notice, but dose not work for me either. I do enjoy that on the Tilt, but I more like the Tilt for the message and email voice notification.
Beahcboyde/JON
PS. I'm simply not keeping the Fuze. I'll stick with my Tilt and TF2. love the whole setup and the speed of the touchflo usingHyperDragon Raphael
Signal is average compaired to my Tilt, when testing out T-Mobile connection. On 3G, I'm constantly around 2 bars(but it spurts to full so I know its working) So I think Hawaii is still bad with 3G is some areas.
I use VC ALOT. So I'm amazed I never noticed this issue where it wont say the caller in my ear.
I'm not sure if I'll keep the phone/drop ATT/both.
Please someone fix this! I dunno if it helps, but all you hear is a bell sound in the background of your normal phone ringtone. I know thats from the MSVC. The only thing not working is the announcement of whos calling. I think everything else is working. I can voice dial,recieve calender announcements and appoinments,etc from my BT headset.
Oh, not just BT headset. It won't announce it from the phone either.
I even did a "bloat free" installation.
the fix is on pdaphonehome.com i had the same problem with my sprint touch pro. weird since the diamond doesn't have this problem. you have to edit the registry to use the wav file instead of the default. only side effect with the fix is the phone will ring once and VC will announce the rest of the duration.
sid
Eww,junk fix. I'll check it out tho. While not a problem when I have my headset, it would be if i had my phone sitting on a table.
Reg hack
I copied this from pdaphonehome.com....kuddos to the person that figured this
out. Kind of a hacky way to get it to work though. Perhaps the brains around
here can figure it out.
--------------------------------paste-------------------------------
This isn't a complete solution - but it's an improvement.
With this fix - the ring tone will play for a second and then be cut off by the call announcement. The announcement will be at a lower volume. The announcement will repeat - the ring tone will not be played again.
NOTE THAT YOU SHOULD ATTEMPT THIS FIX ONLY IF YOU ARE COMFORTABLE IN UPDATING YOUR REGISTRY.
Change the following registry keys:
HKCU\ControlPanel\Sounds\TTSAnnounce\Category
change from VoiceCommand1 to Ring
HKCU\ControlPanel\Sounds\TTSAnnounce\Script
change from as5p to v0p (that's v-zero-p) - for vibrate & ring, or p (ring only)
The above fix seems to get the announcements reliably, and doesn't break the set vibrate/set ringer features in the TF3D interface.
Hopefully we can find a better solution - that will restore the full functionality of Voice Command incoming call announcements - and not need this hack.
Another option is to manually overwrite the ringtone file name:
HKCU\ControlPanel\Sounds\RingTone0\Sound
change to \Application Data\Volatile\TTSCallerID.wav
This fix replaces the ringtone with the call announcement - and at full volume.
BUT this solution has several problems, including breaking the set vibrate/set ringer feature in TF3D.
From reading that, if I DON'T use the TF3D ring/vibrate, but use the windows mobile one, I should be fine by doing the second hack listed above? I think I could live with that as I eventually will kill the TF3D just so I can get the calender of my Pocket Informant to show instead. Only thing I like was the Weather and clock of the TF3D anyways and ATT crippled the clock by removing the animation.
Doe anybody know how to do the 2nd option? Not sure if I'm supposed to delete the whole registry line or somehow add to that line?