Database Info

Video Chat = Low Volume

Anyone else experiencing this in Qik? Tried over wifi and 3G, downloaded all updates. The volume is very low. Does this happen to anyone else?

OMG yes! I thought I was the only one? It's too damn hard to hear who I'm talking to. The person even asked me why I would bring the phone up to my ear every time he spoke. I hope an update can fix this.

I experienced the same thing using Tango. Tried doing a test chat with my friend on his iphone. He kept asking me to repeat myself and said the volume was low. I could hear him fine.
So, just to see, I tried it with the headphones and mic... MUCH better, he could hear me fine.
At first I thought it was the case maybe getting in the way, but taking it off didn't help at all.
Not sure what to make of it... hopefully, it is just some software problem and nothing major.
This is my first post BTW... After leaving the iphone a couple of months ago I have tried 3 Samsung Captivates (Galaxy S), 2 G2's, and 2 MT4G's... I think I finally got a keeper. This thing is redonkulous!
Legaleye3000 said:
Anyone else experiencing this in Qik? Tried over wifi and 3G, downloaded all updates. The volume is very low. Does this happen to anyone else?
Click to expand...
Click to collapse

same - tried over data and wifi. However... girlfriend used headphones and no headphones, and iphone head phones... could barely hear here. it would cut in and out sometimes too... she couldn't hear me half the time either... helllppppp this is why we bought this stupid phone!

i had the same problem today, i hope it's just a matter of an update, other than that this phone is awesome! i can't believe i got a MyTouch after having a g1, i thought i'd be a loyal vanilla user but this phone was too sweet to pass up

lol @2071. Yea I'm about to get it Tomorrow coming from a g1. I wish this was vanilla, or i can at least root

Double check that your call is going through the speakerphone. Is it possible that the video call audio is defaulting to the earpiece? I wonder because if it sounds normal using headphones then there's probably nothing wrong. Just a guess.

The other side they can hear me perfectly. Its just my ability to hear them. During the call, if I push the volume keys, the volume meter comes up on the phone as "media volume." Also, if I make a regular non-video call and put it on speaker, the speaker is LOUD. So its just confined to video calls..... Also, other media (music) is LOUD.

Ya I have also tried Tango and its the same low volume on The network or my wifi. I haven't tried headphones yet though.
from Snugs hTc ViSiON

I can confirm low volume as well. Seems to work way better with headphones in for both sides.
Sent from my HTC Glacier using XDA App

Alright, well make sure you all call in to tmo tech support so this becomes a known issue quickly!

im not experiencing low volume... what i am experiencing is when talking to my friend, I had to switch the mic on and off each time I wanted to talk and hear him.. kinda like a 2 way radio

