Database Develop

[Q] Moto X Interfering with Radar/Laser Detector?

Had a really weird thing happen on my way to the airport the other morning, twice. I was traveling on the highway with my wife early in the morning (predawn) when my phone rang. I went to pick it up to see who it was and hand it to my wife when my Escort 9500ix radar/laser detector started going off saying that there was a "LASER" alert. With this model of radar detector false alarms are almost non-existent, so I slammed on my brakes and slow down...but never saw a cop. About 20 minutes later the phone rang again, wife picked it up and the "laser" alert went off again...and again no cop.
The only thing that I can think of is that the motion sensors are interfering with the laser section of the detector and giving me a false reading. I am unsure if this happens all the time or just with incoming calls (will have to look into it). Anyone else had anything like this happen?

My Passport Max did the same thing this morning. The IR sensor has to be directly in front or directly behind the radar detector but it does set mine off.

2k7gt said:
My Passport Max did the same thing this morning. The IR sensor has to be directly in front or directly behind the radar detector but it does set mine off.
Click to expand...
Click to collapse
Glad to know that it is not just my phone or 9500ix. Thanks for the reply.

I've had the Max 360 for a month now, but my son came home for christmas with his Motorola X Pure Edition and it caused all manner of falsing on the laser spectrum, but only when he was in the car, and even with the phone on the console, out of line of sight. Does not happen with my GS6 Edge or my wife's S5 (which have IR blasters), or her work iPhone (know nothing about that one). Called Escort, and they said this is a known issue with no cure. To be sensitive to highway laser, the detector has to reat to this frequency. If a device inside the car also emits, then there is a conflict.

Very unreliable "Trusted" devices/places unlock

