So when I'm talking on the phone up to my ear the screen isn't shutting off and its hitting all kinds of buttons with my cheek lol. Anyway to solve this or do I have a problem with that proximity sensor?
I have been hearing that due to the size of the phone and the location of the sensor, if you hold it to your left ear it may not register. I don't know if that is the case, just something I read on here somewhere.
cmdauria said:
I have been hearing that due to the size of the phone and the location of the sensor, if you hold it to your left ear it may not register. I don't know if that is the case, just something I read on here somewhere.
Click to expand...
Click to collapse
Yep I'm a lefty so that sounds right. I just trued doing it with my thumb and the screen shut off. Guess I'm gonna need to change my grip. Thanks
I have noticed this issue from time to time. I think I found the cause. For me, when my phone is connected to a bluetooth device, the screen doesn't turn off when I put the phone to my ear, even if I'm using the phone's speaker. This is a bug. It should be using the proximity sensor anytime the phones earpiece is used for calls, regardless of whether or not I'm connected to a bluetooth device.
EDIT: Now its working with bluetooth connected. Seems this one is hit or miss. I'll keep playing with it and try to isolate the steps to reproduce the bug.
same issue today
Just noticed the same things happening today. Been using the phone for a week and hadn't experienced this. First noticed when I heard a static sound, which turned out to be the screen activating. Mistakenly put two calls on hold. Will experiment with different grips. Please post any additional findings.
Sliding the phone on my ear actually did stop my problem, I was holding it too low which would be too far to the right, covering the camera and not the sensor which is on the left side of phone
curious to know if you guys have screen protectors on your phone... the one time i had this issue it was with a screen protector. took it off and problem went away. now i'm using an invisishield (?) protector and have not had any issues. thanks.
this is happening to me when I have Google Glass connected via Bluetooth. If I disconnect Glass from Bluetooth, the problem goes away. I will test it out connected to my car Bluetooth and report back. I am not using a screen protector, and it does not seem to matter how I hold the phone. disconnecting the Bluetooth device fixes it immediately.
kregstrong said:
So when I'm talking on the phone up to my ear the screen isn't shutting off and its hitting all kinds of buttons with my cheek lol. Anyway to solve this or do I have a problem with that proximity sensor?
Click to expand...
Click to collapse
Related
HI,
Here's an idea for developers who doesn't know what app to write next.
I was thinking about using a front camera as a ear/face detector. You start it along with the dialer and monitor the output. As long as the picture is bright above set threshold app does nothing, once the picture tuns black (when you put the phone to your head) the app turns off the screen, turns off outer speaker etc.
There is of course problem of calls at night but still I think it would be nice and maybe even useful app.
So, anyone want to try ?
I'd have thought the biggest problem here would be telling the difference between my ear and the inside of my pocket.
a motion sensor would be helpfull here :/
there was a great discussion about wearable computing on the chaos communication congress a few weeks ago.
they mentioned problems like "where is the device" ie. tracking the position on your body. on possible solution is sending and recognizing a sound played by the external speaker and recorded via the mic thus you can determine if its in the pocket or not
dancj said:
I'd have thought the biggest problem here would be telling the difference between my ear and the inside of my pocket.
Click to expand...
Click to collapse
Would this really be a problem? I'd think that turning the screen off while the device is in your pocket would be just as useful as while near your face.
rafgerm said:
HI,
There is of course problem of calls at night
Click to expand...
Click to collapse
This could be at least partially solved by using the system clock to only have the app active during specified hours of the day.
sinning said:
Would this really be a problem? I'd think that turning the screen off while the device is in your pocket would be just as useful as while near your face.
Click to expand...
Click to collapse
Not to mention that the idea mentioned in the original post suggested starting the "ear-detection" with the dialer. Hopefully you don't routinely use the dialer while it's in your pocket.
This is a great idea... but do get me wrong; a face recognition app to unlock the device could be a start
Ignore me I'm an idiot. I thought you wanted the phone to answer when it's up against your ear.
Hi All,
I am finding an issue with my HTC One when the speakerphone is on. The recipient is having trouble hearing me unless I put the back microphone very close to my mouth. From what I can tell when the speakerphone is turned on, the back microphone turns on while the front one turns off. If I do not put the back microphone close to my mouth, I can barely be heard on the other side. For example, I put the HTC One face down on my desk and the distance between the back microphone and my mouth is probably 1.5-2 feet away. At this distance, I cannot be heard unless I should a bit loud. The back microphone literally has to be 1-2 inches away in order me to be heard clearly. If I have the screen facing me, meaning the back microphone is facing away from me, then it's nearly impossible for the other party to hear me. This is the only problem I have encountered with my HTC One thus far. Everything else works like a charm.
Does anyone else have this kind of issue when using the speakerphone? Is there some settings I can try?
Thank you.
I don't know if anyone else has ever asked this question here but I couldn't find a thread for this so I created a new one
So I have a windows phone for a while, to be more specific Windows Phone 8x by HTC. I have notice that in loud areas the phone automatically lunches speech and start listening.
Here is an example. I'm listening to music and I'm holding the phone to show my friend a picture. He sees the picture and we start commenting it. I'm still holding the phone and we are still looking at the picture and the speech start without pressing anything on the phone.
My question is why is this happening and are there any commands that trigger the speech app to start? I know that the speech is lunched with the windows button below the screen but sometimes it lunches without pressing it.
mentalbreaker said:
I don't know if anyone else has ever asked this question here but I couldn't find a thread for this so I created a new one
So I have a windows phone for a while, to be more specific Windows Phone 8x by HTC. I have notice that in loud areas the phone automatically lunches speech and start listening.
Here is an example. I'm listening to music and I'm holding the phone to show my friend a picture. He sees the picture and we start commenting it. I'm still holding the phone and we are still looking at the picture and the speech start without pressing anything on the phone.
My question is why is this happening and are there any commands that trigger the speech app to start? I know that the speech is lunched with the windows button below the screen but sometimes it lunches without pressing it.
Click to expand...
Click to collapse
Can you check if maybe your headphones have some loose connection on the pin or maybe the cord is damaged?
Just an opinion.
That seems likely. Press-and-hold on the headset button (as found on most phone headsets) will trigger speech-recognition mode; it's possible you're either pressing it by accident or that the headsets have some damage which causes the signal for that button being pressed to be sent to the phone.
cevi said:
Can you check if maybe your headphones have some loose connection on the pin or maybe the cord is damaged?
Just an opinion.
Click to expand...
Click to collapse
Everything seems fine there, i can't see any damaged part so it's probably not that
mentalbreaker said:
Everything seems fine there, i can't see any damaged part so it's probably not that
Click to expand...
Click to collapse
As far as i know there are rare cases when it`s the software that`s causing this.I sometimes have this problem but only when i`m pulling the phone out of my pocket which causes the cord to twist somehow and by that starting the speech recognition option.
Try first by gently twisting the pin on the headphones and then slowly folding the cord all the way to the ends.Or at the end try it with other headphones just to be sure?
GoodDayToDie said:
That seems likely. Press-and-hold on the headset button (as found on most phone headsets) will trigger speech-recognition mode; it's possible you're either pressing it by accident or that the headsets have some damage which causes the signal for that button being pressed to be sent to the phone.
Click to expand...
Click to collapse
I have Philips headphones and they are not made for a phone. I have no microphone nor a headset button. so the problem isn't here either.
cevi said:
As far as i know there are rare cases when it`s the software that`s causing this.I sometimes have this problem but only when i`m pulling the phone out of my pocket which causes the cord to twist somehow and by that starting the speech recognition option.
Try first by gently twisting the pin on the headphones and then slowly folding the cord all the way to the ends.Or at the end try it with other headphones just to be sure?
Click to expand...
Click to collapse
I tried the thing you suggested. And you turned right. It was because of the cord, but I'm curious why is this happening
mentalbreaker said:
I tried the thing you suggested. And you turned right. It was because of the cord, but I'm curious why is this happening
Click to expand...
Click to collapse
Just use original HTC headphones and you`ll be fine.
I'm having issues with my z3 compact.like when i'm in a call,the screen gets activated randomly when i move the phone .if i hold it straight onto my ears it works all good.But if i move the phone even if very little around or take away the phone from my face and put it back,the screen gets activated and randomly touched.Anyone having the issue while in call?
my past phones are, Sony live with walkman,HTC desire X,Moto G,LG G3,Moto X.So i know how it should be.Never had that kind of behavious before with sensors.
Not that sort of problem... my problem is the proximity sensor often does not reactivate the screen when I take the phone away from my face to end a call.
Do you have a screen protector on the front?
no I don't use any protector.and I have the problem you mentioned as well.
if I put the phone on my face at certain angle,proximity sensor won't turn off the display.with other phones I never had this sort of weird problems.
According to Antutu, there is no proximity sensor in my phone. Very surprised to find that out. Using D5833.
its very annoying, sometimes its working and sometimes you have no access to the display. When you call somebody and are in the mailbox, there is no way of hanging up, you have to wait till the other site quits the call. How can sony produce something like that?! Is there no quality control?
I would really appreciate If somebody has/finds a workaround for this issue.
Thanks in advance!
Thorsten
I have the same issue and I've figured out that it's more likely to happen when I hold it to my left ear than my right. It's probably due to the position of the proximity sensor. I always use my phone on my left ear but fortunately I don't see this as a very big issue.
Thorstenk said:
its very annoying, sometimes its working and sometimes you have no access to the display. When you call somebody and are in the mailbox, there is no way of hanging up, you have to wait till the other site quits the call. How can sony produce something like that?! Is there no quality control?
I would really appreciate If somebody has/finds a workaround for this issue.
Thanks in advance!
Thorsten
Click to expand...
Click to collapse
I have the same problem, the issue started when I updated to SW version 5.1.1 did you ever found a solution?
Thanks
I just ended up replacing my nexus 6 battery since it was on its way out (not holding a charge for very long). I followed this guide: https://www.ifixit.com/Guide/Nexus+6+Battery+Replacement/35878
After tearing down the phone the only real issue I ran into was on step 5 where you're supposed to "unplug the battery connector", mine ripped and didn't come off. But seeing as that was solely for the wireless charging feature I shrugged it off and continued on.
I installed the new battery and it's working just fine but I noticed now my vibration doesn't work, well it does but maybe at 2% capacity. I can BARELY hear a slight buzz when pressing the home button. And I mean a SLIGHT buzz, I can't even feel it vibrate and I have to stick my ear to the speaker to even hear it.
Is there a ribbon I might have disconnected when putting the phone back together? Does anyone know where the vibration motor is or have any ideas?
The vibration motor is mounted directly on the motherboard. The only thing I can think of is maybe the side button assembly has some influence (step 7 here). I doubt it, particularly if the power and volume buttons work as expected after reassembly.
So I tore apart the phone again last night and took a look at the motherboard, I didn't really see anything that stood out to me in regards to the vibration motor and any connections for it. I saw the vibration motor but it looked fine. So I closed up the phone and hooted up and my vibration worked! But I was stupid and forgot to add this rubber piece over a connector. I once again took apart the phone, put on the connector, tightened it back up and my vibration doesn't work again...
I'm wondering if something is getting pinched..
Maybe the battery is not shaped to match the curve of the phone. Often people have to mold it a bit so it's not pushing things apart.
Vibrator of phone not working
NITRO_2 said:
I just ended up replacing my nexus 6 battery since it was on its way out (not holding a charge for very long). I followed this guide: https://www.ifixit.com/Guide/Nexus+6+Battery+Replacement/35878
After tearing down the phone the only real issue I ran into was on step 5 where you're supposed to "unplug the battery connector", mine ripped and didn't come off. But seeing as that was solely for the wireless charging feature I shrugged it off and continued on.
I installed the new battery and it's working just fine but I noticed now my vibration doesn't work, well it does but maybe at 2% capacity. I can BARELY hear a slight buzz when pressing the home button. And I mean a SLIGHT buzz, I can't even feel it vibrate and I have to stick my ear to the speaker to even hear it.
Is there a ribbon I might have disconnected when putting the phone back together? Does anyone know where the vibration motor is or have any ideas?
Click to expand...
Click to collapse
see the same website for tearing of nexus 5, in comment section there is possible fix which worked for so many people. try that and good luck