Database Develop

[Q] Screen flickering under WiFi data transfer

Hi,
I have my sgs about 2 months and I'm very happy with it. The only problem I have is, that sometimes there are strange displayinterferences.
It looks like there are moving waves from top to down.
Does anybody have this troubles too and has a solution for it?
Or is it an hardware error? The problem is that the error isn't reproducable.
Maybe somebody can help me, please!
Thanks in advance
spyro

I think I have also noticed that once or twice. I believe it can be seen when you have the android drop down menu (notifications etc) open and you start or stop WiFi. It must be some kind of interferance with wifi hardware. Normal wifi operation does not cause it, only the startup of the WiFI which lasts one second or so.

Yeah, i think this could be true. I also see it often, when I open die Notification bar. But I also have the same interferences, when I am working in apps. Maybe also the 3G connection could be the reason? Does anybody else have this problem.
Is this a problem, which I have to life with or could this be an error of the hardware(warranty)?

http://forum.xda-developers.com/showthread.php?t=753402
I have the same problem. Never on wifi tho.
Which firmware are you using?

Hi,
my firmware is I9000AUJF1(A1 branded from Austria). I don't know if the problem in your posted thread is the same. The interferences I mean only exist one or two seconds. There are horizontal dark lines which moves from top to the bottom. After some time everything is OK again. It looks like anything interfers the display(wifi, 3g?).
The problem of warranty is, that I'm not able to show the problem, because it's not reproducable.

Screen flickering under WiFi data transfer
I noticed this problem a couple of days ago.
Whenever there is some data transfer going on over WiFi, wherever I am browsing or some service syncs up the screen starts flickering and I have what I can describe as faint scan lines crossing the screen vertically like there is some sort of interference.
These are mostly noticeable on white and light grey backgrounds.
I have gone trough 2 firmware updates currently being on stock JPK rooted.
I have searched around on google and found on some forum one guy that was saying the cause is an interference between the WiFi module and the screen refresh rate.
Has anybody encountered this problem or these symptoms ?
Is there somebody around more knowledgeable in this issues that can confirm that this is a hardware problem ?

wow! , you might have a defective phone then.
I use WiFi very often, Wireless N at aprox 87 Mbps
that should be high enough to reproduce the problem you experienced, if i had a faulty screen
the description of the scan line reminds me of interference when you are in close proximity with another LCD or CRT screen causing the distortion field

OMG, I get this too. Usually happens on boot or when I'm browsing a data heavy website or using Android market. Are our phone defective? Does anyone else have this problem? I wonder how common it is.

does the scan line comes from bottom up
or goes from top to bottom?
very slowly or fast?
if you are pluged in and charging, also are you in a 120v or 240v?

AllGamer said:
does the scan line comes from bottom up
or goes from top to bottom?
very slowly or fast?
if you are pluged in and charging, also are you in a 120v or 240v?
Click to expand...
Click to collapse
They tend to be random and I'm on battery power atm. Also they're quite fast but don't last very long. They'll start then stop then start etc ..

Hi,
just for your information. I've sent my phone to samsung on friday. Maybe they find the error. I report, if there are new information.

Yep i have the same problem. Can t find the source though....
Sent from my GT-I9000 using Tapatalk

The lines appear from top and travel the screen fast.
Imagine a TV who for a second has problem with reception.
I am on 240 V.
Also the issue is much more noticeable when not plugged in.
If I have the phone plugged in its barely noticeable.
I will try to call the service and ask about this issue. I have a strong feeling that this is a hardware issue. But Besides the screen being defective I also think about the battery. Maybe when in high load (WiFi) it's voltage varies and affects the screen.

It seems if I uncheck Power saving mode in Settings>Display and also uncheck Automatic brightness things improve a bit.

segun_aduba said:
The lines appear from top and travel the screen fast.
Imagine a TV who for a second has problem with reception.
I am on 240 V.
Also the issue is much more noticeable when not plugged in.
If I have the phone plugged in its barely noticeable.
I will try to call the service and ask about this issue. I have a strong feeling that this is a hardware issue. But Besides the screen being defective I also think about the battery. Maybe when in high load (WiFi) it's voltage varies and affects the screen.
Click to expand...
Click to collapse
Another issue to worry about .. God starting to think about selling this phone and getting something else. Stuck in a 2 year contract though

some one already reported this on another topic
it does seems that some version of the phone are prone to WiFi interferance
we still haven't found out what causes it exactly
for example i can not replicate the issue on my phone when using WiFi

found it
http://forum.xda-developers.com/showthread.php?t=793944

Cant reproduce it.
Not that I'm unhappy with it...

