hi, i'm having a issue with the proximity sensor. Sometimes when i answer calls, the screen stays black even if i press the lock button, sometimes i can't even answer because i can't turn on the screen. Once it had the problem, if i open an app to test the proxymity sensor it tells me that the screen in always covered. If i reboot the phone everything goes back to normal, until the next time it decides to malfunction. I don't use any screen protector and i had this problem with resurrection remix rom and CM 13 snapshot... Anybody had the same issue? Or knows how to fix it? the thing that is driving me insane is that it does this only sometimes, at random...
There's a fix to this. Go to accessibility settings and tick power button to end call. Then reboot. And then untick it. Itll be solved after it. Had the same in my nexus 6 too.
akholicc said:
There's a fix to this. Go to accessibility settings and tick power button to end call. Then reboot. And then untick it. Itll be solved after it. Had the same in my nexus 6 too.
Click to expand...
Click to collapse
I tried and it seemed to work at first, but today the issue was back...
mirko902 said:
I tried and it seemed to work at first, but today the issue was back...
Click to expand...
Click to collapse
I had same problem on my phone. I discovered Proximity Sensor Reset through another XDA post which fixed the problem for me. Google Play Store, it is simple and has remained effective through reboots and ROM updates. Maybe it will resolve for you and others too.
Sent from my Nexus 6 using XDA-Developers mobile app
Related
any one else have this issue with Xperia Z ?
i can make calls or recieve calls and then the screen goes black when put to my ear as it should, but most of the time [not all the time] when i finish the call and take it away from my ear it wont light up so i can't end the call. i have to wait for the other person to hang up, and even then sometimes it wont light up.
they hang up the phone call doesn't end so it just stays black and i can't do anything.
i can restart it by pressing the off button and volume up at the same time, but i don't want to have to restart my phone every time i make a phone call.
has any one had this issue?
Could be software issue, ie a third party app, for example justshake and similar apps have options to alter proximity sensor activity but I stay away from altering them. The only time I have a similar issue is with modded Skype but a brief press or two of power button restores the screen so not a big issue.
You should try in service menu if your sensor is functioning properly.
A small workaround to end call without having to use the screen is to enable ens call with power button press which is in accessibility settings of the phone, so don't need to wait for another party to hang up or to reboot your phone
Sent from my C6603 using Tapatalk 2
thanks for your kind help i am on stock .253 firmware i don't have much software installed only skype, viber whatsapp from the goolge play and i tried in the service menu the sensor is working flawlessly and tried factory reset twice same problem exist
searching on the google for solution i see im not the only one whose having this particular proximity sensor problem there are other people reporting the same problem
Maybe the screen protector?
Sent from my C6603 using xda premium
Proximity sensor
Mine started doing the same thing. After reinstalling and checking if it might be a software issue, I did some research and came across this: talk.sonymobile.com/thread/126533?start=0&tstart=0
I've taken my phone in, and awaiting a response. (The phone is just over a week old, so it just fell out of the "automatic RMA" period).
I put a skin on front... Now having issues... Is there a way to just disable it...
Sent from my C6603 using Tapatalk 4
I had the same problem and did like the post #31 on the linked thread says :
Press firmly on the proximity senson with your thumb (located beside the notification led).
I have a screen protector and did not remov it and it now works like a charm.
Hope it helps.
xperia z. I have the same problem after installing the spg glass protector ver1. Since the ver2 has a cutout at the proximity sensor, I do not like it and therefore keep on using the ver1 without the cutout. I prefer to disable the proximity sensor instead of having a pit on the screen surface. Just add the line:
gsm.proximity.enable=false
to the end of the file build.prop located in /system, reboot, and the sensor will be disabled.
The way to activate the screen during a phone call is to press the power button twice.
Hope this help.
Explanation/please
wmiswm said:
xperia z. I have the same problem after installing the spg glass protector ver1. Since the ver2 has a cutout at the proximity sensor, I do not like it and therefore keep on using the ver1 without the cutout. I prefer to disable the proximity sensor instead of having a pit on the screen surface. Just add the line:
gsm.proximity.enable=false
to the end of the file build.prop located in /system, reboot, and the sensor will be disabled.
The way to activate the screen during a phone call is to press the power button twice.
Hope this help.
Click to expand...
Click to collapse
Can i ask how do i reach this settings. I tryed different data searches via phone and with PC (ofc with mobile connected). But i dont seem to find this system folder no matter where i look. Maybe you can make a tutorial for me or just say where to look. Thanks
You need to be rooted. The build.prop file is in /system.
An easier way to add the property to your build.prop would be to use build.prop editor - https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
I will just say - BE CAREFUL when editing that file. If you edit the wrong thing, you can stop your phone booting.
Sent from my C6603 using Tapatalk
I've tired all these solutions above but unfortunately I'm still facing same problem and it's really frustrating
My phone isn't rooted so I can't disable proximity sensor
If there is any other solutions ?
Install proximity smart cover from market. The screen will then come on when you take the phone away from your ear.
In settings:
Enable device admin
Turn screen off - never
Turn screen on - 0 seconds
Then go back and start the service
Sent from my C6603 using xda app-developers app
Thanks, it did work
wfsolutions said:
I had the same problem and did like the post #31 on the linked thread says :
Press firmly on the proximity senson with your thumb (located beside the notification led).
I have a screen protector and did not remov it and it now works like a charm.
Hope it helps.
Click to expand...
Click to collapse
I was going crazy with this sensor problem, and tried all sort of thing including resetting my phone multiple times. The suggestion you mentioned here worked like a charm.
There seem to be several proximity sensor threads but I've done a search and have not found anyone that is having this same problem.
When I make a phone call, my screen turns off right away. I can only get it to come on by pressing the power button or tilting the phone so that a bright light or glare is on the proximity sensor or light sensor. This is a pain. I use my power button to end calls but I have to disable that option. Otherwise, any time I need to use touch tones for an in-call menu, I hang up or spend a minute tilting my phone or holding it up to a light bulb. I know there are workarounds that I could be using but I am wondering if my proximity sensor or light sensor is malfunctioning or if it is a software issue.
Also, when using the visual voice mail app, my screen goes black but not off. I can still see the status bar. It happens as soon as I tap the play button and works just fine after my voice mail stops. This is likely unrelated but I can't be sure.
Thanks in advance to anyone that helps!
Running stock and unrooted with no physical damage or obstruction of sensors. I have tried a factory reset... twice.
I'm having a weird issue with mine as well. Mine is a little different though. If I need to make a call that requires to enter # prompts and as soon as I move the phone away from my face the keypad will start beeping on the other end so the prompts will always get invalid responses. While on the phone and I move the phone away from my face for any reason, the person on the other end will hear the beeping.
mokash34 said:
There seem to be several proximity sensor threads but I've done a search and have not found anyone that is having this same problem.
When I make a phone call, my screen turns off right away. I can only get it to come on by pressing the power button or tilting the phone so that a bright light or glare is on the proximity sensor or light sensor. This is a pain. I use my power button to end calls but I have to disable that option. Otherwise, any time I need to use touch tones for an in-call menu, I hang up or spend a minute tilting my phone or holding it up to a light bulb. I know there are workarounds that I could be using but I am wondering if my proximity sensor or light sensor is malfunctioning or if it is a software issue.
Also, when using the visual voice mail app, my screen goes black but not off. I can still see the status bar. It happens as soon as I tap the play button and works just fine after my voice mail stops. This is likely unrelated but I can't be sure.
Thanks in advance to anyone that helps!
Running stock and unrooted with no physical damage or obstruction of sensors. I have tried a factory reset... twice.
Click to expand...
Click to collapse
It sounds like your issue is hardware related. Take it to a sprint repair store and have it exchanged.
mrwicked said:
I'm having a weird issue with mine as well. Mine is a little different though. If I need to make a call that requires to enter # prompts and as soon as I move the phone away from my face the keypad will start beeping on the other end so the prompts will always get invalid responses. While on the phone and I move the phone away from my face for any reason, the person on the other end will hear the beeping.
Click to expand...
Click to collapse
You issue also sounds hardware related. The touchscreen sounds like it is going out. It might be the dialer app but I doubt it. Speaking from experience of course.
I went to Sprint store yesterday and they gave me a replacement for mine.
insuusvenerati said:
It sounds like your issue is hardware related. Take it to a sprint repair store and have it exchanged.
You issue also sounds hardware related. The touchscreen sounds like it is going out. It might be the dialer app but I doubt it. Speaking from experience of course.
Click to expand...
Click to collapse
Thanks I will head to a store and follow up here for anyone else. Thanks again.
I would check the sensor settings and play around before trying the store. But if that doesnt work it prob is hardware issues
I'm running 4.4.4. Rooted and unlocked.
This problem occurred before I upgraded.
When I call someone, the dialer screen immediately disappears and when I'm done with the call I usually have to press the power button 3 or 4 times to get my lock screen back. I have blue tooth for my hearing aids. When I use that, it doesn't disappear although after the call I need to hit the power button twice for the lock screen. I might have changed some settings inadvertently due to the screen changing when it sould have turned off. I think the blue tooth on my hearing aids is what activates the screens. I'm using Apex launcher. I have had my phone completely apart because of a plugged mic opening. I don't think this anything to do with the problem at hand, At one time on my phone I saw a setting someplace where I could end a call with the power button. Anyone know where that's at? Any help would be greatly appreciated. I might flash it back completely stock.
Moto X DE
Do you have two dialer apps? I had a similar problem and the problem ended up being having the stock dialer as well as the google dialer installed.
I got rid of the stock dialer and then the problem went away.
Settings > Accessibility > Power button ends call (check that).
Do you have a screen protector? If misplaced, it may activate the sensor that turns off the screen when the phone is up to your face.
metaljr81 said:
Do you have two dialer apps? I had a similar problem and the problem ended up being having the stock dialer as well as the google dialer installed.
I got rid of the stock dialer and then the problem went away.
Click to expand...
Click to collapse
Only one
Groid said:
Settings > Accessibility > Power button ends call (check that).
Do you have a screen protector? If misplaced, it may activate the sensor that turns off the screen when the phone is up to your face.
Click to expand...
Click to collapse
No.. took it off
I am having this same problem . only one dialer app unlocked and rooted.
Sent from my XT1060 using Tapatalk
To anyone having this issue: I have seen this issue several times now with multiple members. I haven't seen a working solution yet except that a factory reset sometimes solves it, and flashing back to 100% stock as per the return to stock thread (in the General sub-forum) always solves it. I know it is often a pain to have to set everything up all over again, but it is the only solution I'm aware of.
Good luck
Yep factory reset was the only thing that fixed it for me
Sent from my XT1060 using Tapatalk
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
JimSmith94 said:
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
if youre using lightflow id suggest wiping the data in it and resetting your notification settings. it does tend to override the system so i can see that screwing with the duration of the notification, and starting fresh usually solves most problems
i have mine set to wake the screen for SMS but not MMS. it creates similar problems with the screen
Thanks for the info. I tried just toggling the screen on settings on and back off for all of the Light Flow apps, and it seems to have fixed my screen turn on problem, at least for now.
Sent from my Nexus 6 using Tapatalk
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
A.Ahmed79 said:
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
Click to expand...
Click to collapse
LightFlow fixed my screen problems, but it was just a coincidence that I installed Marshmallow and my sounds got cut off around the same time. I'm still looking for a solution to that issue. Similar to you, if my screen is on, the notification sounds work correctly. If the screen is off, they get cut off.
I purchased new A71, it's screen gets on by itself after every one or 2 minute. I checked simply whatever possible. Any ideas?
Never had this issue but did you try tweaking AOD settings?
DonAndress said:
Never had this issue but did you try tweaking AOD settings?
Click to expand...
Click to collapse
Already,,, no use.
Now safe mode tried and no screen wakeup.
It means some third party app issue.
I'm trying to figure out which app exactly.
I had this with my wife's phone.... Screen literally cam on everytime the phone was moved.... She has a flip case, which i assumed was the culprit, and i could see the screen pop on even if she moved the phone to one side a little...
I found the answer to our solution in the settings somewhere under advanced features/motion and gestures.... Untick all that lift to wake crap!
Screen stays off now until you press power button or double tap screen...
wastedagen said:
I had this with my wife's phone.... Screen literally cam on everytime the phone was moved.... She has a flip case, which i assumed was the culprit, and i could see the screen pop on even if she moved the phone to one side a little...
I found the answer to our solution in the settings somewhere under advanced features/motion and gestures.... Untick all that lift to wake crap!
Screen stays off now until you press power button or double tap screen...
Click to expand...
Click to collapse
I tried the same already but problem was still there.
Since once I reboot into safe mode, there w no issue. then started apps one by one in normal mode,,,, now not facing issue. I suspect one or two third party apps. Still not finalised which app exactly as these apps got updated meanwhile.
Any way thanks,,,,
my issue already resolved.