Related
My opinion is that the bluetooth audio quality on the HTC Desire is terrible!
When playing music, in most of the tracks I hear clicking/crackling noise when some frequency/dB/something else is reached.
To illustrate what I mean, I have uploaded an audio fragment in which you can hear a similar noise.
Download fragment (MP3) Warning! it's drum n bass
You can hear the sound at the very beginning and at around 6 seconds (and at the end). As if a tweeter (speaker for higher frequencies) get overloaded.
I don't know if it is related to the phone's hardware, (radio) firmware or the Android OS. I've tried different music players, radio firmwares and custom roms. I also enabled an equalizer for bt audio using DSPManager. Unfortunately, nothing helped
edit: Using current versions of DeFoST or OpenDesire (and maybe others), the bt sound quality is how it should be! Fixed for me, but I hope an update from HTC will do the same.
Btw, this crackling/clicking is not only related to the HTC Desire, I have heard it on more (non-android) phones that were connected to my bt audio setup (in car). Unfortunately I haven't been able to test other Android phones, but my old Nokia N82 and SE K800i always sounded clear.
My guess is that it's just a non-controllable system setting of Android to solve the problem, but I don't know where (config/settings files?) to search for BT audio settings.
Any ideas?
That's the typical audio quality of a mediocre A2DP device: give a try at a Sony Ericsson MW-600 headset, you'll see what an Hi-Fi Bluetooth device is.
@ngel said:
That's the typical audio quality of a mediocre A2DP device: give a try at a Sony Ericsson MW-600 headset, you'll see what an Hi-Fi Bluetooth device is.
Click to expand...
Click to collapse
I'm running Defrost rom now and the sound quality is perfect, how it should be! So, it's not related to the audio device, or the default settings/drivers of the Desire are "too good" for my audio device (Pioneer BT unit @ car audio), which I think is not the case, since I also had this noise on my Logitech Pure-Fi.
@ngel said:
That's the typical audio quality of a mediocre A2DP device: give a try at a Sony Ericsson MW-600 headset, you'll see what an Hi-Fi Bluetooth device is.
Click to expand...
Click to collapse
Actually I recently owned this headsert but the quality of the sound was still terrible. I thought it was a problem with the headset at first, but that is not the case. I returned it and bought a Jabra BT3030 and the problem still persists. Anyone know if this is actually a problem with the phone or is it software related? I can add that I don't hear these noises when streaming audio through e.g. the youtube app, only mp3 and it doesn't matter which player I use (I've tried loads).
I have the jabra dogtags, audio playback sounds exactly the same as when my headphones are plugged in direct (tested it several times, culd not tell the difference), except that I have a louder volume via the jabra, which is all good as I listen to drum and bass also. Mabey device fault?
It is software related. Using current DeFroST or OpenDesire roms (and maybe others), bluetooth audio is great
CONTACTMC said:
I have the jabra dogtags, audio playback sounds exactly the same as when my headphones are plugged in direct (tested it several times, culd not tell the difference), except that I have a louder volume via the jabra, which is all good as I listen to drum and bass also. Mabey device fault?
Click to expand...
Click to collapse
well if it would've been device fault you'd think that I'd hear that noise through youtube streams as well.
But yeah as tutti-frutti stated it might be a software issue, which points me towards a root. But since I'd rather not root atm, anyone knows any other solution?
Might try a hard reset first and hope for the best. I will get back to you on that .
Thank you so much for describing my problem!!
I am currently downloading OpenDesire. Just in case that it does not work, where do i find DeFost??? I can't find it on the Market.
Thanks again!
I have Samsung Epic 4g.
nope Desire's Bluetooth audio quality is good in fact Awesome..!!
-May be the problem is not with the phone, its with Bluetooth head set you are using.
-My suggestion is to use Nokia or Motorola A2DP Stereo head phones
-I'm using Motorola motorkr S9 hd ,,,its awesome..!!
-Try this ,,it might work
harish.awe said:
nope Desire's Bluetooth audio quality is good in fact Awesome..!!
-May be the problem is not with the phone, its with Bluetooth head set you are using.
-My suggestion is to use Nokia or Motorola A2DP Stereo head phones
-I'm using Motorola motorkr S9 hd ,,,its awesome..!!
-Try this ,,it might work
Click to expand...
Click to collapse
For me, it is an issue with my car, not headphones.
A little UP!
Having the same issues with a Nokia BH-504 headset. Music quality is poor with every Sense ROM (original, rooted, Sense HD, whatever), sound like the tweeters are overloaded.
Definetly not a problem with the headset, it sound perfect with HTC Legend.
Tried to switch to non-Sense ROM (DeFrost, OpenDesire, etc.). The quality is perfect, but music play stops every 1-2 minutes for a second. Very irritating. Anyone experienced this? Is this a problem with my Desire, should I send it for warranty? (Don't want to send without enough evidence, don't wanna be without a phone for weeks...)
Okay, update: Tested the new Gingerbread AOSP and still having these stops at 2-3 minutes. Very strange...
Anyone any idea? Can I debug the bluetooth transfer somehow? Logcat didn't really show anything... Can it be a fault of the phone?
Chapell said:
Anyone any idea? Can I debug the bluetooth transfer somehow? Logcat didn't really show anything... Can it be a fault of the phone?
Click to expand...
Click to collapse
You need an sd r/w-buffer fix in kernel to stop that. I don't know if it comes with any senseless rom though. Maybe you could try the lite version of baadnewz hd rom.
Sent from my HTC Desire using XDA App
Ik Desire said:
You need an sd r/w-buffer fix in kernel to stop that. I don't know if it comes with any senseless rom though. Maybe you could try the lite version of baadnewz hd rom.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Thanks, I'll look into it. But if that's the problem, it would affect music playback with wired headphones too, isn't it?
And with Sense ROMs I have the overloaded tweeter-like problem, but no stutters. With non-Sense ROMs I have beautiful audio quality but music stops for a second randomly.
Update: Checked Aura ROM with sdfix, no problem with stuttering, but still the overloaded high-frequency problem. Meanwhile I checked that this SD fix is available only for Sense ROMs because it's HTC's hacking, the AOSP versions have no SD problems.
Oh, good lord! I was nearly to believe that I'm some sort of audiophile!
I'm using Plantronics 903 with my Desire and sound quality is just OK (I'm using SENSE ROM, will try OpenDesire in a bit). However, I cannot say I was expecting more.
What funny is happened today: I paired my 903 with PC today - sound quality was nearly same like my Desire, then I noticed someting in Bluetooth Setting Panel of PC. There was a combo box which labeled as "Audio Quality" and it was at the "Low" setting. I switched it "High Quality" and reconnected the device and voila! The sound has been thousands of times better!
Now I'm wondering if such a switch is also available in Desire? Maybe not obvious, but a Kernel variable perhaps? Damn that I don't know a sh** about programming these devices :'(
EDIT : Funny - I think that setting was not of PC's, but Headset's! It's quite well right now! And I didn't even try OpenDesire yet!
Chapell said:
A little UP!
Having the same issues with a Nokia BH-504 headset. Music quality is poor with every Sense ROM (original, rooted, Sense HD, whatever), sound like the tweeters are overloaded.
Definetly not a problem with the headset, it sound perfect with HTC Legend.
Tried to switch to non-Sense ROM (DeFrost, OpenDesire, etc.). The quality is perfect, but music play stops every 1-2 minutes for a second. Very irritating. Anyone experienced this? Is this a problem with my Desire, should I send it for warranty? (Don't want to send without enough evidence, don't wanna be without a phone for weeks...)
Click to expand...
Click to collapse
I have similar sound issues on non-sense roms. I believe it's mostly to do with range is just not quite as good as with sense based roms. I haven't had time to really figure out why yet.
Okay, so they replaced my Nokia BH-504 headset with a new one, still the same issue with Desire Sense ROMs but Legend Sense is still good. So it's not an issue with the headset (well, could be a general incompatibility problem, but I don't think so) Will check my laptop and a Gingerbread ROM on the Desire. Okay, conclusion after further tests with the replaced headset:
with Desire Sense ROMs: horrible quality in the high frequencies with every MP3.
with Desire non-Sense ROMs (OpenDesire, Gingerbred, etc): Good quality, but music play stops for a secons every 1-2 minutes.
with HP TouchSmart TM2 notebook: Quality problem AND music sutter BOTH
with HTC Legend original Froyo ROM: No problem
with Sony Ericsson X8: No problem
with HTC Touch HD: Quality problem
The headset has been replaced with a new one, same errors occur.
I have no idea what's wrong. I can't believe 2 phone's and a notebook's Bluetooth chip is faulty. So this could be an incompatiblity, hooray for great Bluetooth standard specification I should try a Nokia BH-905 and a Sennheiser MM400, will try them after buy (in the store!) and hand them immediately back if there will be a problem with them
Chapell, I have the same problem as you, with the Nokia BH-504 headset. So far the headset works great with the stock ROM, LeeDroid ROMs or just about any Froyo ROM. Gingerbread-based ROMs or Cyanogen nightlies, or any of the AdamG's Oxygen ROMS, on the other hand, they all have the same issue - every 90 seconds or so there is a glitch, the audio stream skips for half a second or so - very, very annoying keeps you from getting in the mood.
My observations: it is not SD card related, youtube video with the audio part streamd through the bluetooth headset also skips (also tried an SD read-ahead zip patch - no change); also, the glitch doesn't manifest using wired headphones; it has nothing to do with CPU spikes (the music player and the BT connection were the only open applications after a fresh ROM install); it has nothing to do with WiFi being on or off; it has nothing to do with 3G/2G network being active or not, or the GPS; using a different radio also doesn't help (scenario - radio X used with N.S.A. ROM -> no glitch; the same radio used with Oxygen 2.0 RC7 -> glitch)...
My guess - as noobish as it may be - is that this issue is related to some kind of buffering in the streaming process - I compared a few bluetooth configuration files in various ROMs, but couldn't figure any setting related to buffering or such.
If anyone could help, I would be very grateful!
Thanks for the info. If I understand correctly, you had no problems with BH-504 using Sense ROMs. So no high frequency distortion, nothing. This means that my phone is definetly faulty
However it seems the non-Sense skips are not unique for me. Strange, no one uses a BT headset with non-Sense ROMs or it could be a problem only with the BH-504?
I've used many ROMs (Viper, Bonsai, Nebula, currently ACS Syndicate) and I've had this problem on all of them. I've even ODIN'd back to stock before and it still didn't fix my problem.
After disconnecting my Epic from my Jawbone Icon headset, the sound often gets stuck inside the earpiece. Music, movies, games, ringtones will all play from the earpiece instead of the speaker behind the phone.
Is there some software fix to correct this? Can any of the devs point me in the right direction as to how I might troubleshoot this (maybe at the kernel level)?
Thanks in advance!
This doesn't really go in Development, and I suspect it will be moved soon.
I can tell you, though, that I've experienced similar problems, intermittantly, and here's what I've observed.
If I'm listening to music through bluetooth, before I disconnect, I'll stop the music. Then I'll turn the bluetooth device off. Then I'll turn bluetooth off on the phone. If I do it in that order, I don't seem to get the bug.
If you do still get the bug, rebooting fixes it.
Hope that helps!
This is a known issue. It's a bug that has to do with being connected to a device for both media and phone calls. If you use only one or the other it doesn't happen.
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
This is a known issue. It's a bug that has to do with being connected to a device for both media and phone calls. If you use only one or the other it doesn't happen.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
It's very annoying for me as well.
The other bug that I noticed is after taking a call over BT, when I end the call, the earpiece on the phone starts randomly popping. rebooting fixes it but it still really irks me.
I think the OP is wondering if there's a way to dig around in the BT stack and fix it ?
daddymikey1975 said:
It's very annoying for me as well.
The other bug that I noticed is after taking a call over BT, when I end the call, the earpiece on the phone starts randomly popping. rebooting fixes it but it still really irks me.
I think the OP is wondering if there's a way to dig around in the BT stack and fix it ?
Click to expand...
Click to collapse
This stuff has been going on since DK28 and before. I believe Rodderick was looking into fixing it from the kernel side, but I'm not sure how much progress has been made. I know it's not as bad as it was on DK28, but still very annoying. It used to happen to me all the time (audio going through earpiece instead of speaker after disconnecting Bluetooth) when I would turn my car off and it would disconnect the Bluetooth to my car stereo. Now that I have the Samsung Car Dock, I just connect Bluetooth for phone only, and use the audio out on the Car Dock for Navigation and Media.
Moved to Q&A.
i am having a simular issue but mine is that when i connect to bluetooth headset i have to have media playing before i get a call or i will not hear the other person in the call.
it seems to me that ANY bluetooth headset with A2DP is doing this and i have tried 3 diffrent headsets. Jabra Stone, Jawbone Icon, and the Blueant T1.
all 3 of these headsets do this. does anyone have any solution yet?
Even if there isn't a fix, I wish there was an app to reset the sound settings post facto. Anyone know of one?
I just want to add my name to the list of those who are affected by this. Glad it's not just me, though. Hopefully it can be debugged easily.
For the record, a Quickboot Hot Reboot (reboot of Android only, not phone) does NOT solve the issue. Only a full reboot works for me. Seems like it may not be a software issue but something hardware-related.
Sent from my SPH-D700 using Tapatalk
Just want to add this happened to me the first time just now. I'm on rooted EC05. I was scared for a bit that the speaker had blown. Then when I discovered it all coming from the earpiece, I remembered this thread. A reboot did make it go away.
I wonder if it has any relation to the issue I see once in a while since the upgrade where my BT devices need re-pairing and ask for a passcode, when they really shouldn't.
I Also Have This Issue
I have had this exact issue since DI18.
After I hang up a Bluetooth call, I have popping sounds coming out of the earpiece. Turning off Bluetooth doesn't fix it. Turning Bluetooth back on after turning off doesn't fix it. In addition, after this happens, all devices sounds (phone ranging, notifications) all come through the earpiece and *not* the main speaker.
I've had all of the stock ROMs up until EC05 loaded on this Epic and have had the same issue throughout. I am now running midNIGHT ROM, which has cured most problems I’ve had with my device, except this issue.
I was just poking around trying to find some sort of tool or the name of the service(s) that I need to restart to fix this issue.
Same issue for me. Quite annoying as I listen to audible over bluetooth quite a bit, and then pretty much know I have to reboot when I turn bluetooth off.
SRF users have reported Bluetooth issues being cleared vs. stock builds. I can't say exactly why, but it does seem to work.
What are SRF users?
Nope...
Syndicate Rom Frozen...
Well, I'm on SRF 1.1.1 and I've got the same incredebly annoying audio issue.
Please, someone, come up with a fix!
Hey everyone. Gotta say, i love this phone its the android device i always wanted. However, im having issues with my car bluetooth which i have not experienced before... namely, that random phonecalls sound completely digitized.
Ive come from an htc desire and htc sensation on the same car without issue and am worried i got a bad BT antenna-or its software...
Anyone out there experiencing the same thing? Any advice (other than buying a new car)?
I am having the same issues on a Verizon Galaxy Nexus V4.02. If I turn bluetooth off mid-call the earpiece sounds fine. The static only happens during voice calls, streaming A2DP sounds fine. There are bluetooth improvements listed in the 4.03 changelog, hopefully this will be resolved.
I had some problems with my BT speaker phone. I turned off the key press sounds and the screen off sounds and that pretty much fixed it.
I have an off topic question for you guys that use bluetooth streaming. Can start the car and press play from the HU to start music? I can with my old D2, but not my TB. I have to actually start the music player on the thunderbolt, then I can control it from my HU. I would like to upgrade, but I don't see a huge advantage in upgrading if I still can't start my music without having to actually take the phone out of my pocket. (Yes, I know it's stupid, but I'm lazy.)
I have this same issue in one of my cars. I ran a number of tests and the issue only occurs on my vehicle when the phone is connected to both for telephony and a2dp music. The static occurs whether or not a2dp is actually being used to stream music or not. This particular vehicle has two separate devices for music and telephony. If I unpair or disconnect the music device, then telephony works without the audio distortion. As soon as I reconnect the music device, the static is re-introduced.
v0yeur said:
Hey everyone. Gotta say, i love this phone its the android device i always wanted. However, im having issues with my car bluetooth which i have not experienced before... namely, that random phonecalls sound completely digitized.
Ive come from an htc desire and htc sensation on the same car without issue and am worried i got a bad BT antenna-or its software...
Anyone out there experiencing the same thing? Any advice (other than buying a new car)?
Click to expand...
Click to collapse
I am experiencing this issue as well and have not been able to resolve it. I've tried disabling the touch sounds, screen off sounds, etc. but to no avail.
It pretty much makes handsfree unusable while driving. What have you guys done in the meantime? Have you been able to resolve the issue yet?
Here's my specific details:
Phone: Verizion LTE Galaxy Nexus v4.02 stock/unrooted
Handsfree Car System (phone audio): Stock 2007 Audi A4
Separate A2DP Module (media audio): Dension Gateway Five connected to factory Stereo
All of my previous phones (Thunderbolt, Droid X, Incredible, OG Droid) have fully supported this setup with no issues whatsoever.
On a sidenote, my A2DP streaming is also unreliable. It first has trouble connecting to the device. If/when it does, audio constantly cuts out when streaming Pandora, Slacker Radio, Google Music... pretty much any streaming over network connection. I have not tried locally stored music yet as I don't have any currently stored on my device. Are you guys experiencing this A2DP issue as well?
I wonder how widespread this is and if it warrants opening an official issue with Google.
I used to have a Blackberry Torch, and I have a Ford Mustang. When I would connect the BT to it, if the Wifi was on, it would "interfere" with the signal. Turning wifi off, fixed the issue. This was a widely known issue with the Torch. Granted that shouldn't have to be a fix, but can any of you verify whether your wifi is on? (regardless of if its connected to anything or not). I'm wondering if the Nexus is using the same BT/WIFI chip that the Torch used.
radi0chik said:
I used to have a Blackberry Torch, and I have a Ford Mustang. When I would connect the BT to it, if the Wifi was on, it would "interfere" with the signal. Turning wifi off, fixed the issue. This was a widely known issue with the Torch. Granted that shouldn't have to be a fix, but can any of you verify whether your wifi is on? (regardless of if its connected to anything or not). I'm wondering if the Nexus is using the same BT/WIFI chip that the Torch used.
Click to expand...
Click to collapse
I appreciate the suggestion but unfortunately, I have the issue even if WiFi is off (I never use WiFi).
I'm going to try and toggle a few of the sound and haptic feedback settings a little more to see if it's pertinent to a certain on/off configuration. It's a shot in the dark but I'll try anything at this point.
ok it was worth a shot. Maybe on a whim turn off 3g/data so basically its airplane mode except BT is on? Just to eliminate any RF interference. Other than that I dont know
Spent quite a bit of time in the car today to try and pinpoint a cause and I have had no luck.
Phone audio will sound great and then all of the sudden turn digitized and distorted for a random period of time, then revert back to sounding great. One thing to note is that the distortion is both ways - the person I'm talking to also hears it when I speak and cannot understand what I'm saying. It's very frustrating not being able to use this feature.
I am on my 2nd replacement phone and ALL of them have had this issue (returned two others to VZW due to this issue and the speaker clicking issue). I am still wondering if it is software/OS releated or if it's due to poor hardware.
Quick Update (kind of):
I messed around with more settings last night. I am happy to report that after I disabled NFC last night, I made several handsfree calls in my car with perfect clarity and no issues. Also, A2DP streaming Pandora worked flawlessly! I was happy that I thought I pinpointed the issue - NFC interference.
BUT this morning, I made a handfree call and it was immediately distorted. Frownie face! A2DP Streaming Pandora still worked great. I am now trying to determine if my success last night was a fluke or if something is different with the phone this morning. The only difference from last night to this morning, that I have been able to identify so far, is I now have the extended battery in the phone. Last night's success had the standard battery. I'll switch them back at lunch and re-test.
Stowegy said:
Quick Update (kind of):
I messed around with more settings last night. I am happy to report that after I disabled NFC last night, I made several handsfree calls in my car with perfect clarity and no issues. Also, A2DP streaming Pandora worked flawlessly! I was happy that I thought I pinpointed the issue - NFC interference.
BUT this morning, I made a handfree call and it was immediately distorted. Frownie face! A2DP Streaming Pandora still worked great. I am now trying to determine if my success last night was a fluke or if something is different with the phone this morning. The only difference from last night to this morning, that I have been able to identify so far, is I now have the extended battery in the phone. Last night's success had the standard battery. I'll switch them back at lunch and re-test.
Click to expand...
Click to collapse
I've got the same issue. Even with NFC disabled. Makes listening to Pandora in the car unbearable. I've gone through the same steps as you, but hasn't exchanged the phone yet. I've had previous Androids and it was a hit/miss with the distortion, but with an iPhone or BB never had this issue. Go figure.
thanks to all the replies, will update to 4.0.3 and try out some more options.
- unplugging my music dongle had no effect on call quality
- NFC on or off had no effect
I also find that the music adapter never auto-connects and needs me to go in to the BT settings page and manually select it.
thanks all.
Hello again. So I have an update that adds to the flakiness ...
Updated to the Bugless Beast ROM and Franco's kernel. My intent was to completely reset the phone and hopefully get a new Bluetooth stack in the process.
Initially everything paired OK, but after a while my audio randomly disconnects after about 20minutes and then reconnects depending on its mood.
My phone connection is more controllable now: if the BT is enabled on my phone when I turn on the car, the sound quality is entirely digitized and unusable. If I turn on the car and THEN enable my phone, the sound quality is flawless every time.
Still not ideal, but manageable. For the music audio part, I lay the blame entirely on the Audi Music Interface BT adapter: the thing is crap and always in pair mode even with the car turned off! The telephone BT in the car head unit has seen several phones pair with it without any issues (I do mobile development so I get to play with many phones) so in that case, I can't blame anything but the Nexus.
I really hope someone at Google or Samsung reads these threads since it would be tough to troubleshoot, but there's no doubt an issue exists with general BT compatibility.
Sent from my Galaxy Nexus using xda premium
Anyone have an update on this issue? Does anyone know of a ROM with a different Bluetooth stack than AOKP? I love everything else about AOKP. I have had the same garbled bluetooth audio from stock - 4.03 with franco and faux kernels with the same result. I had similar problems with Cyanogen 7 ROM I was using on my Incredible the week before I bought the Nexus.
Update - I experimented with a couple of additional devices, and the multiple connections problem with my Nexus is limited to A2DP only devices.
I am now using a Garmin BlueTrip with "phone audio" deselected in bluetooth options. As long as the additional bluetooth device is handsfree profile capable, the A2DP functions perfectly, calls are clear, and the device reconnects after a power cycle consistently. I'm glad this appears to be a software issue and not something we will have to live with for the life of the phone. I'm sure a future update will correct this issue.
I'm also having a problem with Bluetooth calls sounding very digitized and/or choppy. It is bad enough that it can be extremely difficult to make out what the caller is saying. A2DP, on the other hand, has performed pretty flawlessly and the device consistently reconnects each time I get in the car (although it can take up to 30 seconds or so).
I'll have to do a little experimenting with some of the settings mentioned in this thread to see if they have any affect.
On a related note, I feel like sometimes calls made/recieved on the handset can sound digitized as well (although not nearly as bad as over bluetooth). Has anyone else experienced this?
My hardware is:
Verizon GNex (4.0.2)
Parrot MKi9000
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?
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?