Hey recently my proximity sensor broke. When I'm in a call the screen will stay off and will not turn on. Because of this I can't access the dialpad, hit the speakerphone button, or even hangup.
Is there a way to turn the proximity sensor off or force it to think that nothing is up close to it? I'm in latest Sultan rom if that matters. I have tried full wiping and resetting everything already.
Sure,
But, the issue is you'll need xposed for this method.
download this, install, enable, reboot.
Open the app, swipe from the left to inside, go to proximity and disable it completely. Done
Awesome I'll try it out since I already have xposed and root
EDIT: yep works perfectly thanks
surronix said:
Awesome I'll try it out since I already have xposed and root
EDIT: yep works perfectly thanks
Click to expand...
Click to collapse
Happy to be of help
Related
why every build claims to have light sensor works while it doesn't. I tried every build that says light sensor works. Well, that works only If I open an app call "Android Sensor Data", then I can see the light lux changes as well as the screen brightness, once close the app, the system just wont update the light sensor......
can anyone confirmed that it's actually working? like put the phone under a lamp and the screen will have full brightness?
No, it doesn't work properly... WiFi, data, G-sensor, battery, camera aren't good also. Bad luck...
Sent from my HTC Desire using XDA App
why every chef says it's working then? Really confused, I tried at least 4 builds tonight, frustrating.....
it does work, but not properly. U need to enable "Automatically Blacklight Adjustment" under WinMo before boot into Android. Light Sensor works on fresh reboot, but after using android for awhile, and light sensor not working anymore. To get Light Sensor works again, u need to fresh reboot android again
thanks, will try. I am using chucky droidrom and can't find auto brightness option.
Lets just be thankful that we got android running on our phone...if you must have auto light, use winmo...
waichai said:
it does work, but not properly. U need to enable "Automatically Blacklight Adjustment" under WinMo before boot into Android. Light Sensor works on fresh reboot, but after using android for awhile, and light sensor not working anymore. To get Light Sensor works again, u need to fresh reboot android again
Click to expand...
Click to collapse
Thank u so much. I finally managed to find the registry key that controls auto brightness in chuckydroidrom, and now auto brightness in android works (for now)
BTW, I am thankful to the developers, however, thought they should clear things out instead of just saying "it works" and omit the part "how".
I googled all night, read carefully every 1st post in every build, couldnot find anything related, that's why I asked
Thanks again to every contributor
macoy said:
Thank u so much. I finally managed to find the registry key that controls auto brightness in chuckydroidrom, and now auto brightness in android works (for now)
BTW, I am thankful to the developers, however, thought they should clear things out instead of just saying "it works" and omit the part "how".
I googled all night, read carefully every 1st post in every build, couldnot find anything related, that's why I asked
Thanks again to every contributor
Click to expand...
Click to collapse
Hi macoy,
Do you mind to post here how to set it in the registry?
Coz I also using chuckydroidrom.
funky81 said:
Hi macoy,
Do you mind to post here how to set it in the registry?
Coz I also using chuckydroidrom.
Click to expand...
Click to collapse
I open phm registry editor in winmo(included in "tools"), search "backlight" in the current user section, u will find "backlight" under "control panel", there are several keys in it. change "lightDetectOn" to 1 and the screen brightness will change immediately according to ambient light.
launch android
PS. after some time, auto backlight stops working..... and I think the sensors still works coz when I open android sensor data, it reads normally, the system just ignore it after a while.
Thanks for the enlightment. How about in the Android,do you change any settings?
didn't change anything, just enable auto brightness.
I am running CM7 weekly 4 on my ATT Atrix. Sometimes (not always) when I try to lock the phone by pressing the power button, it will turn off, but then immediately turn back on to the lock screen.
Has anyone else seen this?
I have seen it with stock lock screen and widgetlocker.
I have also played around with a few different kernels (stock weekly, Faux123 v23 and Faux123 v24b4) and it happens with all of them.
This wasn't happening with the Ba2TF build, and I can't post in the weekly thread in Atrix Android development because I don't have enough posts to post in the dev section
Trackball is your problem..
Try to click without moving your finger..
Sorry for my Inglish..
Bye
I switched it to 'eraser' mode and thats seems to keep me from accidentally causing movement with the fingerprint sensor. It would be nice if there was a way to completely disable the fingerprint sensor as trackball functionality (I honestly don't miss the trackball from my N1 on my new atrix)
AngerMCS said:
I switched it to 'eraser' mode and thats seems to keep me from accidentally causing movement with the fingerprint sensor. It would be nice if there was a way to completely disable the fingerprint sensor as trackball functionality (I honestly don't miss the trackball from my N1 on my new atrix)
Click to expand...
Click to collapse
Settings> Device Settings> fp navigation> Nav Enable> DISABLE *reboot*
Ahh. I saw that, but didn't realize you had to reboot to make it effectual.
Thanks!
AngerMCS said:
Ahh. I saw that, but didn't realize you had to reboot to make it effectual.
Thanks!
Click to expand...
Click to collapse
Sure, no problem. I didn't realize a reboot was required either until I read that here on XDA. Ideally it should tell you it requires a reboot.
Is there a workaround or fix to the proximity sensor issue when using CyanogenMod 10.1? It doesn't matter which dialer I use, my screen goes blank and I can't get it back on to use the keypad or hang up.
Thanks in advance.
Mr.Preacher said:
Is there a workaround or fix to the proximity sensor issue when using CyanogenMod 10.1? It doesn't matter which dialer I use, my screen goes blank and I can't get it back on to use the keypad or hang up.
Thanks in advance.
Click to expand...
Click to collapse
See if enabling wake on volume helps:
Settings > Display > Volume rocker wake
Mr.Preacher said:
Is there a workaround or fix to the proximity sensor issue when using CyanogenMod 10.1? It doesn't matter which dialer I use, my screen goes blank and I can't get it back on to use the keypad or hang up.
Thanks in advance.
Click to expand...
Click to collapse
If you are using a screen protector, there is a known issue regarding placement. If the protector cutout is too close to the sensor, it will interfere with the proper operation of the sensor and blank out the screen too easily.
I ran into a similar issue, turns out the tinting on the screen for the sensors had gotten dirty inside and I had to disassemble my phone and clean the sensor Windows. However if you don't like the idea of disassembling your phone, the HTC rezound proximity calibrator app on Google play might be helpful to you. I would try the app first before doing something more extreme.
retrostudd said:
I ran into a similar issue, turns out the tinting on the screen for the sensors had gotten dirty inside and I had to disassemble my phone and clean the sensor Windows. However if you don't like the idea of disassembling your phone, the HTC rezound proximity calibrator app on Google play might be helpful to you. I would try the app first before doing something more extreme.
Click to expand...
Click to collapse
I don't have a screen protector. This solved it for me. Many thanks.
That said, the settings I'm using are a little weird. I have the Low set to 81, and it doesn't seem to matter what the High is set to (currently 100).
This fix works
retrostudd said:
I ran into a similar issue, turns out the tinting on the screen for the sensors had gotten dirty inside and I had to disassemble my phone and clean the sensor Windows. However if you don't like the idea of disassembling your phone, the HTC rezound proximity calibrator app on Google play might be helpful to you. I would try the app first before doing something more extreme.
Click to expand...
Click to collapse
this totally worked to fixed this same issue I have had. I used to have to go outside on a sunny day for my screen to come on while making a phone call. Once I used this app I was able to get it to come on in a dark room with hardly any light. I may at some point open her up and actually clean the inside of the sensor cover, but for now this worked like a charm.
Thanks for the tip.
One item to note, if you do decide to open your phone and clean the sensor windows, don't clean too aggressively or you will remove the tint from the backside of the glass. Just a tip.
I'm glad you guys have gotten your sensors working again.
I just had this problem today. Previously I never had issues with prox sensor, but just a couple days ago I did a complete wipe (data, cache, dalvik, system and internal SD card) and installed RC1 with a fresh install. The app mentioned above DID fix my issue however I know its a ghetto fix. Before running the app, the proximity sensor would work normally in good light, but not in low light. After running the app it works even in dark light which is great. However, I know its a weird fix. I can actually see the red proximity sensor during calls, when I couldn't previously. I'm glad I got it working, but I know there is something wrong still, and it's definitely ROM related as opposed to hardware because just 2 days earlier it worked fine before the clean install. Hmm..
Sent from my Incredible 4G LTE using xda app-developers app
Hey guys.
i'm having some issues with my proximity sensor..
its working fine but. somthing inside the device is blocking it.
i think its a mix between some dust and the fact that my screen is a bit loose and far from the sensor.. when i press with my finger on the top of the screen i move something and the sensor reacts.
i tried sevreal apps but nothing could just shut it off completly..
i also found a flashable zip that should shut it off but it didn't went well with my rom..
any other sugesstions will be great..
i'm now using the latest crDroid [cm10.2] for the s2 with the provided kernel:
http://forum.xda-developers.com/showthread.php?t=2435024
tnx for helping:good:
anyone?
kind of desperate..:crying:
drszp said:
anyone?
kind of desperate..:crying:
Click to expand...
Click to collapse
It's quite easy to take apart the phone and clean the part, try that
Inviato dal mio GT-I9100 con Tapatalk
Solution
Heres what I did after trying all the suggestions and still no avail.
Had to disable the proximity sensor altogether.
Root Required. Download Hardware Disabler from Google Play store. Once you installed the app, it scans your root directory. Select your proximity sensor hardware. IT WILL SHOW AS cm3663 IN THE LIST. Manufacturer capella. Tick the box next to cm3663. Reboot your phone.
Your good to go!! :good:
codin said:
Heres what I did after trying all the suggestions and still no avail.
Had to disable the proximity sensor altogether.
Root Required. Download Hardware Disabler from Google Play store. Once you installed the app, it scans your root directory. Select your proximity sensor hardware. IT WILL SHOW AS cm3663 IN THE LIST. Manufacturer capella. Tick the box next to cm3663. Reboot your phone.
Your good to go!! :good:
Click to expand...
Click to collapse
thank you very much! disabled it like you said!
no more black screen during a call :victory::good:
Cheers mate!! Have fun!!
So I'm using the CM11 4.4 Kitkat on my Galaxy S4 and recently found out that my proximity sensor isn't working (when I dial the screen goes black and won't turn on until the call is over). I've read many threads about fixing it but I think it's broken. So all I want now is to disable it but there isn't such option in the Cyanogenmod. Is there anyway to disable it, like with a terminal or something?
bump
bump!
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
kg2128 said:
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
Click to expand...
Click to collapse
glad someone found this useful.
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
sjschoo said:
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
Click to expand...
Click to collapse
Yeah I noticed that, the best solution is to get the proximity sensor fixed in the end. Then you don't have to disable anything. If your lucky it doesn't even need to be replaced, just cleaned. For me I can live with no rotation, because the screen off during calls is a ridiculous PITA by comparison. Also apps can force landscape mode even with the gyroscope not working. I use force landscape for videos through mx player, and mango reader for manga.
I finally broke down and took the phone apart. There were no warranty stickers to break so assuming you don't mess up royally, it shouldn't effect your resale value. All it took was an eye glass screw driver and a q-tip. Once I was inside I tried the can of air first, but didn't help. Swabbed the back of the glass with the q-tip and that finally provided lasting relief.
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
khudko83 said:
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
Click to expand...
Click to collapse
Changing the rom isn't going to do anything, even factory roms (I've tried it). If a replacement sensor doesn't fix it for you, then it's going to be hard to fix it yourself. All the posts I've seen so far have cleaned the sensor or replaced the sensor and fixed the problem. Otherwise people like me just turn the sensor off.
You were right, proximity software fix didn't help! But how is it possible to work in this (the same wrong) way with changed sensor? Can it be some main board hardware problem? But it doesn't look like this...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Maybe somebody knows how to fix the issue???
Finally fixed
Thanks so much qman66 I have had problems with my proximity sensor on my JFLTEXX pretty much since I got it. Had been using the xposed disable proximity sensor module but xposed doesn't work with CM12. Your simple system tweak has given me use of my phone know call options again
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
Hi, I tied to do this but it says I can't save the changed so file... Can you let me know which root explorer and text editor you are using?
Thanks massively
Not a text file
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I found sensors.msm8960.so with many references to proximity sensor but it is not a text file!!
Samsung S4 Active w LOS 15.1 (a&Droid 8.1) - how to disable HW sensor(s).
Hi All
Hope some here will help me stay afloat long enough to learn to surf by myself; bit of a noob in this wild ocean here (more of a 'fresh water/indoor pool' kinda dude I guess) - but trying to break out of tis little pond and learn to 'surf'. Anyway, to the point:
1. HW spec
Samsung Galaxy S4 Active
GT - i9295
TWRP 3.3.0-0
Lineage 15.1 20180227 jactivelte
(sometimes with opengapps pico and addonsu15.1 but mostly just LOS and addonsu nothing else)
2. Have the sensors on phone covered up with black electrical tape - all but the notification light are covered and it's gonna stay that way - NOT negotiable!
Obvious Issue: Have the blank screen during phone call problem. Can end calls using power button but I need to use the keypad quite often so need the screen to stay on. How? Ideally want to (SW) disable most if not all hardware sensors - how?
Tried a few fixes but no luck, e.g.:
(a) adding 'the' fix/control many sensors apk no good as not suported under 8.1 (plus want to find out how to do manually myself not use 'hand outs').
(b) edit selected sensor etc ".so" (eg in system hw) files - so far not resulting in the disabled ProximitySensor.
So, I really want to hack this myself at cmd line level, am ok with that (many years IT ops/admin experience in 'fresh water commercial space'). Can mount system using TWRP then adb shell to connect and find and grep for stuff in files but cannot find setttings I need to change to disable sensors for good. Where to look/find more info?
What do I want to achive:
Make calls and have keypad stay on all the time or give me manual option to turn screen on/off with a hw button during call.
How:
I am happy to disable pretty much all sensors (proximity, gyro, compass etc) in system or firmware memory so that I am free from the overlords and really want to be able to use the keypad during calls - and have option to manually turn screen off/on during call would be cool.
Constraint:
Really want to do this from (a) cmd line or (b) edit code/recompile (learning curve) the LOS 15.1 or whatever to disable sensors for good. I will be using this old thing mostly for just call and txt not much else - and cannot be asked to buy an old Nokia handset.
Thanks,
iHAL8999.999... (hi dave...)