Related
I've been having bluetooth problems with this phone since day 1 & I'm wondering if it's just my phone or if anyone else is having the same experience. No matter what rom or headset I use, I get a craptastic connection. I don't have any problems pairing devices, but I can't get 10 feet away from the phone without it disconnecting and I can't even turn my head without the audio cutting out. It also randomly disconnects for no reason & sometimes won't reconnect until I reboot. This has happened with every rom I've tried & every headset too. I've bought & returned multiple headsets thinking it was just my Blueant, but it happens with every one.
Could I have a faulty unit or does the bluetooth on this phone really suck this bad? I listen to podcasts & music all day long at work so I need to have a decent connection. Opinions needed please.
I think it may be a bad phone.
I have and used the following bluetooth devices:
Plantronics 590A
Jawbone Icon and Era
BlueAnt S4 which I use in the car. And auto connects before I sit down to drive when I have it on.
Sony Ericsson MW600
And Jabra Pro 9470 (office phone setup that connects to my phone via bt)
All connects without a problem. Have you done a titanium backup and perform a factory reset? And after the reset use titanium backup to restore app and data only and leave the system settings alone. You can restore the wifi stuff if you like. From there that's like a fresh install. Hope that works for you.
Yeah I've done many, many wipes & fresh installs & nothing helps. I don't have any problems connecting, I just have problems STAYING connected & listening to audio. It cuts out constantly without me even touching the phone. I've never had such shoddy bluetooth on any other device.
*sigh* Looks like I may be doing an exchange...
kabuk1 said:
Yeah I've done many, many wipes & fresh installs & nothing helps. I don't have any problems connecting, I just have problems STAYING connected & listening to audio. It cuts out constantly without me even touching the phone. I've never had such shoddy bluetooth on any other device.
*sigh* Looks like I may be doing an exchange...
Click to expand...
Click to collapse
Well before leaving the store...if you are going to a brick and mortar to do the exchange, bring the bt headset with you and try it out there and try to replicate the problem with a new phone.
I do not have range problems but I don't usually have my phone more than 5 ft way from me when talking on it via bt.
I have a replacement on the way for bluetooth problems,people complained of a horrid background noise and the range was maybe 8 feet before major static would kick in
Macklessdaddy said:
I have a replacement on the way for bluetooth problems,people complained of a horrid background noise and the range was maybe 8 feet before major static would kick in
Click to expand...
Click to collapse
My BT sounds like crap! People say it sounds like I'm in a wind tunnel or they can't hear me that well, when they speak to me it cuts in and out.
This is when I connect to my Parrot BT in my truck. I know its not the Parrot system because my HD2 works fine with it.
rosedog said:
My BT sounds like crap! People say it sounds like I'm in a wind tunnel or they can't hear me that well, when they speak to me it cuts in and out.
This is when I connect to my Parrot BT in my truck. I know its not the Parrot system because my HD2 works fine with it.
Click to expand...
Click to collapse
I have a Dual car stereo & now that I think about it, everyone says they can't hear me even though I installed the mic on the side column & it's no more than a foot from my face at any time. Aargh this is so annoying. Freaking $600 phone & my damn $25 RAZR from Big Lots has better bluetooth.
If I bring it to the store, would they exchange it for me? I ordered it directly from T-Mobile, I didn't get it in a store.
kabuk1 said:
I have a Dual car stereo & now that I think about it, everyone says they can't hear me even though I installed the mic on the side column & it's no more than a foot from my face at any time. Aargh this is so annoying. Freaking $600 phone & my damn $25 RAZR from Big Lots has better bluetooth.
If I bring it to the store, would they exchange it for me? I ordered it directly from T-Mobile, I didn't get it in a store.
Click to expand...
Click to collapse
No you will have to call T-Mobile and do a warranty exchange. I have no problems with BT on my phone at all.
http://androidforums.com/htc-sensation-4g/375199-white-noise-bluetooth-htc-sensation-4g.html
http://community.htc.com/na/htc-forums/android/f/133/p/12494/52795.aspx
http://forum.xda-developers.com/showthread.php?t=1184936
a few threads about bluetooth problems
So whats the deal? Has anyone been able to fix the BT problems with this phone yet?
Can we flash a different BT.apk file or something?
Somebody by now should have some answers I would think.
My parrot system in my truck suck ass with this phone. Always cutting in and out.
Streaming audio is fine its the talking to people I'm have problems with.
rosedog said:
So whats the deal? Has anyone been able to fix the BT problems with this phone yet?
Can we flash a different BT.apk file or something?
Somebody by now should have some answers I would think.
My parrot system in my truck suck ass with this phone. Always cutting in and out.
Streaming audio is fine its the talking to people I'm have problems with.
Click to expand...
Click to collapse
I use this with my blueant s4 without an issue and experience no cutting in and out. However, I have been running MIUI and now running sense-o-maniac 3.5 and I have no issues.
kpjimmy said:
I use this with my blueant s4 without an issue and experience no cutting in and out. However, I have been running MIUI and now running sense-o-maniac 3.5 and I have no issues.
Click to expand...
Click to collapse
You've been running what and what?
MIUI / Sense-o-maniac 3.5?
I'm running the latest ARHD w/sense 3.5
horrid bluetooth sound quality
it seems a lot of people have been having issues with the bluetooth sound quality. i have mine paired with a motorola HF850 car kit, which has bluetooth v1.1, or something like that. i wonder if the problem is with backward compatibility, as people seem not to have as many issues with newer devices. would flashing a different radio potentiall help this problem? is it possible to downgrade the bluetooth version with a custom ROM? any other thoughts on ways to address this issue?
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.
I've seen that there are others with this same issue: Popping and crackling sounds while listening to MP3, whether listen to a song or even notification sounds that are MP3. Does not matter if coming from external sd or from internal. Streaming audio is find (Pandora, Sirius, YouTube). As there are a lot of people acknowledging this problem, no one seems to have any solution or idea of what it is. Speaker, BT and headphones all have the "noise". I've seen warranty replacements that still have the same problem, software updates by carriers that after the update, still have the issue. Has anyone else had this continous problem as I have, and anyone know of a solution?
Yep and their is an easy solution, though its better to wait for a fix. Its been fixed in the international version already. It seems to happen because even though the audio player is running, the phone is on the lowest CPU speed and put the audio not as an important task.
I'm running SetCPU and I've tried changing the lowest setting to as high as 1100, it still didn't fix it. All that did was get the phone super hot!!!
Still no one else with this issue on here? It did it on stock right out of the box, All of Synergy ROMs, IMO kernels to date, and BEANS 5 & 6. And Samsung and Verizon say there is nothing wrong with the device. Anybody else having anything similar at all?
Its not just us, some people may not notice it. Its their, and its been on almost every Android phone.
Elite49 said:
Its not just us, some people may not notice it. Its their, and its been on almost every Android phone.
Click to expand...
Click to collapse
Thanks for the reply. I knew I wasn't imagining it. Every notification I get, even my ringtone has it.
I am also having the same problem. Headphones plugged in (NOT the stock ones, one with a TRS plug, not a TRRS plug) and I get the dreaded crackling noise...when I have the USB cable plugged in to the PC (not sure about the wall yet). When I unplug it, the crackling/popping stops immediately. Plug it back in, starts up again. So that's definitely it for me. Do you have it plugged in USB to your PC or wall when this happens or no?
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
Having some very annoying BT issues. Phone pairs fine with pretty much anything. But when streaming audio it cuts in and out pretty frequently but never lost its connection. Called ATT and they sent me a new one. Phone does they same thing. This one actually looses its connection periodically, some days are worse than others. Main issue is in my 2013 Subaru Outback. Does it sometimes with my Phillips BT speaker but not as consistently.
I'm not rooted and have tried both ART and dalvik and the issue is present no matter what.
Since this has happened with two phones I figured I can't be the only one. Anybody else have this problem?
I drive a semi all day, I connect my phone via BT to the stereo and listen to audiobooks/slacker radio for 12 hours a day and have never had this issue. In the BT menu there is an option to 'Turn on Audio Channel Mode' have you tried that? I don't have it on but perhaps it will help? Also I know this phone supports some new BT standards for low power, perhaps this is causing an issue with you devices, I don't know if you can turn that off, or if it's something that is just not very backwards compatible?
i have a similar connect/disconnect issue but only if its not in use it seems. like when its just connected but not streaming i'll notice my car will say it disconnected and reconnected. sometimes when i'm on the phone it gets all staticky and robot sounding...but only with my cars bluetooth. never had an issue with my og pro on 4.4 so i dont think its 4.4. havent done a factory reset yet, hopefully thats all it is cuz there are some other little quirks too
I don't experience audio cut outs, but I do experience severe cracking no matter what tweaks/adjustments I make.
Another problem is that it doesn't read my texts to me while connected to my car. Works fine with my Nokia Lumia 1520 and HTC One x. Its pretty annoying.
You guys should post details on the bluetooth devices you're connecting to. I had a white G3 and now have a black one and both did nothing you guys are talking about when connected to Pyle, Klipsch, Logitech or Chrysler Uconnect bluetooth audio devices. I use Spotify, Car Home Ultra, Google Maps Navigation, make calls via the phone and the Uconnect system will pick up the activity and play the audio correctly, initiate and receive calls in UConnect, Send/Receive Texts via UConnect, control audio volume and tracks. None of that causes disconnects or static for me.
I do have serious problems when playing music with the stock music app over bluetooth. If I try to rewind or ff the G3 starts freaking out and will begin playing the music slower despite not having touched the advanced audio controls. It really sucks. Luckily it doesn't do that with Poweramp or Subsonic clients. Doesn't happen with headphones directly connected either.
If this is not a problem with the G3 when paired to certain devices I think your bluetooth radios are defective. There would be way more complaints if this was prevalent.
---------- Post added at 03:58 AM ---------- Previous post was at 03:51 AM ----------
absinthex said:
I don't experience audio cut outs, but I do experience severe cracking no matter what tweaks/adjustments I make.
Another problem is that it doesn't read my texts to me while connected to my car. Works fine with my Nokia Lumia 1520 and HTC One x. Its pretty annoying.
Click to expand...
Click to collapse
Text reading will depend on your device and your car's bluetooth stack compatibility. My GS5 could do everything but call out in my car. It worked good for a month then an update broke it. iPhone 5S could do everything but read and send texts. My G3 does everything great. If you research your car radio model and the G3 I'd bet you'd see that nobody has it working with the AT&T G3. You may see people with variants have it working especially international. Sometimes there are weird tricks to get things working. I had to disconnect and reconnect my GS5 a few times in order for it to work.
GorillaPimp said:
You guys should post details on the bluetooth devices you're connecting to. I had a white G3 and now have a black one and both did nothing you guys are talking about when connected to Pyle, Klipsch, Logitech or Chrysler Uconnect bluetooth audio devices. I use Spotify, Car Home Ultra, Google Maps Navigation, make calls via the phone and the Uconnect system will pick up the activity and play the audio correctly, initiate and receive calls in UConnect, Send/Receive Texts via UConnect, control audio volume and tracks. None of that causes disconnects or static for me.
I do have serious problems when playing music with the stock music app over bluetooth. If I try to rewind or ff the G3 starts freaking out and will begin playing the music slower despite not having touched the advanced audio controls. It really sucks. Luckily it doesn't do that with Poweramp or Subsonic clients. Doesn't happen with headphones directly connected either.
If this is not a problem with the G3 when paired to certain devices I think your bluetooth radios are defective. There would be way more complaints if this was prevalent.
---------- Post added at 03:58 AM ---------- Previous post was at 03:51 AM ----------
Text reading will depend on your device and your car's bluetooth stack compatibility. My GS5 could do everything but call out in my car. It worked good for a month then an update broke it. iPhone 5S could do everything but read and send texts. My G3 does everything great. If you research your car radio model and the G3 I'd bet you'd see that nobody has it working with the AT&T G3. You may see people with variants have it working especially international. Sometimes there are weird tricks to get things working. I had to disconnect and reconnect my GS5 a few times in order for it to work.
Click to expand...
Click to collapse
I found this, but my 2014 FJ Cruiser isn't on the list, neither is my G3.
https://www.google.com/url?sa=t&so...woHcO6CgPFvWsEew&sig2=QZyBxl51eRFrONj056uGBg
Still looking.
absinthex said:
I found this, but my 2014 FJ Cruiser isn't on the list, neither is my G3.
https://www.google.com/url?sa=t&so...woHcO6CgPFvWsEew&sig2=QZyBxl51eRFrONj056uGBg
Still looking.
Click to expand...
Click to collapse
I'm guessing you don't have the JBL radio. http://www.toyota.com/fjcruiser/features.html#!/interior I love FJCs especially for offroading. They're beasts.
I can't find the model info for your radio. You can check Toyota parts for it. Should be the only one besides the JBL. The notes on that interior page reference needing to have a compatible bluetooth stack. I went through similar crap with my 2013 Durango. Nothing past the Galaxy S 2 from Samsung on CDMA (Verizon or Sprint) works with UConnect stereos for placing calls which can suck really bad if you're moving around during the day. No texts read aloud on my radio will say the number or name because of some issue with the was texts in the US are sent as opposed to international ones.
The G2 works well with the Entune Toyota radios so it looks like you just got screwed with that FJC radio. Those Fj radios have always been kinda outdated and more durable looking if not in function. It's kinda like Wrangler radio systems. They don't want a little mud or water to break em or something.
You could try a work around. You could just toggle Settings >Sound> Message/call voice notifications. It's at the bottom of the Sound page. When it's on its supposed to read the texts for you. If the stereo can pause music during a song to allow navigation commands to be heard it may announce the texts for you. Some radios and phones have problems with that too.
If that works maybe use a shortcut to the Sound settings in an app like Car Home Ultra or use something like Tasker to switch it on when bluetooth connects to your car. That second option would be pretty seamless.

