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
Related
Hey guys, got my Focus S about a month ago and everything is working fine. I have noticed one semi-minor bug and want to figure out if its software/hardware related.
On shorter calls (30 seconds-1 minute), when I move my phone away from my face, the screen wakes back up like normal so I can hit End Call.
However, on longer calls (more than 3-4 minutes), when I move the phone away from my face, the screen stays black, and only wakes up when the other person hangs up, after 4-5 seconds.
Its as if the proximity sensor times out, and forgets that my face is there? This seems like a software issue since it works normal on shorter calls. Anyone have any insight on this? I'm still within thirty days of purchase with ATT so I can swap out my unit by this Sunday.
Thanks!
My Focus does this as well, it's always done it and bugs the hell out of me.
Well that makes me feel a lil better >... but it does seem to be a software issue.
Just a theory but, if the samsung focus S has the diagnosis app you could try recalibrating the proximity sensor. There is a thread that has already adressed calibrating the proximity sensor on the original samsung focus.
The diagnosis menu for the Focus S is different than that of the Focus... theres no way to calibrate the proximity sensor on our S's..
I have noticed this same thing. I thought that sensor was real neat until it didn't work all the time. I am still within the window I am contemplating taking jt back for the titan. Not sure yet though. Just seems to maybe be a better phone...
I'm pretty sure I remember my Focus S doing this once. I'll try and test it today and I'll get back to you.
Absolut` said:
The diagnosis menu for the Focus S is different than that of the Focus... theres no way to calibrate the proximity sensor on our S's..
Click to expand...
Click to collapse
please dont take offence, but i dont quite thats an accurate statement. i know many of the diag menu options arent available in the focus s as they were in the focus, but weeks back i do remember testing this function...although i dont recall in what diag function. if i get time, ill see if i can find that function and report back.
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
Hi all,
So a couple months or so ago, my dad got an S5 and handed down his Droid DNA to me which I promptly rooted and rom'd. Fast forward to last week (didn't take long), and I dropped the DNA and broke the screen. So while I'm waiting on a new screen to arrive for the DNA I activated my trusty Bionic. Only now, again only a short time since last use, the proximity sensor is giving me issues which it hadn't before. Now, as soon as I place a call the screen goes black and won't turn back on until the caller on the other end hangs up, as well as the sensor giving off that faint red light I've read so much about. I had slimkat installed and thought that was the issue, so wiped clean and installed PA. The problem persisted and I just tested a call on stock and now it's happening on stock too! Whereas beforehand it wasn't
I've read that an app can be causing this to happen, but between my stock rom, and PA, there are no common "running" apps so that can't possibly be the problem unless it's one app on stock and a separate app on PA which seems unlikely. I have replaced the screen before, but I used the phone for probably another 8-10 months after that before activating the DNA and putting the Bionic on the shelf, during which time I had never once had this issue.
Does anyone have any experience with this? If so what did you do to fix it? It's a super annoying problem :/
Thanks in advance, hopefully somebody's got the answer I need!
EDIT: Just tried blowing really hard through the speaker port while on stock in case something got lodged in front of the senso, and that appeared to fix it! Made a voicemail call and the screen stayed on while allowing use of the keypad. Switching boot options in safestrap to PA to try there.
...no dice in PA faint red light still, and black screen with no access to keypad. Maybe a rom issue, will investigate further I guess...
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!
Hi,
I have installed Pixel Experience rom and I like it a lot, however every month or so battery drain starts and makes the phone not usable. So I switched to Miui.eu 13 rom, which is great in terms of battery life, however there is one thing that I like much better on PE, the proximity sensor behavior. On PE, If I keep the phone held on my face after listending to a whatsapp voice message or after having a call, the screen remains off untill I move the phone away from my face. While on Miui it instantly turns back on once the call is finished without any delay. Is it possible to modify the behavior to be similar to PE?
Thanks