Database Develop

Anyone facing ghost touch on rooted 4.4?

I have unlocked and rooted with the latest 4.4 but have been facing lot of ghost touch, over heating and freeze. Is anyone else facing the same issues with their z1?

ravi_buz said:
I have unlocked and rooted with the latest 4.4 but have been facing lot of ghost touch, over heating and freeze. Is anyone else facing the same issues with their z1?
Click to expand...
Click to collapse
I haven't as yet but I did notice that the touch screen issue I had where my finger / thumb would lose contact briefly with the screen.
Hasn't happened a lot and holding the metal frame fixes it.
What youre describing could be a knock on effect of the new firmware having a higher sensitivity to the previous firmwares, I know Sony were aware of the touchscreen issue that people were facing and there was a fix where you could alter the sensitivity of the touch screen.
Could be that your touchscreen is set too high for your device in particular, either that or it's a problem with the touchscreen or even some dirt.
Give it a good old clean and a few reboots.
All the above is speculation of course, just having a stab at it for you m8.
Not sure where that thread is about the touchscreen but it's definitely in the Z1 forum.

dladz said:
I haven't as yet but I did notice that the touch screen issue I had where my finger / thumb would lose contact briefly with the screen.
Hasn't happened a lot and holding the metal frame fixes it.
What youre describing could be a knock on effect of the new firmware having a higher sensitivity to the previous firmwares, I know Sony were aware of the touchscreen issue that people were facing and there was a fix where you could alter the sensitivity of the touch screen.
Could be that your touchscreen is set too high for your device in particular, either that or it's a problem with the touchscreen or even some dirt.
Give it a good old clean and a few reboots.
All the above is speculation of course, just having a stab at it for you m8.
Not sure where that thread is about the touchscreen but it's definitely in the Z1 forum.
Click to expand...
Click to collapse
Cleaned it and rebooted. Din have this problem before rooting..but as soon as i rooted i started seeing these things happpen

ravi_buz said:
Cleaned it and rebooted. Din have this problem before rooting..but as soon as i rooted i started seeing these things happpen
Click to expand...
Click to collapse
So on the base that you were on you didn't have any issues, Rooting itself will not cause this issue.
What base were you on prior to rooting and what are you on now?

dladz said:
What youre describing could be a knock on effect of the new firmware having a higher sensitivity to the previous firmwares, I know Sony were aware of the touchscreen issue that people were facing and there was a fix where you could alter the sensitivity of the touch screen..
Click to expand...
Click to collapse
How can I alter the sensitivity of the Touch Screen?
EDIT: sorry, I forgot you don't know where it is..
---------- Post added at 02:32 PM ---------- Previous post was at 02:23 PM ----------
ravi_buz said:
Cleaned it and rebooted. Din have this problem before rooting..but as soon as i rooted i started seeing these things happpen
Click to expand...
Click to collapse
Same here, after rooting mine, it starts again the touch screen to respond strange, but not a big problem. Did not had this on .136.
dladz said:
So on the base that you were on you didn't have any issues, Rooting itself will not cause this issue.
What base were you on prior to rooting and what are you on now?
Click to expand...
Click to collapse
Actually Rooting can cause the issue because the Pre-Rooted version can be different from the original one installed on our phone.
After I received the phone from Repair they updated the Software and then I updated to .136 officially and the issue disappear, never had even a bit of it. Then I rooted, but to do so I used a different Base, NUT use the Frence region I think, and after that on mine .136 the problem with Touch Screen appear again, not badly, all is fine but sometime it skips something.
So I think it's really related to the Software and the all the phone have a specific Base.

eclyptos said:
Actually Rooting can cause the issue because the Pre-Rooted version can be different from the original one installed on our phone.
After I received the phone from Repair they updated the Software and then I updated to .136 officially and the issue disappear, never had even a bit of it. Then I rooted, but to do so I used a different Base, NUT use the Frence region I think, and after that on mine .136 the problem with Touch Screen appear again, not badly, all is fine but sometime it skips something.
So I think it's really related to the Software and the all the phone have a specific Base.
Click to expand...
Click to collapse
Then it would be down to the rom and not the rooting process, rooting alone won't affect the touchscreen m8.
The Rom could though.

