Voice Command 21040 - Announcement Cut Short - Upgrading, Modifying and Unlocking

I have MSVC 21040 running in a 21042 ROM. Out of the "box", the announcements didn't work. I am working on a solution to work around this issue. The only part I am having a hard time with is the length of the announcement itself ... It cuts off after ~3 seconds. My TTSAnnounce ringer script is "v0p". To disable the normal ring, I set the category for RingTone0 to "_Ring" (instead of "Ring"). The nice thing about disabling the normal ringer this way is that it doesn't interfere with the build-in Sounds and Notifications settings interface.
Example: Call from 012-345-6789 gets announced as "Call From 012-345-67"
or
Call from Joe Smith on Mobile is announced as "Call from Joe Smith on m..."
If I change the TTSAnnounce ringer script to "p" (remove the vibrate command), it works fine. If I use "pv0", it still works but no vibrate. Any ideas on how I can get vibrate and call announce? I also tried v1p, v1pr, v0pr, v0pw3r ... Same results as v0p. Also tried an "a" in front. This might be a bug in the OS ... I'll have to play around with some other ring tones and see if they get cut off. Is there a max ringer script duration setting somewhere?

Ok ... Here goes ...
I built a 21042 Titan ROM with PPCKitchen.org's BuildOS, including VoiceCommand. I had to change some registry settings to get it to announce my incoming calls, and these announcements were cut short.
I am 98% done building my own 21042 Titan Kitchen. When I use my kitchen, Voice Command announces the full message, and does not get cut short.
I don't know what the issue was, but it is no longer an issue for me.

Related

Phone ringer is silent!

My phone wont ring though, BIZARRE, this is not to do with the rom though as i think it was happening with schaps, really really strange.
Any ideas, I just get a phone icon where the signal strength bar is showing handset. No callerid flashing up, not even an option to accept the incoming call. I go to phone options and test the ring tone and it plays just fine.
maybe i should reflash the radio, on 1.50 at the mo which i recently flashed to downgrade from 1.51, any ideas?
maybe i miss something totally obvious.
bumppppp? anyone?
same happening to mine on ultra ultra lite re-furbished
i had to flash another rom, then it worked. when i flashed back to same rom it didnt work again. the problem started after i added some cabs and did my regular tweaks. even with the fresh install of the same rom after flashing another rom it still didnt work.. i even changed radios
i'm on ultra lite, and it seems nice. So you saying i should flash another rom then come back to ultra lite?
Ok,
I just reflashed schaps, then flashed ultra lite.
I STILL have this wierd problem, what's going on?
Is my fone knackered? Not much good if it don't ring!
the rom has been discontinued and he is fixing it
known bug.....wait until new relase
shame it's a nice ROM, nice un' quick. fixed yet ?
same here..
I noticed that no sound was coming out of the phone when i did a soft reset and the Schap's Rom boot up with the animation + sound didnt sound. Also my speaker phone does not work. Basically and audible sound does not work!!!! i tried flashing it with dutty's rom, still same problem.. any ideas?
Hope this helps in resolving this issue!
Hi. I've run into this issue myself too. Here's my environment:
Cooked ROM via Pandora's Kitchen 7.1 with 3.61 OS
Using Dutty's Touch Dialer (2G) option in BuildOS
Everything was fine with the ringer for a whole week. I then decided to be a bit adventurous and went to look for a 3g dialer because the Touch one is only 2G. I then settled for Schen's 3G dialer 2.0 and followed his instructions in installing it (install OEMSign2007cert.cab first, then the dialer, which was the one with the dialer directory option). I didn't install any colored background cabs as provided by his package.
When I tested the dialer (outgoing portion), it seemed fine. I couldn't test the 3G option because we don't have 3G here yet. The problem began when I received my first call.
I was able to hear the incoming call beep through my BT headset, but that was the only indicator of an incoming call, in addition to the phone icon above the signal meter in the top bar signifying an incoming phone call. Besides that, there were no other indicator such as a pop-up window showing incoming caller's info, phone ringing, or even the vibrate function. I have my phone set to vibrate and ring with the Ringer-Vision.wma as the default ring tone.
I tested the vibrate and ring setting in the phone configuration panel and both the vibration function and ring tone worked. I tried several configurations such as vibrate only, ring only, etc, in addition to other various ring tones of different format (wma, mid, wav). All resulted in success in the phone configuration panel, but in failure when an incoming call came in.
To test the phone function, I used a land line, a cellular line, and SkypeOut. All three resulted in the same failure observed above.
Given that the only thing changed after that week was the 3G dialer, I proceeded to remove it and reboot. It reverted back to the Touch 2G dialer. When the phone rebooted, I retried the above tests and all resulted in the pop-up dialog with incoming caller information (plus the two softkey functions), vibration function, and the proper ringtone.
With the above results, would it help you guys in further diagnosing and fixing this problem? We are slated to have 3G within the next few months and I would like to be able to use this function.
Thanks!
Edit update: One other thing is that I tested the above both with and without my BT headset on.
Quakie
I do understand what you are talking about how you tested out the ringers in the phone options menu.. but for me any type of sound does not work, i ran tests there no sound, speaker phone does not work, MP3 do not sound. The sound only works through a head set. And when im on a call i could hear the other person and vise versa. So the problem is the speaker just went out after a couple of days of having Schap's rom. I tired flashing another rom a couple of days after. No luck. Any ideas?
-thanks

