[CrackBerry Question]

So yeah, my phone is already paired with my Alpine receiver, but whenever making calls/answering calls, the call goes through the handset speakers instead. I have to manually switch the audio and select bluetooth so that it will play through my car stereo. Occasionally this happens, and I will have to delete and re-pair. HELP!

[PantherBlitz]

Sounds more like an issue with the stereo, not the handset. Does it answer with a button on the radio or on the steering wheel, or do you have to touch the phone to answer calls?

[bloke1]

When a call comes in, it rings through the car stereo, I will then press the answer call button on the stereo. Call goes through, but the problem is that the audio output used is the handset's speaker. This used to work properly with my Sony Xperia before this.

[Lusitano17]

Have you enabled "hands free calling " toggle?

If you haven't......In Bluetooth device list hold device name and details window will open up.

[bloke1]

Yes, it's enabled. It's just that I need to toggle the audio button to use the bluetooth output everytime while driving.

Funny thing is my music plays through the car stereo. As well as the voice assistant.

[Rilock4]

Unfortunately, this is not an uncommon issue while using Bluetooth with any device out there. I work for a dealer and having to unpair and re-pair a phone all the time to have all features work normally again is normal. I normally see this issue with iPhones and people who have aftermarket radios.

Posted via the CrackBerry App for Priv

[bloke1]

Update : Okay, now switching it to Bluetooth audio does not work. No sound from the stereo.

[bloke1]

This issue is apparently intermittent. I restarted the phone, first call uses the bluetooth audio by default, second call also, but the third call is defaulted to handset audio.

[CrazyJo82]

What about the car setting? I know my kia has the option to make "private" calls and it routes back to the handset.

Posted via CB10

[bloke1]

I'm using the Alpine UTE-42BT, no such setting is available.

[bloke1]

Issue solved. Turns out to be the call recorder app messing around.