If this is a hardware issue Samsung should replace my phone. I am waiting though a little bit before calling the service to make sure that it is a hardware problem.
If I find that it can easily be fixed with a software fix, it's not worth the hassle of trying to replace it.

can anyone in North America confirm this issue?
i got a huntch it might be an Europe only issue related to the high voltage of the electric interferance nearby, like lights, tv, radio, wifi, etc.

[Q] Phantom Taps, Bad Screens?

Does anyone have a solution for phantom taps on your NC?
I'm on my 3rd Nook Color when I pick up the replacement unit this afternoon.
My general issues are phantom taps - or the NC doing things I don't want it to. So far a very poor experience when typing, turning a page in a book, or even just navigating the ui. The whole issue may be me, it happens regardless if I am plugged in or not. I keep a very clean screen so there is very to little gunk.
I do have sweaty palms on occasion but not out of the ordinary. I have other touch devices that have never given me this issue. If anything I think the screen is overly sensitive - hardware or software issue?

Nope it's not just you. Mine has a multitude of issues with the touchscreen...
Essentially I cannot use the touchscreen when the device is plugged into stock charger/cable as wherever I put my finger, a random touch appears somewhere on the x-axis near my finger.
It seems that the device does not like changes in temperature or humidity either when it is unplugged. Using my tablet while cold was impossible, and likewise while it had been warm.
I'm on my second tablet from Best Buy-- the first one had dead pixels galore (enough to make the best buy rep say "dang!"), and now this one has a bad touchscreen and hard to press power button.
However: I purchased one of these for my mother a few days before mine at Barnes and Noble, and it has no issues whatsoever... at least not yet.
I've come to the conclusion that this hardware is quite beta, but I'm willing to give them a chance since it is the best bang for the buck, even if I have to go through a couple of returns... it's honestly almost worth the time for me since a tablet is so valuable for schoolwork.

Fortunately mine does not do this. I think maybe for those that are having this issue it may be able to be fixed in a firmware update.
My EVO had extremely similar problems when it first came out with the touchscreen and not being able to use the dropdown menu while the device wasn't grounded. After a firmware update the phone was great with touch sensitivity.

my first one did this also. so far the second is doing fine, but the first didn't have any problems till the 13th day of owning it.
i'm hoping it's just an issue that can be fixed via software - maybe someone put an incorrect voltage input somewhere.

I was having the same issues. I bought a screen protector and that seemed to solve it. So far, it's been working fine.

I noticed the screen protector stabilized the touchscreen a lot. Before I seem to have a problem finding the sweet spot for a touch. Now it seems better.
However, my phantom pinky is always touching something while I am trying to navigate. As long I only get one finger near the screen, it's fine.
Mine came from B&N.
The only other issue I have is the magnetic clasp in the cover seems to throw the internal compass/magnetometer off a lot.

Awats said:
The only other issue I have is the magnetic clasp in the cover seems to throw the internal compass/magnetometer off a lot.
Click to expand...
Click to collapse
Considering the Nook has neither I think you are okay.

khaytsus said:
Considering the Nook has neither I think you are okay.
Click to expand...
Click to collapse
Then how is it managing to correctly position the screen with Google Sky? Is it just spooky smart?

Mine only has problem when screen gets dirty. Try a screen protector or use gloves.

is there really a compass in this thing? I just assumed there wasn't. if there is I'm buying another tomorrow!

Screen protector helps to solve my problem.

Are you seeing more issues right after cleaning the screen? I see issues then and I think it is because I an using some moisture on the cloth. If I just dust it lightly with a dry cloth and live with a few finger prints there seem to be less of an issue.

Awats said:
Then how is it managing to correctly position the screen with Google Sky? Is it just spooky smart?
Click to expand...
Click to collapse
Wifi location services provided by Google from data collection by Street Cars or by Location Services on Android phones.
iolinux333 said:
is there really a compass in this thing? I just assumed there wasn't. if there is I'm buying another tomorrow!
Click to expand...
Click to collapse
....no

khaytsus said:
Wifi location services provided by Google from data collection by Street Cars or by Location Services on Android phones.
....no
Click to expand...
Click to collapse
Oh well, it could be worse although I don't see how Google data can tell which direction I am facing.
Thanks dad!

Awats said:
Oh well, it could be worse although I don't see how Google data can tell which direction I am facing.
Thanks dad!
Click to expand...
Click to collapse
Nor can your Nook Colour.. Using something like TetherGPS would have some heading information, but the NC itself without help would not.
It might show 0, dunno there. Maps for me just shows a dot, if yours is showing different, that'd be... interesting.
For S&G I tried "Compass", it of course FC's immediately like almost all apps that try to use the GPS. Enabled TetherGPS (with no server, just the client) and it ran, but of course no data, no heading, etc.