Garmin Nuvi 360 - As Bluetooth Car Kit

Originaly posted this in the Nike Accessory section, but this device has worked on a couple of my phones so I thought it would be great to post here a well. I decided to write this post after testing for two weeks to make sure my excitement has held up to the initial expectations and to see if any woes present itself. So far I stand by my initial comment; this is the best Windows Mobile accessory I have found to date.
I originally bought this device as a GPS for my car and thought the bluetooth capability would be an added bonus. The handsfree capability of this device is by far the most impressive use of bluetooth I have seen. I have only tested this on the HTC Touch Dual 20 Key (Nike), compatibility and functionality may vary for other devices. So far no real problems; it connects, it works as stated and quite well too.
Highlighted capbilites in order of importance/functionality (to me):
(see screen shots for examples)
Handsfree Bluetooth carkit
Phonebook retrieval with Spell/Search Function
(dynamicaly uses phone address book not programed GPS contacts)
On Screen Dailer/Phone Pad.
Incoming Call Notification (image shows number but also displays name)
Call History (From phone, not GPS)
Phone Status (Signal/Battery)
Loud Speaker
Great Mic w/External Mic hookup
Voice Comand/Dail Compatible
General use description - Use images below for reference:
Device connects within 6-20 seconds after initial GPS bootup(about 20 seconds)
When calls come in there is an easy to use screen with Answer or Ignore option.
To make calls goto the main screen, press phone icon and select either phonebook where you can spell name and it will narrow down, or you can voice dail or use your call records or look up Point of interest and select dail from the results.
Call options let you pull up the dailer, mute the phone or transfer audio back to the phone while you are in a call. You can navigate while in a call, press the red call status button in the map mode to to see the status or end a call quickly.
I have so much more to tell you about but I will leave with this and for anybody to ask questions.
Like everything in the world there are always flaws or downsides. Here are a few (not necisarily flaws but fixes that would have made it better)
I listed voice dail last because the use is great but the audio feedback/voice prompt is quiet and I felt was least usefull in comparison to the other features. (using MS Voice Command 1.6) Voice recognition works great with the Nike but it requres a few key presses to initiate through the on screen buttons.
This GPS can send and receive text messages and read incoming aloud but this feature is not compatible with this phone. Maybe we could fix this another time friends!
Slow Device Bootup (20 secs), but fast paring most times after bootup. I have this device permanetly mounted and the slow boot doesnt bother me ever; its rare when I get a call before I can even pull out of the garage but If I do it will connect within seconds.
Thats all for now but if your interested this device retailed for about 600usd, I got mine on clearance for about 350usd.
Have a good one
jcostanza4
Thanks !!!
jcostanza4 said:
[*]I listed voice dail last because the use is great but the audio feedback/voice prompt is quiet and I felt was least usefull in comparison to the other features. (using MS Voice Command 1.6) Voice recognition works great with the Nike but it requres a few key presses to initiate through the on screen buttons.
Click to expand...
Click to collapse
How do you get Voice Command 1.6 to respond? I have a Nuvi 680 and Tilt but nothing happens when I press Voice Dial.

