Related
I just recently popped my phone's cherry and unlocked the bootloader so that I could get Froyo on my AT&T Nexus One. Before the update I had setup my phone to plug into a car dock with a headphone out to auxiliary jack to my car speakers.
The volume was consistently good to my car stereo when unplugged from the dock and when plugged in before the update. Now, immediately after I plug in my phone to the dock with the headphone jack pushing media audio my volume is reduced by 10-20%. I have disabled the dock managing my media audio, put everything to max volume on phone, and it still reduces the audio as soon as I plug it into the dock.
Does anyone else have a similar setup? I realize mine may be unique and I'm on my own. Are there any deeper phone settings to check beyond the standard volume controls?
Yeah I have the same problem. And my phone doesn't pick up my voice with voice commands and auto brightness doesn't work with the phone in the dock. Makes me wanna go back to Eclair...
Still have not resolved this by any means available. Maybe the official ROM will fix this issue. Also my paid apps still have not shown up and I am noticing that when I pick up inbound calls people cannot hear me for a few seconds.
I was hoping by this point in June that the official Froyo for N1 would have been released and there would be a ROM floating around but no such luck!
I've had a similar problem when my phone is docked with the car dock. In-call volume is extremely low, but other types of media are fine (i.e. music, navi, etc). My volume settings are maxed out too. I hope the official Froyo release fixes this problem. I use my car dock on a daily basis.
Looks like frf83 did not fix it. Car dock is useless for me. Seeing comments frome google that indicate they optimized for the cheesy built in speakers and hosed using the headphone jack while docked.
Pandora during the commute keeps me sane, and this ruins it. No froyo for me until this is fixed.
What I've discovered is when I car dock the phone media volume gets set to 12 out of 15 on the headphone jack. The volume setting GUI doesn't show that the volume has changed. Changing the media volume in settings doesn't affect the volume until I undock the phone.
Unfortunately for me that's too much output for my car stereo and music gets pretty distorted.
I downgraded to OTA ERD79 and the volume would remain the same when docked. I upgraded to the latest OTA and the max volume setting returned.
Having the same problem. At least I found this problem is due to Froyo, not my car dock.
Still, wished the USB port is still open while docked so I can bypass the Car Dock's circuits and just use it as a holder only.
Haven't rooted my phone yet, but if the devs can fix the issue on a custom ROM, I will root.
i used to have this set up where my phone was hardwired to the radio and after froyo i have noticed this problem too. I have now gone back to using a bluetooth connection (kensington liquidaux) and it seems to not have the problem.
for those following the other thread regarding the degradation of quality not just the low volume (double sucky). the bluetooth connection seems to not suffer the same fate.
agentkalaw said:
i used to have this set up where my phone was hardwired to the radio and after froyo i have noticed this problem too. I have now gone back to using a bluetooth connection (kensington liquidaux) and it seems to not have the problem.
for those following the other thread regarding the degradation of quality not just the low volume (double sucky). the bluetooth connection seems to not suffer the same fate.
Click to expand...
Click to collapse
You're referring using Bluetooth vs AUX for the dock and car to communicate? I'm guessing most of us don't have that option on our cars.
Check out the Kensington Liquidaux. It is an aftermarket Bluetooth solution that lets you use any AUX connection.
Sent from my Nexus One using XDA App
seancneal said:
Check out the Kensington Liquidaux. It is an aftermarket Bluetooth solution that lets you use any AUX connection.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Seems like an overkill for $80, especially when I don't need any part of the mount.
cigar3tte said:
Seems like an overkill for $80, especially when I don't need any part of the mount.
Click to expand...
Click to collapse
The one I got was $29. (Edit: I looked all over and can't find it at this price anymore...shoulda bought two!) It just included the cigarette lighter part and a steering wheel remote.
Sent from my Nexus One using XDA App
I have been waiting for a solution and still have not found one. I installed the latest Cynogen V6.0.0-RC1 and when reconfiguring for my dock I got full sound! I was greatly excited! Then... it dropped back down to its normal volume.
I need to figure out a way to disable the phone recognizing the dock entirely since I only use the dock for keeping it stable on my windshield and charging. Anyone have ideas?
norok said:
I have been waiting for a solution and still have not found one. I installed the latest Cynogen V6.0.0-RC1 and when reconfiguring for my dock I got full sound! I was greatly excited! Then... it dropped back down to its normal volume.
I need to figure out a way to disable the phone recognizing the dock entirely since I only use the dock for keeping it stable on my windshield and charging. Anyone have ideas?
Click to expand...
Click to collapse
I don't think the dots would pass through the charge if the phone completely stops recognizing the dock. This problem didn't start until Froyo, I'm pretty sure there'll be a fix for it.
I have the same problem. So much time has gone by since they released the car dock, first it was fine but after froyo the audio settings could not be saves anymore and the volume got much quieter.
No word from Google... nothing, no answer, no patch.
I'm really pissed, the car dock is almost unusable, except you go to audio settings every time you dock the phone and recheck the settings... :-(
there are already some people who reported the problem on the issue tracker. If you have the same problem please star the issue, but avoid giving "me too" comments... as everyone in the thread gets an email for your +1 comment.
http://code.google.com/p/android/issues/detail?id=10466
http://code.google.com/p/android/issues/detail?id=9073
http://code.google.com/p/android/issues/detail?id=8292
http://code.google.com/p/android/issues/detail?id=9747
http://code.google.com/p/android/issues/detail?id=8634
http://code.google.com/p/android/issues/detail?id=9445
google didn't even care to merge issues with the same topic... :-(
I really hope Android 3.0 (Gingerbread) will bring up a solution. (If the N1 will receive it)
Hi guys,
There's so many add-in tools out in the market that can easily solve those volume level issue. (e.g. "Dock Volume", "Car Dock v2", and many "Locale" or "Tasker" apps) So in my personal option, this is not an issue at all.
yang901 said:
Hi guys,
There's so many add-in tools out in the market that can easily solve those volume level issue. (e.g. "Dock Volume", "Car Dock v2", and many "Locale" or "Tasker" apps) So in my personal option, this is not an issue at all.
Click to expand...
Click to collapse
You're completely clueless to the issue at hand, please stay away from this thread. Most of those apps have been around before Froyo was even released.
First off I'm not sure if this is the right forum for this and I also searched for the past few days and have had no luck finding anything much on this. Most stuff I come accross is talking about the phone having a built in fm transmitter that doesn't work - blah blah blah. So here goes, I'm now on Paul's Froyo ROM and for the first time decided to try using the phone for playing music in my car thru a wired fm transmitter and it was not good. I now have three fm transmitters (2 I bought and the final one my brother gave me his that he used to use in his car with no problems) all give me the same results which is it seems okay playing through parts of songs that don't have much bass but once bass starts to hit it gets all awful stattic sounding and the Stereo (ST) indicator on my radio blinks so somehow the sound quality goes all bad. I've narrowed it down to obviously being something with the phone somehow cause I've tried with iPhones and another MP3 player and they (FM transmitters) work perfectly. I've also tried it with IntersectRaven's and CM's kernels for Froyo to see if the kernels might make a difference and no luck. So my question is, is this a known issue with the N1 or is this an issue with Froyo and isn't the case with say CM 5.0.7.1, anyone with experience can shed some light? Was thinking to go back to CM but after seeing all the threads of the issues in doing so decided not to but if this is not the case with other ROMs then it would make me switch back until a official Cyanogenized Froyo is out. If this is the wrong forum then my apologies and Dev's plz move to correct forum.
Update: I've messed with it some more and have been able to get it to play fine with Pershoots kernel but I have to turn down the media volume to approximately 70%. So it seems to me that with the media volume up all the way it must be drawing too much power or something from the headphone jack to make the output all distorted. I haven't tried with IntersectRaven's kernel to say if I get the same result since I'm just happy the darn thing works now. I'll also do a post in the Develoment forum linking to this in case anyone there may want to investigate this issue.
Sounds to me like every experience I've ever had with every FM transmitter. They just don't transmit loudness or bass well. I don't think it's the phone, I think its the FM Transmitter technology.
edit: could just be the volume boost or something on the specific kernel (not even sure if the kernel's you are talking about have a volume boost) but that may increase the max volume out and cause the problem.
derfasaurus said:
Sounds to me like every experience I've ever had with every FM transmitter. They just don't transmit loudness or bass well. I don't think it's the phone, I think its the FM Transmitter technology.
edit: could just be the volume boost or something on the specific kernel (not even sure if the kernel's you are talking about have a volume boost) but that may increase the max volume out and cause the problem.
Click to expand...
Click to collapse
yes exactly, try a vanilla kernel and see how that plays out... I am curious of your findings...
Kman Gymrat said:
First off I'm not sure if this is the right forum for this and I also searched for the past few days and have had no luck finding anything much on this. Most stuff I come accross is talking about the phone having a built in fm transmitter that doesn't work - blah blah blah. So here goes, I'm now on Paul's Froyo ROM and for the first time decided to try using the phone for playing music in my car thru a wired fm transmitter and it was not good. I now have three fm transmitters (2 I bought and the final one my brother gave me his that he used to use in his car with no problems) all give me the same results which is it seems okay playing through parts of songs that don't have much bass but once bass starts to hit it gets all awful stattic sounding and the Stereo (ST) indicator on my radio blinks so somehow the sound quality goes all bad. I've narrowed it down to obviously being something with the phone somehow cause I've tried with iPhones and another MP3 player and they (FM transmitters) work perfectly. I've also tried it with IntersectRaven's and CM's kernels for Froyo to see if the kernels might make a difference and no luck. So my question is, is this a known issue with the N1 or is this an issue with Froyo and isn't the case with say CM 5.0.7.1, anyone with experience can shed some light? Was thinking to go back to CM but after seeing all the threads of the issues in doing so decided not to but if this is not the case with other ROMs then it would make me switch back until a official Cyanogenized Froyo is out. If this is the wrong forum then my apologies and Dev's plz move to correct forum.
Update: I've messed with it some more and have been able to get it to play fine with Pershoots kernel but I have to turn down the media volume to approximately 70%. So it seems to me that with the media volume up all the way it must be drawing too much power or something from the headphone jack to make the output all distorted. I haven't tried with IntersectRaven's kernel to say if I get the same result since I'm just happy the darn thing works now. I'll also do a post in the Develoment forum linking to this in case anyone there may want to investigate this issue.
Click to expand...
Click to collapse
what you are describing is quiet normal if you drive the input of the fm transmitter too hard. You even found out the solution; lower the volume.
Yeh, but the thing that was baffling me was that the iPhones I tried worked fine with volume blasted and so did a MP3 player and that was with 3 different FM transmitters. I originally thought it was the transmitter so that's why I ended up buying another one to try then asking my brother for his which I know he used to have running with no issues. But after thinking about it for a while and searching some more I found posts in the kernel threads about audio boost so that's what made me think to turn the volume on the phone down.
Would like to try a vanilla kernel if you can link me to where to find one that's compatible with Froyo.
And actually I think I'm using CM's Froyo kernel but from what I understand it has pretty much the same tweaks as Pershoot's. Also need to go back to IntersectRaven's and try again with the vol down a bit but I don't have enough battery life left to feel comfortable flashing it.
For the FM-transmitter that I use in my car it's actually stated in the manual that you should keep the volume at about 50% on the device as to not ruin the sound. So I guess this is quite normal and just means you have to adjust the volume on the car stereo a bit.
Kman Gymrat said:
Yeh, but the thing that was baffling me was that the iPhones I tried worked fine with volume blasted and so did a MP3 player and that was with 3 different FM transmitters. I originally thought it was the transmitter so that's why I ended up buying another one to try then asking my brother for his which I know he used to have running with no issues. But after thinking about it for a while and searching some more I found posts in the kernel threads about audio boost so that's what made me think to turn the volume on the phone down.
Would like to try a vanilla kernel if you can link me to where to find one that's compatible with Froyo.
And actually I think I'm using CM's Froyo kernel but from what I understand it has pretty much the same tweaks as Pershoot's. Also need to go back to IntersectRaven's and try again with the vol down a bit but I don't have enough battery life left to feel comfortable flashing it.
Click to expand...
Click to collapse
All kernels are compatible with froyo, just go to the kernels thread and find a sock one
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.
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
Okay so here's the situation. A while back I dropped my phone while earphones were plugged in. It must have damaged the headset jack or something because now when I plug in earphones, if you even slightly move the phone around or have it on you while running or moving around, it activates all sorts or things, from pause/play of music, to starting the music player, to Google voice search. Its incredibly annoying, and I've tried several sets of earphones and the problem persists. I'm all ready rooted running a version of the stock ROM. I don't have any headphones that have controls on them, nor do I intend to get any so I would like to know if it is possible to disable all headset controls. Appreciate any and all help.
I used this to root the phone: http://forum.xda-developers.com/showthread.php?t=2046439
ut_icedragon said:
Okay so here's the situation. A while back I dropped my phone while earphones were plugged in. It must have damaged the headset jack or something because now when I plug in earphones, if you even slightly move the phone around or have it on you while running or moving around, it activates all sorts or things, from pause/play of music, to starting the music player, to Google voice search. Its incredibly annoying, and I've tried several sets of earphones and the problem persists. I'm all ready rooted running a version of the stock ROM. I don't have any headphones that have controls on them, nor do I intend to get any so I would like to know if it is possible to disable all headset controls. Appreciate any and all help.
I used this to root the phone: http://forum.xda-developers.com/showthread.php?t=2046439
Click to expand...
Click to collapse
Maybe try replacing the headphone jack. I purchased this part from ebay last year when my S3 headphone jack would not play audio through headphones. I have had no issues ever since. It's fairly simple to replace and only a few bucks.
Gotta ask, are you sure you are not pressing a button on your earphones to activate any of these settings? My SkullCandy earbuds have a pause/play button that I was previously unaware of.
Just wanted to update. I ordered the part you listed and it fixed the issue. The repair was a breeze too. Thank you so much!