Hi all
I hope someone can help me solve an issue. I've had a gear s2 for a couple weeks and am pretty happy with it on the device side.
The problem is that when it is bt connected to my Motor X Pure my phone seems to ignore the proximity sensor when I am on a call. The result is that when I raise my phone to my ear the screen doesn't shut off and I end up with all kinds of phantom button pushes from my ear.
I have tested the sensor and it is working when this happens. Moreover when I disconnect from my s2 from my phone the screen shuts off as expected when I raise my phone to my ear.
Has anybody else experienced this issue and does anybody have a fix?
Further, my watch is a t-mobile 3g variant and has not been activated. Would activating it potentially change znything? Finally, my phone is unrooted as I like android pay. But I am willing to root if there is a way of fixing this.
Thanks
DZ
Related
I am using a Jawbone Era with my HTC Sensation and lately I'm having problems with it.
My phone will be connected to the headset, but sometimes while I'm on a call or listening to music it'll suddenly play the sound through the phone instead of the headset, even though on the phone it is still connected.
Today I realized when I place my phone flat on a surface this problem occurs, and when I immediately lift it off, the sounds plays through the bluetooth again.
Is there something faulty with the hardware or software?
Any help is appreciated, thanks.
Sounds like you're activating the speakerphone by placing it face down on a flat surface. This is a feature of the phone, but I didn't think it would pay attention to the phone's proximity sensor if bluetooth was turned on and being used. I guess it does. Does it ever do it if you haven't activated the proximity sensor?
Hi all,
Just wanted to put this out there to see if anyone else had experienced this. Using SGS2 skyrocket - stock 2.3.5 UCKK1 (rooted) and then updated UCLA3 everything (rooted) - When on a phone call after sometimes 1 minute and then other times 5 minutes my microphone stops working and the other person cannot hear me. I can hear them fine, but they cannot hear me.
Wired headphones work without an issue, but the internal mic seems to have an issue with my phone. a work around I read for the non LTE SGS2 works where you hit the speakerphone button and then they can hear you again and if you turn it off it buys you another 5 minutes or so on mic.
So frustrated with this that I am doing an exchange today on the phone.
Just wanted to see if anyone else had experienced and if there was a know n problem with the phone? Google and XDA returned very little.
Thanks!
MB
Hey I too also have this issue, I had a temporary fix which lasts longer than turning on the speaker but it's still temporary, I have the skyrocket on Rogers and I called them in about it, apparently it has something to do with the network, they did some reset and told me to restart my phone and it worked for about a week or so, hope this helps, if anyone has a fix to this please reply
I read another case like this awhile back, try searching it up. i believe it was rma'd though
I have a very similar problem, I go "in and out" a lot. The problem is the noise canceling mic on the top of the phone by the headset input, I left myself voice mail on my home phone and while talking moved my finger gently over the tiny microphone hole and that causes me to go in and out.
For most turning of Noise Suppression in settings will work, for me it does nothing as if it is perma on lol except on ICS where it actually turns off (dont ask me I have no idea why)
Hi, I have an issue slightly different than the ones I've found from searching. I have an unrooted Nexus 5 on Tmobile. the proximity sensor SEEMS to work, it turns the phone off when I talk but it CONSTANTLY hanging up, muting, or putting calls on speaker. I didn't have this issue with my previous nexus 5 and since I've gotten the new one (new out of package, replacement for previous which was stolen) I've dropped maybe 40% of my calls on accident and maybe 10-15% of calls accidentally put on speaker/muted.
Frustrating when you're in a phone job interview and you keep hanging up on the interviewer. I tried using a friends bluetooth ear piece for awhile just to see what would happen and it just did the same thing except in my purse/pocket.
Is this maybe a sensitivty setting I can adjust or should I take it to nearby T-Mobile store to be serviced/replaced?
Diabolicbutterfly said:
Hi, I have an issue slightly different than the ones I've found from searching. I have an unrooted Nexus 5 on Tmobile. the proximity sensor SEEMS to work, it turns the phone off when I talk but it CONSTANTLY hanging up, muting, or putting calls on speaker. I didn't have this issue with my previous nexus 5 and since I've gotten the new one (new out of package, replacement for previous which was stolen) I've dropped maybe 40% of my calls on accident and maybe 10-15% of calls accidentally put on speaker/muted.
Frustrating when you're in a phone job interview and you keep hanging up on the interviewer. I tried using a friends bluetooth ear piece for awhile just to see what would happen and it just did the same thing except in my purse/pocket.
Is this maybe a sensitivty setting I can adjust or should I take it to nearby T-Mobile store to be serviced/replaced?
Click to expand...
Click to collapse
Do you happen to have a screen protector on?
There isn't any settings you can change unless you root. As the other poster said, the most common culprit is a screen protector that doesn't have a hole for the sensor or is misaligned.
aooga said:
There isn't any settings you can change unless you root. As the other poster said, the most common culprit is a screen protector that doesn't have a hole for the sensor or is misaligned.
Click to expand...
Click to collapse
No screen protector but rooting isn't an issue I've just been lazy and haven't done it yet.
I've had 3 Nexus 5's so far due to one RMA and lastly because of a mistake on Google's part. But with all 3 Nexus 5's I have had two bugs that have been driving me nuts. I was curious to see how many people have had the same problems and if anyone knew of a fix. Bugs:
1) Keypad buttons being pressed while on a call. This happens almost every call. It seems that the screen is still active even if the proximity sensor turns off the screen. I haven't been able to reproduce it on purpose, but every single call I take I hear buttons being pressed. Sometimes it's like my notification bar get's pulled down, then the clock is clicked and I feel all these vibrations and ringing sounds and I look down at my phone and I'm in the date/time settings. This happens even if I don't have the dialer keys open. Weird.
2) Say I'm laying in bed and I answer a call. It seems as if there is some sort of setting for the accelerometer that if my head is tilted too much it's as if the microphone stops working... almost like the phone tries to switch to the second microphone (the one not normally used for phone calls). I can't tell you how many times I've been in bed and get a call from my wife (who works night shifts) calling to say goodnight and if I ever put my head back on my pillow she can't hear a word I say. As soon as I lean forward again she can hear me.
These are two problems that I have had with 3 different Nexus 5 phones. I've experienced the same problem with both Franco Kernel and the stock kernel. I don't know what else to do but it's driving me crazy. Anyone else seen these problems or know of a fix?
Thanks in advance.
Try turning your screen off during a phone call and see if there are still key presses being made. Depending how you hold the phone, the proximity sensor might switch the screen on during your call and could register key presses from your ear. The sensor is on the right side of the phone and will "miss" your head if it's behind it.
Unless you're leaving the digitizer enabled (tap2wake etc.) it shouldn't happen.
The mic issue while lying down seems to be common. Your head/pillow blocks the sound and noise cancelation wigs out. You could alter the way you hold the phone while lying down so the secondary mic at the top sticks out more. Personally, I just sit up and haven't had an issue with the noise cancelation since.
Sent from my Nexus 5 using Tapatalk
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