Related
OK i try to use on my ST15i Spartan Rom V2.0.5, but it have the same bug like stock ROM... proximity sensor don't work...
so i need a little help.. i can't find fix for that (so if this is on xda pls tell me)
or can i somehow install alternative call dialog something like on CM7 or MIUI or anything but that don't have corner interface like stock rom
THNX )
I don't know in what way your prox sensor doesn't work, but here are some links if it can help you....
Proximity Sensor Fix for ST15i:http://www.mediafire.com/?11vfrj1ldx2b8x2 USE ONLY IF YOU HAVE A BLACK SCREEN ISSUE AFTER CALL
If you still face the same problem with the black screen after call, even after flashing the avove zips, here are the zips that will solve your problem for sure:
Ultimate Proximity Sensor Fix for ST15i:http://www.mediafire.com/?d74ijd4p1eh524b
^^
This is taken from Hybrom thread.
Also take a look at this:
http://forum.xda-developers.com/showthread.php?t=1626611
EDIT: I'm also using Spartan on my mini, but I have no such issue
The prox sensor works flawlessly on my phone.
iONEx said:
I don't know in what way your prox sensor doesn't work, but here are some links if it can help you....
Proximity Sensor Fix for ST15i:http://www.mediafire.com/?11vfrj1ldx2b8x2 USE ONLY IF YOU HAVE A BLACK SCREEN ISSUE AFTER CALL
If you still face the same problem with the black screen after call, even after flashing the avove zips, here are the zips that will solve your problem for sure:
Ultimate Proximity Sensor Fix for ST15i:http://www.mediafire.com/?d74ijd4p1eh524b
^^
This is taken from Hybrom thread.
Also take a look at this:
http://forum.xda-developers.com/showthread.php?t=1626611
EDIT: I'm also using Spartan on my mini, but I have no such issue
The prox sensor works flawlessly on my phone.
Click to expand...
Click to collapse
thnx for r i have this problem on stock rom, and on spartan rom, but not on ICS roms and CM rom
Problem is that my screen still work (it is not black) when phone is close to my face... so i can easily touch with my face buttons for mute mic, speakerphone etc...
Bruno_AFK said:
thnx for r i have this problem on stock rom, and on spartan rom, but not on ICS roms and CM rom
Problem is that my screen still work (it is not black) when phone is close to my face... so i can easily touch with my face buttons for mute mic, speakerphone etc...
Click to expand...
Click to collapse
That means, try this fix. It is meant for any GB-based ROMs.
Someguyfromhell said:
That means, try this fix. It is meant for any GB-based ROMs.
Click to expand...
Click to collapse
he say this
"USE ONLY IF YOU HAVE A BLACK SCREEN ISSUE AFTER CALL" I don't have that problem, so i don't need that kind of fix
Bruno_AFK said:
he say this
"USE ONLY IF YOU HAVE A BLACK SCREEN ISSUE AFTER CALL" I don't have that problem, so i don't need that kind of fix
Click to expand...
Click to collapse
The second fix, also in his post...
Sent from my Xperia Live using xda premium.
Hi all!
I've been using this great ROM by MaxWorks, however, after updating to the latest version 2.8.31 I've had a single issue.
The issue occurs when I receive a call, and the phone is in my pocket or covered by something (covering the proximity sensor); the ringtone does stutter until I get the phone out of my pocket or get the something off the proximity sensor, and the screen lights on, then the ringtone sounds normally without stuttering.
I've tried wiping the system, the cache, dalvik cache, and flashing Super Stock Kernel and Suave's Kernel then reinstalling the ROM after each kernel flash.
There's also another issue with the proximity sensor that happens sometimes while using the phone. The issue occurs when I'm trying to slide down the status bar, the screen turns off because my finger gets in the way of the proximity sensor, and then turns on again when my finger gets out of the proximity sensor's way.
Any suggestions to resolve this issue, I'd be happy.
Thanks all!
Me also facing the same problem sometimes... 'm using MIUIv4 (ICS) EN 2.8.31 NeoV/Neo by ZduneX25...!
Hope they will fix it soooon..!
Sorry for the misuse of my wording
It's the Proximity Sensor which locks the screen and causes these problems, not the light sensor
I'll try to roll back and reinstall the 2.8.24 until 2.9.7 gets released today
I had done a clean install of 2.8.24 and have tested the proximity sensor, and there had been no issues. Then I've done another clean install of 2.8.31, and the stuttering ringtones are almost gone, but I'm quite unsure yet. Wanna test it for a longer time. However, the proximity sensor issue when gets hovered by my finger isn't gone yet.
So I think it's a generic bug in MIUIv4 v2.8.31, and neither belongs to Max nor Zdune's ports, as you can see in the following quote.
Hey guys,
I'm facing erratic proximity sensor behaviour in the latest 2.8.31 rom.
When i wake my phone using home button, the proximity sensor kicks in for 3 to 5 seconds. When i hocer my hand near the sensor, the screen switches off and comes back when i move it away. Anyone facing this issue?
Click to expand...
Click to collapse
Source: Miuidroid Forum
Posted by: Adithya
Thread title: Samsung Galaxy SII - Bugs in the latest rom (2.8.17)
Also many users have been complaining about the same issue inside this thread
and the developer, sandy, has uploaded some sensors lib fixes to resolve the issue
It seems the issues are totally resolved and gone in the 2.9.7 release.
Unfortunately, there is an issue in MaxWorks's Rom as the ringtone does not get repeated. It is played once only, and I tried Zdune's, and it's not there.
Therefore, I PMed Max as I can't reply into his thread, and I hope he'd get it resolved sooner.
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...)
Hi guys,
i am on CM11 and the screenprotector is messing with the proximity sensor, i put it on to circumvent the ghosting of the digitizer, *#*#7378423#*#* menu is not working as the service menu is not on CM11.
I've tried looking for a solution but apparantly there is no apparant solution for this unfortunately, can somebody help with a manual calibration perhaps?
maybe someone knows the exact location of the proximity sensor so i can cut the screenprotector away from there.
ashwin1 said:
Hi guys,
i am on CM11 and the screenprotector is messing with the proximity sensor, i put it on to circumvent the ghosting of the digitizer, *#*#7378423#*#* menu is not working as the service menu is not on CM11.
I've tried looking for a solution but apparantly there is no apparant solution for this unfortunately, can somebody help with a manual calibration perhaps?
maybe someone knows the exact location of the proximity sensor so i can cut the screenprotector away from there.
Click to expand...
Click to collapse
you can flash a FTF (cant remember if 4.4.4 / .108 has proximity sensor calibration), calibrate the proximity sensor, then go bacck to CM, that seemed to fix the issues I was having
blueether said:
you can flash a FTF (cant remember if 4.4.4 / .108 has proximity sensor calibration), calibrate the proximity sensor, then go bacck to CM, that seemed to fix the issues I was having
Click to expand...
Click to collapse
aahhh, that's just something i want to avoid, maybe i can extract the servicemenu.apk from a OEM rom and have that installed on the CM11, will look into this next week and will keep this thread updated.
ashwin1 said:
aahhh, that's just something i want to avoid, maybe i can extract the servicemenu.apk from a OEM rom and have that installed on the CM11, will look into this next week and will keep this thread updated.
Click to expand...
Click to collapse
Or you could cut the SP, the sensor is right beside the front camera