Database Develop

[Q] Screen inaccuracy issues

I know that this has been a fairly common complaint about the Nexus One but i'm wondering, roughly what percentage of people actually have this issue? To clarify, i mean the problem whereby touching the screen in one place is actually registering elsewhere on the screen.
I've had this problem since buying my n1 and having to constantly turn the screen off and back on again was driving me nuts. Finally i sent the unit back to Vodafone for repair and they in turn sent it to HTC to be fixed. So yesterday i got it back with an enclosed statement along the lines of "we have fixed your fault etc..".
Three minutes into using the damn thing and the fault crops up again. So much for that! To be fair to Vodafone they are sending out a replacement unit now but of course i'm concerned that even that will have the same issue.
What are the odds?

Here is the same.
To developers: the fact that resetting the screen fix the problem makes me to ask if there isn't a way to make the screen re-calibrate itself every X seconds/minutes, without shut off and on the screen every time. Seems to be until now the only solution to this extremely annoying issue.

It really is a bizarre one. I've seen people discussing whether it's a hardware or software issue but nobody seems to have a definitive answer. If it were a hardware problem, surely it would be constant/permanent? If it's a software issue i would have thought that somebody would have bug-fixed it by now? Especially as it seems so prevailant.
I'm stumped!
Other than this one problem though i am completely in love with this phone. The device itself feels solid, durable and pleasant to use. Android is improving all the time and it always impresses when you demonstrate to the un-initiated what the device is capable of. So close to perfect...but not quite!
EDIT... This from the wiki.. "- Q5: Sometimes my screen registers touches in incorrect places, and I need to turn the phone off and on to make it work correctly again
A: This is a hardware problem, nothing can be done about it. Nexus One's digitizer sucks.
Ho-Hum.

I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App

msavic6 said:
I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
That suggests a software problem although i have had it on 2.1, 2.2 and now 2.2.1. I would say that it has happened to me within three minutes of using the phone, 50% of the time within that three minute window. In other words it's cropped up in half the texts/emails i have sent where i have had to do the screen off/on thing to complete the message.
Very annoying.

It has to do mostly with the way people hold their phones, the possibility of registering false touches - including, for example, touching the screen with fingers that aren't completely dry. Some have the issue more than others.
HW issues still can have SW workarounds sometimes. I'm not sure if it's the case. HW and SW need to be analyzed to find one, if exists.
There is no "calibrating" capacitive touchscreen. Resetting its controller might have effects like missing touches and other random screen misbehavior (for example - if the controller is tracking fingers, resetting it would cause it to lose the tracking).

Since getting my phone back from 'repair' the issue is less frequent, suggesting that it's not a usage problem as i'm obviously still using the phone in the same manner as before. Instead it seems that various devices suffer from the problem in varying degrees.
I suppose if i knew what they had actually done to the phone while it was being tended to it might help us discover why the frequency of the problem has been reduced. I know that the digitizer wasn't replaced as the phone came back with the same screen protector on it as it had when i sent it off. That being said, they obviously did something. I just don't know what!

Most probably replaced the phone's MB.

Try upgrading to the latest radio - the issue will probably not be 100% solved, but now I only get it maybe once a month or so...

I may tell them not to bother sending out a replacement. It's happening far less often since it was returned and (going by the poll results), there's a good chance that the replacement could actually be worse than this one is now.
Perhaps the 2.3 update will jar something loose.

ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App

pyngwie said:
ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?

xyellx said:
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?
Click to expand...
Click to collapse
I have already restored cyano 6.1.1.
However, about "multitouch issues" I mean inaccuracy, the fact that the touch is recognised in another point of the screen (particularly when you press the bottom part of the panel). I didn't verified the axes-inversion issue, but I'm almost sure that it persists.

The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.

Jack_R1 said:
The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.
Click to expand...
Click to collapse
I don't think so....I pay attentions when the screen goes crazy. I'm absolutely sure that (in charge for example) my touch is ONE.

The only times I was able to trigger the "screen nuts" effect, were when I was typing 2-fingered, and fast - making it register dual touches. Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.

