Status Update
Comments
gr...@gmail.com <gr...@gmail.com> #2
Ignore! Apparently this is WAI
na...@gmail.com <na...@gmail.com> #3
Indeed, but I think it's good feedback to improve the doc.
li...@gmail.com <li...@gmail.com> #5
bd...@gmail.com <bd...@gmail.com> #6
mi...@gmail.com <mi...@gmail.com> #7
tr...@gmail.com <tr...@gmail.com> #8
bd...@gmail.com <bd...@gmail.com> #9
So, not being able to quickly unlock my screen, and not being able to put the phone on speaker or use the dailer for the menu's during calls, makes this pixel phone currently unusable for me.
bd...@gmail.com <bd...@gmail.com> #10
bd...@gmail.com <bd...@gmail.com> #11
jo...@gmail.com <jo...@gmail.com> #12
jo...@gmail.com <jo...@gmail.com> #13
jo...@gmail.com <jo...@gmail.com> #14
mi...@gmail.com <mi...@gmail.com> #15
op...@gmail.com <op...@gmail.com> #16
google support weren't helpful
as...@google.com <as...@google.com> #17
Steps to reproduce
What steps are needed to reproduce this issue? Please provide screen recording.
Frequency of occurrence?
Expected output
What is the expected output?
Current output
What is the current output?
Android build
Which Android build are you using? (e.g. OPP1.170223.012)
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please place the files in a folder, upload it to google drive and share the folder to android-bugreport@google.com, then share the link here.
gr...@gmail.com <gr...@gmail.com> #18
What steps are needed to reproduce this issue? Please provide screen recording.
Started about a week ago. Intermittently, but more like 75% of the time face unlock gives the message Clean the top of your phone including the top bar. The phone is clean, no scratches or scuffs. When in this state, reach to wake and tap to wake no longer work.
When the unlock is working fine, I can reliable cause the issue to occur by locking the phone, placing the phone in my pocket and immediately removing. The issue also arises randomly when the phone has not been unlocked (sometimes for a while and sometimes for short periods of time).
Factory reset has not helped, safe mode did not help and deleting the face data and setting up again did not help.
Frequency of occurrence? Intermittent (80% of the time) but can reliably cause it to happen.
Expected output
What is the expected output? Face unlocks
Current output
What is the current output? Get a message to clean the top bar (its clean). Also motion sense no longer works during this state.
Android build
Which Android build are you using? QQ2A.200405.005
Android 10, May 2020 Security
Bug report and video here:
jc...@gmail.com <jc...@gmail.com> #19
ja...@gmail.com <ja...@gmail.com> #20
ja...@gmail.com <ja...@gmail.com> #21
c....@gmail.com <c....@gmail.com> #22
cd...@gmail.com <cd...@gmail.com> #23
tr...@gmail.com <tr...@gmail.com> #24
ot...@unixborg.net <ot...@unixborg.net> #25
fi...@gmail.com <fi...@gmail.com> #26
ja...@gmail.com <ja...@gmail.com> #27
ja...@gmail.com <ja...@gmail.com> #28
ja...@gmail.com <ja...@gmail.com> #29
A bug report has been submitted, developers are working on it, you have to wait for the fix, the timeline is indefinite, and they won't swap my phone for a refurbished one. Would not tell me what the warranty on the phone is and what it covers because there's a bug report already.
I also received a "warning" for saying that this support was "shit"
How is that an acceptable answer? This is my worst Google experience I've ever had and I'll be sharing.
Good luck guys they don't seem to be in a hurry on this one.
ro...@robertdarwin.com <ro...@robertdarwin.com> #30
be...@gmail.com <be...@gmail.com> #31
st...@gmail.com <st...@gmail.com> #32
Its been 2 months!!!
I have pixel buds that disconnect, Stadia that hasnt delivered whats promised, my phone is driving me to the point that i want to smash it into 100 pieces!
GOOGLE, Is there any update on this please?
gr...@gmail.com <gr...@gmail.com> #33
ja...@gmail.com <ja...@gmail.com> #34
te...@gmail.com <te...@gmail.com> #35
to...@gmail.com <to...@gmail.com> #36
bu...@gmail.com <bu...@gmail.com> #37
te...@gmail.com <te...@gmail.com> #38
nc...@gmail.com <nc...@gmail.com> #39
st...@gmail.com <st...@gmail.com> #40
go...@gmail.com <go...@gmail.com> #41
ma...@zaazee.ca <ma...@zaazee.ca> #42
st...@gmail.com <st...@gmail.com> #43
So in conclusion, Google refused to answer my questions regarding the state of a fix, or even an acknowledgement of this issue but i can tell you 100% that so far for me, changing my screen has fixed the issue, I don't know how exactly but it has.
ot...@unixborg.net <ot...@unixborg.net> #44
have seen others in this thread state the beta didn't fix it for them, but
so far it has for me.
Pixel 4 XL for the record.
On Thu, Jun 18, 2020, 8:51 AM <buganizer-system@google.com> wrote:
--
Sent from TwiSpark.com
gr...@gmail.com <gr...@gmail.com> #45
gr...@gmail.com <gr...@gmail.com> #46
vi...@google.com <vi...@google.com> #47
ja...@gmail.com <ja...@gmail.com> #49
m....@gmail.com <m....@gmail.com> #50
ke...@gmail.com <ke...@gmail.com> #51
Pixel4 128GB model.
Android 10 (QQ3A.200605.001)
ju...@gmail.com <ju...@gmail.com> #52
It's frequent enough I might disable face unlock.
yl...@gmail.com <yl...@gmail.com> #53
jc...@gmail.com <jc...@gmail.com> #54
It's driving me crazy too. I have found that if I use my shirt, or a nearby smooth cloth, and rub it back and forth over the front camera lens (top left) for about 2-3 seconds, it temporarily fixes the issue. However, this procedure often must be repeated several times a day.
jo...@gmail.com <jo...@gmail.com> #55
gr...@gmail.com <gr...@gmail.com> #56
gr...@gmail.com <gr...@gmail.com> #57
ke...@creditkarma.com <ke...@creditkarma.com> #58
gr...@gmail.com <gr...@gmail.com> #59
op...@gmail.com <op...@gmail.com> #60
ja...@gmail.com <ja...@gmail.com> #61
ja...@gmail.com <ja...@gmail.com> #62
en...@gmail.com <en...@gmail.com> #63
ja...@gmail.com <ja...@gmail.com> #64
[Deleted User] <[Deleted User]> #65
ta...@gmail.com <ta...@gmail.com> #66
su...@gmail.com <su...@gmail.com> #67
gr...@gmail.com <gr...@gmail.com> #68
ca...@gmail.com <ca...@gmail.com> #69
Happening for me as well. Beta 3. Can't quite put my finger on how to reproduce but a reset consistently (albeit temporarily) fixes it.
an...@gmail.com <an...@gmail.com> #70
di...@gmail.com <di...@gmail.com> #71
er...@gmail.com <er...@gmail.com> #72
Bug report attached:
am...@gmail.com <am...@gmail.com> #73
Additional to Face unlock not working as some others have said, the screen goes black after picking up a call to the point that nothing can wake the screen up till the call disconnects. Going into Developer Quick Settings and disabling sensors before i pick up a call is the only way i can keep the screen from not going black.
Phone : Pixel 4 XL
Build Version - RPB3.200720.005
Additionally, it gets fixed for a short time after a reboot but the problem re-appears after the phone is left idle for 20-30 min.
Bug report attached.
sj...@gmail.com <sj...@gmail.com> #74
li...@gmail.com <li...@gmail.com> #75
an...@gmail.com <an...@gmail.com> #76
br...@gmail.com <br...@gmail.com> #77
ma...@gmail.com <ma...@gmail.com> #78
nt...@gmail.com <nt...@gmail.com> #79
er...@gmail.com <er...@gmail.com> #80
da...@gmail.com <da...@gmail.com> #81
da...@gmail.com <da...@gmail.com> #82
al...@gmail.com <al...@gmail.com> #83
rn...@gmail.com <rn...@gmail.com> #84
gr...@gmail.com <gr...@gmail.com> #85
Never had it before unless the screen was actually dirty or had just wiped it with something damp (not wet).
ri...@gmail.com <ri...@gmail.com> #86
- Android version: 10
- Android security update: August 5, 2020
- Google play security update: July 1, 2020
nl...@gmail.com <nl...@gmail.com> #87
ro...@cyberjunky.nl <ro...@cyberjunky.nl> #88
fe...@gmail.com <fe...@gmail.com> #89
6i...@gmail.com <6i...@gmail.com> #90
I also have to force restart after many phone calls because my screen goes black when it's to my ear and won't light back up after I'm done with the call...
jo...@gmail.com <jo...@gmail.com> #91
tm...@gmail.com <tm...@gmail.com> #92
br...@gmail.com <br...@gmail.com> #93
This seems to be a big issue. 4XL here. Very, very annoying.
gj...@gmail.com <gj...@gmail.com> #94
le...@gmail.com <le...@gmail.com> #95
da...@gmail.com <da...@gmail.com> #96
ju...@gmail.com <ju...@gmail.com> #97
rd...@gmail.com <rd...@gmail.com> #98
Here are my settings:
- Motion sense = off
- AOD = on
- Skip lock screen = off
- Tap phone to check = on
- Life to check phone = on
- Wake screen for notifications = on
re...@gmail.com <re...@gmail.com> #99
I love this phone, please fix this issue asap!
jc...@gmail.com <jc...@gmail.com> #100
FWIW, this isn't specifically an Android 11 issue. I have been having this problem on my Pixel 4 (non-XL) since April on Android 10. I never installed the Android 11 beta, and haven't noticed a significant change in frequency of the issue across my day-one upgrade to 11 on Tuesday. Initial reports in this thread were also from 10.
no...@gmail.com <no...@gmail.com> #101
st...@gmail.com <st...@gmail.com> #102
rh...@gmail.com <rh...@gmail.com> #103
at...@gmail.com <at...@gmail.com> #104
aa...@gmail.com <aa...@gmail.com> #105
ke...@endare.com <ke...@endare.com> #106
vi...@gmail.com <vi...@gmail.com> #107
np...@gmail.com <np...@gmail.com> #108
nt...@gmail.com <nt...@gmail.com> #109
la...@gmail.com <la...@gmail.com> #110
ro...@pacbell.net <ro...@pacbell.net> #111
Updating to Android 11 didn't seem to make it better or worse.
It seems like the issue is more related to the Soli radar.
Perhaps they should have used the accelerometer to sense motion.
Anyway, it appears that face unlock has been abandoned for now.
bo...@gmail.com <bo...@gmail.com> #112
sk...@gmail.com <sk...@gmail.com> #113
vi...@gmail.com <vi...@gmail.com> #114
sp...@gmail.com <sp...@gmail.com> #115
hh...@paloaltonetworks.com <hh...@paloaltonetworks.com> #116
sm...@gmail.com <sm...@gmail.com> #117
we...@gmail.com <we...@gmail.com> #118
ro...@gmail.com <ro...@gmail.com> #119
al...@gmail.com <al...@gmail.com> #120
vi...@gmail.com <vi...@gmail.com> #121
ju...@gmail.com <ju...@gmail.com> #122
ba...@gmail.com <ba...@gmail.com> #123
ni...@gmail.com <ni...@gmail.com> #124
dj...@gmail.com <dj...@gmail.com> #125
ed...@gmail.com <ed...@gmail.com> #126
Is there any solution yet?
Or we need to wait the shitty upgrade?
sk...@gmail.com <sk...@gmail.com> #127
an...@gmail.com <an...@gmail.com> #128
md...@gmail.com <md...@gmail.com> #129
mu...@gmail.com <mu...@gmail.com> #130
ja...@gmail.com <ja...@gmail.com> #131
cl...@gmail.com <cl...@gmail.com> #132
ja...@gmail.com <ja...@gmail.com> #133
ku...@gmail.com <ku...@gmail.com> #134
ss...@gmail.com <ss...@gmail.com> #135
ka...@gmail.com <ka...@gmail.com> #136
er...@gmail.com <er...@gmail.com> #137
ro...@gmail.com <ro...@gmail.com> #138
fl...@gmail.com <fl...@gmail.com> #139
se...@gmail.com <se...@gmail.com> #140
fl...@gmail.com <fl...@gmail.com> #141
mr...@gmail.com <mr...@gmail.com> #142
pu...@gmail.com <pu...@gmail.com> #143
st...@gmail.com <st...@gmail.com> #144
d....@gmail.com <d....@gmail.com> #145
Experiencing the same issue - Pixel 4 XL running Android 11.
-
Face Unlock stops working, with "Clean the top of your screen" message; both for unlock and biometric auth in apps. A reboot fixes this - Sometimes for a few hours, at most for a few days.
-
Proximity Sensor flakey, sometimes when in a call, taking the phone away from my face leaves the screen in a close-proximity "off" state, and will not show any controls. Holding the power button until a forced restart is the only way to regain control of the device.
Had no issues with any of the sensors up until Android 11 updates.
Build: RP1A.200720.009
, Android Security Update: 5 September 2020
, Google Play system update: 1 September 2020
.
ni...@gmail.com <ni...@gmail.com> #146
bi...@gmail.com <bi...@gmail.com> #147
ap...@gmail.com <ap...@gmail.com> #148
kv...@gmail.com <kv...@gmail.com> #149
it...@gmail.com <it...@gmail.com> #150
wk...@gmail.com <wk...@gmail.com> #151
ji...@gmail.com <ji...@gmail.com> #152
na...@gmail.com <na...@gmail.com> #153
gh...@gmail.com <gh...@gmail.com> #154
an...@gmail.com <an...@gmail.com> #155
an...@gmail.com <an...@gmail.com> #156
bb...@gmail.com <bb...@gmail.com> #157
And the screen doesn't turn on after call too.
ma...@gmail.com <ma...@gmail.com> #158
he...@gmail.com <he...@gmail.com> #159
It still happens after the Android 11 upgrade.
Multiple factory reset, no change.
A reboot fixes it for a few hours then the problem returns.
Face unlock thinks the screen is dirty. The phone thinks my face it against it and it's not, preventing me from using the phone until the other party hangs up.
Extremely maddening!!!
vi...@gmail.com <vi...@gmail.com> #160
da...@gmail.com <da...@gmail.com> #161
ap...@gmail.com <ap...@gmail.com> #162
br...@gmail.com <br...@gmail.com> #163
th...@gmail.com <th...@gmail.com> #164
- Face unlock not working properly or only working half of the time
- Face unlock showing "Clean the top of your screen, including the black bar"
- Proximity sensor and soli detection messed up
- Nearby to wake screen up, double tap to wake, lift to wake not working
- When you take your phone out of your pocket, phone doesn't wake up. You need to press the power button to wake screen up, but face unlock won't work. The padlock on the top of your screen just dances as it can't recognize your face. You have to either input your password or pattern, whatever you have as your back up option
-When you are on a call and remove the phone from your ear/cheek, phone won't turn on until the other party ends the call. Basically you can't do anything while on call. Screen goes completely black. If you don't have power button to end call enabled, you are doomed.
- Once you delete face data, you can't setup face unlock or having difficulties with error in detecting your face.
As previous users have mentioned the reboot does solve things for a bit, but otherwise
vo...@gmail.com <vo...@gmail.com> #165
jj...@gmail.com <jj...@gmail.com> #166
th...@gmail.com <th...@gmail.com> #167
me...@gmail.com <me...@gmail.com> #168
pr...@gmail.com <pr...@gmail.com> #169
ph...@gmail.com <ph...@gmail.com> #170
do...@gmail.com <do...@gmail.com> #171
An observation I don't think I've seen yet: Sometimes (perhaps 5% of the time), the problem fixes itself! I reboot, then face unlock works for a time (between an hour and a day), and then fails. But then a short time later it starts working again of its own accord! Most of the time when it fails it seems to stay failed, though (though I do reboot the phone eventually).
I can't discern any pattern to triggering the face unlock fail. As a former programmer this problem feels like a race condition, but it's curious to me that I never had this problem with this phone when it was running Android 10.
It's a real pain having the sole biometric unlocking mechanism on your phone fail and require a reboot on a daily basis.
ol...@gmail.com <ol...@gmail.com> #172
wi...@gmail.com <wi...@gmail.com> #173
te...@gmail.com <te...@gmail.com> #174
pe...@gmail.com <pe...@gmail.com> #175
mi...@gmail.com <mi...@gmail.com> #176
'When you are on a call and remove the phone from your ear/cheek, phone won't turn on until the other party ends the call. Basically you can't do anything while on call. Screen goes completely black. If you don't have power button to end call enabled, you are doomed.'
wa...@gmail.com <wa...@gmail.com> #177
co...@gmail.com <co...@gmail.com> #178
sa...@gmail.com <sa...@gmail.com> #179
Oppoa52 colitis 11 update
af...@gmail.com <af...@gmail.com> #180
cb...@gmail.com <cb...@gmail.com> #181
ju...@gmail.com <ju...@gmail.com> #182
ch...@gmail.com <ch...@gmail.com> #183
be...@gmail.com <be...@gmail.com> #184
After updating face unlock works for a while after restart but then just stops.
ja...@gmail.com <ja...@gmail.com> #185
Face Unlock stops working, with "Clean the top of your screen" message; both for unlock and biometric auth in apps. A reboot fixes this - Sometimes for a few hours, at most for a few days.
Phone screen will also remain COMPLETELY black during a phone call, and cannot get the screen to respond in any way. I cannot use the dial pad during a phone call to enter any entries as the screen stays black. Honestly wish there was a "turn screen off while proximity sensor is blocked" option that I could have control over. This is an issue with the proximity sensor/face unlock feature and it is very frustrating. I had to enable "power button ends call" to at least have some control over answering a phone call - otherwise the screen would remain black and none of the buttons wake the screen.
I believe this to be a software issue - when the phone is acting up, not even the 'touch to wake display" works. If I restart my phone, both the face unlock feature and 'tap to wake display' works again. Guess I just have to restart my phone multiple times a day until they resolve this issue.
sa...@gmail.com <sa...@gmail.com> #186
Face Unlock stops working, with "Clean the top of your screen" message; both for unlock and biometric auth in apps. A reboot fixes this - Sometimes for a few hours, at most for a few days.
jc...@gmail.com <jc...@gmail.com> #187
For everyone new to this thread, let me repeat something I said from earlier this summer that still holds true:
I have found that if I use my shirt, or a nearby smooth cloth, and rub it back and forth over the front camera lens/proximity sensor area (top left) for about 2-3 seconds, it temporarily fixes the issue without having to reboot. However, this procedure often must be repeated several times a day.
fu...@gmail.com <fu...@gmail.com> #188
Same issue here
an...@gmail.com <an...@gmail.com> #189
cs...@gmail.com <cs...@gmail.com> #190
va...@gmail.com <va...@gmail.com> #191
do...@gmail.com <do...@gmail.com> #192
mj...@gmail.com <mj...@gmail.com> #193
jo...@gmail.com <jo...@gmail.com> #194
ng...@gmail.com <ng...@gmail.com> #195
ng...@gmail.com <ng...@gmail.com> #196
ng...@gmail.com <ng...@gmail.com> #197
bl...@gmail.com <bl...@gmail.com> #198
mj...@gmail.com <mj...@gmail.com> #199
wi...@gmail.com <wi...@gmail.com> #200
an...@gmail.com <an...@gmail.com> #201
an...@gmail.com <an...@gmail.com> #202
ji...@gmail.com <ji...@gmail.com> #203
sg...@gmail.com <sg...@gmail.com> #204
It happens sometimes during a phone call, I go to end the call but screen does not turn back on and have to force a reboot. Other times it will just not detect proximity and I need to use pin to unlock. A reboot usually helps as well as random amount of time waiting and seems to work again if I give up trying.
rs...@gmail.com <rs...@gmail.com> #205
zh...@gmail.com <zh...@gmail.com> #206
ss...@gmail.com <ss...@gmail.com> #207
Instead of hard reboot; double tap the power button to pull up the camera-- you should be then able to access the rest of the phone.
No workaround for face unlock issues.
rd...@gmail.com <rd...@gmail.com> #208
mi...@gmail.com <mi...@gmail.com> #209
Pixel 4XL Android 11 Build RP1A.200720.009
am...@gmail.com <am...@gmail.com> #210
I am also getting the "clean your screen" messages and my phone is absolutely clean. I am using the google case but this happens when I take the case completely off too.
jd...@gmail.com <jd...@gmail.com> #211
no...@gmail.com <no...@gmail.com> #212
ja...@gmail.com <ja...@gmail.com> #213
I bought this Pixel 4 XL when my 2 XL's camera suddenly stopped working after a software update. Really not sure what to trust anymore.
po...@gmail.com <po...@gmail.com> #214
As others have pointed out, when the issue is present, if I make a call the screen goes black immediately, and nothing will wake the phone from this state unless the call is ended by the other party, or I hold down power to shut down the phone. It is currently impossible to call any number/automated system which requires keypad input when the screen is black and nothing wakes it up.
I write embedded linux firmware/software for a living. This is almost certainly a software issue in my opinion. Most notably because it happened the instant I updated, and is temporarily resolved by rebooting. I am willing to help/send diagnostics if asked by google or anyone working on a fix.
ho...@gmail.com <ho...@gmail.com> #215
mo...@gmail.com <mo...@gmail.com> #216
si...@gmail.com <si...@gmail.com> #217
s3...@gmail.com <s3...@gmail.com> #218
ia...@gmail.com <ia...@gmail.com> #219
When will Google fix this, or are they not going to bother but that Soli and Face Unlock are basically dead in the water after Pixel 5 announcement?
sa...@gmail.com <sa...@gmail.com> #220
pi...@gmail.com <pi...@gmail.com> #221
ja...@gmail.com <ja...@gmail.com> #222
A couple weeks ago (just over the 6 month mark of having the phone) I had a battery issue - I'll spare the details but my phone would only work when plugged in and crashed/did not function properly even then. (I tried a factory reset and made sure to update, didn't help.) Took it in for a warranty replacement, they said it would be done the next day. I called that day and they said the part was on backorder, they had 5 Pixels waiting for one and it would "hopefully be in by the end of the week." I'm a contractor and rely on my phone for work and with some insistence they checked a nearby store and had it shipped over (sorry to everyone else waiting...)
One day after getting my phone back from them I started having the issues with the proximity sensor, exactly as described here. Face unlock won't work, have to drag my screen all the way to the top to be able to unlock, and I can't do anything while on the phone. I have a proximity sensor app that Google recommended I try and that's clearly the issue. 20% of the time cleaning it works for a short time, then it goes back to the same issue. It typically works after a restart, but only for 30 minutes or so.
I loved my Nexus, had issues with my Pixel at 6 months twice (got it replaced at 6 months, refurbished version had the same
pu...@gmail.com <pu...@gmail.com> #223
No screen protector.
Not dirty
Massive disruptiveness.
Google support only wants me to send in my phone and be without it for 5 to 15 days. Insanity. For the first time since nexus, I'm actually considering an iPhone, I'm so disgusted with Google support and tech and their unwillingness to accommodate me with an advanced return.
je...@gmail.com <je...@gmail.com> #224
3a works fine on A11. Hmm, wonder why the 5 doesn't have a prox sensor.
je...@gmail.com <je...@gmail.com> #225
k7...@gmail.com <k7...@gmail.com> #226
This issue in particular started the day I did the Android 11 update and has been happening every single day since, most of the time 2-3x a day. Every time it happens, I do a hard reset on the phone and it fixes it for a few hours and then were back to the same thing.
Super frustrating because when it happens, I cant quick swipe my pattern up. I have to drag the pattern up from the bottom. I use this phone for work and this is constantly slowing me down from performing my job. Google get your act together and fix this or send us all phones that wont have this issue.
Sincerely,
Long time pixel user who will probably never buy another one.
fe...@gmail.com <fe...@gmail.com> #227
The major problem about the "unlock" bug, is that when it happens a lot of other problems shows up, like the super annoing black screen while on call many other people are claiming. If the called person doesn't respond and he have voice mail, you must brutally turn off the phone because you can't stop the call at all!
I have no idea what is happening when the screen it's black, what if I'm sending messages, calling people, deleting stuff without my knowledge? How can i even trust the phone to be properly locked?
Happened that some people called me and i didn't even got any notification, they told me that they could hear people yelling or some really noisy sound. The truth is that I didn't answer the call, because i had no vibration/notification at all, yet for some reason the phone answered the call by itself.
That's embarssing. We're unable to use our (expensive) phones even for super common activities like CALLING.
A bug like this should be a priority. And even a proper response by Google.
Seriously considering about changing my phone because of this situation.
pb...@gmail.com <pb...@gmail.com> #228
js...@gmail.com <js...@gmail.com> #229
th...@gmail.com <th...@gmail.com> #230
ss...@gmail.com <ss...@gmail.com> #231
Fixed my pixel 4 XL. Proxy sensor and face unlock works. Hopefully it stays that way.
cw...@gmail.com <cw...@gmail.com> #232
st...@gmail.com <st...@gmail.com> #233
ni...@gmail.com <ni...@gmail.com> #234
ja...@gmail.com <ja...@gmail.com> #235
I feel like throwing away my Pixel 4xl, this shows Google didn't even properly tested before releasing new updates. I think this would give me sufficient reason to switch to IPhone. I have Iphone 6 and it still runs super smoothly with no issues.
me...@gmail.com <me...@gmail.com> #236
ne...@gmail.com <ne...@gmail.com> #237
st...@gmail.com <st...@gmail.com> #238
he...@gmail.com <he...@gmail.com> #239
I was told I would be contacted by a specialist on this matter. I never was. The last techs recommendation? Reboot my phone............
I have been a Google hardware fan since the early nexus line. I have had every new generation of Google phone. I have a wife and 3 kids. We all use pixel devices. No more.
This is our last one. It is absolute hot garbage.
ne...@gmail.com <ne...@gmail.com> #240
th...@gmail.com <th...@gmail.com> #241
de...@gmail.com <de...@gmail.com> #242
ti...@gmail.com <ti...@gmail.com> #243
do...@gmail.com <do...@gmail.com> #244
an...@gmail.com <an...@gmail.com> #245
mo...@gmail.com <mo...@gmail.com> #246
re...@gmail.com <re...@gmail.com> #247
ja...@gmail.com <ja...@gmail.com> #248
No choice but to disable all sensors for now via Developer Options. I went to
lv...@gmail.com <lv...@gmail.com> #249
Super ANNOYING
cw...@gmail.com <cw...@gmail.com> #250
workaround the issue.
Disabling phone sensors only introduces other quality of life issues with
your phone.
On Wed, Oct 7, 2020, 3:52 PM <buganizer-system@google.com> wrote:
su...@gmail.com <su...@gmail.com> #251
su...@gmail.com <su...@gmail.com> #252
su...@gmail.com <su...@gmail.com> #253
So I turned the screen off by clicking the power button, and I clicked it again. TO MY SURPRISE, THE PHONE DID NOT LOCK. SO I TRIED THIS AGAIN, locked the phone using the power button, and clicked it again to turn the screen on. AGAIN, THE PHONE REFUSES TO LOCK SECURE USING FACE UNLOCK/ PIN/ PASSCODE. I CAN CONFIRM BY SAYING THAT THERE IS NO SETTING I CHANGED IN THE "SETTINGS'' OF THE PHONE THAT WOULD CAUSE A DELAY IN LOCKING TIME. FINALLY, OUT OF HOPE, I TRIED TO EXIT OUT OF THE APP, BECAUSE THE PHONE WOULDN'T LOCK! THEN I RECEIVED A MESSAGE SAYING "SYSTEM UI HAS STOPPED WORKING". WHAT IN THE ACTUAL HELL? IF SYSTEM UI STOPS WORKING, DOES THAT MEAN MY PHONE IS LEFT UNLOCKED AND CAN'T BE LOCKED AGAIN? THIS MAKES ME FEEL THAT GOOGLE PHONE'S ARENT SECURE ANYMORE! ALL THAT STUPID TITAN M SECURITY CHIP THAT YOU GUYS FLAUNTED ON AND ABOUT IS USELESS! NOW BEFORE YOU SAY THAT MY POWER BUTTON IS BROKEN, IT IS NOT. THIS IS A SECURITY FLAW. IMAGINE IF SOMEONE WAS WATCHING P*** AND SUDDENLY THEIR PARENTS WALK-IN AND THE PHONE FREEZES, AND DOES NOT SECURELY LOCK! GOOGLE, GET YOUR SHIT TOGETHER! THIS PHONE IS NOT SECURE!
le...@smart2b.nl <le...@smart2b.nl> #254
Face unlock works about 0,5% of the time.
Mostly only works in the firth 5 minutes after a shutdown and wait for some minutes and then booting.
When calling the screens stays black untill call is ended by the other side.
Plz fix phone is only 2 months old.
fe...@gmail.com <fe...@gmail.com> #255
I also tried to disable Face Unlock, and nothing changes. Sometimes i still need to drag all the way up to insert the PIN, and if someone calls me the screen turns black. I noticed the same with vocal messages, i had to brutally turn it off after listening to it, because screen frozen on black.
The "fun" part is that if (for example) you press 2 times fast your "lock" button, you can notice the vibration of the camera function starting. This means that your phone it's actually working without any problem, but you can't see anything. So it's just an almost 1000€ phone with a black screen that you have to restart several times a day.
Google, post an official statement over this. It's simply pathetic. I won't continue using a phone like this for too long, and I'm pretty sure many people would change brand and OS rather than using a bugged phone. Just read how many people are thinking of switching on iPhone on the comments above.
And it's obviously a software problem, since before Android 11 update this wasn't a problem for anyone of us.
mn...@prologix.ca <mn...@prologix.ca> #256
- Soli will not active
- Face Unlock will not work
- Power button will unlock
- Must swipe full length of screen
- AOD is extremely bright
A restart fixes the issues temporarily, but they always come back.
so...@gmail.com <so...@gmail.com> #257
I'm having same problem since A11
ja...@gmail.com <ja...@gmail.com> #258
sa...@gmail.com <sa...@gmail.com> #259
n3...@googlemail.com <n3...@googlemail.com> #260
es...@gmail.com <es...@gmail.com> #261
nh...@gmail.com <nh...@gmail.com> #262
bi...@gmail.com <bi...@gmail.com> #263
ah...@gmail.com <ah...@gmail.com> #264
ca...@gmail.com <ca...@gmail.com> #265
ra...@gmail.com <ra...@gmail.com> #266
wi...@gmail.com <wi...@gmail.com> #267
ts...@gmail.com <ts...@gmail.com> #268
Found out when I accidentally called the wrong person and couldn't hang up because phone screen went black. Had to leave a voicemail. A very long voicemail.
gu...@ghielectronics.com <gu...@ghielectronics.com> #269
"Im also experiencing the same issues for over 2 months. When the face unlock does not work it also messes the screen up. Everytime i slide the screen up to get to the keypad, the keypad closes unless i slide all the way to the top of the screen. Also same issues with proximity sensor.
Its been 2 months!!!"
cw...@gmail.com <cw...@gmail.com> #270
Workaround: Restart your phone, :(
When the problem kicks in, instead of swiping from bottom to top, simply
tap the 'Lock' icon at the top of the screen.
On Mon, Oct 12, 2020 at 1:41 PM <buganizer-system@google.com> wrote:
an...@gmail.com <an...@gmail.com> #271
no...@gmail.com <no...@gmail.com> #272
vo...@gmail.com <vo...@gmail.com> #273
Double tap the power button, this will bring up the camera. The gallery
button in the bottom right will have a lock icon over it. Tapping that
will prompt you to enter your usual login credentials.
Not ideal but will not require a restart.
On Tue, Oct 13, 2020, 10:43 AM <buganizer-system@google.com> wrote:
lu...@gmail.com <lu...@gmail.com> #274
cr...@gmail.com <cr...@gmail.com> #275
aj...@gmail.com <aj...@gmail.com> #276
cr...@gmail.com <cr...@gmail.com> #277
ro...@gmail.com <ro...@gmail.com> #278
an...@gmail.com <an...@gmail.com> #279
ti...@gmail.com <ti...@gmail.com> #280
st...@gmail.com <st...@gmail.com> #281
wa...@gmail.com <wa...@gmail.com> #282
da...@gmail.com <da...@gmail.com> #283
jc...@gmail.com <jc...@gmail.com> #284
Wait, the Pixel 5 brought back the fingerprint sensor? I actually liked the fingerprint sensor on my Pixel 2 better than face unlock anyway. I may just pay off Pixel 4 and get the Pixel 5 in that case.
md...@gmail.com <md...@gmail.com> #285
ee...@gmail.com <ee...@gmail.com> #286
Hopefully will help you as well.
On Thu, Oct 15, 2020, 10:23 AM <buganizer-system@google.com> wrote:
au...@gmail.com <au...@gmail.com> #287
am...@lendi.com.au <am...@lendi.com.au> #288
am...@lendi.com.au <am...@lendi.com.au> #289
sh...@gmail.com <sh...@gmail.com> #290
al...@gmail.com <al...@gmail.com> #291
ro...@gmail.com <ro...@gmail.com> #292
ma...@gmail.com <ma...@gmail.com> #293
e8...@gmail.com <e8...@gmail.com> #294
e8...@gmail.com <e8...@gmail.com> #295
Android version: 11.0.0 (RP1A.201005.004, Oct 2020)
ni...@gmail.com <ni...@gmail.com> #296
fa...@gmail.com <fa...@gmail.com> #297
it started before updating to 11
vz...@gmail.com <vz...@gmail.com> #298
My older post:
Dear All, the same issue here, pixel 4 xl, after Android 11 update. The worst situation I had so far, resulting from this, is during the call - the screen gets black and it is impossible to hang up or revive the screen in any other way.
su...@gmail.com <su...@gmail.com> #299
Please fix this, Google.
al...@gmail.com <al...@gmail.com> #300
sa...@popularchips.com <sa...@popularchips.com> #301
It's been over 2 months that I can't do calls as it goes all black.
After reading that the update to Android 11 doesn't fix the problem but has created the same issue to many others, I guess that we'll have to wait and see if Google will enventually take us seriously and do something about it!
Also, tried all the suggestions from Google and it still doesn't work!!
ia...@gmail.com <ia...@gmail.com> #302
gr...@gmail.com <gr...@gmail.com> #303
bu...@gmail.com <bu...@gmail.com> #304
za...@gmail.com <za...@gmail.com> #306
ba...@gmail.com <ba...@gmail.com> #307
When this happens it also makes swiping to unlock difficult. I have to basically swipe from the bottom of the screen to almost the very top to get to my unlock pattern. So strange.
ni...@gmail.com <ni...@gmail.com> #308
di...@gmail.com <di...@gmail.com> #309
do...@gmail.com <do...@gmail.com> #310
Software critical bug that they need to fix asap.
be...@gmail.com <be...@gmail.com> #311
Google, FIX THIS!
so...@gmail.com <so...@gmail.com> #312
ti...@gmail.com <ti...@gmail.com> #313
The fact that for many people the trouble started with Android 11 kind of suggests the story is a bit more complicated than hardware alone. Some sort of interaction of hardware and software.
My previous phone was pixel XL, and suffered from the infamous mic issue. Google support was horrible at the time, worse than non existent. If this doesn't get fixed soon, this is sure to be my last Google phone. Life is too short for this.
bb...@gmail.com <bb...@gmail.com> #314
All I know, actively doing are a couple factory resets, right after I first noticed the problems which always fixed for a couple hours back than. Than IIRC, I disabled Face unlock by just unchecking the 3 "use face unlock for" sliders and just left it like this waiting for a miracle to happen or something like this... This than left me just with the problem, that the screen does not turn on again after a call.
Than after about 2 weeks (on Oct 4th to be exact) or so, I noticed that the screen would turn on back again after a call. I than turned the 3 slides for face unlock back on again, but also checked "require eyes to be open" (I think it was not checked before). And it works flawlessly ever since and I'm not sure what made it work again.
[Deleted User] <[Deleted User]> #315
de...@gmail.com <de...@gmail.com> #316
Trying to unlock my phone with a finger swipe is ridiculous, quickly doing it just fails and I have to slowly move my finger from the bottom of the screen to the top of the screen for a chance to get it to work.
As soon as I start making a phone call the screen goes to black and I can't hang up the phone.
And I don't know if others are experiencing this, but the bottom of my screen can also be unresponsive on apps.
Might have to revert back to Android 10, because this only started when I upgraded to Android 11.
ni...@gmail.com <ni...@gmail.com> #317
Pixel 5 is out, so probably it's not the priority at all to take care of pixe 4 problems.
gr...@gmail.com <gr...@gmail.com> #318
I have smart unlock to keep it unlocked at home so sometimes I don't realise until I have to tap to wake (and it doesn't wake) or I get an audio message on Whatsapp. As soon as I hit play, the screen goes black and I can't do anything with the phone until the audio finishes.
Some times I have to reboot several times a day for the face unlock and tap to wake to work again.
mk...@googlemail.com <mk...@googlemail.com> #319
bo...@gmail.com <bo...@gmail.com> #320
st...@gmail.com <st...@gmail.com> #321
fe...@gmail.com <fe...@gmail.com> #322
I am switching to iPhone this year because of this issue and the pixel 5 being a disappointment
da...@gmail.com <da...@gmail.com> #323
My girlfriend has a Pixel 4 XL too and was not in the beta, she used Android 11 right away with the final version of Android 11 - same problems.
gu...@gmail.com <gu...@gmail.com> #324
Google Pixel 4 with latest updates.
pa...@gmail.com <pa...@gmail.com> #325
rt...@gmail.com <rt...@gmail.com> #326
ro...@gmail.com <ro...@gmail.com> #327
jm...@gmail.com <jm...@gmail.com> #328
cs...@gmail.com <cs...@gmail.com> #329
mr...@gmail.com <mr...@gmail.com> #330
co...@gmail.com <co...@gmail.com> #331
co...@gmail.com <co...@gmail.com> #332
al...@edu.akivaschool.com <al...@edu.akivaschool.com> #333
au...@gmail.com <au...@gmail.com> #334
mo...@gmail.com <mo...@gmail.com> #335
cm...@linode.com <cm...@linode.com> #336
no...@gmail.com <no...@gmail.com> #337
I keep watching this thread to see if the problem has been patched.
Has anyone had this problem solved by having Google send them a replacement phone?
no...@gmail.com <no...@gmail.com> #338
to...@googlemail.com <to...@googlemail.com> #339
Also I have also noticed my screen going black after calls too. Very frustrating.
je...@gmail.com <je...@gmail.com> #340
s....@gmail.com <s....@gmail.com> #341
aj...@gmail.com <aj...@gmail.com> #342
A loyal Pixel user seriously considering to not get Pixel as my next phone.
wi...@gmail.com <wi...@gmail.com> #343
ke...@gmail.com <ke...@gmail.com> #344
nm...@gmail.com <nm...@gmail.com> #345
ja...@gmail.com <ja...@gmail.com> #346
ro...@cyberjunky.nl <ro...@cyberjunky.nl> #347
ad...@google.com <ad...@google.com> #348
ja...@gmail.com <ja...@gmail.com> #349
wk...@gmail.com <wk...@gmail.com> #350
no...@gmail.com <no...@gmail.com> #351
an...@gmail.com <an...@gmail.com> #352
su...@gmail.com <su...@gmail.com> #353
Good Heavens, we can rejoice, for it is finally fixed.
ro...@gmail.com <ro...@gmail.com> #354
da...@gmail.com <da...@gmail.com> #355
li...@hotmail.com <li...@hotmail.com> #356
ny...@gmail.com <ny...@gmail.com> #357
ju...@gmail.com <ju...@gmail.com> #358
sh...@gmail.com <sh...@gmail.com> #359
jc...@gmail.com <jc...@gmail.com> #360
It's "fixed" in the sense that the code to fix it has been checked into Google's internal repository. That does not in any way mean that it has been released. All software projects are like this: fixed merely means there is a code commit containing the fix. No software company waits until release to mark a bug a fixed. Nobody does.
Most likely we will get the fix in the November security update, perhaps December if the November update has already been frozen (releases are often frozen several days in advance to allow time for final testing and building).
be...@gmail.com <be...@gmail.com> #361
rg...@gmail.com <rg...@gmail.com> #362
sm...@gmail.com <sm...@gmail.com> #363
fr...@googlemail.com <fr...@googlemail.com> #364
an...@gmail.com <an...@gmail.com> #365
pc...@gmail.com <pc...@gmail.com> #366
lu...@gmail.com <lu...@gmail.com> #367
cb...@gmail.com <cb...@gmail.com> #368
vi...@gmail.com <vi...@gmail.com> #369
a8...@gmail.com <a8...@gmail.com> #370
Daily Check In (2020/11/03).
This priority should be higher...
ca...@gmail.com <ca...@gmail.com> #371
da...@gmail.com <da...@gmail.com> #372
su...@gmail.com <su...@gmail.com> #373
Pixel 4 XL face unlock fails to work sometimes. It is weirdly inconsistent and fails to work many times throughout the day. I recorded my Pixel 4 XL when face unlock is working perfectly, and when it doesn't work. Pixel 4 XL face unlock doesn't work, so I used a camera to check. To my surprise, the face unlock flood illuminator lights do not light up, which I think causes this issue. In the first recorded video, the lights don't light up, so this is why the face unlock fails, and a message is displayed "clean the top of the screen including the black bar".
In the second video, I did a quick restart of my device. The face unlock flood illuminator works perfectly, and face unlock functionality is restored.
As you can see the face unlock lights don't light up sometimes which causes the face unlock to fail. This is my device info- Device- Pixel 4 XL Security Patch- November 5, 2020
Google released an update on November 5 saying "Fix for dark screen during phone calls" This does not fix the face unlock issue, and is in no way related to that. I wait in hopes that this will be fixed in the near future.
Another major annoyance is that, if I use face unlock and wear a mask, I cannot unlock my phone. So, I have to use my pin/passcode to unlock the device. When I do this, I have to swipe all the way toward the top of the screen to bring up the pin. A single swipe will not work.
wo...@gmail.com <wo...@gmail.com> #374
ni...@gmail.com <ni...@gmail.com> #375
jo...@gmail.com <jo...@gmail.com> #376
It's been ongoing for so long I doubt it will ever be resolved.
I cannot wait to get rid of this phone. It's my second and last Google pixel.
fo...@gmail.com <fo...@gmail.com> #377
do...@gmail.com <do...@gmail.com> #378
er...@gmail.com <er...@gmail.com> #379
Also during phone calls sometimes screen will go completely black and i cant wake up the phone untill the other person ends the call
mn...@prologix.ca <mn...@prologix.ca> #380
sc...@gmail.com <sc...@gmail.com> #381
su...@gmail.com <su...@gmail.com> #382
Google, can we get a reply from you and reopen this case? Thanks.
ge...@gmail.com <ge...@gmail.com> #383
This is definitely not fixed by the Nov update. This needs to be reopened. Not sure how or why google marked this as fixed without verification by the community reporting the issue.
Pixel 4XL (RP1A.201105.002)
a8...@gmail.com <a8...@gmail.com> #384
Still happening
da...@gmail.com <da...@gmail.com> #385
m....@gmail.com <m....@gmail.com> #386
lc...@gmail.com <lc...@gmail.com> #387
Also I have also noticed my screen going black after calls too. Very frustrating.
as...@googlemail.com <as...@googlemail.com> #388
Can't swip notifications without having to actively long swipe, phone goes black on calls then can't get back to hang up.
ma...@shaw.ca <ma...@shaw.ca> #389
vz...@gmail.com <vz...@gmail.com> #390
lu...@gmail.com <lu...@gmail.com> #391
lu...@gmail.com <lu...@gmail.com> #392
lu...@gmail.com <lu...@gmail.com> #393
cl...@gmail.com <cl...@gmail.com> #394
xr...@gmail.com <xr...@gmail.com> #395
al...@gmail.com <al...@gmail.com> #397
ad...@gmail.com <ad...@gmail.com> #398
jo...@gmail.com <jo...@gmail.com> #399
su...@gmail.com <su...@gmail.com> #400
At least it only rarely happens to me. Not every day.
cs...@gmail.com <cs...@gmail.com> #401
ra...@gmail.com <ra...@gmail.com> #402
gu...@gmail.com <gu...@gmail.com> #403
su...@gmail.com <su...@gmail.com> #404
ap...@gmail.com <ap...@gmail.com> #405
ta...@gmail.com <ta...@gmail.com> #406
je...@gmail.com <je...@gmail.com> #407
so...@gmail.com <so...@gmail.com> #408
first noticed it but perhaps a couple of months ago.
On Mon, 9 Nov 2020 at 13:05, <buganizer-system@google.com> wrote:
an...@rethinkmarketing.com.au <an...@rethinkmarketing.com.au> #409
fl...@gmail.com <fl...@gmail.com> #410
ep...@gmail.com <ep...@gmail.com> #411
il...@gmail.com <il...@gmail.com> #412
st...@gmail.com <st...@gmail.com> #413
mj...@gmail.com <mj...@gmail.com> #414
kh...@gmail.com <kh...@gmail.com> #415
jo...@gmail.com <jo...@gmail.com> #416
pa...@gmail.com <pa...@gmail.com> #417
ch...@gmail.com <ch...@gmail.com> #418
ke...@gmail.com <ke...@gmail.com> #419
vi...@gmail.com <vi...@gmail.com> #420
mo...@gmail.com <mo...@gmail.com> #421
ew...@gmail.com <ew...@gmail.com> #422
ad...@gmail.com <ad...@gmail.com> #423
he...@gmail.com <he...@gmail.com> #424
ad...@gmail.com <ad...@gmail.com> #425
sv...@googlemail.com <sv...@googlemail.com> #426
to...@gmail.com <to...@gmail.com> #427
vl...@gmail.com <vl...@gmail.com> #428
"Clean top bezel" message until I unlock with a pin and restart the phone.
ma...@gmail.com <ma...@gmail.com> #429
jo...@gmail.com <jo...@gmail.com> #430
lo...@gmail.com <lo...@gmail.com> #431
It has been escalated to a supervisor but I know nothing will happen with that.
Next option I have is accept a replacement new phone, sell it and buy a different device!
ca...@gmail.com <ca...@gmail.com> #432
am...@gmail.com <am...@gmail.com> #433
ry...@gmail.com <ry...@gmail.com> #434
cl...@gmail.com <cl...@gmail.com> #435
ja...@gmail.com <ja...@gmail.com> #436
ji...@gmail.com <ji...@gmail.com> #437
ia...@gmail.com <ia...@gmail.com> #438
Symptoms:
1) Swipe to unlock requires significantly more thumb travel
2) Swipe to clear notifications also requires substantially more movement to accomplish (need to start almost right at the bezel)
3) Swipe up to open App tray requires significantly more thumb travel
4) Smart Unlock stops working
5) Sometimes says to clean your screen for the sensor.
This is a must fix google.....
This has been too long without correction. I was a Samsung user for almost all of the Note series phones and now might have to go back....
a8...@gmail.com <a8...@gmail.com> #439
su...@gmail.com <su...@gmail.com> #440
This is not a hardware issue. The face unlock flood emitter stops working for a few seconds when this happens. You can visually confirm this by using the camera of another phone which can pickup the flood beams. This is a simple bug, that has to be fixed by google.
sh...@gmail.com <sh...@gmail.com> #441
co...@gmail.com <co...@gmail.com> #442
ni...@gmail.com <ni...@gmail.com> #443
le...@gmail.com <le...@gmail.com> #444
I have tried to call support to determine when the fix for this issue will
be pushed to the user community. They all seem to be unaware of the
problem currently impacting thousands of Pixel 4XL users. We need to know
if the fix will be made available directly to Pixel 4XL users, or will it
be part of a monthly update. If a monthly update, will it be in the
December update? Please let me know, and it would be greatly appreciated
if you would also post the information in the issue tracker forum,
155682995.
Regards,
Leon Claypool
On Fri, Nov 13, 2020 at 2:22 PM <buganizer-system@google.com> wrote:
su...@gmail.com <su...@gmail.com> #445
al...@gmail.com <al...@gmail.com> #446
cs...@gmail.com <cs...@gmail.com> #447
le...@gmail.com <le...@gmail.com> #448
ma...@gmail.com <ma...@gmail.com> #449
go...@gmail.com <go...@gmail.com> #450
is...@gmail.com <is...@gmail.com> #451
re...@gmail.com <re...@gmail.com> #452
si...@gmail.com <si...@gmail.com> #453
the screen goes black when making calls.
On Sun, Nov 15, 2020, 1:49 PM <buganizer-system@google.com> wrote:
jm...@gmail.com <jm...@gmail.com> #454
Same issues as initial post.
4XL
st...@gmail.com <st...@gmail.com> #455
st...@gmail.com <st...@gmail.com> #456
[Deleted User] <[Deleted User]> #457
ir...@gmail.com <ir...@gmail.com> #458
th...@gmail.com <th...@gmail.com> #459
If this is not fixed next month ill probably switch back to my s7 and sell this monstrosity of a phone
cl...@gmail.com <cl...@gmail.com> #460
jo...@gmail.com <jo...@gmail.com> #461
ma...@gmail.com <ma...@gmail.com> #462
a....@gmail.com <a....@gmail.com> #463
Pixel 4 XL purchased approx Dec 2019. Android 11, November 5 2020 update.
pi...@gmail.com <pi...@gmail.com> #465
su...@gmail.com <su...@gmail.com> #466
No one seems to care about this issue here. Please consider leaving a comment on this new issue tracker page:
ad...@gmail.com <ad...@gmail.com> #467
also seem to be implicated.
My screen starts flickering and seemingly trying to do multiple things at
once while on the lock screen, so it never accomplishes anything.
Restarting still seems to help me, fortunately, but this is a pretty
ridiculous problem for a core feature to consistently malfunction for so
many users on such common software and hardware.
On Sat., Nov. 14, 2020, 14:20 , <buganizer-system@google.com> wrote:
cu...@gmail.com <cu...@gmail.com> #468
only for a few seconds until I got home. This happens randomly !!! I could
just be scrolling and the screen just turns black. Almost always happens
with a call. I have had it do the flickering thing someone else mentioned.
On Fri, Nov 20, 2020, 5:05 PM <buganizer-system@google.com> wrote:
za...@gmail.com <za...@gmail.com> #469
ti...@gmail.com <ti...@gmail.com> #470
wo...@gmail.com <wo...@gmail.com> #471
ni...@gmail.com <ni...@gmail.com> #472
The phone also had the "battery stuck at 50%" issue many months ago.
The phone recently had to have the back glass replaced because the "wireless charging gap" issue surfaced.
Too many trips to uBreakiFix for this customer.
This phone will have to get deprecated to be an expensive webcam, and I move on to iPhone. :(
jo...@gmail.com <jo...@gmail.com> #473
ja...@gmail.com <ja...@gmail.com> #474
bo...@gmail.com <bo...@gmail.com> #475
ke...@gmail.com <ke...@gmail.com> #476
sc...@gmail.com <sc...@gmail.com> #477
Also happening to me!
ma...@gmail.com <ma...@gmail.com> #478
cn...@gmail.com <cn...@gmail.com> #479
sh...@gmail.com <sh...@gmail.com> #480
I recently replaced by phone and got a replacement new phone from Google.
Any solution?
ro...@gmail.com <ro...@gmail.com> #481
ta...@gmail.com <ta...@gmail.com> #482
to...@gmail.com <to...@gmail.com> #483
vj...@gmail.com <vj...@gmail.com> #484
masks, but now it doesn't work even when my face is showing :(
As others have said, is transiently resolved with a reboot but was
wondering whether this just a software fault or something hardware
related?? In which case, does it count as a manufacturing issue within my
one year warranty?
On Wed, 11 Nov 2020, 13:54 , <buganizer-system@google.com> wrote:
ig...@gmail.com <ig...@gmail.com> #485
he...@gmail.com <he...@gmail.com> #486
vi...@gmail.com <vi...@gmail.com> #487
tp...@gmail.com <tp...@gmail.com> #488
se...@gmail.com <se...@gmail.com> #489
ro...@googlemail.com <ro...@googlemail.com> #490
It's been 6 months since this has been reported, is there going to be a fix or I should return the device ?
ma...@gmail.com <ma...@gmail.com> #491
ni...@gmail.com <ni...@gmail.com> #492
I'm curious if this workaround fixes it for others. Hopefully Google can get this fixed permanently as this is a really poor experience.
br...@gmail.com <br...@gmail.com> #493
ra...@gmail.com <ra...@gmail.com> #494
al...@gmail.com <al...@gmail.com> #495
ca...@gmail.com <ca...@gmail.com> #496
lu...@gmail.com <lu...@gmail.com> #497
ma...@gmail.com <ma...@gmail.com> #498
rd...@gmail.com <rd...@gmail.com> #499
cl...@gmail.com <cl...@gmail.com> #500
vj...@gmail.com <vj...@gmail.com> #501
much bigger upwards swipe to get to the pattern unlock.
On Wed, 11 Nov 2020, 13:54 , <buganizer-system@google.com> wrote:
ns...@harrowschool.hk <ns...@harrowschool.hk> #502
Is there any way I can return the phone and get a replacement? I am in Hong Kong.
j....@gmail.com <j....@gmail.com> #503
Pixel 4xl running latest version of Android.
ae...@gmail.com <ae...@gmail.com> #504
gr...@gmail.com <gr...@gmail.com> #505
an...@gmail.com <an...@gmail.com> #506
mr...@gmail.com <mr...@gmail.com> #507
da...@gmail.com <da...@gmail.com> #508
ra...@gmail.com <ra...@gmail.com> #509
er...@gmail.com <er...@gmail.com> #510
cs...@gmail.com <cs...@gmail.com> #511
mi...@gmail.com <mi...@gmail.com> #512
Problem started since upgrade to android 11.
Even pattern security is sometimes stuck.
Avi Minsky
On Thu, 3 Dec 2020, 0:13 , <buganizer-system@google.com> wrote:
dp...@gmail.com <dp...@gmail.com> #513
ti...@gmail.com <ti...@gmail.com> #514
da...@googlemail.com <da...@googlemail.com> #515
The screen will get stuck, I'm unable to do a swipe up to bring the PIN entry screen and have to drag my finger from the very bottom of the screen, slowly to the very top of the screen and once I've unlocked the device, the UI seems to work fine. Have to reboot the phone to solve the issue. Issue definitely isn't fixed.
jo...@gmail.com <jo...@gmail.com> #516
za...@gmail.com <za...@gmail.com> #517
Lock screen will get stuck, and I will get a message saying "clean the top of your screen including the black bar" If I attempt to skip face unlock and enter my pin instead, I am unable to swipe up unless dragging from the very bottom of the screen to the top slowly. Rebooting the phone fixes it, however it happens over two times daily.
Definitely NOT a fixed issue.
te...@gmail.com <te...@gmail.com> #518
Effing BULLSH*T. I just got this phone replaced a few days ago because of the camera crapping out and now this again. $1200 phone, a long time Google phone user. I'm just one person and I know it doesn't mean anything to anyone, but I'm moving onto a different brand.
te...@gmail.com <te...@gmail.com> #519
ke...@gmail.com <ke...@gmail.com> #520
g6...@gmail.com <g6...@gmail.com> #521
Basically, the lock screen will get stuck, and I get a message saying to "Clean the top of your screen including the black bar". Sensor bar is clean. Motion sense does not work when this happens. If I attempt to skip face unlock and enter my pattern instead, I am unable to swipe up unless dragging up bottom of the screen to the top VERY slowly. Sometimes that doesn't work either and the only solution is to reboot the device.
Build no. RP1A.201105.002
ke...@gmail.com <ke...@gmail.com> #522
ah...@gmail.com <ah...@gmail.com> #523
Started happening about a week or so ago. was happening randomly where I get the message to clean the top of the phone even when the screen is clean.
Since yesterday, face unlock is not working at all and I have to swipe slowly from the bottom all the way to the top to get to the pattern and unlock the phone
bs...@gmail.com <bs...@gmail.com> #524
ja...@gmail.com <ja...@gmail.com> #525
jo...@gmail.com <jo...@gmail.com> #526
ae...@gmail.com <ae...@gmail.com> #527
Like others have said, my phone has been like this for months and it's quickly becoming the worst phone I've ever owned.
su...@kalbargas.com <su...@kalbargas.com> #528
jo...@gmail.com <jo...@gmail.com> #529
Pixel 2 XL camera stopped working after updating to Android 11. Now the
Pixel 4XL has this AND camera issues. F these phones and Google for not
standing behind them.
On Sun, Dec 6, 2020 at 2:42 PM <buganizer-system@google.com> wrote:
al...@gmail.com <al...@gmail.com> #530
al...@gmail.com <al...@gmail.com> #531
su...@gmail.com <su...@gmail.com> #532
I think this issue has been fixed in the December update. I've used the phone for a few hours now and I'm not seeing any signs of the issue anymore. I will check back and report later. As of now, it works perfectly and face unlock feels faster now.
jo...@gmail.com <jo...@gmail.com> #533
Super dissatisfied.
On Mon, Dec 7, 2020, 10:49 PM <buganizer-system@google.com> wrote:
hs...@roblox.com <hs...@roblox.com> #534
Before the fix, neither the face unlock nor screen during phone call worked for me.
mi...@gmail.com <mi...@gmail.com> #535
Avi Minsky
On Tue, 8 Dec 2020, 11:47 , <buganizer-system@google.com> wrote:
mi...@gmail.com <mi...@gmail.com> #536
also pattern is recognized. I have to restart everytime that happens
Avi Minsky
On Tue, 8 Dec 2020, 12:11 avi minsky, <minsky.a@gmail.com> wrote:
sa...@gmail.com <sa...@gmail.com> #537
su...@gmail.com <su...@gmail.com> #538
Mine is working fine after December patch. Will give long term feedback later.
xr...@gmail.com <xr...@gmail.com> #539
vj...@gmail.com <vj...@gmail.com> #540
Been several days now.
I needed to manually check for the update, as somehow it wasn't pushed
automatically. Might be why some are still stuck with this issue.
On Thu, 10 Dec 2020, 23:39 , <buganizer-system@google.com> wrote:
vj...@gmail.com <vj...@gmail.com> #541
it's a phone breaking bug that they have just fixed, and need to push out.
I don't know how many hardware returns they've had in terms of this
software issue. Especially as this was the last flagship.
On Fri, 11 Dec 2020, 08:52 Vaibhav Joshi, <vjjoshi911@gmail.com> wrote:
vj...@gmail.com <vj...@gmail.com> #542
:(
On Fri, 11 Dec 2020, 08:57 Vaibhav Joshi, <vjjoshi911@gmail.com> wrote:
ch...@googlemail.com <ch...@googlemail.com> #543
My experience with the Dec. update was very good.
My phone works since the update without the issue.
Also have the impression that in some areas the performance was improved. My user experience fast and smooth. Since a couple of weeks with issues, the last days I was happy with my pixel 4.
cl...@gmail.com <cl...@gmail.com> #544
ti...@gmail.com <ti...@gmail.com> #545
su...@gmail.com <su...@gmail.com> #546
So far so good. I have no issues whatsoever. They also fixed the issue where you have to swipe all the way for face unlock to work.
su...@gmail.com <su...@gmail.com> #547
But what they did not fix is that you still have to swipe all the way to the top of the phone if your face unlock setting is set to only unlock the device, not go into the home screen.
it...@gmail.com <it...@gmail.com> #548
jo...@gmail.com <jo...@gmail.com> #549
ro...@gmail.com <ro...@gmail.com> #550
st...@gmail.com <st...@gmail.com> #551
I did all the updates then factory reset to make sure but in initial phone setup or later in settings it keeps refusing me to activate face unlock.
I didn't had those issues with my first (new) one over its whole life from Nov. 2019 to Nov. 2020...
vj...@gmail.com <vj...@gmail.com> #552
needing a reboot. Not ideal but I can accept this.
On Mon, 21 Dec 2020, 12:29 , <buganizer-system@google.com> wrote:
fa...@gmail.com <fa...@gmail.com> #553
je...@gmail.com <je...@gmail.com> #554
ja...@googlemail.com <ja...@googlemail.com> #555
tj...@gmail.com <tj...@gmail.com> #556
jo...@gmail.com <jo...@gmail.com> #557
ha...@gmail.com <ha...@gmail.com> #558
ha...@gmail.com <ha...@gmail.com> #559
ro...@gmail.com <ro...@gmail.com> #560
ja...@gmail.com <ja...@gmail.com> #561
ro...@gmail.com <ro...@gmail.com> #562
to...@gmail.com <to...@gmail.com> #563
ch...@googlemail.com <ch...@googlemail.com> #564
It's a software bug. Before Android 11 everything works fine.
Hope the issue will be fixed with the next update.
m4...@gmail.com <m4...@gmail.com> #565
I don't see any contribution from Google to this thread for months. What's up doc?
el...@gmail.com <el...@gmail.com> #566
br...@gmail.com <br...@gmail.com> #567
This seemed to start around the beginning of December and thought it was an update that might have been pushed. Recently reset my phone and didn't apply any updates (Running October Play system update with Jan Security update). Still not working with same error.
Any progress on this? Is this a warrany issue?
br...@gmail.com <br...@gmail.com> #568
gi...@gmail.com <gi...@gmail.com> #569
[Deleted User] <[Deleted User]> #570
ch...@gmail.com <ch...@gmail.com> #571
ch...@gmail.com <ch...@gmail.com> #572
mi...@gmail.com <mi...@gmail.com> #573
wt...@gmail.com <wt...@gmail.com> #574
ac...@gmail.com <ac...@gmail.com> #575
si...@gmail.com <si...@gmail.com> #576
sh...@gmail.com <sh...@gmail.com> #577
br...@gmail.com <br...@gmail.com> #578
er...@gmail.com <er...@gmail.com> #579
st...@gmail.com <st...@gmail.com> #580
jc...@gmail.com <jc...@gmail.com> #581
Sadly, I doubt this will ever be truly fixed. Rather, they "fixed" it by releasing the Pixel 5 last fall with a fingerprint reader instead of the face unlock. The official workaround seems to be "upgrade to the Pixel 5".
Frankly, I prefer fingerprint over face unlock, as it's more mask-friendly in these pandemic times and it's more widely supported as a biometric authentication for apps (some of the apps I use accept only fingerprints, not face unlock), so I was happy to get the fingerprint reader back, but it's sad to see Google just abandon a major issue like this. It does give me a bit of pause about buying future Pixel phones.
ke...@horizonlorain.org <ke...@horizonlorain.org> #582
si...@gmail.com <si...@gmail.com> #583
st...@gmail.com <st...@gmail.com> #584
vk...@gmail.com <vk...@gmail.com> #585
vk...@gmail.com <vk...@gmail.com> #586
og...@gmail.com <og...@gmail.com> #587
ch...@gmail.com <ch...@gmail.com> #588
ru...@gmail.com <ru...@gmail.com> #589
ba...@gmail.com <ba...@gmail.com> #590
Pixel 4 XL
ar...@gmail.com <ar...@gmail.com> #591
This issue is marked as "fixed" but I am currently experiencing it on Android 12 build SP1A.210812.015
. So far steps to reproduce are wait for it to break. Restarting resolves the issue temporarily. While face unlock is broken, and as others have noted, tap to wake does not work and an exaggerated swipe up to unlock gesture is necessitated.
co...@gmail.com <co...@gmail.com> #592
Behaves exact same as
This issue is NOT fixed.
ro...@gmail.com <ro...@gmail.com> #593
bo...@gmail.com <bo...@gmail.com> #594
ma...@gmail.com <ma...@gmail.com> #595
mk...@googlemail.com <mk...@googlemail.com> #596
mj...@gmail.com <mj...@gmail.com> #597
updating to Android 12. A reboot fixed the first two issues when the lock
screen didn't respond to touches and the pin entry area could not be moved
up into position for use. Now, after a fresh reboot the phone is
exhibiting the exact same condition, lock screen won't respond to touches
and pin entry area can't be moved up into position so no way to unlock
phone. I found a workaround for now, I added the GPay app icon in the
bottom right corner of the lock screen, when I select that and the CC
payment screen opens there is a selection to unlock to pay, this allows the
pin entry pad to open and unlock the phone. The phone basically goes back
to the frozen lock screen after this however so this technique continually
needs to be used to access the phone. Very frustrating, it seemed like
this was fixed on Android 11 but it's back to being completely broken again
on 12....come on Google......
On Wed, Oct 27, 2021 at 7:28 AM <buganizer-system@google.com> wrote:
bv...@gmail.com <bv...@gmail.com> #598
an...@gmail.com <an...@gmail.com> #599
Sincerely hoping that the release of new Pixel phones doesn't cause the team to consider this problem to be unimportant and it will be fixed ASAP (especially since it has already been fixed before, so they must know the root cause of it).
bv...@gmail.com <bv...@gmail.com> #600
Hope this lasts.. no problem today so far.
de...@gmail.com <de...@gmail.com> #601
And then today it stopped working. I am sad. This also means I have no biometrics for various apps in the ballpark of Paypal or any password autofill. In attempts to restore it, I have wound up without a face model and without the ability to create a new one, as shown in the attached screenshot.
Regression testing, my friends... "third party apps" is a lame excuse, by the way. Especially when this is even still broken in Safe Mode. The IR camera is simply not functioning. Oh, and Fast Mode didn't work either. Screenshots attached.
ja...@gmail.com <ja...@gmail.com> #602
pr...@gmail.com <pr...@gmail.com> #603
ma...@gmail.com <ma...@gmail.com> #604
ma...@gmail.com <ma...@gmail.com> #605
st...@gmail.com <st...@gmail.com> #606
jo...@gmail.com <jo...@gmail.com> #607
ro...@gmail.com <ro...@gmail.com> #608
qv...@gmail.com <qv...@gmail.com> #609
ca...@faystonsuji.org <ca...@faystonsuji.org> #610
ch...@gmail.com <ch...@gmail.com> #611
p....@gmail.com <p....@gmail.com> #612
al...@googlemail.com <al...@googlemail.com> #613
di...@gmail.com <di...@gmail.com> #614
Pixel 4, still here, reset doesn't help, reboot temporarily solves
lu...@gmail.com <lu...@gmail.com> #615
This will be my last pixel
ad...@gmail.com <ad...@gmail.com> #616
Thankfully the 911 dispatcher understood, but if you can't do anything on the screen and you can't take out the battery, then you are stuck if your phone decides to do something you don't want to happen.
Pixel 4 on Android 12.
a....@gmail.com <a....@gmail.com> #617
an...@gmail.com <an...@gmail.com> #618
an...@gmail.com <an...@gmail.com> #619
Fix it already Google FFS
ja...@gmail.com <ja...@gmail.com> #620
op...@gmail.com <op...@gmail.com> #621
ki...@gmail.com <ki...@gmail.com> #622
dc...@gmail.com <dc...@gmail.com> #623
aa...@gmail.com <aa...@gmail.com> #624
po...@gmail.com <po...@gmail.com> #625
ro...@gmail.com <ro...@gmail.com> #626
ro...@gmail.com <ro...@gmail.com> #627
Started immediately after Android 12 update.
ej...@gmail.com <ej...@gmail.com> #628
jw...@gmail.com <jw...@gmail.com> #629
ja...@gmail.com <ja...@gmail.com> #630
he...@gmail.com <he...@gmail.com> #631
po...@gmail.com <po...@gmail.com> #632
ti...@gmail.com <ti...@gmail.com> #633
pb...@gmail.com <pb...@gmail.com> #634
de...@gmail.com <de...@gmail.com> #635
This Android 12 is terrible on my Pixel 4. I've dealt with this during the beta versions, as this was... beta and acceptable to have bugs.
But the stable version is still buggy.
Only reason to go to a pixel phone is to get the newest Android on the market, but if it's to get it buggy I'll go back to another brand.
mu...@gmail.com <mu...@gmail.com> #636
kh...@gmail.com <kh...@gmail.com> #637
mj...@gmail.com <mj...@gmail.com> #638
it happens, I turn off Face Unlock in settings, via the Unlocking Your
Phone switch, then turn your phone off and back on then switch this setting
back on and it seems to bring back face unlock functionality.... until of
course it happens again. It might be a hardware aspect of face ID that
gets into an unrecoverable error until it's turned off and the phone is
turned off and back on again. Not sure but it so far has been a more
reliable way to fix the issue when it happens.
On Wed, Dec 22, 2021 at 3:58 AM <buganizer-system@google.com> wrote:
mi...@gmail.com <mi...@gmail.com> #639
pa...@googlemail.com <pa...@googlemail.com> #640
jw...@gmail.com <jw...@gmail.com> #641
kv...@gmail.com <kv...@gmail.com> #642
de...@gmail.com <de...@gmail.com> #643
ja...@gmail.com <ja...@gmail.com> #644
*checks phone*
No it's not.
I'm going to be incredibly optimistic and expect this fix to appear on my phone in Feb.
de...@gmail.com <de...@gmail.com> #645
ns...@gmail.com <ns...@gmail.com> #646
Please fix this Google!
zh...@gmail.com <zh...@gmail.com> #647
ar...@gmail.com <ar...@gmail.com> #648
la...@gmail.com <la...@gmail.com> #649
de...@gmail.com <de...@gmail.com> #650
gr...@gmail.com <gr...@gmail.com> #651
vi...@google.com <vi...@google.com>
la...@gmail.com <la...@gmail.com> #652
nu...@gmail.com <nu...@gmail.com> #653
GET_MAX_3ส่วนหัวของใบแจ้งหนี้: *** Inc.
nu...@gmail.com <nu...@gmail.com> #654
nu...@gmail.com <nu...@gmail.com> #655
nu...@gmail.com <nu...@gmail.com> #657
nu...@gmail.com <nu...@gmail.com> #660
ya...@gmail.com <ya...@gmail.com> #661
Did that five days ago and the nasty bug went away. Before that I need to restart the phone every single day to keep face recognition working.
Phone: Pixel 4, SP2A.220305.012
ma...@gmail.com <ma...@gmail.com> #662
can go a week at a time lately without it but it rears its ugly head every
now and then.
On Sun., Mar. 27, 2022, 5:08 a.m. , <buganizer-system@google.com> wrote:
jl...@gmail.com <jl...@gmail.com> #663
ja...@gmail.com <ja...@gmail.com> #664
It's not rare, it's not hard to reproduce, and if anybody wanted to fix it,
or it could be, it would have been fixed.
I'm on my third 4XL (due to the other bug around the battery status
sensor/cable failing) and all had this problem as well. I've just learnt to
reboot my phone when it happens.
Couple this with the pixel 6 issues and I can only suggest we use this to
guide our next upgrade choice.
On Tue, 12 Apr 2022, 20:27 , <buganizer-system@google.com> wrote:
an...@gmail.com <an...@gmail.com> #665
Every monthly update I've been hoping to get a fix instead of getting all those new features. What use are the features to us if the normal user experience is full of bugs? I am willing to live with other bugs (of which there are many), but the time wasted on restarting my phone, trying fixes and having to enter my PIN instead of having my face unlock it, has accumulated to hours. Fixing this should've been one of Google's priorities the moment it was discovered.
Unfortunately I haven't dared recommend Google phones to anyone in a while now. Today the well-known tech Youtuber Marques Brownlee uploaded a video re-addressing the bug-ridden Pixel 6. Getting confirmation that bugs are not something Google wants to deal with as a priority, I will have to purchase my next phone from another brand.
js...@google.com <js...@google.com> #666
Unbelievable that this is still a thing. I've been dealing with it for more than a year. The only workaround seems to be to restart the phone, which is really damned annoying since it only works for a few days at maximum, sometimes only a day or two. When it's broken, unlocking is incredibly annoying because I have to swipe from the very bottom of the screen to the very top...which is impossible with one hand because it's such a big phone.
yu...@gmail.com <yu...@gmail.com> #667
When it occurs, many phone functions stop working, including motion sense, lift to check phone. The only way to light up the screen is to push the power button. When in a call, the screen totally goes dark and I cannot use the keypad or use phone to check information.
Why this bug comes again and again??
As the
jl...@gmail.com <jl...@gmail.com> #668
ja...@gmail.com <ja...@gmail.com> #669
It's clearly a software bug - and clearly Google's got no intention of/ability to fix it.
ta...@gmail.com <ta...@gmail.com> #670
su...@gmail.com <su...@gmail.com> #671
I have started experiencing the same issue with my 4XL recently and looks like there's no proper fix.
What a shame I'll now have to find another brand :(
ba...@gmail.com <ba...@gmail.com> #672
gu...@gmail.com <gu...@gmail.com> #673
lu...@gmail.com <lu...@gmail.com> #674
Been dealing with clean black bar top screen for quite some time and as others have said restart device is only fix.
Usually occurs offer phone screen has been active and placed in pocket. Guessing proximity sensor is overwhelmed being in pocket and disables this and front camera throwing the clean black bar error.
ro...@gmail.com <ro...@gmail.com> #675
mi...@gmail.com <mi...@gmail.com> #676
br...@gmail.com <br...@gmail.com> #677
ai...@gmail.com <ai...@gmail.com> #678
vi...@google.com <vi...@google.com> #679
de...@gmail.com <de...@gmail.com> #680
ra...@gmail.com <ra...@gmail.com> #681
ma...@gmail.com <ma...@gmail.com> #682
vi...@google.com <vi...@google.com> #683
ma...@gmail.com <ma...@gmail.com> #684
That was generated using full. I have another from earlier but didn't know where to share. If you can let me know where they are stored in my pixel 4xl, I can get you another instance.
vi...@google.com <vi...@google.com> #685
Thanks for your input. You can find the bugreport under Files app > Other storage or you can refer to the link:
ma...@gmail.com <ma...@gmail.com> #686
Uploaded 3 new files into the same shared folder.
I only get a couple more patches and this phone is still great aside from this inconvenience. Would love to get a fix again as it was fixed before. Seems to happen when I have Bluetooth active.
vi...@google.com <vi...@google.com> #687
Re-
However, other affected users who are still facing the issue are also welcome to share the bugreport to take it forward.
ni...@gmail.com <ni...@gmail.com> #688
My bug report here :
I don't understand, is sharing bug reports really going to change anything?
If it's considered a hardware issue it cannot be solved with a software update and if it's soft related will Google provide an update to solve this?
There are literally hundreds of people who reported this bug which must mean thousands impacted by it in reality. This is definitely not a P3. There must be something that can be done to help.
ef...@gmail.com <ef...@gmail.com> #689
Still an issue for me on Android 13, resolved only by rebooting. Happens about 4 times a day, which gets tiresome fast.
sb...@gmail.com <sb...@gmail.com> #690
Been happening for a long long time.
Are we going to fix this Google?
Time to head to a different brand. I have 3 Pixel users in this house and we're all sick of it. I want to grab a newer Pixel for all of us but we ALL have this issue and not a single fix has happened over multiple OS updates.
and now, I guess since these phones are no longer supported they hope it will just sweep under the rug and be forgotten. Never, will I ever recommend a Pixel phone again to anyone.
Let's get an answer. Now.
Even if it's one we don't want to hear.
vv...@google.com <vv...@google.com> #692
Thank you for reporting this issue. Unfortunately, Pixel 4 is no longer supported, please see -
Description
When the unlock is working fine, I can reliable cause the issue to occur by locking the phone, placing the phone in my pocket and immediately removing. The issue also arises randomly when the phone has not been unlocked (sometimes for a while and sometimes for short periods of time).
Factory reset has not helped, safe mode did not help and deleting the face data and setting up again did not help. Many others are having this issue as seen on Reddit