Like the title says, the proximity sensor on my s10 is flashing. (Little circle above the battery percentage)... Everything i find online says this should only happen during a call. But I'm not in a call, nor have i been in a call at any point in the day. Phone apps aren't open.
Only thing that's changed recently is I've update to the newest Good lock earlier today. Just noticed the flashing pixel.
Any ideas, or is this happening to anyone else?
U.s. snapdragon on Sprint
Related
A few days ago I got the Nokia Lumia Icon from Verizon Wireless. Overall, the phone is great as far as Windows phone go. This is my work phone and I use an Android phone as my person cell phone.
I have discovered that during calls periodically that the proximity sensor gets stuck in detected on the Lumia. Basically, whether sensor is covered or not, the phone's display goes dark during calls. This does not happen on every call but it does on most.
Does anyone know of a fix? Is there a patch / update coming soon?
Thank you,
gabato
I found a post on WPCentral that said to blow in to the 3.5 headphone jack and it would fix the issue for a while. Well I did it - heck no one has replied with a fix yet. So what did I have to loose. It worked. Now I want to see for how long.
Remember, the Icon is still extremely new. I have no clue if/when I'll end up getting an Icon. This place hasn't had much Verizon talk anyways....
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
so in short this problem has plagued the phone since day one and i suspected a HW issue since nothing fixed it. for those who dont know whats im talking about, you are lucky. the issue is basically that the proximity sensor is missed up so the screen will light up when you are in a call or listening to Whatsapp/Telegram voice messages.
The Solution:
The problem, turned out, was caused by the factory screen protector that came already applied to the phone. i removed it after it was damaged and also removed the case (Spigen Rugged Armor Case), cleaned the phone and VIOLA its working perfectly fine now...
i hope it works for everyone else.
So, what you are saying is:
Since when this phone got launched in May 2019, not a single user facing the proximity sensor issue had the ingenious idea to remove their factory applied screen protector and you are the first one to come up with this "fix"?
I am really sorry to be this discouraging but: This ain't it chief.
Good that it fixed your perception of the issue though
Comrade, the issue is far graver than that. OnePlus 7Pro does not have a proximity sensor per se. It uses software (an ai I think) to "guess" whether to turn on the screen or not which is why listening to voice notes gets crazy...
amirage said:
Comrade, the issue is far graver than that. OnePlus 7Pro does not have a proximity sensor per se. It uses software (an ai I think) to "guess" whether to turn on the screen or not which is why listening to voice notes gets crazy...
Click to expand...
Click to collapse
Even though it does have an infrared sensor under the screen (that has been proven), i agree with you that it seems to be using something like that.. Curiously, the proximity sensor once fired when i flicked off my lights in my room.. This indeed leads me to believe there is more going on than just a simple infrared proximity sensor..
But yeah, i don't think removing the stock screen protector "fixes" the thing.. It may improve things but i doubt it's a fix.. As i said, this phone has been out for a while and people would have noticed if removing the screen protector fixes the proximity sensor for good..So yeah, cheers mate.
I took the screen protector off before I turned the phone on for the first time. I still get the screen lighting up while I'm on a call, often muting it with my cheek.
I must be lucky but at the moment I have no such issue with my new OP7P (MFD: 2019/05). RR Rom. Still have the screen protector on it. What's the MFD of your unit ?
i have problem with my oneplus since i rooted this phone
after root i have installed pixel expereince rom
when i called i found proximity sensor not working
now almost 6 months no fixed i'm stock oos
please help me there is no guard on my phone also no cover
The simplest solution for me has been to use a Bluetooth headset. I rarely use it without it.