GB..Bluetooth Audio messed up :(

Can someone please confirm that their BT Audio still locks up after about 1hr? Yesterday after installing GB i have noticed that my BT audio locked up and phone says it is connected by no audio comes out. This is the same behavior i have on the Froyo version. The only way to release or fix it is a reboot. I really need BT to work i hate holding phone to my ear. Anyway can someone please confirm that theirs is doing the same thing. I have BlueAnt Q2. I also have another BT and i do believe the froyo version did the same thing with the other BT so i am sure it will happen with the GB version.
PS: the other thing that does not work with the BT is uploading contacts on the BT. This worked fine with Froyo.

can anyone confirm their BT Audio is working for more than 1-3hrs?. I am re-testing and will keep updating on what i find out.

UPDATE: BT has been on for exactly 2hrs and still working. I am currently testing it with the Jabra BT3030. I will report back.
PS: i have made and received calls using this BT just incase.

I've found that for when my BT locks up I can disable it then re-enable it, but it takes between 5-10 tries of re-enabling it before it takes. Probably faster to reboot, but I've had an aversion to rebooting ever since using the G1.

Bluetooth seems to be working better for me with this update. It has not yet failed to pair with my cheap Sony head unit, both handsfree and A2DP.
A2DP in particular used to suck. More than half the time when I'd start my truck the music icon would be missing from the Sony's display, but so far this build's A2DP seems to work right every time just like with my N1.
Navigation instructions through my car stereo FTW!

UPDATE: it is now 6hrs and 32mins into this testing and so far it is holding steady with the Jabra BT3030. I will keep on testing and report back.
PS: I am really amazed how well optimized the battery now is with this GB build.

cenwesi said:
UPDATE: it is now 6hrs and 32mins into this testing and so far it is holding steady with the Jabra BT3030. I will keep on testing and report back.
PS: I am really amazed how well optimized the battery now is with this GB build.
Click to expand...
Click to collapse
So it won't play nice with the Q2? Frack!

mr mystery said:
So it won't play nice with the Q2? Frack!
Click to expand...
Click to collapse
I am not about to rule that out just yet... Waiting to see what happens once i get past 8hrs. I will test Q2 next. so far i am really impressed with the battery optimization on this GB. Once i start freezing things or use one of those custom roms i am sure battery life will be even better.
PS: i wonder if they is any firmware update for the Q2?

mr mystery said:
So it won't play nice with the Q2? Frack!
Click to expand...
Click to collapse
I have a q2 and was connected yesterday for about 3 hours without issue. Was able to make and receive calls during that time without bluetooth disconnects. I did have a disconnect when I first updated (without rebooting), but after I rebooted my bluetooth worked fine.

matyou98 said:
I have a q2 and was connected yesterday for about 3 hours without issue. Was able to make and receive calls during that time without bluetooth disconnects. I did have a disconnect when I first updated (without rebooting), but after I rebooted my bluetooth worked fine.
Click to expand...
Click to collapse
Were you able to upload your contacts? Could you do me a favor and leave it on all day for as long as you can to see if it locks up or you get NO audio. I am about to begin the test for the Q2. So far the Jabra BT3030 seem to be working just fine. Now 8hrs and 20mins and no issue.

I have a Q2 also and I'm constantly turning off and on bluetooth and the headset itself. etc etc, reboot.. damn. I changed from a Jawbone ERA (which was having issues also)
Using the EB 105gb leak rom atm and was using the stock g2x w/faux uv kernel earlier.

I have a Q2 that locks up on EB Froyo, but I love EB Froyo and the only reason I would update to GB is to fix the BT problem with Q2. Please let us know if your Q2 test is positive.

My q2 would not transfer phone book and has lost audio a few times today. Its more stable than stock but the previous gb leak worked perfect for me. Let me also mention that Bluetooth works perfect on cm7, phone book also transfers as well. I see myself going back to cm7 soon mainly because of Bluetooth.
Sent from my LG-P999 using Tapatalk

matyou98 said:
My q2 would not transfer phone book and has lost audio a few times today. Its more stable than stock but the previous gb leak worked perfect for me. Let me also mention that Bluetooth works perfect on cm7, phone book also transfers as well. I see myself going back to cm7 soon mainly because of Bluetooth.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Which rom? Or just straight CM7 (which build too? or any/all?) ?
PS
I'm on a stinkin Wired Headset atm, so I'm quite interested. (0.0)b

Well guys, i can almost confirm it does lock up or looses audio. After over 9hrs testing the Jabra BT3030 i had NO issue with that BT. Charged phone up to 97%, reboot the phone and added the Q2. 1hr and 30min into testing it locked up or lost audio. This was after multiple calls and playing few songs just to make sure i haven't lost audio.... I don't know what to make of it. I don't know if it is the Q2 or our phone. One thing that i noticed and saw this on Froyo as well as other GB roms is that when you turn off the BT on the phone and try to re-enable it in like 2-3secs its like it is still trying to shutdown or something. After about 1-2mins it is back to normal....
As far as not being to transfer contacts to Q2 i can tell you that i spoke to BlueAnt tech support tonight and found out that if you have contacts on your sim card, it confuses the hell out of Q2. This wasn't the case for other roms that i tested or Froyo. I ended up taking my sim card out and guess what, it uploaded the contacts to Q2. Anyway i am thinking about taking my Q2 back to AT&T to see if i can exchange it for another one to see if that will solve this problem seeing that i bought it December of 2010.
Please i ask others that have the Q2 to leave BT and Q2 on for over 4-5hrs and see if it stays connected.

cenwesi said:
Please i ask others that have the Q2 to leave BT and Q2 on for over 4-5hrs and see if it stays connected.
Click to expand...
Click to collapse
I dont need to wait 4hrs to tell you, my problem with it is exactly what you described.
On another note.
Least I only got my q2 a week ago, I can still return it to Bestbuy this weekend.
Dunno what else to get that has a2dp though. Other than jawbone(have/had them all) what headset on the market would anyone suggest or recommend? I had the Discover 975 worked great until I lost it, no a2dp though.. Had the Bose which was fun, but no a2dp either... any suggestions?
That and of course possibly switch to CM7.1 rc1? Except no A2dp.. which defeats the purpose of the whole paragraph above. haha.
What are you leaning toward, Cenwesi?

hiazn said:
I dont need to wait 4hrs to tell you, my problem with it is exactly what you described.
On another note.
Least I only got my q2 a week ago, I can still return it to Bestbuy this weekend.
Dunno what else to get that has a2dp though. Other than jawbone(have/had them all) what headset on the market would anyone suggest or recommend? I had the Discover 975 worked great until I lost it, no a2dp though.. Had the Bose which was fun, but no a2dp either... any suggestions?
That and of course possibly switch to CM7.1 rc1? Except no A2dp.. which defeats the purpose of the whole paragraph above. haha.
What are you leaning toward, Cenwesi?
Click to expand...
Click to collapse
Well i know for sure the Jabra BT3030 works but does not have the phonebook feature so i am leaning towards it. I really think people with A2DP really need to test theirs and then we will know for sure if it is the Q2 or is the the phone or software. Very hard to tell right now.

Lol, looks like it just locked up again. This time more like 2hrs.

cenwesi said:
Well i know for sure the Jabra BT3030 works but does not have the phonebook feature so i am leaning towards it. I really think people with A2DP really need to test theirs and then we will know for sure if it is the Q2 or is the the phone or software. Very hard to tell right now.
Click to expand...
Click to collapse
Hows the sound quality with the 3030? How well does the other person hear you from where it normally hangs if you wear it around your neck? Hows the noise cancellation and the quality of your connection to your phone?

hiazn said:
Hows the sound quality with the 3030? How well does the other person hear you from where it normally hangs if you wear it around your neck? Hows the noise cancellation and the quality of your connection to your phone?
Anyone got first hand experience with the Jabra Stone 2?
Click to expand...
Click to collapse
Sound quality is fine and people here me just fine. Noice cancellation is fine.

[Q] Skyrocket mic issue? or software?

Hi,
I was very excited to get my Skyrocket, but after a day of using it, people I called to reported that there's a weird problem with the call audio quality. For a few seconds my voice seems to be muted out, like speaking very distant. This has gone on for many calls at different locations.
Frustrated, I sent the first one back and got another one. It came today and I was very excited. I tried it and there was no problem. Then a couple of hours later, the same problem came on.
This is really weird. I don't think it's a hardware problem since it has happened on both phones, the second of which is brand new. Makes me wonder if it's a software problem. But this did not happen on my HTC Inspire which had the same set of apps as the Skyrocket.
Does anybody encounter the same problem? Know any tests/ fix for the issue? Or even heard of something similar?

Do you have a case on your phone? If so, perhaps it's covering the mic???
Sent from my SAMSUNG-SGH-I727 using XDA App

I've noticed this phone needs to be right up On Your face for anyone to hear you..
Sent from my SAMSUNG-SGH-I727 using XDA App

Disable the setting that is mic noise cancellation, that's what is causing it.
Sent from my Rocket that is in the Sky!

I am having the same issue where my voice seems fading/distant according to anyone I talk to. I exchanged it once and still have the same problem. I don't really know the problem so I just use BT headset for calls.

Longcat14 said:
Disable the setting that is mic noise cancellation, that's what is causing it.
Sent from my Rocket that is in the Sky!
Click to expand...
Click to collapse
Mines not on
Sent from my SAMSUNG-SGH-I727 using XDA App

nap286 said:
Mines not on
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
Hmmm... my phone was doing the same thing, turned off noise cancellation, fixed.
Sent from my Rocket that is in the Sky!

I have had the identical problem as the original poster. I received my Samsung Galaxy S II Skyrocket on January 18, 2012. Starting immediately, during phone calls, the other party would tell me that my voice cut out, sounded distant and tinny for a few seconds at a time. When using a bluetooth headset, the problem never occurs, so I ruled out the mobile network as the cause of the problem. I do not have a case for my phone, so that is not the cause of the problem.
I exchanged the phone for a brand new Skyrocket, which I received on February 3, 2012. Same problem with the new phone. I am nearly sure the problem is with the noise cancellation hardware/software. It seems to get worse if I hold the phone touching my ear (the noise cancellation microphone is on the top edge, near where the phone will touch the ear).
Besides this defect, I like the phone a lot. Now I must decide whether to use the phone with noise cancellation turned off, or give up on Skyrocket, return the phone, and choose another Android phone.
Are all Skyrocket owners using their phones with noise cancellation turned off? This is a very serious defect.

krazylove said:
I have had the identical problem as the original poster. I received my Samsung Galaxy S II Skyrocket on January 18, 2012. Starting immediately, during phone calls, the other party would tell me that my voice cut out, sounded distant and tinny for a few seconds at a time. When using a bluetooth headset, the problem never occurs, so I ruled out the mobile network as the cause of the problem. I do not have a case for my phone, so that is not the cause of the problem.
I exchanged the phone for a brand new Skyrocket, which I received on February 3, 2012. Same problem with the new phone. I am nearly sure the problem is with the noise cancellation hardware/software. It seems to get worse if I hold the phone touching my ear (the noise cancellation microphone is on the top edge, near where the phone will touch the ear).
Besides this defect, I like the phone a lot. Now I must decide whether to use the phone with noise cancellation turned off, or give up on Skyrocket, return the phone, and choose another Android phone.
Are all Skyrocket owners using their phones with noise cancellation turned off? This is a very serious defect.
Click to expand...
Click to collapse
No problem on mine.... with or without noise cancellation... in spite of what you said, it does sound like a network issue... do you notice this everywhere, or just in some locations?
Sent from my SGH-I727R using xda premium

shaggyskunk said:
No problem on mine.... with or without noise cancellation... in spite of what you said, it does sound like a network issue... do you notice this everywhere, or just in some locations?
Click to expand...
Click to collapse
It has occurred in many different locations.
In the course single phone call, I can experience the problem using the handset, then switch to a headset and the problem stops, and then go back to the handset and the problem picks up again. I am going to start using the handset with noise cancellation turned off, and I'll report back on how that works.

krazylove said:
It has occurred in many different locations.
In the course single phone call, I can experience the problem using the handset, then switch to a headset and the problem stops, and then go back to the handset and the problem picks up again. I am going to start using the handset with noise cancellation turned off, and I'll report back on how that works.
Click to expand...
Click to collapse
My observations:
No issues when using bluetooth headset or loudspeaker.
I experience the problem when using the wired headset, and handset with or without noise cancellation.
I probably have a defective phone but did not bother to exchange it again. I use bluetooth headset all the time.

lyndone58 said:
My observations:
No issues when using bluetooth headset or loudspeaker.
I experience the problem when using the wired headset, and handset with or without noise cancellation.
I probably have a defective phone but did not bother to exchange it again. I use bluetooth headset all the time.
Click to expand...
Click to collapse
Had the same problem as you. I got a SIM replacement and turned off noise cancellation.

Mic Issue Continues
After looking into reviews of this phone, and subsequently buying one in June, I can't believe I missed this issue. Alas, over the past few months, most recipients of my calls as well as callers to me cannot hear me unless I'm speaking loudly into the phone. To make matters worse, I can't simply tilt the phone to my mouth and back to my ear because the motion sensor will activate the screen and my cheek will touch the "end call" button. I have already turned off noise suppression and still, it's a problem. I have already "talked loudly" and then normally, and still, no dice. I have also switched to speakerphone, then back to normal and still, no dice. This is painful. It makes the "phone" useless. (I have not tried switching to Sky ICS.)
Has anyone found a solution to this design flaw besides a headset? Will adjusting the mic gain work? If so, what code do I need to adjust the mic gain?
Rooted Skyrocket. AOKP Milestone 6

My wife is having this exact same problem on her Skyrocket too.
She was on the official ICS from ATT and then I tried CM9 and nothing seems to make any difference.
Anyone found any more info?
You think it's worth exchanging the phone or just a bad design in the hardware?

SimonNWalker said:
My wife is having this exact same problem on her Skyrocket too.
She was on the official ICS from ATT and then I tried CM9 and nothing seems to make any difference.
Anyone found any more info?
You think it's worth exchanging the phone or just a bad design in the hardware?
Click to expand...
Click to collapse
I hear installing the Sky ICS ROM may solve the problem. If that is the case, then it is not a hardware design flaw but possibly noise suppression run amok (regardless of whether the option is unchecked). That would seem to be consistent given the mic location has not changed in the Galaxy line of phones. Further, speakerphone works flawlessly.
If Sky ICS works or if I find a "mic gain" solution, I will report back.

guys try rooting ur skyrocket and flashing a new kernel

Bluetooth issue when audio jack connected

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Headset not fucntioning in call mode at all!!

Hi all,
I have successfully rooted and flashed Paranoid Android 2.54 onto my ATT HOX and it is a wonderful ROM for sure. I love the options that it provides and the silky smooth, almost stock interface. The only real issue that I have come across is when I try to use a headset for calls. I am defining a headset as a 3.5mm plug in set of earbuds with mic (Klipsch S4i to be exact). When I listen to music, be it on Pandora, Google Music or Apollo all is well. As soon as I try to use the phone, no sound comes through the earbuds and the mic does not function. In fact you can see a noticable slow down in the dialer app when the headset it even plugged in. If I make a call, then plug in the headset, everything goes silent and the other side can't hear me until I unplug the headset from the phone.
Here is the real kicker though! I have my car stereo modded with an aux 3.5mm plug for listening to music and if I plug the phone into that it works just fine in phone mode! Now, I do realize that the Klipsch is setup as a TRRS and the car aux is just TRS (so when using the car stereo I am effectively bypassing the mic portion of the 3.5mm plug and using the phone's mic), but I cannot for the life of me understand why the headset will not work.
I am hoping that someone can enlighten me or least tell me that they to are experiencing this same issue. I will gladly provide any more info that someone might need to help diagnose the issue, and thanks in advance!

Update so far...
So, up to this point here is what I've found. If I plug in a normal set of earphone (read buds only no mic inline) then I will get sound through them no matter what I am doing (youtube, music or phone). Also, in this configuration anyone I am talking to on the phone can hear me just fine as I am using the phone's mic. However, when I plug in an earbud/mic combo the phone will not function. I get silence and the other side cannot hear me speaking either. It's as if the software has somehow told the headphone jack to act differently than it used to with earbud/mic combos. I am stumped as to why the OS would not allow this type of use when it is so standard. Anyone have any thoughts?

I actually have the same headset and I started having problems with it on the stock rom before I even rooted and flashed a custom one. I honestly just thought it was because they're really made for apple phones. Sometimes I'll just unlplug and plug them back in for them to register. Other than that I haven't seen a fix for them.
P.S. Klipsch control from the play store seemed to make things worse for me

sourshin said:
I actually have the same headset and I started having problems with it on the stock rom before I even rooted and flashed a custom one. I honestly just thought it was because they're really made for apple phones. Sometimes I'll just unlplug and plug them back in for them to register. Other than that I haven't seen a fix for them.
P.S. Klipsch control from the play store seemed to make things worse for me
Click to expand...
Click to collapse
Thanks for the response! Yeah, I think I am going to try another ROM just to see if it will help, but I have the distinct feeling it might be a hardware issue. I just can't understand why this would all the sudden malfunction right after rooting for me. Maybe just a coincidence. I will definitely respond here though if flashing to a new ROM helps...

guitarman710 said:
Thanks for the response! Yeah, I think I am going to try another ROM just to see if it will help, but I have the distinct feeling it might be a hardware issue. I just can't understand why this would all the sudden malfunction right after rooting for me. Maybe just a coincidence. I will definitely respond here though if flashing to a new ROM helps...
Click to expand...
Click to collapse
I've never tried paranoid but King kang(which has paranoid elements) works fine for the most part. nocturnal'd dirty rom, miui, and cm10 have all worked for me tho. I'm currently on the unofficial cm10.1 4.2 and that's working for me as well, except when I have the headset plugged in while booting.

Final Update....And SUCCESS
So, it appears that it was some sort of ROM specific issue. I flashed CleanROM 5.1 to my phone and "wah-lah"! The headset works perfectly in all modes. I am not sure what it was about Paranoid Android 2.54 that would not allow the headset/mic combo to work with the phone, but I am free of it now I guess. I will miss the interface of PA, but boy does CleanROM run FAST!!! I am in awe of the speed and responsivness. I hope the battery life holds up like PA did for me and I also think that the quick settings on CleanROM basically RULE.