Jack_R1 said:
Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.
Click to expand...
Click to collapse
I mean this....since I moved to MIUI this is not happened anymore.

Since I uninstalled Htcime the inaccuracy issues seem less so far! Almost only with the phone under charge ...much much better than before! Dunno why....
Sent from my Nexus One using XDA App

Problem with the Front Facing camera.

I was wondering if anyone else had this issue with the front facing camera. There's a couple people that had this issue as well, check the
mentions for SamsungSupport on Twitter a couple days back(at the time of this post)
There's even a video of it in action: https://twitter.com/Hired_Assassin5/status/918633351510200320
As you can see at the top, there's some major discoloration going on. It's almost like a negative image.
https://i.imgur.com/2ipVzgS.jpg
I got the phone on Sep 15th, release day. The camera was working fine up until around Oct 5th that I know of. Taking selfies with the dog, etc.
Well, I opened it up on the 12th, haven't used it for a while, and I noticed that issue you see in the first image. I contacted Samsung and they had me
go through the whole troubleshooting process, all the way to me factory resetting my device. Factory Reset, then skipped all the setup wizards
and went straight to testing the camera. Issue is still present!
So the next day, I went to my carrier store, they said they never seen that before. So they're ordering me a shipment to replace it, possible defect.
Well, that night, I decided to try and look deeper into the issue. Flashlight on camera lenses, didn't see anything. Then I remembered from previous
android phones, there's hardware codes you can enter into the Dialer, so I input *#0*#, which is the hardware testing screen.
It looks like this:
https://i.imgur.com/RhJD4WJ.jpg
So obviously, one of the options is "FRONT CAM". I thought I would "test" it. I clicked on it, and it was working fine! I said oh sh!t, WTH.
This is the screenshot of it:
https://i.imgur.com/2BiaA7U.jpg
Then I took the picture as well, and it turned out just fine, like a normal camera. Well when you tap the screen again, it backs out, and switches
into a different mode, or something. And well sure enough, that issue I was having in my main camera app showed up!
This is a screenshot of it:
https://i.imgur.com/kGgJDD1.jpg
Now this is where I'm wondering if the Geniuses and good people here at XDA can figure out.
If you notice in the first screenshot of the "test" https://i.imgur.com/2BiaA7U.jpg
It says SUB AP at the top left....
Then in the next one, the defective one or whatever https://i.imgur.com/kGgJDD1.jpg
It says SUB CC.
Does anyone know what those are, or what they stand for? And if possible, how can I get my camera app to go back to using the correct mode or whatever that is.
This issue happens in all camera apps, the Samsung default camera app, play store camera apps, etc.
Thanks.

FunYunZ said:
I was wondering if anyone else had this issue with the front facing camera. There's a couple people that had this issue as well, check the
mentions for SamsungSupport on Twitter a couple days back(at the time of this post)
There's even a video of it in action: https://twitter.com/Hired_Assassin5/status/918633351510200320
As you can see at the top, there's some major discoloration going on. It's almost like a negative image.
https://i.imgur.com/2ipVzgS.jpg
I got the phone on Sep 15th, release day. The camera was working fine up until around Oct 5th that I know of. Taking selfies with the dog, etc.
Well, I opened it up on the 12th, haven't used it for a while, and I noticed that issue you see in the first image. I contacted Samsung and they had me
go through the whole troubleshooting process, all the way to me factory resetting my device. Factory Reset, then skipped all the setup wizards
and went straight to testing the camera. Issue is still present!
So the next day, I went to my carrier store, they said they never seen that before. So they're ordering me a shipment to replace it, possible defect.
Well, that night, I decided to try and look deeper into the issue. Flashlight on camera lenses, didn't see anything. Then I remembered from previous
android phones, there's hardware codes you can enter into the Dialer, so I input *#0*#, which is the hardware testing screen.
It looks like this:
https://i.imgur.com/RhJD4WJ.jpg
So obviously, one of the options is "FRONT CAM". I thought I would "test" it. I clicked on it, and it was working fine! I said oh sh!t, WTH.
This is the screenshot of it:
https://i.imgur.com/2BiaA7U.jpg
Then I took the picture as well, and it turned out just fine, like a normal camera. Well when you tap the screen again, it backs out, and switches
into a different mode, or something. And well sure enough, that issue I was having in my main camera app showed up!
This is a screenshot of it:
https://i.imgur.com/kGgJDD1.jpg
Now this is where I'm wondering if the Geniuses and good people here at XDA can figure out.
If you notice in the first screenshot of the "test" https://i.imgur.com/2BiaA7U.jpg
It says SUB AP at the top left....
Then in the next one, the defective one or whatever https://i.imgur.com/kGgJDD1.jpg
It says SUB CC.
Does anyone know what those are, or what they stand for? And if possible, how can I get my camera app to go back to using the correct mode or whatever that is.
This issue happens in all camera apps, the Samsung default camera app, play store camera apps, etc.
Thanks.
Click to expand...
Click to collapse
I'm not having that issue *knocks on wood*
But it doesn't sound like a hardware issue though.
Sub AP, Sub CC are probably different Samsung settings not available to end users. Any advice I'd give is to back up, hard reset, test if problem still present, if problem fixed restore data.
When does the problem usually happen, in bright or low light?
What if you use the front camera "flash" does it still happen?

