I am having a problem with my sensor not re-activating the screen when I move away during a call, and when I push any button except to end the call, the phone just disregards it. Is there an app or something similar to reactivate the screen with a button push, or is there something I'm missing?
can anyone help?
eh fore the moment I'm preparing to get sleep, and navigate/search with my device isn't so easy.
but if it can help you take a look on the Q&A thread if my memory is good I thought I have see a thread with this situation/ solution.
kurt-willems said:
eh fore the moment I'm preparing to get sleep, and navigate/search with my device isn't so easy.
but if it can help you take a look on the Q&A thread if my memory is good I thought I have see a thread with this situation/ solution.
Click to expand...
Click to collapse
Alright, thanks dude
Have you installed GPRS_1_Minute_Auto_Disconnect?
This app disabled the proximity sensor on my HD2
Hammett11 said:
I am having a problem with my sensor not re-activating the screen when I move away during a call, and when I push any button except to end the call, the phone just disregards it. Is there an app or something similar to reactivate the screen with a button push, or is there something I'm missing?
Click to expand...
Click to collapse
Hi !
I'm facing the same problem since I upgraded to ROM 3.14.406.2 (french ROM)
Everything was fine before this upgrade.
What I've found is that while calling, when you put your phone away from your face and that the screen is off, if you put a light near the sensor, the screen turns on again.
I think HTC messed up while configuring the proximity sensor values in this ROM...
kinda annoying indeed !
Regards
papagon said:
Hi !
I'm facing the same problem since I upgraded to ROM 3.14.406.2 (french ROM)
Everything was fine before this upgrade.
What I've found is that while calling, when you put your phone away from your face and that the screen is off, if you put a light near the sensor, the screen turns on again.
I think HTC messed up while configuring the proximity sensor values in this ROM...
kinda annoying indeed !
Regards
Click to expand...
Click to collapse
Just install CHT 2.0 (and CHTE and CHTS ). There you´ll find a lot of toggle switches. One of them is for activating/deactivating the proximity sensor and another one is for relighting the sensor. That helped my HD2
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.
"[ROM] MiniCM7-2.1.7 [28/12/11]Gingerbread 2.3.7/CM7.2" Addition / Keyboard lights
Hi,
Happy new year to all of you & Special thanks to nobodyAtall for this great ROM.
Since I can't post to his thread directly I have to post here. I followed the thread carefully and have an addition to the keyboard backlight problem:
The settings in the phone do indeed work. However, the sensor in my Mini Pro sometimes has "-1" as value which is not covered by the settings with start with "0".
The keyboard lights then do not work since this sensor value is not covered. Setting the phone to sleep and sliding out the keyboard makes the sensor working again most of the time.
I am trying to figure out when exactly this happens so you maybe able to find a solution to this.
I think some of those that have the keyboard backlight problem maybe facing the partial "sensor -1" problem which I have.
Maybe this post could be moved to the correct thread.
Btw, I can't find the "Thanks" button. Where is it?
It seems to me that this always just happens when awakening the phone in an area where no light is shone into the sensor.
No matter how i try it, after waking up the phone, the light sensor only starts working after light is shone into it
One time, I even managed to get it stuck at -1 with the kb lights on and not turning off anymore too btw
aand the thanks button should be next to the buttons for quote, multi-quote and edit btw
Hi Carpe Dimi,
thanks for replying. If I understand you correctly this is some sort of bug in this ROM which needs to be fixed. Or is this a problem in the kernel or the hardware? Something does not seem to read out the sensor values correctly.
Its somehow paradox that light needs to be available to get light ...
looks like i have to carry a torch light to light up the sensor
fun apart, i too have no lights on the keyboard. so just using like an ordinary X10i mini phone.
Maybe this is usefull for someone: you can also shine an ir light like your remote control into the sensor to make it work again.
Sent from my U20i using xda premium
Why don't you guys just use D4's Kfix?
Sent from my phone
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
I’m having a serious issue with my Samsung Galaxy S2 GT-i9100.
I was on stock 4.1.2 (rooted via Siyah kernel v6 b5) probably when the problem occurred. The problem is that whenever I make call, the proximity sensor light up and it make the screen black out even if I’m not holding the phone to my ear or so. It’s just lying on the bed. The screen doesn’t light up and I can’t hang up the call. I just can’t do anything till the other person hang up. Pressing home button and Power button just don’t work to make the screen go on.
P.S: The proximity sensor turns on when I first made a call after a reboot and it didn’t gooff till I restart even it stays on after the call.
I have tried formatting internal sd card and also wipe data/factory reset, clear dalvik cache, clear cache partition, flashed stock rom 4.1.2, flashed nexus 2.0 and even downgraded to official 2.3.5 but it didn’t worked out. I even tried to restore the EFS folder from my old backup but still it didn’t helped.
Here in the screenshot you can see the proximity sensor is active, on the home screen even no call is being made.
Please does anyone know what the issue is because it was working before?
Anyone?
I think you should replace the sensor....it's just 3-4 dollars,and it comes with the front camera and light sensor(AIO)
GamingDj said:
I think you should replace the sensor....it's just 3-4 dollars,and it comes with the front camera and light sensor(AIO)
Click to expand...
Click to collapse
Can you do me a favour please?
Can you please press *#0*# on your dialer . then there Press the "Sensor" and then tell me the value of "PROXIMITY" before covering the proximity sensor with your finger and also after covering the proximity sensor with your finger.
'0' when uncovered
'1' when covered
Sent from my GT-I9082 using xda premium
The jOkEr! said:
'0' when uncovered
'1' when covered
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse
I'm getting "9-10" when uncovered
and "144-147" when covered.
Probably a Proxmity Sensor issue? :/
GamingDj said:
I think you should replace the sensor....it's just 3-4 dollars,and it comes with the front camera and light sensor(AIO)
Click to expand...
Click to collapse
Can you provide me a online purchase link for it? Please?
Here is an eBay search for the sensor.Select one you want,just be sure it's for I9100.Search one which ships to your country.:good:
Can you do me a favour please? Can you please press *#0*# on your dialer . then there
i have same problem.
"""Can you do me a favour please? Can you please press *#0*# on your dialer . then there"""
tap on light sensor struck and say "unfortunately, com.sec.android.app.lcdtest has stooped"
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!
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...)