Just FYI for anyone with similar problems:

I was having my HFL fail to connect with both my Blackberry 8320 and Blackberry Bold for about the last 2 months. It seemed pretty random, restarting the phone didn't help, restarting the car helped usually. I could usually manually connected the phone successfully without restarting either.

Then I disabled encryption on the bluetooth connection and it all works flawlessly. It's connected up every time without fail.

Just something to try on your phone if you have similar problems. Drove me nuts for awhile so I wanted to document it in case anyone else was having similar problems.

 

Thanks. I tried this yesterday and was experiencing similar problems. It worked for me.

 

i been having the same problem for about a month and just spoke to acura service about it and they said you need to erase your phone from your cars bluetooth and also from your phone and do it all over from scratch.........it worked for me.

 

i have a wierd problem. i am not able to dial from HFL i mean its works first call perfectly and than i am not able to make calls at all i do receive calls and able to answer it... but the only problem is not able to dial.. i say 123456789 Dial its shows dailing.. but nothing happens...

 

I've heard this before...but never heard an actual explanation of what they think the problem is. Translation - they are giving you some suggestion they hope works because they have no idea what the problem is.

 

I am having this problem with my Blackberry Bold. I tried disabling encryption and that seemed to work for a day, and then the problem returned. I noticed that the only time the bluetooth will drop and switch to handset audio is when the Blackberry says "call forwarding - Conditional" on the screen. Not sure what that is about, but if it doesn't do that, the bluetooth works fine, otherwise i have to manually specify on the device to switch the audio back to HFL.

Any other ideas?

 

I haven't observed the call forwarding conditional message. It sounds like something else is going on there. Have you upgraded the blackberry bold software at all? You may want to do that and see if it helps.

Also, see the following link for some help.

http://www.blackberryforums.com/gene...nditional.html

Let us know what you end up with. If you still have problems can you try another phone that you think should work? The goal would be to determine if it is the car, or the phone. Plus, if you go to the dealer, they will likely immediately claim it is the phone...regardless of what the real problem is.

 

I have a problem with my Blackberry Curve 8330 not connecting to my HFL when I'm on the phone walking to my car and get in my car and start my car up .. it should automatically transfer the call over to my HFL (my other bluetooth phones did this .. sanyo, samsung...) but this doesn't.

any clues?

Also, when i set the security option on my Blackberry, i have the options "HIGH, and HIGH+Encryption" ... and in the HFL setting, i have disabled encryption... any other things to do to improve connectivity?

 

I have a Curve and mine never connected to the HFL if I started the car during a conversation. I've always had to hit the button and say "Transfer" before my convo would come over the speakers. This may have to do with the HFL and not the phone since it would automatically cut over to the speakers in my friends Lexus IS. Same for not being able to dial a number from the phone when linked. I really don't like it but have learned to live with it. I will dial a number and say "Transfer" to have it come out of the speakers or I would dial the number and hang up the phone. I will then hit the button and say "Redail". I used to it now.

Also, I've seen the "Conditional Forwarding" message on my AT&T BlackBerry when traveling out of my home area sometimes but I don't know what it means. I do know that it is not related to the car though.

 

I had an 8300 curve and it worked flawlessly with the HFL. No problems until I started using the bold. I am running the latest bold OS.

 

upgraded from .185 OS to .216 and it is now working fine. Finally!