Database Info

[Q] SGS and Nokia BH-905 compatibility?

Hi everyone,
I was wondering if anyone here has tried using their SGS with a Bluetooth headphone, eg the Nokia BH-905. I've never had a Bluetooth headphone before, been using earphones with wires since forever, but was thinking of making a transition.
Anyone tried the combination before? Does it work? Whats the quality like ?
I'm alright if it doesn't work for calls or can't control the music eg fast forward rewind etc, it doesn't really bother me as I leave everything on shuffle anyhow. Only thing that matters to me is if it is compatible, and how's the sound quality
Never had a Bluetooth to match to my SGS before, so I don't know how well it works.
It's kinda pricey, so I would like to know if it actually works before buying it.
on the side, anyone using a Bluetooth headphone, and any model you would recommend?

works perfect I´d recommend cheaper version for the not so sophisticated audio consumption
I personally use
LogiLink Bluetooth Stereo Headset V2.0
just google for them.... those are about 12 € and they are worth each cent
I can hear about 10 Hours music with them before the go down....

I have used Nokia BH-503 (or possibly a cheap copy of the BH-503, it was from DealExtreme) with no problems. There is about a 250ms delay on the sound so it's not the best if you want to watch video through headphones because the sound will be out of sync with the video, but it's fine for music.

Thanks for the feedback guys. I ended up going for the Sony DR-BT101, the Nokia BH905 seemed really good, but costs about 4-6 times more than the Sony, which I got for 44euros. Will let you know if its any good after I test it out, if anyones interested

Bluetooth issue when audio jack connected