dladz said:
Then it would be down to the rom and not the rooting process, rooting alone won't affect the touchscreen m8.
The Rom could though.
Click to expand...
Click to collapse
Of Course.

i have not experienced ghost touch but i did experience the screen failing to register two finger touch sometimes.
what i mean by that is when u quickly touch another part of the screen after its been touched it would register it as a swipe.
very annoying when typing keyboard or even pressing key pin on lockscreen.
i reproduced this in touch test and
once it registers as a faulty swipe while holding down the touch
it keeps registering swipe wherever the other finger presses untill i stop touching.
also when i installed a fresh rom it seems that the touch is very sensitive.
i tried this out http://forum.xda-developers.com/showthread.php?t=2691849
its not a fix but it helps out.

I think i have drilled down to the cause for this issue.
1. I started mounting my phone on my motorbike and ride. Due to excessive vibration the screen might have started acting out.
2. I also read that x alert causes this.
I have locked bootloder and installed stock ROM. Lets see whats happens

ravi_buz said:
I think i have drilled down to the cause for this issue.
1. I started mounting my phone on my motorbike and ride. Due to excessive vibration the screen might have started acting out.
Click to expand...
Click to collapse
I don't think this cause the issue.
ravi_buz said:
2. I also read that x alert causes this.
Click to expand...
Click to collapse
What is that or where it is?

Been trying to find that adjustment you can make for the touchscreen but can't find it. Its an adjustment of a file within android which deals with how sensitive the touch screen is. Buggered if I can find it though. I commented on it too. Eluded me.
Sent from my C6903 using XDA Premium 4 mobile app

dladz said:
Been trying to find that adjustment you can make for the touchscreen but can't find it. Its an adjustment of a file within android which deals with how sensitive the touch screen is. Buggered if I can find it though. I commented on it too. Eluded me.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe that Calibration.ini file magically can help?
BTW, if you find that thread let me know because I am interested too in changing the sensitivity, I will like to play with that.

eclyptos said:
Maybe that Calibration.ini file magically can help?
BTW, if you find that thread let me know because I am interested too in changing the sensitivity, I will like to play with that.
Click to expand...
Click to collapse
Will do m8.

dladz said:
Will do m8.
Click to expand...
Click to collapse
I would definitely be interested in this as well so could you please inform me as soon as you find something? Thanks

I am unable to pin point the problem.
1. Its not bcoz of root/boot loader
2. Not bcoz of mouting it on my bike. Infact when i mount it, it functions normally.
3. Ghost touch worsens when i play clash of clans but it is there other times too.
So its either bcoz of over heating (games make the phone heat a lot) or water entered it or i am not sure.

http://forum.xda-developers.com/showpost.php?p=51742613&postcount=8
He found my thread
I always surf the forums and check out what is happening, and this thread did catch my eye
I don't like to think that the touch screen issue is hardware related. I really hope it isn't.
Don't put your heart on this 'fix', as I have lost faith in it myself...
I'm going to post there now as well, to tell people what I have said here.

[Q] Random touches, can someone help with a fix ?

Hello there
Did any of you experienced this problem :
http://youtu.be/hitxapYdGl0
If I lock and unlock the screen, it solves it temporarly, untill the next time it occures.
Tried every fix found on xda ( dissabled x-reality, done the calibration thing, etc )
Flashed anoter .ftf firmware ...
If anyone has a sugestion, or a possible fix, i would try it happily.
If not, I will put gasoline on it, and burn this "*****" down ...

Seems like a hardware related issue to me

I have same issues sometimes, but didn't try to resolve problem.
I lock screen and unlock, it fix for some time.
Sent from my C6903 using XDA Free mobile app

Ihave got that experience when my phone become hot

Well, honestly this is not a 100$ phone. So things like this should never happened ...

It's a globally problem
Sent from my C6903 using XDA Free mobile app

Are you having this problem ?
I have a friend with a white Z1 and he isn't suffering from this.

Someone should contact sony centar about this problem, unfortunatly i cant because i leave in country that companys dosent love so much.

I ve removed the anti shatter film from my z1, The screen feels more responsive now ... I ll wait and see if the problem still persists ...

Al3xxxinho said:
I ve removed the anti shatter film from my z1, The screen feels more responsive now ... I ll wait and see if the problem still persists ...
Click to expand...
Click to collapse
Ok, give me report on this one.

