Hi All,
Has anyone experienced this:
Talking on the phone using a bluetooth hands free (Moto H500) and any kind of notification comes in (new txt msg, new voicemail, low battery, etc) the call switches from the headset to the handset. I only had this happen in the WM6 ROMS, but it has been in all the ROMS i have tried. Maybe there's a fix i missed somewhere, maybe it only happens to me... Any thoughs or suggestions would be greatly appreciated.
thanks
Ya, I have the same issue with the WM6 ROMS.
I think I solved it though. You have to set Voice Command to only announce notifications though the device speaker. That seems to have solved the (annoying) issue for me.
Thanks for the info GadgetGuy, I'll give that a try... I just prefer that the people around me not know I just got a new message or my battery is low... If I find anymore on that I'll post again.
Hi,
HTC today posted a hot fix for bluetooth at their e-Club.
Description:
Bluetooth Hot Fix (for HTC TyTN II)
Dropped calls sometimes occur when Bluetooth is on. If you encountered the same problem, please download this Bluetooth Hot Fix and install it on your device.
Br,
Mads
Downloaded it from HTc.cOM
Installation instructions
Follow the instructions below to download and install the hot fix on your device:
Make sure you have Microsoft ActiveSync® installed on your Windows XP PC or Windows Mobile Device Center on your Windows Vista® PC. You can find Microsoft ActiveSync from this link or Windows Mobile Device Center from this link.
Connect and synchronize your device with your PC via Microsoft ActiveSync® or Windows Mobile Device Center using the USB cable.
To download thehot fix, first select the check box below. Next, select thehot fix and the desired FTP site then click Download.
Copy the hot fix, which is a cab file, to your device.
To install the hot fix, tap the cab file and follow the on-screen instructions.
Here is the file:
http://rapidshare.com/files/77588898/TyTNII_BT_Hotfix.zip
Enjoy,
Nadavi
Extracted madsnm's posted cab, which is the same as nadavi's. This is a replacement file for OEM\OEMDrivers\TIInit_4_2_38.bts (a.k.a. \windows\TIInit_4_2_38.bts for non-chefs).
I've re-attached it as the naked file (without the cab installer or the self-extracting exe installer).
Any decent chef should be able to figure out how to turn a single file into an OEM package
Edit: Forgot to add that there are no registry entries, as I've already created registry dumps before/after install...
Edit3: It *IS* the same as the one in the AT&T 1.60 ROM. I did a file compare and there are no binary differences.
Although I am not having any problems as mentioned in the fix log, but the idea of HTC releasing something for us is great .
taiseer999 said:
Although I am not having any problems as mentioned in the fix log, but the idea of HTC releasing something for us is great .
Click to expand...
Click to collapse
Thats right!
Waiting for WM6.1 ROM! or maybe new WM06 Full Touch rom from HTC....
Just my two Cents....
Nadavi
Nadavi said:
Thats right!
Waiting for WM6.1 ROM! or maybe new WM06 Full Touch rom from HTC....
Just my two Cents....
Nadavi
Click to expand...
Click to collapse
well, 6.1 ROM doesnt really looks appealing to me, i believe most of us would want our freaking D3D driver to improve our kaiser speed.
come'on HTC, give us our driver. We want our kaiser to work @ its full potential!
almost forgot, to the brothers at the top 3 post, THANKS for sharing!
Solved my "bad" connection to the BT carset - thx....
ruffruff said:
well, 6.1 ROM doesnt really looks appealing to me, i believe most of us would want our freaking D3D driver to improve our kaiser speed.
come'on HTC, give us our driver. We want our kaiser to work @ its full potential!
almost forgot, to the brothers at the top 3 post, THANKS for sharing!
Click to expand...
Click to collapse
OT but the driver is there. Look here for more info. There's also an XDA thread on this. We just need to tweak it out for general purpose acceleration.
Sleuth255 said:
OT but the driver is there. Look here for more info. There's also an XDA thread on this. We just need to tweak it out for general purpose acceleration.
Click to expand...
Click to collapse
It doesn't say much if they hacked something for Coreplayer, or it was a general fix from HTC for all Windows Mobile devices running the MSM chipset.
Would be nice if the Kaiser was as snappy as that dual-keyboard Pantech running WM6 Standard.
I'm at loss to say if all the UI (and general system) lag is from too much use of .NET, lack of hardware accelerated graphics drivers, or Pro just runs slower than Standard because of the touch-screen support.
Hmm...wonder why i didn't get an email from the e-Club about this. I log into the site and find the fix just fine but I thought I'm supposed to get a notification about it (i'm pretty positive that was my preference when signing up)
Anyway, does this hot fix help in pairing bluetooth with car kits and devices that had problems or were incompatible thus far.
I've never experienced dropped calls with my BT connection, but I do have another problem that is pissing me off.
I have two different Pioneer stereos in two different vehicles. The AVIC-Z1 and the Premier DEH-P980BT.
When I first try to initiate a call with the 980, the connection is made, but the audio is somewhere in limbo between the phone and car speakers. There is a BT connection, but it takes about a minute and a half to actually start sounding through the speakers. By that time, the receiving end has hung up.
Since it only happens for the first call of the ride, I've been getting in the car, calling my voicemail, and waiting until I can hear the voicemail prompts. After that, I can make and receive call normally until I shut the car off.
If this fixes the problem I'm having, I'll be ecstatic.
Hi,
I have no noticable problems with BT exept the sound quality. Will be anything better or maybe worst if I install this upgrade? Does anybody have experience on it?
Thx
Mikus
NuShrike said:
It doesn't say much if they hacked something for Coreplayer, or it was a general fix from HTC for all Windows Mobile devices running the MSM chipset.
Would be nice if the Kaiser was as snappy as that dual-keyboard Pantech running WM6 Standard.
I'm at loss to say if all the UI (and general system) lag is from too much use of .NET, lack of hardware accelerated graphics drivers, or Pro just runs slower than Standard because of the touch-screen support.
Click to expand...
Click to collapse
Sounds like they had to change something with the drivers. So they're there but poorly implemented. And sounds like they'll give us driver info once its released. I'll buy it if it fixes the D3D support!
Still garbled on my Tilt with an Infinity G35..now how do I deleted the Kai6492_HotFix from my Programs directory? I can't see to find it...yet the icon is still there. Any one know?
Flapjack said:
I've never experienced dropped calls with my BT connection, but I do have another problem that is pissing me off.
I have two different Pioneer stereos in two different vehicles. The AVIC-Z1 and the Premier DEH-P980BT.
When I first try to initiate a call with the 980, the connection is made, but the audio is somewhere in limbo between the phone and car speakers. There is a BT connection, but it takes about a minute and a half to actually start sounding through the speakers. By that time, the receiving end has hung up.
Since it only happens for the first call of the ride, I've been getting in the car, calling my voicemail, and waiting until I can hear the voicemail prompts. After that, I can make and receive call normally until I shut the car off.
If this fixes the problem I'm having, I'll be ecstatic.
Click to expand...
Click to collapse
here's what causes that issue on my phone:
hit the ms voice command button and hear the beep prompt.
now hold the button down till you get the cancel beep.
now make a call. you will get no audio either direction.
turn the phone off, and the sound starts working. turn it back on and it's gone again.
key the ms voicecommand button again and let the time expire instead of holding to cancel.
make another call, and the audio will be fine, except for a 5 to 10 second delay.
see if this is how your phone behaves also. if I don't ever cancel a ms voicecommand by holding the button down, everything seems to work fine.
After installing the "fix" I could no longer use voice dial with any of my bluetooth headsets. Uninstalling the fix fixed it.....go figure.....
I think that HTC really need to have more, serious, knowledgable beta testers to tryout this stuff with various software and hardware scenarios before releasing the device. Some of these "bloggers" that they send new, unreleased devices to are either cronies or don't know much, or will not test the devices thoroughly and/or report back to HTC what problems that they experienced. I am a Verizon and AT&T user. Have seen these anamolies between diferent devices for some time now. The Mogul and XV6800 don't have the same issues we have, however, I guarantee you they do have others such as the De-activated GPS flaw that happened recently in the Mogul.
Unfortunately my Kaiser didn't work still with this hotfix. I installed on my device few times, I rebooted the headset and nothing. Probably it's like that because my ROM is 1.83, it's original polish version of it. How can I resolve the problem of bt headset ?
The fix file is a CAB (download from HTC e-club)... I install the CAB and find a link under software menu... I tap it... and another installation is done... I must soft reset the device... and stop...
Okai... so I think in this way the fix is gone... but... I have yet the cab installed under Software CAB and Installed application... can I uninstall it? The trashes pissing me :-D
or for att users go here....
http://forum.xda-developers.com/search.php?searchid=8811535
I have just upgraded to the tilt .
I have installed ms voice Command 1.6 and also the bt voice Command hack to allow voice Command to come over my bluetooth . Well it's not working . even if I edit the reg. I also tried the vc16btfix , still didn't work. is there something i'm missing ?
criddle said:
I have just upgraded to the tilt .
I have installed ms voice Command 1.6 and also the bt voice Command hack to allow voice Command to come over my bluetooth . Well it's not working . even if I edit the reg. I also tried the vc16btfix , still didn't work. is there something i'm missing ?
Click to expand...
Click to collapse
I have 8925 with Custel ROM. I've read here and there that people upgrade and install the BT Hack...
But I never had to. I had the 8525 and I remember I had to add the BT Hack (and give it like 15 seconds or whatever...) to transfer all audio to BT. But at least on my 8925, right out of hard reset, VC 1.6 works fine with my BT Headset (Jabra, Jawbone, few Motorolas, etc...all of them works fine).
Search button is a good friend on this forum it helped me find my solution for this exact same problem
Try this:
Edvard_Greig said:
Hallelujah! I finally figured it out- so it did have to do with the XCSDM setting I believe... so here is what I did for anyone else that is wondering:
1. Installed MSVC 1.6 (from the link in the TNT ROM posted earlier)
2. Soft Reset
3a. Made registry change to set Path = \Program Files\Voice Command\voicecmd.exe (no quotes)
3b. Change button assignment (assigned to Button 6/PTT in my case)
4. Soft Reset
5. Enable XCSDM
6. Soft Reset
7. Disable XCSDM
8. Soft Reset
9. Pair Bluetooth Headset
It seems to be working...the best I can figure is that when it initially gets installed the XCSDM doesn't have any value at all, but by enabling it, and then disabling it, it actually turns it off as opposed to having a null value. Also note that since I am using Alex's 'UltraClean' ROM, there were never any Cyberon installation traces, and therefore I ignored those sections.
In any case it seems to be working great and I'm very happy.
Thank you everyone for all your help, and hopefully what I listed above will help someone else.
Click to expand...
Click to collapse
found in this thread over here: http://forum.xda-developers.com/showthread.php?t=333260&highlight=Microsoft+Voice+Command&page=16
i'm using the original wm6 that came with th tilt. when I do push the button on my headset it's like all the handset volume is transferred to the headset
i had same issues then i tried the steps above and solved my problem i'm not on the original att rom anymore though i'm using dutty's dualtouch v3 rom. You should try those steps mentioned above should solve your problem if not then dunno sorry i went crazy my self trying to fix this problem then when i tried this solution it worked i was so happy all the headaches and times searching forums finally paid off LOL. Anyhow good luck.
Running Dutty's v2K fixed and . . .
no issues with MSVC 1.6 without hack. sometimes stops responding but either turning my BT off and on again, or SR fixes it. Using a Jawbone if that makes a difference.
Problem after updating to new ATT Tilt Rom
I cant use voice command through the headset anymore after upgrading the rom from HTC. What happens now is when I press the Bluetooth button it transfers any sound to the headset (Music playing from MP or in call voice) but will not allow me to use any Voice command functions.
Please HELP!!
Redundant...
Another dead thread that wouldn't have to be killed if the search function was used...
Sorry for posting here but it seems that experts spend their time here.
I have an '05 Acura TL. The phone will not initiate a call over the hands free if I dial from the phone. I have to dial the number, wait for the person to pick up, press the HF button on my steering wheel and say "Transfer". Then I can talk over the Bluetooth connection and speakers. There is no problem with incoming calls, only outgoing. I previously had a Samsung phone and this problem did not occur with that phone.
I am currently on new AT&T WM 6.1 ROM and had the same problem with the 6.0 ROM. I was hoping 6.1 would solve the problem but no luck.
Any ideas on how to fix this?
I have tried different radios.
Thanks in advance.
Ryoh said:
Sorry for posting here but it seems that experts spend their time here.
I have an '05 Acura TL. The phone will not initiate a call over the hands free if I dial from the phone. I have to dial the number, wait for the person to pick up, press the HF button on my steering wheel and say "Transfer". Then I can talk over the Bluetooth connection and speakers. There is no problem with incoming calls, only outgoing. I previously had a Samsung phone and this problem did not occur with that phone.
I am currently on new AT&T WM 6.1 ROM and had the same problem with the 6.0 ROM. I was hoping 6.1 would solve the problem but no luck.
Any ideas on how to fix this?
I have tried different radios.
Thanks in advance.
Click to expand...
Click to collapse
The problem was not that all the "smart people" hang out here, but rather that you have a very specific issue with a specific piece of hardware, and as such it is unlikely that there are many people who can answer your questions. Most "smart people" here also read the General Forum too.
Well...
...I'm not that smart but for as I ever had BT issues, and I can assure you, I've have plenty with my carkit, only one soft was able to fix all that for me and that was Jetware (http://www.jetwaremobile.com/) was able to solve it... Now it works like a charm,
the soft isn't free but you can download a trial first...
I use the HTC adapter with my ATT Fuze to listen to music in my car. When I unplug the adapter to get out of the car, my speakerphone no longer works. If I get a call, it will vibrate but not ring. If I adjust the volume, I don't hear the indication beeps. However, if I make or receive a call, I can hear them through the regular speaker, and they can hear me.
I've tried adjusting the volume everywhere possible, adjusting the audio profile, changing the ringtone, etc, but the only way to fix it is to soft reset. Needless to say, it is very inconvenient to have to reset my phone each time I get out of my car.
I did search the forums but couldn't find any solution. Unlike these people:
http://forum.xda-developers.com/showthread.php?t=526930&highlight=sound+headphones+aux
http://forum.xda-developers.com/showthread.php?t=508225&highlight=sound+headphones+aux
my phone does not show the headphone icon indicating that it still thinks the headphones are plugged in. It also will not allow me to use the TouchFlo Audio Booster, further evidencing the fact that it knows the headphones aren't plugged in.
I had to replace my phone for a different reason, so I have verified this problem on two separate physical units. On both I tried cleaning out the USB jack and wiggling the connection around as suggested elsewhere on the forum, but neither solved the problem. In the process of getting my old phone ready to send back to ATT I restored my stock SPL and ROM and verified that the problem still existed. Other than the stock stuff, I have experienced this issue on EnergyROM 2.0 41609 and 41709, EnergyROM 3.0 'Magic' 20090709, and EnergyROM 3.0 'Mercury' 20090722.
As suggested here:
http://forum.xda-developers.com/showthread.php?t=526930&highlight=sound+headphones+aux
I thought my Bluetooth stack may be causing the issue, so I flashed a new radio as well. I was originally using 1.14.25.35, and am now on 1.14.25.05, which NRGZ28 says is the best for his Mercury ROM. Still didn't fix it. I'm at a loss for what to do, and wonder if anybody else has come across a solution, or has any idea what the problem could be.
Any thoughts or suggestions would be greatly appreciated.
Inferno
im having same problem dude. Have you tried going to your audio recorder and recording yourself and then making a call. That helped get mine back the way its suppossed to be.
That worked. Very interesting... Does anybody have any idea why this might be the case? Is there a registry value somewhere that needs to be reset after I use the adapter?
NRG has a couple of little apps he includes with his ROMs, namely "Finger Menus OFF/ON" and "Notification Manager OFF/ON" that I assume just wrap up a registry value switch. Would it be possible to code the registry values I need into an app like this, so I can click a button and have my sound working again after I use the adapter? Any senior members willing to do this for me or guide me through the process?
And thanks for the tip Mr. Ewok.
Inferno
bump
The voice recorder trick doesn't work for me anymore for some reason. Anybody else have any suggestions?
Thanks,
Inferno
Hardware
hey,
I had exactly the same problem with my Fuze. I've never flashed anything but the stock rom. I sent it to PPC techs because I had them repair another problem. They told me it didn't have anything to do with the speaker or cables, but they "heated up the board" and it started working. I'm wondering if there's a manufacturing flaw (like a cold solder) involved.
BTW PPC techs didn't charge me anything but shipping to repair it (as it was under their warranty, even though it wasn't their fault). Nice guys!