Status Update
Comments
da...@gmail.com <da...@gmail.com> #2
I beleive the problem is inside onSizeChanged that is called after onConfigurationChanged, it has following code:
if (w != oldw) {
recomputeScrollPosition(w, oldw, mPageMargin, mPageMargin);
}
w always not equals oldw when changing orientation, so recomputeScrollPosition is called, but whit the same values for margin and oldMargin.
This should be fixed.
de...@gmail.com <de...@gmail.com> #3
cj...@gmail.com <cj...@gmail.com> #4
de...@gmail.com <de...@gmail.com> #5
cj...@gmail.com <cj...@gmail.com> #6
I managed to fix the issue by importing the source code of ViewPager in my project and modifying from onSizeChanged method the following line:
From:
if (w != oldw) {
recomputeScrollPosition(w, oldw, mPageMargin, mPageMargin);
}
To:
if (w != oldw) {
recomputeScrollPosition(w, oldw, 0, 0);
}
de...@gmail.com <de...@gmail.com> #7
ublic class FixedViewPager extends ViewPager {
public FixedViewPager(Context context, AttributeSet attrs) {
super(context, attrs);
}
public FixedViewPager(Context context) {
super(context);
}
@Override
protected void onSizeChanged(int w, int h, int oldw, int oldh) {
super.onSizeChanged(w-this.getPageMargin(), h, oldw-this.getPageMargin(), oldh);
}
}
cj...@gmail.com <cj...@gmail.com> #8
sa...@gmail.com <sa...@gmail.com> #9
cj...@gmail.com <cj...@gmail.com> #10
Workaround in post #6 still works.
wm...@gmail.com <wm...@gmail.com> #11
ja...@gmail.com <ja...@gmail.com> #12
mj...@gmail.com <mj...@gmail.com> #13
no...@gmail.com <no...@gmail.com> #14
Re
mi...@gmail.com <mi...@gmail.com> #15
sh...@gmail.com <sh...@gmail.com> #16
Giving it another week for a fix to be pushed out or I'll just sell the the phone.
Sloppy second rate stuff from Google.
[Deleted User] <[Deleted User]> #17
re...@gmail.com <re...@gmail.com> #18
pl...@gmail.com <pl...@gmail.com> #19
There is a reddit discussion as well:
I hope that this issue can be fixed with a software update,
otherwise, it will be useless to buy a new Pixel.
ne...@gmail.com <ne...@gmail.com> #20
an...@gmail.com <an...@gmail.com> #21
le...@googlemail.com <le...@googlemail.com> #22
we...@gmail.com <we...@gmail.com> #23
wi...@gmail.com <wi...@gmail.com> #24
an...@gmail.com <an...@gmail.com> #25
de...@gmail.com <de...@gmail.com> #26
vi...@gmail.com <vi...@gmail.com> #27
me...@gmail.com <me...@gmail.com> #28
me...@gmail.com <me...@gmail.com> #29
Just checked and in middle of downloading a new security update and new Google play system update. Hope this fixes issue with the fingerprint
ol...@gmail.com <ol...@gmail.com> #30
ol...@gmail.com <ol...@gmail.com> #31
sh...@gmail.com <sh...@gmail.com> #32
da...@gmail.com <da...@gmail.com> #33
ol...@gmail.com <ol...@gmail.com> #34
kc...@gmail.com <kc...@gmail.com> #35
mo...@gmail.com <mo...@gmail.com> #36
But really its unbelievable that something like this problem can even exist its GOOGLE WTF
cj...@gmail.com <cj...@gmail.com> #37
de...@gmail.com <de...@gmail.com> #38
It's a shame they cant figure this out, or havent put more effort into this.
I couldnt imagine having a brand new car, and the key fob doesnt work and the dealer just straight up doesnt respond.
to...@gmail.com <to...@gmail.com> #39
Your Google Support Enquiry: Case ID [5-5700000032117]
go...@gmail.com <go...@gmail.com> #40
nm...@gmail.com <nm...@gmail.com> #41
pf...@googlemail.com <pf...@googlemail.com> #42
el...@gmail.com <el...@gmail.com> #43
ta...@gmail.com <ta...@gmail.com> #44
s....@googlemail.com <s....@googlemail.com> #45
be...@gmail.com <be...@gmail.com> #46
da...@gmail.com <da...@gmail.com> #47
me...@gmail.com <me...@gmail.com> #48
Anyways, it's going on two weeks already. How frustrating. The fact that there is no update or no reassurance that it's being worked on is terrible.
pa...@gmail.com <pa...@gmail.com> #49
is...@gmail.com <is...@gmail.com> #50
ja...@gmail.com <ja...@gmail.com> #51
I have read that a factory reset fix's it...bt what if my battery runs out again will it happen again? can't re constantly doing factory resets...that's not a fix.
ba...@gmail.com <ba...@gmail.com> #52
s....@brunel.net <s....@brunel.net> #53
For those wondering: The new november update (SD1A.210817.037) does not fix this issue, unfortunately.
jo...@gmail.com <jo...@gmail.com> #54
me...@gmail.com <me...@gmail.com> #55
When I open a support ticket with Google, I feel like I'm just wasting my time.
I called four times. (2 times a week). But, unfortunately, I managed to speak to a rep only once.
"We are aware of the issue" is pretty much the most they would offer.
Even on this bug/ticket, there is no response from a google rep saying, "we are working on this ticket and hope to a fix soon."
It's almost like we are the lucky privileged few who already own the new pixel 6. For that, we must be grateful (even though it doesn't work).
It's a shame.
I'm about to throw in the towel and move on. I'm just about ready to return this cursed phone and move over to a Samsung.
ma...@gmail.com <ma...@gmail.com> #56
ro...@gmail.com <ro...@gmail.com> #57
Later I'll see if I can wipe the cache with ADB and see if that works.
ro...@gmail.com <ro...@gmail.com> #58
So as yet I know of no workaround.
ja...@gmail.com <ja...@gmail.com> #59
ma...@gmail.com <ma...@gmail.com> #60
sa...@gmail.com <sa...@gmail.com> #61
My phone doesn't see any pending updates (build SD1A.210817.036)
mo...@gmail.com <mo...@gmail.com> #62
sp...@gmail.com <sp...@gmail.com> #63
wa...@gmail.com <wa...@gmail.com> #64
ke...@godoy.cc <ke...@godoy.cc> #65
wa...@gmail.com <wa...@gmail.com> #66
ch...@gmail.com <ch...@gmail.com> #67
de...@gmail.com <de...@gmail.com> #68
See my comment above
I would not be surprised if it works after battery failure.
wy...@gmail.com <wy...@gmail.com> #70
ha...@gmail.com <ha...@gmail.com> #71
jo...@gmail.com <jo...@gmail.com> #72
Really really don't want to have to do a factory reset.🙎♂️
na...@gmail.com <na...@gmail.com> #73
I might be wrong here, but I think I came close to finding the root cause.
So far we have seen reports of this issue occuring after the phone is drained or overheating. No charge = not enough for SoC to run = SoC turns off. And overheat = SoC needs to cool down = SoC turns off.
The Tensor SoC contains a security core in addition to Titan M2. The security core is responsible, among other things, for interfacing with Titan M2 whenever the phone requests verification of credentials.
Maybe a loss of power is causing some malfunction in the security core leading to it not being able to communicate with Titan properly? Because if there is no communication between the SoC and Titan there will be no fingerprints and no way to save fingerprint data (at least I'm assuming so), which is exactly what this issue is.
Or, Titan M2 might be corrupting itself, since a factory reset is the only known fix and that wipes Titan M2. Though it might still be an issue with the security core.
Of course all of this is just speculation. I don't work at Google or know how these chips communicate.
bl...@gmail.com <bl...@gmail.com> #74
On Thu, Nov 25, 2021, 12:14 <buganizer-system@google.com> wrote:
mo...@gmail.com <mo...@gmail.com> #75
c....@gmail.com <c....@gmail.com> #76
rs...@gmail.com <rs...@gmail.com> #77
el...@gmail.com <el...@gmail.com> #78
Is there any update on a fix?
ma...@ik.me <ma...@ik.me> #79
ca...@gmail.com <ca...@gmail.com> #80
da...@gmail.com <da...@gmail.com> #81
Has anyone got a replacement device and confirmed it's not an issue on the replacement device after a battery drain?
wa...@gmail.com <wa...@gmail.com> #82
But it is clear that it is an issue that needs to be solved with something other than factory reset.
bj...@googlemail.com <bj...@googlemail.com> #83
al...@gmail.com <al...@gmail.com> #84
sa...@gmail.com <sa...@gmail.com> #85
an...@gmail.com <an...@gmail.com> #86
ja...@gmail.com <ja...@gmail.com> #87
ma...@gmail.com <ma...@gmail.com> #88
Anyone know if the restore after reset will include bring back all your other apps and settings as before eg whatsapp, signal, games etc... ?
si...@gmail.com <si...@gmail.com> #89
when i tried to turn it back on the set up crashed my phone so i had to start it up again. finger print sensor hasn't been working since.
al...@gmail.com <al...@gmail.com> #90
me...@gallische-dorp.net <me...@gallische-dorp.net> #91
pi...@gmail.com <pi...@gmail.com> #92
lu...@gmail.com <lu...@gmail.com> #93
The fact that you need to reset the phone isn't a fix.... This needs to be sorted.
ak...@gmail.com <ak...@gmail.com> #94
ai...@gmail.com <ai...@gmail.com> #95
ic...@gmail.com <ic...@gmail.com> #96
bl...@gmail.com <bl...@gmail.com> #97
jo...@gmail.com <jo...@gmail.com> #98
cl...@gmail.com <cl...@gmail.com> #99
ja...@gmail.com <ja...@gmail.com> #100
br...@gmail.com <br...@gmail.com> #101
ti...@gmail.com <ti...@gmail.com> #102
pe...@gmail.com <pe...@gmail.com> #103
rd...@gmail.com <rd...@gmail.com> #104
gk...@gmail.com <gk...@gmail.com> #105
Battery died, only just discovered pixel 6 pro stopped using fingerprint scanning. Security option is greyed and locked because it won't accept new biometrics.
I can't factory reset, so I am locked with no solution until it is fixed...
ed...@gmail.com <ed...@gmail.com> #106
vi...@gmail.com <vi...@gmail.com> #107
kr...@gmail.com <kr...@gmail.com> #108
na...@gmail.com <na...@gmail.com> #109
gz...@gmail.com <gz...@gmail.com> #110
wa...@gmail.com <wa...@gmail.com> #111
jp...@gmail.com <jp...@gmail.com> #112
ad...@gmail.com <ad...@gmail.com> #113
kh...@gmail.com <kh...@gmail.com> #114
mo...@gmail.com <mo...@gmail.com> #115
pe...@gmail.com <pe...@gmail.com> #116
th...@gmail.com <th...@gmail.com> #117
g3...@gmail.com <g3...@gmail.com> #118
br...@gmail.com <br...@gmail.com> #119
pe...@gmail.com <pe...@gmail.com> #120
sg...@gmail.com <sg...@gmail.com> #121
ha...@gmail.com <ha...@gmail.com> #122
p5...@gmail.com <p5...@gmail.com> #123
pe...@gmail.com <pe...@gmail.com> #124
wi...@gmail.com <wi...@gmail.com> #125
ma...@googlemail.com <ma...@googlemail.com> #126
da...@gmail.com <da...@gmail.com> #127
ru...@gmail.com <ru...@gmail.com> #128
ol...@gmail.com <ol...@gmail.com> #129
but still very annoying to have to do.
On Sun, Dec 5, 2021, 12:22 PM <buganizer-system@google.com> wrote:
ts...@gmail.com <ts...@gmail.com> #130
wi...@gmail.com <wi...@gmail.com> #131
sa...@gmail.com <sa...@gmail.com> #132
sa...@gmail.com <sa...@gmail.com> #133
dj...@gmail.com <dj...@gmail.com> #134
lu...@gmail.com <lu...@gmail.com> #135
Don't want to factory reset.
an...@gmail.com <an...@gmail.com> #136
sa...@gmail.com <sa...@gmail.com> #137
ar...@gmail.com <ar...@gmail.com> #138
Feels like high prio bug!)
ak...@gmail.com <ak...@gmail.com> #139
ss...@gmail.com <ss...@gmail.com> #140
Powered off automatically with 8% battery left, and lost my finger print sensor.
mj...@gmail.com <mj...@gmail.com> #141
How many reports/comments will it take to get some action and acknowledgement from the Android Team about this very real, very repeatable issue?
za...@gmail.com <za...@gmail.com> #142
js...@gmail.com <js...@gmail.com> #143
High priority. Please fix this ASAP!
sa...@gmail.com <sa...@gmail.com> #144
da...@gmail.com <da...@gmail.com> #145
th...@gmail.com <th...@gmail.com> #146
mi...@googlemail.com <mi...@googlemail.com> #147
je...@gmail.com <je...@gmail.com> #148
pl...@gmail.com <pl...@gmail.com> #149
wa...@gmail.com <wa...@gmail.com> #150
cr...@gmail.com <cr...@gmail.com> #152
fr...@gmail.com <fr...@gmail.com> #153
jc...@gmail.com <jc...@gmail.com> #154
cs...@gmail.com <cs...@gmail.com> #155
wa...@gmail.com <wa...@gmail.com> #156
ri...@gmail.com <ri...@gmail.com> #157
wa...@gmail.com <wa...@gmail.com> #158
ma...@ik.me <ma...@ik.me> #159
0r...@gmail.com <0r...@gmail.com> #160
da...@gmail.com <da...@gmail.com> #161
aj...@gmail.com <aj...@gmail.com> #162
SQ1D.211205.016.A1
ts...@gmail.com <ts...@gmail.com> #163
ka...@gmail.com <ka...@gmail.com> #164
ja...@gmail.com <ja...@gmail.com> #165
bj...@googlemail.com <bj...@googlemail.com> #166
bb...@gmail.com <bb...@gmail.com> #167
gr...@gmail.com <gr...@gmail.com> #168
ze...@gmail.com <ze...@gmail.com> #169
wi...@gmail.com <wi...@gmail.com> #170
In this case it may be similar.. the key question is will the problem reoccur on a patched device or not?
I will have to take the plunge and try it , then immediately test what happens to the fingerprint enrollment after a battery drain. This will be the only way to validate whether the patch has fixed it or not
ma...@ik.me <ma...@ik.me> #171
jo...@gmail.com <jo...@gmail.com> #172
I went on the chat support and decided to bite the bullet and do a factory reset. I then waited for the phone to die and the fingerprint sensor has continued to work.
I didn't try a factory reset before the December update so can't 100% say if the issue was solved by the update+factory reset or factory reset alone. I will let the phone die again to make sure it is definitely working properly
me...@gregsharpe.co.uk <me...@gregsharpe.co.uk> #173
me...@gregsharpe.co.uk <me...@gregsharpe.co.uk> #174
vi...@gmail.com <vi...@gmail.com> #175
tu...@gmail.com <tu...@gmail.com> #176
bj...@googlemail.com <bj...@googlemail.com> #177
I'm not sure holding out will prove the successful, given Google are already offering new devices to those affected, though I hope they do fix it for everyone.
ak...@gmail.com <ak...@gmail.com> #178
wh...@gmail.com <wh...@gmail.com> #179
ro...@gmail.com <ro...@gmail.com> #180
je...@gmail.com <je...@gmail.com> #181
ad...@harrisonamj.com <ad...@harrisonamj.com> #182
jo...@gmail.com <jo...@gmail.com> #183
- sideloaded December OTA
- issue still present
- factory reset
- fingerprint sensor working after the reset
- let the battery die twice, both times the fingerprint sensor worked after recharging the phone
so while the OTA update didn't directly solve the issue, it looks like after a factory reset the issue is not there the following times your phone battery dies. But this is just my experience on one device
mo...@gmail.com <mo...@gmail.com> #184
wi...@gmail.com <wi...@gmail.com> #185
Hopefully this is the last time it happened
bl...@gmail.com <bl...@gmail.com> #186
was a factory reset. Sucks to do but it was an attempt. Coming on here
wasnt helping either with everyone whining about the same thing. If there
was help it got lost by the amount of complaining. If you're not happy with
your pixel, trade it in and get yourself an iPhone.
On Tue, Dec 14, 2021, 10:38 <buganizer-system@google.com> wrote:
wi...@gmail.com <wi...@gmail.com> #187
al...@gmail.com <al...@gmail.com> #188
da...@gmail.com <da...@gmail.com> #189
They told me last night that they are working on the issue.
It sucks but I'm thinking it's probs best to wait.
ul...@gmail.com <ul...@gmail.com> #190
This thing is driving me crazy.
Even after the December update, the scanner has a detection rate of 5-6 out of 10. And the duration - if it works - is about 1.5 - 2 sec.
No Google certified bulletproof glass.
Fortunately, I still have my Pixel 5. This fingerprint scanner always works. Even with dirty fingers. And blazing fast. And reliable.
Who invented this non-functioning hipster crap? And sells this non-function as a security feature? Do you think we're stupid?
pe...@gmail.com <pe...@gmail.com> #191
jo...@gmail.com <jo...@gmail.com> #192
ry...@gmail.com <ry...@gmail.com> #193
aj...@gmail.com <aj...@gmail.com> #194
Apparently somebody is saying Google is going to make a fix so everyone doesn't have to factory reset, but I didn't see a real source for that yet and I didn't want to wait. I'm happy with this solution now, sorry for those who will finally give up and reset though.
jo...@gmail.com <jo...@gmail.com> #195
wi...@gmail.com <wi...@gmail.com> #196
Yes, you could wait in vain for months for a patch from Google but it won't happen. You could send your phone back for a refund and buy an iPhone instead.
Or you can just endure the short term hardship, do a backup of everything and start from scratch.
Google has form on this issue , and the customer service track record isn't great. Just count the responses from Google on this thread.
ja...@gmail.com <ja...@gmail.com> #197
I've been holding onto the Android ecosystem for too long. The terrible response from Google may be just enough to tip me over into the iPhone camp.
cp...@gmail.com <cp...@gmail.com> #198
sa...@gmail.com <sa...@gmail.com> #199
Any news on the update, as I am only a few days into my contract in which I am still able to return the phone.
wa...@gmail.com <wa...@gmail.com> #200
ww...@gmail.com <ww...@gmail.com> #201
el...@gmail.com <el...@gmail.com> #202
mq...@google.com <mq...@google.com> #203
ff...@gmail.com <ff...@gmail.com> #204
da...@gmail.com <da...@gmail.com> #205
di...@gmail.com <di...@gmail.com> #206
pp...@gmail.com <pp...@gmail.com> #207
to...@gmail.com <to...@gmail.com> #208
bi...@gmail.com <bi...@gmail.com> #209
da...@gmail.com <da...@gmail.com> #210
da...@gmail.com <da...@gmail.com> #211
mi...@gmail.com <mi...@gmail.com> #212
ad...@gmail.com <ad...@gmail.com> #213
al...@gmail.com <al...@gmail.com> #214
pa...@gmail.com <pa...@gmail.com> #215
Phone died and now it's become my problem too.
mv...@gmail.com <mv...@gmail.com> #216
0r...@gmail.com <0r...@gmail.com> #217
ju...@gmail.com <ju...@gmail.com> #218
pl...@gmail.com <pl...@gmail.com> #219
ll...@gmail.com <ll...@gmail.com> #220
I'm having the issue on my pixel 6. When it was working I didn't experience issues with fingerprint unlock. But it stopped working randomly and fails evertime I try to setup a new fingerprint.
That being said I love the pixel and will wait for an update because I like the abuse.
st...@gmail.com <st...@gmail.com> #221
jo...@gmail.com <jo...@gmail.com> #222
ts...@gmail.com <ts...@gmail.com> #223
da...@gmail.com <da...@gmail.com> #224
COME ON GOOGLE, FIX IT!
rm...@gmail.com <rm...@gmail.com> #225
au...@hotmail.com <au...@hotmail.com> #226
cj...@gmail.com <cj...@gmail.com> #227
ma...@ik.me <ma...@ik.me> #228
me...@gmail.com <me...@gmail.com> #229
ja...@gmail.com <ja...@gmail.com> #230
lj...@gmail.com <lj...@gmail.com> #231
mi...@gmail.com <mi...@gmail.com> #232
wy...@gmail.com <wy...@gmail.com> #233
Eagerly awaiting a fix :) Love you, Google!
al...@gmail.com <al...@gmail.com> #234
What to do? Without doing factory reset.
Please help.
gh...@gmail.com <gh...@gmail.com> #235
mo...@gmail.com <mo...@gmail.com> #236
ab...@gmail.com <ab...@gmail.com> #237
an...@eventx.io <an...@eventx.io> #238
Google, please fix this issue asap.
wo...@gmail.com <wo...@gmail.com> #239
pr...@gmail.com <pr...@gmail.com> #240
fa...@gmail.com <fa...@gmail.com> #241
vi...@gmail.com <vi...@gmail.com> #242
t0...@gmail.com <t0...@gmail.com> #243
It's been almost two months since this issue was reported.
Google should explain the situation.
ll...@gmail.com <ll...@gmail.com> #244
Did backups on everything first but it was still 20 minutes of logging into various accounts.
cr...@gmail.com <cr...@gmail.com> #245
ma...@gmail.com <ma...@gmail.com> #246
cp...@gmail.com <cp...@gmail.com> #247
What a joke at this point.
an...@greylensman.com <an...@greylensman.com> #248
cp...@gmail.com <cp...@gmail.com> #249
ch...@gmail.com <ch...@gmail.com> #250
pe...@gmail.com <pe...@gmail.com> #251
Does anyone in this thread has any email ID for escalating this issue?.
Google support guys are just moving around to get the warranty time get
over so that they do not have to replace the device. I am behind this issue
with Google support team from last 2 months. It's disgusting and utter
failure from Google.
On Thu, Dec 30, 2021, 07:58 <buganizer-system@google.com> wrote:
mi...@gmail.com <mi...@gmail.com> #252
Then, if you have no resolution, file a warranty claim. You can ask Support to do this in the same chat. The warranty does not cover software bugs, but in this scenario a piece of hardware has failed due to some defect in how this phone was built. Simply request a warranty return
ka...@gmail.com <ka...@gmail.com> #253
sa...@gmail.com <sa...@gmail.com> #254
Many users impacted, when are you doing a global product #recall? We need solutions NOW!
mo...@gmail.com <mo...@gmail.com> #255
ko...@gmail.com <ko...@gmail.com> #256
he...@gmail.com <he...@gmail.com> #258
yi...@gmail.com <yi...@gmail.com> #259
Really disappointed.
ja...@gmail.com <ja...@gmail.com> #260
cm...@gmail.com <cm...@gmail.com> #261
je...@gmail.com <je...@gmail.com> #262
lo...@gmail.com <lo...@gmail.com> #263
ed...@gmail.com <ed...@gmail.com> #264
ma...@gmail.com <ma...@gmail.com> #265
ma...@gmail.com <ma...@gmail.com> #266
lu...@gmail.com <lu...@gmail.com> #267
no...@gmail.com <no...@gmail.com> #268
Should we do some public noise?
El mar, 4 de ene. de 2022 6:34 a. m., <buganizer-system@google.com>
escribió:
or...@jaguarlandrover.com <or...@jaguarlandrover.com> #269
ol...@gmail.com <ol...@gmail.com> #270
ja...@gmail.com <ja...@gmail.com> #271
bo...@gmail.com <bo...@gmail.com> #272
Any idea if it will be fixed on the next update [I am on Nov 5th update]? Thanks.
mi...@gmail.com <mi...@gmail.com> #273
lu...@gmail.com <lu...@gmail.com> #274
when will you address this!!!!!!!!!!!!!
ah...@gmail.com <ah...@gmail.com> #275
em...@gmail.com <em...@gmail.com> #276
Plugged in to charge overnight with 30% battery left and woke up to a broken fingerprint scanner.
Nothing working and not allowing me to register a fingerprint.
Please fix this ASAP as this has been ongoing for months already!
be...@gmail.com <be...@gmail.com> #277
ma...@gmail.com <ma...@gmail.com> #278
sa...@gmail.com <sa...@gmail.com> #279
mf...@gmail.com <mf...@gmail.com> #280
er...@gmail.com <er...@gmail.com> #281
ph...@gmail.com <ph...@gmail.com> #282
na...@gmail.com <na...@gmail.com> #283
When my Pixel 6 fully discharges I charge it to around 20-30% before turning it on, and the issue doesn't appear. Though my unit might be unaffected by this in the first place.
je...@gmail.com <je...@gmail.com> #284
lo...@gmail.com <lo...@gmail.com> #285
ng...@gmail.com <ng...@gmail.com> #286
dz...@gmail.com <dz...@gmail.com> #287
status:
"I appreciate your time and patience. I still haven't received an update from the team, I'm constantly checking this with our team. Please be assured, we will get this sorted as soon as possible."
co...@gmail.com <co...@gmail.com> #288
br...@gmail.com <br...@gmail.com> #289
working. Pixel 6 pro won't accept new fingerprint registration. Build
number attached.
Sabrina McKinney
3182189143
On Mon, Jan 10, 2022, 08:00 <buganizer-system@google.com> wrote:
rh...@gmail.com <rh...@gmail.com> #290
Pixel 6 Pro.
Set Up Fingerprint when first got the phone, then let the battery die, now I cannot enroll my fingerprint.
st...@gmail.com <st...@gmail.com> #291
I just started having the same issue last night when my phone ran out of battery on me. Just starting my troubleshooting, but based on previous comments, not entirely hopeful there is a non destructive (aka factory reset) option...
to...@gmail.com <to...@gmail.com> #292
du...@gmail.com <du...@gmail.com> #293
pa...@gmail.com <pa...@gmail.com> #294
ho...@gmail.com <ho...@gmail.com> #295
sp...@gmail.com <sp...@gmail.com> #296
ag...@gmail.com <ag...@gmail.com> #297
ra...@gmail.com <ra...@gmail.com> #298
ba...@gmail.com <ba...@gmail.com> #299
Pls help with some solution, You are Google. If you can't solve, why will people Google???
ja...@gmail.com <ja...@gmail.com> #300
an...@gmail.com <an...@gmail.com> #301
ph...@gmail.com <ph...@gmail.com> #302
jo...@gmail.com <jo...@gmail.com> #303
kr...@gmail.com <kr...@gmail.com> #304
en...@gmail.com <en...@gmail.com> #305
br...@gmail.com <br...@gmail.com> #306
Now I have no finger print and enrollment is broken.
[Deleted User] <[Deleted User]> #307
ro...@robinkanters.nl <ro...@robinkanters.nl> #308
tk...@gmail.com <tk...@gmail.com> #309
m....@gmail.com <m....@gmail.com> #310
er...@gmail.com <er...@gmail.com> #311
mm...@maximilianhp.com <mm...@maximilianhp.com> #312
ri...@gmail.com <ri...@gmail.com> #313
The silence from Google is deafening.
ri...@gmail.com <ri...@gmail.com> #314
No fix incoming.
ph...@gmail.com <ph...@gmail.com> #315
ma...@ik.me <ma...@ik.me> #316
to...@gmail.com <to...@gmail.com> #317
fl...@gmail.com <fl...@gmail.com> #318
ms...@gmail.com <ms...@gmail.com> #319
an...@gmail.com <an...@gmail.com> #320
jp...@gmail.com <jp...@gmail.com> #321
cp...@gmail.com <cp...@gmail.com> #322
F*cking incredible.
zi...@gmail.com <zi...@gmail.com> #323
ma...@gmail.com <ma...@gmail.com> #324
There are definitely thousands of people affected by this issue and if Google engineers see there are only 161 people who started it here, they might think it's something that's only affecting a tiny minority of the owners, while that doesn't seem to be the case.
me...@gmail.com <me...@gmail.com> #325
How can you ignore so many people with such a severe issue? Have you even looked up how many phones you sold encountered this issue?
The most ironic part is that you keep targeting me for Google-Pay advertisements but I have no convinient way to lock and unlock my phone for Google Pay to work!
This is beyond me...
jo...@gmail.com <jo...@gmail.com> #326
js...@gmail.com <js...@gmail.com> #327
sa...@gmail.com <sa...@gmail.com> #328
kr...@gmail.com <kr...@gmail.com> #329
cr...@gmail.com <cr...@gmail.com> #330
ma...@ik.me <ma...@ik.me> #331
See his Reddit comment here:
Hope we can make some noise about that!!!
ma...@gmail.com <ma...@gmail.com> #332
lo...@googlemail.com <lo...@googlemail.com> #333
a....@gmail.com <a....@gmail.com> #334
pj...@gmail.com <pj...@gmail.com> #335
ad...@gmail.com <ad...@gmail.com> #336
le...@gmail.com <le...@gmail.com> #337
to...@gmail.com <to...@gmail.com> #338
lc...@gmail.com <lc...@gmail.com> #339
lu...@gmail.com <lu...@gmail.com> #340
da...@gmail.com <da...@gmail.com> #341
oc...@gmail.com <oc...@gmail.com> #342
lu...@gmail.com <lu...@gmail.com> #343
@everyone, please star this thread.
Google, FIX IT NOW!!!!!!!!!!!!!!!!!!!
oc...@gmail.com <oc...@gmail.com> #344
ph...@gmail.com <ph...@gmail.com> #345
an...@eventx.io <an...@eventx.io> #346
FIX THIS NOW!
ja...@gmail.com <ja...@gmail.com> #347
FIX this NOW
FIX this NOW
FIX this NOW
FIX this NOW
mi...@gmail.com <mi...@gmail.com> #348
je...@gmail.com <je...@gmail.com> #349
Phone ran out of battery last night and now the fingerprint is nonfunctional.
Kind of dumb, as this fingerprint is a key feature for security...
ko...@gmail.com <ko...@gmail.com> #350
I lost the feature while loading the battery. Few minutes after plug in (at about 60% battery level), the phone rebooted itself the the fingerprint sensor was gone.
Applied the January patch but it didn't help.
The sensor is gone, and I keep on getting enrollment error message while trying to register fingerprints.
br...@rowlan.com <br...@rowlan.com> #351
ra...@gmail.com <ra...@gmail.com> #352
ms...@gmail.com <ms...@gmail.com> #353
Google please wake up an address this issue
an...@gmail.com <an...@gmail.com> #354
ja...@gmail.com <ja...@gmail.com> #355
cp...@gmail.com <cp...@gmail.com> #356
xs...@gmail.com <xs...@gmail.com> #357
Do not want to factory reset.
pr...@gmail.com <pr...@gmail.com> #358
mi...@gmail.com <mi...@gmail.com> #359
jo...@googlemail.com <jo...@googlemail.com> #360
I have over a hundred apps and no wish to do a factory reset.
Google please fix this.
ch...@gmail.com <ch...@gmail.com> #361
an...@gmail.com <an...@gmail.com> #362
da...@gmail.com <da...@gmail.com> #363
Like thanks for checking if it works.
As a pixel fangirl I regret leaving my pixel 4.
Is there anyway we can complain or is it just a case of that's it?
cs...@gmail.com <cs...@gmail.com> #364
There is a limit to consumer patience.
I have had these before Nexus 4, 5, 6P
Pixel 2XL, 4a, and the latest 6.
rz...@gmail.com <rz...@gmail.com> #365
gr...@gmail.com <gr...@gmail.com> #366
John Groot
6820 Upland Rd
Camarillo CA 93012
Cell: 805-844-7993
<mailto:grootsocamarillo@gmail.com> grootsocamarillo@gmail.com
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Tuesday, January 18, 2022 6:43 PM
To: b-system+-1146833262@google.com
Cc: grootsocamarillo@gmail.com
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
<mailto:cs...@gmail.com> cs...@gmail.com added
No More Pixel Phones if Google doesn't fix this in the next update.
There is a limit to consumer patience.
I have had these before Nexus 4, 5, 6P
Pixel 2XL, 4a, and the latest 6.
_______________________________
Reference Info: 205335447 Fingerprint Enrollment Failure on latest Security Update - Pixel 6 Pro
component: Android Public Tracker <
status: Assigned
reporter: cj...@gmail.com <mailto:cj...@gmail.com>
assignee: an...@google.com <mailto:an...@google.com>
cc: an...@google.com <mailto:an...@google.com> , il...@google.com <mailto:il...@google.com> , ku...@google.com <mailto:ku...@google.com> , and 6 more
type: Bug
priority: P2
severity: S2
retention: Component default
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue. <
--
This email has been checked for viruses by AVG.
em...@gmail.com <em...@gmail.com> #367
my...@gmail.com <my...@gmail.com> #368
ri...@gmail.com <ri...@gmail.com> #369
reset
I went to this Google page and there it gives you the instructions to
calibrate it yourself
On Wed, Jan 19, 2022, 2:10 PM <buganizer-system@google.com> wrote:
su...@gmail.com <su...@gmail.com> #370
it multiple times. Also update to the latest Android 12. Does not help at
all.
On Wed, 19 Jan 2022, 23:35 , <buganizer-system@google.com> wrote:
su...@gmail.com <su...@gmail.com> #371
0r...@gmail.com <0r...@gmail.com> #372
Given a firmware version XXXXX
Then cause the battery to drain
Then charge the phone and turn on
Then make sure everything works.
wo...@gmail.com <wo...@gmail.com> #373
Your phone's current software version:SQ1D.220105.007 is newer than this
repair tool has.
On Wed, 19 Jan 2022 at 18:35, <buganizer-system@google.com> wrote:
mr...@gmail.com <mr...@gmail.com> #374
dv...@gmail.com <dv...@gmail.com> #375
Is there anyone here who lost enrollment after their battery drained while already on the January update?
It seems pretty clear from the posts that installing January update doesn't fix it once the bug has already happened. I'm terrified of losing battery and experiencing this and having to reset - meaning that Google didn't really fix the bug in January.
I agree that they should have fixed it with an OTA so people don't need to reset, but curious if it can happen from now on.
ga...@gmail.com <ga...@gmail.com> #376
Please tell me Sundar Pichai is not using an Iphone?
Can you fix this dummy issue please ?
Thank you
ch...@gmail.com <ch...@gmail.com> #377
reported issue. Fingerprint scanner lost it's mind, can't enroll new
fingerprints. The calibration tool has not fixed it. I have not Factory
Reset yet.
On Thu, Jan 20, 2022, 3:29 PM <buganizer-system@google.com> wrote:
je...@gmail.com <je...@gmail.com> #378
ch...@gmail.com <ch...@gmail.com> #379
scanner broken
On Fri, Jan 21, 2022, 11:42 AM <buganizer-system@google.com> wrote:
dv...@gmail.com <dv...@gmail.com> #380
After. Jan update first, then battery died overnight, the fingerprint scanner broken
Wow Google, just wow. So this from the December release notes (which most got in January update cause December got halted) does NOT cover this bug.
Additional fixes for issues preventing enrollment of new fingerprints in certain conditions
Google, fix this. It's not acceptable. Everyone should star the issue in the upper left-hand corner.
mi...@gmail.com <mi...@gmail.com> #381
Your phone's current software version:SQ1D.220105.007 is newer than this repair tool has.
mr...@gmail.com <mr...@gmail.com> #382
jr...@gmail.com <jr...@gmail.com> #383
ja...@gmail.com <ja...@gmail.com> #384
ca...@gmail.com <ca...@gmail.com> #385
I guess after all this time I will just give up and factory reset. And pray that my phone never dies again. Not very practical to be factory resetting every few weeks.
oc...@gmail.com <oc...@gmail.com> #386
vs...@gmail.com <vs...@gmail.com> #387
vi...@gmail.com <vi...@gmail.com> #388
Please can this be fixed. Phone batteries die all the time and I can't factory reset my phone constantly!
lj...@gmail.com <lj...@gmail.com> #389
Pretty disappointing to see this issue has been ongoing for over 3 months now, seriously considering going back to my s21, the lack of fingerprint and Face unlock ruins the pixel experience.
Would seriously appreciate an update from Google.
p....@gmail.com <p....@gmail.com> #390
Like all of you we also had exactly the same issue, but I can confirm that after installing the January update, if you DO THE FACTORY RESET once, it will fix the issue forever. Tried it several times after update + factory reset, no more issues even after battery drain with fingerprint unlock or Enrollment. I know a factory reset is not an easy process for most of you specially if you have your phone for several months now, but I recommend you to do so and don't wait for any response or new update from google anymore. Otherwise you might need to wait another 3 months or so.
mr...@gmail.com <mr...@gmail.com> #391
ge...@gmail.com <ge...@gmail.com> #392
If the issue was there every single time to begin with we would have more people complaining about this.
All I can say is in my case after the battery has run out, I plugged in the phone and started it, and before it finished the start it run out of battery again. I'm not sure it as anything to do with it but you can't tell for fact that the way to reproduce is as simple as letting battery drain.
It can be anything that happen at the same time that corrupt any kind of storage used for fingerprint or whatever.
Unless you successfully reproduce that state multiple time in the past at 100% ratio with that same method I would not believe any affirmation saying it can't happen anymore.
That said doing the factory reset is still the only thing we can do you're right on that point. But with this "solution" 2FA and bank apps are a pain (might take few weeks to get the second fully working if you need some paper shit to confirm that's your phone)
wo...@gmail.com <wo...@gmail.com> #393
can't just do factory reset every time this happens.
On Tue, Jan 25, 2022, 20:29 <buganizer-system@google.com> wrote:
ur...@holcroft.net <ur...@holcroft.net> #394
jo...@gmail.com <jo...@gmail.com> #395
vd...@gmail.com <vd...@gmail.com> #396
If the developers need more information let me know.
Hope more people will submit a comment so the problem will be fixed sooner
le...@gmail.com <le...@gmail.com> #397
w....@googlemail.com <w....@googlemail.com> #398
ro...@gmail.com <ro...@gmail.com> #399
se...@gmail.com <se...@gmail.com> #400
More than 2 months and the same problem even after the update...
No fingerprint after the battery is dead !
Google please fix this problem is really annoying for a expensive phone like google pixel 6 pro 256 GB
to...@gmail.com <to...@gmail.com> #401
GOOGLE FIX THIS!!
jo...@gmail.com <jo...@gmail.com> #402
After the restart no fingerprint scanning possible and cannot enroll new fingerprints. Wonderful.
an...@gmail.com <an...@gmail.com> #403
co...@gmail.com <co...@gmail.com> #404
jo...@gmail.com <jo...@gmail.com> #405
ro...@gmail.com <ro...@gmail.com> #406
ow...@gmail.com <ow...@gmail.com> #407
si...@gmail.com <si...@gmail.com> #408
is...@gmail.com <is...@gmail.com> #409
mo...@gmail.com <mo...@gmail.com> #410
This is very unprofessional from Google!!!
ha...@gmail.com <ha...@gmail.com> #411
ma...@ik.me <ma...@ik.me> #412
ha...@gmail.com <ha...@gmail.com> #413
cb...@gmail.com <cb...@gmail.com> #414
ej...@gmail.com <ej...@gmail.com> #415
da...@gmail.com <da...@gmail.com> #416
pi...@gmail.com <pi...@gmail.com> #417
qu...@gmail.com <qu...@gmail.com> #418
I Come from heures nor view 10 and wanted to expérience a Real flagship. Vert disappointed. The finger sensor juste des not work, and no face id to compensate. I have rgistered m'y fingers again and again And it just Does Not work I dont évier rely on online reviews again
ar...@gmail.com <ar...@gmail.com> #419
t0...@gmail.com <t0...@gmail.com> #420
Google may not consider this issue important.
It's crazy that there are no announcements for 3 months.
mi...@googlemail.com <mi...@googlemail.com> #421
cf...@gmail.com <cf...@gmail.com> #422
cc...@gmail.com <cc...@gmail.com> #423
cc...@gmail.com <cc...@gmail.com> #424
cr...@gmail.com <cr...@gmail.com> #425
m....@gmail.com <m....@gmail.com> #426
- cold fingers in Canadian weather, no luck 10 times then fall back to pin unlock.
- trying to unlock on the move while walking or shopping, you have to pin yourself still and keep pressing for a 2 seconds to unlock! If your finger slide a bit on the screen, then try again!
- working hands! carpenters, contractors, painters any tiny bit of dust in your finger is a problem to unlock.
- wet, 2 hours after taking shower is a no no for the Pixel unlock!
Too bad, who is this scanner for? It is not working! If you cant fix it, is it a hardware limitations then recall it and save your reputation!
ma...@gmail.com <ma...@gmail.com> #427
terrible implementation of fingerprint unlock. sometimes it works, sometimes it doesn't. it is completely unreliable and it's not performing as advertised.
Bring back face unlock!
ma...@gmail.com <ma...@gmail.com> #428
je...@gmail.com <je...@gmail.com> #429
ji...@gmail.com <ji...@gmail.com> #430
br...@veg.vet <br...@veg.vet> #431
mo...@gmail.com <mo...@gmail.com> #432
ll...@gmail.com <ll...@gmail.com> #433
I begrudgingly factory reset my phone about a month ago after coming across this article and it fixed the sensor and I've abused the phone/run it dry multiple times without the issue coming back.
If I comes back I'm getting a new phone but no issues so far.
jo...@gmail.com <jo...@gmail.com> #434
ma...@gmail.com <ma...@gmail.com> #435
sh...@gmail.com <sh...@gmail.com> #436
to...@gmail.com <to...@gmail.com> #437
Maybe the fix needs to be tested if it works after battery dies out :p
ak...@gmail.com <ak...@gmail.com> #438
mi...@gmail.com <mi...@gmail.com> #439
je...@gmail.com <je...@gmail.com> #440
si...@gmail.com <si...@gmail.com> #441
On Mon, Feb 7, 2022, 6:29 PM <buganizer-system+559537+205335447@google.com>
wrote:
my...@gmail.com <my...@gmail.com> #442
After the February update, fingerprint registration and fingerprint unlocking are working again!
Good thing I waited long enough and didn't reset to factory settings :)
Yay! Thank you, whoever fixed this at google!
Now I'll continue recommending this device to my friends.
jo...@gmail.com <jo...@gmail.com> #443
-John
(847)293-5708
On Mon, Feb 7, 2022, 6:19 PM <buganizer-system@google.com> wrote:
ke...@rowlan.com <ke...@rowlan.com> #444
ku...@gmail.com <ku...@gmail.com> #445
tu...@gmail.com <tu...@gmail.com> #446
Finally fixed, can confirm and no reset required!
Den tis 8 feb. 2022 03:51 <buganizer-system@google.com> skrev:
ko...@gmail.com <ko...@gmail.com> #447
jo...@googlemail.com <jo...@googlemail.com> #448
jo...@gmail.com <jo...@gmail.com> #449
I would have rather waited. At least it should not happen again.
Very disappointed with the communication
mj...@gmail.com <mj...@gmail.com> #450
ma...@ik.me <ma...@ik.me> #451
vd...@gmail.com <vd...@gmail.com> #452
rd...@gmail.com <rd...@gmail.com> #453
ad...@gmail.com <ad...@gmail.com> #454
vi...@gmail.com <vi...@gmail.com> #455
cf...@gmail.com <cf...@gmail.com> #456
na...@gmail.com <na...@gmail.com> #457
al...@gmail.com <al...@gmail.com> #458
se...@gmail.com <se...@gmail.com> #459
wo...@gmail.com <wo...@gmail.com> #460
du...@gmail.com <du...@gmail.com> #461
ro...@gmail.com <ro...@gmail.com> #462
sh...@gmail.com <sh...@gmail.com> #463
me...@gmail.com <me...@gmail.com> #464
ca...@gmail.com <ca...@gmail.com> #465
sp...@gmail.com <sp...@gmail.com> #466
Initial attempt to enroll still failed, but perhaps as I was preemptively moving my thumb around too much - doing the edges/tip before it asked me to, so perhaps that throws it off.
Followed it's instructions exactly and then it worked.
su...@gmail.com <su...@gmail.com> #467
<Sorry in advance of my comment is too off topic (not just about the Pixel 6 or 6Pro for this bug>
or...@jaguarlandrover.com <or...@jaguarlandrover.com> #468
pc...@gmail.com <pc...@gmail.com> #469
ma...@gmail.com <ma...@gmail.com> #470
ma...@gmail.com <ma...@gmail.com> #471
cc...@gmail.com <cc...@gmail.com> #472
jo...@gmail.com <jo...@gmail.com> #473
ma...@gmail.com <ma...@gmail.com> #474
ta...@gmail.com <ta...@gmail.com> #475
jn...@gmail.com <jn...@gmail.com> #476
kd...@gmail.com <kd...@gmail.com> #477
ve...@gmail.com <ve...@gmail.com> #478
br...@gmail.com <br...@gmail.com> #479
Screen finger print
sl...@gmail.com <sl...@gmail.com> #480
al...@gmail.com <al...@gmail.com> #481
rb...@gmail.com <rb...@gmail.com> #482
rp...@gmail.com <rp...@gmail.com> #483
sa...@gmail.com <sa...@gmail.com> #484
tj...@gmail.com <tj...@gmail.com> #485
Fingerprint Enrollment Failure on latest Security Update - Pixel 6 Pro
It used to work, not very good, but sometimes.
My last Pixel with the fingerprint reader on the back worked flawlessly.
Maybe should have saved some money and got the 5A!
vs...@gmail.com <vs...@gmail.com> #486
vs...@gmail.com <vs...@gmail.com> #487
ca...@gmail.com <ca...@gmail.com> #488
ve...@gmail.com <ve...@gmail.com> #489
bl...@gmail.com <bl...@gmail.com> #490
le...@gmail.com <le...@gmail.com> #491
di...@gmail.com <di...@gmail.com> #492
I'm having exactly the same issue. Wonderful. Time to PIN unlock like it's 2008!
ty...@gmail.com <ty...@gmail.com> #493
ty...@gmail.com <ty...@gmail.com> #494
va...@kongtakane.net <va...@kongtakane.net> #495
mi...@hotmail.co.uk <mi...@hotmail.co.uk> #496
th...@gmail.com <th...@gmail.com> #497
kr...@gmail.com <kr...@gmail.com> #498
ro...@gmail.com <ro...@gmail.com> #499
ro...@gmail.com <ro...@gmail.com> #500
6 months after this defect was raised and there are still no updates from Google, other than the "switch to our official screen protectors" excuse, when that is clearly not the case. Being one of the two latest flagship phones from Google (and not some random startup), after 6 months, one would expect at least a communication from them clarifying whether it's a hardware or software issue. If it's the latter, I wouldn't mind waiting a few weeks or months for an update, but in case of the former, I would expect a company like Google to issue widespread recalls for faulty hardware. And we are talking about an essential and much used piece of hardware like the Fingerprint Scanner. I couldn't care less about other components, such as Bluetooth or NFC, and could wait for a patch even for years, if anything (not that I would notice anyway), if these were defective instead. But the Fingerprint Scanner? That component is integral for some apps like Password Managers and whatnot, let alone the fact that the Fingerprint Scanner is the very first thing that most of us use after grabbing our phones.
Since there are no communications whatsoever from Google on this issue, like an ETA for an update (marketing failure from Google if you ask me—major disappointment), I requested a full refund for my Pixel 6. So that's that. I'm jumping out of the Pixel 6 train as soon as I jumped in. And don't get me wrong, I am a Google/Nexus/Pixel fan, and I am a happy owner of a Nexus 5X and Pixel 3a, but even with their limitations, their essential components, like the Fingerprint Scanner, work just fine.
ak...@gmail.com <ak...@gmail.com> #501
ma...@gmail.com <ma...@gmail.com> #502
and also google play security update not applying
da...@gmail.com <da...@gmail.com> #503
ea...@gmail.com <ea...@gmail.com> #504
me...@gmail.com <me...@gmail.com> #505
ga...@gmail.com <ga...@gmail.com> #506
Factory reset 4 times now.
This is not good Google. Switching to iPhone.
al...@gmail.com <al...@gmail.com> #507
fi...@gmail.com <fi...@gmail.com> #508
ck...@googlemail.com <ck...@googlemail.com> #509
ck...@googlemail.com <ck...@googlemail.com> #510
ad...@gmail.com <ad...@gmail.com> #511
ks...@gmail.com <ks...@gmail.com> #512
je...@gmail.com <je...@gmail.com> #513
we...@gmail.com <we...@gmail.com> #514
pj...@gmail.com <pj...@gmail.com> #515
successfully and then re-enabled, as I'm using a glass screen protector. All working fine now >>
Thanks for a good suggestion. Will try that.
My 2 XL and 3 XL phones had EXCELLENT fingerprint sensors on the back, which was convenient and fine. The 6 Pro (and 6a that I tried and returned for other reasons in addition to the fingerprint sensor) is driving me nuts. Tired of giving it the finger, with bad results.
pj...@gmail.com <pj...@gmail.com> #516
BTW THE ENROLLMENT PROCESS DOES NOT LIKE EITHER OF MY THUMBS. And these are the same 2 I was born with.
Grrrrrrr
rl...@gmail.com <rl...@gmail.com> #517
Love the phone.Hate the onscreen fingerprint reader. The 3a reader was miles better.
This has been going on for far too long with out a fix. Can we at least get a status update on this?
jo...@gmail.com <jo...@gmail.com> #518
I just ran into this sh*t on Android 13 QPR1 beta. The fingerprint doesn't enroll any more. This is ridiculus!
be...@gmail.com <be...@gmail.com> #519
pj...@gmail.com <pj...@gmail.com> #520
I've enrolled both index fingers, each two times, but STILL cannot enroll either thumb. It's VERY inconvenient to need to shift the phone each time to use an index finger instead of a thumb (as I've noted, the back sensor on the older models was much better).
PLEASE improve detection AND fix the thumb-thing. And on that topic, yes I know it's probably because of some detected "flaws" in my thumbprints, but Google should figure out how to take this into account.
They are still MY thumbs, and pretty unique at that.
js...@jfs-tech.com <js...@jfs-tech.com> #521
Thumbs are wider, maybe camera cannot read that far off? too many pixels?
js...@jfs-tech.com <js...@jfs-tech.com> #522
Thumbs do not have edges like fingers. At least not in a way they can be continuous with the central image if you twist on it's side. ( I am in the fat finger 10 percentile)
Thinking the algorithm needs to connect this image with the ones it took of the center area, I tried keeping the thumb almost flat and just shifting left and right.
I'd never use edge like that any way.
Description
- Device type: Pixel 6 Pro
- OS version: Android 12 (SD1A.210817.036) - Nov 5th Security Update
Probably wrong place to put this. For people with same issue please see:
Unable to enrol Fingerprint. All fingerprint profiles removed and now get error 'Enrolment was not complete. Fingerprint enrollment didn't work" after update to the latest Security Update. It's worth mentioning that a lot of the phones that have this issue were dead and charged up this morning (05/11/21)
Troubleshooting:
- Factory Reset
- Safe Mode
- Clearing Cache on Pixel Launcher, Settings and Settings Services.
- Changing Animator Scale in Developer Options
It's also worth mentioning that I have no screen protector and have cleaned screen also.
Please can this be looked into.