Hi there! I recently upgraded from the Samsung Galaxy Nexus to the SIII and I noticed something.. annoying. One thing I always do with my phone is stream bluetooth audio to my car's in dash system (which is a Pioneer X930-BT if it helps...) but the audio being streamed is so UNBEARABLY low, that I have to crank up the amp to levels that make the audio sound terrible and even then, there is barely any bass or depth to the sound unlike when I used my Nexus. I have tried everything, uping the volume on the phone (obviously), repairing, using the phone only as a media device, and fiddling with settings. The ROM I am using is CM10 Final, any help would be much appreciated!
Actually for those interested it seems I found others with the same issues: http://forum.cyanogenmod.org/topic/61504-terrible-bluetooth-stereo-audio-quality/
you could've just went to the cm10 thread hear and read the over 100 posts about the bluetooth audio issues. you would've seen that you are not alone.
task650 said:
you could've just went to the cm10 thread hear and read the over 100 posts about the bluetooth audio issues. you would've seen that you are not alone.
Click to expand...
Click to collapse
Yup! You are correct. But for some reason my brain has been hard-wired to think Android Forum? Better head to XDA automatically and forget about all other websites.
Related
Has anyone figured out why high frequencies get garbled since the EG30 kernel? That's the last one I remember that did not garble. From what I've been told, the bluetooth stack is built into the kernel, not the ROM.
Could someone please clarify and perhaps offer a solution?
How about very low volume on the BT ? I paired my phone with the BT in my 2012 Ford (with SYNC) and the music plays perfectly, but I can't hear S#!T during a phone conversation...
peryp9 said:
How about very low volume on the BT ? I paired my phone with the BT in my 2012 Ford (with SYNC) and the music plays perfectly, but I can't hear S#!T during a phone conversation...
Click to expand...
Click to collapse
I have a 2011 Explorer with SYNC and if memory serves, it considers the BT music volume and in-call volume 2 separate things. Once a call is made, you have to turn up the volume again to get that where you want it. Once it's turned up, it stays that way.
peryp9 said:
How about very low volume on the BT ? I paired my phone with the BT in my 2012 Ford (with SYNC) and the music plays perfectly, but I can't hear S#!T during a phone conversation...
Click to expand...
Click to collapse
I'll try that but then I'll have to remember to turn it down when switching back to SiriusXM so that I dont blow my ears out.
I turned the media player volume down to 10 (as opposed to the normal 15) and it's still static on the high end.
Everything except cyanogen sucks as far as the bitpool goes and low bitpool makes bt sound like ****. I love android so much but I'm soooo disappointed in the amount of attention paid to Bluetooth sound. It's fine for audiobooks or podcasts but sucks for music.
Actually my son has a nexus s unrooted, maybe I should check that and see if music sounds OK. Maybe pure Android doesn't suck its just the touchwizs and senses of the world that make it terrible.
Sent from my SPH-D710 using xda premium
Wow... I was debating getting a Bluetooth speaker today. Didn't realize there was an issue like this with our phone.
Thanks for the insight. I wonder if any dev could do anything about this.
Sent from my SPH-D710 using Tapatalk
I have had a very different experience with in-car bluetooth audio. I just installed an iSimple expansion kit (uses the factory harness/plug and play) into my vehicle, and it sounds excellent! I have the phone volume turned all the way up, changing the level on the stereo instead. It seems to me that it isn't any quieter than XM, FM/AM, or CDs, and I like having all my music in Google Music and Pandora instead of the giant case of CDs I used to carry around. The call quality is average, better than OnStar if you've used it, worse than a call with good signal. The person on the other end sounds great, but I've heard that the driver always seems quieter than through the phone mic. My friends bluetooth audio in his Kia Soul does not sound as good as mine does, but the call quality is sometimes better.
Anyway, just my 2c. Cheers!
I have been using bluetooth audio and phone calls on stock rooted EL29 ROM with the Rogue Gunslinger kernel in both my car as well as a pair of headphones, and the audio comes through crystal clear. The car has a Kenwood KDC-BT945U head unit that supports A2DP and AVRCP, as well as hands-free calling, and I have no problems with either calls or music streaming. In the home, I have a Logitech bluetooth wireless speaker adapter plugged into my AVR, and it also sounds perfectly clear. There is never a hint of hissing, popping, dropouts, etc. I suggest that anyone who has bluetooth issues try my rom/kernel setup. If it does not work, you can blame the Ford or whatever bluetooth setup you have because the phone itself is perfectly good at bluetooth audio streaming. Maybe not out of the box, but with my setup I have no problems. For the record, I have high-end (near audiophile grade) audio equipment in both my car and home, so I know what good music sounds like. One caveat though, don't expect bluetooth streaming to sound as good as a wired connection. There is quite a bit of compression going on, but the difference is barely discernable in the car, probably due to the road noise. In the home though I have much higher quality speakers, and I can perceive a larger difference, but unless I'm listening to classical music in FLAC format, it's negligible.
Bluetooth audio on MyFord Touch is flawless..
Sent from my SPH-D710 using xda premium
I have noticed the crappy quality as well.... but here is some good news... they fixed it with ICS. I'm currently running the FB17 leaked build, and the quality is PERFECT. I'm an audiophile, so I pay close attention to the sound quality. and am very very happy the addressed this issue in ICS.
hijewpositive said:
I have noticed the crappy quality as well.... but here is some good news... they fixed it with ICS. I'm currently running the FB17 leaked build, and the quality is PERFECT. I'm an audiophile, so I pay close attention to the sound quality. and am very very happy the addressed this issue in ICS.
Click to expand...
Click to collapse
I have to agree, I have uConnect in my new Durango and was pissed when BT streaming did not work (it sounded like a constant pause/unpause and fastforward all at once). I just by happenstance tried it on FB17 and FB21 and it was perfect! Although the builds are not great yet so I went back to Calk 2.9 and itchin for a great ICS build to get that back!
dutchman71 said:
Bluetooth audio on MyFord Touch is flawless..
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
The BT sounds very well for music but during a phone conversation, the volume of the other party is way too low. If you were to increase the car's volume to hear the other person, it will decrease your microphone's sensitivity to a point where the other person cannot understand what you're saying (to prevent feedback)... It may be my FORD SYNC, but it worked beautifully on my old Blackberry. I will wait for ICS update and hope they addressed this problem.
Thanks!
hijewpositive said:
I have noticed the crappy quality as well.... but here is some good news... they fixed it with ICS. I'm currently running the FB17 leaked build, and the quality is PERFECT. I'm an audiophile, so I pay close attention to the sound quality. and am very very happy the addressed this issue in ICS.
Click to expand...
Click to collapse
I sure hope you're right! It's so much nicer to use my steering wheel controls then to reach over to my windshield-mounted phone and push the tiny on-screen buttons with Google Music. I'm also an audiophile and couldn't take the low quality sound of BT-Audio. Thanks for the hope!
I was on Paranoid Android 2.16, I used the Bluetooth music and calls in my 2012 Civic Si and sound quality was perfect. I switched to FI27 to give it a try and the Bluetooth sound quality went to crap. Has anyone looked further into the kernel theory? Anybody know a good kernel to use with latest update? That can be pushed with Odin? Thanks for any updates or suggestions.
i believe there is a bug in either the GNex's bluetooth hardware or Android ICS.
i have an A2DP adapter in my car to play music from my phone on my car stereo. my car also comes with the ability to connect to a phone for the purpose of taking and making calls thru its stereo and mics (using bluetooth HFP). when both are enabled simultaneously, i am able to listen to my music fine. if i get or make a call, the phone pauses the music, as you would expect, and goes into the call (although when i receive calls there seems to be a delay before the GNex switches over), but in the call the audio is garbled/robotic/scrambled...whatever you want to call it. this is the case both for what i hear and for what the person at the other end hears.
i wanted to start this thread to get more info about this problem from others that have experienced it, and maybe see if we can come up with a workaround.
there is an AC thread about this here:
http://androidforums.com/samsung-galaxy-nexus/524885-galaxy-nexus-bluetooth-bug.html
and i put in a bug at google here:
http://code.google.com/p/android/issues/detail?id=29564
any more info is appreciated!
According to other posts in the forums, the AOKP ROM does not have these issues.
I really did not want to root this device. I know, that's just not cool. But everything else was just working.
My Sensation did not have these problems, but alas I dropped it and it died and I was still on contract. The Nexus was more cost effective than bending over for the off-contract price from TMO.
Anyway, chalk me up as a "me too" on this issue. I'm going to root tonight and try AOKP.
I would be kind of surprised if it didn't exist in AOKP, because the problem definitely exists in CyanogenMod 9 (and AOKP is essentially a kang of that). In fact, I uninstalled CM9 and reverted to stock expressedly because I initially thought that this bug was a CM9 issue and it was annoying enough that I figured I'd revert to stock until CM9 reaches stable, only to discover that the problem is in the official Google builds as well.
ianken said:
Anyway, chalk me up as a "me too" on this issue. I'm going to root tonight and try AOKP.
Click to expand...
Click to collapse
Please let us know how it goes! I've been using Bugless Beast, but would switch to AOKP if it fixes this bug.
I've yet to find a build without BT issues of some sort.
The garbled call audio is new to me. I've not see that on other devices but have yet to find a GN ROM that mitigates it. This is in addition to issues that go back to the Nexus 1. There was an audio.conf fix for that, I'll see if I can wrangle it up and see if it helps here.
My setup: Factory BT hands free (crap Audi OEM goo) + FIPO A2DP device for music. So, two completely discrete BT devices.
Edit:
try this: edit etc/bluetooth/audio.conf and set master=true (backup the file first)
I also set HFP=true (it's commented out in the file)
What I found:
1- Calling: audio quality was still pretty poor with a lot of pops. It sounds a bit "hot." Quite inferior to other devices I've used with this setup.
2- However: A2DP playback no longer glitches. In my case audio played fine after the first connect after BT was turned on. But subsequent connects, say after leaving and the returning to the car would result in glitchy audio.
So far this tweak seems to have improved things. I'm really bummed by the audio all quality.
ianken said:
I've yet to find a build without BT issues of some sort.
The garbled call audio is new to me. I've not see that on other devices but have yet to find a GN ROM that mitigates it. This is in addition to issues that go back to the Nexus 1. There was an audio.conf fix for that, I'll see if I can wrangle it up and see if it helps here.
My setup: Factory BT hands free (crap Audi OEM goo) + FIPO A2DP device for music. So, two completely discrete BT devices.
Edit:
try this: edit etc/bluetooth/audio.conf and set master=true (backup the file first)
I also set HFP=true (it's commented out in the file)
What I found:
1- Calling: audio quality was still pretty poor with a lot of pops. It sounds a bit "hot." Quite inferior to other devices I've used with this setup.
2- However: A2DP playback no longer glitches. In my case audio played fine after the first connect after BT was turned on. But subsequent connects, say after leaving and the returning to the car would result in glitchy audio.
So far this tweak seems to have improved things. I'm really bummed by the audio all quality.
Click to expand...
Click to collapse
audio.conf does not seem to exists in 4.2.2. Has anyone found audio.conf in 4.2.2?
If someone can present a resolution I'd be very grateful.
I'm having trouble listening to music on my E4GT when it comes to listening to music. Whenever I connect earphones the sound is automatically distorted and robotic sounding. But oddly, whenever I connect to my car audio auxiliary it plays fine. I try different options to pinpoint the problem, its not the headphones because they work with any other device (also tried multiple headphones) and its not a hardware issue because it works with my car stereo hookup. I havent tried portable speakers because I dont possess any. Its very frustrating.
Thing is this started recently, I havent changed roms or installed any apps.
Im on Jellybean 4.1.2, rooted running the latest MIUI from the Android Development thread..
Ive seen a thread before the issue started on a different forum site, but it has no search feature so I cant relocate it.
Can anyone help me out??
I have done extensive testing with both my HTC One and Samsung Galaxy Nexus regarding the phantom ringing noise that exists on bluetooth audio. This issue is not only present on streaming bluetooth audio but also present when the sound file is kept on the actual phone (using Google Play Music). So far I have tried the following:
1) Tried multiple roms both sense and aosp - the ringing/buzzing noise still exists on both (DEFINITION - PHANTOM RINGING/BUZZING NOISE - a buzzing series of overtones that exists particularly when listening to jazz music that has a lot of ride and crash cymbals being played) As a professional musician, this can be quite annoying.
2) Tried going back and forth between bluetooth and auxiliary cable on both phones (HTC One and Galaxy Nexus), trying AOSP vs. SENSE roms, streaming vs. non streaming. Both phones and all roms have the same issue present, the bluetooth audio has a fuzzy clarity to the cymbals. It is worth mentioning that the AOSP roms are slightly better in terms of less Phantom ringing/buzzing but far from perfect.
My question is, does anyone have a fix for this? I paid big bucks to have Bluetooth installed in my car and really want to use it.
The auxiliary cable sounds good until you plug your phone charger in.....that presents an even larger noise issue. Please help.
Thanks,
MightyChigger said:
I have done extensive testing with both my HTC One and Samsung Galaxy Nexus regarding the phantom ringing noise that exists on bluetooth audio. This issue is not only present on streaming bluetooth audio but also present when the sound file is kept on the actual phone (using Google Play Music). So far I have tried the following:
1) Tried multiple roms both sense and aosp - the ringing/buzzing noise still exists on both (DEFINITION - PHANTOM RINGING/BUZZING NOISE - a buzzing series of overtones that exists particularly when listening to jazz music that has a lot of ride and crash cymbals being played) As a professional musician, this can be quite annoying.
2) Tried going back and forth between bluetooth and auxiliary cable on both phones (HTC One and Galaxy Nexus), trying AOSP vs. SENSE roms, streaming vs. non streaming. Both phones and all roms have the same issue present, the bluetooth audio has a fuzzy clarity to the cymbals. It is worth mentioning that the AOSP roms are slightly better in terms of less Phantom ringing/buzzing but far from perfect.
My question is, does anyone have a fix for this? I paid big bucks to have Bluetooth installed in my car and really want to use it.
The auxiliary cable sounds good until you plug your phone charger in.....that presents an even larger noise issue. Please help.
Thanks,
Click to expand...
Click to collapse
if 2 phones and different roms still cause the problem then it might be your BT system.
what music player are you using / do any of them have an EQ system you can adjust.
what BT system do you have?
synisterwolf said:
if 2 phones and different roms still cause the problem then it might be your BT system.
what music player are you using / do any of them have an EQ system you can adjust.
what BT system do you have?
Click to expand...
Click to collapse
I am using an Audiovox Media bridge, however, I do not think that is the issue due to the fact that the issue improves slightly on the Aosp ROM. Additionally, when I run the aux through the media bridge I have no issues.
I am using Google play music. I have tried adjusting the EQ using Viper ROM 5.0 and have had no success. Any other ideas?
Hello. I change phones alot and have noticed that some phones(all android) have better bluetooth playback than others.
I had a oneplus 7 pro before this phone and the bluetooth quality to my truck was great and had no issues but with this phone the highs sounds scratchy or like if the speaker is bad. But if i connect it with a wire connection it sounds great. Everything with the 2 phones is the same. On both i was using the galaxy watch and pretty much the same apps. On a previous phone the note 8 i had the same issue but it was a different car. Seems like its the way samsung handles bluetooth.
Has anyone had this issue? If so was there a fix?
Thanks
make sure not on mic
Sent from my SM-N975F using Tapatalk
jemfalor said:
make sure not on mic
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
What do you mean?
The only two things I think about is the codec used that may be different across devices, and the Bluetooth settings that sync the phones volume with the headset (the differences are noticeable).
Since no DAC is used in Bluetooth, I don't think it can comes from them, for a same headset.
On Samsung phones you should run the adapt sound process. Try this.
I tried with the sync volume off too and no improvement.
I looked for the adapt sound and my phone doesn't have that setting. Or is it something different?
It's in Sounds and Vibration 》 Advanced Sound settings 》Sound Quality and effects 》 Adapt sound
You have to do this in a quiet place and ensure to answer honestly. If you can't hear the beeping press no.
After doing this the sound quality is night and day difference.
Ok found it. Ill play with it a bit. Thanks
I've had issues sometimes with audio being piped through the "Calls" Bluetooth channel versus the "Audio" channel so worth checking as the quality is obviously night and day.
I also like enabling Dolby Atmos on my Note 10+ for music so worth playing with too. Additionally, I recently found Samsung's Sound Assistant app which let's you customize a bunch of sound settings so worth checking out as well:
https://play.google.com/store/apps/details?id=com.samsung.android.soundassistant
sansnil said:
I've had issues sometimes with audio being piped through the "Calls" Bluetooth channel versus the "Audio" channel so worth checking as the quality is obviously night and day.
I also like enabling Dolby Atmos on my Note 10+ for music so worth playing with too. Additionally, I recently found Samsung's Sound Assistant app which let's you customize a bunch of sound settings so worth checking out as well:
https://play.google.com/store/apps/details?id=com.samsung.android.soundassistant
Click to expand...
Click to collapse
Is there an easy way to tell if the audio is going through the call channel?
ErickF said:
Is there an easy way to tell if the audio is going through the call channel?
Click to expand...
Click to collapse
Easiest is probably just uncheck calls in your phones BT settings for your truck (and make sure audio is enabled). If the sound is still not great then this isn't the issue.
Sorry to respond to an old thread, but I was wondering if any of this fixed the OP's problem. I followed all the recommendations here and on other threads but have not been able to solve my recent Bluetooth audio problem. The sound has been terrible lately.
Same issue here on my s10+. When playing any audio in my car via BT i hear the distortion/hissing noise especially when the song has a higher treble frequency.
I have just about tried all fixes i could find on Google, and no luck.
When connecting to my ear buds (Jabra Elite 65t) it disappears and checked in developer mode that it supports to AAC for BT Codecs.
But when connecting to the car it reverts to SBC.
The issue clearly lies on Samsungs side, as my brother has a Huawei p30 Pro, also has bluetooth 5 and plays amazingly well in all aspects (Bass-Mids-Treble).
I know I'm posting this almost a year later, but i am desperately looking for a fix.
SN. I have recently updated my phone to Android 10, despite all the complaints to Samsung from many users... Sadly this issue has not being fixed on my side.
From what i see online, people have given up on Samsung and opted for Rooting their Samsungs and installing Viper4Andriod.
Has any one done this and can confirm that it fixed the issue?