I noticed that my screen doesnt turn off when I answer phone calls. I though it was a problem with the ROM I was running until I flashed a new one and found out it was there too. So I flashed to stock and unrooted via ODIN. The issue still exists. I turned off the lights in my room...no flashing of the proximity sensor and I tested it in the Galaxy S3's hidden menu...it read "Proximity 0.0 ADC; 0(0,0,0)"
I was wondering if there is a possible fix that I could do, because I would really hate to have to return it to VZW. I had multiple replacements with my Nexus till finally they budged an gave me the S3 as a replacement. I hate all the hassle. I just wish they could give us sufficient CLN Devices.
I've heard from a few other owners that the S3's proximity sensor can be very finicky.
No screen protector? Several of these, most notably the XGear Spectre, create prox sensor issues.
And you haven't manually disabled it in call settings?
Sent from my SCH-I535 using xda premium
pdinphx said:
I've heard from a few other owners that the S3's proximity sensor can be very finicky.
No screen protector? Several of these, most notably the XGear Spectre, create prox sensor issues.
And you haven't manually disabled it in call settings?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
No screen protector or case...I havent disabled it either. I tried disabling it and re-enabling it to see if that would fix it and it was a no go. Like I said, Im really hoping I dont have to deal with VZW
Can someone please tell me what their proximity sensor reads as in the hidden menu
Sent from my SCH-I535 using xda app-developers app
Related
I have tried multiple sensor readout programs and games that supposedly use the phone's Gyroscope if functioning, but don't think it's working. Doesn't this phone have one?
Sent from my SAMSUNG-SGH-I997 using XDA App
paolofat said:
I have tried multiple sensor readout programs and games that supposedly use the phone's Gyroscope if functioning, but don't think it's working. Doesn't this phone have one?
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
It's got one, we have devices for it in the kernel, but I have no idea how to read it. Catting the dev doesn't work (but it doesn't for the accelerometer either).
Actually... hmm... /dev/k3g has the same broken permissions that were hosing up the compass in some of the early Gingerbread custom kernels. I wonder what happens if I change it. Will try in a day or two, probably going out of the house soon.
Im running Glorious Overdose V2 but I had this issue with other roms as well for some reason my touchscreen sometimes doesnt respond. In order for it to start working again I have to lock and unlock my phone sometimes it happens frequently and other times it doesnt. Any tips on how to fix this issue?
Sorry no tips on how to fix, but I'm running stock and it happens to me too. I though it might have to do with my crappy screen protector or me somehow messing with the optical trackball, but it seems not since you're experiencing the same issue.
Sent from my SGH-T839 using XDA App
I have this issue, too...
...can confirm it happens on stock and custom roms.
Sent from my SGH-T839 using XDA App
This app worked awesome on my sensation. Give it a try and report back please? I set to performance.
https://market.android.com/details?id=br.shop4apps.touchscreenbooster.com
Sent from my SGH-T839 using xda premium
Nope
I tried the app and it didn't help at all and sometimes my phone also starts randomly selecting as if I touched it.
Its a hardware problem. Samsung claims its a software problem but I doubt it. It happens to me all the time and I've posted threads about it as well.
What I have found is that any sweat or liquid on your fingers that gets left behind on the screen causes it to act sporadically. All you can do is constantly clean your screen when the phone is locked.
Sent from my SGH-T839 using XDA App
i have this problem, but i have noticed its only after iv gotten my hands wet. i kinda figured it was 1$ screen protector.
My screen would do the same thing until i bought one of the sk screen protectors. Haven't had that problem since.
Hi there!!
I don't know if this is a know thing anyway, on the right of the HTC logo there is the proximity sensor that shut down the display during a call. When it's on a you can see a red light from it. It should be turned on only during call. In the last days I have noted that the light remain always on even if I'm not doing a call. It turns off only if I taskiller all the process, but this stand only for 40 second as after this period of time the light reactivate itself again ( probably because some proces automatically restarts ) what can I do?? Is there somebody else who he's experiencing this too??
Sent from my HTC One S using xda app-developers app
light_n_roses said:
Hi there!!
I don't know if this is a know thing anyway, on the right of the HTC logo there is the proximity sensor that shut down the display during a call. When it's on a you can see a red light from it. It should be turned on only during call. In the last days I have noted that the light remain always on even if I'm not doing a call. It turns off only if I taskiller all the process, but this stand only for 40 second as after this period of time the light reactivate itself again ( probably because some proces automatically restarts ) what can I do?? Is there somebody else who he's experiencing this too??
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Do you have any apps for brightness management? I've experienced the same before and it was due to such app.
no..I use no app for that...
Have you tried to make another phone call and see if it switches off after hang up? Maybe in the last call it hasn't switched off for whatever reason/bug.
I noticed this, but after some digging I found out that Viber is causing this:
http://www.boards.ie/vbulletin/showthread.php?p=80972874
nor-ric said:
Have you tried to make another phone call and see if it switches off after hang up? Maybe in the last call it hasn't switched off for whatever reason/bug.
Click to expand...
Click to collapse
Already tried and not worked
boardlord said:
I noticed this, but after some digging I found out that Viber is causing this:
http://www.boards.ie/vbulletin/showthread.php?p=80972874
Click to expand...
Click to collapse
Thanks you very much!! You are right, it's viber, I have manually closed it and it stop doing that!!:good:
boardlord said:
I noticed this, but after some digging I found out that Viber is causing this:
http://www.boards.ie/vbulletin/showthread.php?p=80972874
Click to expand...
Click to collapse
THANK YOU, this was driving me insane and I couldn't find anything on it
Yes, viber is the problem. Thank you guys for the info!
Sent from my HTC One X using xda app-developers app
An updated version of viber is now out with fixed proximity sensor controller..no more bug
Sent from my HTC One S using xda app-developers app
Good to see you've found the cause.
I also noticed this behaviour if you made a call and switched staight to loudspeaker without putting the phone to your ear. When the call was finished the sensor would remain active requiring a reboot of the phone to turn it off.
Seems to have been fixed with the 4.0.4 update
Same thing happened to me, except I don't have viber. Reboot fixed it.
Sent from my HTC One S using xda premium
TheForumTroll said:
Same thing happened to me, except I don't have viber. Reboot fixed it.
Click to expand...
Click to collapse
I don't have viber and even after reboot, wipe cache/dalvic it still glows. HTC One S with Axiom ROM. this just started in the last week. I haven't downloaded any new apps though several have updated but I couldn't tell you which ones now. Trying to disable everything I can think of that would use the proximity sensor to no avail. Any help would be appreciated.
This happens to me whenever I'm using bluetooth, but what works for me is this:
Download "Proximity Sensor Finder" from the play store, open it up and wave your hand over the proximity sensor. Close the program and the red light goes away. It's faster that doing a reboot. This works for me and hopefully it works for others as well.
My problem was related with a bug inside viber, the app has been updated and the sensor start working good again
Sent from my HTC One S using xda app-developers app
Bowmanspeer said:
I don't have viber and even after reboot, wipe cache/dalvic it still glows. HTC One S with Axiom ROM. this just started in the last week. I haven't downloaded any new apps though several have updated but I couldn't tell you which ones now. Trying to disable everything I can think of that would use the proximity sensor to no avail. Any help would be appreciated.
Click to expand...
Click to collapse
I am facing the exact same scenario. I have never installed Viber on my phone.
Does the issue get resolved after the JB update?
Sent from my HTC One S using xda app-developers app
Snapperjacker said:
This happens to me whenever I'm using bluetooth, but what works for me is this:
Download "Proximity Sensor Finder" from the play store, open it up and wave your hand over the proximity sensor. Close the program and the red light goes away. It's faster that doing a reboot. This works for me and hopefully it works for others as well.
Click to expand...
Click to collapse
This is what I used and haven't had a problem since.
you could also try to install taskiller and kill everything, if the sensor stop being on it's related to a process that keep it active if not it's probably and hardware issue
Since we're talking about the proximity sensor, it shouldn't stay on during a call when the screen is manually turned off. On the Galaxy Note II the sensor turns off.
Sent from my HTC One S using xda app-developers app
Having your vibration setting activated caused the proximity light to stay on.
Sent from my HTC One S
I've searched and other than the "Viber" problem, I haven't seen anyone mention anything about the proximity sensor being stuck on(mine is). I tried everything I saw in the forums and saw nothing then was just searching the market and found this:
Rezound Prox Sensor Calibrator
By default, mine showed "NEAR" when the prox sensor came on, so if you change the top setting (Low Threshold) to 100(all the way to the right) then it makes the distance you need to be before the sensor recognizes you as "FAR" about 3 inches away from the phone. Fixed the issue for me, figured I'd help someone else out.
Is it compatible with the S?
Sent from my HTC VLE_U using xda premium
Spastic909 said:
Is it compatible with the S?
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Yep, I used it to fix mine
It works for me
Hy there.
Thank you for this. It fixed my phone immediately.
It's just a life saver.
Hello everyone,
So i bought a one X a couple months ago and it already came with a custom rom, i removed that and installed the Team Viper rom and currently have the latest version installed (April 10). The phone screen will not turn on during a call if you move the phone away from your ear like it should, the only way to get it to turn on is by pressing the power button and even then it only stays on for a few seconds and then turns right back off. Im not sure if this worked before i installed Viper. Any suggestions guys?
Joe-Pk said:
Hello everyone,
So i bought a one X a couple months ago and it already came with a custom rom, i removed that and installed the Team Viper rom and currently have the latest version installed (April 10). The phone screen will not turn on during a call if you move the phone away from your ear like it should, the only way to get it to turn on is by pressing the power button and even then it only stays on for a few seconds and then turns right back off. Im not sure if this worked before i installed Viper. Any suggestions guys?
Click to expand...
Click to collapse
Do you have a case? Try placing a call and use your finger to left of the AT&T logo. I don't know much about viper but could be a setting (usually accessibility) that does that.
Sent from my Carbon-ize Evita using xda-developers app
You can also try calibrating g sensor.
Settings-Display and Gestures- G Sensor
Sent from my HTC One X using xda premium
Herc08 said:
Do you have a case? Try placing a call and use your finger to left of the AT&T logo. I don't know much about viper but could be a setting (usually accessibility) that does that.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
I tried both of the suggestions from you guys and none of them work. I tried doing a full wipe and re installing the viper rom but no success...anything else?
Have you set a security lock for the home screen?
Sent from my HTC One X using xda premium
Venomtester said:
Have you set a security lock for the home screen?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
also is there a screen timeout? and im sure android has a feature where you can hang up using power button...again i am not sure about viper, but if you go to settings > accessbility > and make sure certain things are not checked, that can help...if that doest work, then your proximity sensor could not be working...does your auto brightness adjust accordingly?
Herc08 said:
also is there a screen timeout? and im sure android has a feature where you can hang up using power button...again i am not sure about viper, but if you go to settings > accessbility > and make sure certain things are not checked, that can help...if that doest work, then your proximity sensor could not be working...does your auto brightness adjust accordingly?
Click to expand...
Click to collapse
Venomtester said:
Have you set a security lock for the home screen?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
There is no security lock for the homescreen, the auto brightness also works perfectly. I cant find anything in accessibility the only thing checked off is auto rotate screen. I think it may be the proximity sensor then because the digitizer on the phone looks like it was replaced.
The only other thing that I can think of is a screen protector that is blocking it or it has smudges that need to be cleaned. They have apps that calibrate proximity sensors but I have never used them.
Sent from my One X using xda premium
Venomtester said:
The only other thing that I can think of is a screen protector that is blocking it or it has smudges that need to be cleaned. They have apps that calibrate proximity sensors but I have never used them.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I seen those up here. Search the forums or play store. Is the auto brightness using the same sensor or is it two? Tried looking, but can't tell.
Sent from my Carbon-ize Evita using xda-developers app
I believe it is two. If both auto brightness and proximity were running off the same sensor, they would both act up. I think. Just a theory. But if it is one sensor then the calibration app should work.
Sent from my One X using xda premium
Venomtester said:
I believe it is two. If both auto brightness and proximity were running off the same sensor, they would both act up. I think. Just a theory. But if it is one sensor then the calibration app should work.
Sent from my One X using xda premium
Click to expand...
Click to collapse
It would make sense to be two. But who knows?