I always use my bluetooth headset when talking to family and friends(due to the length of time, hate holding phone). Since, I switched from my nexus one people have griped about the interference/noise they hear when I'm on my bluetooth headset. It is not my BT headset as I've tried a few(motorola S305, and two smaller bluetooth earpieces), all of which exhibit the noise. I was wondering if anyone else has had this problem ?
Running the Galaxy S I9000 ROM rooted.
Everyone complains about hearing me whenever I try to use a headset. Seems like the stack sucks or the radio is terrible.
Got the same problem. My bluetooth calls are loud and clear on my side, but everyone on the other side complains about static noice and I sound very distant.
I tried the original ATT rom (stock unrooted) and the most current 2.1 that is available for download. No difference.
Any ideas what to try to remedy this?
I haven't noticed anything like this on my Motorola S9-HD headset.
I have noticed sometimes it will cut the music every once in a while, whereas my iPhone never did.
konawayne said:
I always use my bluetooth headset when talking to family and friends(due to the length of time, hate holding phone). Since, I switched from my nexus one people have griped about the interference/noise they hear when I'm on my bluetooth headset. It is not my BT headset as I've tried a few(motorola S305, and two smaller bluetooth earpieces), all of which exhibit the noise. I was wondering if anyone else has had this problem ?
Running the Galaxy S I9000 ROM rooted.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
This is a known issue with the I9000 ROM... Bluetooth doesn't work well for some...
I'm running the stock rom... is that the I9000 rom?
None of my friends have mentioned such a problem when i've called them, although I've only made bluetooth calls a couple of times (including on the bus and at home).
Using after-market Nokia BH-503s.
I'm definately seeing the same problem on the stock rom. Not as bad as athe I9000 ROM but still bad enough for them to complain. Seems like it's made worse by the different roms/kernels we've been flashing but there's definately a problem.
wpb2 said:
I haven't noticed anything like this on my Motorola S9-HD headset.
I have noticed sometimes it will cut the music every once in a while, whereas my iPhone never did.
Click to expand...
Click to collapse
I'm seeing similar symptoms, except my music cuts out every 30 seconds or so. My setup is a Kensington iPhone adapter connected through aux input in my car with an Anycom FIPO on the iPhone adapter (it converts the iPhone/iPod adapter into a bluetooth receiver). I then stream from my Captivate to the adapter and it works fine except that it cuts out every 30 seconds. Did you ever figure out how to fix it?
UPDATE: Just wanted to add that I figured out what was causing my problem: having Wifi turned on. Once I turned it off, my bluetooth streaming worked beautifully, with no hiccups.
Still have a problem with this. Stopped using my BT headset completely... sucks having this thing stuck to my head for calls.
I have encountered several problems:
Party can not hear me at all; though I can hear fine.
Party hears tinny sound to my voice.
Headset disconnects while playing music.
Using a Motorokr S9-HD. Works fine with Samsung A-737.
I too have the static problem. This phone sounds wonderful on my end, but everyone complains that that can't hear me! This is so far the only complaint I have.... I hope someone will have a fix, or come up with something.
I have this problem too !
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.
Mic Issue With Speakerphone Calls
I purchased a Verizon Galaxy S6 last week and have been enjoying it so far. Today I tried out the speakerphone several times and every time the person on the other end could not hear me. Is this a software or hardware issue? Is it defect or user error? What can I do to fix this? Any help in resolving this matter would greatly be appreciated. Thank you for your help.
-EDIT-
To clarify the microphone does work fine for normal calls. Does the Galaxy S6 use the same mic for both operations? Also, I have tested with and without case on. It seems like a secondary mic or software issue. Is there a secondary mic for the S6? If not then what software or settings could be effecting the speakerphone mic functions?
The Galaxy S6 I believe is like the Note 4 in regards to microphones. When you turn speakerphone on the mic at the top of the phone near the IR blaster is enabled, when just using the phone the mic on the bottom of the phone is enabled. My Note 4 had an issue, on speakerphone mode the people I tried calling could hardly understand me and it kept breaking up my voice to them. I ended up having to send it in for a warranty claim.
There are a couple holes at the top of the S6 on either side of the IR blaster. I haven't been able to dig up any reliable specs. I was hoping for a software fix, but understand hardware might be a likely culprit. Do you think there is any reason I should not take it back other than the cost of time to me waiting in the store and reloading accounts onto the phone?
Exchanged it this morning. Thank you for your help. Problem is fixed with new unit.
S6 MIC not work - all possible answers listed
So I have been struggling with this since opening day!
When the watch is connected to my 6P (and my Nexus 6 before that - which was not Marshmallow) I can answer and make calls from the phone, but the audio and mic always default to the watch. This is super annoying. Verizon sent me a new watch which does the same. Samsung says it's a Marshmallow problem. Google says its a Huawei problem. And they send me back to Verizon.
So, what I have resorted to is waiting for the call to connect and then on the phone override the BT audio to handset prior to talking. What a hassle!
If you override the BT audio on the phone's BT setting for the S2, then you are no longer given the option to take the call on the S2 (of course).
Anyone have a similar experience? What to do next?
I have the same exact problem with the S2 3G paired with the Nexus 6P. I unchecked phone audio in the phones bluetooth settings but as you said, it disables the option to use the S2 as a phone. Hope there is a solution soon.
Seems to not be fully compatible with marshmallow yes
I have this issue as well. Also when I make a call with my phone (Nexus 6) the call is always completed on the watch via Bluetooth connection. I have to switch back to the phone on the watch during the call.....
Sent from my Nexus 6 using XDA Free mobile app
Update - Sammy Boo
Spoke with Samsung again. I thought the Gear Manager update yesterday would fix this - no deal!
Samsung is now claiming this is a software upgrade with the Gear S2 and is intentionally programmed functionality! Really?
I requested an escalation to their development team as a software enhancement to revert to prior functionality - they assured me that would happen, and they'll send me a notification from their team; problem is, they did not take any of my contact info!
I'm having an issue with CM13 on a Note 4 with a Gear S2. I changed the build.prop from Samsung to HTC to allow the Gear app to function (it doesn't like CM on Samsung phones) and all seemed well. When I try to click send to take a call, nothing happens. When I receive a call I only have the option to reject it from my watch. My watch is not activated, I don't need 2 numbers.
After spending hours on the phone with Verizon and Samsung I flashed a TW based rom and calls instantly worked. I'm pretty happy with my CM rom and I'd like to find a way to get it to work with that rom.
Did this ever get resolved?
I had Samsung Gear S2 with my Note 7 and life was awesome! Then tragedy struck and my life with a good phone is put on hold for at least 6 months, until the S8 series releases in Feb?/March?/April? of 2017. Until then, I decided to limp along with a somewhat cheaper Nexus 6P. The problem is, it throws all my incoming calls over to my Gear S2 instead of picking up on the phone handset. I then have to choose the drop down option to use my handset instead. This is NOT the intended operation. If I wanted to answer the call on my watch, I would answer it on my watch. I don't want to answer on my phone and then have my watch pick up. There is no way that I have found to correct this. This is terrible functionality for an otherwise very promising piece of technology (the watch, no the phone).
I have the same issue on 6p on ATT. What I normally do is like said above is uncheck the Bluetooth handset under Bluetooth settings. Then just turn call forwarding on..Therefore when I want to take calls on the watch I just wait about an extra 10secs. Or of course answer on the phone.
BTW when i had a samsung S6 this was not an issue...
Bizarre issue. It seems that lately my first phone call from my 2015 CRV results in louder than normal ringing and static-y voice noise from the person on the other end. I have to hang up, redial, and then it is fine. It happens with every first call I make or receive when connecting to bluetooth in the car. At first I thought it was an issue with the phone being rooted(sounds ridiculous I know) but that wasn't it. It seems to be on Marshmallow. I went back to Lollipop 5.1.1 and low and behold there is no issue. I took my girlfriends Galaxy S4 and paired it with my car and there was no issue at all. I don't want to waste my time bringing my car into the dealer because I have a feeling they won't know what to do so I figured I would ask here. I have deleted the pairings multiple times too when dealing with the issue. TIA
Well obviously it's a problem with marshmallow so I would wait for an update or stay on lollipop
Sent from my Nexus 5 using Tapatalk
Yeah agreed although pretty annoying.