For some reason the proximity sensor isn't working properly. When I'm in a call, and move the phone away from my face, the screen stays off... Anyone know where the setting is, if there is one, to change this?
One thing you might check is the setting for "In-Pocket detection" under Display Settings. I don't believe that feature works very well (if at all), and if it is enabled I've heard it can mess with the way the proximity sensor works when holding the phone next to your head. Try disabling it and see if there's any improvement.
Diablo_692 said:
One thing you might check is the setting for "In-Pocket detection" under Display Settings. I don't believe that feature works very well (if at all), and if it is enabled I've heard it can mess with the way the proximity sensor works when holding the phone next to your head. Try disabling it and see if there's any improvement.
Click to expand...
Click to collapse
Yeah, that fixed it. Thanks. It would be nice if that feature actually worked though, it's useful.
I agree it's a great idea, but poor or no implementation seems to be where it stands currently. Perhaps a patch for this and other 4.5.91 issues will be forthcoming in the not too distant future.
Related
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
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...)
Just updated to Oreo on my H830 today. When I was on Marshmallow/Nougat, disabling KnockOn was as easy as using the Quick Shortcut Maker app to disable it.
Now, it doesn't seem like there is an option to disable it using the app. Does anyone have a solution?
Update for OTA?
Enviado desde mi LG-H830 mediante Tapatalk
I am having the same exact issue. It seems when LG rewrote their settings interface from scratch, they actually remembered to remove the hidden settings this time (Only God knows why the settings are even hidden and now completely disabled to begin with). Unless they just changed the name of the "KnockOn" Setting.
Its a shame too, because one of the first things I would always do whenever I needed to factory reset.etc was to download QuickShortcutMaker and disable KnockOn right away. But now I can't do this. Hopefully someone finds a workaround. Why can't LG just let us disable these things?
NullaVisus said:
I am having the same exact issue. It seems when LG rewrote their settings interface from scratch, they actually remembered to remove the hidden settings this time (Only God knows why the settings are even hidden and now completely disabled to begin with). Unless they just changed the name of the "KnockOn" Setting.
Its a shame too, because one of the first things I would always do whenever I needed to factory reset.etc was to download QuickShortcutMaker and disable KnockOn right away. But now I can't do this. Hopefully someone finds a workaround. Why can't LG just let us disable these things?
Click to expand...
Click to collapse
Excuse me just a quick question. Why would you disable it?
OverplayOfficial said:
Excuse me just a quick question. Why would you disable it?
Click to expand...
Click to collapse
My point exactly i don't think it's draining slot of battery.
I'm curious why they disable it.
1) Battery-saving concerns
2) Avoiding accidental wakes
3) Absolutely no point in keeping it on if the user doesn't want it
Because it can be triggered by accident. And depends on how you setup the phone, it could cause annoying problems if phone is turned on by accident.
nookin said:
Because it can be triggered by accident. And depends on how you setup the phone, it could cause annoying problems if phone is turned on by accident.
Click to expand...
Click to collapse
I may be wrong but I think it's not that easy to trigger it. As the phone don't turn the screen on unless the proximity sensor is not triggered, the phone inside a pocket or in a situation like that won't turn the screen on.
but I'm not saying this applies to all situations
Most accidental trigger occur while holding the phone or dropping off the phone. I think the point OP trying to make is that owner should have the option to turn the feature off. If you need the knock-on feature, by all means keep it. I use the fingerprint reader to turn phone on. Knock-on is really just a way for me to make mistakes.
I have the same issue.
I had KnockOn disabled and updated to Oreo; now double tap to wake doesn't work (using default LG home) .
Normally this would be OK but recently power button started giving some trouble so double tap to wake would be a good feature to have.
Unfortunately can't find the menu to re-enable it in Oreo.
Hoping someone one finds a way and post it here
Through testing I have determined that the "phone-going-automatically-to-speakerphone", any time I pull my head more than five inches fro the screen during a call, is due to the proximity sensor. It was not like this before the latest update.
I defeated this by placing a tiny piece of black electrical tape over the proximity sensor.
I would rather just turn the proximity sensor off, or at least turn the "automatically going to speaker phone) function off, but in past requests no one seemed to know how to do that.
So, I am left with just turning off the proximity sensor off.
Anyone know how?
Thanks.
MB
Variant: LGH932 Unrooted, stock firmware
Update: November 1st 2018 security patch
papamalo said:
Through testing I have determined that the "phone-going-automatically-to-speakerphone", any time I pull my head more than five inches fro the screen during a call, is due to the proximity sensor. It was not like this before the latest update.
I defeated this by placing a tiny piece of black electrical tape over the proximity sensor.
I would rather just turn the proximity sensor off, or at least turn the "automatically going to speaker phone) function off, but in past requests no one seemed to know how to do that.
So, I am left with just turning off the proximity sensor off.
Anyone know how?
Thanks.
MB
Variant: LGH932 Unrooted, stock firmware
Update: November 1st 2018 security patch
Click to expand...
Click to collapse
Why did you open a new thread when you had already started this one on the same topic?
https://forum.xda-developers.com/lg-v30/help/v30-automatically-goes-speakerphone-t3886240
My US998 20G (January 2019 security update) does not have that proximity sensor/automatic speakerphone feature.
I would love that feature, because if I need to check something on my phone during a call, I can keep listening/talking to the person on the call. It's actually a feature you can enable on many custom ROMs, like Resurrection Remix.
I'm curious why you do not like it?
papamalo said:
I would rather just turn the proximity sensor off, or at least turn the "automatically going to speaker phone) function off, but in past requests no one seemed to know how to do that.
So, I am left with just turning off the proximity sensor off.
Click to expand...
Click to collapse
You can try this:
Settings/General/Acessability/Vision/Talkback/Settings/Use Proimity Sensor - turn off.
There's also various apps that claim to turn off/disable proximity sensor.
You may be able to enter the H932 hidden menu and turn off the proximity sensor.
https://forum.xda-developers.com/lg-v30/how-to/tmo-v30-hidden-menu-t3753465
"Talkback is not installed"
Should I install it to disable something else?
And WHAT secret hidden ninja invisible menu?
Thanks!
papamalo said:
"Talkback is not installed"
Should I install it to disable something else?
And WHAT secret hidden ninja invisible menu?
Thanks!
Click to expand...
Click to collapse
See post #1 of the link I included.
The hidden menu has calibration, and other technical features not available to normal people, thus it's called the "hidden menu". Be very careful messing with anything in there, however. One time I screwed up something in there and had to do a Master Reset (got stuck on one LTE band).
---------- Post added at 08:09 AM ---------- Previous post was at 07:12 AM ----------
papamalo said:
"Talkback is not installed"
Should I install it to disable something else?
Click to expand...
Click to collapse
That came up when doing Google search for disabling proximity sensor. Some handicapped people need to bring the phone very close to their face without the screen going dark, so that was the suggestion for them on how to turn off proximity sensor. I thought it might work for you also.
What you want to do is very unusual -- turn off proximity sensor to disable a feature only you seem to be complaining about. I'm just trying to give information.
Thank you Chazzmatt! I wasn't trying to seem like I didn't appreciate the help.
For me it doesn't work because I work with my phone and it going automatically into speakerphone ode reveals Private client information to others who may be standing nearby.
But thanks. I figured out how to make it work. I simply places a tiny (one eighth of an inch) piece of black electrical tape over the sensor, and now it's fine.
Thanks again.
Papamalo
Ive tried just about every combination of options for this setting but no matter what I cannot get edge lighting to work when the screen is off. It works perfectly fine when the screen is on, which seems pointless to me as, well, the screen is on. Is this a known issue?
Google has been useless as there are very few results specific to the Note 20.
aodNotify works flawlessly but I would rather not have to use a 3rd party app for a function I believe should work natively. Any input would be appreciated.
theskeptic said:
Ive tried just about every combination of options for this setting but no matter what I cannot get edge lighting to work when the screen is off. It works perfectly fine when the screen is on, which seems pointless to me as, well, the screen is on. Is this a known issue?
Google has been useless as there are very few results specific to the Note 20.
aodNotify works flawlessly but I would rather not have to use a 3rd party app for a function I believe should work natively. Any input would be appreciated.
Click to expand...
Click to collapse
I got a response from Samsung support. Screen needs to be face down for it to work with screen off.
gk1984 said:
Ingot a response from Samsung support. Screen needs to be face down for it to work with screen off.
Click to expand...
Click to collapse
Uh.
OasissisaO said:
Uh.
Click to expand...
Click to collapse
My thoughts too. I guess it's supposed to glow the table or something. But I don't see it with my case on
OK I have since noticed that if I recieve a normal sms I get a notification, with lighting. But it only lasts seconds. It isnt persistant as the old skool led would be. I.e. the led stayed lit till you dismissed the notification.
However, this has only happened with an sms. Gmail, Discord, Outlook ect even though sound and vibrate fork fine, no lighting.
Considering this is meant to be a flagship unit (yeah not the ultra but meh) youd have though something as basic as a notification being visible would be a no brainer.