8525, Voice Command 1.6 and HTC WM6 ROM upgrade.

Hi.
I have spent months trying replacement VC files and cabs in hope to get consistant Call notifications to various BT ear pieces with no resolution.
Has anyone been able to enable VCs call announcements to reach any BT ear piece.
THX.
Do you mean that your ear piece tells you when a call is coming in? If so I use the Voicecommand cab that's in the add ons for vp36's ROM: http://forum.xda-developers.com/showthread.php?t=334946&highlight=vp3G.
I also use the little Jabra ear piece: http://www.jabra.com/Sites/Jabra/NA-US/products/Pages/JabraBT8040.aspx
I can initiate Voice Command with it and the ear piece tells me when calls are coming in.
If you are expecting VoiceCommand to tell you the name of who is calling in that you recorded, I don't think it actually does that.
Just read the specs for 1.6 and it looks like it does include what you want. We'll see if we can find a cab for it. If you find it post the link here and I will do the same.
The bottom line is this..You need a headset with the AD2P profile like the one linked above. You also need to install the .cab linked and enable it once installed.
I use the Jabra BT8010 myself..If you don't have a headset with AD2P its not gonna happen so no need to go further.
Now if you have all this like I do then yes notifications with come through the headset. If you want incoming calls announced then goto Start/Settings/Voice Command then highlight phone and click options...check off 'Announce incoming calls' then press ok.
So when I'm driving in my car I can tell if I got a email or txt msg just by the tone I have set for each. If I turn on announce calls then it will say what I have in my contacts.

MS voice command problems

when im at work i use MSVC alot to make calls, its great in that way since i dont have to mess my phone up with dirty hands and stuff "hiker at hertz car rental" but when i use handsfree with the application and i receive a call i can only hear the ringtone for maximum a second, then it stops because the MSVC notification system tells me who is calling, what i can see this function cant be fully dissabled on the phone? anyone that have any tips or similar application but the option to completely dissable incoming calls notification?
Regards /Daniel
In Settings -> Voice Command, highlight phone, and press the options button. There should be an announce incoming option that you can uncheck. Is that what you're looking for?
i found a thread somewhere yesterday, but i dont have all those optiops that where written there either? anyone have a working cab for my X1?
BUMP
as i said, i cant find all the notification options in my version of MSVC, anyone have another cab file that i can try, this problem is rally annoying

YABtI - Yet Another Bluetooth Issue

After getting my US TMo TP2 last month I've been pretty sure everything Bt was working properly.
Giving commands is 100%, I can touch the call button on my Moto S9's and say Dial <contact>, or Dial <555-1212> or What are my appointments tommorrow?, etc. and it works great.
I thought notifications were working as well. Calender appt. announced via my S9's and the text to speech was impressive as it read them out to me but something was missing and I just realized what it was. Incoming phone calls were not being announced properly. I did hear it ring and I could press the headset button and take the call just fine but it was the default S9 ring not my ringtone and I did not hear VC announce the number or contact. I was having to look at the phone to see who was calling.
So I went searching XDA and found this post that has just about everything you need to know about MS VC. After reading thru it thoroughly and trying many of the settings and reg tweaks I found out how to make VC announce incoming calls but it will only do so thru the device speaker an not thru Bt Handsfree. I've tried everything in that post that might help but to no avail.
Any one here have any idea?
S
Microsoft are working on it apparently.

Categories

Resources