Related
Hi all,
I think my display has a problem of flickering: I noticed it going to "system status" window by clicking on battery, or signal icon. Here you have a gray stripped background that on my display seems to be unstable...something like flashing. I have the same impression if I look at the headers stripes of the tabs, where you find, "People", "Messages" etc...
The strange thing is that what ever I see, pictures, different windows, they all seems to be very stable, no flashing...flickering...problem.
Now I ask to myself, could it be an optical effect due to the pattern of that specific background?
I make the same answer to you all...and did somone notice the same problem?
Please answer me becouse I should have to replace it if I really have this trouble...
THX so much!
asci said:
Hi all,
I think my display has a problem of flickering: I noticed it going to "system status" window by clicking on battery, or signal icon. Here you have a gray stripped background that on my display seems to be unstable...something like flashing. I have the same impression if I look at the headers stripes of the tabs, where you find, "People", "Messages" etc...
The strange thing is that what ever I see, pictures, different windows, they all seems to be very stable, no flashing...flickering...problem.
Now I ask to myself, could it be an optical effect due to the pattern of that specific background?
I make the same answer to you all...and did somone notice the same problem?
Please ask me becouse I should have to replace it if I really have this trouble...
Click to expand...
Click to collapse
Did you try a Clear Storage followed by a Hard Reset?
@tnyynt
Thank you for your replay.
Other people suggested it to me. I've tried it right now and it had no effect, I'm still having the same problem.
BTW: Clear Storage performs by itself a HardReset after typing 1234...am I right?
I too am noticing this flickering on the top bar. I couldn't work it out. No idea what it is, but quite glad I'm not the only one with it. No idea if it is an illusion or a fault though. Can anyone else confirm?
asci said:
@tnyynt
Thank you for your replay.
Other people suggested it to me. I've tried it right now and it had no effect, I'm still having the same problem.
BTW: Clear Storage performs by itself a HardReset after typing 1234...am I right?
Click to expand...
Click to collapse
Yes, you are right, but it's a different one than the normal Hard Reset.
Try to change brightness of the backlight, for example turn it off and check then.
asci said:
Hi all,
I think my display has a problem of flickering: I noticed it going to "system status" window by clicking on battery, or signal icon. Here you have a gray stripped background that on my display seems to be unstable...something like flashing. I have the same impression if I look at the headers stripes of the tabs, where you find, "People", "Messages" etc...
The strange thing is that what ever I see, pictures, different windows, they all seems to be very stable, no flashing...flickering...problem.
Now I ask to myself, could it be an optical effect due to the pattern of that specific background?
I make the same answer to you all...and did somone notice the same problem?
Please answer me becouse I should have to replace it if I really have this trouble...
THX so much!
Click to expand...
Click to collapse
thats normal. it has something to do with the refreshrate. that occours on every phone and pc monitor and so on. it always depends on what you are viewing at the momeent and often occurs when there are many very thin lines like at the top of the HD.
I have noticed no flickering at all.
@tnyynt
Do you mean I should perform a normal Hard Reset? How can I do it...I still haven't discover how to do it...
@Raziel1
It would be normal if everyone could see it on their HD, but it seems that only some terminals have this problem...Do you mean so that my HD has no problem?
THX to all!
Raziel1 said:
thats normal. it has something to do with the refreshrate. that occours on every phone and pc monitor and so on. it always depends on what you are viewing at the momeent and often occurs when there are many very thin lines like at the top of the HD.
Click to expand...
Click to collapse
A LCD display shouldnt flicker. It's either a hardware or software problem. Old CRT-monitors and TVs flickered because they "painted" the picture from top to bottom, and if they didnt do it fast enough it was perceived as flickering. LCD displays uses a dot matrix and shouldnt flicker regardless refreshrate.
Marinese said:
A LCD display shouldnt flicker. It's either a hardware or software problem. Old CRT-monitors and TVs flickered because they "painted" the picture from top to bottom, and if they didnt do it fast enough it was perceived as flickering. LCD displays uses a dot matrix and shouldnt flicker regardless refreshrate.
Click to expand...
Click to collapse
Do you mean that I'm calling my display problem improperly or that it really can be a problem of this kind of display and so it means it is broken?
I have been noticing this exact same flickering, and couldn't decide if it was normal or not!?
but this flickering only occures when there are certain things on the screen like the thin lines of top of the home screen. its not the screen itself which is flickering. maybe it has something to do with vision and not with a technical aspect. the same thing can be seen on every screen i ever looked at. you can try it out, by taking a picture of a pc monitor at close range with high resolution. when you look at it and scroll around with zoom, it will often flicker like hell because of all the details and maybe downscaling or whatever
asci said:
Do you mean that I'm calling my display problem improperly or that it really can be a problem of this kind of display and so it means it is broken?
Click to expand...
Click to collapse
I havent seen the problem myself so it's hard to tell. You can often see by looking at it if its a software or hardware problem. If it's a software problem its just a certain part, for example a window titlebar, that flickers. This is usually caused by bad programming, the programmer has told the program to repaint with a certain interval even if there is no change. If it's a hardware problem the flickering usually isnt constrained to parts of the window, for example it doesnt follow the titlebar. Instead its usually diffuse parts of the screen that flickers.
@Marinese
Uhm...I'm figuring out how to test it...If I look at a picture, I can't notice the problem, and it seems to be localized on upper bars and on some particular windows I told before. If I could flash it with another ROM...but it's not HardSPL yet and I would keep it in warrenty untill my provider/seller TIM tell me what to do with it. So it could be a ROM problem too?
It would be usefull to have two of them placed side by side
and see the differences...
For me it seems to happen when the brightness is set to high, or I am in a well lit room with auto brightness enabled. With the brightness reduced I see no flickering...
Does that give any clue as to whether it is hardware or software? It seems to be dark colours that flicker.
@evilskanker
Uhm perhaps if you reduce brightness, you reduce the visibility of the problem as well...
I don't know about the dark colours...but I took a black picture and it doesn't flicker...
I have that exact same issue..
Altought I only notice it, on the upper horizontal lines on the RIGHT in TouchFlo3D.
What is the reason for that? And how to solve it?
Thanks.
I'm not sure we're talking about the same thing, but what I have is quick fluctuation in the brightness level without changes in the ambient lighting. You could call it flickering, although I would say it's not as fast as a flicker in my case. It seems to me it has something to do with the light sensor and its sensitivity. I would like to think that a ROM update will sort it, but we will have to wait and see. I'm not doing anything about yet.
@atomikpt
It's the same of mine and also try to go to "system status" window by clicking on battery, or signal icon and take look of what it happens.
@arisg
Nothing to do with your case. Consider that I desabled the light sensor and I'm using brightness to its maximum level.
This has been happening pre and post Nodo on my focus. If i'm on a phone call for at least a few minutes, then pull the phone away from my head, the phone's display should become active, but it isn't.
Anyone else having this issue or is it time to exchange the phone?
I have the same issue also it seems like I have to press the power button a couple of times to get it back.
Sent from my SGH-i917 using XDA Windows Phone 7 App
I'm also having this issue. Anyone remember if ther were having it pre-Nodo? Just wondering if the update changed something.
Regardless, it's a bit of a PITA.
I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.
ArcWhistler said:
I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.
Click to expand...
Click to collapse
How did you do that?
Yeah, ditto that - how do recalibrate the sensor?
Samsung Diagnostic App.
http://forum.xda-developers.com/showthread.php?t=839154
I was pecking around the screens months ago, and there was one bank of tests (multi-touch, red, green, blue, white, battery, etc, etc) that allowed setting and viewing the proximity sensor.
I remember playing with moving my hand closer, and further and watching it change from sensed to clear.
Sorry, can't remember which codes now.
I used the Wiki:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
LCD Test - *#0*#
Ok, mine says No Detection. Is there anyway to set the value?
One other thing to note, about the samsung focus specific update regarding disabling the touch sensitive buttons while in a program, that also isn't working for me either. Not sure if they are related, but thought I'd throw it out there.
And as far as calibrating goes, not sure it would help since the problem only occurs while I'm on a longer phone call. On short ones the proximity sensor works just fine.
If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.
ArcWhistler said:
If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.
Click to expand...
Click to collapse
Mine says No Dectection. It has Prox Sensor: XXX I've taken my entire hand and covered my phone. NOTHING. When I push SET, It says ProxThreshold :0. Is there anyway to set it manually?
samsung focus post nodo
I believe the prox sensor issue is happening post nodo, I have never had this problem prior to the update... I have been able to fix it temporarily by pulling the battery and starting it up... don't know how long the fix works... got to do some testing... I am wondering if its a power thing as the screen wouldnt work when you plugged it in to power and had on a soft surface....
Still nothing. I didn't want to hard reset since I have Chevron installed. For some reason I did four updates on my phone and don't have a single backup. If I hard reset I'm S.O.L. with Twin Blades and other homebrew apps
What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?
BooR4dley said:
What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?
Click to expand...
Click to collapse
It has a big red box. It says No Detection. Prox Sensor:XXX Do I press Set or Reg?
another thing is wrong
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?
rockclimbaudiextreme said:
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?
Click to expand...
Click to collapse
same problem here. seems like those two sensors are burned
I just got my note and am having problems with auto rotate.
I ran the tests in *#0*#
It looks like they all passed fine
But sometimes mine rotates n it's own and when it rotates, it sticks in Horizontal.
I do not understand the calibration instructions for Horizontal and Gyroscope.
For instance, when it says place device on a level surface and press calibrate, does that mean just place it on it's back on a table? Also, after it is done calibrating, should the gyroscope "ball" on that page move when you move the device? Mine is always stationary.
On the horizontal calibration, how do you position the device before you hit the calibrate button? Should it be landscape or portrait?
IMO they don't explain these very well and it's confusing how to set this up.
Yes, just place it on a table or the floor. Not sure with the gyroscope since i don't have the Note yet, but i imagine the ball moves.
If this is a bug it's a software bug. All Desire HD owners including me had the auto rotate bug when it got released. These are bugs that's very common on freshly released Android devices, and it will get fixed.
BazookaAce said:
Yes, just place it on a table or the floor. Not sure with the gyroscope since i don't have the Note yet, but i imagine the ball moves.
If this is a bug it's a software bug. All Desire HD owners including me had the auto rotate bug when it got released. These are bugs that's very common on freshly released Android devices, and it will get fixed.
Click to expand...
Click to collapse
Here's the question I have:
I only have 30 days for return if it's broken. Nobody else has complained about auto rotate yet and I would think that would come out pretty fast. I figured out mine had a problem 30 seconds out of the box.
Hi les_garten (another maemo/TMO refugee here!) - I've had my note for over a week, haven't seen any spontaneous rotations at all. I calibrated my gyro on day 1 though I think you don't ned to unless you are having problems. Once calibrated, the blue ball just sits in the centre of the circles, it doesn't move at all.
_pigro_ said:
Hi les_garten (another maemo/TMO refugee here!) - I've had my note for over a week, haven't seen any spontaneous rotations at all. I calibrated my gyro on day 1 though I think you don't ned to unless you are having problems. Once calibrated, the blue ball just sits in the centre of the circles, it doesn't move at all.
Click to expand...
Click to collapse
Thanx for that info! Mine also rotates when I turn horizontal, then won't go back into portrait.
How do you do the Horizontal calibration. Do you stand it on it's edge in landscape mode?
I'll never give Nokia another Nickel! Great idea with dismal execution.
horizontal calibration just involves sitting it flat on a flat surface. After calibration the ball can be "rolled" across both axes - like I said above, for me at least the gyro calibration screen does not allow the ball to roll at all either before or after calibration (hope that's what's supposed to happen, I've never had a phone with a gyro before, I would have assumed the ball was meant to move in response to tilt/turn ....
_pigro_ said:
horizontal calibration just involves sitting it flat on a flat surface. After calibration the ball can be "rolled" across both axes - like I said above, for me at least the gyro calibration screen does not allow the ball to roll at all either before or after calibration (hope that's what's supposed to happen, I've never had a phone with a gyro before, I would have assumed the ball was meant to move in response to tilt/turn ....
Click to expand...
Click to collapse
if you go into the dialer and dial *#0*#
then do sensors and run the Gyro tests and graph, it seems to be fine.
I have to keep auto rotate off.
It will rotate Landscape, but won't return to portrait.
It wil flip Landscape on one side and Landscapeon the other side, but won't do portrait, till auto rotate is turned off.
Anybody have any suggestions on how to fix this?
I guess I could whack it and start over, but that blows! That would at least tell me something I guess.
It's really irritating. And I would hate to keep it if it is broke.
I have the auto rotate bug also...you need to try many times before it will rotate... kind of embarrsing.. but I am sure it will be fixed first..but sometimes I wonder..if samsung have tired the phone at all before they ship it...such fundamental feature should work...without any problems
blackstar84 said:
I have the auto rotate bug also...you need to try many times before it will rotate... kind of embarrsing.. but I am sure it will be fixed first..but sometimes I wonder..if samsung have tired the phone at all before they ship it...such fundamental feature should work...without any problems
Click to expand...
Click to collapse
For some strange reason this makes me feel better!
bug was solved in 2.3.6 ..works without problems now.
blackstar84 said:
bug was solved in 2.3.6 ..works without problems now.
Click to expand...
Click to collapse
Thanx. I just did mine last night as well.
Very happy now!
i just got a galaxy note 3 weeks ago and it is running gingerbread 2.3.6
i have the same problem for the auto rotation problem, when i test the gyro and horizontal calibration, the ball doesnt move or move in a very laggy motion, when i lever my phone to a certain angle in all direction, the ball will not move in some area of the display. i had calibrated once before it has this problem, the ball move smoothly in any angle...now my message will auto rotate to landscape while i holding it in potrait...please help
I can't actually help fix anything - but if you enter *#0*# in the dialer and then select "sensor" from the LCD tests, then "image test" (under accelerometer sensor) you'll get a picture of a dog whichshould rotate between portrait & landscape as you rotate the phone, and there is an overlayed real time display of x and y axis angles as registered by the accelerometer.
This test should at least show whether the h/w is working or not.
Fix here
http://forum.xda-developers.com/showthread.php?t=1592170
I can fix that.This is from galaxy S2 but i dont knows how for Note, i try and working for Note. But after install from CWM, i see Setting/Display/ Gyroscope calibrationand Horizontal calibration. It not working. I was very afraid and i flash new rom N7000ZSLPF---------4.0.3 http://hotfile.com/dl/156123968/e690f65/N7000ZSLPF_N7000OZSLPF_OZS.zip.html
And now Gyroscope not work but rotation is work good.
Sorry my English
auto rotat pro
dude plz helppp......................I have to keep auto rotate off.:crying::crying:
It will rotate Landscape, but won't return to portrait.
It wil flip Landscape on one side and Landscapeon the other side, but won't do portrait, till auto rotate is turned off.
Anybody have any suggestions on how to fix this?
I guess I could whack it and start over, but that blows! That would at least tell me something I guess.
It's really irritating. And I dont wat to do:crying::crying::crying::crying:
saad elahi said:
dude plz helppp......................I have to keep auto rotate off.:crying::crying:
It will rotate Landscape, but won't return to portrait.
It wil flip Landscape on one side and Landscapeon the other side, but won't do portrait, till auto rotate is turned off.
Anybody have any suggestions on how to fix this?
I guess I could whack it and start over, but that blows! That would at least tell me something I guess.
It's really irritating. And I dont wat to do:crying::crying::crying::crying:
Click to expand...
Click to collapse
Since you are on Rocket ROM, check here:
http://forum.xda-developers.com/showthread.php?p=30107755
Hello everyone,
I have searched far an nigh - - , but it seems my question has only been addressed once and there the answer had to do with unlocking or rooting the phone. I don't want do that just yet. I can still send it in for repair, so I'd rather try to exhaust the available legal options first.
So, here goes my problem: Autorotation doesn't work properly. It hardly switches to landscape mode and cannot be bothered to return to portrait mode, if I don't close and reopen the app. The level and the accelerometer app confirm this problem. I'm on a T-Mobile (in German, that's Telekom) branded Omnia 7 running 7.10.8773. It seems the accelerometer is off or broken and there is no way to calibrate it. In the level app, when putting the phone flat on its back the white dot indicating the position is in the bottom right. I'd have to pick it up and hold it in front of me in a tilted position to center the white dot. Calibrating it within the app is only possible in said tilted position and in diagnosis mode, there is no "cal" button, only an exit button. The accelerometer app allows for calibration with the phone flat on the table; however, the calibration is not applied to the phone's sensor or the app: when I close it and then reopen it, the calibration is gone. - What can I do about this? I.e. can I do anything about this? I'd like to avoid an RMA.
Please help!
Thanks in advance,
Thomas
I have two SGS4's. On one, when I place a call, the call screen stays on and it turns off when I raise it to my ear. It then turns on when I pull it away.
On the other, as soon as I place I call the screen goes dark. The only way to get it back is to push the power button and unlock the phone.
The "Turn screen off during a call" setting is set on both phones.
Anyone have any idea what is causing this? Next step is to do a wipe, but that just sucks.
I'm on stock and not rooted.
Thanks!
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Sirchuk said:
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Click to expand...
Click to collapse
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
jprocket45 said:
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Nope, mine is naked for now. I'll have to do a reset today/tomorrow and see if that solves my issue. If not, I'm taking back to the store for an exchange. It's only been a couple of weeks.
To late for me to take it back but suppose to be a update coming soon that does alot of fixes so we will see Good luck like I said reset I did notice fixed it a bit let me know how it goes I'm threw sprint just curious if you have them only reason I ask if it's just a carrier issue with software or something I doubt it but just figured to see who you had lol
Sent from my SPH-L720 using xda app-developers app
Dial *#7353# and make a test
sent from my Galaxy
samersh72 said:
Dial *#7353# and make a test
sent from my Galaxy
Click to expand...
Click to collapse
That's what I was looking for!
Sure enough,the proximity sensor was always on and wouldn't go off.
I'm with T-Mobile and they have a 30 return/exchange policy if you buy it outright, which I had, so it only took about 10 minutes for them to exchange it!
Thanks for the testing code! XDA comes through once again!
Same problem when I'm making a call, the screen goes blank when I put it to my head and when I remove it nothing happens.
I tried *#7353# and the proximity sensor goes of but will not stop..
I'm currently rooted, could it solve the problem to go back to stock?
Possible Fix
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
I have had the same problem over the last 3 weeks and decided to take a gamble. I tightened up all the screws on the device and squeezed real hard on the area where the prox sensor is and poof... it works. I have no idea what was up but I feel like the sensor is loose and the pressure resolved the issue. Many other post have talked about cleaning the area over the prox real good and it works but I think its the pressure that is actually fixing the issue. Anyone else have any ideas? Sorry if this was posted incorrectly, I have never posted before but I felt this issue is a PITA.
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
My proximity sensor works - when I go into diagnostic, it goes green when I bring a hand near the sensor - my issue is that it doesn't seem to notice when I remove my hand and there no longer is anything proximal - until I hit the back button to exit the test. Other than blowing out the earphone jack, does anyone have a suggestion?
Thx.
divche said:
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
Click to expand...
Click to collapse
Proximity sensor
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
I guess what it comes down to is.....for some you can reset the sensor, for some they can blow it out with compressed air, but others actually have to take apart their phone to fix this issue.
marduj5 said:
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
Click to expand...
Click to collapse
hi
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Shohat said:
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
Click to expand...
Click to collapse
Hubris2 said:
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Click to expand...
Click to collapse
i'm sorry. i already tried your first solution and it worked like charm ! thank you ! :good:
HOw to solve, none of this works. How cann i clean proximity?