Hey all,
Has anyone observed erratic proximity sensor function during calls? I often find that it works for one toggle (i.e. putting phone to ear/wave hand), but subsequent toggles/calls do not trigger the screen to go off.
I have tried various stock ROMs (rooted), but no luck. I'm wondering if the issue is common on all stock builds, hence the question.
Any ideas?
ringo0800 said:
Hey all,
Has anyone observed erratic proximity sensor function during calls? I often find that it works for one toggle (i.e. putting phone to ear/wave hand), but subsequent toggles/calls do not trigger the screen to go off.
I have tried various stock ROMs (rooted), but no luck. I'm wondering if the issue is common on all stock builds, hence the question.
Any ideas?
Click to expand...
Click to collapse
Anyone??
I have the opposite issue. The screen does turn off during call, but not on until the other puts back
Related
My proximity sensor seems to have stopped working (always gives a value of 0.0) as a result whenever a call is placed the screen goes off and i cant do anything at all, cant even end the call. This seems to be hardware problem, as cleaning the area is not helping.
Is there a way to disable the proximity sensor completely/permanently?
The only working way i found was using the "Hardware Disabler" app in play store and disabling /sys/bus/platform/drivers/proximity, but that makes the phone as slow as hell. How would I go about deleting this folder otherwise? Root Explorer is not allowing me to do this.
All the other solutions i found on the net do not help (using proximity recalibration, adding lines to build.prop, putting a script in init.d - Though perhaps I am not using it correctly).
Someone please help. The problem is driving me crazy.
Note: using CM9.0 RC2
Nobody has any issues with the proximity sensor on their phones?
And is there no actual way to disable it?
nobody here who can help?
manish_bhaumik said:
Nobody has any issues with the proximity sensor on their phones?
And is there no actual way to disable it?
Click to expand...
Click to collapse
I still need help on this?
Hi, last time I tried MIUI rom and iinm there is an option to disable the proximity sensor. But, if you doesn't like MIUI.. I am don't know any other workaround for it anymore.
Or try some different ROM to make sure if it is actually hardware issue or software issue.....
Use miui rom and press on dial and then menu...Again press on setting and Answer setting .. You will find there the option to disable proximity sensor..
Yes, another proximity question!
I have trouble with this sensor using 3rd party apps.
On system it works fine without a problem (screen on/off during phone call never had any problems)
but any apps which use this sensor stops working after rebooting.
-Gravity screen on/off
-Automaton gestures
-Automate it!
These are the apps I tried and encountered problems with...so pretty much all of them!
The sensor works, cpuz sees it working with both distances 3cm near and 10cm far, but apps don't :S
For example if I try to record sensor state in automate it it just reads '10 far' and notihng else.
aamof rules with sensor far work fine but with near don't....
I encountered this problem both across 10.1 and 10.2 and different roms...anybody else encountered this isse?
I recalibrated tegra.so from adb...I'll try to go back to stock and try from there recalibration but seen thtat it "works"
I'm not sure how that is going to help.....
Rudjgaard said:
Yes, another proximity question!
I have trouble with this sensor using 3rd party apps.
On system it works fine without a problem (screen on/off during phone call never had any problems)
but any apps which use this sensor stops working after rebooting.
-Gravity screen on/off
-Automaton gestures
-Automate it!
These are the apps I tried and encountered problems with...so pretty much all of them!
The sensor works, cpuz sees it working with both distances 3cm near and 10cm far, but apps don't :S
For example if I try to record sensor state in automate it it just reads '10 far' and notihng else.
aamof rules with sensor far work fine but with near don't....
I encountered this problem both across 10.1 and 10.2 and different roms...anybody else encountered this isse?
I recalibrated tegra.so from adb...I'll try to go back to stock and try from there recalibration but seen thtat it "works"
I'm not sure how that is going to help.....
Click to expand...
Click to collapse
yeah, i noticed in viber screen doesn't turn off when you put your phone enxt to your ear. i dont have any other apps that use proximity sensor other than phone app, but that one works without issues.
the issue persists in stock as well as custom roms. no idea how it was on ics, though
It also appears on stock?! wow never would've thought...
It's a pretty considerable bug to have never been mentioned before...
all problems with proximity encountered so far always seemed caused by bad calibration..
this kinda sux :S
Devs and wise people, do you think this could be caused by the fact that the 'near' state is set at 3cm reading and 3rd party apps look for 0 distance with 0% tolerance to have widespread compatibility?
Do you think it is possible to change these settings?
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
Currently using PixelExperience Plus ROM. Was using HavocOS before this. There were similar issues in both the roms.. The proximity sensor just won't work during calls. Phone needs a restart to fix this.. goes back to problematic in a short while..
The autobrightness sensor issue is less frustrating.. waking up the device the brightness gets stuck at about 50%. The slider does nothing.. locking the screen and waking up again solves it. Minor issue..
But.. does anyone have a fix?
Same problem here with latest oficial rom. Randomly screen goes black in a call although the phone is on a table.
Same problem here
Why do Xiaomi seem to have such a problem with proximity sensors?
The one on my Note 7 doesn't work properly and a google search reveals complaints about sensors on many models.
It's not as if they are rocket science any more.
Could this also be the reason when I receive a call the phone screen on some occasions didn't even light up and I have to double tap to see who's calling. I really hope it's something they can fix.
Did anyone get a fix? I still have this goddamn problem! Even with the latest evolution x rom or pixel experience rom (tried the latest version released like days back for both roms). This problem started right after I unlocked my bootloader and flashed a custom ROM and the problem is present in EVERY custom rom that I've tried. Please help me out with a fix as this is really annoying and the phone is practically useless. As soon as I make a call or get a call my display simply shuts down and doesn't switch on until 30 secs after the call ends. So my display is basically off for easy 2-3 minutes. Can't use my phone then. This sucks when I've dialled a wrong number or want to cut the call myself because I can't do any of that!
Did anyone get a fix for the proximity sensor issue where the screen shuts off during a call? I still have this goddamn problem! Even with the latest evolution x rom or pixel experience rom (tried the latest version released like days back for both roms). This problem started right after I unlocked my bootloader and flashed a custom ROM and the problem is present in EVERY custom rom that I've tried. Please help me out with a fix as this is really annoying and the phone is practically useless. As soon as I make a call or get a call my display simply shuts down and doesn't switch on until 30 secs after the call ends. So my display is basically off for easy 2-3 minutes. Can't use my phone then. This sucks when I've dialled a wrong number or want to cut the call myself because I can't do any of that! Also I used a sensor testing app to check if the proximity sensor is working, and turns out it's working completely alright! Responds properly to relevant distance input. And I tested multiple times just to make sure