lennie said:
I'm not having that issue *knocks on wood*
But it doesn't sound like a hardware issue though.
Sub AP, Sub CC are probably different Samsung settings not available to end users. Any advice I'd give is to back up, hard reset, test if problem still present, if problem fixed restore data.
When does the problem usually happen, in bright or low light?
What if you use the front camera "flash" does it still happen?
Click to expand...
Click to collapse
I originally thought it was a hardware issue, but seeing it function normally when I did the diagnostic testing, I knew it had to be
something that triggered the software to not work correctly.
the issue is still present no matter what settings I change. Changing resolution, flash on/off, picture size, HDR on/off/auto, all the settings
I can find, the issue is still exists.
EDIT: Is a hard rest the same as a Factory Reset?

FunYunZ said:
I originally thought it was a hardware issue, but seeing it function normally when I did the diagnostic testing, I knew it had to be
something that triggered the software to not work correctly.
the issue is still present no matter what settings I change. Changing resolution, flash on/off, picture size, HDR on/off/auto, all the settings
I can find, the issue is still exists.
EDIT: Is a hard rest the same as a Factory Reset?
Click to expand...
Click to collapse
hard reset = factory reset

have you tried using Odin and doing a fresh FW install?

htc-8925 said:
have you tried using Odin and doing a fresh FW install?
Click to expand...
Click to collapse
I have not. I did a factory reset.

My friend had the same issue.

whiteangelcl said:
My friend had the same issue.
Click to expand...
Click to collapse
Dam, that's unfortunate. That's 4 people now that have had this issue. I wonder how much worse it will get. Hopefully the new replacement doesn't have this issue.
It's weird because it was working fine for a few weeks, and then something happened. Not sure if it auto updated without me knowing and caused this issue.

FunYunZ said:
Dam, that's unfortunate. That's 4 people now that have had this issue. I wonder how much worse it will get. Hopefully the new replacement doesn't have this issue.
It's weird because it was working fine for a few weeks, and then something happened. Not sure if it auto updated without me knowing and caused this issue.
Click to expand...
Click to collapse
sounds like they're sending you a replacement. make sure you are satisfied with the replacement because they might send you a refurb.

i have the same issue as well ... so what happened at the end ? did they end up finding the issue ? how they fixed it ?

emazens said:
i have the same issue as well ... so what happened at the end ? did they end up finding the issue ? how they fixed it ?
Click to expand...
Click to collapse
Nope, Samsung never got back to me. I just went to the Tmobile store and they were like, yep, never seen that before. So they overnight me a new one.

I just begun to have the same issue on my phone and I'm not happy after spending 1k on it. I'm going to my career tomorrow but unfortunately don't know I this will be resolved. Please Let me know what Samsung did for you.

Same problem on my Note8. Following for solution.

