When I make a call and don't hold a phone near the ear the screen still turns off.
This started to happen 1 months after I bought the phone. Before it was working fine, which means if I don't hold the phone near the ear the display doesn't fade, and if I do, it does fade.
Im running unrooted stock 4.3 latest android.
Is there anyway to fix this problem?
Sent from my GT-I9505G using xda app-developers app
jodvova said:
When I make a call and don't hold a phone near the ear the screen still turns off.
This started to happen 1 months after I bought the phone. Before it was working fine, which means if I don't hold the phone near the ear the display doesn't fade, and if I do, it does fade.
Im running unrooted stock 4.3 latest android.
Is there anyway to fix this problem?
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Restart phone and if problem remains Hard-reset phone
and IF it remains try to flash another Stock-ROM
also check if u installed any app to customize sensors !?!??
:good:
x102x96x said:
Restart phone and if problem remains Hard-reset phone
and IF it remains try to flash another Stock-ROM
also check if u installed any app to customize sensors !?!??
:good:
Click to expand...
Click to collapse
I did wipe out cache, that didn't help. I don't want to do a hard reset, as its annoying to restore the environment and settings back.
I don't use any software that tampers the sensors. Also I'm on a stock I9505G android 4.3.
Any other ideas, please ?
Sent from my GT-I9505G using xda app-developers app
must be a problem with ur proximity sensor...
U didnt cover proximity sensor with screen protector?
razno said:
U didnt cover proximity sensor with screen protector?
Click to expand...
Click to collapse
Nope, I don't have screen protector.
Also, when I make calls I just hold phone in front of me and so nothing covers the proximity sensor.
Related
Just wanna ask if there is any temporary fix to the proximity sensor of nexus 4.
During calls the screen doesn't turn off when placed close to the face.
I didn't get the chance to test it on stock 4.2 because when i turned my phone on it updated first to 4.2.1. Ever since then it has had proximity sensor not working during calls.
And i have never had any screen protectors on the screen.
Tried many custom ROMS as well but no difference at all.
Sent from my Nexus 4 using xda premium
how about kernals could be a bug in franco.
return it to 100% stock make sure its still doing it under those conditions then if it is contact Google and ask for an RMA this is probably your best course of action. if it has been like this since you pulled it out of the box then contact google right now and tell them the proxmity sensor is clearly broken
I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
BTW as for screen protectors, unless you have a giant bubble or crap on your protector or underneath in the adhesive layer, the proximity sensor should perform fine. Before you blame my screen protector, I downloaded a proximity sensor app to show the readout. The screen protector with no cutout is fine. It's not optimal to have one like that, but the proximity sensor works fine.
isnt there a proximity senor app which lets you test it on the market?
dmo580 said:
I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
Click to expand...
Click to collapse
Using stock. No issues on the sensor. Turns off on calls and turns on when I remove from the face. Have a spigen protector on with a cutout for it
Sent from my Nexus 4 using Tapatalk 2
dmo580 said:
I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
BTW as for screen protectors, unless you have a giant bubble or crap on your protector or underneath in the adhesive layer, the proximity sensor should perform fine. Before you blame my screen protector, I downloaded a proximity sensor app to show the readout. The screen protector with no cutout is fine. It's not optimal to have one like that, but the proximity sensor works fine.
Click to expand...
Click to collapse
I was on stock 2 weeks ago when I started noticing it.
I am on cm now as well and its very much messed up.
Sent from my Nexus 4 using xda premium
bobola said:
isnt there a proximity senor app which lets you test it on the market?
Click to expand...
Click to collapse
There is.
I've installed and tested.
According to the app results, The proximity sensor seems to know when my hand is on it and when its off it. The value changes from 1.0 to 2.0
It just won't work on phone calls.
Sent from my Nexus 4 using xda premium
noobdeagle said:
how about kernals could be a bug in franco.
return it to 100% stock make sure its still doing it under those conditions then if it is contact Google and ask for an RMA this is probably your best course of action. if it has been like this since you pulled it out of the box then contact google right now and tell them the proxmity sensor is clearly broken
Click to expand...
Click to collapse
It doesn't seem to be a hardware issue.
Sensor tests were made and the proximity sensor picks up when my thumb is placed on it.
Problem is on phone calls alone. Right from stock ROM to CM, PA, Xylon, AOKP, almost all of the ROMs.
Sent from my Nexus 4 using xda premium
slimldj said:
It doesn't seem to be a hardware issue.
Sensor tests were made and the proximity sensor picks up when my thumb is placed on it.
Problem is on phone calls alone. Right from stock ROM to CM, PA, Xylon, AOKP, almost all of the ROMs.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mine is stock and during calls it usually goes to my settings menu and changes my clock setting. When I get off the phone, screen is blank and I hit power button to end call. Still annoying at times when the clock changes.
any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.
feedmylittletroll said:
any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.
Click to expand...
Click to collapse
I think it's a bug and not a hardware issue. Perhaps one of the other reason for having a new factory image soon.
Sent from my Nexus 4 using xda premium
feedmylittletroll said:
any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.
Click to expand...
Click to collapse
I'm suffering this same problem too, hope they fix it soon..
slimldj said:
I think it's a bug and not a hardware issue. Perhaps one of the other reason for having a new factory image soon.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yes I think the fact that the app testing showed the sensor working so it points to software. Something is missing when the phone is in a call its not connecting to turn off. I thing Jellybean was flawed in many ways. My drop down brightness slider doesn't work for me nor auto brightness its OK for me cause I don't use either but still makes me mad.
Using Tapatalk 2
meetoo
Same problem here. Nexus 4. Stock Android 4.2.1. No screen protector installed.
While I'm in a call - the proximity sensor seems to work, as the screen goes dark... but at the end of the call when removing the phone away from my face, the screen does not come back on - making it impossible to hang up on the call (unless the caller on the other end hangs up first). It also makes it difficult to impossible to switch to and from speakerphone in the middle of a call.
Pushing the power button when this happens doesn't wake the screen either... sometimes it flashes but then goes black again. It doesn't happen on every call... maybe 75% of the time it does happen though. I've installed the proximity sensor app and it seems to recognize "covered" and "uncovered" states correctly when I cover the sensor at the top left corner of the phone while not in a call... so I'm thinking this is actually a software issue with the sensor and not a hardware issue. Drives me nuts though.
I've set "accessibility settings" to have the power button hang up calls as a temporary workaround... we'll see how that works.
treaty said:
Same problem here. Nexus 4. Stock Android 4.2.1. No screen protector installed.
While I'm in a call - the proximity sensor seems to work, as the screen goes dark... but at the end of the call when removing the phone away from my face, the screen does not come back on - making it impossible to hang up on the call (unless the caller on the other end hangs up first). It also makes it difficult to impossible to switch to and from speakerphone in the middle of a call.
Pushing the power button when this happens doesn't wake the screen either... sometimes it flashes but then goes black again. It doesn't happen on every call... maybe 75% of the time it does happen though. I've installed the proximity sensor app and it seems to recognize "covered" and "uncovered" states correctly when I cover the sensor at the top left corner of the phone while not in a call... so I'm thinking this is actually a software issue with the sensor and not a hardware issue. Drives me nuts though.
I've set "accessibility settings" to have the power button hang up calls as a temporary workaround... we'll see how that works.
Click to expand...
Click to collapse
Having the exact same issue here too on stock ROM.
Good idea on the accessibility settings! Will work until/if they fix it..
Also no screen protector.
I had the opposite problem to this where my screen would stay off during a call and I have to force restart to regain control.
Turns out it was the rubbish screen protector causing the issue. This was quickly fixed by cutting the screen protector so that the sensor was uncovered.
Dav_prime said:
I had the opposite problem to this where my screen would stay off during a call and I have to force restart to regain control.
Turns out it was the rubbish screen protector causing the issue. This was quickly fixed by cutting the screen protector so that the sensor was uncovered.
Click to expand...
Click to collapse
It was the same fix for mine when I first got my bse it worked fine for about a week but then over time it got worse. It was the screen protector just that lil bit worth of it wear caused enough blockage of the sensor. I got some new bse's and they now have a cutout for the proximity sensor and are screen optimized.
Sent from my Nexus 4 using Xparent Blue Tapatalk 2
use Proximity Actions by Novum Inceptum in playstore
rat99 said:
use Proximity Actions by Novum Inceptum in playstore
Click to expand...
Click to collapse
That won't fix anything.
while I am still waiting for my oppo phone, a friend e-mailed me about this little app to solve the smart cover not working on custom roms. I can't test it so some one can try and see if it works.
https://play.google.com/store/apps/...wsMSwxLDEsImNvbS5pdHNtZTR1Y3ouc2NyZWVub2ZmIl0.
It's basically a app using proximity sensor to shut off the screen. There is a timer as well so you can fine tune based on personal usage.
Seems to be working! My smart cover works on cm10.1 turning the screen on but not off.
Nice find!
Sent from my Find 5 using xda premium
i think the screen will turn on fine with custom roms fine just can't turn off, no?
this app suppose to turn the screen off based on the proximity detection so when the cover is on, the screen will turn off based on a timer you set, i guess couple second would be fine.
QUOTE=WhiteSRT69;42886854]Seems to be working! My smart cover works on cm10.1 turning the screen on but not off.
Nice find!
Sent from my Find 5 using xda premium[/QUOTE]
Can this be done with Tasker?
silvscorp said:
i think the screen will turn on fine with custom roms fine just can't turn off, no?
this app suppose to turn the screen off based on the proximity detection so when the cover is on, the screen will turn off based on a timer you set, i guess couple second would be fine.
QUOTE=WhiteSRT69;42886854]Seems to be working! My smart cover works on cm10.1 turning the screen on but not off.
Nice find!
Sent from my Find 5 using xda premium
Click to expand...
Click to collapse
[/QUOTE]
lol i think i might have woreded my first post wrong
on CM10.1 my smart cover with turn the screen on.. but not off
this app does work and does turn my screen off after 1 sec that i have it set to
lol i think i might have woreded my first post wrong
on CM10.1 my smart cover with turn the screen on.. but not off
this app does work and does turn my screen off after 1 sec that i have it set to[/QUOTE]
cool, glad to know it works. Noticed any unusual battery drain with this? I doubt it will since it's pretty much the same as if you are making a phone call, the screen shuts as you put it against your face. But you never know. I am still waiting to receive my replacement phone so can't test it much.
i made a cm build that fixes the smart cover problem
you can download it here http://forum.xda-developers.com/showthread.php?t=2342489
I'm using the default screen lock, with swiping, and it happened 2 times in the last 3 days, that my camera was turned on, in my pocket. (The phone is in a leather pouch)
is there a way, to disable the camera on the lockscreen (swipe left)?
It´s not the lock screen. It´s because of volume buttons. If you hold it pressed for some time volume up starts quick memo and volume down starts the camera. I have the same problem: phone carried in a pouch. I wonder if there is a way to disable it since I don´t really use quick keys.
I've never had this issue in the past week and half that I've had this phone without any case on.
The back volume rocker buttons are definitely getting pressed if your camera is turning on. When you put the phone in your pocket, do you put the camera facing towards you or away?
Mine is doing the same, actually. Yesterday I logged into my Google Plus page and saw there were new photos uploaded, ready for review. There were 8 or so pictures taken inside my pocket.
I would have thought that the proximity sensor would immediately put the device back to sleep if the camera was turned on inadvertently while holstered or pocketed...?
Klotar said:
I would have thought that the proximity sensor would immediately put the device back to sleep if the camera was turned on inadvertently while holstered or pocketed...?
Click to expand...
Click to collapse
You're right! I completely forgot about that.
I think the proximity sensor (located between front camera and the earpiece) should prevent the camera from turning on and I just did a quick test.
Phone in hand, pressing volume down rocker results in the camera turning on. This is normal.
To simulate phone in pocket, I took a shirt and used 1 layer to cover the proximity sensor and then pressed the volume down rocker. The phone did not turn on.
Quick easy test, took 10 seconds, give it a try to see if your camera still turns on. If not, something else other than the volume down rocker is turning on your phone.
This might be a stretch, but I've noticed the phone turns on by itself sometimes when putting it down on the desk. I'm thinking it's picking up a double-knock signal some how in the pocket and further movements cause the lock screen to slide to the right (which is the camera).
I would have thought that the proximity sensor would immediately put the device back to sleep if the camera was turned on inadvertently while holstered or pocketed...?
Click to expand...
Click to collapse
I can confirm this is not accurate. I put my g2 in my pocket and launched the camera with the vol down action, and it loaded.. Multiple times.
However I'm on the sprint g2 and removed a bunch of junk I didn't think I'd need so I could have deleted something that would prevent the phone from waking if the proximity sensor was tripping. Maybe?
Sent from my LG-LS980 using xda-developers app
bearsblack said:
However I'm on the sprint g2 and removed a bunch of junk I didn't think I'd need so I could have deleted something that would prevent the phone from waking if the proximity sensor was tripping. Maybe?
Click to expand...
Click to collapse
I don't think so. I'm on T-Mobile, and while I rooted my phone last night, I had the issue prior to rooting.
bearsblack said:
I can confirm this is not accurate. I put my g2 in my pocket and launched the camera with the vol down action, and it loaded.. Multiple times.
However I'm on the sprint g2 and removed a bunch of junk I didn't think I'd need so I could have deleted something that would prevent the phone from waking if the proximity sensor was tripping. Maybe?
Sent from my LG-LS980 using xda-developers app
Click to expand...
Click to collapse
Cover the proximity sensor and hold down the volume down rocker button to see if it goes to the camera app.
I tried it about 8-10x and during that time, the phone never goes to the camera app if the proximity sensor is covered.
yyz123 said:
Cover the proximity sensor and hold down the volume down rocker button to see if it goes to the camera app.
I tried it about 8-10x and during that time, the phone never goes to the camera app if the proximity sensor is covered.
Click to expand...
Click to collapse
Obviously lol... But nope.. Still loading the the camera with sensors covered. I'm not too worried about it tho. I haven't unlocked this phone in my pocket yet. Even with knock on active.
Sent from my LG-LS980
I have the T-mo one and I keep getting the camera and quick notes opening. It's super annoying. I have recently turned my phone arround, now the screen faces outward. It seems to be helping, I have not had it happen since.
Stop wearing your girlfriends pants
Sent from my LG-D803 using XDA Premium 4 mobile app
Must be some thin ass pants. Never once had happened to me. Proximity cover still lets cam launch.
xdafoundingmember said:
Stop wearing your girlfriends pants
Sent from my LG-D803 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol... I wish it was that easy.
I wear black 5.11 tactical pants everyday at work that have plenty of room and I have this issue.
did anybody find a way to turn the Vol Up/Down functions on lockscreen off?
I reckon an Xposed mod could help you with that.
I have been having the same problem and yesterday deleted 17 photos taken from inside my pocket in the last 2 days while I was at work. I have no case on the phone at the moment and I am not rooted.
Sent from my VS980 4G using xda app-developers app
I had the exact same problem when I first got this phone. Had no idea the camera was on until I felt my phone extremely hot in my pants. A case solved that problem for me.
robogo1982 said:
I reckon an Xposed mod could help you with that.
Click to expand...
Click to collapse
strangely enough, it lets you control the Vol keys only for the screen off (which would help everybody in this thread, yes) but i'm also looking to disable it for the lockscreen.
Using beanstalk Kitkat 4.4 uring calls my screen has been going black, when i hit the power/home button it comes on for a spit second then shuts off so I am unable to use my keypad... screen protector is not blocking the sensor, is there an option keep the screen on in this rom? I went into the beanstalk option and tried to remove the sensor proximity option but still getting thr same results. Any help is appreciated
Ill answer my own post as this seems to be an issue with galaxys. If you are having issues with your screen during calls its more than likely a proximity sensor hardware issue.. Had to unscrew the back and open the sensor area then spray with computer duster.. Fixed it immediately
Sent from my SCH-I545 using XDA Free mobile app
templton said:
Using beanstalk Kitkat 4.4 uring calls my screen has been going black, when i hit the power/home button it comes on for a spit second then shuts off so I am unable to use my keypad... screen protector is not blocking the sensor, is there an option keep the screen on in this rom? I went into the beanstalk option and tried to remove the sensor proximity option but still getting thr same results. Any help is appreciated
Click to expand...
Click to collapse
Add these lines at the bottom of your Build.prop and you done
ro.lge.proximity.delay=15
mot.proximity.delay=15
ro.ril.enable.amr.wideband=1
This past summer I had my Nexus 4 LCD and digitizer replaced, after which the proximity sensor stopped working. I installed the Proximity Screen Off app as a workaround to keep the screen alive during phone calls. Ever since I upgraded to Android L yesterday, this fix no longer seems to work. Is there anything that I can do besides sending the unit in for repair? I lack the tools to take apart the phone.
This problem is rather crippling as I cannot use the dialer or speakerphone during phone calls, or even hang up when the screen is off.
I have this exact same issue, and was also hoping to find a fix. Any ideas?
One thing to end calls. Accessibility - power button ends calls
Sent from my Nexus 4 using XDA Free mobile app
n2d551 said:
One thing to end calls. Accessibility - power button ends calls
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you. I have done this, for the time being, as it's difficult to end calls, otherwise. However, not being able to use the keypad whilst in call is posing to be an issue. Prior to the update and using 'Proximity Screen Off' app, I was able to catch the 'Home' button when pressing the power button, which allowed me to use the phone screen whilst in a call. With the new update, I am unable to do this.
I have come across a Disassembly Video (watch?v=AZDAIgwbXk4), but I'm not sure how confident I feel taking my phone apart.
The screen on my Nexus 4 has previously been replaced. When it was replaced, I'm fairly sure the Proximity Sensor did work, but then I dropped it on wooden flooring, and after that it no longer worked. It was a seemingly short drop, but this has somehow damaged the sensor. I'm not sure if the rubber cover (as shown in the video) has just moved out of place, or if it is completely broken. The light sensor works fine, in any case.
BobSmith9 said:
I have this exact same issue, and was also hoping to find a fix. Any ideas?
Click to expand...
Click to collapse
Admiral Nelson said:
This past summer I had my Nexus 4 LCD and digitizer replaced, after which the proximity sensor stopped working. I installed the Proximity Screen Off app as a workaround to keep the screen alive during phone calls. Ever since I upgraded to Android L yesterday, this fix no longer seems to work. Is there anything that I can do besides sending the unit in for repair? I lack the tools to take apart the phone.
This problem is rather crippling as I cannot use the dialer or speakerphone during phone calls, or even hang up when the screen is off.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2657176
mene82 said:
http://forum.xda-developers.com/showthread.php?t=2657176
Click to expand...
Click to collapse
I thought I had fixed it, but unfortunately the fix was short-lived. I discovered that I'm missing the gasket covering the proximity and light sensor, and this is causing an issue.
Anyone have any workable alternatives?