Assigned
Status Update
Comments
de...@gmail.com <de...@gmail.com> #2
Same issue, also logged a support request - Your Google Support Inquiry: Case ID [7-5646000031635]
cm...@google.com <cm...@google.com> #3
Same Issues as well. Logged it with them.
je...@google.com <je...@google.com> #4
Reattempted a factory reset which resolved the issue. Think the issue could relate to system/dalvik cache needed clearing when it did the update but arguably a factory reset shouldn't be a full term solution especially when another update could be released to resolve and when clearing system cache isn't provided in the bootloader other than via ADB/Fastboot tools which not every user is going to be comfortable doing and could result in further issues so shouldn't be a supported solution.
de...@gmail.com <de...@gmail.com> #5
So - If you lose battery again, is it going to happen again? Or you think Im good with just one factory reset?
bu...@gmail.com <bu...@gmail.com> #6
My advice would be to wait until I've tested it as I'm currently waiting for my battery to drain. I'm UK based and it's currently 1am so I should know more tomorrow
ha...@gmail.com <ha...@gmail.com> #7
Appreciate that. Good luck !
fr...@obiwo.com <fr...@obiwo.com> #8
Hi, I can confirm my fingerprint reader still works after the phone died
pc...@gmail.com <pc...@gmail.com> #9
I had the same issue occur last night where my Pixel 6 crashed and rebooted while still having 49% battery left. After the crash I am unable to use the fingerprint reader or register new fingerprints. This indicates that draining the battery might not be the cause of this problem.
am...@google.com <am...@google.com> #10
I don't think draining the battery causes it either, I reckon it's something to do with the security update which could apply after the phone's died and been recharged or after the phone has been restarted manually or via a crash. The crashing may actually be a separate issue altogether I haven't heard of any other phones crashing
pc...@gmail.com <pc...@gmail.com> #11
Confirming I'm experiencing this with the Pixel 6. I'm going to avoid the factory reset for now and hope there's a patch or it's resolved in the December update. I let the battery die last night, and when I turned on the phone this morning, all fingerprints were erased and I'm unable to enroll new ones.
am...@google.com <am...@google.com> #12
Same problem starting a couple days ago after my phone ran out of batteries. Only solution for me was to factory reset, which seems to have done the trick
ma...@gmail.com <ma...@gmail.com> #13
I've been going nuts trying to troubleshoot this. I have a on-call position and cannot just factory reset my phone on a whim....so I have been avoiding doing that since I am on call for the next 2 weeks. So glad to see this so I know that I am not going totally crazy!
su...@gmail.com <su...@gmail.com> #14
Same issue, though I have definitely not let the battery run down to zero. Just stopped working a few days ago.
yt...@gmail.com <yt...@gmail.com> #15
Same issue, happened after my battery died.
ni...@gmail.com <ni...@gmail.com> #16
Same issue. It seemed to start after the Nov 5th security update for me at least. Full battery drain and then not able to register a finger print having done it before.
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.
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.
w....@futuremind.com <w....@futuremind.com> #17
same issue here, and i don't want to factory reset ...
re...@gmail.com <re...@gmail.com> #18
exactly the same issue, my phone turned off after being low on battery, and since I can't enroll a new fingerprint or unlock my phone this way....
pc...@gmail.com <pc...@gmail.com> #19
I suffer the same problem. I have reported this problem to Android Authority and they wrote an article for this issue: https://www.androidauthority.com/google-pixel-6-fingerprint-3055692/
There is a reddit discussion as well:https://www.reddit.com/r/GooglePixel/comments/qmuxok/pixel_6_pro_fingerprint_scanner_not_working/
I hope that this issue can be fixed with a software update,
otherwise, it will be useless to buy a new Pixel.
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.
ay...@gmail.com <ay...@gmail.com> #20
Come on Google. This is the exact reason I hesitated to buy your phone. Have the guts to say we messed up, send this over to the owner teams and send a urgent hot fix update. If this doesn’t get resolved with an update by end of the year, I swear I am never buying or recommending a pixel for me or my family and friends again.
lb...@gmail.com <lb...@gmail.com> #21
Any updates on that?
jm...@x2studios.com <jm...@x2studios.com> #22
I have had this same problem since this morning last night I charged my phone to 93 percent from 11 percent so my battery was not dead I then unplugged the phone and switched off for the night but when I woke up this and turned my phone on the fingerprint sensor was gone tried many times to redo my prints but it's not letting me. Come on Google sort this out with a hot fix or patch I don't want to have to reset my phone
fe...@google.com <fe...@google.com>
ca...@gmail.com <ca...@gmail.com> #24
Same issue, Pixel 6. Surely there is a software fix that doesn't require a factory reset?
st...@gmail.com <st...@gmail.com> #25
Same issue as well on my pixel 6, has there been any word from Google as to a patch to fix the issue? I'd rather not factory reset.
ca...@gmail.com <ca...@gmail.com> #26
Not sure if anyone has suggested the fingerprint re-calibration tool.
https://pixelrepair.withgoogle.com/
sh...@navi.com <sh...@navi.com> #27
What is the long-term plan or solution for this from Google?
cm...@google.com <cm...@google.com> #28
deleted
cm...@google.com <cm...@google.com> #29
I have the same problem with my phone.
Just checked and in middle of downloading a new security update and new Google play system update. Hope this fixes issue with the fingerprint
Just checked and in middle of downloading a new security update and new Google play system update. Hope this fixes issue with the fingerprint
cm...@google.com <cm...@google.com>
lb...@gmail.com <lb...@gmail.com> #30
I have the same issue, successfully enrolled and used my fingerprint when I got the phone, then after it ran out of battery it erased all memory of my enrolment - now allows me to go through the full fingerprint set up before saying "enrolment failed try another finger"
yt...@gmail.com <yt...@gmail.com> #31
FYI this is on a Pixel 6 (not pro)
cm...@google.com <cm...@google.com> #32
deleted
st...@gmail.com <st...@gmail.com> #33
Same issue
de...@gmail.com <de...@gmail.com> #34
Yup same problem my phone died and as soon as I restarted it fingerprint was not working. Restarted it several times still isn't working.
pc...@gmail.com <pc...@gmail.com> #35
My Pixel 6 Pro 128 GB is affected. Can we expect a fix soon or should I factory reset? This is ridiculous.
de...@gmail.com <de...@gmail.com> #36
same here...Dont factory reset they must release a patch... Or each time we will reach 0% we will reset factory xD no way
But really its unbelievable that something like this problem can even exist its GOOGLE WTF
But really its unbelievable that something like this problem can even exist its GOOGLE WTF
ji...@gmail.com <ji...@gmail.com> #37
Hasn't happened since I've factory reset even when battery has gone flat but for anyone that does decide to factory reset, go into developer options and disable automatic updates. I'll test the update and let you know if it happens again. Realistically, they need to provide a better solution though. I reckon clearing the dalvik cache would resolve it but they don't provide an option to do that unless you use fastbootd/ADB so they just need to do that via an update
mi...@gmail.com <mi...@gmail.com> #38
Going on a week now, with no fingerprint unlock. To factory reset my phone is a pain, with so many work related apps already setup, authenticators, etc.
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.
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.
de...@hepsiburada.com <de...@hepsiburada.com> #39
Same issue. My Pixel 6 died last night and scanner hasn't worked since.
Your Google Support Enquiry: Case ID [5-5700000032117]
Your Google Support Enquiry: Case ID [5-5700000032117]
co...@gmail.com <co...@gmail.com> #40
Same issue, phone died an hour ago then fingerprint stopped working and i can't register new ones. I then found articles online about it and it's really disappointing. I refuse to factory reset, pls fix it google.
mo...@wandering-minds.eu <mo...@wandering-minds.eu> #41
Same issue for me after phone battery drained
de...@gmail.com <de...@gmail.com> #42
Same issue for me with a Pixel 6...
de...@gmail.com <de...@gmail.com> #43
Just here to report I have also experienced this
de...@gmail.com <de...@gmail.com> #44
Also experienced this issue
ca...@gmail.com <ca...@gmail.com> #45
Same here, really disappointing.
ph...@gmail.com <ph...@gmail.com> #46
Same here with a pixel 6; I've also had 2 spontaneous power offs and the bug may have to happened after the first of those
sh...@navi.com <sh...@navi.com> #47
If no update from Google within the next 24 hours, I'm returning for a full refund, as the replacement device Google has offered won't fix the underlying issue.
la...@gmail.com <la...@gmail.com> #48
Another interesting thing on my pixel 6. Besides for the fingerprint sensor no longer working: on the settings > security page it will sometimes show (green) as 'no problems found' but a few minutes later it shows in brown (red) that there is a security problem: that 'google play system update' needs to be updated. When searching it can't find a new update. Although somehow the 'last updated on' date reverted back to August 1.
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.
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.
tr...@gmail.com <tr...@gmail.com> #49
Same issue here in the Pixel 6 Pro after my battery fully deleted. I don't want to factory reset as I spend hours setting it up
sa...@meteoblue.com <sa...@meteoblue.com> #50
I guess I'm added to the list... A factory reset fixed my issue.. but still...
ro...@gmail.com <ro...@gmail.com> #51
Same issue...Case ID 9-7440000031310
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.
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.
ia...@gmail.com <ia...@gmail.com> #52
I have the same issue on a Pixel 2XL (with a physical reader)
de...@gmail.com <de...@gmail.com> #53
Comment has been deleted.
al...@immobiliare.it <al...@immobiliare.it> #54
Same issue except my phone got too hot and shut down. Battery at 47%. When I powered it back on fingerprint was gone and enrollment kept failing
lb...@gmail.com <lb...@gmail.com> #55
It is such a shame...
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.
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.
va...@aadhan.in <va...@aadhan.in> #56
It's more than a week and still they can't fix it not sure how many more days we need wait before they, release the fix
lb...@gmail.com <lb...@gmail.com> #57
This just happened to me. Phone booted due to letting the battery go flat and then it taking the Nov 5 update when i woke it up.
Later I'll see if I can wipe the cache with ADB and see if that works.
Later I'll see if I can wipe the cache with ADB and see if that works.
va...@aadhan.in <va...@aadhan.in> #58
Comments 4 and 37 mention wiping the Dalvik (system) cache but there is no such cache on these devices because seamless updates work differently.
So as yet I know of no workaround.
So as yet I know of no workaround.
lb...@gmail.com <lb...@gmail.com> #59
Same. Vzn P6pro 128gb. All updates are current
Description
From the Android Studio team:
This is a known issue of the AdMob and Google Services libraries
(AGP before 8.3 would have not surfaced the conflicts between the property definitions, which is why you see this during upgrade of AGP)
The solution suggested from the error message is the right one
Until the libraries are fixed: just override the property yourself in your
AndroidManifest.xml
Issue as reported below
DESCRIBE THE ISSUE IN DETAIL: I am not sure where can I report this issue as it seems it is more related to AdMob and Google Services manifest conflict. However this issue appears after updating to Iguana and AGP from
8.2.2
to8.3
and Gradle8.2
to8.4
.STEPS TO REPRODUCE:
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
ATTACH LOG FILES
IMPORTANT: Please readhttps://developer.android.com/studio/report-bugs.html carefully and supply
all required information.
Studio Build: Build #AI-232.10227.8.2321.11479570 Version of Gradle Plugin: 8.3 Version of Gradle: 8.4 Version of Java: 17 OS: macOS Ventura