2013 BRZ Limited + Samsung Galaxy Note 2 Bluetooth issue

[JS + BRZ]

So, my car is 4 months old. The phone has been paired up and ran fine until last Saturday.

When I turn on the car, the phone connects fine. It plays the songs through the Bluetooth.

However, whenever I call someone, the display says it's calling, yet the call sound doesn't come through the speakers.

When the call is connected, it still doesn't make any sound. I have manually turn off the Bluetooth headset and talk through the phone.

Does anyone have experienced this problem?

Not sure if this is related, but I do have a separate Nexus 7 tablet which is running Torque Pro app connected to OBD via Bluetooth.

Thank you guys.

[Churnobyl]

My Samsung GS4 drops Bluetooth connection all the time. I have a feeling the Bluetooth components in this car are pretty much garbage. Fortunately I like the car so well its not really that big of a deal. I didn't have Bluetooth in my last car so not having it reliably in this one isn't a deal breaker. Maybe the newer generation Samsung's will somehow compensate for that shoddy car connection.

[supramkivtt2jz]

I have an S3 that always worked perfectly with the base pioneer headunit until Samsung pushed the last update. Now its all fucked up. I giggle and feel like the luckiest girl in the world when it connects.

[JS + BRZ]

Ah.. maybe my phone updated the software over the weekend?

Before it worked fine except it dropped its connection 2 times within first 5 minutes. For the most part, I had no problem with it.

That's the crappy part. If it didn't work from the beginning, it wouldn't have bothered me much.

[N1rve]

Are you running Android 4.4? Are you using Power Saving Mode or any power saving apps?

I have a Galaxy S4 and I've noticed there is a delay with my FRS and the bluetooth. My GS4 will say "Dialing" but there will be like a few second delay before it goes through my car.

I've never had a call drop though.

[JS + BRZ]

Originally Posted by N1rve

Are you running Android 4.4? Are you using Power Saving Mode or any power saving apps?

I have a Galaxy S4 and I've noticed there is a delay with my FRS and the bluetooth. My GS4 will say "Dialing" but there will be like a few second delay before it goes through my car.

I've never had a call drop though.

I just checked and it's running 4.3 version.

But that's the thing though. I had a little delay too but never had any problem with the sound not coming through.

The call is on, only the sound is not coming through the speakers. It's weird.

[supramkivtt2jz]

Originally Posted by JS + BRZ

I just checked and it's running 4.3 version.

But that's the thing though. I had a little delay too but never had any problem with the sound not coming through.

The call is on, only the sound is not coming through the speakers. It's weird.

what hardware version? im android 4.3 hardware version i535.10. 4.2 on i535.10 worked perfectly before.

nvm, i read youre rocking a galaxy note 2. different phones.

[N1rve]

Originally Posted by JS + BRZ

I just checked and it's running 4.3 version.

But that's the thing though. I had a little delay too but never had any problem with the sound not coming through.

The call is on, only the sound is not coming through the speakers. It's weird.

I guess wait for the 4.4 Update...hopefully that will resolve the issue.

Do you have another phone to test? I believe you have a wife?

[2pt5RS]

My Nexus 5 was just having some issues last week. removed it from the unit, re-synced it and it's been solid ever since.

You don't, by chance, have a headset jack in the headset port, do you? I had a samsung that did that with the in-car bluetooth if I were using the auxilliary port. For whatever reason, the aux in takes precedence over the bt.

[DoomsdayJesus]

Here's some good troubleshooting tips (I have a GS4 and eliminated all problems, Samsung has a bit of a tricky bluetooth setup).
1) delete all pairings. All of them. On your phone and head unit.
2) Change the bluetooth setting from headunit initiating the connection to the phone initiating (there is no difference in connection time when the car/headunit is turned on). This ended the frequently dropped connection for me.
3) Check your settings, ensure your car's bluetooth profile after pairing has call audio and media audio checked on your samsung device.

Fun tip: If you use google now a lot, long pressing the menu button and saying "ok google" gets the voice command working, once you master the voice commands you never have to touch the phone while driving again. You can send texts, check traffic to home/work, all without touching the phone, and it uses your car's microphone.

Helps to turn down the music, though.

[Struckbylitenin]

my verizon note 2 has never had issues... Though I am rooted and running AllianceRom.

[JS + BRZ]

Originally Posted by DoomsdayJesus

Here's some good troubleshooting tips (I have a GS4 and eliminated all problems, Samsung has a bit of a tricky bluetooth setup).
1) delete all pairings. All of them. On your phone and head unit.
2) Change the bluetooth setting from headunit initiating the connection to the phone initiating (there is no difference in connection time when the car/headunit is turned on). This ended the frequently dropped connection for me.
3) Check your settings, ensure your car's bluetooth profile after pairing has call audio and media audio checked on your samsung device.

Fun tip: If you use google now a lot, long pressing the menu button and saying "ok google" gets the voice command working, once you master the voice commands you never have to touch the phone while driving again. You can send texts, check traffic to home/work, all without touching the phone, and it uses your car's microphone.

Helps to turn down the music, though.

This worked!!!!

Thank you very much.

[DoomsdayJesus]

Glad it worked, there's some reason why it just works poorly when the head unit initiates the connection. I tried every settings permutation until it worked.

[Eurasianman]

Originally Posted by 2pt5RS

My Nexus 5 was just having some issues last week. removed it from the unit, re-synced it and it's been solid ever since.

Originally Posted by DoomsdayJesus

Here's some good troubleshooting tips (I have a GS4 and eliminated all problems, Samsung has a bit of a tricky bluetooth setup).
1) delete all pairings. All of them. On your phone and head unit.
2) Change the bluetooth setting from headunit initiating the connection to the phone initiating (there is no difference in connection time when the car/headunit is turned on). This ended the frequently dropped connection for me.
3) Check your settings, ensure your car's bluetooth profile after pairing has call audio and media audio checked on your samsung device.

This stuff right here. My phone was running fine for a while and then all of a sudden, BT started dropping in and out. Clearing out the BT paired devices on the head unit and the phone and re-syncing resolved my issue. Running Verizon Wireless Samsung Galaxy S3 with stock Android 4.3 and no issues.