Hello everyone,
Recently, everytime I get a phone call, the screen doesn't go off when the phone is next to my ear. In other words, the sensor does not sense that I picked up the phone.
I have tried many ROMs to get this fixed. I flashed the factory GB and that didn't work either.
I'm not sure if this a driver problem or a hardware problem. Can somebody help me fix this??
Thanks.
Proximity sensor problem anyone??..
Sent from my GT-I9000 using xda app-developers app
Hello,
at first I would try to test the hardware. I did find a small app called 'My Android sensors'. Start that and look for a proximity sensor. If you can't find it then there is a problem.
Bug it should be there even if it isn't working. Then open if and look for the sensor state. On a SGS it can only say 'near' or 'far'. Test the sensor by moving the hand to the left side of the speaker grill. There is the sensor. The state should change. If it doesn't then you have a malfunctioning sensor so changing the Rom is of no use.
If it does change you should contact the Rom developer for a start.
Can try reflashing stock or custom Rom whatever you are on. Mostly it can be a sensor driver issue present in the current Rom.
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk HD
dal8moc said:
Hello,
at first I would try to test the hardware. I did find a small app called 'My Android sensors'. Start that and look for a proximity sensor. If you can't find it then there is a problem.
Bug it should be there even if it isn't working. Then open if and look for the sensor state. On a SGS it can only say 'near' or 'far'. Test the sensor by moving the hand to the left side of the speaker grill. There is the sensor. The state should change. If it doesn't then you have a malfunctioning sensor so changing the Rom is of no use.
If it does change you should contact the Rom developer for a start.
Click to expand...
Click to collapse
the value (near far) doesn't change. So it's dead?
AW: [Q] Call sensor
Maybe there is software to disable the sensor. Or your Rom has such an option. But I'm not aware of such things. So it looks like your sensor is dead. Sorry!
Related
Hello i found out my N1 Proximity sensor have issue wen a install 2.3.3 my screen shutoff when i do call and stuck blank screen i have to remove the battery and put the back.
i download Elixir App and doing some test and Sensor only Say "NEAR" I put my hand on the screen still say Near...
/etc/permissions
android.hardware.sensor.proximity.xml
android.hardware.sensor.light.xml
/system/lib
libssensorservice.so
Factory Code Nexus One
#*#0588#*#* Proximity sensor test (no work in my N1)
can i restart the sensor?
can i disable Proximity in DIAL ?
do i need to take tHTC Support N1?
where is the CM3602 on N1?
can i fix my self?
and I have the same problem but no answer :-(
___
http://forum.xda-developers.com/showthread.php?t=707234&highlight=nexus+proximity
Hi,
Have the same issue, too !
hmm, looks like a android 2.3 issue on that one....
The same here. Is there any way to do a downgrade to 2.2? The phone is unusable, I'll have to go back to my old Nokia!!
Also, at the same time, when I plug the earphones on the Nexus, it doesn't detect them and continues playing through internal speaker!! And I suspect that the light sensor doesn't work.
Hasta luego.
Nexus one proximity sensor problem
Hi guys i had the same problem with my phone
and I manage to fix it
I open the phone and check where the proximity sensor was
and clean it with the a spray duster they sell in computer store
I clean the entire phone
put i back together and it was fix
thanks me if it works for you like that
You are lucky,, just opened my phone and cleaned the proximity sensor and light sensor with specialized electronics solutions i borrowed from work and nothing happened,,dont know what to do about it
RE: how to disable proximity sensor
hey there, this is my second post, THIS PLACE IS AWESOME!!! I was able to disable my nexus one proximity sensor using the hex edit method (after granting the app root access) and now a brick to be is no more. thank you to the poster who made the original post and the one who mentioned the way to give hexedit root access. my sensor definition was exactly where he said it would be. the name of course was cm3602 (lowercase, looking for uppercase found nothing) I was able to change hex position 0000323d from 32 to 00 , and poof, no more black screen after dialing or when receiving a call. a temporary solution I was using was to use a bluetooth headset.
Thank you all.
does anyone experience proximity and ambiant light sensor issues mines wont work. first i thought it was broken and bought a new sensor replaced it and it still wont work. the headphone jack and speaker works ok but not the sensors anyone? I also tried the sensor reading apps to see if its working. proximity wont show anything and the light sensor gives me between 4700-5000 lux but wont change no matter what light condition any help i cant even make a phone call without headphones anymore
What kind of rom are you running?
If you replaced it then its not a hardware issue it software then
Sent from my GT-I9000 using xda app-developers app
well ı've been using pa v2.54 before and flashed lots of roms in this 3 months i even flashed official rom went stock but still no luck :/
Really strange even with a new sensor and stock rom isnt working maybe the socket isnt good maybe a problem with the motherboard i dont know i thought it might have been a rom problem maybe the people here had a similar issue and they might help i wish you luck and i hope you find a fix
Sent from my GT-I9000 using xda app-developers app
thanks if it was due to the socket im guessing that the speaker and the headphone jack would also not respond... but yeah its a minor issue but really annoying
So I realized if I unplug the sensors the reading will still continue bounce between 4500-5000 lux so im guessing its not an issue of the sensor itself there should be something else... Right?.. Please back me up can be it be caused by the drivers of the sensors ?
And i found this (last post) http://forum.xda-developers.com/showthread.php?t=1446005&nocache=1
Yes that picture in the last post could be it it could be a motherboard problem like that just be careful if you dont know what your doing
Sent from my GT-I9000 using xda app-developers app
Wondering if someone (hopefully more than one) can check something to see if this is an issue with my particular phone or something related to the software/hardware. It seems that when a call is placed or received, the proximity sensor goes to "far" and won't reset until it is uncovered and then re-covered. I have searched through the Verizon HTC One forums and have not found anything related to this issue.
If the proximity sensor is covered, and I make a call (via bluetooth headset (double click for last dialed)) or receive a call, the proximity sensor goes to the uncovered state. It then stays in that state until I uncover and then re-cover it. How I checked this was using Elixir 2 and checking the sensor data. I also set up variables in Tasker and Automagic.
So, this was my test procedure:
I start the sensor data in Elixir 2 for the proximity sensor. I cover the sensor with my finger (it now shows "near"). I use my bluetooth headset to place a call. The screen comes on with the current call. I back out of the current screen (the phone screen) and get back to Elixir 2 sensor data. The sensor now shows "far". From that point on, until I uncover the proximity sensor and then cover it, it shows far. I set up variables in Tasker and Automagic that show the same results.
I am running the stock debloated ROM. Rooted and S-Off.
EDITED:
So, this is the latest for my issue. I went from stock ROM to ViperOne 5.8.0. I am still getting the same results. So, I think I have eliminated the software side of it. Would that be right? So, it could be the firmware or the hardware? I'm still wondering if it's my phone only or if it is an issue with the HTC One in general. Is there anyone that can check this? Or give me another route to take?
I'm on ViperOne 5.8.0
Android 4.4.2
Senses 5.5
Any other info you might need, please just ask.
Some thing like that happened to me and i posted a thread and no answers.
My problem is that when the phone is in my pocket only one speaker is ringing(the lower one) and when on the desk face up both of the speakers are ringing.I noticed this affects only the call option(if i get a sms/notication and it's in my pocket/desk both of the speakers work).i've made all off the tests i can find am the problem seems to be from software.When i cover with my finger the sensor and some ones call s me only the bootom speker is ringing,when removing my finger from the sensor and receving cal SURPRISE both of the are ringing.
I've change the software ARHD 53 with ELEMENTALX Kernel.
Cid TMOB-101
alex.foto said:
Some thing like that happened to me and i posted a thread and no answers.
My problem is that when the phone is in my pocket only one speaker is ringing(the lower one) and when on the desk face up both of the speakers are ringing.I noticed this affects only the call option(if i get a sms/notication and it's in my pocket/desk both of the speakers work).i've made all off the tests i can find am the problem seems to be from software.When i cover with my finger the sensor and some ones call s me only the bootom speker is ringing,when removing my finger from the sensor and receving cal SURPRISE both of the are ringing.
I've change the software ARHD 53 with ELEMENTALX Kernel.
Cid TMOB-101
Click to expand...
Click to collapse
Well, seems to be the same here. I have this posted under the Verizon HTC One > One Q&A, Help & Troubleshooting as well as here and at the Android forums. It seems that either no one else is having this issue, no on cares or no one can run this test with free programs. I dunno. The problems I have is that I use by bluetooth headset most of the time. I am a blue collar worker and try not to pull my phone out of my pocket when my hands get filthy. But, when I take or make a call using the headset, the display kicks on and then stays on because I can't use the proximity sensor to turn the screen back off. Guess I'll have to try other routes. This sucks. LOL
I haven't heard of the other issue you are referring to. I can tell you that I have not had that issue with my One. Doesn't mean that it's not a problem. Have you checked the Sounds settings for pocket mode and quiet ring on pickup? If so, I think I would try to either get with Verizon about it or maybe even HTC. It definitely sounds like it could be a phone issue. But I'm kind of new to all of this.
Same problem here, when i'm in a call the screen go on, very annoying.
Now i'm trying this app "rezound prox sensor calibrator"
I've tried every possible solution including Pocked mode& Quiet ring.I still think this is a soft bug till further notice.
Lets hope we get a answer soon.Btw same here with the headset,I'm using a hands free and when i answer/call some one i must manually turn off the screen or its turn of by itself after 1-2 min i think.
psicobelico said:
Same problem here, when i'm in a call the screen go on, very annoying.
Now i'm trying this app "rezound prox sensor calibrator"
Click to expand...
Click to collapse
It's not a calibration issue. When the phone rings or you make a call via a headset and the proximity sensor is covered (ie. in your pocket or screen face down), the display kicks on and the prox sensor seems to default to "far" or "uncovered" (whatever term you like). It will remain at that value until you ACTUALLY uncover the sensor and then cover it back again.
alex.foto said:
I've tried every possible solution including Pocked mode& Quiet ring.I still think this is a soft bug till further notice.
Lets hope we get a answer soon.Btw same here with the headset,I'm using a hands free and when i answer/call some one i must manually turn off the screen or its turn of by itself after 1-2 min i think.
Click to expand...
Click to collapse
The problem I have is that while the display is ON and sitting in my pocket, I have a chance of butt dialing someone or starting programs that drain the battery in addition to the dsplay being on. Not to mention, with the display on in my pocket, the heat builds up in the phone. I guess I have a $700 butt warmer? LOL
I just bought a new m7 yesterday and my experience is horrible. It was all ok but after the lollipop upgrade everything is messed up.
Proximity sensor is totally fine because I have checked it with several apps...
problem one: the screen doesn't turn on after I remove tho phone from my ear while calling, so I can't hang up unless the other person hangs up.
Problem 2: Same thing with Lock Screen. It doesn't turn on..
Problem 3: my phone's touch is not working at a certain horizontal line along the screen, When I touch there, two touches are senses just right and left....
If anyone has encountered these problems, please give me a solution or find me a better solution.
ikyorince said:
I just bought a new m7 yesterday and my experience is horrible. It was all ok but after the lollipop upgrade everything is messed up.
Proximity sensor is totally fine because I have checked it with several apps...
problem one: the screen doesn't turn on after I remove tho phone from my ear while calling, so I can't hang up unless the other person hangs up.
Problem 2: Same thing with Lock Screen. It doesn't turn on..
Problem 3: my phone's touch is not working at a certain horizontal line along the screen, When I touch there, two touches are senses just right and left....
If anyone has encountered these problems, please give me a solution or find me a better solution.
Click to expand...
Click to collapse
looks like you are having hardware problem with the digitizer and the proximity sensor, you might want to send back this phone a get another one.
same issue 100% positive its a lollipop bug after a reset it gets fixed but if i update my apps through playstore it comes back
likhon02 said:
same issue 100% positive its a lollipop bug after a reset it gets fixed but if i update my apps through playstore it comes back
Click to expand...
Click to collapse
If the problem returns after updating your apps through the playstore then it's related to one of your app, not lollipop itself. One of your apps must be interfering with the screen or the proximity sensor.
Sent from my HTC One using XDA Labs
alray said:
If the problem returns after updating your apps through the playstore then it's related to one of your app, not lollipop itself. One of your apps must be interfering with the screen or the proximity sensor.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
anyways found the solution
http://forum.xda-developers.com/htc-one/help/lockscreen-issue-wake-lag-unlock-black-t3450726
Hi All,
My proximity sensor isn't triggering during calls (Possilbly at all?) causing me to accidentally put people on hold.
(very annoying! at least make a tone so I know I hit the button)
Is there a switch for that?
What's weird is that I don't see a HW test for the proximity sensor in the diagnostics screen (tapping on kernel version)
Edit -> settings -> system apps -> phone -> incoming call settings -> proximity sensor is ON.
Can someone whose proximity sensor is working download a sensors test app like https://play.google.com/store/apps/details?id=com.wered.sensorsmultitool&hl=en
and tell me if that detects your proximity sensor distance correctly? (or whatever app you want, just tell me which one).
- Frank
Go to Settings - About phone and tap 5 times on Kernel tab. You will get into test menu. There you can to test and calibrate proximity sensor.
sergmarin said:
Go to Settings - About phone and tap 5 times on Kernel tab. You will get into test menu. There you can to test and calibrate proximity sensor.
Click to expand...
Click to collapse
I don't see it. What is the test called?
What Rom are you running? I'm on 8.0.10.0
See pictures below. Test menu works on any firmware.
sergmarin said:
See pictures below. Test menu works on any firmware.
Click to expand...
Click to collapse
Well,that's damned odd.
My proximity sensor item is missing.
https://drive.google.com/open?id=0B6qmkujf4DlWVVFWVXBxTkJoRTA
xx
ChodTheWacko said:
Well,that's damned odd.
My proximity sensor item is missing.
https://drive.google.com/open?id=0B6qmkujf4DlWVVFWVXBxTkJoRTA
Click to expand...
Click to collapse
Just looked at mine and I have prox sensor as number 9. Sounds like you may need to flash an updated build.
I updated to developer rom and proximity appeared and was working.
I then re-updated to stable rom (8.0.12.0 i.e latest) and it dissapeared again!
ChodTheWacko said:
I updated to developer rom and proximity appeared and was working.
I then re-updated to stable rom (8.0.12.0 i.e latest) and it dissapeared again!
Click to expand...
Click to collapse
You already have the answer you're looking for. Guess the sensor is broken in the stable build. In this case, you may have to wait for the next stable release or use an alternate ROM.
ChodTheWacko said:
I updated to developer rom and proximity appeared and was working.
I then re-updated to stable rom (8.0.12.0 i.e latest) and it dissapeared again!
Click to expand...
Click to collapse
Confirm proximity sensor missing in 8.0.12.0
Unfortunately, it is also missing in 8.2.1.0 stable
On Chinese 8.2.3.0 and the settings are missing from the CIT list also ... with that said I don't depend on it anyways lol. Just checking things.
for some thick case the proximity sensors might have problem... need to reboot phone with case on to "register" the case thickness...
hi mi mix fans , I came through lot of applications,proximity sensor tests, procedures, secret codes etc . to get solution for "screen off during call and not on automatically" but i found the real solution in this is .. remove back cover which almost users use . , tpu transparent also and see whether it work during call ..yes,finally got solution. check yourself all test works properly and screen on during call when device is away from ear..if not ?? pls consider to clean sensor ..
Wanted to test it. I can see the test, but not sure how to test it. I still don't.
So I tried to the front microphone test to learn how to use these tests...
But it scared the s**! out of me. It's such a haunting noise! Is that normal?!
I'm on global stable, CIT proximity option doesn't show too. I think my sensor is bugged by my cover since when the device isn't covered the sensor works fine.
jaekry said:
Wanted to test it. I can see the test, but not sure how to test it. I still don't.
So I tried to the front microphone test to learn how to use these tests...
But it scared the s**! out of me. It's such a haunting noise! Is that normal?!
Click to expand...
Click to collapse
Yes, such an annoying noise.
i have same problem i just updated phone after proximity sensor not work why xiaomi not try before update this f*cking fw.
What I observed is after resetting when I tested it I came to know that sensors sensi
What I observed is after resetting when I tested it I came to know that sensors sensitivity distance increase up to an inch but starts dropping again as I move object in front of sensor 8 to 10 times and is reduce to 1 cm finally which is very less if you hold mobile in left hand ear but it works on right hand ear as proximity sensor is placed left of mobiles front side.I think it is a software problem which xiaomi should look in to.Sensor keeps on calibrating till it reduces distance to 1cm from nearly 1 inch that is 3 cms.This is very shameful for xiaomi that after so many years of experience they have not yet resolved this for Mi A1.
My proximity sensor also isn't working. I've tried to do this test we find on kernel tab, but I couldn't test it, it shows no options for me to calibrate or sth. Help me please!!
Same issue here. Phone just turns black, when I am calling people - difficulties to restart the display afterwards. Using Lineageos 16 - no chance to tab the kernel there. Dialing * # * # 64663 # * # * shows no results. Wandering, if this is a hardware or a software issue.