So now lets talk real world experience of the phone interface
When it blanks the phone buttons seem to operate...
I mean a number of occasions I have lost people because I have mysteriously put them on hold...with the phone to my ear.
People are always complaining to me that I am quiet even though the phone is in the correct place on my face and incall volume is at max
Often I cannot pick up calls ...I hit the answer icon to no avail...if I flick it upscreen it works but pressing the icon is only recognised intermittently
What is it like for you?
PianoSam said:
So now lets talk real world experience of the phone interface
When it blanks the phone buttons seem to operate...
I mean a number of occasions I have lost people because I have mysteriously put them on hold...with the phone to my ear.
People are always complaining to me that I am quiet even though the phone is in the correct place on my face and incall volume is at max
Often I cannot pick up calls ...I hit the answer icon to no avail...if I flick it upscreen it works but pressing the icon is only recognised intermittently
What is it like for you?
Click to expand...
Click to collapse
have to tried to factory data reset the phone to see if that helps?
This is called the incall/proximity sensor issue and the reasons have not yet been found by xda people.
There are few fixing attempts available though which involve different strategies.
Someone lately suggested to the ViperOne team to make a tweak that allows for automatically locking the phone on call pick up as a permanent workaround fix. There was no developer response on this yet though. Its a good idea though.
The same sensor is causing another issue which is quite frustrating. On some occasions the normal method of simulated battery pull (press power for more than 15 seconds to force reboot) does not do anything unless shining a really bright light into the sensor. Apparently the prox sensor, not the light sensor.
It seems there are a few units out there which have issues with this sensor.
Another theory is that its jut the user tilting the phone until it recognizes landscape orientation and then the sensor is switched off...
Related
I'm running CM 7.0.3, and I'm having massive proximity sensor issues, t the point where the phone is becoming unusable. If I'm in a call and I don't manually shut the screen off, the following happens (constantly):
I'll feel some haptic feedback on my ear, and my voice will mute. When I look at the screen, the lock screen is up and when I unlock it, it's at the dialer screen. I'm not hitting the mute or hold button with my ear, it seems like once it gets away from the call screen, my voice is muted.
Needless to say, this is getting massively annoying. Later tonight I'm going to try to see if using a Sense based rom fixes this, but I'd much rather stick with CM. Has anyone else experienced this?
I believe there is another post on this.. you can also Google search for inspire proximity sensor adjustment - someone created an app to adjust the sensor
Sent from my Desire HD using XDA Premium App
The thread in question:
http://forum.xda-developers.com/showthread.php?t=1062561
EDIT: I haven't used the proximity sensor adjustment application that's linked in the thread as mine is working normally. If it doesn't work there's a possibility the sensor's faulty and should be replaced (I recently went through this whole thing with my old iphone 4).
Yeah, to be honest, I tried that app and it didn't seem to make much difference. I'll try calling HTC
Flashed to a sense based ROM, and the sensor seems to be working fine. Very odd, to be honest. I will say that after using AOSP for so long, I have no idea how you guys deal with Sense at all.
Well, now I have to decide: I can live with Sense, or I can ship my phone back to HTC and be without a device for 2 weeks. Going to try out the proximity sensor app again, but it didn't seem like any setting made a difference, but it could be that I just don't know what I'm doing with it.
Check under Settings>Call Settings and put a check mark in the "Always use proximity" box. It says it's to help with prox. sensor screen locking when the phone is horizontal, but the CM7-based ROM that I was using showed the same issues and I fixed my particular issue by checking that box.
Tested with a few calls and the screen is definitely shutting off when the phone is standing or lying down.
I read up on the proximity app, and I think I have it calibrated properly at 5/6. It certainly helps, but it's definitely not perfect. Night, thanks for the advice, but yeah, that option has been checked from the start. At least the issue is tolerable now, before it would do this 10 times per call.
Funny - mine was calibrated at 10/11 by default and works pretty well. Try going up to those values. I used a local time/temperature number here, and it worked well when my finger got 1/8" or so from the phone. While I admittedly haven't measured the depth of my ear or anything, it does seem to be working well at those settings.
I think the upper threshold is where you may want to adjust. From my playing with that app, changing the lower threshold too high will make it ignore things too close to the phone and so will an upper threshold that is too low. Try lower 5, upper 11 and see what happens. Anything between lower and upper apparently triggers the sensor. (<<< speculation without documentation)
Hi,
I just saw today, that there was a very weak red light just next to the proximity and light sensor. It looked like it was flickering at a very high rate!
I tried to restart the phone normally, but the light didn't disappear. After that I tried a reset by holding the power button down for 10 seconds. That made it vanish.
What the f**k was that all about???
Best regards
Casper
If you were making a phone call, the red flashing light is normal It's the proximity sensor. If you were doing nothing, it should not be seen the red light, might be faulty.
Sent from my HTC One S using XDA
Moved To Q&A
This is best in the Q&A section, as it been written as a question.
h.han said:
If you were making a phone call, the red flashing light is normal It's the proximity sensor. If you were doing nothing, it should not be seen the red light, might be faulty.
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Its The Goverment Spyin On us...Making Sure We Dont Flash Anything Or Even Root...If So It Will Say Tampered And The S.W.A.T. Team Will Come Crashin in Our Homes...
That red light is in fact the actual proximity sensor and it's in use while in a call. If you where not in a call then that was a strange occurance unless you ran some of these sensor testing apps...
Well, I wasn't in a call. I had been calling someone through the hands-free in my car on my way to work, where I discovered it about 10-15 minutes after the call was finished...
cawith said:
Well, I wasn't in a call. I had been calling someone through the hands-free in my car on my way to work, where I discovered it about 10-15 minutes after the call was finished...
Click to expand...
Click to collapse
That was an odd one... maybe it was a temporary fluke? Strnag nonetheless...
I often use face unlock. The red light turns on when the front cam turns on.
Sent from my HTC VLE_U using XDA
any tips on how to trouble shoot this? I wish I could figure out which app (if any) is causing the proximity sensor to stay lit.
I've heard it's related to an autobrightness tweak, but it appears even when tweak is not applied, across multiple roms. The only commonality between my roms is the apps I have installed.
I've tried multiple proximity sensor testing apps and, it's working.. it's just always lit up.
decalex said:
any tips on how to trouble shoot this? I wish I could figure out which app (if any) is causing the proximity sensor to stay lit.
I've heard it's related to an autobrightness tweak, but it appears even when tweak is not applied, across multiple roms. The only commonality between my roms is the apps I have installed.
I've tried multiple proximity sensor testing apps and, it's working.. it's just always lit up.
Click to expand...
Click to collapse
Same here. Have to restart to get it off again. Any help? (TrickDroid 4.3)
Anytime you make a call by any means other than handset to your ear, the proximity sensor will come on and stay lit until reboot or until you make another call via handset.
Example:
Place call> turn on speaker phone> hang up - proximity sensor will stay lit after call;
To fix do this:
Place call from handset (not using speaker phone or hands free) and hang up right away, or reboot device and light will go out.
Same seems to go for calls through hands free as well.
These guys are lying its a bomb isn't it obvious flashing red light HTC controls it if u do something they don't want u to do boom ur hands are no more why do u think the phone heats up so much its a warning don't believe me read the thread in forums about heats in the one s another reason they don't want us to remove back well see the bomb :what:
Sent from my HTC One S using xda premium
Hi All,
My One S also does this. I'm finding it a pain to have to make a call after using speakerphone to turn the proximity sensor off again. Has anyone found out what the cause of this is?
I've tried clearing cache partition with HTC support but still no fix.
Hi all, I forgot to mention that the issue on my phone only happens when the call is ended with speakerphone active. If I turn off the speakerphone before ending the call it does not happen.
Hey brothers.. I had the same problem with the proximity sensor not turning off.. Even after so many restarts resets... Finally I just opened the original task manager of the one x, and push "stop all" .. and YES!! the sensor was turned of and stopped lighting.. After that I tried calls with speaker phone or not.. No problem.. Now it is working how it has to...
Sv3TL10 said:
Hey brothers.. I had the same problem with the proximity sensor not turning off.. Even after so many restarts resets... Finally I just opened the original task manager of the one x, and push "stop all" .. and YES!! the sensor was turned of and stopped lighting.. After that I tried calls with speaker phone or not.. No problem.. Now it is working how it has to...
Click to expand...
Click to collapse
You maybe have turned off Viber doing this: http://www.boards.ie/vbulletin/showthread.php?p=80972874
Does it come back after restarting Viber?
Sometimes a restart fixes the problem.
I had the same problem. I uninstaled Viber and the light disipired.
foner81 said:
You maybe have turned off Viber doing this:
Does it come back after restarting Viber?
Click to expand...
Click to collapse
Later I realized that Viber is the reason. Yes. But now it seems that Viber is fixed after last update, and no red light when viber is turned on
Hey all,
I'm very seasoned with Android, and I LOVE the OnePlus One so far, but there is one issue that is driving me MAD.
Whenever I am on a call, and I lift the phone away from my ear, the notification shade triggers and gets stuck at the top of the screen... No matter where I touch, it snaps to that location. For example; if I am in a call, and I want to add another user to the call, I press the +Call button at the bottom of the screen, but it never triggers, it snaps the notification shade down, and I have to drag it back up before I can use the phone functions. This doesn't happen all the time, but it happened a lot to me today.
My girlfriend was kind enough to help me with a screenshot (she just quietly stayed on the line )
Anyone else experience this? Is there a fix at all? I'm still 100% lock and stock if that matters. I also posted this on the OnePlus One support forums, so if I hear back there first, I will post the solution.
I had the same problem too. Seems like this happens because your ear touches the display, the top part which when touch gives you a peek at the notification showing the date and time, before the proximity sensor can detect.
The solution I found is to get the phone close to your face at an / angle, the top first and then the bottom.
I had the same issue with my HD2 running cyanogen, which has the same feature to peek notification.
Thanks @Sir Awesome!
I'll give this a try later... Sounds a lot like "You're holding it wrong" to me... It's okay that it gives the peek, but it just stays there.
Wondering if anyone has any advice for my weird mic issue - it's a little different to the others I've seen but willing to try anything at the moment. Here's what I've found so far:
*People can't hear me when I talk into the phone. I've tried calling my home phone and listening and I don't hear anything either.
*This problem seems to happen when I'm holding the phone normally (i.e. against my face - ear to the ear speaker and mouth near bottom of the phone's mic)
*If I talk right into the bottom of the speaker (as in have the bottom mic and speaker right in front of my mouth), it picks up audio fine on the other end.
*Speakerphone appears to be fine so secondary mic is working fine.
*Done the usual clean the mic hole with pin (and compressed air), made sure my finger wasn't covering the mic hole, removed any cases, etc.
My suspicion is maybe the proximity sensor is doing something to cause the audio to cut out? I can't imagine the bottom mic being that directional that it picks up nothing in one particular direction while works fine in another.
Phone is bone stock S6 - SM G920W8 running 6.0.1 (Build G920W8VLU3CPC8)
I've already done a factory reset so this thing is as clean as it gets and still no luck. Help!
Apps could be the issue.
Do you have any apps or had any apps in the past that use the proximity sensor on your Galaxy S6? I know that I have had these problems in the past where certain apps that use the proximity sensor, such as the wave your device on and off app that I frequently use interfere with how the microphone detects how far away your face is.
WSADKeysGaming said:
Do you have any apps or had any apps in the past that use the proximity sensor on your Galaxy S6? I know that I have had these problems in the past where certain apps that use the proximity sensor, such as the wave your device on and off app that I frequently use interfere with how the microphone detects how far away your face is.
Click to expand...
Click to collapse
Not that I recall. I did boot the device up in Safe Mode (which should stop any third party app from loading) and the problem still occurred. I also tried it again after I did a factory reset and before I loaded any apps but that didn't help either.
I don't use the gestures at all so I don't think it's that but maybe the factory reset turns it on. I'll see if I can find it to check.
syee said:
Not that I recall. I did boot the device up in Safe Mode (which should stop any third party app from loading) and the problem still occurred. I also tried it again after I did a factory reset and before I loaded any apps but that didn't help either.
I don't use the gestures at all so I don't think it's that but maybe the factory reset turns it on. I'll see if I can find it to check.
Click to expand...
Click to collapse
Well, it looks like gestures were turned on by default. Turned them all off and then turned them on one by one and made a test call and found it's the "Smart Alert" feature that caused the mic to not work when near my face.
Thanks WSADKeysGaming for the reminder about the gestures! I completely forgot about it because I never used them.
Don't mention it!
There are so many settings nowadays that its hard to remember whats on and off, left and right. Glad I could help!
syee said:
Well, it looks like gestures were turned on by default. Turned them all off and then turned them on one by one and made a test call and found it's the "Smart Alert" feature that caused the mic to not work when near my face.
Thanks WSADKeysGaming for the reminder about the gestures! I completely forgot about it because I never used them.
Click to expand...
Click to collapse
Sorry for bumping an old thread, are you familiar with why the Smart Alert feature would do this? Thanks!
I have reading the forum and tried contacting 1+7 also but they just say switch off nfc and so on but till today (1 month since I bought it ) I still have the problem . while making a call it goes on hold or connects another call or something or the other happens and the other person gets irritated as if I am doing on purpose. I am still unable to solve this will changing rom be the solution or can someone please help I am fed up with this instrument
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
will try out can you advice reset sensors apps
jonsat said:
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
Click to expand...
Click to collapse
will try out can you advice reset sensors apps
Issue is back again after 9.5.9 update.
IEESH said:
will try out can you advice reset sensors apps
Click to expand...
Click to collapse
Search for "Proximity sensor reset" or similar names. Usually apps like that needs root privileges, btw.
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Superguy said:
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Click to expand...
Click to collapse
Disabling double tap to wake resolved my screen wakeup during calls issue...
UPG to 9.5.10 Plz - Issue has disappeared again.
ram4ufriends said:
Disabling double tap to wake resolved my screen wakeup during calls issue...
Click to expand...
Click to collapse
I'll try that, but I don't think I have that enabled. I disabled NFC for the other tap issues and that helped some.
I really wish there was a screen calibration tool. Samsung curved screens have none of these issues.
Do you have a dirty screen protector?
This is a known bug with the proximity sensor, although, actually, I believe the root cause is something else.
Screen does go black, which indicates the proximity sensor is working and recognizes your face is near... But input is still allowed (meaning it does not lock it).
As a result, during a call your face/ear will press whatever is underneath and trigger random actions.
I believe (I hope?) that OnePlus is aware of this issue and they issue a fix.
I think it was briefly fixed for 9.5.9 and then reverted on 9.5.10 since it introduced other issues.
Quality control has been a bit subpar on the OnePlus 7 Pro builds when compared to my previous OnePlus phones...