after root & unlock i have Bluetooth sound quality issues ....any suggestions ? thx
Did you flash a ROM? Simply rooting and unlocking should have no impact on that.
Sent from my HTC One X using xda app-developers app
tried couple different rom's right now i'm on clean rom
What do you mean by sound quality issues? Like is there a lot of noise, sound distorted, low volume, etc?
I'm on CleanROM Developer Edition 3.1.1 and I'm having no BT sound issues and I use it in my car with a Samsung BT adapter (with Apt-X)
obvious troll is obvious
thanks , i switch to clean rom 4.0 an everythings run nice now , before everybody on the other end was complaining about sound quality ...
I know it is a known issue that headphone controls on android are a pain. I was wondering if anyone has had luck finding an app that allows the controls on the headphones that came with the S3 work on an AOSP ROM? I have tried multiple apps with no luck and use Power Amp as the player. Any suggestions and advice would be greatly appreciated.
I had the same problem in liquid smooth illusion rc1 I tried remotecontrol for earphones and poweramp app and still nothing. Im going to try installing beats and see if that'll work.
Sent from my SCH-I535 using xda premium
Same problem
I"m also looking for a solution to this. I don't think an app is going to cut it since the buttons aren't getting recognized on a driver level. If anyone knows an easy hack (likely copying a specific library file) I'd really like to know about it.
To make things more simple and an actual fix, look in gerrits and githubs for headset controls. I've been on the hunt for about an hour or two haha.
I've ran a variety of TW ROMs including CleanROM, Hyperdrive and am currently running BoneStock - all are based on 4.1.2.
However, Bluetooth Calling/Voice quality sucks when I am paired with my car (2010 Nissan Maxima). I can hear callers fine, but they say I sound garbled and robotic. At first, I thought the problem was my car until I paired an iPhone and call quality was fine.
FYI, streaming music via Bluetooth works perfectly.
I've done research on XDA and other forums, and the problem seems to be with 4.1.2. Does anyone know if switching over to an AOSP 4.3 ROM will alleviate Bluetooth issues?
I like everything else about Touchwiz (e.g. the stability, battery life, etc.) and I know Google was messing around with the Bluetooth stack. However, I work in Sales and need Bluetooth in the car. Thoughts?
Sent from my Samsung Galaxy s3 via Tapatalk Pro
Any solution?
Comp625 said:
I've ran a variety of TW ROMs including CleanROM, Hyperdrive and am currently running BoneStock - all are based on 4.1.2.
However, Bluetooth Calling/Voice quality sucks when I am paired with my car (2010 Nissan Maxima). I can hear callers fine, but they say I sound garbled and robotic. At first, I thought the problem was my car until I paired an iPhone and call quality was fine.
FYI, streaming music via Bluetooth works perfectly.
I've done research on XDA and other forums, and the problem seems to be with 4.1.2. Does anyone know if switching over to an AOSP 4.3 ROM will alleviate Bluetooth issues?
I like everything else about Touchwiz (e.g. the stability, battery life, etc.) and I know Google was messing around with the Bluetooth stack. However, I work in Sales and need Bluetooth in the car. Thoughts?
Sent from my Samsung Galaxy s3 via Tapatalk Pro
Click to expand...
Click to collapse
Hi,
Did you find a solution to your problem? I have the exact same issue and I need bluetooth in my car .
Thanks,
John.
starcraft04 said:
Hi,
Did you find a solution to your problem? I have the exact same issue and I need bluetooth in my car .
Thanks,
John.
Click to expand...
Click to collapse
Sorry for not seeing your post sooner. If I get a chance, I am going to flash 4.3 ROM's myself (4.4 is still a bit unstable for my tastes) this weekend and see if the BT stack is improved.
Otherwise, I think I might jump on the Moto X deal happening on Monday (if the MotoMaker site decides to work. :silly
Hi, bought a Nexus 5 a few days ago, which is now running AOKP on stock kernel . Coming from a One M7 that was running Cyanogenmod 10.2.
I've noticed over the past couple days that the quality of the audio streaming via bluetooth to my car's stereo is comparatively much worse than my old One. In particular, I often get these very stringent, distorted high frequencies, especially when the music grows more complex. I don't recall any of this strange artifacting with my One. Could it have something to do with the better audio hardware of the One (superior DAC, amping, etc)? I don't know how much of an effect those would have on bluetooth streaming, though. Could it be the ROM I'm using has unoptimized bluetooth? Has anyone else noticed this?
I'm using the Google Music app if that helps anyone. Thanks in advance for the help.
The DAC and amplifier in the phone are not involved in the Bluetooth streaming process. Bluetooth is a digital signal so the digital-to-analog conversion is handled at the receiver end. The M7 does support Apt-X, which could have explained the quality difference assuming your car stereo also supports it (unlikely). You did say you were running Cyanogenmod though, and Apt-X is proprietary and thus I do not think it is supported in CM.
There could be an issue with the ROM. I know that CM11 is having some bluetooth audio issues, so AOKP may be as well. I would say a good first step would be to try stock and see if that resolves the problem.
Lastly, are you using the streaming functionality of Play Music? They did at one point change the streaming options so that it defaults to "Normal" quality instead of high. If you go to Play Music -> Settings -> Mobile Network Stream Quality, make sure High is selected.
Thanks for the tips. I tried adjusting the quality like you suggested, but I actually didn't notice any difference. I'm going to assume for now that this is a ROM issue and try stock when I get home.
I went through the arduous process of flashing a stock rom back onto the phone and tested the audio; there was no difference. I paired my old M7 to the car and played the same songs in comparison, and there was no question that it sounded much better. I think it bears repeating that the M7 is running 4.3.x, would that make a difference?
The issue comes up with upper treble frequencies, where it begins to sound very compressed and distorted, much like white noise. To eliminate all doubt, I played some CD's with the same songs, and they sounded crisp and fine.
Any additional help with this would be greatly appreciated. Streaming bluetooth audio in the car is very important to me and the inability to do so at a level of quality I would consider acceptable makes me rather inclined to return the phone. Is this a potential fix upcoming in 4.4.3? Thanks in advance.
I can confirm similar issues. My setup isn't going to win an high-fidelity awards, but I'm using a BT to FM converter. I do notice some clipping at high frequencies. For comparison, my N4 didn't have the clipping issue my N5 has, but the N5 sounds significantly brighter than the N4. The N4 was always a bit muddy on BT.
It could be an issue where the gain is too high by default. I'm not sure about AOKP but CM has the DSP manager built in, and you can adjust output for BT. Maybe play around with those settings?
I'll flash CM11 and see what results I get, thanks for the heads up.
I have the exact same issue. Will be following. I've found that the issue doesn't occur on anything CM based, probably because they use CAF drivers not AOSP. I'm currently running PA with Franco.
I have found a fix for 4.3 but I don't think it applies to kitkat.
http://forum.xda-developers.com/nexus-4/general/android-4-3-bluetooth-audio-quality-fix-t2386032
Sent from my Paranoid, ARTified and Francoed Nexus 5 via XDA Premium
hi everyone. i have a fiat bravo,and it only supports incoming and outgoing calls,what i ld like to do is , listen to pandora or youtube thru that connection. Because some of applications such as sygic etc transfers the sound to the car stereo,but youtube and etc doesnt. is there any solutions for that?
burakthepascal said:
hi everyone. i have a fiat bravo,and it only supports incoming and outgoing calls,what i ld like to do is , listen to pandora or youtube thru that connection. Because some of applications such as sygic etc transfers the sound to the car stereo,but youtube and etc doesnt. is there any solutions for that?
Click to expand...
Click to collapse
That's a bit OT for this topic, but in short, unless your car supports A2DP you can't listen to music over that connection.
Sent from my Paranoid, ARTified and Francoed Nexus 5 via XDA Premium
abra5umente said:
I have the exact same issue. Will be following. I've found that the issue doesn't occur on anything CM based, probably because they use CAF drivers not AOSP. I'm currently running PA with Franco.
I have found a fix for 4.3 but I don't think it applies to kitkat.
http://forum.xda-developers.com/nexus-4/general/android-4-3-bluetooth-audio-quality-fix-t2386032
Sent from my Paranoid, ARTified and Francoed Nexus 5 via XDA Premium
Click to expand...
Click to collapse
Interesting how you state that you don't perceive any issues with CM-based roms. I flashed 4.4.2 AOKP onto my M7 (which is coming from CM10.2) to test what the audio sounds like on it with KK, and I can confirm that the audio has the same issues the Nexus 5 has. With all the variables removed and with two different devices running the same ROM, I come to the conclusion that this is a software issue. I'm going to flash the latest CM onto the M7 later today to see if that resolves anything.
To say the least, this is frustrating, but good to see that there was a fix identified for 4.3. Hopefully that will trickle over to 4.4 soon enough.
Aftershok said:
Interesting how you state that you don't perceive any issues with CM-based roms. I flashed 4.4.2 AOKP onto my M7 (which is coming from CM10.2) to test what the audio sounds like on it with KK, and I can confirm that the audio has the same issues the Nexus 5 has. With all the variables removed and with two different devices running the same ROM, I come to the conclusion that this is a software issue. I'm going to flash the latest CM onto the M7 later today to see if that resolves anything.
To say the least, this is frustrating, but good to see that there was a fix identified for 4.3. Hopefully that will trickle over to 4.4 soon enough.
Click to expand...
Click to collapse
I had a look in that folder and it has stuff to do with A2DP in there, so that's helpful. Might have a look now. I'll report back here with my findings.
Sent from my Paranoid, ARTified and Francoed Nexus 5 via XDA Premium
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
In fact, if you're flashing CM, can you have a look at that folder and screen shot it for me so I can see if the files are the same?
Sent from my Paranoid, ARTified and Francoed Nexus 5 via XDA Premium
abra5umente said:
I had a look in that folder and it has stuff to do with A2DP in there, so that's helpful. Might have a look now. I'll report back here with my findings.
Sent from my Paranoid, ARTified and Francoed Nexus 5 via XDA Premium
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
In fact, if you're flashing CM, can you have a look at that folder and screen shot it for me so I can see if the files are the same?
Sent from my Paranoid, ARTified and Francoed Nexus 5 via XDA Premium
Click to expand...
Click to collapse
Thanks for your help. Can you be more specific as to which folder you're referring to? I'm fairly green when it comes to the nuts and bolts of this stuff, but I think I can handle a screenshot.
Aftershok said:
Thanks for your help. Can you be more specific as to which folder you're referring to? I'm fairly green when it comes to the nuts and bolts of this stuff, but I think I can handle a screenshot.
Click to expand...
Click to collapse
If you go to system/lib/hw there should be a lot of files in there which tell the hardware how to work with the software. There should be one in there which is called audio.a2dp.default.so
To do this, you'll need a root browser or something which allows you to view root files.
abra5umente said:
If you go to system/lib/hw there should be a lot of files in there which tell the hardware how to work with the software. There should be one in there which is called audio.a2dp.default.so
To do this, you'll need a root browser or something which allows you to view root files.
Click to expand...
Click to collapse
Does this help? I've attached two screenshots. I can't open the file itself.
Aftershok said:
Does this help? I've attached two screenshots. I can't open the file itself.
Click to expand...
Click to collapse
Yeah, you can't open them in Android.
I wonder if they're the same files, seeing as CM uses CAF not AOSP drivers...
abra5umente said:
Yeah, you can't open them in Android.
I wonder if they're the same files, seeing as CM uses CAF not AOSP drivers...
Click to expand...
Click to collapse
I wanted to confirm that I don't perceive a huge difference with the CM rom, if at all. The signal has a hard time keeping the highs clean and sounds very strident at times.
Did you have the DSP Manager (in CM) set up on the One?
I have both the One and N5... I immediately noticed a difference in A2DP quality with DSP Manager on/off.
Wanted to come in here and also state that the bluetooth audio for the Nexus 5 can be improved quite a bit. I actually miss the audio quality of my iphone 4 with both the audio out via headphone jack as well as the bluetooth audio out.
Running purity rom + elemental x kernel
Is bluetooth the only way to play music in the car through your phone.
USB won't work? I tried it in my car and it didn't work but when I googled it some people say different radios might work.
I am currently having outgoing voice quality issues while using a bluetooth headset (or in car/truck bluetooth) that I am trying to nail down with both HTC and Jawbone. I'm 90% sure at this point it's an HTC issue. I purchased an HTC One M8 on Verizon a week or so ago and immediately had issues with my Jawbone ERA. Voices sounded fine on my end but my voice on the other end sounded static-ey and overly loud - almost like the mic was too hot. I tried a ton of troubleshooting steps with both Jawbone and HTC and so far the issue remains. I also took the phone back and exchanged it for a new one and the new phone has the same issue. I've now tried 5 different bluetooth devices all with the same/similar result.
I found an old HTC One (M7 I think?) thread over on Android Central that seemed to be discussing the same issue:
http://forums.androidcentral.com/htc-one/309574-anyone-else-having-bluetooth-headset-sound-quality-issues-one.html
but no solution was found and it sounds like most people there just sort of gave up.
Sorry for the long explanation but one thing I wanted to try was using a ROM with a different bluetooth stack or system to see if that might point me to an HTC software issue vs a strict hardware issue. Does anyone have any recommendations? I'm fairly comfortable with installing ROMs though on my old Droid, Safestrap certainly made it easier for me.
Thanks!
I had a ridiculous static with my jaybirds so I just ended up returning the headphones and ditching Bluetooth sadly. I don't think a ROM will change it
Sent from my HTC6525LVW using Tapatalk
So there's no difference in bluetooth implementations between a Sense based ROM and say an AOSP or CM based ROM?
AustinML71 said:
So there's no difference in bluetooth implementations between a Sense based ROM and say an AOSP or CM based ROM?
Click to expand...
Click to collapse
Well, out of curiosity I s-off'd the phone, perma-rooted, and flashed TWRP. I installed the GPE ROM, the Viper ROM, and the latest nightly of Cyanogenmod. Interestingly, the CM rom seemed to have MUCH improved outgoing bluetooth voice quality. The other ROMs all had the same issue.
Does CM somehow use a different bluetooth stack or something that would cause this? Honestly, I'd stay on the CM but I actually like some of the HTC features (like the duo-camera) and not sure I'd want to give those things up. Would it somehow be possible to use CM's bluetooth solution in something like the GPE ROM or even stock?
AustinML71 said:
I am currently having outgoing voice quality issues while using a bluetooth headset (or in car/truck bluetooth) that I am trying to nail down with both HTC and Jawbone. I'm 90% sure at this point it's an HTC issue. I purchased an HTC One M8 on Verizon a week or so ago and immediately had issues with my Jawbone ERA. Voices sounded fine on my end but my voice on the other end sounded static-ey and overly loud - almost like the mic was too hot. I tried a ton of troubleshooting steps with both Jawbone and HTC and so far the issue remains. I also took the phone back and exchanged it for a new one and the new phone has the same issue. I've now tried 5 different bluetooth devices all with the same/similar result.
I found an old HTC One (M7 I think?) thread over on Android Central that seemed to be discussing the same issue:
http://forums.androidcentral.com/htc-one/309574-anyone-else-having-bluetooth-headset-sound-quality-issues-one.html
but no solution was found and it sounds like most people there just sort of gave up.
Sorry for the long explanation but one thing I wanted to try was using a ROM with a different bluetooth stack or system to see if that might point me to an HTC software issue vs a strict hardware issue. Does anyone have any recommendations? I'm fairly comfortable with installing ROMs though on my old Droid, Safestrap certainly made it easier for me.
Thanks!
Click to expand...
Click to collapse
I'm on CleanRom and I'm also extremely sensitive to Bluetooth quality issues. I'm using both a Plantronics Legend and the Bose ear pieces and I hook the device up to a Pioneer DEH-80PRS in my car. I have to say I've never had a better Bluetooth experience. No complaints - superb quality - both ends
MARKREIF said:
I'm on CleanRom and I'm also extremely sensitive to Bluetooth quality issues. I'm using both a Plantronics Legend and the Bose ear pieces and I hook the device up to a Pioneer DEH-80PRS in my car. I have to say I've never had a better Bluetooth experience. No complaints - superb quality - both ends
Click to expand...
Click to collapse
I'm now also on CleanRom and it is definitely better. My few tests so far weren't quite as clear as my CM tests but MUCH better than stock. This seems so strange to me. This is just a stripped down Sense ROM, like others yet a significant difference in quality. Both Viper and GPE had the same bad quality as stock. I wish I had the understanding/capability to truly root cause the issue as I'd love to have the freedom to use whichever ROM I choose. However, I do very much like CleanRom for now - the Verizon bloat on this phone was the worst I've ever had yet I do like a few of the Sense 6 features.