Ok ...
Things i've noticed so far :
- touchscreen is more responsive without the antishatter film
- if the phone is used only for basic things and does not heat up, the touchscreen works flawlessly
- if the phone is used intensively and heats up, things start to look messy ( for example if i run quadrant 4 times in a row, there is a very very big probability for the "problem" to occure.
- if the problem occures, regardless of the temperature of the phone, if you lock it and unlock it, the problem disappears, untill the next time it appears.

OK this is definitely a hardware issue for this device (globally, it has to be). The only I fixed it is my cleaning the grease/oil/sweat etc from the screen with a piece of cloth or directly washing it with water. I do this once in 3 days, I no longer experience this issue when the screen is clean.

Made another video
https://www.youtube.com/watch?v=N42NX8hP8nM
Ran a stability test which heated the phone to ~40 degrees. As you can see in this video, the problem starts to appear, and disappears as the phone cools down. This happens every time I run the test and the phone gets hot.
Well f*** you Sony !!!

I have exactly the same problem! Only lock unlock fixes it for some time. Very annoying!
Sent from my iPad using Tapatalk

It is hardware problem. I had the same problem and replaced it with brand new phone
But I have a new problems on new mobile
Notification bar comes down itself very often (see video below)
Sometimes screen stops working and I have to restart phone
Restarting fixes the problem for a few hours
Can you tell me is this software bug or hardware problem? I can not contact support at this time

i had experienced this problem but it was no hardware problem
+ try to remove any screen guard if applied to your screen
+ try to remove asf
+check if pen mode is enabled and disable it

Jedidiah-Morse said:
It is hardware problem. I had the same problem and replaced it with brand new phone
But I have a new problems on new mobile
Notification bar comes down itself very often (see video below)
Sometimes screen stops working and I have to restart phone
Restarting fixes the problem for a few hours
Can you tell me is this software bug or hardware problem? I can not contact support at this time
Click to expand...
Click to collapse
Mostly i have problem like you, and i dont know what it couse that.
Anyway, yesterday i was on skype with my GF, and my phone heat up, and then i found that my phone recognized touches on the left side next to front face camera. Basicly, there is no digitizer, no screen, so, how can my phone recognize touch up there?

NiM72NiK said:
i had experienced this problem but it was no hardware problem
+ try to remove any screen guard if applied to your screen
+ try to remove asf
+check if pen mode is enabled and disable it
Click to expand...
Click to collapse
Thank you, I removed screen protector and will see if the problem occurs again
But how can I disable pen mode? It is not in the settings menu
And one question, what is asf?
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
Do you mean anti scratch film? I can not remove it because phone is under warranty

Jedidiah-Morse said:
Thank you, I removed screen protector and will see if the problem occurs again
But how can I disable pen mode? It is not in the settings menu
And one question, what is asf?
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
Do you mean anti scratch film? I can not remove it because phone is under warranty
Click to expand...
Click to collapse
Hmmm...seems you are on stock and it shows the pen mode is not enabled... So pen mode is not on... Are u using any screeb guards on your asf?

NiM72NiK said:
Hmmm...seems you are on stock and it shows the pen mode is not enabled... So pen mode is not on... Are u using any screeb guards on your asf?
Click to expand...
Click to collapse
Yes I am on stock. I never root/jailbreak my phones
Right, I had applied matte screen protector on the asf and removed it few minutes ago

[PROBLEM] [BUG REPORT] Delay in every Nougat-based ROM in fingerprint unlock

Hello people, I've noticed a very annoying problem, that happens with every notable custom ROM based on Android 7. Tried LOS (CM based), Slim (AOSP based), and RR as well. Sometimes it takes a lot of time to unlock the screen when putting the finger on the home button on all of these roms, it usually should 1,5 secs but it can take up to 4. This never happens when the phone is locked from less than 5-6 seconds, or when it is charging. Does this happen to any of you? Please share your experience below.

Nope.
Fast as usual.
I'm on RR 5.8.1 btw.

Do any of you with this problem have a Sharp panel?

Bytecode said:
Hello people, I've noticed a very annoying problem, that happens with every notable custom ROM based on Android 7. Tried LOS (CM based), Slim (AOSP based), and RR as well. Sometimes it takes a lot of time to unlock the screen when putting the finger on the home button on all of these roms, it usually should 1,5 secs but it can take up to 4. This never happens when the phone is locked from less than 5-6 seconds, or when it is charging. Does this happen to any of you? Please share your experience below.
Click to expand...
Click to collapse
The same as you,l think it's a bug of lineage OS.

Xiaoyu Jiao said:
The same as you,l think it's a bug of lineage OS.
Click to expand...
Click to collapse
Ooooh nice to see I'm not alone on this. Can you put the phone in airplane mode, close all apps, let it sleep for ten seconds, and try to wake it up touching the fingerprint, and see how much it takes?
EDIT: also, when did you buy your phone? And when was it manufactured?

While rare, I have this same problem using CM. There is a small delay to wake up with the fingerprint, it takes 1 or 2 seconds.
It's a brand new device, received this month from Banggood.

Bytecode said:
Ooooh nice to see I'm not alone on this. Can you put the phone in airplane mode, close all apps, let it sleep for ten seconds, and try to wake it up touching the fingerprint, and see how much it takes?
EDIT: also, when did you buy your phone? And when was it manufactured?
Click to expand...
Click to collapse
I did as you said,and it took about 1-2seconds for my phone to wake up.I bought it in July last year,and it was manufactured in April last year.Excuse me for my bad English since I'm a Chinese.
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
Bytecode said:
Ooooh nice to see I'm not alone on this. Can you put the phone in airplane mode, close all apps, let it sleep for ten seconds, and try to wake it up touching the fingerprint, and see how much it takes?
EDIT: also, when did you buy your phone? And when was it manufactured?
Click to expand...
Click to collapse
I'm using the latest official lineage OS.

Xiaoyu Jiao said:
I did as you said,and it took about 1-2seconds for my phone to wake up.I bought it in July last year,and it was manufactured in April last year.Excuse me for my bad English since I'm a Chinese.
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
I'm using the latest official lineage OS.
Click to expand...
Click to collapse
All right. So 2016.04? And also, could you check if you have a Sharp display on your phone? (no worries about your english!)
BananaPrime said:
While rare, I have this same problem using CM. There is a small delay to wake up with the fingerprint, it takes 1 or 2 seconds.
It's a brand new device, received this month from Banggood.
Click to expand...
Click to collapse
I understand. Can you try to put it into airplane mode, close all apps, lock the screen and let it sleep for a while, and see how long does it take to unlock? Also, can you check manifacture data and panel manufacturer (Sharp, JDI, LGD)?

Bytecode said:
All right. So 2016.04? And also, could you check if you have a Sharp display on your phone? (no worries about your english!)
I understand. Can you try to put it into airplane mode, close all apps, lock the screen and let it sleep for a while, and see how long does it take to unlock? Also, can you check manifacture data and panel manufacturer (Sharp, JDI, LGD)?
Click to expand...
Click to collapse
The packing box has been thrown away by me,but I vaguely remember the number 201604 is written on the box.Display is jdi not sharp,In China, it's just as hard as hitting the jackpot to get a sharp display; almost all are jdi.What about your country.

Xiaoyu Jiao said:
The packing box has been thrown away by me,but I vaguely remember the number 201604 is written on the box.Display is jdi not sharp,In China, it's just as hard as hitting the jackpot to get a sharp display; almost all are jdi.What about your country.
Click to expand...
Click to collapse
Sharp :/ and I bought it from a Hong Kong Aliexpress store..

I will test in airplane later, but how do I check my screen manufacturer?
Here's the last line:
mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_lgd_fhd_td4322_cmd:1:none:cfg:single_dsi
In general I don't this delay is a big issue, at least for me it only happened a delay above 2 seconds once.

lte+
Hello . I have the mi5 32 GB version. Operators in my country in two band 1800, lte 2600 provides the lte Internet. But I do not have 4g+. Other phones have 4g+ .Carrier Aggregation not work. i am on miui global stable 8.1 . in cm14.1 Carrier Aggregation is work ?

Bytecode said:
Sharp :/ and I bought it from a Hong Kong Aliexpress store..
Click to expand...
Click to collapse
......

So, It seems my display is LGD (LG Displays).
I cleared all apps and put my phone in Airplane mode and somehow it got WORSE, I have to put my finger more than once and it takes 2-3 seconds until the screen turn on.
If I disable airplane mode it goes back to normal.

BananaPrime said:
So, It seems my display is LGD (LG Displays).
I cleared all apps and put my phone in Airplane mode and somehow it got WORSE, I have to put my finger more than once and it takes 2-3 seconds until the screen turn on.
If I disable airplane mode it goes back to normal.
Click to expand...
Click to collapse
Yep, have this problem too!

Same for me

I didn't get this with stock LOS, installing any sort of custom kernel has the issue.
Is there a way I can find out what display I have without the phone box?

No problem for me, on 32gb version with LOS, stock or custom kernel.

Happens on los based ROMs for me not on aosp.

Ambient display bug

Good evening.
I have noticed a bug with the ambient display. I have it to be permanently active but either when a notification comes or if something covers the light sensor it stops working and if you do not press something on the mobile the screen is dark. Does it do this to you? Thanks.

When you cover the light sensor it thinks that the phone is in your pocket and that's the reason it turns the always on display off.

tonev said:
When you cover the light sensor it thinks that the phone is in your pocket and that's the reason it turns the always on display off.
Click to expand...
Click to collapse
I know...but when tou take away your hands does not come back thats the point...
I think the same happens after a notification

I have noticed the exact same issue. Rebooting the device seems to fix the issue temporarily and after an hour or so it comes back. That is really annoying.
---------- Post added at 06:42 PM ---------- Previous post was at 06:35 PM ----------
tonev said:
When you cover the light sensor it thinks that the phone is in your pocket and that's the reason it turns the always on display off.
Click to expand...
Click to collapse
But once out of pocket or hand is removed from the proximity sensor, the AOD should light up again. My unit is actually doing it right for sometime when rebooting, than stops and I get back screen too until I double tap or push power button.
---------- Post added at 06:48 PM ---------- Previous post was at 06:43 PM ----------
eddiedimitris1981 said:
Good evening.
I have noticed a bug with the ambient display. I have it to be permanently active but either when a notification comes or if something covers the light sensor it stops working and if you do not press something on the mobile the screen is dark. Does it do this to you? Thanks.
Click to expand...
Click to collapse
Did you solve the problem? I'm actually thinking to contact Sony.

After a couple of test, I also noticed that when it happen even notification do not wake up the screen (despite option being selected)

This happened to me as well, was connected to the auto brightness issue I faced. The issue went away after a couple days. Ambient display worked normally then. I have mine set to always on as well.

Adaptive brightness also have bug,,mine it get delay to automatic brightness in outdoor and indoor
X1 II AT52
Already lates update

iArvee said:
This happened to me as well, was connected to the auto brightness issue I faced. The issue went away after a couple days. Ambient display worked normally then. I have mine set to always on as well.
Click to expand...
Click to collapse
Using the device for serveral days now but no improvements.
May I know what Software version are you running and what model do you carry ?
My model is XQ-AT52, Build No. 58.0.A.3.39 with June 1, 2020 security patch.

Tane18 said:
Using the device for serveral days now but no improvements.
May I know what Software version are you running and what model do you carry ?
My model is XQ-AT52, Build No. 58.0.A.3.39 with June 1, 2020 security patch.
Click to expand...
Click to collapse
Yep. AT51, same build number on Customized EU.

Anyone got fix for this? @Tane18 did you contact Sony regarding this?

Fixed with factory reset with PC and Sony Companion
exFugitive said:
Anyone got fix for this? @Tane18 did you contact Sony regarding this?
Click to expand...
Click to collapse
The issue got fixed when I did a factory reset/software repair with Sony PC companion.

Tane18 said:
The issue got fixed when I did a factory reset/software repair with Sony PC companion.
Click to expand...
Click to collapse
Good to know, will try reset the phone.
Did you factory reset using the Android itself or using tool?
FYI, I just got this phone recently and use flashtool to update and wipe everything before using it.
Sounds like this is commom issue for Android 10 (some Pixel device had this issue).

Software repair via PC with USB cable
exFugitive said:
Good to know, will try reset the phone.
Did you factory reset using the Android itself or using tool?
FYI, I just got this phone recently and use flashtool to update and wipe everything before using it.
Sounds like this is commom issue for Android 10 (some Pixel device had this issue).
Click to expand...
Click to collapse
I used the Xperia Companion software on laptop with USB cable to phone

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?