When streaming audio from my gf's lg g2 to her car the left channel audio is super low, maybe half power. We tried 2 other phones that both streamed audio equal on both channels. Couldn't find anywhere in the app or phone settings that would control balance levels, and now I'm thoroughly confused. Anyone dealt with this before?
Announcement
Collapse
No announcement yet.
weird Bluetooth audio issue - lg g2 + car
Collapse
X
-
Sounds like an issue with the phone, but wtf do I know. lol
Have you tried listening to music on the phone with headphones? Wondering if the balance is off with those as well.
Only other thing a moron like me would try would be to delete the profile (or whatever it's called) for that phone in the car then set it back up. Of course, that's just the standard IT "have you tried restarting" method.
Comment
-
I agree its in the phone, however for the life of me can't tell where or how a balance issue like that would show up. i went into the music player(s) and verified that none of them have a balance setting. we've deleted and reinstalled the phone to the car multiple times. other devices will pair and play full audio in both channels.
i have not verified the audio via corded connection is the same, thats a good test i suppose but i can't say for certain that the audio follows the same path to be tx via BT instead of physical connection.
Comment
-
I appreciate it. Going to try a few more things and then head to the phone store and see if we can get them to refund/trade us something. If i can prove it's the phone, that is.
I did also try switching between "phone audio" and "media audio" settings in the BT menu with no change. was really hoping one of those would be the magic fix.
Comment
-
Has it done it since the beginning? Any thought on wiping the phone clean and starting over? I had a weird issue with my phone (Galaxy S5) where streaming over Bluetooth would cause music to "stutter". Google'd it and found other people complaining about the same thing and that booting up into Recovery Mode and clearing the cache fixed it for a lot of people. Maybe gave that a try.
Comment
Comment