Related
Hi all,
So a couple months or so ago, my dad got an S5 and handed down his Droid DNA to me which I promptly rooted and rom'd. Fast forward to last week (didn't take long), and I dropped the DNA and broke the screen. So while I'm waiting on a new screen to arrive for the DNA I activated my trusty Bionic. Only now, again only a short time since last use, the proximity sensor is giving me issues which it hadn't before. Now, as soon as I place a call the screen goes black and won't turn back on until the caller on the other end hangs up, as well as the sensor giving off that faint red light I've read so much about. I had slimkat installed and thought that was the issue, so wiped clean and installed PA. The problem persisted and I just tested a call on stock and now it's happening on stock too! Whereas beforehand it wasn't
I've read that an app can be causing this to happen, but between my stock rom, and PA, there are no common "running" apps so that can't possibly be the problem unless it's one app on stock and a separate app on PA which seems unlikely. I have replaced the screen before, but I used the phone for probably another 8-10 months after that before activating the DNA and putting the Bionic on the shelf, during which time I had never once had this issue.
Does anyone have any experience with this? If so what did you do to fix it? It's a super annoying problem :/
Thanks in advance, hopefully somebody's got the answer I need!
EDIT: Just tried blowing really hard through the speaker port while on stock in case something got lodged in front of the senso, and that appeared to fix it! Made a voicemail call and the screen stayed on while allowing use of the keypad. Switching boot options in safestrap to PA to try there.
...no dice in PA faint red light still, and black screen with no access to keypad. Maybe a rom issue, will investigate further I guess...
I just bought a new m7 yesterday and my experience is horrible. It was all ok but after the lollipop upgrade everything is messed up.
Proximity sensor is totally fine because I have checked it with several apps...
problem one: the screen doesn't turn on after I remove tho phone from my ear while calling, so I can't hang up unless the other person hangs up.
Problem 2: Same thing with Lock Screen. It doesn't turn on..
Problem 3: my phone's touch is not working at a certain horizontal line along the screen, When I touch there, two touches are senses just right and left....
If anyone has encountered these problems, please give me a solution or find me a better solution.
ikyorince said:
I just bought a new m7 yesterday and my experience is horrible. It was all ok but after the lollipop upgrade everything is messed up.
Proximity sensor is totally fine because I have checked it with several apps...
problem one: the screen doesn't turn on after I remove tho phone from my ear while calling, so I can't hang up unless the other person hangs up.
Problem 2: Same thing with Lock Screen. It doesn't turn on..
Problem 3: my phone's touch is not working at a certain horizontal line along the screen, When I touch there, two touches are senses just right and left....
If anyone has encountered these problems, please give me a solution or find me a better solution.
Click to expand...
Click to collapse
looks like you are having hardware problem with the digitizer and the proximity sensor, you might want to send back this phone a get another one.
same issue 100% positive its a lollipop bug after a reset it gets fixed but if i update my apps through playstore it comes back
likhon02 said:
same issue 100% positive its a lollipop bug after a reset it gets fixed but if i update my apps through playstore it comes back
Click to expand...
Click to collapse
If the problem returns after updating your apps through the playstore then it's related to one of your app, not lollipop itself. One of your apps must be interfering with the screen or the proximity sensor.
Sent from my HTC One using XDA Labs
alray said:
If the problem returns after updating your apps through the playstore then it's related to one of your app, not lollipop itself. One of your apps must be interfering with the screen or the proximity sensor.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
anyways found the solution
http://forum.xda-developers.com/htc-one/help/lockscreen-issue-wake-lag-unlock-black-t3450726
This is a pretty big issue that blue up on the OnePlus forum and Reddit. People are experiencing ghost touches in apps. It's very easy to also experience this by opening cpu-z and letting it sit there for a minute or two not doing anything. It seems not everyone is experiencing this though. I have tested and do experience it. Do you?
Yup. Mine does with cpu-z open. what do we do?
BossJ said:
Yup. Mine does with cpu-z open. what do we do?
Click to expand...
Click to collapse
Depends if it's a hardware or software issue. Personally I already submitted a return request with OnePlus.
I just cancelled my order.. hopefully there is a software fix for you guys
This only happens to me on cpu-z and not in any other app. So I guess a future software update is gonna fix it.
Left it for a minute and didn't notice anything. On 9.5.3, bootloader unlocked and patched boot image with root.
I haven't experienced in a few days, it was happening a lot until I disabled pretty much all gestures.
I installed CPU-Z just to check on my International 8GB/256 model and I've got no issue with ghost touches. Not sure what is causing this for you all, but I do hope it is sorted out for you all.
When I turned off NFC the issue went away for me glad I don't use it whatsoever haha
Purest said:
I haven't experienced in a few days, it was happening a lot until I disabled pretty much all gestures.
Click to expand...
Click to collapse
Well that's not a solution disabling a useful feature to not have ghost touch issue.
On screen/off screen gesture are one of my favorite using it, so not a solution to me.
Simple will return the device.
I haven't order yet but i will next couple of days.
There's many reports across oneplus forum.
https://www.androidpolice.com/2019/...ros-are-suffering-phantom-touch-input-issues/
I left CPU-Z running for at least 10 mins.
And all is OK. Maybe it's a rouge program or something to do with the unlock\twrp?
The only way to be sure is to reset to stock and only install CPU-Z
Seems OnePlus using Novatek panels https://github.com/OnePlusOSS/andro...input/touchscreen/oneplus_touchscreen/Novatek
Poco F1 had same problems with Novatec and only way fix it was replacing whole panels, they tried to fix over updates but witout luck
romanB_SK said:
Seems OnePlus using Novatek panels https://github.com/OnePlusOSS/andro...input/touchscreen/oneplus_touchscreen/Novatek
Poco F1 had same problems with Novatec and only way fix it was replacing whole panels, they tried to fix over updates but witout luck
Click to expand...
Click to collapse
Wow that's seems real bummer.
Why would OP use Novatek display controller since had bad reputation and bad track record.
So the question is how do we know if all that units effected having all of the them Novatek display controller?
Or if there's another supplier for those units that don't have that issue.
Man things are getting much worse if it's hardware related and not software that I thought.
Sent from my V1821A using Tapatalk
It's extremely annoying it has happened to me a few times even when I was boasting about the new device to some colleagues at work. I thought it was me at first until then I read IRS an actual thing. I won't return it yet but I might if it's not sorted soon. It's extremely irritating.
Sent from my [device_name] using XDA-Developers Legacy app
Looks like ghost touches are related to NFC. Try with NFC turned off.
C3C076 said:
Looks like ghost touches are related to NFC. Try with NFC turned off.
Click to expand...
Click to collapse
Can confirm. My Ghost touches seize when NFC is disabled.
Sent from my GM1913 using Tapatalk
I've started yesterday experiencing that ghost touchs and also screen not responsive to touch in some panel sections (mostly the upper right zone). The phone didn't gave me that problem since I bought. I noticed when this happening, pulling the notification bar down to the tile settings makes that zone work again. Same thing happened when that random ghost touchs happens.
Didn't had any problems, don't use NFC, tried turning it on, ghost touches started appearing on cpuz, but not on other apps. As i don't use NFC i probably won't return the phone.
I just tried with CPU-Z and a few seconds after starting the app, the screen turns crazy tapping here and there. Can confirm also disabling NFC solves it.
Turning off nfc or not using gestures or not using cpuz app is just temporary solution.
And there's multiple reports that ghost issues happening other app too.
And we never know if thing get worse over time.
I'm afraid it's a more common issue than we thought but many users simple didn't notice it until now.
Oneplus should clearly take attention on that issue seriously and fix it ASAP.
Shouldn't be happening at all with any kind app or scenario of usage.
Sent from my V1821A using Tapatalk
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
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?