I have Moto360 and it's supposed to keep the phone unlocked. Well, once in a while (at least once per day) it doesn't work so I decided to add a Trusted Location (my house). This made it worse because there seems to be some sort of "race condition" and I get a lot more issues at work now. Basically it seems like it's seeing that I'm not home and skips the check of Moto360 presence all-together. I also added an NFC tag (for my car in case I forget Moto360 at home). So having these 3 settings enabled at once makes this a worse experience than just with Moto360 (which isn't reliable to begin with)
Anyway, this unlocking mechanism is one big mess and hasn't been reliable for me. I understand that it's better to be safe than sorry but these are clear bugs.
Anyone else experiencing this?

T-R said:
I have Moto360 and it's supposed to keep the phone unlocked. Well, once in a while (at least once per day) it doesn't work so I decided to add a Trusted Location (my house). This made it worse because there seems to be some sort of "race condition" and I get a lot more issues at work now. Basically it seems like it's seeing that I'm not home and skips the check of Moto360 presence all-together. I also added an NFC tag (for my car in case I forget Moto360 at home). So having these 3 settings enabled at once makes this a worse experience than just with Moto360 (which isn't reliable to begin with)
Anyway, this unlocking mechanism is one big mess and hasn't been reliable for me. I understand that it's better to be safe than sorry but these are clear bugs.
Anyone else experiencing this?
Click to expand...
Click to collapse
That's strange. I have the same setup except my car's BT is a trusted pair also.
No issues here.

Dusty Rhodes said:
That's strange. I have the same setup except my car's BT is a trusted pair also.
No issues here.
Click to expand...
Click to collapse
Is the BT in ur car capable to read your text msg? My note 4 use do it perfect but nexus is not option is grayed out on my car screen.

My home and work are "trusted places" and it works about 50% of the time. At work it barely works...My Nexus 5 was the same way. It is probably a thing on Google's end that they need to update.

T-R said:
I have Moto360 and it's supposed to keep the phone unlocked. Well, once in a while (at least once per day) it doesn't work so I decided to add a Trusted Location (my house). This made it worse because there seems to be some sort of "race condition" and I get a lot more issues at work now. Basically it seems like it's seeing that I'm not home and skips the check of Moto360 presence all-together. I also added an NFC tag (for my car in case I forget Moto360 at home). So having these 3 settings enabled at once makes this a worse experience than just with Moto360 (which isn't reliable to begin with)
Anyway, this unlocking mechanism is one big mess and hasn't been reliable for me. I understand that it's better to be safe than sorry but these are clear bugs.
Anyone else experiencing this?
Click to expand...
Click to collapse
i'm not experiencing this at all. i've had it working with my N5 flawlessly (before i got my N6) as well. if your phone isn't showing that you're at home, your location services might be turned off though.
worst case is that you back up your settings and try a clean wipe/reflash and see if it's working as expected.
*EDIT* are you sure that you're not accidentally hitting the little lock/unlock icon at the bottom of the screen? that will lock it regardless of the trusted devices/location settings.

NICEGYPT said:
Is the BT in ur car capable to read your text msg? My note 4 use do it perfect but nexus is not option is grayed out on my car screen.
Click to expand...
Click to collapse
Mine could work but I use hangouts as my messaging app and THAT doesn't work.
So that you know what I'm working with, I have a 2012 Mustang GT with MyFordTouch.

Dusty Rhodes said:
Mine could work but I use hangouts as my messaging app and THAT doesn't work.
So that you know what I'm working with, I have a 2012 Mustang GT with MyFordTouch.
Click to expand...
Click to collapse
I have a 2014 Charger with Uconnect

Lucke said:
*EDIT* are you sure that you're not accidentally hitting the little lock/unlock icon at the bottom of the screen? that will lock it regardless of the trusted devices/location settings.
Click to expand...
Click to collapse
Wow, that could be it! I didn't even realize this icon is there and I often unlock from the very bottom (old habits). I will pay attention from now on and hopefully this is exactly what it was.
Thank you!

T-R said:
Wow, that could be it! I didn't even realize this icon is there and I often unlock from the very bottom (old habits). I will pay attention from now on and hopefully this is exactly what it was.
Thank you!
Click to expand...
Click to collapse
Haha I had the same problem til I realized this

Ok Google not working while screen off and charging

Like the title says. When the phone is screen off but plugged in, OK Google isn't recognized. Works fine if screen is on. In my Google / Voice settings I have turned on Say Ok Google Anytime and Trusted Voice to unlock.
It worked fine on my LG G3 previously before I came to the 3T.
Any ideas?
Sent from my ONEPLUS A3000 using Tapatalk

For me also not works

This is proving to be very annoying.
I tried the Now Launcher to see if it would fix this problem (I was going to use it anyway since autorotate seems broken with stock Launcher).
Now launcher doesn't change the situation. Does anybody have a work-around? This is the first phone/os that I have had this problem with.
Help!
Sent from my ONEPLUS A3000 using Tapatalk

When i tried, it says there is locked screen (i have fingerprinted lock screen), but when i recognized and accepted, it had no reaction. Do you tried only swiped lock screen?

Tried a bunch of things. When screen is off (but charging)I haven't found any combination of settings that work. I use a fingerprint but noticed problem before setting up the fingerprint. Also have set that my voice can be trusted to unlock; also in my car the phone is unlocked as a trusted Bluetooth device.
Sent from my ONEPLUS A3000 using Tapatalk

For me sometimes it has vibration, sometimes it says that phone are locked. But still not works "ok google" on black screen

I guess what does it means. When you press unlcok button, if there is swipe or something, it unlocks device when you say "ok google"

I have the same problem..ok Google does not work when the screen is off..bt works fine when the screen is on

I've asked this question over in the OnePlus community forum on OnePlus.net. I don't think the readership there is as savvy as here though. I've already gotten some patently wrong answers. I'm still hoping someone can suggest a fix or at least work-around.
Sent from my ONEPLUS A3000 using Tapatalk

gioyocho said:
I guess what does it means. When you press unlcok button, if there is swipe or something, it unlocks device when you say "ok google"
Click to expand...
Click to collapse
I have that option checked and it still stops working for me if I haven't used my device for more than 5 minutes.
Sent from my ONEPLUS A3000 using Tapatalk

I also would like to use OK Google with the screen off.

This has been driving me a bit crazy. I can't imagine what is blocking it from working. Glad to hear it isn't just me experiencing it... At least I am not alone.
I can't imagine it is a technology gap on the phone... That would only apply to screen off / not charging cases. Microphone certainly can work with screen off... For example talking on phone the screen shuts off in proximity to the head. And it's not a power issue, since this use case includes charging.
Somewhere there must be a hidden toggle for some feature set the wrong way.
Anybody have skills to investigate?
Sent from my ONEPLUS A3000 using Tapatalk

you can't.
always listening isn't enabled on our phone (something about licensing with qualcomm).

I don't need always listening... I need listening while charging. Even phones from 5 years ago do this...
Sent from my ONEPLUS A3000 using Tapatalk

again, you can't. IT IS NOT ENABLED ON OUR PHONE.
Yes, my nexus from years ago can do it.
but no, our 3T will NOT do it.

exb0 said:
again, you can't. IT IS NOT ENABLED ON OUR PHONE.
Yes, my nexus from years ago can do it.
but no, our 3T will NOT do it.
Click to expand...
Click to collapse
This kind of makes hands-free driving and home voice actions pointless.

exb0 said:
again, you can't. IT IS NOT ENABLED ON OUR PHONE.
Yes, my nexus from years ago can do it.
but no, our 3T will NOT do it.
Click to expand...
Click to collapse
Thanks for the reply. What exactly isn't enabled... or better asked, at what level is it not enabled? The SnapDragon 821 has support for it. So, perhaps this will come in an update or a custom ROM. Or is there some other layer which needs to be developed that OP currently hasn't?
It's beyond shocking that a major feature ... voice response while driving ... would be crippled in a recent model phone. And, I am ignorant of what exactly needs to work. The microphone works fine when the screen is off, and I have no concerns about battery performance when plugged in and charging, so an app should be able to be told to listen to the microphone under these circumstances.
Any further info about what's missing would be greatly appreciated!

It worked for a short time for me. I could say, "ok google" with the screen off, but I'm guessing the app updated or a rom changed one little thing and now it's a pain in the ass.
Sent from my ONEPLUS 3T using Tapatalk

cbwhat said:
This kind of makes hands-free driving and home voice actions pointless.
Click to expand...
Click to collapse
Uhh, yeah. That's why you keep the screen on.
Frankenscript said:
Thanks for the reply. What exactly isn't enabled... or better asked, at what level is it not enabled? The SnapDragon 821 has support for it. So, perhaps this will come in an update or a custom ROM. Or is there some other layer which needs to be developed that OP currently hasn't?
It's beyond shocking that a major feature ... voice response while driving ... would be crippled in a recent model phone. And, I am ignorant of what exactly needs to work. The microphone works fine when the screen is off, and I have no concerns about battery performance when plugged in and charging, so an app should be able to be told to listen to the microphone under these circumstances.
Any further info about what's missing would be greatly appreciated!
Click to expand...
Click to collapse
Yes, the 821 has support for always listening. However, the phone company (OnePlus) has to pay the SOC company (qualcomm) in order to use always listening (more on always listening later). Is it possible for a developer to somehow enable it? Yes. As seen with the Ok Snapdragon concept with the nexus 4, we can indeed enable it. However due to legal issues, that mod was never released.
Another reason is marketing. Motorola was able to promote their Moto X Pure so much because it had their custom "Ok Google" thingiemajig. If every phone had always listening, why buy a nexus / pixel / moto?
If you want the phone to listen and respond to your voice actions while the screen is off, regardless of whether or not it's plugged in, you need always listening. Unless you're in a call, of course.
I've heard that PA and/or CM managed to make a hackaround this for other OP phones, but I cannot confirm that it actually exists as I have never looked into it.

Great explanation. Thank you
Sent from my ONEPLUS A3000 using Tapatalk

Flickering dot under display in notification area

Hi all,
Been quite a few years since I posted anything here!
I have just received my pixel 5 and have noticed that dead center of the notification tray when in portrait, there is a flickering dot, especially in low light it flickers white or if not flickering leaves a faint grey dot over whatever is on the screen (stays in the same place even if I rotate the phone or watch a video)
If I reboot I can't see it for a minute or so until it then appears.
Factory reset doesn't solve it.
Has anyone else noticed this? I'm thinking it might be the ambient light sensor under the display but it is really irritating, possibly mine is faulty?
Cheers!

It's the underscreen proximity sensor.

I get that it is the proximity sensor but, It is flashing constantly - I spoke to google and they said that it should only show when in a call - it is flashing even while watching YouTube - does anyone else get this same behaviour?

Not showing on mine

I have it constantly when KinScreen is running, I saw someone having it with cpuz

I hadn't noticed until I saw this thread. I did wonder where the proximity sensor was. It's only visible when on a phone call for me.
Is the light sensor under the screen also? You can usually see that on a lot of devices when you tilt the screen slightly.

Joshhudsy said:
I get that it is the proximity sensor but, It is flashing constantly - I spoke to google and they said that it should only show when in a call - it is flashing even while watching YouTube - does anyone else get this same behaviour?
Click to expand...
Click to collapse
Mine only shows when on a call

You probably have some apps using it. Possibly something like Tasker that happened to have proximity sensor based profiles configured, etc.

Mine went mental during Google Play downloading all my apps on initial phone setup. Then it went out and I've not seen it since.

Joshhudsy said:
I get that it is the proximity sensor but, It is flashing constantly - I spoke to google and they said that it should only show when in a call - it is flashing even while watching YouTube - does anyone else get this same behaviour?
Click to expand...
Click to collapse
It's a software bug. I read about it on reddit and twitter yesterday. Did you move your data from your old phone using the cable?
To fix it you should factory reset, then migrate your old data using WiFi, not cable, don't restore or restore your apps manually (at least until you make sure it's fixed).
If that still doesn't work, check if you have an app called HomeAssistant (HASSIO) installed. There's one report of that causing it. To fix that you need to disable the proximity sensor on the assistant app itself.
Sources: here, here, and here.

I got the same Problem after installing notifybuddy. There must be some Bug where the sensor gets started the moment an overlay is shown. I can reproduce the Bug over and over again. Install notifybuddy and Start the App give all permissions and than Pull down notificationscenter (its an overlay). To solve the Problem, uninstall notification Apps That are using overlays.

Mine is working fine. Only during a call or listening to voice messages.

akpe said:
It's a software bug. I read about it on reddit and twitter yesterday. Did you move your data from your old phone using the cable?
To fix it you should factory reset, then migrate your old data using WiFi, not cable, don't restore or restore your apps manually (at least until you make sure it's fixed).
If that still doesn't work, check if you have an app called HomeAssistant (HASSIO) installed. There's one report of that causing it. To fix that you need to disable the proximity sensor on the assistant app itself.
Sources: here, here, and here.
Click to expand...
Click to collapse
Hit the nail on the head there!
It was the Home assistant app causing it (even though it had installed after restoring from my backup, I had never opened it yet since having this phone). Uninstalled home assistant and it has stopped flashing!
Thanks so much for the replies all!

Have this issue on my one too...which is the home assistant app? Deleted the "Home" but that doesn't seem to have solved the problem.

Anwar902 said:
Have this issue on my one too...which is the home assistant app? Deleted the "Home" but that doesn't seem to have solved the problem.
Click to expand...
Click to collapse
Go to the gestures options (don't know exactly where the specific one is located, it could also be at the Digital Wellbeing settings) and disable the Flip to Shh one. See if that helps.
Στάλθηκε από το Mi A2 μου χρησιμοποιώντας Tapatalk

Anwar902 said:
Have this issue on my one too...which is the home assistant app? Deleted the "Home" but that doesn't seem to have solved the problem.
Click to expand...
Click to collapse
The Home assistant is a 3rd party home automation app that I had previously installed - if you don't use it, I'd check for any other apps you have installed for something that might be using the proximity sensor.

Couldn't find that was causing the issue. After a restart it would be fine but once unlocked and apps started loading it would go crazy. Went through all my apps but couldn't find the cause so just reset my phone. Hopefully it doesn't show up again.
Seems to.be software issue so hopefully google will do something about it

Joshhudsy said:
The Home assistant is a 3rd party home automation app that I had previously installed - if you don't use it, I'd check for any other apps you have installed for something that might be using the proximity sensor.
Click to expand...
Click to collapse
It really shouldn't matter if something is using the proximity sensor. It shouldn't ever be visible.

jimv1983 said:
It really shouldn't matter if something is using the proximity sensor. It shouldn't ever be visible.
Click to expand...
Click to collapse
That's incorrect. A quick Google search for "S20 proximity sensor blinking" will yield results that show otherwise. Maybe go to YouTube instead as there's quite a few videos there on it. The Samsung subreddit has an influx of posts, it seems, for almost every device they've released over the past couple of years because folks aren't used to seeing it. It's visible under the display on my S20 Ultra and I had it on my S10 plus also.
Now of course there's bugs where it's blinking on the Pixel 5 when it shouldn't, but is it supposed to be visible when an app is using it legitimately? Yes.
Edit: It just dawned on me that YouTube vids wouldn't be the best example of this because they use cameras to video the proximity detector. Everything else stands though. Google searches and Samsung subreddits are ripe with examples though.

MasterBelch said:
That's incorrect. A quick Google search for "S20 proximity sensor blinking" will yield results that show otherwise. Maybe go to YouTube instead as there's quite a few videos there on it. The Samsung subreddit has an influx of posts, it seems, for almost every device they've released over the past couple of years because folks aren't used to seeing it. It's visible under the display on my S20 Ultra and I had it on my S10 plus also.
Now of course there's bugs where it's blinking on the Pixel 5 when it shouldn't, but is it supposed to be visible when an app is using it legitimately? Yes.
Edit: It just dawned on me that YouTube vids wouldn't be the best example of this because they use cameras to video the proximity detector. Everything else stands though. Google searches and Samsung subreddits are ripe with examples though.
Click to expand...
Click to collapse
If what you are saying is true then why can't you see the sensor flashing on any phone when in a phone call or when the "Flip To Shhh" feature is enabled with just your eyes?
And if that is true about the Pixel 5 then there will be no way to use the "Flip To Shhh" feature without always seeing the sensor flashing which I can do with my Pixel 2 XL.
Here is a video of my Pixel 2 XL taken with the camera on my tablet. You can see that the tablet picks up the flickering sensor when "Flip To Shhh" but the sensor goes off when I turn the feature off. That's because the feature uses the proximity sensor to work. However, the flickering is ONLY picked up by the camera on my other device. I can't see it with just my eyes looking at the phone even though the sensor is active.
https://streamable.com/z30mgx

Always on Display Issue

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?