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
So I am studying and taking notes on papyrus when all of a sudden screen goes black.
And it's not like it went to sleep mode because if I hit the power button it makes a sound but does not turn the screen back on.
When I click the second time it turns the screen on, as if I turned the screen off and on while it was black screen.
Has anyone experienced this?
So far I have had this only happen while taking notes on Papyrus, I have 30min set to turn of screen and this happens during my note taking...
Also I am using GMOD SPen, to turns of capacitive sensor. -Maybe it could be the problem?
The only input I can provide is that under the same circumstances as you, ( GMD to turn off capacitive touch) and using papyrus, I had no such issues.
Something I feel I should share though, is that the spen latency is greatly decreased in papyrus on a custom ROM such as baked#8 but you lose the Samsung features.
Just my 0.02
Regards
Jack
What about Android Revolution HD 5.1?
I was having serious latency problems earlier but that was due to 2d gpu acceleration.
Once I disabled that I still see some lag, but it's much more tolerable.
Should I try the rom you mentioned, is the latency really that good?
So far, the least latency I've seen was with software called "write" although it has a lot of useful features Papyrus is still my favorite.
Sent from my GT-N8000 using Tapatalk HD
Well, if you are comfortable with taking a cwm/twrp backup the you can try it for yourself
I noticed a great deal of difference personally.
Regards
Jack
I've actually had the exact same issue, although I use LectureNotes: I can be taking notes from anywhere between 2 minutes and 30 when the screen suddenly goes dark (but not off). Pressing the power button turns the screen off and another power button press brings you back to you note-taking app.
I thought this was an issue with LectureNotes' auto-saving feature, but after seeing this thread, I'm thinking it's system-related (software or hardware).
Anyone have any insights into why the screen randomly goes dark while using the S-pen?
Sent from my GT-N7105 using Tapatalk 2
dima202 said:
So I am studying and taking notes on papyrus when all of a sudden screen goes black.
And it's not like it went to sleep mode because if I hit the power button it makes a sound but does not turn the screen back on.
When I click the second time it turns the screen on, as if I turned the screen off and on while it was black screen.
Has anyone experienced this?
So far I have had this only happen while taking notes on Papyrus, I have 30min set to turn of screen and this happens during my note taking...
Also I am using GMOD SPen, to turns of capacitive sensor. -Maybe it could be the problem?
Click to expand...
Click to collapse
I have had the same thing happen to me while using " Note Anytime ".
I'm using the app and the screen goes completely black, wait 3 seconds or so and the screen comes back on.
I'm using the new B3 stock ROM.
.
dima202 said:
So I am studying and taking notes on papyrus when all of a sudden screen goes black.
And it's not like it went to sleep mode because if I hit the power button it makes a sound but does not turn the screen back on.
When I click the second time it turns the screen on, as if I turned the screen off and on while it was black screen.
Has anyone experienced this?
So far I have had this only happen while taking notes on Papyrus, I have 30min set to turn of screen and this happens during my note taking...
Also I am using GMOD SPen, to turns of capacitive sensor. -Maybe it could be the problem?
Click to expand...
Click to collapse
I get this, but I'm unrooted running latest official for n8013.....I have to hit the power button twice to wake the screen again
Sent from my GT-N8013 using XDA Premium HD app
I noticed that I am getting this while using the s-pen.
This does not apply to just papyrus, it just randomly happens.
Please let me know if I should return this to Samsung as I only have 90 day warranty on this refurbished note 10.1
Do you have auto brightness selected? I never have this problem when I use manual brightness but notice it when I use auto brightness.
I just open a topic about this before I notice this one.
I get this problem also, I had this with a few different apps.
And i use auto brightness.
I will try contacting samsung to here what there have to say
Sent from my GT-N8010 using xda app-developers app
I've never used auto-brightness and I have this issue.
drdoombot said:
I've never used auto-brightness and I have this issue.
Click to expand...
Click to collapse
I've the same problem.. no rooted, original 4.1.2 galaxy note 10.1.
somebody said that would contact Samsung: have you any additional information?
AlexxN
I do have the same problem (with LectureNotes, but this is the only pen-focused app I use). Independently of auto-brightness, this should not happen. Any news from Samsung?
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..
I haven't been able to find this problem documented anywhere so I thought I'd ask.
It seems that my Nexus 5 has suddenly began turning on when being held at a certain angle. I believe that the proximity sensor has something to do with it. It started to happen after I was on the phone for a couple of hours. I've tried restarting, and switching from Art to Dalvik.
Is anyone else familiar with this problem or a solution? It's driving me nuts!
Thanks
onewaylife4all said:
I haven't been able to find this problem documented anywhere so I thought I'd ask.
It seems that my Nexus 5 has suddenly began turning on when being held at a certain angle. I believe that the proximity sensor has something to do with it. It started to happen after I was on the phone for a couple of hours. I've tried restarting, and switching from Art to Dalvik.
Is anyone else familiar with this problem or a solution? It's driving me nuts!
Thanks
Click to expand...
Click to collapse
Are you using a case? it might be pressing the power button.
I have using a case, but there is an oversized cutout around the power button. I am almost certain that this is related to a bug with the proximity sensor.
Mine, when using stock kernel would sometimes turn on by itself after pulling it from my shirt pocket..
Hasn't happened since I stopped using stock kernel.
Doesn't seem too common another poster, think whozilla saw this behavior as well.
No biggie.just odd.
WR
Sent from my Nexus 5
onewaylife4all said:
I have using a case, but there is an oversized cutout around the power button. I am almost certain that this is related to a bug with the proximity sensor.
Click to expand...
Click to collapse
does it turn ON after you power the phone OFF
or you mean that it wakes up from sleep state randomly?
GUGUITOMTG4 said:
does it turn ON after you power the phone OFF
or you mean that it wakes up from sleep state randomly?
Click to expand...
Click to collapse
No, it won't turn on if the phone if OFF. I'm referring to it "waking up". It will wake up simply by holding the phone at a certain angle and distance away from the body.
onewaylife4all said:
No, it won't turn on if the phone if OFF. I'm referring to it "waking up". It will wake up simply by holding the phone at a certain angle and distance away from the body.
Click to expand...
Click to collapse
Are you using a custom Rom/kernel? if so, try installing a new Rom
If that happens to be a hardware problem, It could be more related to the power button than the P.sensor
Most common issues related to the sensor is that screen stays off. Eventually, a screen protector can produce that, but not in your case.
The proximity sensor won't notice the angle you tilt the phone at (compass sensor does). It needs to detect something in front of it closer than +-1 inch to act up and should
turn off the screen when in a phone call. There's no much reason to turn on screen because it is not its function and much less if not phone call is happening.
Maybe the USB port is dirty and thinks you plugged a charger
or power ribbon/connector is loose inside, if any.
Hey guys,
So I got a S6 G920I last week, and I had to return it because the home button was kind of loose, and it was making a fun noise every time I pressed it. Now I have the replacement working fine, but I noticed something rather odd.
When I restart the phone, if I enter my SIM pin and unlock the device immediately after restarting (i.e. without letting the device to turn off the screen) I'm getting overly saturated screen colors, to the point that my wallpaper looks completely different.
The problem goes away after turning the screen off and on, but it's very weird this is happening. I've seen several issues with the S6 screen on the forum but nothing like this.
I'm adding the steps to reproduce (old habit from my QA days) just in case you have time to check it on your device:
1. Press and hold the power button
2. Tap on Restart
3. Immediately after the device restarts, enter you SIM pin (if needed). Don't let the screen turn off.
4. Unlock the device
After step 4. I'm seeing the device with a completely different screen color. Blacks are waaaaay to black, and generally looking very weird.
As I said the problem goes away after turning off and on the screen.
I'm adding some (very low quality) pictures, so maybe you can notice the issue. In the normal picture, you can see some diamond shapes in the wallpaper, but in the saturated image you can't because of the high contrast colors.
Let me know your thoughts please.
Thanks.
Mine does it too. Weird. Are you using a custom launcher or anything?
Sent from my SM-G920I using XDA Free mobile app
ThatChinskiGuy said:
Mine does it too. Weird. Are you using a custom launcher or anything?
Sent from my SM-G920I using XDA Free mobile app
Click to expand...
Click to collapse
No, default launcher. I'm using the basic mode for the display, but I noticed it also happens if you're using Adaptive display. I can see you're using the international version, maybe it only happens on those devices... Can anyone using a T-Mobile or AT&T device confirm?
Can you try the same process with basic display mode instead of adaptive ?
ecksreturns said:
Can you try the same process with basic display mode instead of adaptive ?
Click to expand...
Click to collapse
I tried with basic display mode and adaptive display mode, both are behaving the same way.
Netrunner16 said:
No, default launcher. I'm using the basic mode for the display, but I noticed it also happens if you're using Adaptive display. I can see you're using the international version, maybe it only happens on those devices... Can anyone using a T-Mobile or AT&T device confirm?
Click to expand...
Click to collapse
I'm on a Canadian variant with a T-Mobile ROM. I don't THINK I have that issue. I tested with a dark wallpaper and it seems fine for me.
Just as a closure for this topic, after the last update I received in my SG6 a couple of days ago, the issue seems to have gone away. I've tried with different display configurations and couldn't reproduce it anymore.