Hi all,
Been struggling with this for the last days.
I have a Samsung Galaxy S3, Rooted, with CM11 for i9300 (nightly).
Everything seems to work properly except for the Proximity Sensor.
When I make calls the screen will go black and won't recover.
Proximity Sensor Finder always show 0.0 cm as if objects are constantly near.
These are the things I tried so far, with no luck:
1. Opening the device and cleaning the sensor.
2. Creating a bolder separation between the two receptors of the sensor.
3. Running Auto Calibration
4. Running Manual Calibration returns:
Code:
$ cat state #finger on the sensor to test if the sensor is working properly
0
$ cat state #blank value
0
Code:
$ cat prox_cal
0,15
Which means my 'new' calibration adds up to '0' which makes no sense (is it?)
What else would you suggest? This is really frustrating
Any ideas???
Please give me something
I am also having this issue on my girlfriends T-Mobile s3 (d2lte i think) on CM11 M7-M9. Just now starting to investigate, but I will report back here if I find anything
---------- Post added at 09:42 AM ---------- Previous post was at 08:47 AM ----------
This app fixed it for me (while others that claimed they should did not). Check it out:
https://play.google.com/store/apps/details?id=it.iiizio.screenwakeup&hl=en
Thanks but...
thefanum said:
I am also having this issue on my girlfriends T-Mobile s3 (d2lte i think) on CM11 M7-M9. Just now starting to investigate, but I will report back here if I find anything
---------- Post added at 09:42 AM ---------- Previous post was at 08:47 AM ----------
This app fixed it for me (while others that claimed they should did not). Check it out:
Click to expand...
Click to collapse
Thanks but this is not really a solution.
I don't want to use an app, I want to fix the proximity sensor issue.
Any other ideas?
The point is, it was not a problem with the proximity sensor. It was a bug. Try the app, if it works, you proximity sensor is fine.
Xolusia said:
Thanks but this is not really a solution.
I don't want to use an app, I want to fix the proximity sensor issue.
Any other ideas?
Click to expand...
Click to collapse
What settings?
thefanum said:
The point is, it was not a problem with the proximity sensor. It was a bug. Try the app, if it works, you proximity sensor is fine.
Click to expand...
Click to collapse
What settings in the app did you use to test it?
Enable screen wake up, restart on startup, auto lock screen, auto wake up, 2 second time out and status bar icon.
Sent from my SM-N900T using XDA Free mobile app
Update...
I tried flashing my CWM again and downgrading the CM rom to a stable version (10.2).
Still same problem.
What else can I do? The previous user of this phone said there was no problem (he used the stock rom).
I don't want to install a third party app to "fix" it.
I need a decent solution and a functioning proximity sensor.
You can install the app temporarily, to find out if it is a hardware problem or not. No one can help you until you fully diagnose it and find the source of the problem.
Sent from my SM-N900T using XDA Free mobile app
Solved it:
http://forum.xda-developers.com/galaxy-s3/help/fixed-proximity-sensor-manual-t2930556
Related
Am I the only one having problems with the Proximity Sensor on the Atrix? I can't seem to get it to kick in when on a call. I have already dial-toned a couple of people when talking on the phone. I have tried covering up the sensor by placing the palm of my hand over the to 1/2 of the phone and it never kicks in.
Can someone verify for me that it does work and not some software bug.
Thanks,
Ed
Did you ever find the problem? My proximity sensor has stopped working also.
i am having an issue with mine too. at first i thought it was an issue with the screen not coming back on, but now i realize that the proximity sensor is not turning off the screen at all and my screen is just turning off when the screen timeout value is reached.
my phone is rooted, i have used titanium backup to freeze some of the apps associated with blur, and i have installed the hack to use webtop mode. can others that have this issue confirm if they are running stock or modified software?
***EDIT***
http://forum.xda-developers.com/showthread.php?p=12035170#post12035170
Any of you guys ever find a fix for this? I just noticed that mine is not working anymore either. It's rooted using aRoot but it was working for a while and now it doesn't anymore. I have another couple of days to exchange in store if I want to if it's a phone issue.
Crap, I'm having the same issue now too -- was working fine since I had it, but this occured just today, Day-2 of using 1.5.7 .... wonder if it's related ...
Crap, I'm having the same issue now too -- was working fine since I had it, but this occured just today, Day-2 of using 1.5.7 .... wonder if it's related ...
Reboot seems to fix this -- but annoying >_<
Is anyone that is having these issues using bluetooth? I have isolated mine to bluetooth and sent an issue report to Motorola.
same problem here but not using bluetooth
My wife's Atrix does the same thing. "dials or hangs up while in a call". She does not own a bluetooth headset and I have only connected a Motorola 305 one time to it. Reboot fixes the problem. Reboot seems to take forever when compared to my Dell Streak.
Ed Venture said:
Am I the only one having problems with the Proximity Sensor on the Atrix? I can't seem to get it to kick in when on a call. I have already dial-toned a couple of people when talking on the phone. I have tried covering up the sensor by placing the palm of my hand over the to 1/2 of the phone and it never kicks in.
Can someone verify for me that it does work and not some software bug.
Thanks,
Ed
Click to expand...
Click to collapse
Had the problem with mine when I installed a different launcher had to delete it and restart the phone now it works ....for me anyways
Sent from my MB860 using XDA App
Hi I believe I traced the problem with the proximity sensor not working to Handcent SMS. On two separate Atrixes, as soon as I uninstalled Handcent and rebooted the phone the problem went away and stayed away. I have since installed GoSMS and now it happens just sometimes (usually after I install a new app) but a reboot after installing an app ususlly fixes it.
My Phone has a standard Telstra (Australia ROM) and is not unlocked or modified in any way.
Ed Venture said:
Am I the only one having problems with the Proximity Sensor on the Atrix? I can't seem to get it to kick in when on a call. I have already dial-toned a couple of people when talking on the phone. I have tried covering up the sensor by placing the palm of my hand over the to 1/2 of the phone and it never kicks in.
Can someone verify for me that it does work and not some software bug.
Thanks,
Ed
Click to expand...
Click to collapse
hi, you can try this
open /system/build.prop and add this
persist.mot.proximity.touch=1
reboot phone
Seem that i have this problem on my atrix,when i calling someone,the screen turn off immediately and the led on proximity sensor just keep turn on when i stop calling,i cant imagine this atrix have a lot a lot hardware problem
Sent from my MB860 using Tapatalk 2
If you are using unlocked bootloader or if u have unlocked the dim using a code then u will have to disable the In Pocket detection and then try sounds crazy but worked for me.
Sent from my MB860 using xda premium
ranjithkumar1201 said:
If you are using unlocked bootloader or if u have unlocked the dim using a code then u will have to disable the In Pocket detection and then try sounds crazy but worked for me.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
care to share how?
Similar issue
Just installed latest stable build onto my Atrix 4G, everything seemed fine last night, although I was using phone with bluetooth, this morning get a call, answer, screen goes dark, red proximity light comes on, and I can hear no sound, [later on the caller said he could hear me fine].
Phone would not wake up right off, and when it did it I still could not hear caller.
Been screwing around with settings all morning to no avail, discovered that the phone will only work with bluetooth device connected. without bluetooth the device goes dark, cannot wake up, have to hard reboot, with bluetooth and volume button awaken enabled, it performs normally, so possible connection to issues in post with proximity but with a bluetooth twist...
12as2005 said:
hi, you can try this
open /system/build.prop and add this
persist.mot.proximity.touch=1
reboot phone
Click to expand...
Click to collapse
Did that...... Does nothing much....
12as2005 said:
hi, you can try this
open /system/build.prop and add this
persist.mot.proximity.touch=1
reboot phone
Click to expand...
Click to collapse
Worked for me!!!
Stock rom with, root, atrix tweaks installed.
Thank's a lot!!!
Hey guys,
it seems my proximity sensor stopped working. I noticed that my display doesn't turn off anymore when I put the phone to my ear.
I already installed phone tester and in "Sensors" it shows for proximity sensor only "waiting for data ...".
Does this mean I got a hardware defect or is there any other way to reinitialize the sensor somehow?
thanks,
boba
boba23 said:
Hey guys,
it seems my proximity sensor stopped working. I noticed that my display doesn't turn off anymore when I put the phone to my ear.
I already installed phone tester and in "Sensors" it shows for proximity sensor only "waiting for data ...".
Does this mean I got a hardware defect or is there any other way to reinitialize the sensor somehow?
thanks,
boba
Click to expand...
Click to collapse
Have you tried any other fws?
Dial *#0*# and select sensor option.. Hide the proximity sensor with hand,.see if there is any response..? Do this relaxly and report back...
Sent from my GT-I9100 using XDA Premium App
boba23 said:
Hey,
no there isn't any response on the prox sensor values, they stay at "null ADC: 0(0,0,0)
I am on stock XXKK5 right now, no modifications at all. Before I was on CM7 where I first noticed the sensor is not working.
Anything else I could try before returning the phone for repair?
boba
Click to expand...
Click to collapse
Try any other stock firmware...
Sent from my GT-I9100 using XDA Premium App
boba23 said:
Hey,
no there isn't any response on the prox sensor values, they stay at "null ADC: 0(0,0,0)
I am on stock XXKK5 right now, no modifications at all. Before I was on CM7 where I first noticed the sensor is not working.
Anything else I could try before returning the phone for repair?
boba
Click to expand...
Click to collapse
Null is actually a default value , meaning that no object is in the radius of the proximity sensor. If you put a finger over the sensor the screen should turn green and the value will be over ~200. Try that.
also go to settings -> call -> Turn on proximity sensor and see if its ticked. if its not , tick it
boba23 said:
I tried all of that ... but I can't get any reaction of the proximity sensor, no matter what I do :-( I guess I'll return the phone for repair tomorrow, running out of options here ....
boba
Click to expand...
Click to collapse
I've seen threads around the web with people complaining about the sensor too. Some guy said he took it to repair , and they changed the entire front panel including the sensors. I guess these things do happen sometimes, bad luck bro. Hope it goes well
Hey , Just now i got into your thread via Google ... I am also facing the same proximity sensor issue. Could you please tell me what u did? Gave it for service ?? How is your phone now ??? Waiting for answer.. thanks...
Hello every one !
I'm french so sorry for my bas english
I encounter a problem with the proximity sensor on my phone (Mozart7).
In fact, when I issue or receives a call the screen goes black and I can not hang up or to get to the options.
Is there an application that would disable the proximity sensor?
I noticed that when you plug a headset during a call the screen turns on, ignoring the information from the sensor
If it does not exist, could someone tell me the registry keys to change to solve my problem?
Thank you in advance and good day
I've got the exact same problem, am wonderin if it might be a hardware problem.
Anyone got any advice or fixes please?
thanks.
------------
HTC Mozart WM7
UK Orange stock ROM
---------- Post added at 05:43 PM ---------- Previous post was at 05:11 PM ----------
...tried a hard reset, still behaves the same.
I had the same Issue with my Mozart 7 and im not 100% sure what fixed the problem, but it was either the removing of my protective foil, or it was flashing a new Rom. I did both in a short time and after it it worked... Have a try and good luck
K2Death said:
Hello every one !
I'm french so sorry for my bas english
I encounter a problem with the proximity sensor on my phone (Mozart7).
In fact, when I issue or receives a call the screen goes black and I can not hang up or to get to the options.
Is there an application that would disable the proximity sensor?
I noticed that when you plug a headset during a call the screen turns on, ignoring the information from the sensor
If it does not exist, could someone tell me the registry keys to change to solve my problem?
Thank you in advance and good day
Click to expand...
Click to collapse
Hello
the front of Proximity sensor may be dirty! so you should clean that from internal side of it ! so try it!
I had this problem and it was cleared!!
msadeghz said:
Hello
the front of Proximity sensor may be dirty! so you should clean that from internal side of it ! so try it!
I had this problem and it was cleared!!
Click to expand...
Click to collapse
Thanks, any clues on how I can get to the inside of it?
I tried a ROM re-flash and no difference so think it must be hardware related, but I can't see any easy eway to get to it.
So, I've re-flashed the ROM, stripped the phone and cleaned the sensor and window - still the screen turns off when I'm in a call.
Could there be a registry setting to resolve this? Any ideas?
Thanks
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 ) .
Hi, I got my Mi 3 this week. I noticed some weird behavior from my magnetometer and Accelerometer, wondering if anybody else is experiencing the same. After a day of use, sensors go haywire and suddenly stop reporting data. Can't use compass and my auto rotate stops working. I tried different apps to see if it's a global problem or just a not compatible app, so far when sensors go blank, the effect is global. Even the Mi self test is not reading anything from the sensors. Pedometer is on the other hand operational tho.
Things come back to normal after a restart. I suspect it must be a software bug maybe?
sherlock.holmes said:
Hi, I got my Mi 3 this week. I noticed some weird behavior from my magnetometer and Accelerometer, wondering if anybody else is experiencing the same. After a day of use, sensors go haywire and suddenly stop reporting data. Can't use compass and my auto rotate stops working. I tried different apps to see if it's a global problem or just a not compatible app, so far when sensors go blank, the effect is global. Even the Mi self test is not reading anything from the sensors. Pedometer is on the other hand operational tho.
Click to expand...
Click to collapse
My sensors are working but they are wrongly calibrated :/ and pedometer isn't working! I thought the pedometer was disactivated by default...
greenpays said:
My sensors are working but they are wrongly calibrated :/ and pedometer isn't working! I thought the pedometer was disactivated by default...
Click to expand...
Click to collapse
Dial *#*#6484#*#* it's the built-in test. U can recalibrate your accelerometer there and also test the device. Use power button to exit. And for +-45 test's of the accelerometer tilt your device on it's corners.
sherlock.holmes said:
Dial *#*#6484#*#* it's the built-in test. U can recalibrate your accelerometer there and also test the device. Use power button to exit. And for +-45 test's of the accelerometer tilt your device on it's corners.
Click to expand...
Click to collapse
Thanks for the tip it works perfectly!
By the way, you are using European firmware or Global, because for me the pedometer isn't counting the steps :/
greenpays said:
Thanks for the tip it works perfectly!
By the way, you are using European firmware or Global, because for me the pedometer isn't counting the steps :/
Click to expand...
Click to collapse
I'm glad to hear it worked for you. My pedometer comes and goes... Not reliable unfortunately. btw how can I check my ROM region? Got the October patch, It doesn't solve the bug...
I also have problems with my vibrator. It doesn't react to short vibrations (that much I can make out of it).
sherlock.holmes said:
I'm glad to hear it worked for you. My pedometer comes and goes... Not reliable unfortunately. btw how can I check my ROM region? Got the October patch, It doesn't solve the bug...
I also have problems with my vibrator. It doesn't react to short vibrations (that much I can make out of it).
Click to expand...
Click to collapse
Well I seem to have the global version. MIXM
I hope they get problems solved fast.
If anybody else with the device is reading this post, can you please check your sensors with an appropriate app and see if yours is also malfunctioning randomly?
I had this problem, but I just restarted the device and everything came back normal
braulio_holtz said:
I had this problem, but I just restarted the device and everything came back normal
Click to expand...
Click to collapse
Yes! It goes away with restarting (and sometimes doesn't!!!)
But it's just a temporary fix, in matter of hours, you r back to the square one.
sherlock.holmes said:
I'm glad to hear it worked for you. My pedometer comes and goes... Not reliable unfortunately. btw how can I check my ROM region? Got the October patch, It doesn't solve the bug...
I also have problems with my vibrator. It doesn't react to short vibrations (that much I can make out of it).
Click to expand...
Click to collapse
Go to Accessibility settings and turn on Touch Vibration. Keeping it off also hinders the in call volume function. Hope it helps
Arkapravoarka said:
Go to Accessibility settings and turn on Touch Vibration. Keeping it off also hinders the in call volume function. Hope it helps
Click to expand...
Click to collapse
Well yeah, it did work actually. But the thing is, I don't like to have the touch vibrations on always, I just want it to work with G-board and some other apps that use short vibrations as a feedback...
It's like the touch vibrations setting, controls everything lol.
It's definitely a bug they have to get fixed.
So it turns out the sensor problem that I reported is being caused by the G-cam port I had installed. The solution is to close the app (in the multitasking menu !?) Whenever you are done using it.
Flash the stock rom again and your problem will be solved for sure, also faced the same issue.
I have same issue and flash stock rom but still not working how can i fix it ?
I also have a problem with compass apps. north and south are correct shown, west and east are not correct.
Stefan_1 said:
I also have a problem with compass apps. north and south are correct shown, west and east are not correct.
Click to expand...
Click to collapse
I use this solution and it worked.
https://forum.xda-developers.com/showpost.php?p=82161897&postcount=4
My Mi A3 has just got an system update of android 10. Just after that, my camera isn't working. Please help me out of this problem.
Chaitanya123 said:
My Mi A3 has just got an system update of android 10. Just after that, my camera isn't working. Please help me out of this problem.
Click to expand...
Click to collapse
Did you try wiping data and cache for camera app?