2014 limited Bluetooth sound issue

[13sr54runner]

Hello everyone, my father recently went from a 2011 trail to a 2014 limited. The truck is fully loaded and has the jbl audio system. Superb 4runner as usual but he seems to be having trouble with the hands free cell phone speaker. It sounds very far away and not as clear and crisp as it did in his trail and currently does in my 13 sr5. It sounds like the calls are coming from one speaker under or around the glovebox. Does anyone know if there is a setting to fix this or experience this problem? I have already attempted to play with the audio settings but have had no luck. If not, it may be a call to the dealer.

 

[Tleahcim]

Not sure if this is all that helpful, but I know that my 2014 LE Bluetooth audio for phone calls/Entune apps outputs from the driver's side tweeter. I checked the "General" settings for Entune and I was only able to adjust the volume and not the L/R balance so maybe the speakers are wired incorrectly? My crude troubleshooting method would be to play some music via Bluetooth and adjust the balance for that to see if it switches between L/R correctly.

 

[13sr54runner]

Not sure if this is all that helpful, but I know that my 2014 LE Bluetooth audio for phone calls/Entune apps outputs from the driver's side tweeter. I checked the "General" settings for Entune and I was only able to adjust the volume and not the L/R balance so maybe the speakers are wired incorrectly? My crude troubleshooting method would be to play some music via Bluetooth and adjust the balance for that to see if it switches between L/R correctly.

Ahh ok well if the sound in this truck sounds like it is coming from the glovebox, that should hopefully mean that the l/r balance is off if your audio comes from the driver side. Thank you

 

[rigtec]

"... I have already attempted to play with the audio settings but have had no luck."

Hi 13sr5'

Not sure if this is it but you can try "un-pairing" the cell phone(s) w/the truck's bluetooth network, and then 'pairing' it again; could just be a poor file 'loading' issue.

cheers!