Is this occuring when the nook is plugged in? sometimes the charger can cause phatom touches with the touchscreen. Cleaning the screen and being on a stable ROM usually gets rid of that problem.

If only I weren't so stupid ...
khaytsus said:
Nor can your Nook Colour.. Using something like TetherGPS would have some heading information, but the NC itself without help would not.
It might show 0, dunno there. Maps for me just shows a dot, if yours is showing different, that'd be... interesting.
For S&G I tried "Compass", it of course FC's immediately like almost all apps that try to use the GPS. Enabled TetherGPS (with no server, just the client) and it ran, but of course no data, no heading, etc.
Click to expand...
Click to collapse
LOL! Ok, I sat down with it and played for a bit. It appears some tilt sensor is handling the up and down tilt. If you raise the screen over your head, it shows those stars and if you tilt it down, I see what is below the horizon. That is pretty consistent. But it's also "simulating" a compass inadvertently.
By that I mean that if I happen to turn it on facing north, it appears to track as you turn in a circle but it's really just me tilting it and it's rotating he view. If you do it enough it has no clue the direction it's facing.
I'm just glad I figured this out before I got lost in the Amazon.

Just got mine plugged it in and unplugged and within stew minutes phantom touches couldn't even reboot it im on cyanogen mod 7
Sent from my SCH-I500 using XDA Premium App

Nook Screen Recalibrate
You guys can try my app from the market

assid2 said:
You guys can try my app from the market
Click to expand...
Click to collapse
Wow, it seems to have improved the accuracy! I need to play with it more to be sure.

Getting a better look at this multitouch issue, with some good ol' community feedback

Hey guys,
Thought I'd post this here and keep you guys updated on further developments.
I live in the Netherlands and bought a 32GB version at Dixons at the 13th of November 2012
I had found the touchscreen a bit unresponsive sometimes in the past.
But couldn't really find out why it was acting up. I finally isolated the issue.
It is exactly the same as this guys vid:
(Thanks for the vid injahnet)
Together with a little backlight bleeding, I decided to send for repair.
(The problem persisted after a factory reset, no other apps were open when testing.)
I went back to Dixons and showed the problem to the Dixons dude.
He acknowledged there was an issue and sent it for repairs or replacement.
Due to the holidays this can take some time. Maybe even next year
I was about to open my tablet for a look inside one of these days, boy am I glad I didn't do that yet
Anyway to get a good view on this issue globally, are there more people that have the same issue?
You could go to: Settings > Developer options > and then under "Input" you can enable Show touches. and try to to the same procedure as in the vid. (Thanks Peterk-1)
Or you could test with MultiTouchTester like Injahnet.
The weird thing is, my dad's N7 16GB does the same.
Update 17-12-2012: Please do not test while plugged in as the device will be grounded and the issue will not occur. (Thanks dad)
Feedback is really appreciated!
Please vote in the poll above!
Cheers,
Daan

I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.

If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.

peterk-1 said:
If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.
Click to expand...
Click to collapse
Nice one. I'll add that.
khaytsus said:
I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.
Click to expand...
Click to collapse
I've done a factory reset before I tested No apps are open except MultiTouchTester
It's in for repairs

Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan

Yes, i have this problem. And only while device is laying on the table.

Wow, this is bizarre, thanks for pointing it out. I can confirm it happens when it's laying on my pillow, and doesn't when I'm holding it.

Thanks for the vote guys.
By the way, it seems obvious that the Nexus should not be plugged in while testing.
However I cannot test this 'cause mine is at the shop
Would anyone be willing to test?
I'll add that in the original post (+ a mention of your name and a thank you of course))
Cheers,
Daan

Mine was unplugged while testing.
Sent from my Nexus 7 using Tapatalk 2

if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.

herrrevo said:
if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.
Click to expand...
Click to collapse
However, zooming in Google maps for example will become quite difficult

Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.

ionstorm66 said:
Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.
Click to expand...
Click to collapse
Exactly! I was also thinking of this.
Do people who have this issue also have the flickering issue!?

ecoviws buttress
Just an FYI, I installed CM 10.1 with Trinty Seven. Now I get 10 touches on pretty much any surface.

I don't have a multitouch issue, but I do have an entire band on my screen which has stopped responding to touch at times. It all started when I let my tab shut down due to low battery. Initially, the Nexus 7 neither charged (when put on charging, obviously), nor did it boot up. After trying for several hours, somehow it started charging. And since then, sometimes certain areas of my touchscreen become unresponsive to touch. Since the band which is unresponsive is towards the upper part of the screen, using notifications becomes completely impossible. It keeps 'snapping back up' when I try to pull it down, cos while I am pulling it down, the notification tray encounters an unresponsive area, so it just goes back up. Called up Google and they will be sending a replacement device. All I am afraid about is that I have an 8gb version, and they would be sending an 8gb as well, so I hope it isn't refurbished or something, as Asus has stopped making the 8gig model.