solution anyone?
did anyone of u find a solution?
---------- Post added at 12:41 PM ---------- Previous post was at 12:38 PM ----------
i'm suffering with this problem presently and is trying to find a solve.
totaldepth said:
Same problem on my Note8. Following for solution.
Click to expand...
Click to collapse

i am seeing when i open camera ,camera failed
can anyone advise on how to fix?

If you did not mistreat the device, dropped it or fiddle with system settings or something of the sort, warranty is the all time solution for these problems

Hey my note 8 front camera just experienced the same issue. I've talked to Samsung support, and frankly it seems like it is a hardware issue. It is recommended that you use Samsung Support to make a service request. Free shipping both ways, so if you can live without your phone for a week or two (or have a backup phone to use), that's the route I recommend people going.
Original Problem:
MENU / COMMON APPLICATION ( NATIVE) - CAMERA / VIDEO - CAMERA EFFECTS NOT WORKING
Problem found:
FRONT CAMERA FAIL
Solution:
REPLACED COMPONENT
Click to expand...
Click to collapse

Did you manage to find the cause of the problem?
My front selfie camera has the same problem!

sorry to raise up this issue again.. my s8+ is from Indonesia region, and facing the same issue when try to use front camera is failed with notification Warning Unknown Error Occured.
already try Wipe cache partition and hard reset but still facing the same issue..
but if i use front camera for video call thru whatsapp it's working fine, but yet again if check thru *#0*# for Front Camera it's Camera Failed..
is it hardware issue or FW issue ?

Front Facing camera has double image
Has anyone found a fix for this issue yet? Mine started this issue last year and I haven't found a remedy for it yet. Ugh.

Samsung Note 9 - Display Discoloration & Overheating

Who else are facing the same problem ?
1)Initially, when I unlock phone by pressing power button the display was changed to dim colour(mostly yellowish) and with horizontal lines displayed when the brightness is below 50%. After tried with multiple times pressing on power button the display came back to normal.
2) Next stage, it's not solved with power button. I have to keep my phone aside for some time to get back to normal display. It's been 15 to 20 min then.
3) Now, I would get normal display only in morning. Else, I need to keep my phone idle without touching for at least 4 to 5 hours. I've also changed screen power off time from 30 Sec to 10 Minutes. So that my screen wont turn off and I can keep the normal display. If I forgot to use or kept aside more than 10 min then my screen would go off and display would gone again and irritation starts with that discoloration problem..
4) If display changes to yellowish to reduce the horizontal lines problem I need to increase the brightness to 80 or 85% but this causing my phone with another problem "heating issue"
Samsung haven't responded on this issue yet, how could we bring up the issue and get the proper resolution from Samsung.

This happened after last March update installation?
What note 9 do you have?

Probably not a hardware fault if it happened after recent software update.
A number of note9 affected although samsung seems to disagree at the moment.

Hello,
I also have a problem with the display after waking up with the POWER button. There are tinted colors distorted and some stripes like dim lines and slow refreshing. Everything started after updating to Android 10. In fact, when the display lights up incorrectly, it starts to heat up from the bottom. Putting the smartphone aside for a moment or cooling down causes the display to work correctly.
Workaround? I turned on Active Display and first knock to activate it, then the display lights up correctly and then I unlock the screen and use normally. It is known that battery consumption increases. Of course mine is Exynos.

hi guys,, i remember a similar experience sometime back.. try this. if u have turn on the proximity sensor i mean the advance feature where the phone screen doesn't turn on while in pocket , switch it off and restart the phone and see if the problem still exist.

i am having same issue
is anybody on xda come to rescue our issue?? friends need urgent help out ., if the solution is to reinstall the firmware kindly tell how to ?? while phone is just giving odd lines and not responding to touch even ??

ahmadtanveer7007 said:
is anybody on xda come to rescue our issue?? friends need urgent help out ., if the solution is to reinstall the firmware kindly tell how to ?? while phone is just giving odd lines and not responding to touch even ??
Click to expand...
Click to collapse
whats the firmware version u are having now and phone model?

