Before anybody flames me, although I am a newbie here, I have searched, and searched, and searched....I am a previous user of the 6700, and am a propeller-head by trade.
With all that said, I have a legal copy of VC 1.6 (see sig for details and device), and I'm looking for a fix to address any or all of the following issues:
1) Dialing confirmation prompts do not work over bluetooth.
2) Caller and appt. announce does not work over device speakerphone.
Although I use a bluetooth headset, I really prefer announcements on the device speaker. If anyone has a solution to only #2 above, I'd scrap the BT headset in a heartbeat because sound seems to wave in and out over BT on WM6 on this device anyway.
I've seen posts of replacement files that fix the announcements; unfortunately, the reports of those fixes say that the ringer doesn't work for "unknown" callers. Yikes!
ANY help or direction-steering would be greatly appreciated.
Upgrade to any of the 3.16 ROMs. I had the same problems as you, and the upgrade fixed all of them. Some of the ROMs include an OEM of MSVC v1.6.17913, so that will be upgraded too.
Thanks for jumping in here.
What phone are you using?
Also, can I go back to the standard Verizn ROM if it doesn't work or something fails?
And where can I find these ROMs?
I have the Sprint PPC-6800. Look here in the Titan Upgrade forum for several ROMs, and several more on PPCGeeks in the HTC Titan forum and its Upgrade sub-forum.
Be sure to read the instructions first, as there are several steps the first time. You have to unlock the bootloader, load a new radio, and the ROM. The bootloader and radio only need to be done once, then you can load any 3.16 ROM you want.
Other benefits of the new ROMS are WM 6.1, EVDO-A and working A-GPS.
Did you get the VC to work on a Verizon XV6800 and "hear" the confirmation?
Did you get the Voice Command to work on your Verizon XV6800 so that it "hears" the confirmation via Bluetooth?
Thanks
Related
Hi all,
Please go easy on me here, as I have some probably pretty basic questions. I have been digging around the internet (mostly these forums) for the past two days since I got my new Mogul from Sprint running WM6. I had the PPC-6700 prior to this (as I expect most of you had) and I was fairly good at tinkering on that one, but I'm on new ground here with WM6 and a new phone.
First, I am a little confused by all the names.
For sure, I know that this phone can be called the Titan, the Mogul, or the PPC-6800. What I'm not sure of is that some people also call this the Hermes or the TyTn. I figured Titan and TyTn were the same things, but apparently not.
The main reason I'm asking is so that when I am looking for information and posts on this phone, which can I use and which should I disregard. It seems that many of the things posted under the Hermes forum are valid for the Mogul as well, but alas..I'm confused.
Once we get names settled, I'm going to start with only one other question that I have dire need for. I have looked around for answers and most are many months old, so I have to think that there are some more recent findings. My question regards Microsoft Voice Command 1.6 with a BT headset on this phone.
I have installed MS VC 1.6 and paired my new Cardo Scala 800 headset. It seems to work with the following problems:
1) BT quality is not great, including VC voice getting cut off. This is my first BT headset with this phone, and I have read that many people have poor BT quality with this phone. If that's the case, can anyone recommend a BT headset that works well with this phone (preferablly one that charges directly via mini-USB).
2) Confirmation don't work - based on what I have read this is a problem with all WM6 phones with VC 1.6. It appears the only solution is to disable confirmations completely. I have done this and it appears to be able to function. I just want to confirm that there isn't any newer data out there for this issue.
3) Last issue is that I don't get notifications. Meaning, when an incoming call comes in I get the ringing sound, but it doesn't tell me the name. In my searches I came across this posting:
http://forum.xda-developers.com/showthread.php?t=316881&page=51
It is for the Hermes (again..confused) but contains a zip file with 4 files to copy over the default VC files. When I did this and reset my phone, notifications seem to work. I want to make sure that this is the best way to get VC 1.6 working as fully as possible on this phone.
I really appreciate any feedback you can give.... I have a few more questions, but I'll wait till we get these squared away.
Thanks to all!
Well, I've not been a Mogul owner for much longer than you, and certainly have been a PPC owner less (this is my first PPC), however let me try to answer a few of your questions.
First, the "Sprint Mogul" is Sprint's name for this phone. The phone "codename" of sorts is the Titan, and model is the PPC-6800. Hopefully I got that all right. Bottom line, they all refer to the same phone. Also, different cell companies have different names for phones, so it can get a little confusing sometimes.
Now the TyTN is the same device as the Hermes, aka the 8525. From what I've gathered in my short experience, this is basically the same same phone as the Titan, however, it's the AT&T GSM version. Where we have CDMA and EVDO, it has GSM and HSDPA.
The files get tricky too, and you have to know your way around the system before you try replacing files from other phones. A lot of files (and issues) are general for WM6. That means that any device running WM6 may have these same files, behaviors, or issues. However, with that said, certain files are specific to the network. Some of the things like dialers are coded for GSM on one phone, and CDMA on another. So if you think it might have anything to do with the network, double check before you replace it from another phone that's on a different network. In your case, the voice command thing is general to WM6, so grabbing the files from the Hermes was ok.
The bluetooth? Well, that's a question a lot of us still have. The bluetooth on these phones suck. I've heard a lot of people say it's HTC's fault, and I've also heard a few people say WM6 just isn't good with BT anyway. I personally haven't gotten into what's wrong with it much yet, so I can't tell you exactly the issues, but we can only hope for a firmware and/or software update in the future that will help these problems.
I know that if you look around, I've seen lists where people have listed which BT headsets seem to work well, and which don't. The only I have, and thus have tested, is a Jawbone, and I can report, as well as tell you from reading, it's one of the better BT headsets for this phone. It's a little expensive though, so it's not in everyone's price range. Unfortunately I can't help much past that since I've never used any other, but if you search you can probably find threads like I mentioned and just get feedback from other people.
Also, I've never played with Voice Command, so I can't answer any more specific questions on that subject. Hopefully I helped clear a few things up. As I said, I'm definitely still learning myself, but I've been taking in all kinds of information. I love this phone and don't see how I've survived without a PocketPC before.
Ajerman,
Thanks for your input. Ok that makes sense regarding the AT&T GSM version. I think most of what I will want to tweak will be related to WM6 and not carriers.
Unfortunately my Cardo 800 BT headset is my first headset too, and this is the first time I'm using it with the phone. So, I too don't have anything to gauge it against. I'm probably going to return the headset however as it was advertised as having a mini-usb charging jack, when infact it has a micro-usb. I saw the jawbone, looks nice, but again, I only want a headset that uses a mini-usb jack (too many adapters to carry around).
My next questions (hopefully someone can address), is unlocking the Extended ROM for customization. I did this on the PPC-6700 WM5 with an Extended rom unlocker tool and modified the config.txt in there to automatically install certain apps upon hard-reset.
I need to assist the mobile admins at my company with setting everyone's phone up with some additional settings en masse.
Is it safe to use the same procedures on WM6? I'm probably going to try it anyway but thought someone could point me to a good primer on upgrading my skills from WM5 to WM6.
Any more input is valued!
thanks
I am very sorry in advance if this issue has been raised elsewhere on the site, but after spending quite some time searching for an answer by both the forum search and google search, I am going round in circles and haven't found a solution.
I have a UK Tmobile Vario 2 (Hermes) running its original Rom (I have been too scared to flash it in case I break the phone as I don't really know what I am doing) and I have a Motorola S705 A2DP headset. I love the feature on VC 1.6 which reads out new text messages in full but can't find any way of routing the audio for this feature through my bt headset. The incoming call notification works through the headset but every time an SMS comes through it pauses A2DP, reads it via the phones loudspeaker, then diverts sound back to the headset again?!?
I went on the WIKI and found the Voice Command section. I tried installing the patch/program it suggests and did the tweaks it said to the registry , but it didn't make any difference on this problem.
I just wondered if this is an unfixable problem, or if there is anything I can do to get it working because this feature would be incredibly useful to me (I ride a motorbike and to get texts read through my headset when riding would be excellent).
Thanks in advance for any help guys. Sorry again if I am raising a known issue, if I am, if you could point me in the right direction it would be much appreciated.
have you tried this? i know this .cab file worked on my jawbone but i dont/have not used VC 1.6.
bapski said:
have you tried this? i know this .cab file worked on my jawbone but i dont/have not used VC 1.6.
Click to expand...
Click to collapse
Thanks Bapski, I have just installed it but unfortunately it hasn't helped thank you anyway though, it was definitely worth a try
Well, I have had a good read through the threads on Voice Command and all the fixes for the headset button but it seems nothing yet solves the problem of routing the SMS notification through the headset which is a shame, it would have been so useful.
Well, hopefully, when I get my nice new Kaiser upgrade (whenever that may be ) .. I will have more luck with the bluetooth audio
Don't buy a phone with a MS BT stack because they will never fix the problem..MS has known about this for so long its just sad..The next phone I get will have a widcomm bt stack.
Yeh, got to say that the bluetooth hasn't been particularly great ... especially when trying to get it working on A2DP.
If only I hadn't stumbled across VC 1.6 I would be none the wiser and wouldn't even know it is possible to have SMS messages read out oh well
it doesnt work dont even bother, I loved it on my wizard, but there is a hardware problem with the heremes or whatever the problem is the last revision of the BT stack doesnt fix it and its never worked. all the patches and fixes only work for awhile then just stop and rquire a cryptic series of hacks to make them half work again. your better off buying a thai slave to read your messages to you.
Greetings.
This is my first post to this forum section. I'm more of a Windows/web developer who's just beginning to get his feet wet with WM development - I've written a process manager and a "kill task" command line tool so far.
I own a 8125 (Wizard), and I've had a blast customizing it. I'm currently running the latest release of TNT's WM6 ROM and quite content. However, I do have one issue that I have not been able to resolve.
When using a Bluetooth headset, most audio is redirected to the headset as expected. However, when I invoke a call via VoiceCommand, the dialer still outputs the dial tones to the internal speaker. This can be annoying when in a crowd.
Has anyone come across this issue? Does anyone have a solution? I've considered trying one of the dialers posted under the HTC thread, but I thought it might be wise to consult with experienced devs.
Thanks much,
W James
P.S. I originally posted this question under the Wizard WM6 section. Unfortunately, no one was able to offer a solution. Sorry about the cross posting. Hopefully someone can provide some suggestions here.
I am in the process of moving from a TP to a TP2, and am configuring the latter, however (and I have seen this problem elsewhere regarding this phone) I cannot get my bluetooth headset to play nice with MSVC. Specifically the button to initiate the call.
I have tried the steps listed by bengalih and all should work. From what I have read, they are using a different bluetooth stack for the TP2 which is the issue.
So I have a few questions.
1. Has anyone got the headset button to activate MSVC successfully?
2. Is there a way to change the bluetooth stack without changing the ROM
3. will changing the ROM fix this? Any way I can tell which ROMS will have a working bluetooth stack?
I have Vodafone UK branded model.
This is I think the last thing that I need to make the phone 'functional' for my daily use, and so would be really grateful for any advice.
crazyC said:
[...]
1. Has anyone got the headset button to activate MSVC successfully?
2. Is there a way to change the bluetooth stack without changing the ROM
3. will changing the ROM fix this? Any way I can tell which ROMS will have a working bluetooth stack?
[...]
Click to expand...
Click to collapse
1. Yes, with certain headsets that will allow a verrry loooong press without turning off.
2. I suppose it's theoretically possible, but I do not know for sure.
3. Yes. Some of the cooked roms work fine with MSVC and bluetooth headsets on the TP2.
Could you give examples of the cooked roms that work?
Cheers
C.
any trick or hack we can borrow from "bt-MSVCworking roms" and transplant in stock roms? maybe a skilled dev might try to do something.... PLEASE guys!
crazyC said:
Could you give examples of the cooked roms that work?
Cheers
C.
Click to expand...
Click to collapse
NRGs Genesis ROM works for me. http://forum.xda-developers.com/showthread.php?t=553506
Gordon
Flashing now and will confirm experience with my two headsets shortly.
EDIT:
Only had time to test the specific problem identified at the start - both headsets work fine now. Hurrah. I do not know the specifics behind why, or if this will apply to all 6.5 based roms. But for anyone desperately seeking a resolution the headset initiation of MSVC, using the ROM above does fix it. And so far the NRG ROM does seem good.
crazyC said:
Could you give examples of the cooked roms that work?
Cheers
C.
Click to expand...
Click to collapse
I currently use EnergyROM version 20090822 (Titanium) with MSVC 1.6.21040.
Thanks to those above for their help.
thank you for the contribution, but for who is keeping stock rom, any possible solution??? I would sell my soul for this...
A "stand alone solution" for Touch Pro2s with an original ROM would be great. Possibly one of the ROM cookers can extract it for us.
Thanks a lot in advance,
Klaus
that would be really appreciated!!!
Got it to work, but...........
Hi I have a TP2 with MSVC installed. I got it to work by editing the regsitry and swapping SDDialer.exe with voicecmd.exe. It works great. I press the button on my bluetooth headset and MSVC is invoked.
The only problem is that the voice commaned that i say has to go through the TP2 microphone not the bluetooth headset microphone. Any one knows how to direct the audio input to the headset microphone???
I am using Miri cooked ROM 23017 with manila v2.5
rgd
Raed
this bluetooth activation is a real bugger!! does the audio from VC go to the device loudspeaker, or BT headset? that would be a beginning, somehow...
any luck with cyberon voice commander yet?
cyberpunk627 said:
this bluetooth activation is a real bugger!! ...
any luck with cyberon voice commander yet?
Click to expand...
Click to collapse
Well I have the Voda version of the TP2 and I also have a spare to play with (I cracked the screen on my first one and got a new one but they never asked for the old one back - it works fine) so I loaded the EnergyROM from a link elsewhere on this thread on to it. My bluetooth headset does not work with the Cyberon Voice speed dial program which I prefer - although this ROM does alow you to put all sounds through the headset. It worked fine on my old TyTn from Voda. Like you said, this is a real bu**er!
Barry
mmmh I'm becoming more and more obsessed with this. I googled everywhere but found anything... someone reports msvc and cvc as working, someone else not.. but nobody says it's working from BT headset... blame on htc that forgot such an important thing!
cyberpunk627 said:
mmmh I'm becoming more and more obsessed with this. I googled everywhere but found anything... someone reports msvc and cvc as working, someone else not.. but nobody says it's working from BT headset... blame on htc that forgot such an important thing!
Click to expand...
Click to collapse
It's all true
I understand that on the Telus ROM MSVC works with Bluetooth out the box
MSVC and CVC do work, UNLESS you want to use Bluetooth, when they don't (with stock ROMS in the EU) ;-)
I'm using MSVC on NRGs Genesis ROM and it works from Bluetooth as it should. If I get a Chance I'll install CVC and give it a try and report back.
Gordon
it would be nice if someone can mange to transplant needed files... I like the bluetooth stack on TP2, really better than usual, but this thing needs more attention from HTC and the 3rd party developers.
msvc is 3 years old as of now, no newer versions, same as cvc... too bad, technology evolved a lot it 3 years, and these programs might improve really really much!! especially the recognition algorythm, and functions.
well, I hope the new wm6.5 will bring some BT improvements for TP2 then...do not want to stick with custom roms yet. keeping my fingers crossed!
should you manage to try, let us know about cvc and make a little comparison for us! you lucky! ;-)
cheers
I´m usign Smaberg´s Touch X "HERO" EDITION and VC works just fine.
GordonTGopher said:
I'm using MSVC on NRGs Genesis ROM and it works from Bluetooth as it should. If I get a Chance I'll install CVC and give it a try and report back.
Gordon
Click to expand...
Click to collapse
As my touch screen has died I am without a TP2, so I can't do this for the moment
Gordon
I've had this problem sometimes on my VZW CDMA Touch Pro 2. my solution has been to turn off the headset and turn it back on. It seems the problem starts for me when I have the headset on when rebooting the phone. Possibly MSVC doesn't detect the presence of the headset or something to that effect.
Hello,
I've got a lot of problems with Voice Command + LEO + BT Headphone.
Voice command speaks on the Leo (Do you want to call Mr TITI at work?) instead of speaking in headphone.
Do you have similar problems??? In France we all have it.
Do you have a solution?
Thanks in advance.
Hi, I have the same problem: some times it use the headset, some times the phone pseaker....
I have other problem with VC 1.6.21725:
- as Mail are read perectly, I have no SMS read.
- Call announcment are not thrown every times I have an incoming call...
Any help?
Is there anymore development for VC? or is it discontinued to Tellme?
same problem here....
does anyone have a solution yet? how to make Leo let voice command speak via bluetooth? Not through the the device? I searched the hole Forum. Any tips and hints that where given didn't work for me. So, if someone have an Idea please post.
Thank you.
Joshua
Same thing happens with Cyberon VSD I am using. Hope someone finds a solution. This didn't happen both in my Omnia and Topaz.
There are a lot of threads here discussing this problem... do a search if you want to research it.
Basically, it is because the HD2 uses the Widcomm BT stack instead of the usual MS one... it will not play nice with many apps (and some hardware) which may have been written with the MS one in mind. This is not an easy thing to fix by just cooking into ROMs too. THe guys with the Touch Pro 2 have this same issues longer than us HD2 owners cause of the same stack... and they still have no solution.
Our only hope is that Widcomm updates their stack to play nice... or more importantly, MSVC or CSVD issues an update that will play nice with the Widcomm stack. Last update to MSVC was shown on Handango site as 20th Nov 2009.... I would like to hear from anyone who has tested this with our units.
Seems to have no issues to our problem
Looks like it's a problem of certain BT headset devices.
Look here http://forum.xda-developers.com/showpost.php?p=5318249&postcount=31