Related
Title says it all. Its a very odd glitch. If i call someone, unless i quickly exit the phone app, my screen turns black but my call will continue. I cant turn the screen back on until the call is ended and i have to pull the battery. It happens regardless of what rom im on. Any help? Thanks in advance everyone
Sent from my SCH-I535 using Tapatalk 2
Have your cleaned your sensor in the front of your phone.
Sent from my SGS3 running Eclipse 2.1
No, what is/how do i do that?
Edit: I also have a ghost armor/ slick wrap sort of thing on the front of the phone. Is that the reason?
http://a248.e.akamai.net/origin-cdn...pfiles/photos/SW-GALS3-CFRED-3.jpg?1342082302
Sent from my SCH-I535 using Tapatalk 2
I would try removing that skin, it could be blocking the proximity sensor. I had the same problem on a galaxy nexus. I tried clearing phone app data, reboots, factory resets. In the end had to send it in on warranty because the sensor was bad.
Sent from my SCH-I535
Its weird though because the screen only turns off if the app i am running and xcan interact with is the phone application. If i use firefox or anything else while making the call everything is hunky dory.
Sent from my SCH-I535 using Tapatalk 2
GalaxyS3IsMeh said:
Its weird though because the screen only turns off if the app i am running and xcan interact with is the phone application. If i use firefox or anything else while making the call everything is hunky dory.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Try using an app that shows sensor readings. I like to use Elixir2 which has a sensor section. When viewing the proximity sensor readings, it should indicate "Far" when nothing is activating the sensor, and "Near" if you cover the sensor (with your finger or whatever). If it reads Near without you purposely tripping the sensor, your protector could be covering it or something else is wrong.
Sent from my SPH-D700 using xda app-developers app
bbelos said:
Try using an app that shows sensor readings. I like to use Elixir2 which has a sensor section. When viewing the proximity sensor readings, it should indicate "Far" when nothing is activating the sensor, and "Near" if you cover the sensor (with your finger or whatever). If it reads Near without you purposely tripping the sensor, your protector could be covering it or something else is wrong.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Yeah try this. Problem with my phone was intermittent, clearing the phone app data seemed to fix it but it always came back.
Just out of curiosity did you ever install an app called facebook contacts?
Sent from my SCH-I535
Not an app besides messenger and the actual fb app persay, but i did sync them to my contacts
Sent from my SCH-I535 using Tapatalk 2
The app was actually facebook contact sync. It's a third party app and I had originally thought it may of had something to do with the problem. That's why I asked.
I don't think it's a software problem because you said it happens on all of the roms you've tried. My nexus was stock and I did several factory resets, even waited for the jellybean update. Nothing I did was ever a permanent fix.
So I think either something is blocking the sensor i.e. dirt or the screen protector, or the sensor is bad.
Sent from my SCH-I535
My proximity sensor went bad after I replaced a screen lens by heating up and unglue technique. I turned it off in the phone app, and now it's fine, but for me it's very irritating that I have a high-end device which is somewhat broken, so I started researching what's wrong and how to fix.
It does work, I tested it by enabling hidden menu ( *#22745927 ) and then diagnostic mode ( *#0*# ) + click "Sensors". It does show proximity sensor at ADC 16 or more (I think it triggers at 15, so always on). When I bring the hand to the sensor, ADC goes to 100, so the sensor is somewhat working, but it always does sense something which isn't there, which is causing it to misfire. I have another good S3, and ADC value on it is 0 or 1 when nothing is in front of it, so my sensor could clearly be better.
I have no idea what ADC is, by the way
I have another broken front panel laying around, so I took the phone apart and replaced a sensor with the one from that panel. I did see a slight improvement, which is: ADB value went down to 11-12, so the sensor was not ALWAYS in triggered state, but clearly still no bueno.
What I'm going to do now is get a new item and try replacing with a new one. It's not overly expensive, like 10 bucks when shipped from china (search for "Front Facing Camera s3" on ebay). Should that be a success, I will post my results here.
I also am not sure if it is possible to recalibrate sensor to not trigger if ADC value is, say, below 20 and such. I would imagine there could be a configurable value. Somewhere this value of 15 is coming from, isn't it? So, idk, if some guru here is reading this post, maybe could advise where to go to configure it
Not to keep this thread alive or anything, but I gave my dad my old phone and he complained to me a few days later that the screen kept going off as well so I met him only to find out that he had the case on wrong and it was blocking the proximity sensor. He definitely is not cut out for a smart phone.
Sent from my SCH-I535 using xda app-developers app
galets said:
My proximity sensor went bad after I replaced a screen lens by heating up and unglue technique. I turned it off in the phone app, and now it's fine, but for me it's very irritating that I have a high-end device which is somewhat broken, so I started researching what's wrong and how to fix.
It does work, I tested it by enabling hidden menu ( *#22745927 ) and then diagnostic mode ( *#0*# ) + click "Sensors". It does show proximity sensor at ADC 16 or more (I think it triggers at 15, so always on). When I bring the hand to the sensor, ADC goes to 100, so the sensor is somewhat working, but it always does sense something which isn't there, which is causing it to misfire. I have another good S3, and ADC value on it is 0 or 1 when nothing is in front of it, so my sensor could clearly be better.
I have no idea what ADC is, by the way
I have another broken front panel laying around, so I took the phone apart and replaced a sensor with the one from that panel. I did see a slight improvement, which is: ADB value went down to 11-12, so the sensor was not ALWAYS in triggered state, but clearly still no bueno.
What I'm going to do now is get a new item and try replacing with a new one. It's not overly expensive, like 10 bucks when shipped from china (search for "Front Facing Camera s3" on ebay). Should that be a success, I will post my results here.
I also am not sure if it is possible to recalibrate sensor to not trigger if ADC value is, say, below 20 and such. I would imagine there could be a configurable value. Somewhere this value of 15 is coming from, isn't it? So, idk, if some guru here is reading this post, maybe could advise where to go to configure it
Click to expand...
Click to collapse
UPDATE: I bought a brand new sensor/camera block, and same issue there: minimum ADB is ~12. So, it's glass. It is possible that the sensor openings are either slightly shifted, or too dark.
Anyone knows how to configure the threshold value?
galets said:
UPDATE: I bought a brand new sensor/camera block, and same issue there: minimum ADB is ~12. So, it's glass. It is possible that the sensor openings are either slightly shifted, or too dark.
Anyone knows how to configure the threshold value?
Click to expand...
Click to collapse
You shouldnt have to go through all this man. You should get a new phone
Sent from my SCH-I535 using Tapatalk 2
Solved, yay!!!!!!
GalaxyS3IsMeh said:
You shouldnt have to go through all this man. You should get a new phone
Click to expand...
Click to collapse
Nope, I got it resolved!!!!!!!!
Here's how, with pictures: http://blog.galets.net/2013/01/fix-proximity-sensor-on-samsung-s-iii.html
Is anyone else having an issues when on a call to someone you take it away from your ear and look at your phone and the screen doesn't come back on. I have to hit the power button to make the screen wake up. I'm all stock (4.4.2) with unlocked bootloader. I m trying to see if this is a hardware problem where I need to RMA or software problem.
Mine works perfectly well. Are you sure you don't have anything that might be affecting the proximity sensor, like smudges or a screen protector?
Sent from my Nexus 5 using Tapatalk
No, I don't have any screen protector not any smudges. I saw similar issues on other phones and someone said to clear data and cache on the phone app so I don't know if that will work or not.
ProBird79 said:
Is anyone else having an issues when on a call to someone you take it away from your ear and look at your phone and the screen doesn't come back on. I have to hit the power button to make the screen wake up. I'm all stock (4.4.2) with unlocked bootloader. I m trying to see if this is a hardware problem where I need to RMA or software problem.
Click to expand...
Click to collapse
What time out do you have your screen set to? Sounds like it's simply locking after the designated time.
I've noticed the screen turning on and off occasionally when talking. Almost like the sensor isn't sure if I'm holding it to my head or not but then I do hold it away from my face.
I have the same issue...
I can't hang a call because the screen simply don't turn on when I remove my phone from the ear.
In add at this issue, seems like the proximity sensor turn off the backlight screen only.
When I finish a call, I found the clock screen opened, in my case the settings screen of advanced clock widget...
It's really annoying...
Sent from my Nexus 5 using XDA Premium 4 mobile app
Do you guys have a screen protector applied by any chance? Everyone had this issue with the nexus 4 because the sensor is really sensitive and picks the protector up, not letting it turn the screen on. Try removing a section of the protector where the sensor sits, this will fix your issue.
Surprisingly, I don't have this problem
Team Nexus 5 sucks. Underpowered battery for a 5inch 1080p screen that is non-removable. Weak generic antenna that drops signal. Worst speaker of any device on the market. Cheap plastic build.
dalton8 said:
Do you guys have a screen protector applied by any chance? Everyone had this issue with the nexus 4 because the sensor is really sensitive and picks the protector up, not letting it turn the screen on. Try removing a section of the protector where the sensor sits, this will fix your issue.
Click to expand...
Click to collapse
My phone is naked... No screen protector, no cover...
Sent from my Nexus 5 using XDA Premium 4 mobile app
bblzd said:
What time out do you have your screen set to? Sounds like it's simply locking after the designated time.
I've noticed the screen turning on and off occasionally when talking. Almost like the sensor isn't sure if I'm holding it to my head or not but then I do hold it away from my face.
Click to expand...
Click to collapse
I have it on 15 seconds. Shouldn't that feature be bypassed when a call is in progress so that the proximity sensor is usable. This is the first phone that I've had that has done this to me. On all others the proximity sensor stays live even after the predetermined sleep time.
After 15 seconds you're screen is simply turning off as you have set. Mine does so after 1 minute, which is my screen time out setting.
Sent from my Nexus 5 using Tapatalk
I have 30 minutes of inactivity...
The proximity sensor is broken...
Sent from my Nexus 5 using XDA Premium 4 mobile app
bblzd said:
After 15 seconds you're screen is simply turning off as you have set. Mine does so after 1 minute, which is my screen time out setting.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
During a call shouldn't the screen timeout be bypassed then go back to the default setting once the call has ended? That makes much more sense to me.
ProBird79 said:
During a call shouldn't the screen timeout be bypassed then go back to the default setting once the call has ended? That makes much more sense to me.
Click to expand...
Click to collapse
This seems to be the built in functionality of the phone and not a bug. I can't really say if one way is better then the other but I just turn the screen off during calls now.
This is the bug...
really annoying
same problem
ProBird79 said:
Is anyone else having an issues when on a call to someone you take it away from your ear and look at your phone and the screen doesn't come back on. I have to hit the power button to make the screen wake up. I'm all stock (4.4.2) with unlocked bootloader. I m trying to see if this is a hardware problem where I need to RMA or software problem.
Click to expand...
Click to collapse
Same problem here do any one have solution for this..
Anyone else having issue with this feature. I noticed my phone would wake up randomly in my pocket with this feature on.
I'm not sure exactly how it's even waking up as you still need to slide the bar across to unlock it. After i turned the feature off my phone wouldn't unlock itself anymore.
vtracer20 said:
Anyone else having issue with this feature. I noticed my phone would wake up randomly in my pocket with this feature on.
I'm not sure exactly how it's even waking up as you still need to slide the bar across to unlock it. After i turned the feature off my phone wouldn't unlock itself anymore.
Click to expand...
Click to collapse
You would need to see if this ever happens outside your pocket, without anyone touching it. If it doesn't, perhaps you can try touching the phone through the outside of your pocket; perhaps you're doing that without noticing it.
So after two charging cycles with it off I don't see any major difference. Its just like the LG G2 for me, very minimal impact on battery life.
vtracer20 said:
Anyone else having issue with this feature. I noticed my phone would wake up randomly in my pocket with this feature on.
I'm not sure exactly how it's even waking up as you still need to slide the bar across to unlock it. After i turned the feature off my phone wouldn't unlock itself anymore.
Click to expand...
Click to collapse
becos your phone screen face towards you when u put it in your pocket.
n while u walking, it keeps brushin against your skin in your pocket.
Sent from my D6653 using XDA Free mobile app
They should have used the proximity sensor to detect if it was in your pocket. Even manually covering the sensors up still allows the phone to be woke up.
Yeah, I had this issue too. Very annoying so so had to disable the feature. It's a shame because I liked unlocking it by tapping. Maybe they can fix it to not unlock if the proximity sensor is covered with a feature software update?
Sent from my D6633 using Tapatalk
That's probably what they *should* do. I never/don't have a problem with it on my M8.
I doubt it'd use much battery life to check if it's up against something before turning the screen on.
I have same problem with waking up in pocket. And since lollipop update the new slide up to unlock has caused issues with phone activating the flashlight and messing with wifi bluetooth nfc and other quick settings. Sad I have to disable as I love this feature.
Glad I installed gravity box and had proximity sensor option for that
Sent from my SGP621 using XDA Free mobile app
Running 5.0 on AT&T model. I have auto brightness turned on with baseline at dimmest setting which as most know is bright enough for most indoor situations. When I go outside into broad daylight, the brightness does not change. I can manually increase to full (and then the display is readable) but nothing happens on it's own.
Is this normal, am I missing something else? Defective light sensor?
EDIT: According to the following apps, I don't have a light sensor and my proximity sensor is failing. Can anyone confirm good data from them? -- Sensor Box for Android, Sensor Test, Phone Tester, Sensor Kinetics
If your screens turns off during calls that means the proximity sensor *is* functioning. I tried a sensor test and don't see fail anywhere.
Sent from my LG-H950
Ace42 said:
If your screens turns off during calls that means the proximity sensor *is* functioning. I tried a sensor test and don't see fail anywhere.
Sent from my LG-H950
Click to expand...
Click to collapse
Yea, my screen doesn't turn off during calls (unless I knock-knock on my head/ear). Also knock on constantly turns the screen on when I have the phone in my pocket (when proximity sensor should prevent it, right?) There isn't really a "failure" in those apps per se, I am just not getting any type of change in the data from proximity sensor and I am not even getting an option for light sensor test. More or less trying to verify I have a hardware issue before trying to get a replacement or warranty service. I've only had phone for 2 days.
Thanks for the feedback.
Neo42 said:
Yea, my screen doesn't turn off during calls (unless I knock-knock on my head/ear). Also knock on constantly turns the screen on when I have the phone in my pocket (when proximity sensor should prevent it, right?) There isn't really a "failure" in those apps per se, I am just not getting any type of change in the data from proximity sensor and I am not even getting an option for light sensor test. More or less trying to verify I have a hardware issue before trying to get a replacement or warranty service. I've only had phone for 2 days.
Thanks for the feedback.
Click to expand...
Click to collapse
Have you tried a factory reset already and is yours rooted?
Sent from my LG-H950
Ace42 said:
Have you tried a factory reset already and is yours rooted?
Sent from my LG-H950
Click to expand...
Click to collapse
Tried factory reset last night with no change. This phone has never been rooted (and I received it new)
This is from the sensor app. I would conclude yours is faulty if resets aren't fixing anything.
http://imgur.com/eudDXuc
http://imgur.com/xMS0hzS
Edit: Sorry about dark screen, using screen filtering to avoid burning my eyes.
Sent from my LG-H950
Ace42 said:
This is from the sensor app. I would conclude yours is faulty if resets aren't fixing anything.
http://imgur.com/eudDXuc
http://imgur.com/xMS0hzS
Edit: Sorry about dark screen, using screen filtering to avoid burning my eyes.
Sent from my LG-H950
Click to expand...
Click to collapse
Thanks so much for the screen grabs, this confirms my results are abnormal.
Does anyone noticed that the night mode is turned off on the lock screen untill we unlock it with our fingerprint. I also noticed this in some apps that require fingerprint that nightmode automatically turns off when device needs to scan fingerprint and turns back on after it's done
Sent from my GM1901 using Tapatalk
I noticed that fingerprint unlock doesn't respect the display calibration settings. Since my screen has a noticeable yellow tint without custom calibration, I had to disable it.
pragunjain said:
Does anyone noticed that the night mode is turned off on the lock screen untill we unlock it with our fingerprint. I also noticed this in some apps that require fingerprint that nightmode automatically turns off when device needs to scan fingerprint and turns back on after it's done
Sent from my GM1901 using Tapatalk
Click to expand...
Click to collapse
I can confirm this, noticed the same.
Tagilso said:
I can confirm this, noticed the same.
Click to expand...
Click to collapse
I think it has something to do with light based fp sensor it is not the case in Samsung s10
Sent from my GM1901 using Tapatalk