01/18/2011, 03:07 PM
|
#1 (permalink) |
|
Member
![]() Join Date: Sep 2009
Posts: 15
Likes Received: 0
Thanks: 1
Thanked 0 Times in 0 Posts
|
Hello.
I got the Palm Pre and just got an 2010 Acura TSX (no navi). I have found that when I use the phone to start a call, it won't automatically start in the handsfree mode (it will start in phone mode). This is very anoying, since you have to manually change from phone to bluetooth every time you make a call to someone not on your short voice recognition list. In my previous car ( I had a Kenwood bluetooth enabled radio) when you made a call it automatically went to the bluetooth speaker. I was wondering if anyone has encountered the same problem and if there is any solution it. Thank you, |
01/18/2011, 03:29 PM
|
#2 (permalink) |
|
Member
![]() Join Date: Aug 2009
Location: Omaha, NE
Posts: 49
Likes Received: 4
Thanks: 0
Thanked 1 Time in 1 Post
|
I have a 07TL, and usually if I have some sort of problem, deleting the phone, and re-pairing it seems to help.
But I have never had this problem. Mine goes directly to the bluetooth. Few questions: The way I interpret your post, it works fine when you have someone saved with voice recognition? Are you saying "Call" or "dial" to the system? There may be a difference. I always say "Call", then say the number. And it works fine. If it works correctly with the name voice recognition, I would think it should work to just dial a number straight up. |
01/18/2011, 03:52 PM
|
#3 (permalink) |
|
Member
![]() Join Date: Sep 2009
Posts: 15
Likes Received: 0
Thanks: 1
Thanked 0 Times in 0 Posts
|
Thats exactly it. If I use the voice recognition program, it works fine and goes directly to handsfree.
If, on the other hand I use the dialer on the phone to dial out (or the speed dial on the phone) the call starts out in phone mode and I have to change it to handsfree on the phone before I can use the speakers. As you can imagine, that is very anoying when you have the phone on the Tombstone and have to go thru the change before talking. |
04/06/2011, 02:16 PM
|
#5 (permalink) | |
|
Member
![]() Join Date: Apr 2011
Posts: 10
Likes Received: 0
Thanks: 0
Thanked 3 Times in 2 Posts
|
Quote:
By the way, I have an 07 TL so I feel you. I always forget that the phone does this, you'd think I would have learned by now. :-P |
|
04/06/2011, 02:24 PM
|
#6 (permalink) |
|
Moderator
![]() ![]() Join Date: Jan 2010
Posts: 15,150
Likes Received: 958
Thanks: 3,804
Thanked 3,911 Times in 2,777 Posts
|
its the same as answering a call. If you answer from the phone, that's where the call goes. If you answer by tapping a bluetooth headset, it answers to the headset.
On my Garmin GPS, if I dial the call from the GPS, it initiates through the GPS and my car stereo. If I dial from my handset, it initiates the call from the phone. That's the way I want it to work, so I don't see the issue. |
11/01/2011, 02:45 PM
|
#7 (permalink) |
|
Member
![]() Join Date: Feb 2010
Posts: 7
Likes Received: 0
Thanks: 0
Thanked 0 Times in 0 Posts
|
I have an 08 MDX (no navi)and have this exact same issue with the VZW PrePLus and now the Pre2...absolutely irritating.
Calls coming in go directly through the handsfree link. Making an outgoing call requires me to pick up the phone and hit the bluetooth option on the phone itself for it to go through the car. In addition, you have to wait for the call to actually connect, then it gives you the option to press the bluetooth icon and then select bluetooth...two presses required. This isn't safe. I travel for business and rent cars regularly...can pair my phone easily with these cars and never have to hit the bluetooth button on the phone for outgoing calls. So, it is either an Acura issue or combined Acura/Palm compatibility issue (might be a no navi issue). yes, the "transfer" command works, but you really shouldn't have to do that. I am looking around to see if I can find a solution. Will update here if I find anything. |
![]() |
|
| Tags |
| acura, bluetooth |
| Thread Tools | |
| Display Modes | |
|
|