Try wiping the cache partition in Recovery Mode. If that doesn't work then back up your device and manually reinstall the OS back onto your device.

Im having the exact problem. I flash LineageOS and it worked by max brightness then back to auto. I installed brightness widget to max brightness and back to auto everytime I turn on screen.
This issue is popular after March update. I tried everythings you mentioned above, reset, flash new firmware, even April update, wipe cached, flash cooked rom, heat screen, turn off features, disable gpu overlay, etc... Samsung Vietnam guaranteed can fix with new screen but I'm out of warranty.

I dont have any issues us unlocked snapdragon xaa model on latest android 10 version.

Can we confirmed that a screen replacement fixes the display problem or is it still a software issue

Signup said:
Who else are facing the same problem ?
1)Initially, when I unlock phone by pressing power button the display was changed to dim colour(mostly yellowish) and with horizontal lines displayed when the brightness is below 50%. After tried with multiple times pressing on power button the display came back to normal.
2) Next stage, it's not solved with power button. I have to keep my phone aside for some time to get back to normal display. It's been 15 to 20 min then.
3) Now, I would get normal display only in morning. Else, I need to keep my phone idle without touching for at least 4 to 5 hours. I've also changed screen power off time from 30 Sec to 10 Minutes. So that my screen wont turn off and I can keep the normal display. If I forgot to use or kept aside more than 10 min then my screen would go off and display would gone again and irritation starts with that discoloration problem..
4) If display changes to yellowish to reduce the horizontal lines problem I need to increase the brightness to 80 or 85% but this causing my phone with another problem "heating issue"
Samsung haven't responded on this issue yet, how could we bring up the issue and get the proper resolution from Samsung.
Click to expand...
Click to collapse
I have the same problem at the beginning it was when the phone was warm now the screen is yellow and when I lower the brightness I have lines coming out

jonaki said:
I have the same problem at the beginning it was when the phone was warm now the screen is yellow and when I lower the brightness I have lines coming out
Click to expand...
Click to collapse
Hi Bro, the same problem now facing by many users. We have created a Telegram group do discuss about the issue. Plz join there.
https://t.me/samsungDisplayProblem

luisfer21069 said:
Can we confirmed that a screen replacement fixes the display problem or is it still a software issue
Click to expand...
Click to collapse
No one knows what is the exact cause here, its noticed in many devices right after this March update but few are noticed months before. But, now the problem came to many users at same time. So its been brought up by many tech blogs, websites.

pheonixxdark said:
hi guys,, i remember a similar experience sometime back.. try this. if u have turn on the proximity sensor i mean the advance feature where the phone screen doesn't turn on while in pocket , switch it off and restart the phone and see if the problem still exist.
Click to expand...
Click to collapse
Thanks for tour suggestion, however I couldn't find the the exact option you mentioned in advanced features plz look into below once and help me to solve this.

joedellosso69 said:
This happened after last March update installation?
What note 9 do you have?
Click to expand...
Click to collapse
Hi, Yes like many other saying I too have this problem after March update only. I'm using Exynos one and also please have a look at below screenshot. Please let me know if you need anything further to know about the issue also attaching the links about the issue.
https://r2.community.samsung.com/t5...tion-amp-Overheating-Posting-4th/td-p/4049910
https://www.sammobile.com/news/galaxy-note-9-march-2020-security-update-broken-screen/
https://www.androidauthority.com/samsung-galaxy-note-9-march-update-broken-displays-1103766/
https://www.androidheadlines.com/20...in-of-broken-display-after-march-update.html/

pheonixxdark said:
whats the firmware version u are having now and phone model?
Click to expand...
Click to collapse
Please have a look into below screenshot. Plz let me know if you need any other info.

Rosli59564 said:
Probably not a hardware fault if it happened after recent software update.
A number of note9 affected although samsung seems to disagree at the moment.
Click to expand...
Click to collapse
Yes Bro but, We haven't found any fix for this till now.