I'm having an issue where the screen, ( mostly in a webpage or document,) starts moving up and down and zooming in and out without my input.
Sent from my Nexus 7 using xda app-developers app

Just tested this out and yes, my device is doing it too. Interesting. No other issues like screen flicker (except the auto brightness bug in 4.2). My n7 is c9O

DaanJordaan said:
Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan
Click to expand...
Click to collapse
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.

dilldoe said:
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.
Click to expand...
Click to collapse
Don't feed the trolls!
Must... not... feed... aaargh....
You are kinda missing the point of this thread.
It is to see how many people have this issue.
There is no thread capturing that in an easy way unless you want to count every post.
Now please tell your brain to start functioning again and leave this thread alone if you have nothing to add.

Asus Google Nexus 7 32GB touch death zone
Hi DaanJordaan,
Found out that my brand new N7 seems to have a similar "no touch zone" issue; an area the size of my little finger on the left lower part of my screen does not seem to react to touch! It interferes with typing the keyboard in portrait mode (no keyboard problems in up-side-down portrait mode).
When I use the Easylabs Multi Touch test I can see the dot changing color when I move over this area, doesn't happen anywhere else on the screen..
Using the developer tools (turning on the two options that allows to show touch/leave a trail of touch) it becomes even more clear that this area does not react to touch! I can "paint" lines around the "no touch zone" (it actually splits into 2 touch areas using one finger around the "death spot"), and the "no touch zone" reveals itself by not showing any trail/history line of touch..
Oh yes, and it does not matter if I lay the N7 on the table, or hold it in my hand, the issue is always there.
Therefore I returned the N7 back to the MediaMarkt, and they will send it in for repairs...
I've got a bad feeling about this | - )
I am curious to hear about experiences with your N7, once you have it back!
I'll report mine here, in three weeks or so (that's the outlook...).
Cheers!
NeverMind

Multitouch with +5 fingers

****UPDATE: *****
This is what happens https://imgflip.com/gif/1xvxm0
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
****EO UPDATE ****
I have been testing with both
Settings -> Developer Options - > Show Pointers (and looking at the top left that says x/x points)
or
Using a multitouch test app like so https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
The latter is nice because it has big handlers and you can clearly see the point/touch flickering like loosing and creating point (hence creating a new point ID)
From what i can say in Marshmallow it worked way better, on the last 2 Nougat updates i saw that at the 7th point it started to do the flickering and with this one it starts at the 5th point.
With 3 fingers screenshot disabled (and all the gestures for that matter) as i know it would create a conflict.
Just tested in a Motorola with Marshmallow and it created the 10 points flawlessly.
I wonder if any of you noticed the same or is something off with my touchscreen?
Might it be a Nougat thing ?
Any known solutions?
I searched around and nothing Nougat related seem to pop up
Just tested with both OP2 and a Moto G5 and they both work great, actually it even worked great on my Samsung Galaxy i9000
I have noticed that for the last 2 updates or so multitouch capability has been decreasing.

When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.

JarJarWinks said:
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
Click to expand...
Click to collapse
That is irrelevant for what i am trying to figure out, what i want to know is if it is a HW problem by default or just my HW is faulty or even if it is a Nougat problem.
It works flawlessly on other less capable phones

Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.

pitrus- said:
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
Click to expand...
Click to collapse
Thank you, from what i get so far is a Nougat thing, all the users that have Oreo seems to work fine

Conductive electricity ?
Ok some pretty strange updates...
I accidentally tested it on a metal table and it worked perfectly, which lead me to think that it might be due to conductive energy or something.
So i tried the test on a wooden table and it does flicker and loose touches, so i pressed with a finger on a metal part of the OP3T casing and the points are registered properly.
I had made a video so people don't think i am crazy here is the result https://imgflip.com/gif/1xvxm0 at this point i can say that is directly related.
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?

anyone ?

This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO

nagi_007pk said:
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
Click to expand...
Click to collapse
It is definitely a problem did you watched the video ? because it seems like a real hard problem to me, use cases for you might be different from others. My old samsung galaxy i9000 as well as my OP2 did not had that problem

It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?

thes3usa said:
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
Click to expand...
Click to collapse
I had the feeling that it might be from the updates (still using official OP updates) but right now i think it might be hardware. Yes i tried with other fingers, thinking about opening the phone to see if there is something touching the metal case inside.

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?