Issue with A2DP Stereo Bluetooth and Making/Receiving Phone Calls

Hi All,

I upgraded from my Verizon Curve 8330 to the Verizon Tour 9630 (OS v4.7.1.40). I cannot seem to make/receive phone calls properly while streaming audio from the phone via A2DP Stereo Bluetooth.

I thought this issue may be related to the other Tour 9630 Bluetooth issue people are reporting and thought I may get help here. Verizon Tech Support and Blackberry both claim no one has reported this issue.

The following used to work on my Curve 8330, but does not work on the Tour 9630:

1) Connect to a A2DP Stereo Receiver (Blackberry Stereo Gateway)
2) Use the BB Media Player to play music over the A2DP connection
3) Try to make/receive a phone call using the phone itself (i.e. no bluetooth headset in use)
4) The A2DP streaming audio mutes/pauses automatically (as it should)
5) The phone indicates that the phone call is connected (e.g. it says "Connected" and the timer counts up
6) On the Tour 9630, people cannot hear me at all, and I either hear nothing or a buzzing sound on the phone's speaker

Note: If I manually pause the streaming audio from the BB Media Player BEFORE making/receiving the call, the phone call works as expected.

Anyone else have this issue?

The media player on tour is very wonky and has issues. Many of the so called Blackberry experts on various forums sometimes refuse to acknowledge this for whatever reason.

Try this:download unsynced media player Unsynced - Music Just for BlackBerry. use 8900 version. Tested with my 9630 and BB stereo gateway and works fine. The music will stop when message comes in and you have to hit play again- but- it won't lose it place and calls are handled fine on mine.
I tried unsynced with a few different A2DP BT speakers and most worked fine.

Thanks, I'll try Unsynced.

I also wanted to note that the same issue occurs when using Slacker Radio or PodTrapper. So, the issue is not just constrained to the BB Media Player application.

Can anyone try the same steps on their Tour 9630 and confirm the issue is common or just isolated to my phone?