Hi all professional friend, few days ago i had bought a samsung galaxy a510fd, when i start to call the screen turn off because of proximity sensor, i seems the sensor dosent work good properly, i had search in xda and found some ways i use *#0*# and when i press ''sensor'' the screen become green and start vibrating and when i cross over the sensor only the adc number start to chang from 24 and the proximity number is always 1, after that i use echo code and other calibrating manual codes but it dosent change, what should i do??
http://forum.xda-developers.com/showthread.php?t=2569141
Related
My Galaxy S has a problem with the Light Sensor, every time i make a call my phone freezes or black screen, I tried running some sensor tests but also does same when i try the light sensor, so that must be it. have this problem for a year, at first i thought it was the proximity sensor.
When my headphone is plugged in, i dont have this problem because the light sensor wont interfear then.
I want to disable the startup of the light sensor,
I already setup ADB, so im ready to push and pull, but i don't know wich file i need to edit. remove a # here and there
Can anyone tell how wich file it is?
Got inspired by :
http://forum.xda-developers.com/archive/index.php/t-764368.html
Sure its not the proximity sensor? Cause I got the same problem. When I accept a call screen goes black, the upper bar is visible and after a while the screen turns off. Im ceratin that is a problem with the proximity sensor or not?
Same here, yeah think its the proximity, but my light sensor also doesn't function properly, auto brightness adjustment doesnt work also.
Very anoying problem.
Hello everybody. Firstly I'd like to sorry but my English is poor. Ok, so what's going on? One day I saw that 4 touch buttons don't have backlight. So I tought it could be that light sensor. I've gone to the display settings and I set up auto brightness. And nothing has changed... No matter where I go, brightness doesn't change at auto. And this no backlight of 4 touch buttons... My question is: what it could be? What is wrong with my HTC? Could it be software issue or rather hardware?
the autobrightness setting your messing with is for the backlight of the screen, not the 4 buttons. as for the 4 buttons, what kernel and rom are you on? newer xe kernels have brightness setting for the buttons (if its bright outside itll turn off, if its dark then itll turn on). does the backlight of the 4 buttons never work or just sometimes?
I use stock 1.50~~ ROM with stock htc kernel. Sometimes (as now for example) 4 buttons backlight works, sometimes not, it's lottery... Now there is working also light sensor. I woke up today and it has been working, but since monday to yesterday it didn't work. Strange issue...
Try check tour sensors with androsensor from Market/Google Play.
It shows you whats sensors do work.
Light sensor is at the top left hand side of the phone at the front beside the speaker. Put your thumb over it and see if the buttons light up. If they do light sensor is working!
My sensors are still not working to all the time.
I did edit the build.prop with this line at the botten:
ro.mot.buttonlight.timeout=0
Reboot 2x
Wich helped .
But now its gone again,it drives me nuts
There is shortcut for light sensor check, for example on Samsung i9001 I can use *#*#0588#*#* - Proximity sensor test
hope this can help
addisuw said:
There is shortcut for light sensor check, for example on Samsung i9001 I can use *#*#0588#*#* - Proximity sensor test
hope this can help
Click to expand...
Click to collapse
And what should happen ?
Tried it,nothing.
Thanks tho.
Do you have it in a case? I put mine in a gel case and although it didn't appear to block the sensor I was finding that when I finished a call the screen didn't light up again. I trimmed the case so that it had much more clearance around the sensor and it works well now.
xynox93 said:
Hello everybody. Firstly I'd like to sorry but my English is poor. Ok, so what's going on? One day I saw that 4 touch buttons don't have backlight. So I tought it could be that light sensor. I've gone to the display settings and I set up auto brightness. And nothing has changed... No matter where I go, brightness doesn't change at auto. And this no backlight of 4 touch buttons... My question is: what it could be? What is wrong with my HTC? Could it be software issue or rather hardware?
Click to expand...
Click to collapse
Is your proximity sensor working during calls?
Not for me
(Ps.factory reset in total dark worked till reboot)
Did anyone figure this out?
I bought a used phone for a great price but my light sensor and proximity sensor dont work. Confirmed with androsense.
I would really like to just have the buttons light up all the time when the screen is on. Anyone know how to make that possible?
Hello,
I have HTC Radar and trying to enter bootloader i entered this Omega System Loader Menu http://store.picbg.net/pubpic/BC/B9/ef1a07a1500bbcb9.JPG
When i managed to exit this menu my proximity sensor went red and i was like "wtf - Hal 9000!"
after restart the red proximity sensor was gone and i installed new rom. later i entered Navigon and under Reality scanner a massage appeared:
"Your device doesnt support this feature. Possible causes:
-the devicde doesnt dispose of a motion sensor.
-the motion sensor doesnt work properly"
Can you tell me what is that red sign and did i broke my htc
thank you
That's a bit too bright for a proximity sensor, but the light it emits is red, but more like infrared like the one found in Kinect. And about the motion sensor, I think it means the gyroscope, the Radar doesn't have this sensor.
Make a call and look on proximity sensor. Red means is working during call.
yes, yes, it is very slight red signal. so everything is working normal
There are several topics on red dim light (emitting out of proximity sensor) on the galaxy note 2 just left to the front facing camera. I was having same problem for 2-3 days back, one of two sensors beside front facing camera lit up continuously showing red dim light even with phone screen off or at standby mode. I searched a lot about this topic and was disappointed. There was also solution given by one senior member about uninstalling Viber, Viber was found as culprit messing with proximity sensor and keeping it on all the time. This really helped a bit. Here is solution.
It is not only Viber a culprit but you have to go into flashback and recall which was the last app you have installed after which actually the problem started, mine was rockettalk, all these are kind of apps which deal with instant messaging, internet calling, etc Just recall and find out such app and uninstall it, after that just reboot your device and check whether the quick glance feature is off i.e., settings/motion/quick glance, make sure it is not ticked. Reboot our device and thats it........!!! The annoying red dim light is gone :laugh:
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
Apparently this is a fairly common issue with the Samsung Galaxy S10 range and after doing some simple tests I'm hoping my insight can help.
The first test I did was to dial *#77692# to access the proximity sensor test menu. While I was on this menu I covered the sensor with my hand and got a proximity reading of 1.0 everytime the sensor was covered and 0 when it wasn't, which to me suggests that the sensor is working fine.
the second test involved ringing up my voicemail and basically doing the same thing, now here is where it gets interesting; if I cover the sensor for a few seconds and then lift my hand the screen stays turned off. But if I then recover the sensor an inconsistent number of times (sometimes once, sometimes a bunch of times) it'll turn the screen back on.
Additional: I also tested this on Skype and the behaviour was identical.
To me it looks like the issue is purely on a software level rather than a hardware level as this only seems to happen during phone and Voip calls, but not during tests.
Now I'm not a developer so I can't begin to understand how this issue could be fixed, but I'm hoping my little tests can help matters along.
Had the Problem also, fixed it by rebooting into recovery and wipe cache partition.
Same issue here..
I have had S10e, but i sold because of this issue.. now i want to buy it again, but i don't know if exists an S10E series without the proximity sensor issue.. anyone with ans S10E without this bug? (just try to hear a whatsapp audio near the ear)