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,
I am encountering the light and compass Sensors not working after 4.4.4 update on my Z1.
I have checked the service menu and it shown no value to both the sensors... Need help to solve this... I am rooted btw..
Yes! I have had this problem for a few months now, but no-one on this forum seems to be experiencing this so I thought it might just be my phone.
The light sensor issue for me is intermittent, if I restart the phone then it would be fine for a day or two before it stops working.
The compass however simply does not register, the service menu shows no value for it and in Google Maps the arrow is always pointed North.
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...
My rear camera was working last night and this afternoon it(Motorola Stock Camera) suddenly started telling me to restart the camera while Google Camera says that it can't connect to the camera. It's weird because I haven't dropped or treated the phone roughly lately and there haven't been any updates that would effect it.
Since the problem started I've done multiple restarts and completely wiped the device. The problem continues to persist. By experimenting with other camera apps I was able to figure out that the front facing camera still works fine. I'm worried that it is a hardware issue.
Mine just went out today. Mine happens to be an Asurion refurb. Anyone have any insight to this problem?
Hi everyone,
Almost all sensors stoped working after few days on my brand new Pixel 5 :
Failing sensors :
- Proximity sensor
- Accelerometer
- Gyroscope
- Compas
And maybe others I don't know of...
Fingerprint & cameras are still working.
I've contacted Google support, and they advise me to clean my screen :-/
I'll try a factory reset today before asking for a replacement unit, but my hope is low...
Anyone facing the same issue ?
Any advise ?
Edit :
After a factory reset : same situation
Same here. Had phone for about ten days. All seemed to work. Then thinks went weird over several days. First thing I noticed when going to hang up a call I was no longer presented with phone dialler screen. During calls phone was also spontaneously switching to handsfree. I suspect this was wall tilt related. Then camera images were in incorrect orientation. Google photos not longer rotating images and so on. Installed a sensor app and it reported gyroscope as missing. Clean booted - no change. Factory Reset and still no change. Arranged for an exchange with Google. While waiting for that to pan out, after about a day the gyroscope has come back to life. Although presently reporting no compass. Doe the P5 have a compass?
Anyhow given it working again now I am wondering if some power saving activity is killing the Gyroscope? Waht was the out come with your sensor failure. Did they recover or did you need to exchange?
logger said:
Doe the P5 have a compass?
Anyhow given it working again now I am wondering if some power saving activity is killing the Gyroscope? Waht was the out come with your sensor failure. Did they recover or did you need to exchange?
Click to expand...
Click to collapse
I tried a random app from the store : Sensor Test with my bad unit and it reported 0 sensor !
I've exchanged my P5 and now the same app reports 30 sensors.
While waiting for the exchange , mine never came back to life : can't rotate, screen stayed on during calls (and auto brightness not working), compass was not working in Maps...
Also on the faulty unit I noticed that the OTA update tooks ages (30 minutes or so, for a ~30MB update). On the new unit, the same uptate took just a normal reboot time.
Thankyou for the update.
While mine has a working gyroscope (at the moment) the proximity sensor is still borked and the screen stays on during calls. I just installed the Sensor Test app and it says I have 16 sensors!
30 for me
Sent from my Pixel 5 using Tapatalk
30 sensors also for me.
Oh my god yes exactly this happened to my phone since yesterday. No auto rotation, no auto brightness, no tap2wake.
I have to send mine back, I hate it. Sensor app does not recognize a single sensor. Factory reset didn't help either
When rebooting like 10 times it changes between 0, 1 and 16 sensors.
I factory reset my phone again and that made it worse. Has gone from 16 to 0 on Sensors Test!
Has lost screen rotation again.
logger said:
I factory reset my phone again and that made it worse. Has gone from 16 to 0 on Sensors Test!
Has lost screen rotation again.
Click to expand...
Click to collapse
At this point, you should contact Google Support and ask for an exchange.
Like my old one, I doubt this is a software issue...
I hope my new one does not have this flaw.... but this definitely hurt my confidence in P5 devices....
Sounds like issue with corrupt persist partition caused by update gone wrong.
dannejanne said:
Sounds like issue with corrupt persist partition caused by update gone wrong.
Click to expand...
Click to collapse
Indeed ! I didn't know about this.
But it seems that the solution is to root the device, and this void the warranty (Google asked me if it was rooted before the exchange).
Weird. It did not happen to mine right after an update, more like 20 days later. Btw Google did not ask me if I rooted the device, which I haven't, but I did unlock the Bootloader for a short period of time to use the android flash tool from Google.
I'm not very familiar with partitions on android but all I can say is that a newly flashed stock firmware from Google itself did not help me
All my sensors work according to that app - it shows 30 sensors every time I launch it - except the proximity sensor sometimes does not actually work right. I was noticing an issue because KinScreen would think my proximity sensor was covered and would turn the screen off because the proximity sensor looked to be covered when it was not, even though the app should have kept the screen on. I downloaded multiple sensor testing apps and the proximity sensor works most of the time but sometimes it does not. Weird. Not sure if I should exchange the phone, I got this with AT&T.
AlEsC said:
At this point, you should contact Google Support and ask for an exchange.
Like my old one, I doubt this is a software issue...
I hope my new one does not have this flaw.... but this definitely hurt my confidence in P5 devices....
Click to expand...
Click to collapse
Took a couple of weeks, but I now have a replacement unit. 30 sensors showing and all working properly now. I took it for granted how reliant these devices are on having sensors working for basic things like the phone to work properly. Glad I found this thread and was able to get it sorted out. thanks for the help.
I had to get a replacement PIxel 5 through AT&T for the broken proximity sensor. This one works fine.
Couple of weeks?
I got a new device within 4 days where 3 days were for shipping
Just out of curiosity, am I the only one Google asked if I have rooted my device before sending it back ?
They asked me 5 questions for the warranty (I live in France/EU btw):
- Has the device been impacted, or is the screen damaged?
- Has the device come into contact with liquid?
- Has the device been in contact with a heat source?
- Has the device been rooted?
- Has the device been repaired by unauthorized personnel?
AlEsC said:
Just out of curiosity, am I the only one Google asked if I have rooted my device before sending it back ?
They asked me 5 questions for the warranty (I live in France/EU btw):
- Has the device been impacted, or is the screen damaged?
- Has the device come into contact with liquid?
- Has the device been in contact with a heat source?
- Has the device been rooted?
- Has the device been repaired by unauthorized personnel?
Click to expand...
Click to collapse
I started an RMA process on their website and no I'm not 100% sure about the other stuff but I'm sure they didn't ask if I was rooted.
Germany
I see where Google announced that a fix in the December update could possibly fix the sensor issue for some. I'm guessing you guys got the update and it didn't work huh.
idk I got a new device in december