It is already the second time that the Proximity Sensor of my Nexus 5 is broken. During a call the display turns off and I cannot turn it on again. When I check the sensor with the App "Sensor Box" I can see that it always returns 0. As a workaround I want to disable the broken sensor. I already tried to disable it by adding "gsm.proximity.enable=false" to the build.prop file but this does not work. Does anyone has other ideas how to do this on a Nexus 5 with CM11 installed?
Related
My Galaxy S has a problem with the Light Sensor, every time i make a call my phone freezes or black screen, I tried running some sensor tests but also does same when i try the light sensor, so that must be it. have this problem for a year, at first i thought it was the proximity sensor.
When my headphone is plugged in, i dont have this problem because the light sensor wont interfear then.
I want to disable the startup of the light sensor,
I already setup ADB, so im ready to push and pull, but i don't know wich file i need to edit. remove a # here and there
Can anyone tell how wich file it is?
Got inspired by :
http://forum.xda-developers.com/archive/index.php/t-764368.html
Sure its not the proximity sensor? Cause I got the same problem. When I accept a call screen goes black, the upper bar is visible and after a while the screen turns off. Im ceratin that is a problem with the proximity sensor or not?
Same here, yeah think its the proximity, but my light sensor also doesn't function properly, auto brightness adjustment doesnt work also.
Very anoying problem.
My proximity sensor appears broken so it always is detecting "covered". This causes the screen to always go off when making a call.
Is there any way to disable the sensor and/or the call screen obeying the sensor?
I'm using CyanogenMod 10.1.2 on a Sprint Nexus S 4G.
Note that I've tried using Hardware Disabler to disable the gp2a driver (which should correspond to the sensor). Sadly doing that just causes the device to reboot,
Hi all,
I've had this issue for about 2 weeks or so. The proximity sensor on my Nexus 5 randomly stays active no matter what app is on or if the screen is locked. So whenever the screen is active and I put my hand/finger near the proximity sensor it will blank the screen. You can see how this would be annoying when you're just checking notifications and the screen blanks out. Any thoughts or suggestions? It definitely seems software related as a reboot solves the issue until it happens again. I've tried to consistently recreate the issue, but I can't tie it to any one app that was/is active, or any combination of events that causes it. After a few hours when I unlock my phone to check a notification I notice it's active because the screen will go dark. Is there a way to see what app(s) could be doing this?
My phone is unlocked and rooted, but stock rom. No screen protector at all. I can't think of any non mainstream apps that I have installed.
Thanks!!
I have this issue exactly. Did you ever find the fix for it?
Are you using any app that uses the proximity sensor to turn on the screen? (e.g. Shake Screen-On). Those apps keep the proximity sensor on (if using near receiver mode).
One way to see if an app is using the proximity sensor is by checking the battery options. One of those apps might be the one draining your battery.
Same here. Reboot makes it work fine for a couple days, then the proximity sensor just stays active til the next reboot. Has done this on CM, PA, and Cataclysm.
I have a XT1031 running on Boost Mobile. I'm currently running official SlimKat build 9 but switch back to stock when I am expecting alot of calls since I can't find a voicemail app that works with Boost Mobile on custom ROMs. I've searched for months for a fix that works to correct the faulty proximity sensor but haven't had any luck. Does anyone know of a way to completely disable the proximity sensor?
BaumerGXP said:
I have a XT1031 running on Boost Mobile. I'm currently running official SlimKat build 9 but switch back to stock when I am expecting alot of calls since I can't find a voicemail app that works with Boost Mobile on custom ROMs. I've searched for months for a fix that works to correct the faulty proximity sensor but haven't had any luck. Does anyone know of a way to completely disable the proximity sensor?
Click to expand...
Click to collapse
I guess it is not possible to disable it... If you want to fix the proximity sensor you must flash your phone with an stock room...
The proximity sensor has been bad since I received the phone. It was a gift and out of warranty. My issue is there no matter if the phone is stock or running a custom ROM. I was hoping a dev would have some insight to disabling it with a prop/hex editor or something.
Caution DO NOT DO THIS unless you want your proximity sensor completely disabled!!!
Also you're doing this on your own risk!
So if your proximity sensor is not working at all, you can disable it completely by chopping it off the board. The light sensor is separate, so this won't affect your auto-brightness.
Open your phone (14 torx screws), pop out the back panel.Barware not to lose your Power and Volume keys.
You don't need to detach the battery, just go ahead and lift the board carefully ( there are videos on YouTube how to do that ).
Flip the board to your right hand side, be careful, the display flex is still attached, you don't want to break that.
You can now find both sensors on the top right corner of the board, the proximity sensor is the LEFT one when you face the board straight up.
Use a small flat screwdriver and with a semi-gentle push in its base you can chop it off.
You're done!
Reassemble carefully.
Thanks for the suggestion I'll try to find some of those YouTube vids you mentioned. But from what I've been reading is that the sensor is just an ambient light sensor that can detect proximity when coupled with an IR-LED so I'm not understanding how I can just chop off the prox sensor. I can't post the link but the article is on Andrux & me blog titled CT406: proximity and light sensor on MotoG
Sent from my Moto G
BaumerGXP said:
Thanks for the suggestion I'll try to find some of those YouTube vids you mentioned. But from what I've been reading is that the sensor is just an ambient light sensor that can detect proximity when coupled with an IR-LED so I'm not understanding how I can just chop off the prox sensor. I can't post the link but the article is on Andrux & me blog titled CT406: proximity and light sensor on MotoG
Sent from my Moto G
Click to expand...
Click to collapse
Proximity and light sensors are separate, so chopping off the proximity one won't affect anything, besides proximity not working and the circuit will report "open", which means no object near, hence your screen won't turn off.
There are many types of sensors and they might differ in the way they work.I seriously don't see what y you've said is related at all.
For anyone interested, I found a module for Xposed Framework called Disable Proximity Sensor and it works flawlessly
Sent from my XT1031
hi, is anybody know if there any mod (magisk/xposed) that disable proximity sensor only?
already tried disable sensor on developer mode toggle, it working fine, but i only need the proximity sensor off (faulty hardware)
it makes the screen goes always black if receiving/call (phone & whatspp)
Already tried sensor disabler on Xposed also not working as it already outdated
im using 10.3.4 oxysgenOS
Try turning off the pocket mode in settings. Otherwise you'll have to manually press the power button so that it doesn't become dark.
mudepz said:
hi, is anybody know if there any mod (magisk/xposed) that disable proximity sensor only?
already tried disable sensor on developer mode toggle, it working fine, but i only need the proximity sensor off (faulty hardware)
it makes the screen goes always black if receiving/call (phone & whatspp)
Already tried sensor disabler on Xposed also not working as it already outdated
im using 10.3.4 oxysgenOS
Click to expand...
Click to collapse
Hello,
I have the same problem, did you find a solution?
Thanks
nope
i think the hardware sensor is faulty, and you need to change it
temporary solution is to disable hardware sensor on quick toggle (enable it on developer mode)
disable on receiving call, enable it again after that
i replaced the sensor (have to replace the damage oled screen because fall of the ground)
and now its working again