I'm going to guess that your G does not have navi... Is that accurate? The bluetooth unit on the G's with navi is inferior to the one on those without and most of the problems with various phones only occur on the cars with navi. If you do have navi, then I'm interested in why it would work when the diamond does not.

Cheers
T1328

 

My G does have the Navi. I will test the beam option and see if the car sees this. I never selected it in the past as beam usually represents IR from device to device.

Thakns for the info!

 

Dude,
The beam worked awesomly... I was able to transfer all my contact form the htc diamond to my car with no problem...

Thanks again for the tips!

 

good info, ill have to try it when i get my 37.

 

Oops .... sorry, missed the navi reference in the OP.
You are correct mine is non-navi.

 

Hi,
Anyone get the HTC Fuze (AT&T's version of the Touch Pro)? The phone can connect to the car's Bluetooth with out any problems, but, when I make a call or take a call, it sounds like there is major studdering, or, like skipping on a cd/vinyl record.
Anyone have this symptom?

Thanks

 

I'm having the same problem with the Fuze. Skipping/echo from the bluetooth connection. Changed bitpool speeds to several different settings and nothing seemd to work. Had a palm centro before and it worked fine. If i don't find a fix i'll be buying the unlocked palm pro. Seems like if the centro worked, the palm pro should too.

 

It's the bluetooth stack on WM6. A quick fix is to "transfer to headset" when a call comes in then immediately transferring it back to the car.

Or, if you're up to it, downgrade to WM5.

 

I have WM5 on my HTC (AT&T 8525). Although it works, the BT stack on my phone needs a work around to beam ALL contacts. This capability sounds like it is built into WM6.

 

It doesn't work on my Shadow, but in all honesty i would much rather have the seamless bluetooth signal from WM5 when on a call than WM6's alleged all-contacts beaming.

 

Hey guys sorry to resurrect such an old thread but I thought you guys might want to hear about this.

I recently got an AT&T (HTC) Fuze and synced it to my car. I had heard about the issues here with not being able to answer calls from the car with out using the handset first. Well the first day I had it I used the stock ROM and I too had that problem but I could only deal with the AT&T crap on there for so long. I headed over to www.xda.com and check out their forums and after doing some reading I reflashed my ROM. I used the ROMeOs conFUZEd edition ROM and since have had no problems answering calls. You will see something there about changing radios but I kept the stock one. If you guys need more info please feel free to PM me and I can direct to the appropriate links.

 

I have an AT&T Fuze, and have it synced with my G35 (navi & prem). I make and receive calls using the car controls with no problems. When a call comes in, I get caller ID info. I have also transferred phone contacts from the Fuze to the car with out problem.

If people are having a problem answering calls using the car controls with their Fuze, it's probably because they have Voice Command Phone announcements turned on. There is a known problem with the Fuze, and any Bluetooth device when it comes to answering calls. If you have Voice Command Phone announcements turned on, and you try to answer a call using a Bluetooth device, then the person on the other end can hear you, but you can't hear them. At that point, you have to transfer the call from the Bluetooth device to the Fuze handset, and then transfer it back to the Bluetooth device.

Turn off Voice Command Phone announcements, and your Fuze should work just fine with the G35 phone controls.