GorillaPimp said:
I'm guessing you don't have the JBL radio. http://www.toyota.com/fjcruiser/features.html#!/interior I love FJCs especially for offroading. They're beasts.
I can't find the model info for your radio. You can check Toyota parts for it. Should be the only one besides the JBL. The notes on that interior page reference needing to have a compatible bluetooth stack. I went through similar crap with my 2013 Durango. Nothing past the Galaxy S 2 from Samsung on CDMA (Verizon or Sprint) works with UConnect stereos for placing calls which can suck really bad if you're moving around during the day. No texts read aloud on my radio will say the number or name because of some issue with the was texts in the US are sent as opposed to international ones.
The G2 works well with the Entune Toyota radios so it looks like you just got screwed with that FJC radio. Those Fj radios have always been kinda outdated and more durable looking if not in function. It's kinda like Wrangler radio systems. They don't want a little mud or water to break em or something.
You could try a work around. You could just toggle Settings >Sound> Message/call voice notifications. It's at the bottom of the Sound page. When it's on its supposed to read the texts for you. If the stereo can pause music during a song to allow navigation commands to be heard it may announce the texts for you. Some radios and phones have problems with that too.
If that works maybe use a shortcut to the Sound settings in an app like Car Home Ultra or use something like Tasker to switch it on when bluetooth connects to your car. That second option would be pretty seamless.

