Related
I dont know if this is an issue with other handsets.
I installed proximity screen off application . The purpose was to have the phone turn the screen off when i close my flip case.
However i found something strange.
When the flip case is very close to the screen the proximity sensor does not seem to detect that there is something covering it.
Is this an issue with every one ?
Any solution
Please see the videos
As you can see from the videos when i bring the shield very close the proximity sensor does not seem to detect the sheild.
Edit : However if u use ur finger this is not seen
I've noticed the same behavior, it's quite annoying because it kills one of NoLed's best features (screen off using prox. sensor).
[deleted]
Still really annoying that the original flip cover won't work with the proximity sensor. A workaround might be a third party flip case. A diy modification of to the original one won't work since if I close it AND hold whatever object that alone is enough for a positive result over the flip cover, the sensor will still not register positive [because a minimal distance between an object and the glass surface is required, see below].
mine works even with a finger...
I've done it a few times accidently when i was trying to access the notification bar while on the phone
ph00ny said:
mine works even with a finger...
I've done it a few times accidently when i was trying to access the notification bar while on the phone
Click to expand...
Click to collapse
Thats the thing i was saying.
With finger i works great even if u touching the screen
Dial *#0*# and press sensor. If it vibrates, the proximity sensor is registering an object.
Maybe it comes in handy with testing.
It's working for me, thanks for the tip about the app!
edit:
Okay, I tested and found that indeed when you set the app to:
"Cover an hold to lock the screen" to say 5 seconds.
Close the flipcover.
It does not register.
However. If I set:
"Disable Accidental Lock" to .25 seconds.
Close the flipcover.
It works quite well.
Coming back to the sensor. It indeed does not register the flipcover when it's closed and touching the screen.
Weird thing is it does not register your hand anymore either.
Recreating issue:
Remove flipcover and lay it completely flat over the sensor.
Dial *#0*#.
Press "Sensor".
No registration.
Now hover your hand over where the proximity sensor is, and... How about that, no registration.
This indeed messes up NoLed's battery saving feature.
This can also be a problem when:
You set screen timeout to 10 min.
In the app's settings set "Disable in landscape" to on.
Then use an app in landscape mode.
Close flipcover while in landscape mode.
Then rotate to portrait. At this point it should start registering again and turn off screen..
The sensor does not register and screen stays on.
Drains battery.
It is a really cool idea, but it does not function properly.
It's too flaky, also when just handling your phone. I find myself accidentally turning off the screen.
Maybe if you use a case or some other cover with a different or thicker material it would work better.
I ordered a Zenuscase, I'll give it a try with that one.
Don't know how long it'll take to arrive though
reflective color
heey i found the problem , the sensor is working fine ... but when so close with any black object the light is not reflected back to the proximity sensor.(black color absorbs light).
Repeat your video with any white object and you will notice the difference..
Now i am using Autostart and it works great with samsung original flip cover (white flipcover).
you can use any white sticker on the black one.
ahmedtaha7 said:
heey i found the problem , the sensor is working fine ... but when so close with any black object the light is not reflected back to the proximity sensor.(black color absorbs light).
Repeat your video with any white object and you will notice the difference..
Now i am using Autostart and it works great with samsung original flip cover (white flipcover).
you can use any white sticker on the black one.
Click to expand...
Click to collapse
ya correct, just few day back i have asked this issue to developer
http://forum.xda-developers.com/showpost.php?p=22170417&postcount=5
But it will work perfact if you use proximity + light both sensor enabled.
Color has no influence, distance between an object and the proximity sensor is what matters. I've just tested this using pieces of paper, cloth, metal and wood in white and black colors. The sensor seems unable to correctly register anything that is less than approximately 1 mm away from the glass (it may report 0 cm or jump to 5 cm). Also it seems it only reports changes of a certain minimal distance between two readings, even if the reported value remains the same as the old one. Anything below the threshold of the 5 cm reading will always result in a reported value of 0 cm, but if the effective distance between reading A and reading B was below a certain threshold, the sensor will not report a new reading of 0 cm (thus an object hovering stable over the sensor will not produce a 2nd post). I'm not sure if the sensor has a state that can be read at any time. From my tests using AutomateIt Pro, it seems only new posts can be used by apps. And if the delta between two readings is to small to make the sensor post a "new" result, then this can be problematic under certain circumstances (like trying to turn the screen off after the flip cover got closed (prox. sensor = 0 for 0 sec) and stays closed (light sensor = 10 for 5 sec) while preventing the screen from going off after an accidental wipe over the prox. sensor e.g. with the hand).
@Dr. Ketan: I've tested Power Switch (again) and I'm quite certain that for the Note + Flip Cover it only works through the light sensor (which is unsatisfying since it then won't work correctly in the dark). Covering the proximity sensor only doesn't make the app reliably react.
Power switch works ok for me with the Samsung flip cover. I have the confirmation set to minimum Abe theactivation delay set to 0 seconds.
It doesn't always work from the lock screen but works fine from the home screen or apps
Sent from my GT-N7000 using xda premium
so is it a hardware issue of software?
might it be fixes in ICS? it's fu***ng annoying! just bought the flip cover(black) yesterday and also bought smart cover app, my note's screen keeps on turn off (when flip closed) then it turns back on (flip still closed)!
Any solution for gingerbread? like proximity calibrator perhaps? (while waiting for final version of ics to come out)
Power switch will work if you use proximity + light sensor both.
Sent from my GT-N7000 using xda premium
dr.ketan said:
Power switch will work if you use proximity + light sensor both.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
It's so sensitive that the moment my finger move over the sensor, the shutdown menu pops up.
Any app that works with the flip cover?
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.
I am currently running:
3.4.0 franco kernel
JOP40D - 4.2.1
And I have a really annoying bug on my nexus4 which I dont know if its just a fault on my phone or if its a setting that I have not configured.
Basically when I call someone the screen automatically switches off and there is no functionality, even when I press the power button the screen doesnt become active, which means I cant push keypad numbers when I am calling a number which has menu options, I cant hang up unless the other person does it first, and I cant put my phone on loudspeaker.
As soon as the call ends the screen becomes active again, Im sure that it has something to do with the camera sensor on the front of the phone because i know most of them detect when you are putting it up to your ear so then it turns off the touchscreen so that you dont acidentally touch the buttons with your face, with mine it just doesnt let you do anything at all when im in a call.
Would much appreciate any advice/help. Thanks in advance :good:
I believe you're referring to the proximity sensor. Do you have a screen protector with no cutout for the sensor or, perhaps, an incredibly oily face?
Agree with estallings15, I modified my screen protector and all has been well.
ahhhhhh right i have never thought to look into that, i assumed that the proximity sensor was just the camera which has a cutout on my screen protector but ive just realised that there is a small sensor on the left of the phone which I now assume is the proximity sensor.
OK i have just took my screen protector off and it works fine now! thanks for pointing that out
Maybe u guys could also help me with the other question that I posted on the q&a section lol :good:
much appreciated
My defy+ proximity sensor is not working.
As soon as I make a call, the phone screen goes black. The call goes thru fine, but the screen goes black.
No, I don''t have my finger or face near the proximity sensor.
No mods on the phone OS.
I did some debugging-
Cleaned the back of the phone by blowing air.
Tried the screw loosening like in the youtube video
Changed brightness settings from auto to manual.
Changed display turn off from 1min to never.
Finally, I downloded a sensor app and checked for change in the value of the proximity sensor when put by finger in the sensor area. The value was stuck at 3%, no matter what I did.
I was playing around and when I pressed the speaker area near the proximity sensor, the sensor value jumped to 100%
So I think the glass is blocking the sensor (or acting as a reflector).
Just to make sure the glass was the issue, I made a call by keeping the speaker area pressed. It worked as expected - no screen blanking after call. It does go black if I put my finger in the proximity sensor area.
I have no idea how to fix it.The screen & sensor need to be pressed closer.
Only thing I have tried is tighten the screws in the back. But no use.
Any help?
Since you don't have mods, it's probably broken, go to customer care.
Or you can maybe try factory reset
Do you have a screen protector?
Out yes remove it.
If not your sensor is broken.
Sent from my MB526 using XDA Premium 4 mobile app
My nexus 4 Lollipop 5.1 Seems to have a problem when I make a call. I hit the phone symbol, select the number I want to call from my requent call list. I hit the dial button and make the call........ The problem comes when I go to end the call the screen goes black such that I can end the call. I just have a black screen........
Does anyone out there have any idea whats happening and what the fix may be?
Thanks for any help
Remove your screen protector.
Blacksmith5 said:
My nexus 4 Lollipop 5.1 Seems to have a problem when I make a call. I hit the phone symbol, select the number I want to call from my requent call list. I hit the dial button and make the call........ The problem comes when I go to end the call the screen goes black such that I can end the call. I just have a black screen........ Does anyone out there have any idea whats happening and what the fix may be? Thanks for any help
Click to expand...
Click to collapse
The screen is supposed to go black when you make a call--or, rather, when you place the phone to your ear. There is a "proximity detector" along the top edge of the screen, and it detects your ear when your ear gets close. The phone then turns off the screen sensors so that your ear or your cheek doesn't push any buttons while you are talking, and turns off the screen illumination for aesthetic reasons. However, the proximity detector is supposed to cause the screen to turn back on when you remove the phone from your ear. That isn't happening for you. When it didn't happen for me, I took it to the shop. The tech said the proximity detector was broken, and ordered a new one. But replacing the proximity detector didn't help. He finally disabled the sensor so that proximity was never detected. that worked.
This story does not have a happy ending for me. The phone worked for a couple of days. Then I tried to reboot, and it went in to a boot loop. None of the standard cures for a boot loop is helping me. I doubt if the two problems are connected.
Proximity sensor turns off screen when you put it to your ear to avoid your skin touching the "End call" button or something else
kbakalar said:
The screen is supposed to go black when you make a call--or, rather, when you place the phone to your ear. There is a "proximity detector" along the top edge of the screen, and it detects your ear when your ear gets close. The phone then turns off the screen sensors so that your ear or your cheek doesn't push any buttons while you are talking, and turns off the screen illumination for aesthetic reasons. However, the proximity detector is supposed to cause the screen to turn back on when you remove the phone from your ear. That isn't happening for you. When it didn't happen for me, I took it to the shop. The tech said the proximity detector was broken, and ordered a new one. But replacing the proximity detector didn't help. He finally disabled the sensor so that proximity was never detected. that worked.
This story does not have a happy ending for me. The phone worked for a couple of days. Then I tried to reboot, and it went in to a boot loop. None of the standard cures for a boot loop is helping me. I doubt if the two problems are connected.
Click to expand...
Click to collapse
Thanks for that info I had not thought about that... That may be cause of my problem.... I will have to figure out a solution
Thanks again
Didgeridoohan said:
Remove your screen protector.
Click to expand...
Click to collapse
I am not using a a "screen protector" But thanks for the input
Ok, was worth a shot...
Then you must likely have a faulty proximity sensor, as stated previously.
Download an app, like AndroSensor, and see what the output for the proximity sensor reads. When nothing is covering the sensor (top left corner) it should read 5 cm/2 inch, or something similar. If it reads 0, it's busted...
Didgeridoohan said:
Ok, was worth a shot...
Then you must likely have a faulty proximity sensor, as stated previously.
Download an app, like AndroSensor, and see what the output for the proximity sensor reads. When nothing is covering the sensor (top left corner) it should read 5 cm/2 inch, or something similar. If it reads 0, it's busted...
Click to expand...
Click to collapse
I did as you suggested and the results say 2" uncovered 0 when covered
Hmm... The plot thickens...
That means you have a working proximity sensor. No idea what it could be then.
Didgeridoohan said:
Hmm... The plot thickens...
That means you have a working proximity sensor. No idea what it could be then.
Click to expand...
Click to collapse
I'll keep looking for a solution.......... It's a pain especially if if I have to respond to a VM and hit a Number.......
Thanks again
I have the same issue. In my case, the proximity sensor may have been broken or blocked by dust.
My "temporary" solution is using the power button to disconnect calls. While using a Bluetooth headset, the screen can be turned on. I hope there is a better solution.
Man of La Mancha said:
I have the same issue. In my case, the proximity sensor may have been broken or blocked by dust.
My "temporary" solution is using the power button to disconnect calls. While using a Bluetooth headset, the screen can be turned on. I hope there is a better solution.
Click to expand...
Click to collapse
Yes I resetthings so I only have to hit the power button to end a call Thanks for all the help