Signup said:
Hi, Yes like many other saying I too have this problem after March update only. I'm using Exynos one and also please have a look at below screenshot. Please let me know if you need anything further to know about the issue also attaching the links about the issue.
https://r2.community.samsung.com/t5...tion-amp-Overheating-Posting-4th/td-p/4049910
https://www.sammobile.com/news/galaxy-note-9-march-2020-security-update-broken-screen/
https://www.androidauthority.com/samsung-galaxy-note-9-march-update-broken-displays-1103766/
https://www.androidheadlines.com/20...in-of-broken-display-after-march-update.html/
Click to expand...
Click to collapse
I'm having the exynos version too but with ITV (Italy) firmware ...never had this problem and now I'm on April's version after March's version.
This looks a little bit like what happened to the S5 years ago when after 1 and a half/ 2 and a half year's the screan began flickering, having green spots or lines, randomly didn't go on with low luminance settings since it completely died....a lot of people said on forum's that it was the screen and a replacement solves, but when it happened to me years ago the Samsung assistance center told me that it was another component (never told me what it was) causing the issue and once they changed it , they solved the problem.
So, after my experience with the S5, don't know what to think now for what is happening to some guys even if I think that this issue might depend with something happening after marchs update because for the too many people having it after the update, coincidences are not credible.

joedellosso69 said:
I'm having the exynos version too but with ITV (Italy) firmware ...never had this problem and now I'm on April's version after March's version.
This looks a little bit like what happened to the S5 years ago when after 1 and a half/ 2 and a half year's the screan began flickering, having green spots or lines, randomly didn't go on with low luminance settings since it completely died....a lot of people said on forum's that it was the screen and a replacement solves, but when it happened to me years ago the Samsung assistance center told me that it was another component (never told me what it was) causing the issue and once they changed it , they solved the problem.
So, after my experience with the S5, don't know what to think now for what is happening to some guys even if I think that this issue might depend with something happening after marchs update because for the too many people having it after the update, coincidences are not credible.
Click to expand...
Click to collapse
Yes, many people were facing this problem and how many times we have contacted the Samsung they are behaving like they just hearing the issue for the first time. Just created and posted the link in Members app and 67 members joined so far. Everyone having the display problem out of nowhere. All of them on out of warranty except one or two. Still members app floating with the display problem messages.
Display issue got noticed in S20 too but they immediately released the security patch and solved it. Don't know why they were silent on Note 9.
https://www.androidauthority.com/samsung-galaxy-s20-ultra-green-tint-1107738/

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?

All (almost) sensors stop working

Hi everyone,
Almost all sensors stoped working after few days on my brand new Pixel 5 :
Failing sensors :
- Proximity sensor
- Accelerometer
- Gyroscope
- Compas
And maybe others I don't know of...
Fingerprint & cameras are still working.
I've contacted Google support, and they advise me to clean my screen :-/
I'll try a factory reset today before asking for a replacement unit, but my hope is low...
Anyone facing the same issue ?
Any advise ?
Edit :
After a factory reset : same situation

Same here. Had phone for about ten days. All seemed to work. Then thinks went weird over several days. First thing I noticed when going to hang up a call I was no longer presented with phone dialler screen. During calls phone was also spontaneously switching to handsfree. I suspect this was wall tilt related. Then camera images were in incorrect orientation. Google photos not longer rotating images and so on. Installed a sensor app and it reported gyroscope as missing. Clean booted - no change. Factory Reset and still no change. Arranged for an exchange with Google. While waiting for that to pan out, after about a day the gyroscope has come back to life. Although presently reporting no compass. Doe the P5 have a compass?
Anyhow given it working again now I am wondering if some power saving activity is killing the Gyroscope? Waht was the out come with your sensor failure. Did they recover or did you need to exchange?

logger said:
Doe the P5 have a compass?
Anyhow given it working again now I am wondering if some power saving activity is killing the Gyroscope? Waht was the out come with your sensor failure. Did they recover or did you need to exchange?
Click to expand...
Click to collapse
I tried a random app from the store : Sensor Test with my bad unit and it reported 0 sensor !
I've exchanged my P5 and now the same app reports 30 sensors.
While waiting for the exchange , mine never came back to life : can't rotate, screen stayed on during calls (and auto brightness not working), compass was not working in Maps...
Also on the faulty unit I noticed that the OTA update tooks ages (30 minutes or so, for a ~30MB update). On the new unit, the same uptate took just a normal reboot time.