I am wondering if any of you fellow Verizonites would be willing to help me test this out, as I have already asked my friend with the AT&T version if his does this, and it does not:
When connected to the aux in (very common on cars and stereos nowadays, you know, so you can listen to music off your phones and iPods and MP3 players, etc.) I now have the SAME incredibly aggravating problem I could never resolve with my Fascinate. As usual, I have my bluetooth connected to take the call. When I answer the call, I hear NOTHING over my bluetooth unless I disconnect the audio cable out of the headphone jack!!! This is a huge safety hazard, as it takes your hands and eyes off the road, requiring you to disconnect a cable every time you get a call!!
I called Verizon and complained about this with my Fascinate to no avail. I never had this issue with my Droid X, HTC Eris, or my Galaxy Nexus, another dual core Snapdragon based Verizon LTE phone made by Samsung.
Not to mention the SGS III is laggier and less responsive than my Nexus, although not as bad once you disable S Voice (S is for stupid, by the way, at least in my opinion ... I can't get it to work worth a darn!! Could be that I'm the stupid one, but I've certainly given it a lot of effort in a very quiet environment.)
This is horrible because the screen is incredible, and the battery life far outpaces every other smartphone I've ever had by a ridiculous margin, so PLEASE, fellow Verizon SGSIII friends, help me out if you can!! I don't want to have to return this phone, but reasons to do so are stacking up.
If there's no fix for the audio cable thing, that is a definite deal breaker, and enough to make the phone "defective" in my opinion. That is such a blatant safety hazard. I do NOT want a "Fascinate 2". The other issues pale in comparison to the audio cable issue.
Here is a video of the AT&T version NOT having this glaring safety and functionality issue:
http://www.youtube.com/watch?v=A37p4fF-h-k

This is a glaring safety issue you are right. I planned to have bluetooth on my ear to take calls but have the phone plugged in for music on my car speakers.
The other thing is I bought a Samsung HM7000 thinking it would work with the SAMSUNG S III. Pff. I guess FreeSync App doesn't support the S III yet. I will definitely express to Verizon/Samsung why I have to return this headset if this isn't solved in a few weeks. I will contact Verizon on this.
So this doesn't affect other US Galaxy S III units only Verizon? That's so weird but it also suggests it's an easy fix.

I tested it with Bose Bluetooth earpiece and that works, somewhat. If you have the Aux plugged in and get a call, the phone picks up your voice from the Bluetooth and plays the other guys voice through the Aux. Unplugging the Aux mid-call will route the other guys voice back to the Bluetooth. In both cases both me and my friend could hear each other.
There is a problem though. When the Aux is plugged in, with Bluetooth our not, the call quality will drop significantly. It will sound as if you're in a horrible signal area and will cut out every other second or so making it impossible to carry on a conversation. Funny thing is as soon as I unplug the Aux the call is back to normal and we can hear each other just perfect. It's as if with Aux the noise cancellation kicks in and starts cancelling out everything, including your and the other guys voice, lol. Not sure if that's just my phone or SGS3 in general. I actually intentionally used this "glitch" to avoid taking to annoying person. Just tell them "I'm in a bad area and can't talk" and plug in the aux mid-call and they will stop bugging you as soon as they hear the voice glitch up

My bluetooth headset works fine with the audio out through the "dock" connector.
macdroid01 said:
This is a glaring safety issue you are right. I planned to have bluetooth on my ear to take calls but have the phone plugged in for music on my car speakers.
The other thing is I bought a Samsung HM7000 thinking it would work with the SAMSUNG S III. Pff. I guess FreeSync App doesn't support the S III yet. I will definitely express to Verizon/Samsung why I have to return this headset if this isn't solved in a few weeks. I will contact Verizon on this.
So this doesn't affect other US Galaxy S III units only Verizon? That's so weird but it also suggests it's an easy fix.
Click to expand...
Click to collapse

Same here
Using bluetooth in a 2009 infiniti, AUX jack prevents proper bluetooth calling or receiving. I had come to rely on this in my other phones (HTC).

same here too
I upgraded from a fascinate to a s3 and have the same problem on both phones. It is really annoying and I'd love to find a fix for it.

adsbar said:
Using bluetooth in a 2009 infiniti, AUX jack prevents proper bluetooth calling or receiving. I had come to rely on this in my other phones (HTC).
Click to expand...
Click to collapse
I think I am having the same problem with the Bluetooth in my 2010 G37. It seems like if u connect via Bluetooth for media audio, I can't get calls and vice versa. Plus when I connect to media audio and try and switch back to just phone, it doesn't auto connect when I get in the car.
My Rezound didn't seem to have any of these issues.
Sent from my SCH-I535 using xda app-developers app

This was the case with my 1st generation galaxy s epic 4g. Looks like Samsung still hasn't recognized this as an issue. The smart developers here ultimately fixed this on my epic but my s3 is still suffering from this... Btw I'm on synergy. I would love for someone smarter than me to figure this out. Please, please....
Sent from my SCH-I535 using Tapatalk 2

sinman02 said:
This was the case with my 1st generation galaxy s epic 4g. Looks like Samsung still hasn't recognized this as an issue. The smart developers here ultimately fixed this on my epic but my s3 is still suffering from this... Btw I'm on synergy. I would love for someone smarter than me to figure this out. Please, please....
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I don't know who to blame, Samsung or Verizon. I have the Samsung Galaxy Nexus and it does NOT have this issue. Never had that issue, with stock or custom ROMs. A good friend has the SIII on AT&T and it also does NOT have this issue, as the video above demonstrates. He also owns the Galaxy SII, which also does not have this issue. I used to rock a Droid X. At least my Droid X did not have this issue, although I have read reports of other Droid X owners' phones having this problem. My old HTC Eris also didn't have this issue. But, as mentioned above, my Fascinate does have this issue.
It's horrible. I have messaged Samsung, and they have responded that they are looking into it. It's the same response they gave me several weeks ago when I first posted on the support page on Facebook about this issue. I have also called and complained, after which their support tech said she wasn't yet fully trained on the SGS III yet, and they had a special number for me to call, which of course wasn't open at the time.
If a dev can figure this out, he can at least count on a donation from me.
I am sick of this ... I decided to keep this phone despite this issue, because of all the other goodness it brings to the table (especially battery life!! Wow!!) But this is still a horrible issue.

SirKronan said:
I don't know who to blame, Samsung or Verizon. I have the Samsung Galaxy Nexus and it does NOT have this issue. Never had that issue, with stock or custom ROMs. A good friend has the SIII on AT&T and it also does NOT have this issue, as the video above demonstrates. He also owns the Galaxy SII, which also does not have this issue. I used to rock a Droid X. At least my Droid X did not have this issue, although I have read reports of other Droid X owners' phones having this problem. My old HTC Eris also didn't have this issue. But, as mentioned above, my Fascinate does have this issue.
It's horrible. I have messaged Samsung, and they have responded that they are looking into it. It's the same response they gave me several weeks ago when I first posted on the support page on Facebook about this issue. I have also called and complained, after which their support tech said she wasn't yet fully trained on the SGS III yet, and they had a special number for me to call, which of course wasn't open at the time.
If a dev can figure this out, he can at least count on a donation from me.
I am sick of this ... I decided to keep this phone despite this issue, because of all the other goodness it brings to the table (especially battery life!! Wow!!) But this is still a horrible issue.
Click to expand...
Click to collapse
I have the same problem - my 2008 Tundra does not have A2DP for audio streaming, but does have BT for phone calls (and works great). On my previous Droid2, I could use the AUX jack for music and the BT for calls no problem. Now, with the S3, if I hook up AUX for music and BT for calls, then when a call comes in the phone keeps the audio out going to the AUX jack while my truck switches to BT for sound. Therefor, I can't hear the other person (but they can hear me) unless I unplug the audio jack.
From what I've found on the net, it seems it's something in the bluetooth settings/drivers in how Samsung has them implemented on the phone, which is not the same as how they are implemented in the Motos and HTCs. I was unaware that other carrier versions and/or certain other Samsung phones (S2, Nexus) did not have this problem.
For now, I've solved it by getting my hands on a car dock for the ATT Infuse 4G, which has the "dock" mode built into the USB connector with both power and audio output. I dock my S3 into this dock and changed the settings to output audio out the dock. Then I plug my AUX cable into the dock and it works like I expected it to from the start.

CIPuyleart said:
I have the same problem - my 2008 Tundra does not have A2DP for audio streaming, but does have BT for phone calls (and works great). On my previous Droid2, I could use the AUX jack for music and the BT for calls no problem. Now, with the S3, if I hook up AUX for music and BT for calls, then when a call comes in the phone keeps the audio out going to the AUX jack while my truck switches to BT for sound. Therefor, I can't hear the other person (but they can hear me) unless I unplug the audio jack.
From what I've found on the net, it seems it's something in the bluetooth settings/drivers in how Samsung has them implemented on the phone, which is not the same as how they are implemented in the Motos and HTCs. I was unaware that other carrier versions and/or certain other Samsung phones (S2, Nexus) did not have this problem.
For now, I've solved it by getting my hands on a car dock for the ATT Infuse 4G, which has the "dock" mode built into the USB connector with both power and audio output. I dock my S3 into this dock and changed the settings to output audio out the dock. Then I plug my AUX cable into the dock and it works like I expected it to from the start.
Click to expand...
Click to collapse
Does the S3 fit into the dock ok? Any stability problems? And you get proper 3.5 inch output for your car's input, plus your bluetooth call works? I have the same kind of deck in my Freestyle. Installed it myself. It does bluetooth for calls but not A2DP. Thanks for your responses so far! I am willing to buy a dock if it works like that. I would just appreciate any reassurance you could give me that it will work out ok ...

but that's a really nice idea that i didn't consider. I would really like to get this thing working and willing to apply any dev fix. what's interesting is that skype calls work fine, yet regular phone calls do not i'll give this doc a try.

Ok, I have the dock now, and wanted to update everyone on this. Audio quality is good, better than bluetooth, but an ever so slight downgrade from just plugging straight into the headphone with an audio cable, but it's certainly good enough.
The one thing that is annoying enough to prevent me from using it is that there is an audible click between each song. I haven't a clue how to get rid of this!! ARGHH!!! I haven't tested the dock with video or pandora output to see if the clicks persist, but as of right now, it's a bit annoying on a long trip. Otherwise, this would work really nicely, and is a pretty cheap fix for $18, not to mention getting a fully functional windshield/dash mount to use your phone as a GPS with.
Hoping my new ROM I installed might solve the audio issue. It has a custom kernel, and possibly improved car dock compatibility. We shall see...

Hello everyone!
I just upgraded to the SIII from my Droid 4 and am having this same issue. Does anyone have a fix? It seems silly to have to buy additional items to get it to work when it worked fine on other phones.
I like the stock ROM, but will flash if necessary to get this to work, as its very distracting while driving.

misterpat1975 said:
Hello everyone!
I just upgraded to the SIII from my Droid 4 and am having this same issue. Does anyone have a fix? It seems silly to have to buy additional items to get it to work when it worked fine on other phones.
I like the stock ROM, but will flash if necessary to get this to work, as its very distracting while driving.
Click to expand...
Click to collapse
SoundAbout Pro is an app that will override Samsung's stupidity when it comes to BT/AuxJack audio routing. Well worth the price of admission.

[Q] Nexus 5 Bluetooth and wired headset problems

Hello,
Pardon if this has been answered already, I simply did not find my exact question answered.
I am using my unmodified Nexus 5 (not even rooted), with the latest KitKat (v.4.4.2 build KOT49H) with quite a few wired and wireless headsets and people always complain they cannot hear me. Eventually I got my hands on an old Samsung Galaxy S2 and tried my best bluetooth headset with it: Imagine my surprise, I could hear myself quite clearly even when I was talking really really softly, barely above a whisper. My headset is excellent. My phone is not.
My questions revolve around what to do about it.
Nothing in KitKat allows me to adjust the bluetooth microphone gain, nor does it let me use an equalizer on my microphone. I can adjust the volume of the headset, but this does not do anything to the microphone gain.
So...
Question 1: am I the only person with this problem?
Question 2: what do you people do about it?
Question 3: are there any mods / custom ROMs out there that attempt to fix this problem? Google does not appear to be interested in doing so.
Thanks in advance!

*bump*
Any ideas? I have tried re-pairing my bluetooth headset - no go. I have tried flashing custom ROMs and kernels - no go again. It seems to be a problem with the phone, but I have no idea how to fix it. And Google searches always return other people having this problem. Noone with solutions, though.
Using a wired headset results in even worse results, if that were at all possible.
Has anyone tried to replace the bluetooth stack or driver with something that works?
Thanks!

*bump*
Yesterday I spent quite a few hours tinkering with my phone. I tried every last radio out there for the Nexus 5 and none had any effect on bluetooth microphone levels. Then I tried a few AOSP ROMs: CM11 and Omni. They turned out to be so closely related I might as well have just tried one. None had any effect on bluetooth microphone. Heck if CM11 doesn't do it, there really are no alternatives out there! I tried the FauxAudio tweak, even paid $2 to Faux, which successfully managed to do nothing: app didn't was written badly. Finally, I tried a bunch of volume boost tweaks. That worked, actually. That is, it boosted the wrong volume. Finally, in a moment of true and utter desperation, I opened an ADB shell and edited that mixer file by hand. I then discovered that microphone gain on bluetooth is not controlled there.
I tried all my wired headsets again: Etymotic HF3's microphone produces such an atrocious sound, if I am to rely on it I need to seriously consider becoming a mime. Then there were my Bose QC15 headphones with a remote cable for Android by some off-brand company: that was terrible, the cable is useless. Heck, not even mime lessons can help me there.
Eventually I chanced upon an old microphone cable for my QC15 headphones. Just microphone, no remote. Surprisingly, this one is loud and clear! That after being anything but loud or clear on my old cell phone. Interesting. Unfortunately, it's been out of production for a few years. My working theory is that Bose realized putting a decent microphone on expensive headphones gives people real value, makes them spend money, and that way lies madness. We can't have that, can we. So when that cable starts cutting, so does my use of this cell phone.
I am screwed.
In any case, I will stop bumping my own thread, you guys obviously don't know a solution or there would have been a lively conversation right now. And I am pretty sure there is a moderator or two frowning right now, possibly getting ready to throw an encyclopedia at me. My only hope is that Google is going to do something about that pesky Broadcom driver that doesn't work sometime before the mass exodus to the iPhone. And before my precious microphone cable stops working, or I will be leading the way for that exodus. It's a phone, damnit, if it doesn't work like one it's no good.
Hmmm.... it should be possible to wire a good lavalier mike on a cell phone cable... maybe I can get an op-amp from an old tape recorder to get decent amplification... When attaching a 9V battery on my headphone cable begins to look appealing, we really have a problem.

Yes, if nobody reply you is because no one can help u.
But for what it's worth, i had an Xperia Play for 2 years. Using an Motorola Bluetooth Headset H350 while driving and a MW600 Sony Ericsson Stereo Bluetooth Headset, both never had a problem.
Now from 2013 Christmas both headsets with my new N5: still never a problem and not noticing any low volume or mic. Sorry

same issue
Dany XP said:
Yes, if nobody reply you is because no one can help u.
But for what it's worth, i had an Xperia Play for 2 years. Using an Motorola Bluetooth Headset H350 while driving and a MW600 Sony Ericsson Stereo Bluetooth Headset, both never had a problem.
Now from 2013 Christmas both headsets with my new N5: still never a problem and not noticing any low volume or mic. Sorry
Click to expand...
Click to collapse
hi,
i am having the same issue with my Nexus 5 in combination with my Logitech H800 Wireless headset (people can`t hear me).
Anybody who did find a solution for this?
Thx

pitchdown said:
hi,
i am having the same issue with my Nexus 5 in combination with my Logitech H800 Wireless headset (people can`t hear me).
Anybody who did find a solution for this?
Thx
Click to expand...
Click to collapse
No solution. I tried everything, everything I could think of. I got FauxAudio to work eventually and that did nothing for Bluetooth performance (and it said it wouldn't, but I was desperate).
I returned a lot of high end bluetooth headsets over this issue. Eventually I came upon the Plantronics Voyager Legend. I would like to tell you this really expensive headset works fine, but no - microphone gain is still low, though this time around people can hear me okay. Not great, just okay. I am using that now. It's not perfect, it's far from perfect, but finally usable. Sort of. If I speak loudly.
For what it is worth, the ElementalX kernel improves Bluetooth stability on the N5 quite a bit. Microphone gain is still low, though. Another thing that sometimes helps a little is turning off the multimedia profile on the headset, though why THAT would make a difference is beyond me.
All we can do is wait, watch the Samsung Galaxy S5 get released and wonder if we should switch.

kangelov said:
No solution. I tried everything, everything I could think of. I got FauxAudio to work eventually and that did nothing for Bluetooth performance (and it said it wouldn't, but I was desperate).
I returned a lot of high end bluetooth headsets over this issue. Eventually I came upon the Plantronics Voyager Legend. I would like to tell you this really expensive headset works fine, but no - microphone gain is still low, though this time around people can hear me okay. Not great, just okay. I am using that now. It's not perfect, it's far from perfect, but finally usable. Sort of. If I speak loudly.
For what it is worth, the ElementalX kernel improves Bluetooth stability on the N5 quite a bit. Microphone gain is still low, though. Another thing that sometimes helps a little is turning off the multimedia profile on the headset, though why THAT would make a difference is beyond me.
All we can do is wait, watch the Samsung Galaxy S5 get released and wonder if we should switch.
Click to expand...
Click to collapse
Somebody advised me to download the app "persist"
This is free from the playstore.
Can you try this and let me know this is working for you?
Thx

pitchdown said:
Somebody advised me to download the app "persist"
This is free from the playstore.
Can you try this and let me know this is working for you?
Thx
Click to expand...
Click to collapse
This app controls the bluetooth volume, not the bluetooth gain. The bluetooth volume was never a problem.

kangelov said:
This app controls the bluetooth volume, not the bluetooth gain. The bluetooth volume was never a problem.
Click to expand...
Click to collapse
Ok,
i am having the problem with my Logitech H800 headset with the nexus 5.
So this is a android kitkiat 4.4 issue?
Or is this problem only on several Nexus 5-devices?

pitchdown said:
Ok,
i am having the problem with my Logitech H800 headset with the nexus 5.
So this is a android kitkiat 4.4 issue?
Or is this problem only on several Nexus 5-devices?
Click to expand...
Click to collapse
My guess is either the bluetooth baseband or the bluetooth kernel driver used in the N5 is flaky. This is why I think so:
Problem does not exist on my old Samsung Galaxy S2, including when it runs the same nightly of CM11, nor does it exist on my computer or my desk phone. All the headsets I've owned performed admirably there, so the headsets are not directly the cause. From what I've seen no ROM and no kernel out there seem to be making a difference as far as Bluetooth gain is concerned, the problem is persistently there and the same. Best I could tell it's just the N5 with a problem and it's just for the phone profile. I've tried the Bose headset (the worst performer headset with the N5 of the lot) on a colleague's N5 and his phone was just as bad with it as mine. I am not sure if it's a small batch of N5s having a problem, I don't own lots and lots of N5 phones to try on, but I doubt it: with anything digital things are usually all-or-nothing and the N5 has an off-the-shelf Bluetooth chip, which is not unique to the N5. My guess is it's the entire model, but having only tried on 2 N5 phones, this is no more than a guess.
From what I saw online, the entire Nexus line has poor Bluetooth performance, not just the 5, and Google changed the Bluetooth stack with KitKat besides possibly introducing more problems. If you have a non-Nexus phone, the manufacturer most certainly replaced the Bluetooth driver and radio with one of their own, so problem goes away, but the Nexus line does not enjoy such attention.
An interesting thing to try would be for someone to put the LG G2 Bluetooth driver on a N5 kernel and try it out. I don't have the time or the expertise to do that, but there are plenty of people who do. Assuming the G2 does not have problems with bluetooth gain, if the problem still persists it will tell us if it's the N5 baseband or hardware doing it, and noone can help us there if that's the case.

I have this problem too, using my Nexus5 with iphone headsets. Peoples told me in skype and hangouts, that they hear me bad...

Shiver2005 said:
I have this problem too, using my Nexus5 with iphone headsets. Peoples told me in skype and hangouts, that they hear me bad...
Click to expand...
Click to collapse
That's a different problem. The wired headset problem is easily solvable with FauxAudio and a supported kernel.

This maybe realted to the changes Google made to the core Bluetooth stack as of Android 4.3+ I know they made adjustments for the BLE [low poer Bluetooth devices like pedometers and other senor type crap]. It is BEYOND me as to why Google keeps adding functionality ot the core Bluetooth stack when it is GLARINGLY OBVIOUS they have real problems with Bluetooth as a whole. WHY NOT fix the core issues so Bluetooth is much better at the basics before trying to add functionality or more complex?
I know they complained it would cost a bit for a different newer Bluetooth license but I mean in my personal experience with many different phones Bluetooth is SUPER flaky even at it's best in Android, and does not even work the same way across devices [I have used 3 different Jabra speakerphones on my bosses Galaxy 3 recently and they all worked to varying degrees even though they all use the same version of Bluetooth protocol], but my T989 [Galaxy 2 T-mobile], my parents G2s My bosses older Bionic, My fathers new Droid X, etc. all have random problems. You can usually find one device that works well with a certain phone/ROM, but that can change between ROM versions and devices so it is like you need to go and buy 1 of everything every time there is an update and go crazy finding the ONE that works [and as noted on page 1 with the gentleman using the same Platronics Voyager Platinum as I have it is a super expensive very nice device that worked BEAUTIFULLY in ICS, but now in 4.1 + you can not get more than 1 or 2 words across the mic unless you are YELLING at it like a crazy person on the SAME device].
So all that to say I think it is prolly related to changes Android made in 4.3+ flipped the Bluetooth operability on it's head.

Mic Volume OK with KitKat 4.4.4 and cheap "HB-800" headset
there've been no posts for a while so maybe the problem has gone away with the KitKat updates.
But anyway:-
I have a Nexus 5 and recently bought a cheap generic stereo earbud headset with mic from eBay .... $14.82 Ozzie including delivery to Western Australia.
I've actually asked the other party whether they can hear me (specifically "am I loud enough?") because I read this thread and have been assured that it's all good.
In fact it's a pity the sound quality at MY end isn't better, but that's probably the low quality ear buds rather than electronics / firmware reasons.
Of course, ymmv.
Here's the ebay item title in case anyone wants to look it up or I can pm the item number if it helps.
"Headphones Earphones with MIC 1st Stereo Bluetooth Hands-Free Wireless HV/HB-800"

No, the problem is still there. Reason there are no posts is that no one has a solution. Nothing has changed since March. I am somewhat controlling it with CM11 running on the ElementalX kernel. Without this kernel Bluetooth performance is unbearable. With it it is barely adequate.
It's funny that a cheap headset would work okay while multiple top-of-the-line everything-but-the-kitchen-sink models like the Plantronics Voyager Pro would still be having problems.
I was seriously considering getting the OnePlus One, the Nexus 6 and even the iPhone 6 hoping the issue would finally be fixed. It's ridiculous that a phone commonly accepted as the measuring stick of the Android world would be having problems with simple tasks like driving a bluetooth headset. *very disappointed*

Me too. Two days with my new N5 and when I use my Sony SBH20 people hear me bad... With my N4 no problem. Its annoying! Ive to speak with headset because Ive problems with my left arm and legs, I only have the right to hold the phone, I cant do anyhing more and when I walk I need that arm to hold my cane.
I dont see a real solution, I will have to return the N5

Annoying buzz or static noise when using headphones in Nexus 5

For your information.
-Unrooted, it only has the Aviate launcher but this thing has been going on weeks before it.
-No cellular service(I am using it only at WiFi. It is like as if it were an iPod touch.)
-Happens in videos, YouTube daily motion etc.
-Only when using earphones.
Hey forum! I once again bring up another problem with my Nexus 5. I had it for 60ish days, and this thing has only been occurring for a few weeks. It is this annoying sound which occurs when I plug my headphones and watch some YouTube videos. Initially I thought it was my headphones, but I used two and found that the problem was the same. I believe it is definitely my Nexus 5, but I do not know why and how. It is a pest to me which I want to exterminate, and I gladly could use some help. Is this worthy enough to send back and get a new device? If so, what do I need to be aware of (additional charges, if I can ask for a new color etc).
I found this video which has strong resemblance to my problem only his occurs on speaker. https://www.youtube.com/watch?v=6XZSef6fuKU&feature=youtube_gdata_player
Thank you for your help,
EL
Sent from my Nexus 5 using Tapatalk

I'm having the same issue on my N5 (stock, rooted). I've been searching online, but have yet to find an explanation or solution. I'll report back here if that changes.
Hopefully somebody else on this forum can chime in with some useful information.

I'm getting an annoying buzzing through my headphone jack as well. Noticed it more when playing through my car stereo. I'm inclined to say it's software related, not hardware. Hopefully in 4.4.3 there will be something that will take care of it. I can't see the hardware degrading that quickly, i've only had my phone for less than 4 months and this issue is just starting.

So I think I solved this problem on my phone. Before, I was having glitchy hiccups at least once per song. This hasn't happened once in the past two days since I went into the xposed module gravitybox and disabled "More music volume steps." Hopefully this helps someone else or perhaps inspires them to their own solution.

ancient light said:
So I think I solved this problem on my phone. Before, I was having glitchy hiccups at least once per song. This hasn't happened once in the past two days since I went into the xposed module gravitybox and disabled "More music volume steps." Hopefully this helps someone else or perhaps inspires them to their own solution.
Click to expand...
Click to collapse
I do have more music steps in the ROM settings I changed, but not on Gravity Box. I'll have to see if those are possibly a cause.

I have the same issue but also when playing music using the internal speakers of the phone. It happens when playing music with Spotify and YouTube but I do not think it ever happened to ingame music of any game.
I will also try the XPosed module and report back if it worked..
Edit: Using this tweak of GravityBox did not work for me. The buzzing continues

everyone with this problem
does it only happen when you have the phone plugged into a car or home charger?
i have always gotten this on all my android phones when charging and listening to music in my car or with headphones.. its just one of those things that happens because all the components inside our phones arent shielded as well as they should be

It does not has anything to do with the charger because it happens without it plugged in

Does anyone have updates on the issue? It still occurs on my phone, even on Android L. So I guess it cannot be a software issue

Mine does this all the time when I'm watching videos on YouTube on speaker or headphone... On every ROM from stock to slimkat (using now) and sometimes through the music player. I'm guessing it's some sort of WiFi interference?

My newly acquired Nexus 5 also suffers from this issue
It's exactly the same as in the video. And I don't know why, it's more apparent when watching youtube videos, and much less common when listening to music (both locally with Poweramp and while streaming with Spotify).
I also can confirm this has nothing to do with the device being in charge or not.
Help??

I'm going to buy Nexus 5 soon and that issue sounds really bad to me. Any more information about it? I listen to music on my phone every day and I'd be really disappointed if the noise happened to me.

For me that issue stills persists after over half a year of owning the Nexus 5. I tried several ROMs, some Audio Mods. Nothing helped. I guess it must be a hardware issue.
I wrote a ticket about it to LG, but never got an answer. Since there is not much discussion about it in the internet it appears like it is only an issue with a small amount of devices. So if you are going to buy one the chances are low to get this bug.

You are probably right but when I consider my luck, I still get worried. Keeping my fingers crossed though Thanks for an update.

i think all nexus 5 devices have it, but not everybody notices it.
from my experience with various brands, as much as i dislike them as a company, but samsung has the best headphone jack sound output.

rayiskon said:
i think all nexus 5 devices have it, but not everybody notices it.
from my experience with various brands, as much as i dislike them as a company, but samsung has the best headphone jack sound output.
Click to expand...
Click to collapse
I see. I'm not a big fan of Samsung either, I had some phones from them and I didn't really like those Also for comparision, HTC Desire Z's sound that was coming from the minijack output was perfect for me on my Soundmagic PL11 buds (I'm not an audiophile).
I need to get a new phone anyway and Nexus 5 seems to be something I was looking for - cheap, powerful and comes with Full HD screen. Even if headphone jack isn't going to work well...

TheReduxPL said:
I see. I'm not a big fan of Samsung either, I had some phones from them and I didn't really like those Also for comparision, HTC Desire Z's sound that was coming from the minijack output was perfect for me on my Soundmagic PL11 buds (I'm not an audiophile).
I need to get a new phone anyway and Nexus 5 seems to be something I was looking for - cheap, powerful and comes with Full HD screen. Even if headphone jack isn't going to work well...
Click to expand...
Click to collapse
The headphone jack on the N5 works well, i listen to music through my phone almost on a daily basis, so you don't have to worry about that, but i've come across the glitch linked in OP several times, and it can be reproduced. it doesn't just appear out of nowhere.

i had have this issue from when i bought my device
Annoying buzz and static noise but ya live with it ,regard's joe.

since upgrading to lollipop i can notice this sound glitch (while listening to music over headphones) more often, it occurs once in every 10min for sure... it's really annoying

I hope it's not placebo, but for me, since the lollipop upgrade, I haven't noticed this noise. I've even been listening to more music than before, as this quite got on my nerves, but now it seems to be gone.

Bad sound quality through Bluetooth

I'm having bad sound quality when making call through Bluetooth in my car. It sounds like the audio is breaking up. Anybody else have this problem? My note 3 was working just fine through bluetooth
Sent from my One using XDA Premium 4 mobile app

I also noticed the same thing yesterday driving home. I did not have this problem earlier in the week. I'm not sure what is going on. This along with a strange wifi problem has recently surfaced. If I leave my wifi range and then return, it does not want to reconnect. I have to toggle the airplane mode then wifi will reconnect. I am running stock 11s rooted with 2.7.1.0 TWRP, Xposed framework, Xpoxed GEL, Gravity Box, Tasker, Autovoice.

richeazy said:
I'm having bad sound quality when making call through Bluetooth in my car. It sounds like the audio is breaking up. Anybody else have this problem? My note 3 was working just fine through bluetooth
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you still experiencing poor Bluetooth audio in your vehicle? Mine is still the same.
Sent from my A0001 using XDA Free mobile app

kevinga said:
Are you still experiencing poor Bluetooth audio in your vehicle? Mine is still the same.
Click to expand...
Click to collapse
I am. I'm looking for suggestions for things to try and improve the stuttering/skipping/dropouts that I'm experiencing when using my OnePlus One in media playback mode through my Chevrolet MyLink car radio. I have some additional details to offer and things I have tried:
1) The playback application doesn't seem to make any difference, the problem is most pronounced (unlistenable) when playing back music files and is highly annoying when listening to speech (e.g. podcast) files. I suspect the difference is the music having a beat that gets interrupted while there are some normal pauses in speech so the stuttering blends in a bit more. In any event, it's not a problem with the playback application.
2) It seems unlikely to be a problem with the car radio (Chevrolet MyLink). Though I haven't done extensive testing I have done some using my old Motorola Atrix HD with a nightly CM11 on it from a few weeks back and that does not seem to have the issue, or at least it is not nearly as severe.
3) When I use a third party bluetooth audio receiver (some cheap no-name one from ebay) the quality seems to be fine but when I try to go directly to the car stereo I get tons of stuttering/skipping/drop outs.
A friend suggested that I try running an alternative kernel and see if that improves things. Any ideas on whether that may be the case or which one might be the best to try? Any other suggestions? It's quite annoying that I can't playback audio through the car radio...
Thanks!

