I've had an '04 TL for 6 years and have never had any issues with the way any of my phones interact with the Bluetooth system. (I did have problems with static/cracking, but that's totally different.) About a month ago, VzW pushed out an update that took my Droid phone from Android 2.3.3 to 2.3.5. Now, the Bluetooth does a strange thing where the car will show that the Bluetooth is connected, but the very first phone call I initiate from the steering wheel buttons, it says that there is no phone connected. Try again 5 seconds later and it makes the call just fine. Incoming calls still work just fine and no issue there. It's only a minor nuisance, but I'd like to fix this.

Anyone else experience something like this?

Any ideas? I wouldn't mind rolling back the update, but I'm not sure how to do that either.

 

I also have Verizon, but I had a similar issue when I had my Droid 2 Global. My bluetooth was connected to the car(icon) but as I tried making a calling it sounded high pitched static noise or than say "no phone connected" after I hung up. Strange I thought, this was also after I got an update not the one you had but an earlier version(there is always a little hiccup in new updates).

But it would intermittently throughout the week not connect to my phone even though the icon appeared, so I just:
1st: just disconnect and erase my phone from the car
2nd: turned off my phone(hard reset-->battery pull)
3rd: power it up, reconnect my phone to the car again(PITA)

Result: no more intermittent loss connection.

That is just if you want to go through that, but it worked for me. May or may not work for you.
Now have a Galaxy Nexus connected to my car and its an improvement over my D2G Bluetooth connectivity.