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.
Related
Dear fellas,
Although this topic has been briefly discussed in various locations, it hasn't gotten "big" enough.
I know a number of ya guys are having this problem. The touch-sensitive action button used to focus does not focus the camera (and yes, I have set it to "touch & press").
Mine works intermittently, in fact, doesn't work most of the time. I know it's 100% not a hardware problem, as the button lights up and brightens up my screen according to normal behavior. Now I'm wondering, for those guys who don't have this problem, do U have a different version of the camera app?
K.. mine's the stock HK 1.93.831 ROM and my cam app is version 6.00 (build 31516).
I'm not sure what causes this problem. Although I'm not a camera freak, but this prob makes my baby "imperfect".
Pls post yr ROM and camera version (I wonder if there's a difference) and state if youre experiencing this problem. Thanks!
Hi MasK,
I'm having the same problem as you, the "touch & press" feature didn't work most of the time.
I'm using HTC SG ROM 1.37.871.3, camera version 6.0 (Build 31364).
I used to think the camera didn't focus properly until I took some time to play with it. It's pretty slow, but mine seems to work. When I touch the button, it will take anywhere from 1-5 seconds to focus, and then the cross-hair turns green and beeps to indicate focus lock. At first I didn't realize I needed to wait for the beep, so my shots were out of focus. Seems to work fine now that I know that.
I'm currently on stock 1.37.401.3 with camera 6.0 Build 31364 ... same as previous post, just a different ROM region, which I doubt makes a difference.
i have a similar problem where i run the camera app, then the 1st time i place my thumb over the button nothing happens, but if i take my thumb away and try again it will work fine.
It will continue working fine untill i restart the camera app, just never registers the 1st attempt.
This does show that there is some serious prob with this functionality. For me, it's the first time that has a higher chance of working.. not subsequently.
How abt the rest? We needa find out what's causing this!
upz...
Anymore ppl having this prob?
Same here. Most of the time, including 1st time also fails.
+1, most of the time I have to click on the button to do the focus + photo. When I just touch, the camera tries to focus but the square doesn't become green. Sometimes there's no white square at all.
Hi,
mine recognizes the first touch so it focuses correctly but after i take the picture, it doesn't focus anymore when i touch it. actually i just found out about this focus thing and tested. until now i always just pressed the button when trying to make pictures and it always makes a focus and then capture the image. is this OK or it makes them better if i first let him focus and then press the button all the way?
p.s. i do have "touch and press" selected.
p.s.2: is there any way i can change exposure time or something like that so my pictures won't get blurry when my hand shakes or something? many of my pictures are fuzzy because i don't really have a steady hand :-s
Best regards,
Florin
GeckoDev said:
I used to think the camera didn't focus properly until I took some time to play with it. It's pretty slow, but mine seems to work. When I touch the button, it will take anywhere from 1-5 seconds to focus, and then the cross-hair turns green and beeps to indicate focus lock. At first I didn't realize I needed to wait for the beep, so my shots were out of focus. Seems to work fine now that I know that.
I'm currently on stock 1.37.401.3 with camera 6.0 Build 31364 ... same as previous post, just a different ROM region, which I doubt makes a difference.
Click to expand...
Click to collapse
Yep that's how it works and I don't seem to be having problems, just tried doind a few shots and it works perfectly.
Everytime I touch the center button the white square appears and the camera does the autofocus until it turns green. Then I change the orientation and do the same again. I just did it 6 times in a row and the autofocus worked perfectly all the times.
I had this problem with all my previous ROMs.. I am now on Bepe's 0.96 which has the latest camera app and the problem is no longer there - I can touch and press to activate the autofocus as many times as I want after shooting as many photos as I want. No problems now.
Huey85 said:
I had this problem with all my previous ROMs.. I am now on Bepe's 0.96 which has the latest camera app and the problem is no longer there - I can touch and press to activate the autofocus as many times as I want after shooting as many photos as I want. No problems now.
Click to expand...
Click to collapse
Cool.. so it goes to show it's a pure firmware issue. I'm wondering perhaps it's due to registry tweakings that creates this problem.
Any more feedbacks?
Is there a difference in quality if it makes the focus on touch and picture on press versus focus and picture on press?
cannabis23 said:
Is there a difference in quality if it makes the focus on touch and picture on press versus focus and picture on press?
Click to expand...
Click to collapse
No difference in quality, however with the "touch-then-press" focus you see a focused picture on the display before taking the shot.
Mask,
Can you tell me what is the camera app version in Bepe's 0.96 Rom?
I just changed the camera capture setting to "press" rather then "touch and press".
Now all I have to do is point at what i want. Then just press the button down and it does all the auto focussing itself and then takes the pic.
Couldn't be easier.
Roy_Drage said:
I just changed the camera capture setting to "press" rather then "touch and press".
Now all I have to do is point at what i want. Then just press the button down and it does all the auto focussing itself and then takes the pic.
Couldn't be easier.
Click to expand...
Click to collapse
I actually prefer the 'touch and press' option, because I might end up needing to re-adjust my position before taking the shot.. and having the 'touch' to autofocus, before 'press' to shoot allows me to do so.
@MasK: I don't think it's a firmware issue or related to registry tweaks, but more a issue related to the camera app - bepe noted that it was a newer version (thus you won't see the Resolution icon in the Settings anymore - you can still change the resolution via Advanced settings). You could ask bepe more about the camera app and whether he did any tweaking in regards to the camera.
Huey85 said:
I actually prefer the 'touch and press' option, because I might end up needing to re-adjust my position before taking the shot.. and having the 'touch' to autofocus, before 'press' to shoot allows me to do so.
Click to expand...
Click to collapse
Yeah I know what your saying, I tend to just point n click, let it auto-focus once clicked and take the pic. As long as I'm pointing at what I want and I'm as far zoomed in as I choose then it's fine. I'll take a load at a time and then just delete the unwanted ones later.
But none the less I think the general point is that everything should work!
Roy_Drage said:
..But none the less I think the general point is that everything should work!
Click to expand...
Click to collapse
Quite right. I do not see why HTC overlooked this problem. Seems to me that HTC rushed the release of the Diamond without going through more intense test phases.
Huey85 said:
Quite right. I do not see why HTC overlooked this problem. Seems to me that HTC rushed the release of the Diamond without going through more intense test phases.
Click to expand...
Click to collapse
Completely agree, it's plain to see now that the phone was rushed. I know for a fact that if I hadn't found this site and wasn't able to flash the thing with new ROMS and applications etc then I probably wouldn't of bought it.
In effect this site is doing the work that HTC should of done in the 1st place. We shouldn't be finding ways around their problems by simply saying "oh doing it this way doesn't bother me". It would of been nice to have the thing working smoothly from release.
But then again this is half the fun right? Mucking around with new ROMs and apps to set it up how each individiual likes.
I know that I would feel sorry for anyone with a brand new HTC Touch Diamond that is still at factory settings!
The one I am running now pisses on the phone it was 2 weeks ago
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
My Nexus 6 seems to have an issue from day one and is still present with the 5.0.1 update and the most recent camera update. I'm unlocked and unencrypted.
When using the camera, any camera app, the viewfinder and ultimately the photo/video comes out blurry when shooting in landscape. If i shoot in portrait, the viewfinder and the photos are sharp.
In landscape is starts clear and sharp and then quickly changes to being blurry. Even resting the phone on a still surface it is always blurry. Lighting conditions or shooting mode don't make any difference.
I attached two photos showing the difference, both handheld.
It's almost like something is wrong with the OIS in landscape. Hardware issue?
did you touch to focus or did you just point and shoot?
simms22 said:
did you touch to focus or did you just point and shoot?
Click to expand...
Click to collapse
touch to focus... it actually begins to focus and then it looks like the sensor is shaking on the screen and shows up in the photos. I have no issues at all when in portrait mode.
This even happens when the camera is sitting on a still surface so its not my hand shaking.
This is with the camera sitting stationary on my desk and a 10/sec timer
mine did the exact same thing. the OIS never fully settles due to a hardware defect. i got a new one from T-Mo and returned my defective one and the problem has gone away.
http://forum.xda-developers.com/showpost.php?p=57450996&postcount=78
Lucke said:
mine did the exact same thing. the OIS never fully settles due to a hardware defect. i got a new one from T-Mo and returned my defective one and the problem has gone away.
http://forum.xda-developers.com/showpost.php?p=57450996&postcount=78
Click to expand...
Click to collapse
Thanks for the info and helping verify its a hardware issue. guess I will be calling T-MO then. Where they hard to convince in replacing it?
drwolcot said:
Thanks for the info and helping verify its a hardware issue. guess I will be calling T-MO then. Where they hard to convince in replacing it?
Click to expand...
Click to collapse
i was lucky to call and complain about it within the 14 day buyers remorse period so they could send me a brand new one instead of a possible refurbished one, but it was like pulling teeth with them. i had to explain that it was a hardware issue several times before they agreed to send me another one. after several phone calls later in the next few days, i finally got someone who was willing to do it then and there while on the phone.
good luck :good:
I have about the same problem with my more then 1 year old Nexus 6. After my nexus 6 fell of my bed (with a tpu case and no visible damage) it seems that i can only get the camera to properly focus while holding it at 90 degrees (so with the camera sensor towards my right hand) and while holding it at 180 degrees (so upside down) 0 and 270 degrees (camera towards left hand) the camera focusses, during the focussing it's focused for like a fraction of second and then the blurriness/vibration starts, in both camera and video mode.
So thanks for this topic, i guess i'm ordering a replacement camera module.
Replacing the camera module has fixed my focusing problem. The module itself was around 13 dollars on aliexpress. For anyone that's facing focussing/ois problems with the camera, you can easily replace the module yourself.
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
andrewd71 said:
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
Click to expand...
Click to collapse
I was having the same issue when I had the edge notification app installed that makes the screen light up around the camera when you get a notification.
Uninstalled and no issues since
Tap to wake not working for me
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
andrewd71 said:
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
Click to expand...
Click to collapse
Do you have any notification or edge lighting apps installed?
Mdizzle1 said:
Do you have any notification or edge lighting apps installed?
Click to expand...
Click to collapse
No, I've not installed any apps like that.
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
andrewd71 said:
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
Click to expand...
Click to collapse
Not using a case. It's sporadic. Tap to wake works fine for a while and then stops. The issue during calls is constant. Not major issues just niggles.
Not noticed any bugs with ambient display, but it has used 20 percent battery in 21hrs.
Seems a bit high to me, have just turned it off, not worth a 5th of my battery.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
RockStar2005 said:
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
Click to expand...
Click to collapse
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
czm said:
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
Click to expand...
Click to collapse
Yeah. Seems like more and more people are noticing and like me reporting these various issues to Google. So hopefully the next batch will include fixes for all this stuff.
I have same two problem with AOD, touch to wake up and screen off/on when calling.
DOMIN_ said:
I have same two problem with AOD, touch to wake up and screen off/on when calling.
Click to expand...
Click to collapse
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
RockStar2005 said:
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
Click to expand...
Click to collapse
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
czm said:
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
Click to expand...
Click to collapse
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Morpherios said:
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
Click to expand...
Click to collapse
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
RockStar2005 said:
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
Click to expand...
Click to collapse
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Morpherios said:
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Click to expand...
Click to collapse
Hey Morpherios,
Ok.............downloaded that app and tried it out several times. It passed some of the time, but then I'd try it again a few minutes later and it would fail on both tests. Ughh!!
You think even though it passed a few times I still need to replace it?
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.