Bluetooth Problems!
#16
10-12-2007, 09:49 PM
Originally Posted by mobilezen
Hmm I'm going to have to do some research and then respond back. That is interesting. When you upgraded the ROM, did you update the radio/ARM/etc?
Yes I did, that could be the possibility.
Why have a cooked one when the official AT&T WM6 ROM is available but you didn't hear that from me
Yes I did, that could be the possibility.
Why have a cooked one when the official AT&T WM6 ROM is available but you didn't hear that from me
#17
10-12-2007, 11:02 PM
Originally Posted by BlackGSedaN1027
Yeah but the official one has bloatware on it, which Im not interested in, plus the cooked ROMs have more memory left over & if I need CV, or MobiTv(or any other AT&T apps) I have the cabs to install.
It's easy.
#18
10-13-2007, 05:26 PM
Me too...
You guys beat me to this post - I'm glad I'm not the only one.
Here's some more data points:
Based on the fact that there's no problem with actual headsets that I've tried, I feel like it's the car. Also, I've tried to do the phonebook download (via the JETware extension) multiple different times with different settings, and haven't been able to get past about 20% before it fails. LAME.
Here's some more data points:
- I had an LG CU500 - no problem with normal BT headsets (Plantronics) or my G35.
- Got an LG CU500v - no problem with either type of BT hands-free.
- Got an 8925 (Tilt) - no problem with headset (Plantronics) but crappy with the G - exactly the same description as the OP's, where the initial call connect sucks, but turn off hands-free, then turn on hands-free from the car and it's fine.
- Re-flashed the 8925 to the HTC Kaiser ROM - no change - same as Tilt ROM above.
- Got the JetWare BT extension - no change to above.
Based on the fact that there's no problem with actual headsets that I've tried, I feel like it's the car. Also, I've tried to do the phonebook download (via the JETware extension) multiple different times with different settings, and haven't been able to get past about 20% before it fails. LAME.
#19
10-14-2007, 05:20 PM
A few items to add - the JETware extension has some configuration files available on their website for the Hermes/TyTN (though nothing for the TyTN II / Kaiser / Tilt), but nothing helped. It appears that some Audi people have a similar issue, but their connectivity problems are limited only to the first call. After that, it's ok - ours is for every call. Lame.
I've posted our issue on JETware's site:
http://www.jetwaremobile.com/forums/...hread.aspx#376
Let's see if we can get some attention.
I've posted our issue on JETware's site:
http://www.jetwaremobile.com/forums/...hread.aspx#376
Let's see if we can get some attention.
#20
10-14-2007, 05:56 PM
Same problem with tilt and G35
I bought the tilt the other day. THe bluetooth audio quality when paired with my G35 was unusable. Garbled and crackly.
My old 8525 with WM5 worked clear and beautifully.
I had to take the tilt back today. What a bummer.
I am back to using my 8525. Hopefully they will find a fix for this and I can upgrade at another time.
My old 8525 with WM5 worked clear and beautifully.
I had to take the tilt back today. What a bummer.
I am back to using my 8525. Hopefully they will find a fix for this and I can upgrade at another time.
#21
10-14-2007, 06:01 PM
Originally Posted by lisamel
I bought the tilt the other day. THe bluetooth audio quality when paired with my G35 was unusable. Garbled and crackly.
My old 8525 with WM5 worked clear and beautifully.
I had to take the tilt back today. What a bummer.
I am back to using my 8525. Hopefully they will find a fix for this and I can upgrade at another time.
My old 8525 with WM5 worked clear and beautifully.
I had to take the tilt back today. What a bummer.
I am back to using my 8525. Hopefully they will find a fix for this and I can upgrade at another time.
#23
10-14-2007, 07:58 PM
#24
10-14-2007, 08:16 PM
weird
I think that is an awful lot to go through.
In my car to answer a call, I just hit a button on my steering wheel and say hello.
But then callers can't hear me. I don't want to have to go through pushing extra buttons, when I didn't have to do that with my 8525.
I figure for $300 it should work properly.
In my car to answer a call, I just hit a button on my steering wheel and say hello.
But then callers can't hear me. I don't want to have to go through pushing extra buttons, when I didn't have to do that with my 8525.
I figure for $300 it should work properly.
#25
10-14-2007, 09:16 PM
Originally Posted by J. Diddy
I'm having bluetooth / phone issues and was wondering if anyone else has had something like this.
My phone connects fine, but when I make a call (or answer a call), the person can't hear me (through the speark in teh car or through the phone). If I select "Use Handset", then hit the phone button, everything works fine.
It's really weird - all other functions work fine. I can voice dial, the display shows me my signal strength, battery life, etc.
Any ideas what I can try?
My phone connects fine, but when I make a call (or answer a call), the person can't hear me (through the speark in teh car or through the phone). If I select "Use Handset", then hit the phone button, everything works fine.
It's really weird - all other functions work fine. I can voice dial, the display shows me my signal strength, battery life, etc.
Any ideas what I can try?
#26
10-14-2007, 10:23 PM
#27
10-15-2007, 07:08 PM
Nov 2007 G35 Journey with Nav/Tech/Prem.
Phone: Verizon Wireless Treo 700W.
Issue: When answering a call, I could hear the other person they could not hear me.
Lexus 2007 IS250 AWD + NAV
Phone: Verizon Wireless Treo 700W
Issue: None. Works find.
Volvo 2007 S40 AWD T5
Phone: Verizon Wireless Treo 700W
Issue: None. Works find.
Car or phone? You decide. The Treo 700W is not officially support by any of them. Interesting to note that on the IS250, it finds the phone in less than 5 seconds. On the G35 I am down the road a quarter of a mile before it finds it - and sometimes not finding it at all.
Phone: Verizon Wireless Treo 700W.
Issue: When answering a call, I could hear the other person they could not hear me.
Lexus 2007 IS250 AWD + NAV
Phone: Verizon Wireless Treo 700W
Issue: None. Works find.
Volvo 2007 S40 AWD T5
Phone: Verizon Wireless Treo 700W
Issue: None. Works find.
Car or phone? You decide. The Treo 700W is not officially support by any of them. Interesting to note that on the IS250, it finds the phone in less than 5 seconds. On the G35 I am down the road a quarter of a mile before it finds it - and sometimes not finding it at all.
Last edited by Adam Zapple; 10-15-2007 at 07:11 PM.
#28
10-15-2007, 07:44 PM
Originally Posted by Adam Zapple
Nov 2007 G35 Journey with Nav/Tech/Prem.
Phone: Verizon Wireless Treo 700W.
Issue: When answering a call, I could hear the other person they could not hear me.
Lexus 2007 IS250 AWD + NAV
Phone: Verizon Wireless Treo 700W
Issue: None. Works find.
Volvo 2007 S40 AWD T5
Phone: Verizon Wireless Treo 700W
Issue: None. Works find.
Car or phone? You decide. The Treo 700W is not officially support by any of them. Interesting to note that on the IS250, it finds the phone in less than 5 seconds. On the G35 I am down the road a quarter of a mile before it finds it - and sometimes not finding it at all.
Phone: Verizon Wireless Treo 700W.
Issue: When answering a call, I could hear the other person they could not hear me.
Lexus 2007 IS250 AWD + NAV
Phone: Verizon Wireless Treo 700W
Issue: None. Works find.
Volvo 2007 S40 AWD T5
Phone: Verizon Wireless Treo 700W
Issue: None. Works find.
Car or phone? You decide. The Treo 700W is not officially support by any of them. Interesting to note that on the IS250, it finds the phone in less than 5 seconds. On the G35 I am down the road a quarter of a mile before it finds it - and sometimes not finding it at all.
#29
10-16-2007, 05:41 PM
Originally Posted by Adam Zapple
Nov 2007 G35 Journey with Nav/Tech/Prem.
Phone: Verizon Wireless Treo 700W.
Issue: When answering a call, I could hear the other person they could not hear me.
Lexus 2007 IS250 AWD + NAV
Phone: Verizon Wireless Treo 700W
Issue: None. Works find.
Volvo 2007 S40 AWD T5
Phone: Verizon Wireless Treo 700W
Issue: None. Works find.
Car or phone? You decide. The Treo 700W is not officially support by any of them. Interesting to note that on the IS250, it finds the phone in less than 5 seconds. On the G35 I am down the road a quarter of a mile before it finds it - and sometimes not finding it at all.
Phone: Verizon Wireless Treo 700W.
Issue: When answering a call, I could hear the other person they could not hear me.
Lexus 2007 IS250 AWD + NAV
Phone: Verizon Wireless Treo 700W
Issue: None. Works find.
Volvo 2007 S40 AWD T5
Phone: Verizon Wireless Treo 700W
Issue: None. Works find.
Car or phone? You decide. The Treo 700W is not officially support by any of them. Interesting to note that on the IS250, it finds the phone in less than 5 seconds. On the G35 I am down the road a quarter of a mile before it finds it - and sometimes not finding it at all.
New item - I'm beginning to have quality issues with my Plantronics headset too... the plot thickens...
#30
10-16-2007, 07:05 PM
Registered User
Join Date: Sep 2007
Location: Richmond, VA
Posts: 110
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Adam Zapple
Car or phone? You decide. The Treo 700W is not officially support by any of them. Interesting to note that on the IS250, it finds the phone in less than 5 seconds. On the G35 I am down the road a quarter of a mile before it finds it - and sometimes not finding it at all.
I have an old Motorola E815 and the bluetooth works perfectly and the sound is quite clear. The car recognizes it and connects in just a few seconds.
I remember reading somewhere that Verizon would fiddle with the bluetooth in their phones to prevent you from establishing certain bluetooth connections. Don't know if it's true anymore or if other wireless companies are doing it. Just a thought.