Related
Anyone "in the know" on what is going on with Microsoft Voice Command?
For those not up to date heres the brief bio:
Microsoft released a rocking WM program that offers true voice recognition on pocketPCs and smartphones. If it didn't come with your carrier's build, it's a $40 upgrade, and well worth it. The latest version is 1.6. Unfortunately, it's been fraught with little issues, mostly related to Bluetooth headset compatibility, but most people still find it indispensable in spite of these challenges. I'm one of those people. The dial by number, and recognition of any name in the address book is invaluable to me, and a "must have" app for my 6800, no matter how badly it works.
The program is at version 1.6, and hasn't been updated in 2 years now.
What's the skinny?
jtg
I agree. I have had the same problems and have searched the net for any info about an update. Like you, I have not been able to find anything about a projected release of a new version. I guess that is just the microsoft way...only 2 years..
I heard a rumor that it was goint to be built into the next version of Windows mobile, but I hope that's not true.
If that happens, hoppefully it will be DCD to the rescue with a port for use all!!!
The real deal:
Ok, to those who haven't been following:
Microsoft DID update the VC software, but it was never released. It seems the Windows Mobile version went to the back burner since they made a deal with Ford Motors to start including the VC technology in the new Ford in-dash stereo systems (que up your mp3's, make calls via your bt phone, etc).
However, there was a test rom floating around for another WM device that had a greatly improved new VC version, which fixed 99% of the problems everyone was having.
This version was extracted and made available as an OEM to load into a kitchen to build into your ROMs.
There is NO .cab installation that I've seen for this version, so you're stuck with either cooking it in, or just replacing the files (there's a zip floating around here somewhere of the files u need to replace to make it the new version, but I don't recall where I saw it).
The OEM can be found in the excellent new PPCGeeks kitchen (ppckitchen.org), which incidentally supported Titan roms now.
For you DCD fans, it seems he hasn't made his rom compatible with the new kitchen GUI, but its relatively simple to make it a basekit. If enough of you push dcd, he might consider doing it... otherwise, you can always copy the OEM directory into DCD's kitchen OEMs.
Try Dutty's Voice Commander
This works for me, it is the best of both versions I have seen of the voice software. There are a couple versions out there, this is the most recent I have found. It is a cab.
I've got VC almost completely working. I cooked it into the DCD ROM. One reg key needs to be changed to get the button on your headset to work. The part I don't have working is the prompt and confirmation comming to the headset. The prompt and confirmation come out of the phone. It takes commands fine through the headset, just no audio until the call is started. Anyone know how to fix that? I'm using a Jawbone.
Dishe said:
Ok, to those who haven't been following:
Microsoft DID update the VC software, but it was never released. It seems the Windows Mobile version went to the back burner since they made a deal with Ford Motors to start including the VC technology in the new Ford in-dash stereo systems (que up your mp3's, make calls via your bt phone, etc).
However, there was a test rom floating around for another WM device that had a greatly improved new VC version, which fixed 99% of the problems everyone was having.
This version was extracted and made available as an OEM to load into a kitchen to build into your ROMs.
There is NO .cab installation that I've seen for this version, so you're stuck with either cooking it in, or just replacing the files (there's a zip floating around here somewhere of the files u need to replace to make it the new version, but I don't recall where I saw it).
The OEM can be found in the excellent new PPCGeeks kitchen (ppckitchen.org), which incidentally supported Titan roms now.
For you DCD fans, it seems he hasn't made his rom compatible with the new kitchen GUI, but its relatively simple to make it a basekit. If enough of you push dcd, he might consider doing it... otherwise, you can always copy the OEM directory into DCD's kitchen OEMs.
Click to expand...
Click to collapse
i prefer the functionality of dcd's kitchen over ppcgeeks.... except for the splash screen thing... but it's all opinion
serfboreds said:
This works for me, it is the best of both versions I have seen of the voice software. There are a couple versions out there, this is the most recent I have found. It is a cab.
Click to expand...
Click to collapse
Does this version require you to set tags for contacts?
Thanks
roninld said:
Does this version require you to set tags for contacts?
Click to expand...
Click to collapse
No, it doesn't require you to set tags, but provides that as an option. The tags are useful for frequently called numbers as they should reduce errors somewhat.
This version also works properly through my bluetooth headset including confirmations.
-dwdoc
ok, here is what I did to get it working with DCD:
1. Take the voice command folders from ppckitchen and put them in the OEM folder. There are two folders for the newest version
2. Cook your rom
3. Change the button assignment to VC if you want (settings -> buttons)
4. HKLM\Software\OEM\VoiceCommand change "path" to "\windows\voicecmd.exe"
5. HKLM\Software\Microsoft\Bluetooth\AudioGateway change "BTAGExtModule" to "vcbthag.dll"
Hope that helps you guys!
P.S. On the handset the initial voice prompt beep doesn't work.(the first time you press the button)NOT USING HEADSET
When you dial by the headset the little dial tones come out the handset.
This also lets the phone send ring tones to your headset when it is ringing.
Dishe--thanks for the tip, I googled and found a cab--I have voice command 1.6.17913, and it is a significant improvement over the one I purchased. I can now use my BT headset like I did with my old 6700!! Can anyone confirm this is the most recent build?
jtg
1.9.19209 is available as an OEM in the PPCGeeks Kitchen, but I don't know if there is a CAB of it anywhere.
JimSmith94 said:
1.9.19209 is available as an OEM in the PPCGeeks Kitchen, but I don't know if there is a CAB of it anywhere.
Click to expand...
Click to collapse
I just went through the Kitchen process described above and I get a version number of 1.6.19209. Perhaps just a typo?
whbell said:
I just went through the Kitchen process described above and I get a version number of 1.6.19209. Perhaps just a typo?
Click to expand...
Click to collapse
The Tip in option.xml for this version says, "Microsoft Voice Command - Latest version from kaiser". No2Chem shows as the author, so maybe he will chime in.
JimSmith94 said:
The Tip in option.xml for this version says, "Microsoft Voice Command - Latest version from kaiser". No2Chem shows as the author, so maybe he will chime in.
Click to expand...
Click to collapse
This is what I see also.
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="Microsoft Voice Command" group="Voice Control" checked="True">
<Tip>Microsoft Voice Command - Latest version from kaiser</Tip>
<Guid type="p">410788f1-acd5-457b-b9ea-df86ac7f990e</Guid>
<OEMDate>3/30/2008</OEMDate>
<AppVersion>1.6.19209</AppVersion>
<AppAuthorURL>http://www.microsoft.com/windowsmobile/</AppAuthorURL>
<ButtonType>GroupRadioNone</ButtonType>
<OEMAuthor>No2Chem</OEMAuthor>
<Require>93f31b6d-078b-4dae-a335-8ea8c3b22c97</Require>
</Item>
</Items>
I believe it was just a typo and he meant a newer build of 1.6. I have the 1.6.19209 installed from the kitchen and can not seem to get voice dialing to work when I dial by name though. It recognizes the command and will ask me if I want to dial work, home, cell, etc. However, when I confirm it never actually dials. It will work fine if I tell it to just dial a number though. Anyone else experiencing this and know of a fix?
djlenoir said:
I believe it was just a typo and he meant a newer build of 1.6. I have the 1.6.19209 installed from the kitchen and can not seem to get voice dialing to work when I dial by name though. It recognizes the command and will ask me if I want to dial work, home, cell, etc. However, when I confirm it never actually dials. It will work fine if I tell it to just dial a number though. Anyone else experiencing this and know of a fix?
Click to expand...
Click to collapse
There are 3 olders in the PPCKitchen. Voice Command 1.6 (which is the 1.6.17 version), VoiceCommand (version 1.6.19), and VoiceCommand_Lang_0409 (supports files for 1.6.19). I threw the VoiceCommand_Lang_0409 into the SYS folder in DCD kitchen, and VoiceCommand into the OEM. Cooked with no problems.
Have no issues with VC not dialing a contact.
roninld said:
There are 3 olders in the PPCKitchen. Voice Command 1.6 (which is the 1.6.17 version), VoiceCommand (version 1.6.19), and VoiceCommand_Lang_0409 (supports files for 1.6.19). I threw the VoiceCommand_Lang_0409 into the SYS folder in DCD kitchen, and VoiceCommand into the OEM. Cooked with no problems.
Have no issues with VC not dialing a contact.
Click to expand...
Click to collapse
Sorry, which kitchen? I can't find those files...
88fingerslukee said:
Sorry, which kitchen? I can't find those files...
Click to expand...
Click to collapse
After you install the ppcgeeks buildos and update, there is a kitchens folder. In there, PPCGeeks_OEM.rar has these folders.
How come there's no MMS when I go to receive/send pictures? How can I get it back?
I have DCD 3.1.2 rom, and the 3.72.20 radio
paulash said:
How come there's no MMS when I go to receive/send pictures? How can I get it back?
I have DCD 3.1.2 rom, and the 3.72.20 radio
Click to expand...
Click to collapse
run this cab
It looks like that cab coffey attached is Verizon Wireless specific. We should find out what carrier paulash needs before giving this out. What carrier are we talking about here?
Yeah, I'm still trying to figure out how to get MMS with Sprint.
assuming from reading his other comments on other threads he's on verizon. that's why i went ahead and posted it
coffey_joshua said:
assuming from reading his other comments on other threads he's on verizon. that's why i went ahead and posted it
Click to expand...
Click to collapse
Thanks a bunch Joshua I do have verizon, here it goeeess!
coffey_joshua said:
assuming from reading his other comments on other threads he's on verizon. that's why i went ahead and posted it
Click to expand...
Click to collapse
this doesn't work for some reason. Do I add verizons #777 or does it send through a wifi network??
did you soft reset?
coffey_joshua said:
assuming from reading his other comments on other threads he's on verizon. that's why i went ahead and posted it
Click to expand...
Click to collapse
OK, cool. I just wouldn't want someone unknowingly installing this on their device without realizing it was for vz. It may be a good idea to edit the post incase someone else stumbles on it in the future.
Uhhh it says VZW right in the freakin file name. If someone installs it and doesn't have VZW, then they have no business upgrading their phone to begin with
paulash said:
How come there's no MMS when I go to receive/send pictures? How can I get it back?
I have DCD 3.1.2 rom, and the 3.72.20 radio
Click to expand...
Click to collapse
Paul, did you install the verizon carrier cab???
I have DCD 3.2.0 & 3.35 Radio and ran the Verizon CAB after upgrading from 3.1.4, but MMS doesn't exist anymore. I'll try the cab in this thread.
Read the changelog. It clearly states Arcsoft was removed. Install the Arcsoft MMS cab after installing the carrier cab.
Thanks, I missed that line. Phone is resetting now...
gc14 said:
Read the changelog. It clearly states Arcsoft was removed. Install the Arcsoft MMS cab after installing the carrier cab.
Click to expand...
Click to collapse
Wait... is there a different change log I should be looking at? Regardless, MMS is back to normal after running the .CAB. Thanks.
3.2.0
http://forum.xda-developers.com/showthread.php?t=402920
dcd's titan rom:
CHANGED:
Power Management
Dialer
Commmanager
Calculator
Relaxed security
Volume tweak
Touch-like skins
MMS included if carrier supports it
Mortscript included
UC Compatible
REMOVED:
Encryption
SQLCEMobile
Entertainment (Games)
HTC Homeplug
Windows Live
Adobe Reader
HTC Zip
Jbed Java
Wait... is there a different change log I should be looking at? Regardless, MMS is back to normal after running the .CAB. Thanks.
Click to expand...
Click to collapse
That is not the changelog, that's just a list of what was changed/removed. The changelog is in post #2, though for 3.2.0, he only posted the changelog for 3.2.0. Arcsoft was removed a while ago and is in prior changelogs.
UPDATED: SEPTEMBER 26, 2008
September 26, 2008, 8:23 PM EST
Alltel Beta 6 is up.
Please post your results for both sending and receiving.
GC
-------------------------------------------------------------------------
September 26, 2008, 6:52 PM EST
Alltel Beta 5 is up. I'm just going to be making 1 change at a time for each beta from this point forward so I can tell exactly what the issue is. Sorry for all the uninstalling/reinstalling, but it is necessary to properly test.
Please post your results for both sending and receiving.
GC
-------------------------------------------------------------------------
September 26, 2008, 5:32 PM EST
Alltel Beta 4 is up.
Please post your results for both sending and receiving.
GC
-------------------------------------------------------------------------
September 26, 2008, 4:19 PM EST
Alltel Beta 3 and USCC Beta 1 are up, so please test them out and post results for both sending and receiving.
I've made a very minor change in the VZW Arcsoft setup dll and have re-uploaded the new one.
GC
-------------------------------------------------------------------------
September 25, 2008,
Alltel Beta 2 is up.
Please post your results for both sending and receiving.
GC
September 24, 2008,
Ok Alltel users, you ready for some testing? I've posted Beta 1 for download. If you already have an Arcsoft cab installed, uninstall it first. The setup dll is incorporated and should add a string value of "X-Alltel-MDN" with your MDN with a "1" appended to the front of it as data to HKLM\Software\Arcsoft\Arcsoft MMS UA\Config\mm1\WspHeader. I don't have Alltel so I haven't been able to test anything AT ALL except the setup dll, so I apologize if it doesn't work. Don't forget though, this is only Beta 1.
Please post your results for both sending and receiving.
GC
-------------------------------------------------------
September 21, 2008,
Alright, I've updated the VZW 5.0.70.24 cab. The Alltel setup dll is still being worked on so please be patient. I'm also now working on a beta USCC Arcsoft cab, and if I get the proper information for Cricket, that's next.
I've fixed the following bugs (I think) in this latest cab:
- Date/Time issue some users reported
- Default connection now properly set to "Verizon Wireless" instead of "The Internet"
- Send limit options now properly displayed as 100K, 300K, and 399K instead of 0K, 0K, 399K, 0K, 0K.
- Default send limit of 399K now properly set upon install.
Ya just had to ask my friend....
Where is the link??
In the first post
All worked for me as you have directed. I will actually test the MMS here and report back.
Update:
Both versions have installed and worked correctly for me. Thanks gc for making this easy for us.
I have MMS working on my phone with dcd VZW Arcsoft MMS 5[1].0.31.19 which GC i think you posted in another thread on here recently. It works fine for me. What is different between this one and the one i have?
I have MMS working on my phone with dcd VZW Arcsoft MMS 5[1].0.31.19 which GC i think you posted in another thread on here recently. It works fine for me. What is different between this one and the one i have?
Click to expand...
Click to collapse
I have coded a setup.dll in Embedded C++ which is included with Arcsoft for Verizon customers that gets rid of the need for Mortscript and a soft reset in order to retrieve the X-VzW-MDN key.
Testing of this would be greatly appreciated, as in the future we'd like a complete out of the box Arcsoft solution for all carriers. This is the first step.
Everything worked and was in the registry as you said.
It did not send at first, then I looked at the servers in MMS. The sample server is gone now with the Verizon Server being the only and default.
Within that, I scrolled down and it said that "Connect Via: The Internet" I changed it back to Verizon Wireless and works like a charm. Sent a pic to myself, send and receive are now flawless. Great Job.
I am not sure if Conect via the internet was a fluke or not. Just thought I would let you know.
I'm not sure what is supposed to be different about this one vs dcd's last cab release... but still no camera/attach integration working.
Is there any way to post the OEM that I can drop into a kitchen. I am going to redo my ROM and would like to include this.
gc14 said:
I have coded a setup.dll in Embedded C++ which is included with Arcsoft for Verizon customers that gets rid of the need for Mortscript and a soft reset in order to retrieve the X-VzW-MDN key.
Testing of this would be greatly appreciated, as in the future we'd like a complete out of the box Arcsoft solution for all carriers. This is the first step.
Click to expand...
Click to collapse
sorry GC I don't understand what this means as its a little high level for myself. I would love to try it anf provide feedback but without knowing what i should be looking for I can't do much.
Running latest radio and DCD kitchen rom.
Previous Version: DCD 5.0.31.19
Uninstalled and checked registry per instructions, then soft reset.
Ran cab, installed to Device.
X-VzW-MDN was set correctly.
I could not send a MMS at first, but I think it was because I had it hooked up to ActiveSync. I was just now able to send and receive a message with no problems.
Everything worked and was in the registry as you said.
It did not send at first, then I looked at the servers in MMS. The sample server is gone now with the Verizon Server being the only and default.
Within that, I scrolled down and it said that "Connect Via: The Internet" I changed it back to Verizon Wireless and works like a charm. Sent a pic to myself, send and receive are now flawless. Great Job.
I am not sure if Conect via the internet was a fluke or not. Just thought I would let you know.
Click to expand...
Click to collapse
Hmm I'll look into that. That doesn't happen when I install it.
I'm not sure what is supposed to be different about this one vs dcd's last cab release... but still no camera/attach integration working.
Click to expand...
Click to collapse
This is the exact same build of Arcsoft that was included in dcd's cab. Therefore there will be no fixes or included features. I think a lot of people are confused about the purpose of this. I'll explain at the end of my post.
Is there any way to post the OEM that I can drop into a kitchen. I am going to redo my ROM and would like to include this.
Click to expand...
Click to collapse
No. That is defeating the whole purpose behind this project. The Arcsoft OEM was purposly removed from the kitchen in order to develop an out of the box MMS solution for ALL carriers.
sorry GC I don't understand what this means as its a little high level for myself. I would love to try it anf provide feedback but without knowing what i should be looking for I can't do much.
Click to expand...
Click to collapse
The Arcsoft MMS package used to be included in the kitchen (along with carrier selection). dcd removed it because each carrier requires its own settings, whether it be an X-blah-MDN key in the registry, different server settings, etc.
For a while now, our goal has been to develop a setup.dll to be included with the cab install which will run a carrier check, then provision Arcsoft correctly for that carrier. It requires a lot of coding to interact with the registry.
dcd's Verizon MMS cab has the Verizon MMS server info hard coded into it (which is why it won't work for other carriers). The only downfall to his cab, was that it still had no way of including that one beloved registry key that we've all known to love...X-VzW-MDN, which is different for every user because it needs to be set to their own phone number. In order to circumvent the problem, dcd included Mortscript and a script that adds itself to \Windows\Startup so the next time you soft reset, the script runs and fetches your phone number from the registry to set the key and then deletes itself, hence why a soft reset is required when using his cab. This was only a temporary fix, and only worked for Verizon as the mortscript was hard coded as well.
As I said, this is the first step in this project with much more to come. This cab is stripped of Mortscript and the start up script, and includes version 1 of the setup.dll I mentioned. So far, it's only coded for Verizon. I've asked you guys to test it, just to make sure this part of it works. Later, I'll hopefully be able to add more code to make it work cross carrier and fetch the required information.
Hopefully this clears it up for people.
Hopefully this clears it up for people.
Thank you GC for your explanation! I think this should minimize plenty of questions/concerns you may have gotten. Also thank you for your continued interaction in the forums!
Haha I know I just posted this cab for testing, but in this short time, I've managed to stumble across a newer build of Arcsoft and I've edited it to include the setup.dll. So if anyone wants the new build, I've posted it in the first post.
SWEEET ASSS CAB..... GC - Very nicely done.....
I cooked the program into my last ROM. Could I remove the registry string and then install you newer version to see if it picks it up? Would that be a good test?
I don't see why that won't work, give it a try... what was your previous version...?
azclown said:
I don't see why that won't work, give it a try... what was your previous version...?
Click to expand...
Click to collapse
I was on ver: 5_0_31_7.
I deleted the whole ArcSoft folder key and then rebooted. Then installed the newest cab and it pick up the registry string correctly. Seems to be sending and receiving after the install with out any other adjustments.
I was on ver: 5_0_31_7.
I deleted the whole ArcSoft folder key and then rebooted. Then installed the newest cab and it pick up the registry string correctly. Seems to be sending and receiving after the install with out any other adjustments.
Click to expand...
Click to collapse
Hmm...it may still be working, but you might not have it installed correctly. You might be using a cross between the two. If it works for now, that's fine, but the next time you flash or perform a hard reset I wouldn't do it again like that.
Just for curiosity...when you open up SMS \ MMS, and go to MMS Options. In the About tab, what does it say for your MMS Composer version?
Everyone has a different story, or a different item that has triggered that call waiting sound. But it's a minority of people that seem to have it.
I'd like to use this thread to simply have everyone who does have that sound to state, when they got it.. and what applications they had installed... maybe we can determine what combination of items causes it.
Please help if you have that sound and want to get to the bottom of it.
(dont bother with random suggestions on how to fix.. I just want to keep a clean thread to see if we can gather info to see if we have anything in common)
I personally had DCD 3.2.5 / Radio 3.42.02
I upgraded my radio to 3.42.50 and it started.
I have (had) the following installed at the time of upgrade:
GC Arcsoft MMS 5.0.31.25
Pocket CM Keyboard 0.14
SPB Mobile Shell 2.x
SPB Phone Suite
DCD QuickGPS
Resco Explorer 2008
Resco Registry Add-in
Resco FTP Add-in
Palringo
Skunkworks Flash Video Bundle
shamanix HTC Streaming Media
Wisbar Advance 3.2b
Google Maps
Inav Iguidance
MS Reader
Resco Keyboard Pro 5.01
Opera 5.xx
Coreplayer
Nadavi HTC GPS Tool
Handmark Yahtzee
Vito Funcontact
MS Entertainment Pocket Pack
Dinarsoft MemMaid
Shaun33 Sip Config Tool
SJ Labs SJPhone
C. Ghisler & Co. Total Commander
MyPhoneskin (Made with TDial)
resco Aeroglass Keyboard Skin
vito Winterface
Franson GPSGate 2.0
PointUI
Sleuth's WM6Voip
Here is what I have gone through
OK. I was on DCD 3.1.6 and it was my favorite!!! I hated to leave that version. I had radio 3.42.30 (from the vogue). I had no call waiting sound issues whatsoever.
I got my friend to purchase a TITAN and I was showing him how to cook his phone using DCD's kitchen. He had his phone for 2 months and we hadn't cooked. We started on 3.2.2. Note, he was on the stock radio, 3.42.02. We didn't upgrade his radio. We then cooked his phone with DCD 3.2.2. The OEMS we added were:
Google Maps (From PPCKitchen oem)
Games (Chess, Freecell, Galaga, Hearts, Kevtris, Ms PacMan) (From PPCKitchen)
Sprint TV (From PPCKitchen oem)
YouTube Player (From PPCKitchen oem)
The items below are the ones we selected that were built into DCD's kitchen:
Adobe
Entertainment
Voice Command
Startup Animation
HTC Vogue PhoneCanvas
After cooking both of our phones, we both started receiving this sound during call waiting. I then upgraded my Radio to 3.42.50. I still had the sound.
So I thought it was DCD 3.2.2. I then upgraded to 3.2.5. I still had the sound.
I then downgraded my radio to 3.42.40. I still had the sound.
After that, last weekend, I then used the PPCKitchen version 20270 to try cooking it to see if it removed the annoying sound. I still got the sound again.
So at that point today, I just put the 3.56 Stock ROM on my phone to reset the radio, etc. I then used DCD's 3.2.5 kitchen with my same OEM's. The only difference is that I put the phonecanvas.dll file from DCD 3.1.6 in the HTC Vogue PhoneCanvas (OEM_HTC_PhoneCanvas_1_0_31335_0). He mentioned in another thread. I love DCD's work! His kitchens are awesome!
So I am currently at Radio: 3.42.02 and DCD 3.2.5 (using the phonecanvas.dll from DCD 3.1.6).
I am hoping this fixes the problem.
Things to note:
* When I cooked with DCD 3.2.2 and the PPCKitchen 20270. I got the annoying sound.
* People have it using every radio from 3.42.02 to 3.42.50. (Which makes me think it's not a radio issue)
Is ts the CE OS Build of Windows? Or is it the PhoneCanvas people keep mentioning?
Something else?
I will update everyone with how it goes.
I thought someone already had said that it was the Dialer/PhoneCanvas causing this problem?
Either way, I am, like so many others, interested in the solution for this. With the help of someone else, I may spend an evening and figure this out for sure.
The first thing that needs to be done is to see if it acts differently bad on how the call is (you calling out first vs you getting a call) before getting another call. I imagine that this factor shouldn't affect it happening, but taking a scientific approach, it should be evaluated.
Next, make sure you can reproduce it every time. If not, there must be other (hidden?) circumstances.
I could sit here and elaborate on how to narrow this down, but it would take longer than anyone would care to hear. Just be scientific and intellectual about trying to find it, and you should be able to for sure.
Well, my 2 cents? Had it with 3.42.50 and 3.42.40 (downgraded) on the 20270 kitchen. A couple of days ago, I cooked with dcd 3.2.5 kitchen and its gone. I chose NO dialer skin as I prefer the standard dialer. (i like the contacts being right there along with the "smart" dialing. Any excuse to use the scroll wheel is good enough for me )
you can stop the sound from playing all together. in a registry editor, go to HKCU->ControlPanel->SoundsCategories->Sounds and delete the CallWaiting key. this will stop any sounds from playing.
Or you could wait for 3.2.6. as dcd said it's fixed.
Hmm, so why do some people have the problem and some don't? I flashed with dcd 3.2.5 and it's gone, whereas others say they still have it. *shrugs*
I'm one that's never had the problem but at the same time I always use a specific dialer with each new upgrade. That's why I think it's a phone canvas issue.
worldwidepmp said:
I'm one that's never had the problem but at the same time I always use a specific dialer with each new upgrade. That's why I think it's a phone canvas issue.
Click to expand...
Click to collapse
I can say just the opposite since I NEVER use anything but the default canvas/dialer.
I first got this after flashing radio 3.42.30 and dcd 3.2.2 (same night)
I flashed to dcd 3.23, and it was still there.
I flashed to dcd 3.25, and its still there.
I re-flashed the radio, and its still there.
I Upgraded the radio to 3.42.50, its still there.
I edited my registry to not use the vogue dialer--still there.
I'm using dcd's kitchen, no OEMs added, just enterprise, entertainment, vc, and everything else as defaults.
I'm on alltel, I do use activesync with exchange, spb pocketplus, google maps, livesearch, htc gps viewer, and wififofum2.
I did NOT re-flash without the dialer--too tired of reinstalling everything.
I'm pretty sure its every call, regardless of whether its incoming or outgoing.
jtg
worldwidepmp said:
Or you could wait for 3.2.6. as dcd said it's fixed.
Click to expand...
Click to collapse
Does this mean they know what the issue is? I wasn't aware of that.. I thought a handfull of people had the issue and the cause was still unknown?
Updated to DCD 3.2.6.. Installed all apps.. No more Call waiting sound!!!
Same as x51. I flashed 3.2.6 and the fall out noise is gone! WOOT
ppc 6800
alltel
3.42.50
dcd's 3.2.6
ditto
Same here--the beep is gone!!!
jtg
so what caused it? How to change call waiting to personal tones?
studentjunk said:
so what caused it? How to change call waiting to personal tones?
Click to expand...
Click to collapse
I dont know. It's fixed in 3.2.6.. so DCD knows..
I wonder if he can release a fix for those who are comfortable and dont wish to flash??
studentjunk said:
so what caused it? How to change call waiting to personal tones?
Click to expand...
Click to collapse
i would guess that you would need to open the dll's in the phonecanvas package using resource hacker and modify them before cooking your rom (or make a cab)
dcd1182 said:
i would guess that you would need to open the dll's in the phonecanvas package using resource hacker and modify them before cooking your rom (or make a cab)
Click to expand...
Click to collapse
People just need to flash to 3.2.6 I am loving this Rom! Call Waiting is fixed for me also....3.2.6 with 3.42.30
Can someone post the vzappzone cab from the TP? I want to check out the visual voicemail using the XV6800...hopefully.
THANKS!
There is no CAB in memory... it was a download from Verizon, not sure how extract it...
I dont see a Visual Voicemail app anywhere on VZAPPZONE either... I searched.
As far as I know, Visual Voicemail is only available on the blackberry storm and costs $3/mo.
Here I found this:
http://products.vzw.com/index.aspx?id=fnd_toolsapps_detail&appId=3109611
Apparently it will be pre-install on the Samsung Omnia (WM6.1 device) so we may be in luck soon!!
ramborami said:
There is no CAB in memory... it was a download from Verizon, not sure how extract it...
I dont see a Visual Voicemail app anywhere on VZAPPZONE either... I searched.
As far as I know, Visual Voicemail is only available on the blackberry storm and costs $3/mo.
Click to expand...
Click to collapse
I think that when you download the cab, you can save to the storage card. If you have the time to try that and then attach here that will be great.
Thanks!
froader said:
I think that when you download the cab, you can save to the storage card. If you have the time to try that and then attach here that will be great.
Thanks!
Click to expand...
Click to collapse
FWIW, I asked about visual voice mail when I bought my TP (through the telesales store), because I noticed it comes pre-installed on the Saga, too. The Verizon rep told me that it's not compatible with the TP.
But, don't let that slow you down -- Verizon reps say LOTS of things....
Kalnel said:
FWIW, I asked about visual voice mail when I bought my TP (through the telesales store), because I noticed it comes pre-installed on the Saga, too. The Verizon rep told me that it's not compatible with the TP.
But, don't let that slow you down -- Verizon reps say LOTS of things....
Click to expand...
Click to collapse
I am seriously getting sooo sick of Verizon's Bull Sh**. First they cripple the Touch Pro and charge more than other uncrippled versions. Now the rep says no visual voicemail even though the TP support page shows the feature and the visual voicemail page shows the TP as a supported device. One of these days it would be nice to get what you are actually told you are buying!
froader said:
I am seriously getting sooo sick of Verizon's Bull Sh**. First they cripple the Touch Pro and charge more than other uncrippled versions. Now the rep says no visual voicemail even though the TP support page shows the feature and the visual voicemail page shows the TP as a supported device. One of these days it would be nice to get what you are actually told you are buying!
Click to expand...
Click to collapse
I got fed up with it too. I orriginally bought the verizon TP. ended up buying the sprint version, returning the vzw one, and going through the lengthy, hacky, process of making the sprint TP work on verzon's network. I'm very happy now.
What route did you go to buy the Sprint Touch Pro and how much?
Any problems yet?
Thanks!
I found a registry key identifying the Titan as XV6800 for IE browsing. Can someone with a Touch Pro pass on the info in this reg key for me.
HKLM\Security\Internet Explorer\User Agent-Custom.
Thanks!
froader said:
I found a registry key identifying the Titan as XV6800 for IE browsing. Can someone with a Touch Pro pass on the info in this reg key for me.
HKLM\Security\Internet Explorer\User Agent-Custom.
Thanks!
Click to expand...
Click to collapse
Alright, I just got it. I changed the above reg key to XV6850 pointed to ota.getvzappzone.com and got the download. On to Visual Voicemail.
Here is the Cab.
I just checked, VZAppZone is now on mobile.vzwapp.com
froader said:
Alright, I just got it. I changed the above reg key to XV6850 pointed to ota.getvzappzone.com and got the download. On to Visual Voicemail.
Here is the Cab.
Click to expand...
Click to collapse
WOW.... so you think if you change that reg key to "Omnia" or "SCH-i910" then VZAPPZONE would let you download Visual VM????
I uninstalled piece of crap vzappzone because it kept turning ON my internet connection at random times for no apparent reason.
Original Registry Key:
HKLM\Security\Internet Explorer\User Agent
"480x640; XV6850; Windows Mobile 6.1 Professional;" (without the quotes)
Uninstalled vzappzone, changed reg key to: "240x400; SCH-i910; Windows Mobile 6.1 Professional;"
reinstalled vzappzone, still no ability to find visual voicemail...
Here is the visual voicemail cab I have been running on my i910 as well as i730, going to try it on my saga next, remember to install .net framwork 3.5 with it!
Link to framework: http://frifor.com/download/IBI/NETCFv35.wm.armv4i.CAB
VVM Cab - Attached
I downloaded the cab and installed it. When running through the startup sequence it failed and said to call customer care. They obviously wont help with this. Do I also need to change update the reg key so that VZ on connection thinks its a touch?