Anyone have any ideas? I tried running the Franco kernel tonight and it seems to have the same issue. I did some logcat captures and I seem to be getting a lot of "W/bt-btif ( 2104): btif_media_aa_prep_2_send congestion buf count 24" messages when playing back audio through the car radio. See the attached full logcat captures with both the stock and Franco kernels and connected to both an alternative Bluetooth dongle and to the MyLink car radio.
Any suggestions?

After further testing I was able to determine this is an issue with the phone and not the car radio as I was able to find at least one other BT device which exhibits the same issue. I have created a ticket for this issue at: https://jira.cyanogenmod.org/browse/BACON-1005 if you are also experiencing this issue you are encouraged to go and vote for the ticket.

One question though. Do you have WiFi on when traveling in your car? Try turning it off and see if you still get skipping.

I do in fact have WiFi on at all times. I tried turning it off for the day today while doing some driving and it appeared to clear up the problem. I would think it's still a bug because having WiFi on should not prevent BT audio from working correctly but it at least gives someone a direction to investigate.

So I've done some slightly longer term testing and what I can say is the problem is not totally cleared up when WiFi is off but it is much, much better (definitely listenable). I will still get a couple dropouts when first starting a stream (sometimes, not always) but after 30 seconds to a minute it seems to settle down and be fine as long as I keep the WiFi off.

