While in a call the screen, doesnt turn off properly and some keys get pressed most of the time calls get disconnected for me..
any one else facing this issue.
I have tried on wolfreaks rom as well as MIUI by trip and i face the above issue.
however it works fine with the stock ROM.
most of the custom roms use sensor libs compiled from source. You can still have the proximity sensor in custom roms. You have to just replace the libs with SE's but they are slow and buggy because of the compatibility layer.
Related
Hey guys,
I know this thread already exists in this forum but has come to an end with no solution and since its kinda very important to sort this issue to be able to use my phone I thought ill start fresh for some input from the experts.
I have a Galaxy S2 I9100 rooted with a custom ROM(slim ICS 4.1 when the issue started) and it started randomly freezing when unlocking the screen and normal use .but since last week it wouldnt let me make or receive calls as the phone freezes and reboots 10-20 secs into the call..i updated to 4.2 with the hope of resolving this but tht didnt work..I have changed kernels and ROMS(resurrection, cm9 release build)..though the dialer did work for calls on resurrection ROM the proxomity sensor wouldnt work..
so i tried going back to stock sammy ICS (XXLPH) and then the dialer would work but again without the proximity sensor and the samsung tests also confirmed that the sensor wasnt registering...
am rooted now and back to slim 4.2(dont like the look of sammy) with siyah kernel 3.2.2...the dialer and proximity sensor don work..the rest of it is all fine..
Ive done all the wipes each time ive installed a new ROM...also done kernel wipes before installing Kernels..
I think its not a ROM/hardware problem but well it could be but hope to get it sorted through the normal techniques..I cant return my phone for repairs as it was in mint condition bot second hand in UK without warranty papers..
Any help would be highly appreciated..thanks
EDIT: It seems the proximity sensor is to blame for this problem as i found out through other posts..and also i can make and receive calls with the headset/headphones plugged (in which case i assume the phone doesnt try to activate the proximity sensor)..
For now i would like to know how to disable the proximity sensor on the phone..I have tried inserting the gsm.proximity.enable=false in the build.prop editor using the ROM Toolbox lite app n rebooted...but that din seem to work...is there any other way to do this??pls help
I am having EXACTLY the same issue as reported here and it's driving me mad. Did you ever find a fix for it?
proximity sensor and screen brightness sensor
3dawg said:
I am having EXACTLY the same issue as reported here and it's driving me mad. Did you ever find a fix for it?
Click to expand...
Click to collapse
I havent managed to find a solution as yet..it seems the proximity sensor and the screen brightness sensor(which are on the same PCB i think as per the unassembling video) have a hardware fault and might need repairing..
Some kernels i think maybe bypass using the proximity sensor if its not working..for now I am back to the SLIM 3.2 ICS rom..It doesnt switch off my screen on call and also no auto brightness adjustment but rest all works ok so am using it for now before i get the hardware repaired..
also the resurrection rom v 2.5.1 works fine in the same manner(havent tested many others..CM7 release build doesnt work)..or you can try that script in build.prop to disable the proximity sensor..
check how it goes..
How about CM9? Do these problems disappear on CM9? CM9 was working well for me but the home key and lock screen never worked. I applied all the common fixes to the keystr file but it never made a difference so I switched to slimics which worked. Then I discovered these annoying call screen off and waking problems :/
proximity sensor and screen brightness sensor
3dawg said:
How about CM9? Do these problems disappear on CM9? CM9 was working well for me but the home key and lock screen never worked. I applied all the common fixes to the keystr file but it never made a difference so I switched to slimics which worked. Then I discovered these annoying call screen off and waking problems :/
Click to expand...
Click to collapse
I tried checking with the testers for the Slim ROMS..regarding differences in kernel or anything for slim 3.2 and 4.2(3.2 works while 4.2 doesnt) but they couldn't tell me what was the exact problem or the differences that should affect in this case..I haven't tried a CM9 ROM yet but it could work..The kernel for the resurrection ROM is siyah kernel but when i tried that kernel with the slim 4.2 ROM that still didn't work for calls as the phone rebooted.
Have you managed to find a replacement cost for the proximity sensor? also does your screen brightness sensor work?
Every sensor in my phone has stopped working after updating to KitKat. Going in *#0*# and hitting Sensor reveals that they are indeed not working at all. I have tried factory restoring my phone, rooting it, and installing different roms and kernels but none of these have fixed it.
Does anyone have any ideas?
I have this issue with my S3, that is infuriating! Whenever I get a call and answer it, my screen turns off after a short while and during the call I can't turn it back on. The power and home buttons do nothing, and the proximity sensor isn't working either, so I can't turn off a call.
Anyone know how I can fix this? I have Lollipop, CyanogenMod 12.1 custom ROM installed.
Thank you for your time.
This bug partially exists in stock roms too. It's just magnified in custom roms.
You should be able to set it to keep the screen on during calls. It's the only way i know of.
I fixed this problem by opening up the phone, unplugging the proximity sensor, and throwing it in the bin. (the trash to you Americans)
Screen stays on during calls now, but I've not had problems with accidentally ending calls with my face, so I'm happy.
You also lose your front camera because it's part of the same tiny PCB. But I've never used the front camera on a phone in my life. So my solution is perfect for me, but maybe not for you.
The other option is a software fix. There's an app, or a method that you can do yourself to disable the proximity sensor, but I had problems with it, so did it my way.
Edit: I forgot to mention that the reason my proximity sensor wasn't working was because whoever had this phone before me did a screen repair and had half severed the ribbon cable for the proximity sensor by accident. Not just because of the bug that sometimes exists.
Sent from my GT-I9300 using Tapatalk
Proximity sensor problem. Manually calibrating it solved the issue for me.
http://forum.xda-developers.com/showthread.php?t=2569141
Go to that thread and follow instructions. The code for sensors might be different for s3, Google it.
sashankps said:
Proximity sensor problem. Manually calibrating it solved the issue for me.
http://forum.xda-developers.com/showthread.php?t=2569141
Go to that thread and follow instructions. The code for sensors might be different for s3, Google it.
Click to expand...
Click to collapse
Bah, that's the boring way to fix it.
(didn't work for me. maybe work for OP though)
Sent from my GT-I9300 using Tapatalk
I remember that I saw a MOD or xposed module to keep screen on during call.
It's better than throwing the sensor to the bin (trash ) .
after the latest update, to version 7.3.2.0(LHOMIDD), the proximity sensor's functionality has regressed (actually I do not remember the previous behaviour, can someone comment .
But now, while in a call, and when i place the handset close to the ear, the display switches off, but it does't automatically switch on , once i remove it from the ear.
This is quite irritating, is there a work around for the same?
Yes it happens to me too !! actually my device came with the latest version ! I did not update it !! May be a software issue !?
It's a known issue, hopefully it will be fixed with miui8. A workaround is to disable auto brightness
Well usually restarting fixes it.. go to settings about and click kernal version 5 times it will take u to service mode and try calibrating proximity sensor from there.. if this helped please hit the thnx button : )
Proximity sensor issue
Proximity sensor is not working properly on my Redmi Note 3 . I don't know when it stopped working, noticed it yesterday.
The phone is currently running on 7.5.3.0 MIUI. I am not able to calibrate as well it just displays Fail.
Can someone help?
Try this it'll help me to fix my all Sensors..
http://en.miui.com/forum.php?mod=viewthread&tid=312976&mobile=2
Sent from my Redmi Note 3 using Tapatalk
I have the same problem, even on custom roms I flashed miui and recalibrate the sensor and flashed RR rom there was no issue the issues started after I rebooted and again to temporary fix this issue I had to again reboot the phone and it solves and the problem comes back again after some time.....
@nexuspur, @techocentral, @kesavvel, @ coolant9 , there is one app i found in playstore which may fix this because it reloads the values on evry reboot try it....
https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset
Hi All
Any one facing proximity issues here , i saw so many peoples reported in mi forums that when we make a call screen blacks out when we moved to ears( Thats normal) and won't turn back again , so i have to wait the other side person to hangup the call or screen won't turn on power button does work that time, i think this only affects with Sensortek stk3x1x sensor, Redmi note 3 pro comes with two proximity sensors one is from Liteon and other is Sensortek.... Liteon sensors doesn't have this issue, for temporary fix "Wipe proximity area with a cloth or reboot fixes this and it comes back after sometime....( Calibrated but same it works for sometime) no idea wats causing this , issues there in Miui and CM roms....
I found sometimes a flip case with a magnet can cause issues like this when folded right back against the back of the phone, the screen won't come back on because it thinks the flip case is closed.
meangreenie said:
I found sometimes a flip case with a magnet can cause issues like this when folded right back against the back of the phone, the screen won't come back on because it thinks the flip case is closed.
Click to expand...
Click to collapse
yeah but i don't have flipcase, this sensor issues starts with those have "Sensortek Proximity Sensor" Liteon doesn't have issue i think....
Flash the rom again using mi flash tool u will find that yr issue will be solved
Or go to test mode amd calibrate the sensor... that's all
Fastboot flash persist persist.img from latest miui rom? I recently had a problem with sensors. The above cured all
@Hemphiz i think that method for dead sensors bro, this one working sometimes it doesn't mostly if we flash a new rom and use no issues but if we reboot the phone after sometime issue starts.... @ra.one i did that bro flashmiui and recalibrate sensor but that works for temporary please check which sensors you got from this app from playstore https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
if you got Liteon Sensors mostly no issues with proximity, if u got Sensortek u will be having issues or once u got issue it will come back..... im not sure why is causing that..... this is really very annoying bug.... Thousands of people reported in Mi forums about these proximity issues on various devices even on newly launched Redmi 3s/ prime may be they have all got "Sensortek Proximity Sensors".......
This is not a bug, You can disable Prevent Pocket dials under Settings-->Lock screen-->Prevent pocket dials...
I had this since last miui 6.9.9 flash.
Disabled prevent Pocket dials and All is working fine
Edit: for a few hours it was working.
Now its the same again. Phone blacked Out After a call and wont turn on, After a few seconds its coming back. As i said , since flashing new 6.9.9
Android2003 said:
This is not a bug, You can disable Prevent Pocket dials under Settings-->Lock screen-->Prevent pocket dials...
I had this since last miui 6.9.9 flash.
Disabled prevent Pocket dials and All is working fine
Edit: for a few hours it was working.
Now its the same again. Phone blacked Out After a call and wont turn on, After a few seconds its coming back. As i said , since flashing new 6.9.9
Click to expand...
Click to collapse
like i said it may be mostly an issue with Sensortek proximity, can u check which sensors u got from this app https://play.google.com/store/apps/d...droidsensorbox
I have sensortec.
But i think its Software related.
Its since last Update.
I calibrate the Sensor and the issue with calls is still there.
Sensor Works fine, test is okay.
Android2003 said:
I have sensortec.
But i think its Software related.
Its since last Update.
I calibrate the Sensor and the issue with calls is still there.
Sensor Works fine, test is okay.
Click to expand...
Click to collapse
Yes i think its software related but, one trick works clean flash the same rom and use it for a week without any reboot...... (DO CLEAN FLASH and Dont reboot the phone)
don't need to calibrate.... for me when i install new rom and use it for a week no issues , if i reboot the phone the issue starts after sometimes.... i don't knw wats causing it so many peoples with sensortek having issues and this bug is not resolved from Miui 7 to Now Miui 8 MM, the issue there in Custom roms im using RR rom i have issues....
Guys For those having issues Check which sensor you got from this app, if u have proximity issues while calling its mostly "Sensortek"
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
We need Permanent fix....
I also have exact same issue and i have sensortek sensor. But i can unlock the screen while on a call by pressing power button and then unlocking with fingerprint. Bit annoying
Sent from my Redmi Note 3 using Tapatalk
haree87 said:
I also have exact same issue and i have sensortek sensor. But i can unlock the screen while on a call by pressing power button and then unlocking with fingerprint. Bit annoying
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
So its confirmed its an issue with Sensortek Sensor, no Liteon users reported here, like i told flash the same rom which you are in (clean flash) and don't reboot phone for a week there will be no issues it works perfectly, if u reboot a phone once the issue starts again after sometime so after reboot something is going on no idea what....
i am using this app(for rooted users) on official RR and it works fine
https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset
anujyadava said:
i am using this app(for rooted users) on official RR and it works fine
https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset
Click to expand...
Click to collapse
even me used, but i don't think its properly working..... this issue starts only after a reboot, when u flash new roms and after boot dont reboot or power off the phone for a week, not needed any apps, proximity will work properly but once u rebooted issue starts....
But this app's settings load every time phone boots up.so it will work after every boot.
press thanks if I helped u in any way
anujyadava said:
But this app's settings load every time phone boots up.so it will work after every boot.
press thanks if I helped u in any way
Click to expand...
Click to collapse
yes this app i tested earlier, but after sometimes may be in a day or two it won't work....
Found another related issue with proximity , i think proximity is not working properly when there is not enough light around us something related with ambient light sensor i think ..... Eg: if we are in a dark room proximity won't work correctly turn on the light and try it works properly.... i think Xiaomi messed up with something with both sensors Liteon and Sensortek thats why Liteon users face Gyroscope lag in games in dark room and now i think may be the same reason why proximity not working properly in dark room....
hello. I have the BUG but my phone has sensortek version 1 (not 2)
When in a call the screen wont turn off when placing the phone at my ears. With whatsapp the bug wont happend.
I think this is a BUG related to sensor + phone app
A functional workarround is to dial, then press menu (putting the call at background) and then putting the call at foreground again. It works 100% of the time.
Any news? I have this annoying problem too!