My face/ear hits number keys while I'm talking on the phone which sounds off tones and is annoying when talking to someone, especially when I'm talking to my customers. Is there any way to lock the keypad while talking on the phone?
southernblonde said:
My face/ear hits number keys while I'm talking on the phone which sounds off tones and is annoying when talking to someone, especially when I'm talking to my customers. Is there any way to lock the keypad while talking on the phone?
Click to expand...
Click to collapse
Your screen should go off when you're on the phone, did you make any changes?
BWolf56 said:
Your screen should go off when you're on the phone, did you make any changes?
Click to expand...
Click to collapse
I've made no changes.
What ROM are you running.
There's a proximity sensor that is supposed to shut off the screen when the phone is next to your head.
If you hold the phone and place your finger across the top where the ear speaker is, does the screen shut off?
If it doesn't shut off, then you need to check if it is hardware or software prob.
You can get apps that will give you status on the sensor on Google play. Example, Phone Explorer.
With it, you can move your finger over the ear speaker area near the top of the phone and see if the sensor is working. Its range is up to 5 cm, about two inches.
There are also some settings in some roms to override the proximity sensor staying on whenever the headphone jack is in use. The setting in CM10 is that the proximity sensor is ignored when the headphone jack is in use, or not ignored, if you so choose in settings.
Sent from my SGH-I897
laughingT said:
What ROM are you running.
There's a proximity sensor that is supposed to shut off the screen when the phone is next to your head.
If you hold the phone and place your finger across the top where the ear speaker is, does the screen shut off?
If it doesn't shut off, then you need to check if it is hardware or software prob.
You can get apps that will give you status on the sensor on Google play. Example, Phone Explorer.
With it, you can move your finger over the ear speaker area near the top of the phone and see if the sensor is working. Its range is up to 5 cm, about two inches.
There are also some settings in some roms to override the proximity sensor staying on whenever the headphone jack is in use. The setting in CM10 is that the proximity sensor is ignored when the headphone jack is in use, or not ignored, if you so choose in settings.
Sent from my SGH-I897
Click to expand...
Click to collapse
I'm using CM9 in Slim Bean 3.1.0 I called my other phone number and the phone screen did turn black whenever i was holding it against my ear. When I take calls for work, I have to press 1 to receive the call and I'm not sure whats happening because when i pressed 1 the screen turned black.
I read that dialing *#*#0588#*#* will change the proximity sensor but it didn't work for me.
I will check out a program you mentioned because I've had two customers hang up on me, they thought we just had a bad connection with all the tones. LOL Thank you!
southernblonde said:
I'm using CM9 in Slim Bean 3.1.0 I called my other phone number and the phone screen did turn black whenever i was holding it against my ear. When I take calls for work, I have to press 1 to receive the call and I'm not sure whats happening because when i pressed 1 the screen turned black.
I read that dialing *#*#0588#*#* will change the proximity sensor but it didn't work for me.
I will check out a program you mentioned because I've had two customers hang up on me, they thought we just had a bad connection with all the tones. LOL Thank you!
Click to expand...
Click to collapse
I found that someone had the same problem http://forum.xda-developers.com/showthread.php?t=842049&page=2 and it was corrected with Gingerbread....but now is it only me that's having this problem with Slim Bean/Jelly Bean?
southernblonde said:
I found that someone had the same problem http://forum.xda-developers.com/showthread.php?t=842049&page=2 and it was corrected with Gingerbread....but now is it only me that's having this problem with Slim Bean/Jelly Bean?
Click to expand...
Click to collapse
Here is what came up for Proximity in Phone Explorer:
Name: GP2A Proximity Sensor
Vendor: Sharp
Version: 1
Power: 0.8
Resolutio:n 5.0
Max: 5.0
Range:
Inches: 1
When I ran my finger in front of the sensor, it sensed me only about 1/2 inch away.
southernblonde said:
Here is what came up for Proximity in Phone Explorer:
Name: GP2A Proximity Sensor
Vendor: Sharp
Version: 1
Power: 0.8
Resolutio:n 5.0
Max: 5.0
Range:
Inches: 1
When I ran my finger in front of the sensor, it sensed me only about 1/2 inch away.
Click to expand...
Click to collapse
I would change the inches range to 2-3 inches, perhaps that will help.
BWolf56 said:
I would change the inches range to 2-3 inches, perhaps that will help.
Click to expand...
Click to collapse
Do you know how to change it? Looks like Phone Explorer won't allow me to change anything, just observe.
southernblonde said:
Do you know how to change it? Looks like Phone Explorer won't allow me to change anything, just observe.
Click to expand...
Click to collapse
I'm not sure if there are apps that allow it, although, script/code can be made so users change it, I'll look into it. Feel free to look for a app that allows it though!
EDIT: Sooo I found the needed coding but it's for an app build. I'm hoping someone already built an app for this though.
BWolf56 said:
I'm not sure if there are apps that allow it, although, script/code can be made so users change it, I'll look into it. Feel free to look for a app that allows it though!
EDIT: Sooo I found the needed coding but it's for an app build. I'm hoping someone already built an app for this though.
Click to expand...
Click to collapse
Right here in the Genius Forums! lol
http://forum.xda-developers.com/showthread.php?t=951858
Oh crap! Will it work with my phone?
I found this app: Rezound Prox Sensor Calibrator in Google Play store. I'll let you know how it goes!
hmmm,
have you got a dirty screen protector or anything else blocking those little windows next to the ear speaker?
Sent from my SGH-I897
laughingT said:
hmmm,
have you got a dirty screen protector or anything else blocking those little windows next to the ear speaker?
Sent from my SGH-I897
Click to expand...
Click to collapse
No, nothing's covering it.
The Rezound App is totally not working. The same issue is happening. I wonder if it could be the Slim Bean rom I'm using? Should I try a different rom?
It seems like your sensor calibration is off and I don't know if a rom change will fix it. Did the problem start after flashing slim bean? Is anyone else with Slim Bean reporting same problem
I'm running straight CM10.0 stable build, November 13 build plus Gapps. Proximity is okay.
Sent from my SGH-I897
laughingT said:
It seems like your sensor calibration is off and I don't know if a rom change will fix it. Did the problem start after flashing slim bean? Is anyone else with Slim Bean reporting same problem
I'm running straight CM10.0 stable build, November 13 build plus Gapps. Proximity is okay.
Sent from my SGH-I897
Click to expand...
Click to collapse
Yes. The problem started when I flashed Slim Bean. I tried a proximity sensor app but it failed me.
Did you try proximity screen off lite?
It looks like in allows you to set threshold levels in the advanced settings.
You could also try reflashing slim bean if other slim bean users are not having the problem
Sent from my SGH-I897
laughingT said:
Did you try proximity screen off lite?
It looks like in allows you to set threshold levels in the advanced settings.
You could also try reflashing slim bean if other slim bean users are not having the problem
Sent from my SGH-I897
Click to expand...
Click to collapse
Yes, I did actually see that app but it scared me away when I read the reviews of all the problems that may accompany it.
I'm gonna try your other idea to flash Slim Bean again. Is there anything I need to do before that like wipe the cache? Perhaps some crap was left behind from all the problems I was having flashing a couple weeks ago?
southernblonde said:
Yes, I did actually see that app but it scared me away when I read the reviews of all the problems that may accompany it.
I'm gonna try your other idea to flash Slim Bean again. Is there anything I need to do before that like wipe the cache? Perhaps some crap was left behind from all the problems I was having flashing a couple weeks ago?
Click to expand...
Click to collapse
Clear cache and dalvik before reflashing. If it still doesn't work, I'd say to try a different ROM.
Related
Does anyone know of a way to remove the proximity sensor drivers or shut it off completely my screen just goes black during a call and i need to use the keypad during calls i have tried all the proximity apps on market and it has no effect, have tried calibration etc odin firmware updates to the point i killed my phone just got it back from repair and was told it needs a new chip to rectify the problem.
I have spent weeks going through forums for a solution and i know on my brothers sgs 2 it has a setting in the menu to turn it off.
This seems to be a common problem with no resolve so im looking for someone to resolve this problem and make alot of people happy.
We all no As these phones age this will be more and more common.
Techies get ur teeth into this or even software writers make An app n earn some cash,
This would b a great ego booster for someone to say i solved that when no one in the world could.
Thanks...........looney
Sent from my GT-I9000 using XDA App
Mh? Why not pressing the home button during call.
Screen is enabled then...
Anyway MIUI got this option to switch it off.
Don't know if this setting is available in Stock ROMs.
screen should go back on when you move your head out of the ~5cm sensor radious. if it is not happening there are two possibilities:
- something wrong with firmware -> reflash phone with pure unrooted samsung firmware and check if problem persist
- someting is wrong with proximity sensor -> use warranty and send it to service center with proper description of the problem
Thanks for the replys the home button won't work as the proxy is up the spout had it checked the chip is blown, when u press the home key won't work as the phone is trying to find the proxy then eventualy it will crash and force close.
No software update will do it as its a hardware fault unless it turns it off so will have a look at the one you suggested.
There is def a stock version but i fear it is only on the s2 to turn blank screen off il check my bro's firmware, till then keep the suggestions coming in thanks....
Sent from my GT-I9000 using XDA App
Here is a possible solution. Check the + 3.7 volts at this point, if there is no tension, then feed it thither with a jumper
SADист said:
Here is a possible solution. Check the + 3.7 volts at this point, if there is no tension, then feed it thither with a jumper
Click to expand...
Click to collapse
Thanks for the tip. Where can i get 3.7 V from? (which part of the MB)? Is there a way of hardware disabling the sensor? the software testers report 0.7 mA leakage on a sensor (which is faulty anyways)
lusjash said:
Thanks for the tip. Where can i get 3.7 V from? (which part of the MB)?
Click to expand...
Click to collapse
You can do this:
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
For the life of me I cannot use my N6 no-handed, even for just a moment. The 5-10 seconds I need to hold my phone up between my shoulder and my face to free both hands.......it never fails that I cause an issue with a live phone call. Obviously the larger screen (larger touch-sensitive area) and the screen being on for some reason during the call.......I always either put the phone call on hold, or even put the current call on hold and manage to dial one of my starred contacts. It is driving me up the damn wall. I am not a huge fan of the L phone interface (the starred favorites especially), I much prefer the KK layout.
Anyone else having as hard of a time as me? I'm wondering if the screen being off during the call would cure this. I guess I could manually cut it off when going to no-hands.......but figured it should do it on its own. Anyone care to either give me some suggestions, or even punch me for my ignorance and tell me what I am doing wrong?
Love everything about the phone, and also loving LiquidSmooth.......just hoping the development gets into high gear soon.
The screen is suppose to be off during calls, that's what the proximity sensor is for. Are you sure you are not hitting the power button while in call, i find it to be sensitive??If its not turning itself off when you put it up to your face, flash back to full stock. Still not working, then its probably a hardware issue???
Sent from my Nexus 6 using XDA Free mobile app
holeindalip said:
The screen is suppose to be off during calls, that's what the proximity sensor is for. Are you sure you are not hitting the power button while in call, i find it to be sensitive??If its not turning itself off when you put it up to your face, flash back to full stock. Still not working, then its probably a hardware issue???
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I forgot to reply I had this issue while stock as well. I wasn't looking to 'fix' this issue with a different ROM either, I just like the capabilities and development done in the ROM's themselves. Can't say I didn't hope something would change though.....
I only experience this with my left hand, LOL. Right handed, no issues with the screen turning off.
wilson289 said:
I only experience this with my left hand, LOL. Right handed, no issues with the screen turning off.
Click to expand...
Click to collapse
Well that is certainly odd lol.....
Anyone else? Surely I'm not the only one....... :silly:
Hello guys ...sorry if a similar question was already asked.
I have a problem with my phone. When i want to make a phone call the screen goes off. At first I thought that the phone switched itself off, but later I noticed that the credit was gone...:/ I happens even after the factory reset. It also happens with another dialer from google play...however, people can still call me and there is no problem...no problems with sms either.
I have 2.3.6 Gingerbread
Please help
I think that's normal. There's a sensor which causes this.
Lars124 said:
I think that's normal. There's a sensor which causes this.
Click to expand...
Click to collapse
so its not software problem? is it worth to replace it? how much may it cost?
i also checked another thing...its not only the screen there's no signal and a phone call is not made...:/
Every phone has this sensor. The intention is that you don't touch any button on your screen during the phone call.
You can try to reflash the stock rom.
Lars124 said:
Every phone has this sensor. The intention is that you don't touch any button on your screen during the phone call.
You can try to reflash the stock rom.
Click to expand...
Click to collapse
I reflashed it...the problam's still there...but my friend call me back i called him but i didn't here any signal and the screen went off...:/
Lars which sensor did You mean? Proximity sensor? Would that cause the phone to go silent (no dial signal)?
zombie1977 said:
Lars which sensor did You mean? Proximity sensor? Would that cause the phone to go silent (no dial signal)?
Click to expand...
Click to collapse
I run the proximity sensor test using *#*#0588#*#* and looks like it's broken...the screen is blue and displays "proximity x 1" covering the sensor has no effect, looks like the sensor is activated all the time...
I noticed some dust, maybe moisture in there so i think it will be a good idea to take the phone apart and clean the sensor...
zombie1977 said:
I run the proximity sensor test using *#*#0588#*#* and looks like it's broken...the screen is blue and displays "proximity x 1" covering the sensor has no effect, looks like the sensor is activated all the time...
I noticed some dust, maybe moisture in there so i think it will be a good idea to take the phone apart and clean the sensor...
Click to expand...
Click to collapse
I feel like a crazy person answering my own posts...
I took it apart, cleaned it, but the problem's still there. I bought a new assembly jack-speaker-proximity sensor on ebay for 7 euro...hope it will work after replacing this part...
The way it's all together explains why there was no dial signal.
When I replace the part i will let You know Thanks for Your help
No problem.
Tell me when you're done.
Lars124 said:
No problem.
Tell me when you're done.
Click to expand...
Click to collapse
Hello Replaced the part, tested, everything working beautifully Sweet I love this phone :cyclops:
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?