Related
Howdy,
In about a week (assuming that G.W.B. can resist starting WWIII for that long), I'm going to build another ROM. This time I'd like to get some input on what to include.
A few things to keep in mind:
1) The goal is to include apps and hacks that appeal to the widest audience and are useful. If it's something that's not useful to a lot of people, then there's no reason to put it into a ROM. I can add more themes and ringers as well, but they should appeal to as broad a group as possible.
2) I won't include any commercial apps. Not even in an unregistered state. I might consider things that have been extracted from other ROMs, but I'm debating that with the voices in my head and will decide later.
3) Apps should be mature, not beta, if possible. I don't want to have to rebuild the ROM every time a new beta version of an app comes out.
4) If possible, attach registry hacks in the form of .reg files to your request. Or at least post the registry entry in you message.
5) It would we swell if someone could take the lead on tallying up the suggestions and help to prioritize. I'll shoot for building the ROM in about 10 days.
If we can keep the additions under 5 Megs total I think we'll be OK.
Here's what will be in there as of now (which is in the current custom ROMs)
-Oregami themes
-digital, cellular, and electronic ringers
-.NET Compact Framework 2
-A2DP/AVRCP
-Wireless Today screen plugin
-enable multi-select/delete contacts
-a hidden treasure map providing the precise pinpoint location of $2.33 in pennies that I previously buried when I was perhaps 7 or 8
First I want to say thinks for the bang up job you have done on putting together these roms for us.
The only things that I would like to see that I can think of would be the registery hack that makes GPRS/EDGE stay on all the time. And I would also like, if it is possible, anything that would make the phone us a WiFi connection, when present and turned on, instead of GPRS/EDGE.
I am not sure if it is possible to do that or not.
Usefull apps
Well I would like to have these applications in the next ROM
1) Smartkeys - http://forum.xda-developers.com/viewtopic.php?t=41060&highlight=smartkeys
2) Wakeapp - to easily setup OmapClock and other event-driven applications. http://www.kent7.com/holly/wakeapp/ , download EN version at http://kent7.sakura.ne.jp/holly/wakeapp/wa_arm021_e.zip
3) SMSDeliveryFix - to show SMS recipient name in a delivery report - http://forum.xda-developers.com/viewtopic.php?t=42696&highlight=sms+delivery+fix
4) WM5NewMenu - similiar to WM2003 "New" button - http://forum.xda-developers.com/viewtopic.php?t=40088&highlight=wm5newmenu
5) WM5torage - PDA acting as a memory card reader without ActiveSync - http://www.modaco.com/WM5torage-t238545.html
6) Some software for sending and receiving vCard via SMS.
Thank you for the great effort :wink:
The correct E or G icon
Caps, Num, lock indicators
ability to set OMPA and forget it.
smaller scroll bars
the three reptile themes at this site, I think everyone would like these, grey, blue, and red.
http://www.zombienexus.net/portal/GL_SubDirectory.asp?SEC=3&CatID=70
TCPMP-media player
Total Commander-file explorer/reg editor
Agile Messenger-great messaging app aol,msn,icq etc.
I think these are good apps that everyone could use.
the only thing i think would be beneficial would be adding all the reg edits that reg wiz adds to speed up our device, so we don't have to do it each time we clear storage. THAT would be awesome. i could care less about apps being included, i can install them just fine; but it's a pain in the ass every time i clear storage/flash new rom, that i have to redo all the reg tweaks.
I haven't found a way, but more emphesis on Storage Memory than Program memory would be good for me. I use alot of storage memory with Contacts, Email (even with moving my attachments to storage) and Calendar databases.
I used the much cleaner 2.17 RUU rom without the ringtones but did copy over a couple of them from the 2.17 with RT and OC. Also copied the OMAP clock and it's shortcuts.
A clean Rom without much of the extras would be good.
I also have customized my Cingular connection to use isp.cingular and [email protected] instead of the built in wap.cingular and [email protected] connection. I also turned of the proxy as it was interfeering with my AKU2 push from my Exch2K3-SP2 box.
Is there anyway to use the EXT ROM or add a slider bar like in WM2003SE?
J-Man5
p.s. thanks for the ROMs. I just got my 8125 about 2 weeks ago and have been having mucho grande fun with it.
ROM additions
How about:
- Total Commander
- ?? some sort of free registry editor (PHM RegEdit?)
- smartskey, I agree, but I think it's ini file needs to be in the same directory and it's small so this may not work
- RegWizard (the xda developer forum developed list of hacks), although actually i don't think this is necessary because it along with its framework requires over a meg, and you can just delete it once you install the desired reg hacks. . .
- Magic Button or some other similar task manager thing
I don't think more themes or ringers would be uniformly useful.
jason
Can you add something to truly shut down apps?
I've gotten in the habit of shutting down apps through the running programs tab under memory. Is there any way to make this easier such as putting a direct link in the Start menu to this page or on the Today list.
You know, summiter, you could just fix it so that the programs actually close when you hit the X.
Re: Can you add something to truly shut down apps?
sbuff said:
I've gotten in the habit of shutting down apps through the running programs tab under memory. Is there any way to make this easier such as putting a direct link in the Start menu to this page or on the Today list.
You know, summiter, you could just fix it so that the programs actually close when you hit the X.
Click to expand...
Click to collapse
Not unless he is going to rewrite the way Windows Mobile works. Thats a M$ thing. And also why apps such as vBar and Magic Button and InClose exist.
Summiter may be a ROM compiling wizard but lets not lay too many burdens at his feet to fix.
I'm just really happy push email is working.
J-Man5
Suggestions:
TCPMP with plugins http://tcpmp.corecodec.org/about
tGetFile.dll http://tillanosoft.com/ce/tgetfile.html
PocketNotepad http://tillanosoft.com/ce/pnotepad.html
PocketTweak http://tillanosoft.com/ce/ptweak.html
Adobe Reader 2.0 is huge and belongs in ROM. But is it popular enough? http://www.adobe.com/products/acrobat/readstep2_mobile.html#pocketPC
Continued Bluetooth Fixes
I have notice several still having Bluetooth issues with the lack of support; specifically, SSP over bluetooth. This opens up additional application possibilities not available today. I wouild like to run Bluetooth GPS with receivers such as the Holux 236 GPSlim, but the lack of SSP makes this almost impossible.
Just a thought
I'd like to see common registry hacks already applied and perhaps a txt file explaining the ones included with the new ROM. For example, the ones I listed below are from my own notes so when I re-flash I can re-apply them.
Regarding software, I'd almost prefer to see CAB files instead of pre-loaded software. Since CABs disappear once installed, we could make the choice of installing or deleting, and thus possibly save space but also gain the benefit of having them ready-to-install. You could even use different subdirectories for free vs the ones requiring a registration code to help keep the surprise / disappointment factor down (when we find out it costs money). This would also prevent a problem of competing solutions for some who prefer one plugin over another if they both serve a common function.
Along the same lines, I believe registry hacks can be applied via CAB files or maybe even .reg files (or maybe not - I'm still educating myself with all of this). You could stick with what you have for the current ROM but load it up with optional extras which could be deleted if we just didn't want them.
I think what you're doing is great and applaud your efforts!
I just started configuring my 8125 today, these are the hacks I applied so far (after stepping up to your 2.17 ROM):
Enable scrolling in IE with 4-way button
HKLM\SOFTWARE\Microsoft\Internet Explorer\Navigation\4-Way Nav
Change Value from 1 to 0.
____________________
Slide-out Keyboard Status Indicator
\HKCU\ControlPanel\Keybd
Create entry EnableIndicator and assign DWORD value of 1(decimal)
____________________
Increase your 8125 speed
HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\
Change "CacheSize" value from "0" to "4096".
Assign a value of 1 to EnableCache
HKEY_LOCAL_MACHINE\System\StorageManager\Filters\f sreplxfilt\
Assign a value of 4096 to ReplStoreCacheSize
____________________
Disable menu animation – removes menu animation which uses up system resources
HKEY_LOCAL_MACHINE\SYSTEM\GWE\Menu
Change "AniType" from "6" (default) to "0" (disabled).
____________________
Change the width of the vertical scroll bar and the height of the horizontal scroll bar so they take less room on the screen:
HKEY_LOCAL_MACHINE\System\GWE
Change cxVScr to (say) 9 to make vertical scrollbar narrower. Default value is 13
Change cyHScr to (say) 9 to make horizontal scrollbar narrower. Default value is 13
____________________
Enable 802.11g
[HKEY_LOCAL_MACHINE\Comm\TNETWLN1\Parms]
"dot11SupportedRateMaskG"=dword:00000008
"dot11SupportedRateMask"=dword:00000001
TCPMP
TCPMP definitely, I use this more than any other app on pocketpc devices.
I think you should also consider a paired down ROM. One without any Cingular addons that aren't required to make the device work on Cingular. Basically only the ones that set up MMS and the GPRS settings. I'd even leave out the proxy if thats possible.
But in this paired down ROM I'd still include a few extras like some extra themes and ringers.
And I'd put in the two programs I don't think anyone can live without, SmartSkey and TotalCommader.
Thats basically the setup I have now, but I'm wasting space in my extended ROM and other areas because there are things on my device that I can't remove and I'm not using.
azagahl said:
Adobe Reader 2.0 is huge and belongs in ROM. But is it popular enough? http://www.adobe.com/products/acrobat/readstep2_mobile.html#pocketPC
Click to expand...
Click to collapse
Is Adobe reader prefered over the ClearviewPDF Reader that is already in the ROM?
Re: Continued Bluetooth Fixes
jlsenter said:
I have notice several still having Bluetooth issues with the lack of support; specifically, SSP over bluetooth. This opens up additional application possibilities not available today. I wouild like to run Bluetooth GPS with receivers such as the Holux 236 GPSlim, but the lack of SSP makes this almost impossible.
Just a thought
Click to expand...
Click to collapse
I'm not familarwith SSP. Is it a profile? What does it enhance/enable?
Do you know if there are any WM5 devices which have it? (perhaps it can be ripped out and added to the Wiz)
knight4led said:
I think you should also consider a paired down ROM. One without any Cingular addons that aren't required to make the device work on Cingular. Basically only the ones that set up MMS and the GPRS settings. I'd even leave out the proxy if thats possible.
But in this paired down ROM I'd still include a few extras like some extra themes and ringers.
And I'd put in the two programs I don't think anyone can live without, SmartSkey and TotalCommader.
Thats basically the setup I have now, but I'm wasting space in my extended ROM and other areas because there are things on my device that I can't remove and I'm not using.
Click to expand...
Click to collapse
haha this is at least the second message that goes something like: "how about a ROM stripped of everything, but add this and that and oh yeah add this too". I say this in good fun so don't take offense. It just indicates that everyone has quite unique needs.
I will create a barebones ROM as well. But I don't want to have too many ROMs out there because I don't want to have to rebuild them all when something changes.
As far as using the Extended ROM for other purposes..as of now it can't be done. It's locked in some way that prevents effectively using as storage space. (if you try to manipulate it, it becomes corrupted). So the only use for it is to install stuff at first boot.
Well I might as well put in my two cents....but first....Summiter....marry me! I'll tell my wife to divorce me and she can take her nokia phone with her!
-Ok definitely Smartskey in the same folder as Omapclock so smartskey.ini file can tell omapclock to clock me at 216 everytime after soft reset.
-Please take out the stupid SIP keyboard...i'ts useless and can only be used by leprechauns with little fingers.
-A way to easily change splash screens.
-Hide SIM contacts
HKCU\ControlPanel\Phone
new DWORD value named "ShowSim" and set it to 0
1. Disable menu animations to increase performance:
"HKEY_LOCAL_MACHINE \SYSTEM\GWE\Menu"
Change "AniType" from "6" (default) to "0" (disabled).
- Add vibration instead of sound to keypresses in the phonepad for better tactile feedback:
for i = 0 to 9
Give an example for "i" Button:
[HKEY_CURRENT_USER\ControlPanel\Sounds\Dtmf "i"]
1. Rename Standart DWORD parameter "Sound" to "Sound1"
2. Create new String Parameter "Sound"
3. Assign value *vibrate* to this new parameter.
For this there is also a cab file available.
***this is a cool registry tweak
- oh and this is a must have, all these pda phones lack in the phone department...people on the other side of a phone call can barely hear us until you put this registry tweak in.
\\\registry\HKLM\Software\HTC\AUDIOGAIN(x)\
changed RECEIVE_UPLINK_VOLUME and EARPHONE_UPLINK_VOLUME values to CC. after that change, microphone sensitivity got better and didn't receive any more complaints.
Though i wish someone knew a way to improve the sound mic quality during speakerphone.
And there are so many ringtones in your rom summiter...they all sound alike lol. put the You've got mail.wav file for incoming mail, i have it if you want. how bout some funny ringtones or music ringtones instead?
k that's all
Okay, first post.
Summary: Requesting WM5 PIE standalone, Tutorial of how to change user agent for WM6 on (Hopefully) most AT&T Tilts/HTC TyTN IIs.
Full post: On the upside, I figured out how to change the user agent to anything on my AT&T Tilt (Custel series v2.1 ROM). Not sure if it will work for everyone, but I'll put what I did here anyways. On the downside, it didn't help the problem I stayed up all night to figure out how to do it for. @[email protected] In conclusion, I have decided it might be a good idea to use the older version of Pocket Internet Explorer. If anyone has the PIE WM5 (Or earlier?) version standalone, please upload for me. I tried extracting it from my older PPC, but as I am very new to this I have no idea how to get a locked system file out of the windows directory (Keeps telling me the file cannot be copied.) As a sidenote, I'm not sure the WM5 PIE will run on WM6 but I'd like to try it anyways because I'm running out of ideas. x.x
Anyways, now that my request is done, on to the tutorial. There have been quite a few of these user agent changing tutorials all around the net, but none of them really worked straightout for me, so I made my own.
1. Open up HKLM\Security\Policies\Policies in a registry editor
2. Change 00001001 to the value 1, and 00001005 to the value 40
3. Reboot
4. Now, your standard WM6 user agent string should be unlocked and ready to edit. (HKLM\Security\Internet Explorer\User Agent\CustomBase) Just add whatever user agent you want in there and it will show up. I tested it with www.useragentstring.com, so it did indeed work. To revert back to standard user string, just blank the value.
Simple stuff, but it took me all night to get it right.
Cheers,
Vena.
Should this have been in the networking forum instead of the kaiser forum? I think I miscatagorized it. If a mod thinks I'm right about this, and wrong about where I originally put it just go ahead and move it. Sorry for the confusion.
This didn't work for me. I tried your registry settings (the first one was already set to 1), and when going to useragentstring.com, it still shows "Windows CE" and "IEMobile 7.6".
Are the registry values you quote above Binary or Hexadecimal?
Ack. You're right. I tried changing the user string again as a test, and (at least for me) all it did was add the custom string to the beginning. In short, it's sending both the default and custom user agent strings. Back to work, I guess. Must figure out what was different now from the first time I did it. x.x
Note: All those policy keys do are unlock the user agent key. Otherwise you wouldn't be able to change it no matter how hard you try. Those registry entries should be pretty easy to change. If the HKLM/Security/Internet Exporer/User Agent key shows up (If it's already visible, you don't really need to change the keys.), then you did it right. If it doesn't show up, I'll try and look over those keys again as I obviously did something wrong.
As I've stated in a previous thread I'm coming from an HP IPAQ 4150.
If in the IPAQ Tasks module you selected a Category and closed the application, the last selected Category would be stored in the registry. When you reopened the application the last Category would be active.
In the HTC Kaiser (I think all WM6) the Category is not stored and when the application is restarted it always reverts back to All Categories.
Is this a bug or is this how Microsoft wrote the 'upgraded' version.
If there is a way to restore the original Tasks application from PocketPc 2003 I would be very grateful.
Thanks.
im assumming its how they wrote the upgraded version. I doubt they store it in registry. More likely they put the program to "sleep" so it starts faster, i believe this turned out to be undesirable in future windows mobile versions, seeing as RAM is to valuable to waste on programs that arent in use, but in sleep.
This is a repost as requested (original thread was closed because the original author apparently left the site because he felt he was being treated unfairly)... I TAKE NO CREDIT
here is the discussion confirming that
and here
and here is the archive of the original thread
The Definitive Guide to Microsoft Voice Command (MSVC) for the Kaiser/Tilt - 2.0
*** UPDATED 9/16/2008 ***
PLEASE READ THIS FIRST POST (AND ANY REFERENCED SECTIONS) BEFORE ASKING ANY QUESTIONS!
Hello and welcome to the Definitive Guide for Microsoft Voice Command (MSVC) on the Kaiser/Tilt. I hope that this resource is effective in getting MSVC working to a satisfactory level on your device. As you go through this guide, please remember the following:
I am not a programmer or Windows Mobile engineer. I am just a tech-savvy user with an IT background. All the information I have discovered on this product was by reading what was available from all over the web and doing many tests on my own.
I am not affiliated with Microsoft in any way. I have no special insight as to why Microsoft doesn’t offer better support on this product.
I maintain this guide on my own time. Therefore I can only update it and answer questions when I have the time, which will most likely be less and less as time goes on…
THIS GUIDE IS FOR THE HTC KAISER and AT&T TILT! While it is quite possible much of the information in this guide will help you on other devices, I wrote this with the Kaiser/Tilt in mind. This is because I own a Tilt and so that is what I can perform tests on. If you own a device other than the Kaiser/Tilt then by all means read the guide and absorb its information. More likely than not if the answer isn’t in the guide I won’t be able to help with it. Look to a device specific forum for help.
How to post your issues with MSVC:
BEFORE POSTING:
READ THE ENTIRE GUIDE - There is a lot of information here and 85%+ of the time you will find what you need herein.
FOLLOW THE TROUBLESHOOTING SECTION – Make sure you read and re-read the troubleshooting section and try ALL remedies before posting.
If after the above you are still having issues with MSVC on your device, please post your information in the following format to allow myself and other members to easily assist. Please keep in mind all the above information before posting:
ROM: Version of ROM you are using (be specific!)
MSVC Version: Version of MSVC. (You can find this under Start > Settings > Voice Command)
Bluetooth: Your bluetooth headset model
Description: Provide a detailed description of what problem you are having, how to recreate it, as well as what you have attempted to do to remedy it.On to the Guide...!
Documenting Microsoft Voice Command (MSVC) functionality has proved to be a lengthy (and tricky!) proposition. There are many scattered posts out there as to how to install and configure it. I hope to bring as much information as I can to this central location. I will also offer some custom tools to overcome some of the current limitations of MSVC. For information on what MSVC is, or basic information on how to use it, please refer to the official Microsoft site for MSVC here
There are several steps to get MSVC working; generally they fall into the following categories:
Obtaining MSVC (or locating an installed copy)
Installing/Upgrading MSVC
Testing Basic MSVC functionality
Mapping a button to MSVC
Configuring the BT headset
Configuring Incoming Call Announcements
Obtaining MSVC:
Use a ROM with MSVC already installed – This is probably the best way to do it. In many cases if you have ROM with MSVC already installed you hopefully won’t need most of this guide. Official ROMS with MSVC should work out of the box. In addition, most cooks who include MSVC spend some time ensuring that it works. You may still want to refer to the guide to tweak or optimize your MSVC installation.
Purchase a copy of MSVC – If you don’t have a ROM with MSVC installed, you can purchase a copy from various online vendors. Be aware that the retail versions of MSVC currently for sale may not function fully on newer Windows Mobile devices.
Download a copy of MSVC – You can download a copy of MSVC from this guide or another location. The legality of downloading copies of MSVC has been much disputed and more information on that below.
MSVC Versions
RETAIL VERSIONS:
1.5 – There are retails version of MSVC 1.5. These are very outdated, and will not work on Windows Mobile 6.0+ devices. I will not discuss them here
1.6.4622 - Retail localized versions (available in US, UK, and French versions). Should work on WM 6.0 but WITHOUT incoming announcements.
1.6.17913 - Updated retail US version. Should work with some WM 6.0 and 6.1 builds.
EMBEDDED VERSIONS:
1.6.19209 - Embedded WM 6.0 US version, not available for retail. Should work with most WM 6.0 and 6.1 builds. RECOMMENDED FOR 6.0 devices.
1.6.19213 – Updated WM 6.1 US version. Should work with newest 6.1 builds. RECOMMENDED FOR 6.1 devices.
1.6.19214 – Latest WM 6.1 US version. Should work with newest 6.1 builds. RECOMMENDED FOR 6.1 devices.
You will note that the Microsoft has not release a retail version since 1.6.17913. Unfortunately most 6.0 and 6.1 device will not work without at least version 1.6.19209 or newer. This has left the user community in a difficult position: User’s cannot buy a working version, but the legality of obtaining an updated version has been put into question.
With the latest HTC official ROM release for the Kaiser, MSVC is included. Because of this many accept that MSVC is now in the public domain for usage, since anyone can download this ROM. In reality, you should probably be an AT&T customer or own a retail version of MSVC in order to use the newer non-retail versions.
Below are downloadable copies of non-retail MSVC versions below. These CABs were created by packaging the appropriate embedded files and registry entries from the various test and official ROMs that HTC/AT&T has released and that are available for download elsewhere on this forum.
NOTE: I have not been able to find any discernable differences between the functionality of .19209, .19213, and .19214. In fact, I continue to use .19209 because of this. This guide was written with 1.6.19209 in mind.
Download MSVC 1.6.19209
Download MSVC 1.6.19213
Download MSVC 1.6.19214
Notes on Older Versions, Methods, and Hacks
This information is provided for informational purposes only. It is not recommended that you use these older methods, but rather run one of the newer MSVC versions.
Version 1.60.4622 (Localized versions) has been tested to work but WITHOUT incoming announcements (either to phone or BT). To get incoming announcements to work you can replace the voicecmd.exe with the version from 1.6.17913 or 1.6.19209.
The file voicecommandreplacementfiles.zip that is circulating is simply a set of 4 files from version 1.6.17913. Copying these over your current installation in effect upgrades it to that version. There should be no need to apply those files if you are running 1.6.17913 or above.
The older methods of updating the audio gateway and using xcsdm's BTVoiceCommand (the 0.9f hack) do not seem to be valid for the Kaiser. Covering these methods is out of scope of this guide, but you can find more information by searching xda-developers and looking at info for other devices like the Hermes. Check out the section on MSVC here
How to Determine MSVC Version
To determine which version of MSVC is running on a device, do the following:
Go to Start > Settings > Personal Tab > Voice Command
This is the Voice Command settings applet. Open the applet to see the version number you are running.
Installing/Upgrading MSVC
Installing MSVC is as simple as running the CAB to install.
NOTE: Always install MSVC to your device's internal system memory, not to an external storage card.
In general MSVC will be installed in one of two locations:
\Windows – This is common on devices using ROMS with MSVC already built-in.
\Program Files\Voice Command – This is common on devices where MSVC has been installed separately from a .CAB file. Most retail versions will install in this method, as well as the embedded CABs offered for download from this guide. This method is preferred, as it isolates the MSVC files and allows for easier upgrading.
Once MSVC is installed, you should reboot your device and then follow the instructions above for determining MSVC version to see if it installed.
To upgrade MSVC you should first uninstall the old version and reboot before attempting to install the newer version.
Unfortunately, if you have a ROM with MSVC built-in it may impossible to upgrade. This is because ROMs with MSVC built-in have files which cannot be overwritten, as they are burned into the ROM. All of MSVC can be placed in alternate locations except for the Voice Command applet in Settings. This must always be placed in the \Windows directory. As most ROMs place their MSVC files in the \Windows directory, you can attempt to install one of the non-retail versions offered in this guide. This would mean that you would be using the old applet file, and MSVC may function improperly, or not at all. For more information, see the additional information section.
Testing Basic MSVC Functionality
The purpose of this guide is not to walk step-by-step on how to use MSVC, suffice it to say that once you have installed the application, or located your installation, you should be able to use it to a basic degree. To test basic functionality, do the following:
Locate the voicecmd.exe file. This will be in the MSVC installation directory or \Windows. Usually a shortcut is also created in the Startup folder.
Click to run the file (sometimes you may need to click it 2 or three times to initialize).
When launched, you should hear a beep and a microphone icon appear at the top of the screen.
You should now be able to speak into your phone (not BT at this point) and get MSVC to respond. You can try saying “help” and MSVC should respond with some options. You can also try “dial 555-1212” (or some other number) to make sure it begins to dial.
To my knowledge, there are no issues with getting MSVC to work through the local speakers (assuming you are using a version appropriate to your Windows Mobile version). If you can click the “voicecmd” executable in the proper directory, hear the beep, and get the microphone icon to appear then you should be able to speak to MSVC to get it to dial, etc.
Mapping a button to MSVC
We obviously don’t want to have to manually run the voicecmd.exe every time we want to issue a voice command. The easy solution is to map a button.
In most cases you only need to map a button to MVC if you want to launch if from your phone. By this I mean if you only plan on initiating MSVC via your BT headset then you do not necessarily need to do this. However, for purposes of testing, I recommend you map a button and then you can remove the mapping once your BT works.
*In some instances it appears that the Bluetooth headset device may not trigger MSVC if a button is not mapped. If you are having problems initiating MSVC from your headset, I recommend you try and map a button.
Mapping a button to MSVC is as simple as going into Start > Settings > Buttons and changing any button to launch Voice Command.
The challenge is that most peoplewant to keep their buttons how they are and instead remap the PTT button (the one on the top-left side of the phone) to launch MSVC.
If you would like to remap your PTT button to MSVC, do the following:
Download and install on your phone one of the popular registry editors (PHM RegEdit, Resco, etc…).
Goto HKLM\Software\ Microsoft\Shell\Keys
- Add a new key named "40C6"
- Add a new string value under the key called "Name" with a value of "Button 6" (or anything else you may want to call it, like “PTT”)
You can test that this is created properly by going back to Start > Settings > Buttons and you should now see the button listed. Choose to change this button to “Voice Command.”
You have now mapped the button to MSVC! There are two issues however: The first is that this won’t work until after a soft reset. The second is that a soft reset will cause the PTT service to overwrite the change you just did! Therefore, our only option is to remove the PTT service.
To remove the PTT service do the following:
Goto HKLM\Services\PTT
Delete the entire “PTT” Key. (NOTE: You may wish to backup/export this key first with your registry editor.)
Soft-reset your device. You should now be able to launch MSVC from the PTT button!
Remember, if you have another application handling your device’s buttons (like AE Button Plus), you may not need to do any of this. In addition, if you prefer to use a button other than PTT, simply map the button without the above tasks.
Configuring the BT Headset
This is probably one of the more problematic issues that people encounter. Various results have been reported with trying to get your BT headset to launch MSVC. Sometimes it does nothing, other times it redials the last number or, if you’re lucky, it will actually just work!
The key configuration point appears to be a registry key named BTAGExtModule. I believe this stands for: BlueTooth Audio Gateway Extension Module. As its name suggests it is an extension to Bluetooth which controls what application to launch and thus establish an audio gateway between your BT headset and your phone.
NOTE: In some cases this is the critical and only step you need to get MSVC working. On some devices the BTAGExtModule is set to OEMAGW.DLL. Setting it to VCBTHAG.DLL and resetting is all that is need to get MSVC working!
There are several options you can enter here and you may need to do some experimentation. The important thing is that whatever file you enter for the value of the BTAGExtModule must actually exist on your phone! Be sure to use File Explorer and browse to whatever directory you are specifying any make sure the file exits (be sure to turn on “Show All Files in Explorer options!”).
In all my tests, I am using the 1.6.19209 build of MSVC and therefore the proper gateway to use is “vcbthag.dll” (Voice Command Blue Tooth Audio Gateway). This is true of all later versions as well.
For informational purposes, here are all the audio gateways that are known to exist:
VCBTHAG.DLL – This is the audio gateway included in all of the versions of MSVC I have tested. It always appears to work in all my tests and I suggest you use this one.
OEMAGW.DLL – This is the OEM Audio Gateway. I assume it can be customized by the OEM, or rather the OEM renames whatever gateway they want to use to this filename. It may not exist on your phone, or may not do anything at all.
BTAGTEXT.DLL – This is another audio gateway. It may be generic, but I think it may have also been the default in earlier versions of MSVC. I don’t think you should ever need to use this one, but I mention it because I believe it was used in previous solutions.
To check your audio gateway:
Goto HKLM\Software\Microsoft\Bluetooth\AudioGateway
Ensure BTAGExtModule is set to “\Windows\vcbthag.dll” or “\Program Files\Voice Command\vcbthag.dll” (or another location depending on where your MSVC files are located).
SOFT RESET the phone
Wait about 60 seconds after restart to ensure all services are started
You should now be able to use your BT headset to initiate the audio gateway and initialize Voice Command.
Be sure you pair your BT headset with a “hands-free” profile!
Click your BT button and you should hear the MSVC “beep” and see the microphone icon. You should now be able to speak MSVC commands to initialize a call, etc.
TIP: You may want to walk about 10 feet away from your phone to test this. This will make sure that your voice commands are being send through your headset and aren’t just being picked up by your phone microphone. I have not seen this problem recently, although some people have claimed this issue previously.
Configuring Incoming Call Announcments
Incoming call announcements are another major hurdle with MSVC. Even on an otherwise functioning Voice Command, the incoming announcements won’t always function properly. One of three behaviors occurs:
No incoming announcements at all
Incoming announcements come only from the phone, and not from the BT headset.
Incoming announcements work properly…which is of course what we want!
I believe the issues with incoming announcements not working are due to one of two reasons:
An older version of MSVC (pre 1.6.17913) - In actuality, the file voicecmd.exe is solely responsible for incoming announcements. Whether or not they work for you is dependent on your version of that file. See the beginning of this article for information about proper MSVC versions and how to obtain them.
Incorrect MSVC settings – In some cases, MSVC simply isn’t set up properly. This is what I would like to detail here.
To ensure your MSVC is properly set up for incoming announcements, do the following:
Go to Start > Settings > Personal Tab > Voice Command
Ensure “Enabled” is checked (you probably wouldn’t have gotten this far if it wasn’t!).
Scroll down to “Phone” and make sure it is checked.
With “Phone” highlighted click “Options”
Check “Announce Incoming Calls”
Click OK to go back to the main Voice Command screen
Click “Notifications” and set your notification options.
Now place a call to your phone and you should have the incoming call announced. If the number is in your phone book it should speak the name, otherwise it will speak the phone number.
Where the announcement comes from (device speaker BT headset will depend on your Notification options.
Please read the following sections for more information on this!
Important Notes regarding Incoming Announcements
Location of incoming call announcements are a function of the “Notifications” settings in the MSVC applet. There are 3 setting in this dialog:
“Announce notifications using Bluetooth hands free only” - Use this if you want incoming announcement ONLY to come in over your BT headset and not your phone.
“Announce notifications using Bluetooth hands free if available” – Use this if you want incoming announcements to come in over both BT when BT device is available (and BT is on) or on your phone’s speakers (when not using BT).
“Announce notifications through device speaker or wired headset only.” – Use this if you want to have incoming announcements ONLY come through your speakerphone under any circumstances.
ISSUE #1:
Incoming announcements (and ring tone) don't come through BOTH the BT headset AND the speakerphone simultaneously.
The problem here lies in the fact that if you have option #1 or #2 set AND BT is on, announcements/rings will only go to your BT headset. This may be inconvenient if your headset is not in your ear. Here is a summary of what will happen when using option #1 or #2:
If MSVC is DISABLED and BT is DISABLED then an incoming call will ring normally on your phone.
If MSVC is DISABLED and BT is ENABLED then an incoming call will ring normally on the phone AND your BT headset will ring with its built-in ring tone.
If MSVC is ENABLED and BT is DISABLED then an incoming call will ring ONLY on the phone. If incoming announcements are on, these will also play only through the phone.
If MSVC is ENABLED and BT is ENABLED and INCOMING NOTIFICATIONS are ON then an incoming call will announce/ring on ONLY the BT headset. (NOTE: you will actually hear the phone’s ring tone coming through your BT headset along with the incoming notification).
If MSVC is ENABLED and BT is ENABLED and INCOMING NOTIFICATIONS are OFF then an incoming call will ring on both the phone (normal ring) and the BT headset (built-in ring). No announcements will be heard.
SOLUTIONS:
If you aren’t happy with any of the scenarios presented above by choosing notification options #1 and #2 then you have the option to use notification option #3, "Announce notifications through device speaker or wired headset only." Of course this will allow you to hear notifications over the device speaker, but not over BT.
One other option which appears to work, but is not fully tested is to set your phone to also vibrate for calls. It seems from my limited testing that the phone will vibrate even if incoming announcements are directed to the BT headset.
Again, these are not the best of all possible worlds, but there are some other options. For more information, see the next post.
ISSUE #2:
Calls from PRIVATE or UNKNOWN numbers do not seem to always (most of the time) properly announce. In fact, they will cut the ring off when using incoming announcements. As of current, I am not aware of any fix for this. This happens with incoming announcements over the phone AND the BT headset.
This issue seem to be coded into the Voice Command files themselves. When MSVC is enabled it installs some sort of proxy between the phone’s hardware to intercept incoming calls. It does this whether or not you turn on incoming announcements. This IS NOT related to the audio issues. In fact, if you put in a false value for the BTAGExtModule value then you will not be able to initiate MSVC from your BT however all the ringing issues still exist!
SOLUTIONS:
None
Additional Information Regarding MSVC
List of File and Registry Entries for Voice Command
Attached is a .ZIP with 4 files. 2 .REG files (one for 1.6.17913 and one for 1.6.19209) and 2 .CSV files (one for 1.6.17913 and one for 1.6.19209) listing files.
The information for 1.6.17913 is gathered from an official .CAB file and should be everything you would expect if you installed a retail copy of MSVC.
Since there exists no official version of 1.6.19209 I pulled the information from a recent decompiled AT&T 6.1 ROM. Since this is a built-in version of Voice Command, all files would be installed in the \Windows directory (apart from shortcuts in StartUp).
The .CAB for 1.6.19209 that I offer above is actually a conglomeration of these two. It uses all the updated 1.6.19209 files while maintaining a proper directory structure (In this case using Program Files\MS Voice Command instead of dumping everything in \Windows). It also maintains those files that were not present in the ROM's 1.6.19209 files, namely those dealing with WMP skins. I attempted to make it as close as to what an "official" version might look like from Microsoft.
Built-in versions and manual installs
MSVC, like all applications installs files and registry entries onto your device. The problem with using a Stock or Cooked ROM with MSVC pre-installed is that it may not have been installed correctly (with all the correct files or registry entries). Additionally, because pre-installed applications are often embedded in the ROM and you cannot always move or update files with working versions (because ROM files are read-only). Because of this, it may be easiest to use a ROM that doesn’t have MSVC pre-installed. However by modifying files, locations, and registry entries you may be able to get MSVC working.
Because of these limitationsit is necessary to understand a few things about how MSVC files work.
As I have already covered, MSVC files are generally installed in one of two locations:
\Windows
\Program Files\Voice Command
Generally, if you are in the built-in boat, your files will be installed in \Windows
How does MSVC know where to look for your files?
Well, the first thing to know is where and how is MSVC usually initiated:
The answer is one of three ways:
From your \Windows\StartUp folder when WM first boots
When manually launched from the shortcut or a button
When called from the BT audio gateway to receive a voice command
For #1 and #2 you will generally want to ensure that the version of MSVC being launched is the one you want. There will generally be a shortcut to your copy of MSVC (specifically the voicecmd.exe file) that launches the application in the \Windows\StartUp folder. Therefore, if you want to install a different version of this exe (and if you can’t overwrite it and need to install it to a different location) make a NEW shortcut in \Windows\StartUp to launch your new copy.
Once voicecmd.exe is launched it will want to look for the rest of its files. It knows where to look by accessing the registry at this location:
HKLM\Software\Microsoft\Voice Command
The two keys to pay close attention to are:
AppInstallPath and ResourcePath
The value of AppInstallPath should be the full path to the copy of voicecmd.exe that you want to use, for example:
"\Program Files\Voice Command\VoiceCmd.exe"
Or
“\Windows\VoiceCmd.exe”
The value of ResourcePath should be the full path to the directory that the supporting files are stored in, for example:
“\Program Files\Voice Command”
Or
“\Windows”
Changing these two keys, along with the shortcuts should effectively allow you to bypass a built-in version of VC in lieu of file versions that you want to use. If the keys don’t exist in the root of HKLM\Software\Microsoft\Voice Command you can create them as string values.
You will also want to update your BT Audio Gateway so that the proper gateway is launched from your BT headset. Find it at the following location:
HKLM\Software\Microsoft\Bluetooth\AudioGateway
Set BTAGExtModule to the full path to the copy of the audio gateway dll being used, for example:
“\Windows\vcbthag.dll”
Or
“\Program Files\Voice Command\vcbthag.dll”
EXAMPLE:
If I have a built-in version of MSVC with all files in \Windows, and I wanted to update to a different build I would do the following:
Install all files into a new location, e.g. “\Program Files\NewVC”
Update AppInstallPath to “\Program Files\NewVC\VoiceCmd.exe”
Update ResourcePath to “\Program Files\NewVC”
Update BTAGExtModule to “\Program Files\NewVC\vcbthag.dll”
Delete shortcuts that point to “\Windows\VoiceCmd.exe” and create new ones that point to “\Program Files\NewVC\VoiceCmd.exe”
NOTE: The VoiceCommand_PPC.cpl file may pose an issue becuase as a control applet, it always needs to remain in the \Windows directory. If you can't overwrite this file you may still be ok since you should be able to use a copy of VoiceCommand_PPC.cpl that is different from the other file versions.
NOW AVAILABLE - Manual install for 1.6.19209 to help assist in this process. It is available here. Additional instructions enclosed.
How Incoming Announcements Work (Under the Hood)
Incoming Announcements are the function of the voicecmd.exe and the following registry key:
Code:
HKEY_CURRENT_USER\ControlPanel\Sounds\TTSAnnounce
"Script" = "as5p"
"Category" = "VoiceCommand1"
"Sound" = "Application Data\Volatile\TTSCallerID.wav"
When a call comes in and MSVC is enabled it checks itself to see if it should be performing incoming announcements. If it is configured to play announcements it uses the above settings. The “Script” section is similar to the scripts used for normal ring profiles, it basically is telling it to play the file listed in “Sound”
The file in “Sound” is dynamically generated for each call and then played over your ringtone as your announcement.
On versions where Incoming Announcements don’t work (like UK version 1.60.4622.0) the settings are the same, but the voicecmd.exe file does not properly generate the TTSCallerID.wav and thus no announcements are made.
The Private/Unknown caller issue is also related, as voicecmd.exe doesn’t seem to properly generate the file. It actually appears to leave the .wav file open since it doesn’t know how to properly output “private” or “unknown” this locking of the file appears to be why no ringtone plays at all.
This also appears to be why occasionally you will get an announcement of the last caller's ID when you get a Private call. It hasn't properly cleared out the old TTSCallerID.wav and is replaying the last one in queue.
Troubleshooting, Tweaks, and Tips
TROUBLESHOOTING
Remember that an app alone is not responsible for how it functions. Cooked ROMs and 3rd party software can all interfere with the operation of not just another application, but the OS itself. There are quite a few fantastic cooked ROMs out there that incorporate MSVC successfully, and many other individuals are running it. Chances are it can work for you, but you may be forced to try a different ROM.
INSTALLATION/UPGRADING:
Always use a current version of MSVC
Always install to main device memory (no storage card!)
Always remove previous versions first (when possible).
Soft-reset after any install/uninstall of previous versions.
Soft-reset after making any change to files or registy
Always read and re-read this guide to ensure that your problem isn't already listed
APPLICATION HANG/NON-RESPONSIVENESS
Disable and then enable it in Start > Settings > Voice Command
BLUETOOTH:
Delete and re-pair your Bluetooth headset
Try a different bluetooth headset
Ensure it works through the device speakers (without a bluetooth headset)
Talk loudly and clearly
Use a non-A2DP BT headset (or disable A2DP)
If using a car-kit, or another BT device with voice recognition, it may be best to disable MSVC and use the car-kit's built-in voice recognition abilities.
RECOGNITION:
Ensure that you are not using a localized version (for example trying to dial UK formatted numbers with an EU version).
CONFIRMATIONS:
By default, when you say "Call contact" MSVC will speak a confirmation and wait for you to say "Yes/No" or "Correct/Incorrect." Some devices (and older versions of MSVC) will cut off before accepting the confirmation. The only solution is to upgrade and if that doesn't work, turn off confirmations. This will cause the call to initiate immediately after speaking "Call contact." The downside is that you will not have the option to cancel the call via MSVC. However, MSVC will still repeat the name/number back to you so you can cancel it via your BT headset buttons.
ANNOUNCEMENTS:
Please see the appropriate sections on incoming announcements and see my MSVC tools for more information.
BUTTON MAPPING:
If your button mapping stops launching MSVC, try to remap the button to another application, save the changes, then remap back to MSVC.
OTHER:
See Tweaks and Tips for more!
MORE BELOW!
TWEAKS
There aren't too many additional tweaks you can do with MSVC. If you have information on additional tweaks, please advise:
Change Speech Speed - If your friendly MSVC assistanct Michelle is talking too slow or too fast for you, you can change her speed.
Go to HKEY_CURRENT_USER\Software\Microsoft\Speech\Voices
Change the value of "DefaultTTSRate" from between 1 (slowest) and 10 (fastest). Default if 4. I prefer 0 as it is not that slow and makes her a little clearer to understand.
Change MSVC to another voice - Can't be done! At least not any way that has been discovered. The various localized versions (US vs. UK, etc.) use different voices, but part of this configuration appears to be hard-coded into the application.
Change the sounds MSVC uses - Can't be done! The following registry keys exist dealing with sounds for MSVC:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Voice Command\Speech\Earcons]
"SRDirectedEarcon"="SRDirected.wav"
"TimeoutEarcon"="SRAsleep.wav"
"PTTEarcon"="SRAwake.wav"
If you remove or change these values the sounds go away, so they are definitely linked to these keys. But the issue is these files don't exist! So the sounds are apparently built into the program code. I have played around with changing these values to redirect to other sounds with no success.
Change Bluetooth PTT Delay - When you press the button on your BT headset to initiate MSVC two things happen: Your audio gateway opens to pass your voice to the phone AND MSVC initiates on the phone to accept your command. Some BT headsets take a while to establish their audio gateway. Because of this MSVC may open before the audio gateway is established. This can cause your voice to get cut off or decrease your recognition. To increase or decrease the delay from when you push your BT headset to when MSVC "picks up" do the following:
Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Voice Command\Speech
Add/Change a DWORD value "BluetoothPTTDelay"
Add a value in milliseconds (ms) - I believe the default is about 400ms. I'm not sure how high a value it will accept, but I think it maxes out at somewhere between 2-4000 (2-4 seconds). A value of "2000" should be good if you need a longer delay. Alternatively, you can try setting this to 0 if your BT gateway establishes quickly...this may make MSVC pick up quicker.
SOFT RESET!
Change Recognizer Timeout - When the MSVC Microphone appears at the top of your screen, you have 4 seconds to start talking before it closes. If you want to increase or decrease this interval do the following:
Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Voice Command\Speech
Add/Change a DWORD value "SRTimeout"
Add a value in milliseconds (ms) - The default is "4000" (4 seconds). I'm not sure how high a value it will accept, but I have tested it between 0 and 8000. 8000 is an 8 second timeout and 0 causes it to not listen to a word you say!
SOFT RESET!
Change Rejection and Ignore Threshholds - When you speak a voice command, MSVC attempts to understand what you say. It assigns your speech a confidence level based on its interpretation on a scale from 1 to 100. It compares the confidence level to the IgnoreThreshold (default 10). If the confidence level is less than the IgnoreThreshold it discards the command. This would happen if you said something that MSVC doesn't understand at all like "cook me breakfast." It would assign a very low confidence level based on it's matching techniques. It would then most likely discard this and do nothing further. If what you say is somewhat recognizable to MSVC, meaning it is above the IgnoreThreshold it will attempt to interpret it. It will compare the confidence level to the RejectionThreshold (default 36). If the confidence level is less than the RejectionThreshold, but GREATER than the IgnoreThreshold that means that it won't reject you, but it isn't 100% sure. In this case you will be asked to "Try again" or "Please Repeat." Otherwise, if your confidence level is above the RejectionThreshold that means MSVS thinks it understood you and will do its best to interpret your command to one in its set. To change the values of these thresholds to better tune MSVC to your vocal tones, you can modify the following:
Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Voice Command\Speech
Change DWORD value "IgnoreThreshold" or "RejectionThreshold"
Soft-reset
Adjusting Volume of Announcements - There are two values that seem to influence the volume of announcements. They are stored within the following key:
HKCU\Control Panel\Sound Categories\Voice Command1
The values are:
AttenutationCategory
InitVol
There are apparently different default setting based on your device. In general the values are generally around 1-4 for AttenuationCategory and 1-5 for InitVol. Some research shows that setting InitVol to 40 and AttenuationCategory to 1 provide the best results. In my testing I have found the InitVol to do nothing. The AttenuationCategory definitely does something, it seems the lower the number the lower the voice. When set it to 0 the announcements were very faint. Setting it higher made them higher, although I can't say that anything over 4 or 5 got any louder.
In my findings I would say set both of these to 5 (I have read some other posts that lead me to believe setting InitVol over 5 is pointless, in addition, the posts that recommend setting it to 40 don't specify if that is decimal or hex).
Adjusting Incoming announcements while on a call - Incoming announcements will come in if they are enabled...even when you are on a call. The only time they will not is if your time is marked as "busy" in your calendar. See my MSVC tools for ways around this and other announcement issues.
TIPS
Windows Media Player Voice Commands:
Apparently MSVC doesn't properly read ID3v2 tags. If you want it to understand you properly you should use ID3v1. Find out more info here. (courtesy nonsequitir).
Problems using "Dial":
Some people have issues with the "Dial" command in MSVC. This often occurs when trying to dial numbers that are different than the standard dialing system for the country that the version of MSVC supports. The workaround for this would be to create a contact and use the "Call" command instead.
Use the nickname field to improve recognition accuracy:
From Microsoft: "You can name contacts with nicknames such as Home, Mom, or Dentist. After doing this, you can call by simply saying Call Home, etc. If you have a contact that you consistently cannot access, try adding a nick name that looks the way that you might pronounce it."
To add a nickname to a user, edit the contact. Click the arrow to the right of the contact's name to bring down an advanced dialog box that allows you to specify a nickname.
Jawbone 2 Users:
In order to initiate MSVC from this headset, you do not press the talk button. Instead you hold the Noise Assassin button for 2 seconds. (courtesy Mario23)
Additional MSVC Tools - For Incoming Announcment Issues
Microsoft Voice Command Toggle Script
This tool presents my solution to the above issues with incoming announcements coming to both the BT headset and the phone. Others, like myself would prefer MSVC to deliver incoming announcements to the BT headset AND speakerphone simultaneously. The main reason for this is that ideally, we want the announcement coming to our BT, but out BT might not always be in our ear. Therefore it would be nice to for the announcement to come to the phone as well so we don’t miss a call.
Unfortunately, this doesn’t seem possible with the current version of MSVC. But I have written a simple script to give the next best thing.
The basic idea the script uses is this:
When the BT headset is in the ear, Notification option #2 is chosen (“Announce notifications using Bluetooth hands free if available”).
When we want to remove out BT headset, the script quickly toggles to option #3 (“Announce notifications through device speaker or wired headset only.”)
This allows the BT channel to remain in its default state and simply redirects through a toggle of the notification option where you want the announcement to come out. By mapping this script to a button (like PTT) you can quickly toggle your phone when you remove or replace the headset from your ear.
The below file is a .CAB file that will install MortScript onto your phone as well as my MSVC Toggle Script. It will place the script into your Start\Programs\Tools so that you can then map it to a button of your choosing. I will also post the separate .mscr file for those that already have MortScript installed. (Warning: Installing and then removing the CAB file may also remove MortScript).
Basically MortScript is a application that allows the creation of advanced scripts to control the device and applications.
The MSVC Toggle script works in the following way:
When you initiate the MSVC Toggle either by a button or clicking, it first attempts to determine where your MSVC is installed. The application only supports MSVC installations to \Program Files\Voice Command or \Windows. You will get 3 warning buzzes and the application will quit if it is installed elsewhere. (Specifically it is looking for the location of the VoiceCommand_PPC.cpl file, which should almost always be in \Windows).
Once the application is located, the script simply toggles between notification option #2 (BT headset announcements) and #3 (speakerphone announcements).
However, changing the registry key isn’t enough as the changes aren't loaded into MSVC running memory. So, the next thing the script does is reload MSVC settings by opening and closing the MSVC applet. You will see the MSVC applet briefly flash on the screen and then close.
You will then feel a quick vibration to let you know the toggle has completed There will be a short (250ms) vibration when switching to option #2 (BT announcement) and a longer (500ms) vibration when switching to option #3 (Phone announcement).
It’s that simple!
Free/Busy Toggle Script
Another issue with incoming announcements is that they often "announce" at inopportune times, like when you are already on a call, or in a meeting. One way to prevent this is to se the notification option "only during free time". Free/Busy time is normally determined if you have an appointment in your calendar that sets your disposition to Free/Busy. So, if you have a meeting scheduled in your calendar and the time is set to "busy" you won't get announcments if this option is selected. However this is inconvinient to have to go in and create an appointment everytime you want to be marked as "busy". Luckily, I have found a location in the registry which records that information and have used it in the following tool.
FreeBusyToggle Script works like the MSVCToggle Script from above. It installs into the same \Programs\Tools folder and uses MortScript. For easy use you should map it to a key.
When you run the script it will make one short beep indicating your time is set to free, or two short beeps indicating your time has been set to busy.
So, if you are going to be taking calls or in a meeting, press to toggle till you get the two beeps and then your time is set to busy and you won't get announcments. After the meeting, press again and your time will be set back to free.
Not a perfect solution...but That's It!
reserved*************
reserved************
Awesome thank you
Thanks for keeping this alive
Pumpiron579 said:
Thanks for keeping this alive
Click to expand...
Click to collapse
excuse me, but can we give advice/link to Bengalih's formes files???
such as if some one want to flash their rom they should use sashimi afterwards... is such discussion allowed??? and files can't be uploaded? (even to rapidshare, etc???)
sorry but this is the first time I've sen this kind of thing in forum...
yes sometimes noobs and also oldies can be annoying when come to words picking, but just to make someone like him to go is no one intention of course
so does it mean we cant post files uploaded by bengalih or????
so confused here
rajmagi said:
excuse me, but can we give advice/link to Bengalih's formes files???
such as if some one want to flash their rom they should use sashimi afterwards... is such discussion allowed??? and files can't be uploaded? (even to rapidshare, etc???)
sorry but this is the first time I've sen this kind of thing in forum...
yes sometimes noobs and also oldies can be annoying when come to words picking, but just to make someone like him to go is no one intention of course
so does it mean we cant post files uploaded by bengalih or????
so confused here
Click to expand...
Click to collapse
He deleted all his stuff, but i provided a link to the snap shot that google took of it before he did so, if you would like to access it it is at the top of the page.
as for posting his stuff i think that as long as you do not claim it as your own you should be able to post it
if you have anything you would like to add i can put it in the original posts (sorry if i missed anything i was just trying to get it up)
edit: Yes discussion is allowed but he deleted most of his stuff or his forums are closed. This repost was approved by a mod(thats why i can say reposting his stuff should be fine.)
brynwall said:
Awesome thank you
Click to expand...
Click to collapse
Pumpiron579 said:
Thanks for keeping this alive
Click to expand...
Click to collapse
no problem
Refresh, move up list to find.
Version 1.60.4622 (Localized versions) has been tested to work but WITHOUT incoming announcements (either to phone or BT). To get incoming announcements to work you can replace the voicecmd.exe with the version from 1.6.17913 or 1.6.19209.
The file voicecommandreplacementfiles.zip that is circulating is simply a set of 4 files from version 1.6.17913. Copying these over your current installation in effect upgrades it to that version. There should be no need to apply those files if you are running 1.6.17913 or above.
Click to expand...
Click to collapse
But so, is it enough, to copy the new voicecmd.exe over them, or should we need to add the other three files from voicecommandreplacementfiles.zip as well ?
Thanks !
Hi all -- I do not know any of the specifics, and I really don't care, of exactly why bengalih left, but since this thread represents his work, I do not think it inappropriate to provide you a link where you can interact with him directly.
http://www.winmo-experts.com/viewtopic.php?f=11&t=2
Hey,
I checked out all the settings mentioned in the first page ... but the announce voice is not working at all with receiving proceedure (sms, phone called ...etc); however VC is working normally when I give/say a command!
My MSCV v1.6.19971
My Radio version: 1.02.25.19
Any suggestions?
Read subject of email
When I was using msvoice in wm6.0 I could have msvoice anounce the name of sender and the subject of the email. I can't seem to get it to work in wm6.1 with msvoice .209.
Any thoughts?
Omnia2MessagingAppMgr v1.0
Hi Friends,
Got my shiny new OmniaPro B7610 3 days ago. Great phone I must say. But I find the Samsung's own messaging app bit too restrictive for me. Plus, on my WM 6.1 stock ROM, phone hang many times after selecting to add contact from phonebook. On the Internet, i found a few registry entries that can enable the default messaging app, but due to the way Samsung has designed its MMS application, you cannot use MMS functionality if you use the default messaging application.
Now, MMS is not something people use everyday AFAIK. So I decided to write a small utility around the above mentioned registry entries to make this process easy. So, here it is, my app, Omnia2MessagingAppMgr, for all of you. It allows to quickly switch between the two applications without the hassle of digging into registry every time. I've been using this for 1.5 days, and its doing its job fine. But as there is always scope for improvement, your suggestions are welcome.
Since writing to privileged registry areas from .NET CF apps requires signing the app with a digital certificate (paid or the SDK ones) and then install those on the users device, i skipped the process. I instead have used the excellent Task Manager / Registry editor by DotFred available here. I hope he wont have any problem with this, as I am not selling this for monetary gains. But if he has, by any chance, he can contact me in this thread and I will remove this app and recode it.
Cheers!
Nice! I will try it later today
krazy_about_technology said:
Omnia2MessagingAppMgr v1.0
Hi Friends,
Got my shiny new OmniaPro B7610 3 days ago. Great phone I must say. But I find the Samsung's own messaging app bit too restrictive for me. Plus, on my WM 6.1 stock ROM, phone hang many times after selecting to add contact from phonebook. On the Internet, i found a few registry entries that can enable the default messaging app, but due to the way Samsung has designed its MMS application, you cannot use MMS functionality if you use the default messaging application.
Now, MMS is not something people use everyday AFAIK. So I decided to write a small utility around the above mentioned registry entries to make this process easy. So, here it is, my app, Omnia2MessagingAppMgr, for all of you. It allows to quickly switch between the two applications without the hassle of digging into registry every time. I've been using this for 1.5 days, and its doing its job fine. But as there is always scope for improvement, your suggestions are welcome.
Since writing to privileged registry areas from .NET CF apps requires signing the app with a digital certificate (paid or the SDK ones) and then install those on the users device, i skipped the process. I instead have used the excellent Task Manager / Registry editor by DotFred available here. I hope he wont have any problem with this, as I am not selling this for monetary gains. But if he has, by any chance, he can contact me in this thread and I will remove this app and recode it.
Cheers!
Click to expand...
Click to collapse
Thats great....
I can smell new ROMs in this section...
Krazy is active in Samsung....
krazy_about_technology said:
Omnia2MessagingAppMgr v1.0
Hi Friends,
Got my shiny new OmniaPro B7610 3 days ago. Great phone I must say. But I find the Samsung's own messaging app bit too restrictive for me. Plus, on my WM 6.1 stock ROM, phone hang many times after selecting to add contact from phonebook. On the Internet, i found a few registry entries that can enable the default messaging app, but due to the way Samsung has designed its MMS application, you cannot use MMS functionality if you use the default messaging application.
Now, MMS is not something people use everyday AFAIK. So I decided to write a small utility around the above mentioned registry entries to make this process easy. So, here it is, my app, Omnia2MessagingAppMgr, for all of you. It allows to quickly switch between the two applications without the hassle of digging into registry every time. I've been using this for 1.5 days, and its doing its job fine. But as there is always scope for improvement, your suggestions are welcome.
Since writing to privileged registry areas from .NET CF apps requires signing the app with a digital certificate (paid or the SDK ones) and then install those on the users device, i skipped the process. I instead have used the excellent Task Manager / Registry editor by DotFred available here. I hope he wont have any problem with this, as I am not selling this for monetary gains. But if he has, by any chance, he can contact me in this thread and I will remove this app and recode it.
Cheers!
Click to expand...
Click to collapse
I will try it today...
tanx...
hey thanks i alwaysgo tothe registry to do this manually and well i was abou to create the app to do it thanks!
@charly_mx: My pleasure. Actually the registry path is a bit cumbersome as first you need to go and change the value and then kill tmail.exe and restart messaging. This app makes it easy by doing these two tasks. Good for someone who do it in routine.
@all: BTW, I am thinking of adding the functionality to enable default windows contact suggestion and t9 dictionary when the default messaging app is enabled. I'm thinking of giving a checkbox for this. Any views on this guys?
Thanks alot
Hi! Sumit
can you please add some more functionality to ur app for switching the messaging app in omnia
I would like to use quick switch buttons for--
*default settings visible/hide
*disabling samsung dialer
*enable/disable touchviz
*soft reset
Hope you would entertain this request & develop something for us
Thanks
Yeah! Thanx, very useful app, thx a lot!
Well you can always change it manually in win mo...