I am sure that I am not the only person experiencing this. I am hoping someone has figured out a fix for this. I am not smart enough to figure this one out on my own. When I use the bluetooth feature of my Prius, there is a delay between the time the call connects and the hands free activating. Because of this, when I call someone, they answer and have to repeatedly acknowledge that they are on the phone. This is not an occasional thing. This happens every time without fail. Sometimes, because of the delay, the person I am calling hangs up before I can even say hello to them. Here is what I am doing, just to make sure I am explaining myself clearly. 1. I dial a number on my phone while bluetooth is enabled. 2. The party I am calling answers. 3. There is a delay between the time the person I am calling answers and the time the call transfers to bluetooth hands free. I can't imagine that this is by design. I have lost so many calls this way that I have stopped using the bluetooth hands free feature in my Prius. I called my local Toyota dealership about this, but they have no answer. This is not surprising since they don't seem to know anything about the Prius. I'd really appreciate it if someone could tell me if this can be rectified. If so, how? Thank you in advance.
I know what you mean. Now that I have had 2 different phones and service providers that it varies by phone and/or service provider. It is more noticeable with Cingular and the Treo than it was with Verizon and v710. Happens with incoming calls as well. It is less noticeable when using the one touch on the MFD. That may be because the car has to set up the link first then dial. With Verizon it also varied from day to day and time to time during the day. I would imagine that may have something to do with how busy the network is? What phone do you have, service provider, Car package and year?
<div class='quotetop'>QUOTE(05PriusDriver @ Apr 1 2006, 11:55 AM) [snapback]233459[/snapback]</div> What kind of phone do you have?
The only way I know of to get around this is to initiate the dialing from the car. Though, I have had some weird instances where the network droped the call, the phone hung up, but the prius didn't disconnect. the next call I made from the phone in this circumstance was pre-connected and did not have the delay. I know of no way to predicably and reliably do that, though.
I have a Motorola v330 using T-Mobile. My car is an '05 package 6. I am not sure what, if anything the network would have to do with this problem. I am no expert, but from what I am experiencing, I think that the problem is between the bluetooth on the phone connecting to the bluetooth of the Prius. The call is going through and connecting, but the person answering the call is repeatedly waiting for my reply while I am waiting for the car to engage the connection with the phone via the bluetooth. I am not dropping calls, and I can be heard clearly once connected. Dialing from the MFD is not always possible, for example if the car is moving. I have to initiate the call from the phone handset. Thank you for the replies.
I had the same problem in my 2004 with a Treo 650 and found a cure that makes it work perfectly - buy a 2006. Toyota changed something in the 2006 Bluetooth system that makes the connection instant whether I'm dialing from the MFD or the phone. This is one of the most satisfying benefits of moving to the 2006.
<div class='quotetop'>QUOTE(David @ Apr 2 2006, 11:10 AM) [snapback]233753[/snapback]</div> That is one very expensive upgrade! :lol: I think I'll live with the problem. Trading to the '06 model after owning this model for only 10 months is a bit extreme for me.
<div class='quotetop'>QUOTE(05PriusDriver @ Apr 2 2006, 07:29 AM) [snapback]233748[/snapback]</div> I also use T-Mobile, but with a Motorola V600 and have never experienced the delay that is the subject of this thread. My guess is the network has nothing to do with it but the specific phone is the culprit. David
I also have this problem in my 05 with a Nokia 6230 (Cingular). I have already ordered my 2006, so I'm REALLY HAPPY to hear that it's fixed in that version! I have also had the occasional situation where the phone & car LOSE each other, and don't find each other again until I power cycle the car. (So I know it's not the phone. I can even tell the phone to LOOK for devices, and it says it cannot find any!) It's like the car gets confused and stops looking for paired devices. Happens maybe once every 2-3 months? The only solution I have found is to power the car off and on. No biggie.
<div class='quotetop'>QUOTE(Armature @ Apr 3 2006, 01:07 PM) [snapback]234275[/snapback]</div> Correct. It's your phone model, not the car.
its the way the phone treats handsfree my old sony-ericsson 610t would have a 1.5 second delay my new T-mobile MDA has no delay because it never disconnects, it keeps the connection open until power is cut
I have a 2006 and have this problem too- so its not the car model year! I have a Verizon Razr and 2006 pkg. 7
<div class='quotetop'>QUOTE(05PriusDriver @ Apr 2 2006, 10:29 AM) [snapback]233748[/snapback]</div> There is sort of a way around that part, but its a fair bit of extra work. First, set up anyone you would like to be able to call as memory points in the nav system. The points don't have to have anything to do with the actual location of you callee. You can then attach a name and phone number to each memory point. Then, while driving, use the nav override sequence. Then go as if you were going to set a destination from a memory point to the callee. Then you get to the map screen where it lists the destination on the top, but before you commit the destination, there will be an info button beside the destination name. Click that to get to the screen with the destination details. There will be a phone icon beside the phone number. Click that to start the call without the connection delay. This will also work from the map screen if you can see the intended memory point. If you click it, you get the same info button available. It's a bit of a pain, but it works.
<div class='quotetop'>QUOTE(hawkjm73 @ Apr 15 2006, 10:51 AM) [snapback]240213[/snapback]</div> Clever
OK... so from the replies it appears that it is not the model year of the car that is the culprit. It seems to be the phone. This would make sense because I also have a bluetooth earpiece that I use with the phone. I have no problem with that at all. It seems to be a problem with the interface between the phone and the car. I guess its just another annoyance in life that I am going to learn to live with. I am thinking about looking at the new Hybrid Camry. Anyone have any thoughts on that Camry?
<div class='quotetop'>QUOTE(David @ Apr 2 2006, 07:10 AM) [snapback]233753[/snapback]</div> I just bought my 2006 Prius last week. I registered the bluetooth using my Treo 650. It was working fine up until now. Every now and then I had to re-register the signal. I now cannot get a connection. My phone shows as connected, but my Prius is not connecting. Any suggestions ? David