BenFranske said:
So I've done some slightly longer term testing and what I can say is the problem is not totally cleared up when WiFi is off but it is much, much better (definitely listenable). I will still get a couple dropouts when first starting a stream (sometimes, not always) but after 30 seconds to a minute it seems to settle down and be fine as long as I keep the WiFi off.
Click to expand...
Click to collapse
Just to clarify the situation..
My Xperia Z2 have the same issues.. It is not your phone but the Bluetooth stack in android that pretty much sucks the problems you are dicribing has been there since android 4.2 on a lot of devices.
I have just changed my Lumia 1020 out with this Z2 and call me disappointed in music quality! On the Lumia you would have trouble hearing a difference between jack/auxiliary and Bluetooth..

And today I did notice some dropouts even with WiFi off well into my drive but it was just a few packets I would guess more of an annoyance than a serious problem. I've heard about issues in the Android BT stack but the confusing part of that is why certain devices (such as my Atrix HD) don't seem to experience the problem.

I have a bluetooth stereo I use every morning in my home and a bluetooth stereo in my car. I almost exclusively use pandora, but I have also used power amp on longer trips. I have never experience this issue with my opo. I have ran 25-33 all rooted with no problems and am currently using CM11 nightlies. I also am not having any wifi issues.
Sorry it's not very helpful, but it doesn't sound like a widespread issue at least.

It certainly has something to do with the particular bluetooth implementation used by the receiver interacting with the OPO. As I indicated I have three different BT receivers I can test with and the problem affects two of them but not the other.