Click to expand...
Click to collapse
Yes, they are! That's the main reason for purchasing one; and that it's the last year that they are being sold in the US, so I thought I'd pull the trigger on one.
But, no, I don't have the JBL head unit. I have the stock FJammer unit, but at least it's an upgraded model of those that were being sold in prior years.
I tried that work around when I first got my phone. Didn't work. I've gone through all Google, Google Now and all LG settings that have anything to do with Bluetooth and TTS. The nagivation works, but when it wants to. Sometimes, it will pause music, whether the music is playing through a CD or Bluetooth, and sometimes it won't pause the music, and it's barely audible. Even though I can hear it, it doesn't mean it's working how it should. When I should be hearing, "In a quarter mile, make a left turn at blah blah..." I really end up hearing, "ake left turn at bla..."
I think I'm just gonna live with it. Hopefully there will be a Bluetooth fix for this when LG releases an update.
Thanks for the replies.
absinthex said:
Yes, they are! That's the main reason for purchasing one; and that it's the last year that they are being sold in the US, so I thought I'd pull the trigger on one.
But, no, I don't have the JBL head unit. I have the stock FJammer unit, but at least it's an upgraded model of those that were being sold in prior years.
I tried that work around when I first got my phone. Didn't work. I've gone through all Google, Google Now and all LG settings that have anything to do with Bluetooth and TTS. The nagivation works, but when it wants to. Sometimes, it will pause music, whether the music is playing through a CD or Bluetooth, and sometimes it won't pause the music, and it's barely audible. Even though I can hear it, it doesn't mean it's working how it should. When I should be hearing, "In a quarter mile, make a left turn at blah blah..." I really end up hearing, "ake left turn at bla..."
I think I'm just gonna live with it. Hopefully there will be a Bluetooth fix for this when LG releases an update.
Thanks for the replies.
Click to expand...
Click to collapse
Yeah I read about it being the last year. If I had it to burn I'd buy one and import a 2014 rereleased 70 Land Cruiser.
Damn that sucks. My Nexus 4 wouldn't make those pauses in music or other audio apps for navigation at all. It really sucked after having it with HTC and Samsung phones for a few years.
There's always those Jabra Freeway & Tour units. Not the best builtin option but a lot cheaper than an upgrade of radio. In my experience counting on a manufacturer fix for stuff like that hasn't worked out for me. That's why I am cancelling my Sprint account this week. I got stuck with a phone that wouldn't work and they wouldn't cut me any slack at all. It's probably because I just moved over from T-Mo.
I hope it works when ATT finally updates us. Rock climbing in that FJ should take your mind off things.
GorillaPimp said:
Yeah I read about it being the last year. If I had it to burn I'd buy one and import a 2014 rereleased 70 Land Cruiser.
Damn that sucks. My Nexus 4 wouldn't make those pauses in music or other audio apps for navigation at all. It really sucked after having it with HTC and Samsung phones for a few years.
There's always those Jabra Freeway & Tour units. Not the best builtin option but a lot cheaper than an upgrade of radio. In my experience counting on a manufacturer fix for stuff like that hasn't worked out for me. That's why I am cancelling my Sprint account this week. I got stuck with a phone that wouldn't work and they wouldn't cut me any slack at all. It's probably because I just moved over from T-Mo.
I hope it works when ATT finally updates us. Rock climbing in that FJ should take your mind off things.
Click to expand...
Click to collapse
It's a damn blast!! Sucks it's my daily driver; I want to mod it out more and more. Thanks for the help. If I ever get this resolved I'll let you know.