Thankyou for the update.
While mine has a working gyroscope (at the moment) the proximity sensor is still borked and the screen stays on during calls. I just installed the Sensor Test app and it says I have 16 sensors!

30 for me
Sent from my Pixel 5 using Tapatalk

30 sensors also for me.

Oh my god yes exactly this happened to my phone since yesterday. No auto rotation, no auto brightness, no tap2wake.
I have to send mine back, I hate it. Sensor app does not recognize a single sensor. Factory reset didn't help either
When rebooting like 10 times it changes between 0, 1 and 16 sensors.

I factory reset my phone again and that made it worse. Has gone from 16 to 0 on Sensors Test!
Has lost screen rotation again.

logger said:
I factory reset my phone again and that made it worse. Has gone from 16 to 0 on Sensors Test!
Has lost screen rotation again.
Click to expand...
Click to collapse
At this point, you should contact Google Support and ask for an exchange.
Like my old one, I doubt this is a software issue...
I hope my new one does not have this flaw.... but this definitely hurt my confidence in P5 devices....

Sounds like issue with corrupt persist partition caused by update gone wrong.

dannejanne said:
Sounds like issue with corrupt persist partition caused by update gone wrong.
Click to expand...
Click to collapse
Indeed ! I didn't know about this.
But it seems that the solution is to root the device, and this void the warranty (Google asked me if it was rooted before the exchange).

Weird. It did not happen to mine right after an update, more like 20 days later. Btw Google did not ask me if I rooted the device, which I haven't, but I did unlock the Bootloader for a short period of time to use the android flash tool from Google.
I'm not very familiar with partitions on android but all I can say is that a newly flashed stock firmware from Google itself did not help me

All my sensors work according to that app - it shows 30 sensors every time I launch it - except the proximity sensor sometimes does not actually work right. I was noticing an issue because KinScreen would think my proximity sensor was covered and would turn the screen off because the proximity sensor looked to be covered when it was not, even though the app should have kept the screen on. I downloaded multiple sensor testing apps and the proximity sensor works most of the time but sometimes it does not. Weird. Not sure if I should exchange the phone, I got this with AT&T.

AlEsC said:
At this point, you should contact Google Support and ask for an exchange.
Like my old one, I doubt this is a software issue...
I hope my new one does not have this flaw.... but this definitely hurt my confidence in P5 devices....
Click to expand...
Click to collapse
Took a couple of weeks, but I now have a replacement unit. 30 sensors showing and all working properly now. I took it for granted how reliant these devices are on having sensors working for basic things like the phone to work properly. Glad I found this thread and was able to get it sorted out. thanks for the help.

I had to get a replacement PIxel 5 through AT&T for the broken proximity sensor. This one works fine.

Couple of weeks?
I got a new device within 4 days where 3 days were for shipping

Just out of curiosity, am I the only one Google asked if I have rooted my device before sending it back ?
They asked me 5 questions for the warranty (I live in France/EU btw):
- Has the device been impacted, or is the screen damaged?
- Has the device come into contact with liquid?
- Has the device been in contact with a heat source?
- Has the device been rooted?
- Has the device been repaired by unauthorized personnel?

AlEsC said:
Just out of curiosity, am I the only one Google asked if I have rooted my device before sending it back ?
They asked me 5 questions for the warranty (I live in France/EU btw):
- Has the device been impacted, or is the screen damaged?
- Has the device come into contact with liquid?
- Has the device been in contact with a heat source?
- Has the device been rooted?
- Has the device been repaired by unauthorized personnel?
Click to expand...
Click to collapse
I started an RMA process on their website and no I'm not 100% sure about the other stuff but I'm sure they didn't ask if I was rooted.
Germany

I see where Google announced that a fix in the December update could possibly fix the sensor issue for some. I'm guessing you guys got the update and it didn't work huh.

idk I got a new device in december