First off, apologies if you read this in the i730 thread. I hope that broadening the subject matter might get a response that will help fix the problem since if I can't reliably use my car's Bluetooth, I will have to get a new phone, and I love my i730 too much to give up easily.

I hope that someone has an idea on how to either upgrade or modify the Bluetooth stack (or whatever it takes) to allow my phone to work once again. The irony is that it worked extremely well when the phone was using WM2003, but though almost everything else is better with WM5 somehow the Bluetooth connection part is unusable.

This concerns my '04 Acura TL and recently upgraded i730 (to WM5). I have been able to pair without problem (multiple times), but virtually every call, a few minutes into the conversation I can no longer hear through the Acura's speaker, nor can I be heard. I quickly fumble for the phone and can continue the call there, though the Acura's display indicates it thinks it is still handling the call. This used to happen very rarely under WM2003, but I'd always get an HFL announcement along the lines of, "Bluetooth connection has been lost...".

In addition, a short call that hasn't yet disconnected will often fail to hang up with the appropriate steering wheel button.

I even tried Jetware's software:

http://pdaphonehome.com/forums/samsu...sfreelink.html

...hoping that this might modify the Bluetooth stack. Unfortunately, I still have the same problems, though I like having the battery and signal strength shown.

This is not due to add-on programs, since it happened right after upgrading the phone, though I do have several programs running at this point.

I would greatly appreciate any help or advice here. Searching both here and the pdaphonehome.com forums did not yield any answers. Thanks in advance.

 

I've had that happen several times with my Blackjack and even with my Treo 650 before that. I hadn't considered it a software issue, though. I thought it may have been related to a weak Bluetooth signal between the HFL and the handset, but you're probably right that it is the software. I don't have an answer for you, but I'll certainly be watching this thread.

BTW, the link in your post appears to be broken. From what I can see of it, though, it looks very interesting to me.

 

Thanks for your reply. I consider it a software problem only because my phone worked so well while running WM2003.

Sorry about the link - here is the correct one:

http://www.jetwaremobile.com/

Still looking for advice - anyone?