I had a Verizon Pixel XL on which the fingerprint reader failed after the Oreo update. It would just say it could not enroll my fingerprint and to try again, but never worked. A factory reset did not help. So I RMA'd the device and the new one I was sent has Nougat on it. Fingerprint reader is working fine, but now I hesitate to update to Oreo.
So I'm wondering if this is a widespread problem or just something weird that happened to the phone I sent back. Since it's the Verizon Pixel, there's no way for me to downgrade back to Nougat if I have the same problem with Oreo again.
Update to Oreo. It'll be fine.
Edit.. although on second thought I might just stick with N. O is not doing that well in the battery life department.
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
Update to Oreo. It'll be fine.
Edit.. although on second thought I might just stick with N. O is not doing that well in the battery life department.
Click to expand...
Click to collapse
Do you have the Verizon Pixel? I guess my question is: Are there people with the Verizon Pixel who have updated to Oreo and the fingerprint reader is working. Or is it breaking the fingerprint reader on all (or many) of the Verizon Pixels?
cb474 said:
I had a Verizon Pixel XL on which the fingerprint reader failed after the Oreo update. It would just say it could not enroll my fingerprint and to try again, but never worked. A factory reset did not help. So I RMA'd the device and the new one I was sent has Nougat on it. Fingerprint reader is working fine, but now I hesitate to update to Oreo.
So I'm wondering if this is a widespread problem or just something weird that happened to the phone I sent back. Since it's the Verizon Pixel, there's no way for me to downgrade back to Nougat if I have the same problem with Oreo again.
Click to expand...
Click to collapse
I'd say go ahead and update as this does not appear to be a widespread issue. Worst case scenario you can downgrade back to Nougat.
bobby janow said:
Update to Oreo. It'll be fine.
Edit.. although on second thought I might just stick with N. O is not doing that well in the battery life department.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've actually noticed improved battery life on O compared to N.
mlin said:
I'd say go ahead and update as this does not appear to be a widespread issue. Worst case scenario you can downgrade back to Nougat.
Click to expand...
Click to collapse
How do I downgrade on a Verizon Pixel? Without an unlocked bootloader I thought I don't really have control over those things?
cb474 said:
How do I downgrade on a Verizon Pixel? Without an unlocked bootloader I thought I don't really have control over those things?
Click to expand...
Click to collapse
Sorry, I missed that point. Can only roll back if your bootloader is unlocked. Sorry for the confusion.
mlin said:
Sorry, I missed that point. Can only roll back if your bootloader is unlocked. Sorry for the confusion.
Click to expand...
Click to collapse
Okay. Yeah, that's why I want to be sure about Oreo and the fingerprint reader, before I do the update, because there's no going back on the Verizon Pixel.
cb474 said:
Okay. Yeah, that's why I want to be sure about Oreo and the fingerprint reader, before I do the update, because there's no going back on the Verizon Pixel.
Click to expand...
Click to collapse
The logical answer is that it can't be widespread. If it was then this thread would have hundreds of reports of this happening and the Oreo update would have to be pulled. So a mere Google search even would show a lot of hits. No such thing other than a very few reports. A friend of mine had the same thing happen on his 5x and the solution was to clear the cache in recovery. That was long ago so I'm not sure if that's even still possible but perhaps worth looking into. Nonetheless, I wouldn't worry about it if you want O. Happens again, return it again.
I recently got the Oreo update on my Google Pixel XL and shortly after my fingerprint reader also stopped working.
It doesn't even recognize the hardware is there, no Pixel Imprint option in security & location menu. Factory reset was no help.
Google is sending me a replacement.
thekenster said:
I recently got the Oreo update on my Google Pixel XL and shortly after my fingerprint reader also stopped working.
It doesn't even recognize the hardware is there, no Pixel Imprint option in security & location menu. Factory reset was no help.
Google is sending me a replacement.
Click to expand...
Click to collapse
Did you clear cache in recovery?
Sent from my Pixel using XDA-Developers Legacy app
I have a Verizon pixel XL and I am running official Oreo on my device, however, I have my bootloader unlocked and flashed it manually via adb. I can confirm my fingerprint scanner is working perfectly.
Pixel XL 128GB from Google Store here
Updated via OTA to Oreo, and the fingerprint scanner still works fine to unlock the device.
HOWEVER, it seems to be much more strict when it comes to authentication in Apps such as banking apps, credit monitoring apps, etc. It's annoying because it will temporarily disable the fingerprint login for the entire phone after a small number of failed attempts EVEN if I lock the screen, and unlock with fingerprint in the middle of trying to login to the app with the same finger positioning...
bobby janow said:
The logical answer is that it can't be widespread. If it was then this thread would have hundreds of reports of this happening and the Oreo update would have to be pulled. So a mere Google search even would show a lot of hits. No such thing other than a very few reports. A friend of mine had the same thing happen on his 5x and the solution was to clear the cache in recovery. That was long ago so I'm not sure if that's even still possible but perhaps worth looking into. Nonetheless, I wouldn't worry about it if you want O. Happens again, return it again.
Click to expand...
Click to collapse
Yes I already thought of all that and did all of that. But when you do a search on the Pixel and try to find posts that only have to do with the Verizon Pixel, it's not so simple. Mostly people are talking about the Google Store Pixel or just don't indicate which phone they're talking about. So I posted my question just to double check. I especially wanted to hear that people on the Verizon Pixel XL are not having problems with Oreo and the fingerprint reader, so that I would know that it is working okay in some instances, at least, and can conclude it's not a problem particular to Oreo.
thekenster said:
I recently got the Oreo update on my Google Pixel XL and shortly after my fingerprint reader also stopped working.
It doesn't even recognize the hardware is there, no Pixel Imprint option in security & location menu. Factory reset was no help.
Google is sending me a replacement.
Click to expand...
Click to collapse
That's a little different from the phone that I returned. It recongized the hardware. It just never worked to enroll a fingerprint.
bobby janow said:
Did you clear cache in recovery?
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I don't see an option to clear cache in recovery on the Google Pixel XL. Am I missing something?
thekenster said:
I don't see an option to clear cache in recovery on the Google Pixel XL. Am I missing something?
Click to expand...
Click to collapse
Yes, you're right. It's no longer there I just checked. Sorry about that. Used to be and that did it back then.
Related
Does anyone here have a chromebook they use with their Oneplus 3?
I got a chromebook recently and can't pair the OP3 to the chromebook, and as a result can't use Smart Lock to unlock the chromebook by unlocking the phone. Am I doing something wrong or is the chromebook or the phone the issue?
I have an Acer Chromebook 14 and smart unlock works as expected. Is Bluetooth on for both your chromebook and OP3?
Anova's Origin said:
I have an Acer Chromebook 14 and smart unlock works as expected. Is Bluetooth on for both your chromebook and OP3?
Click to expand...
Click to collapse
Are you on stock OOS?
I can set my car and PC BT as trusted devices in Smart Lock. BUT not Nexus 7 & 9 and Pixel C tablets!! - neither can I set any of them as trusted devices with each other. There are inconclusive "internet" threads about it. I think it may be Google being "economical with the truth" and hoping this issue will go away in time.
peterk-1 said:
I can set my car and PC BT as trusted devices in Smart Lock. BUT not Nexus 7 & 9 and Pixel C tablets!! - neither can I set any of them as trusted devices with each other. There are inconclusive "internet" threads about it. I think it may be Google being "economical with the truth" and hoping this issue will go away in time.
Click to expand...
Click to collapse
that's interesting, but I'm referring to unlocking the chromebook, using my oneplus 3 as the "trusted device" so to speak.
my OP3 also works fine to unlock itself using my car's BT as trusted device.
2x4 said:
that's interesting, but I'm referring to unlocking the chromebook, using my oneplus 3 as the "trusted device" so to speak.
my OP3 also works fine to unlock itself using my car's BT as trusted device.
Click to expand...
Click to collapse
Sorry - I missed the point in my explanation. I should have made clear the "trusting" doesn't work in either direction. In the case of attempting to set up any device to unlock a Pixel C, the Pixel C menu Smart Lock > Trusted devices doesn't open to BT / NFC options but instead gives an "error" message " Trusted devices feature is not available to use". This has been the case with Android M and N so it has been suggested that this is a hardware restriction. The relevance? - Pixel C started life designed as a Chrome device. Another suggestion is that there is a coding error and GPS has been included as a requirement - I doubt this since trusted locations works.
2x4 said:
Are you on stock OOS?
Click to expand...
Click to collapse
Yes, stock OOS 4.1.0, rooted with Magisk and on Franco's r14.
Is Bluetooth on for both your phone and chromebook? Maybe try re-pairing them.
Anova's Origin said:
Yes, stock OOS 4.1.0, rooted with Magisk and on Franco's r14.
Is Bluetooth on for both your phone and chromebook? Maybe try re-pairing them.
Click to expand...
Click to collapse
i'm on the freedom OS OB with magisk and stock kernel. is it my chromebook that's having the issue perhaps? I've tried unpairing and re-pairing on both, the chromebook says it can't connect to my phone
2x4 said:
i'm on the freedom OS OB with magisk and stock kernel. is it my chromebook that's having the issue perhaps? I've tried unpairing and re-pairing on both, the chromebook says it can't connect to my phone
Click to expand...
Click to collapse
Is your chromebook up to date in terms of Chrome OS updates? If you could pair them before but not now, maybe try powerwashing your chromebook.
Anova's Origin said:
Is your chromebook up to date in terms of Chrome OS updates? If you could pair them before but not now, maybe try powerwashing your chromebook.
Click to expand...
Click to collapse
i only got it a few days ago, it's the samsung chromebook plus. It paired before but smart lock never worked once, even when i hit the try now button after setting it up. I've jumped on the beta channel since then and still not able to get it to work.
Anova's Origin said:
Is your chromebook up to date in terms of Chrome OS updates? If you could pair them before but not now, maybe try powerwashing your chromebook.
Click to expand...
Click to collapse
yes it is up to date
2x4 said:
i only got it a few days ago, it's the samsung chromebook plus. It paired before but smart lock never worked once, even when i hit the try now button after setting it up. I've jumped on the beta channel since then and still not able to get it to work.
Click to expand...
Click to collapse
I had this exact issue with my chromebook plus and my oneplus 3 while on oos. It worked fine up until maybe two or three weeks ago on oos.
It started working for me when I un greenified the Google app. It could be also I switched to resurrection remix.not sure which fixed the issue >__<
Cool to know somebody else is rocking the oneplus 3 and the chromebook plus!
MrWilsonxD said:
I had this exact issue with my chromebook plus and my oneplus 3 while on oos. It worked fine up until maybe two or three weeks ago on oos.
It started working for me when I un greenified the Google app. It could be also I switched to resurrection remix.not sure which fixed the issue >__<
Cool to know somebody else is rocking the oneplus 3 and the chromebook plus!
Click to expand...
Click to collapse
Thanks for the input! I just wanted to make sure it wasn't the Samsung Chromebook Plus. Hopefully it gets fixed with the OnePlus 3 at some point
2x4 said:
Thanks for the input! I just wanted to make sure it wasn't the Samsung Chromebook Plus. Hopefully it gets fixed with the OnePlus 3 at some point
Click to expand...
Click to collapse
My pleasure. I doubt it's a problem with the CBP. Probably something to do with oxygen OS unfortunately.
added a new user to the chromebook today, and enabled smartlock with her phone (Nexus 6P) with zero issues - it's definitely the Oneplus 3.
i'm current on freedomOS community beta version. not sure what the issue is...
I had the exact same issue weeks ago, I'm unsure what the fix was because I had a whole lot going in between finding the fix for it, I powerwashed the Chromebook and reinstalled the ROM I used (with a clean wipe, of course). It's either of those that fixed it for me.
F4uzan said:
I had the exact same issue weeks ago, I'm unsure what the fix was because I had a whole lot going in between finding the fix for it, I powerwashed the Chromebook and reinstalled the ROM I used (with a clean wipe, of course). It's either of those that fixed it for me.
Click to expand...
Click to collapse
im doing a clean flash now - what ROM are/were you on if you don't mind me asking?
and when you clean flashed, did you use Google's "restore a backup" during setup?
2x4 said:
im doing a clean flash now - what ROM are/were you on if you don't mind me asking?
and when you clean flashed, did you use Google's "restore a backup" during setup?
Click to expand...
Click to collapse
For the ROM, it's a custom-built AOSP ROM, but I also jumped to LineageOS 14.1 for a short while (and it also works there as well)
No, I use the other option that don't require me to restore things.
F4uzan said:
For the ROM, it's a custom-built AOSP ROM, but I also jumped to LineageOS 14.1 for a short while (and it also works there as well)
No, I use the other option that don't require me to restore things.
Click to expand...
Click to collapse
tried a clean flash of the ROM I'm currently on (FreedomOS based on OOS beta), and the issue still persists.
I'd be open to using another ROM but haven't ever had a reason to switch and I like the optimal camera performance with OOS
just tried a clean flash of lineage OS (https://forum.xda-developers.com/oneplus-3/development/rom-t3532088) - smart lock STILL didn't work (I keep getting the "can't find your phone" error message)
what specific ROM(s) did you see it work on @F4uzan ?
Still on May update, never upgraded to June because of this issue. Does the July update fix it?
beezar said:
Still on May update, never upgraded to June because of this issue. Does the July update fix it?
Click to expand...
Click to collapse
Yes it does. Feels good to have it back
Feels back to normal...
beezar said:
Still on May update, never upgraded to June because of this issue. Does the July update fix it?
Click to expand...
Click to collapse
BTW this wasn't an issue, it was intentional from Google.
Sent from my Pixel 2 XL using XDA Labs
Has anyone pulled the update by manually clicking "Check for Updates"? I have hit it multiple times throughout the day as recently as 15 minutes ago and still saying I'm up to date on June. Is this busted again?
jrg67 said:
Has anyone pulled the update by manually clicking "Check for Updates"? I have hit it multiple times throughout the day as recently as 15 minutes ago and still saying I'm up to date on June. Is this busted again?
Click to expand...
Click to collapse
As soon as I clicked it, then I received the 54.7 MB OTA.
galaxys said:
As soon as I clicked it, then I received the 54.7 MB OTA.
Click to expand...
Click to collapse
I just looked around some more online and found others complaining of the same thing. Perhaps it's working for some but definitely not all. Just hit it again, still nothing.
Hate to hijack the thread, but this is as good a place as any to ask this really simple question of mine:
How do I update to the latest July patch if I'm still on stock May, but rooted with Magisk & Xposed enabled? I'm assuming I can just flash the full factory image zip with fastboot (disabling -w to avoid wipe) and just making sure to remove Magisk/Xposed before hand.
Latiken said:
Hate to hijack the thread, but this is as good a place as any to ask this really simple question of mine:
How do I update to the latest July patch if I'm still on stock May, but rooted with Magisk & Xposed enabled? I'm assuming I can just flash the full factory image zip with fastboot (disabling -w to avoid wipe) and just making sure to remove Magisk/Xposed before hand.
Click to expand...
Click to collapse
Yeah you can for sure do that when you flash the factory image it will remove magisk and xposed for u.
mac796 said:
Yeah you can for sure do that when you flash the factory image it will remove magisk and xposed for u.
Click to expand...
Click to collapse
Thank you for the confirmation. I assumed it would do that, but I'll probably do it myself to make sure nothing goes wrong in the flashing process.
Still slow after July update.
Sent from my [device_name] using XDA-Developers Legacy app
jrg67 said:
Has anyone pulled the update by manually clicking "Check for Updates"? I have hit it multiple times throughout the day as recently as 15 minutes ago and still saying I'm up to date on June. Is this busted again?
Click to expand...
Click to collapse
My work pixel 2 got the OTA yesterday. My pixel 2 xl still not seeing it.
Travisdroidx2 said:
My work pixel 2 got the OTA yesterday. My pixel 2 xl still not seeing it.
Click to expand...
Click to collapse
I tried to report the issue to google chat support but those people are useless outside of processing RMAs. 2 different reps told me the update isn't out yet bc it's dated the 5th and had no idea hitting the check for updates button overrides the staged rollout. Ugh.. I reported the issue on the pixel community board so let's see if that gets any traction.
jrg67 said:
I just looked around some more online and found others complaining of the same thing. Perhaps it's working for some but definitely not all. Just hit it again, still nothing.
Click to expand...
Click to collapse
I side loaded it using ADB. For some reason, it takes several days for the update to get to me in June (when prior updates worked after running "check for update").
I think delay is still present in july build as confimred by some users, so i will stay with May Build till now(waiting for fix).
I am still waiting for the July updates....
still haven't recieved July security update OTA for my Pixel 2 XL.
FPSRocketeer said:
still haven't recieved July security update OTA for my Pixel 2 XL.
Click to expand...
Click to collapse
Same.
For me June's OTA showed up instantly, but also still waiting for July security update.....
Sent from my Pixel 2 XL using XDA-Developers Legacy app
grgana said:
For me June's OTA showed up instantly, but also still waiting for July security update.....
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Exactly the same here, thats so odd.. I wonder what is the cause of this, cuz some people got it pretty much instantly when Google released the update.
So I have been having issues with my Note 10+ ever since I've upgraded to Android 10. Did pretty much everything from a reset to a factory reset and delete amd still having issues with smartlock. I have it set to a few devices like my work van, earbuds ,beats and home. I keep getting asked to unlock it when hooked up to any of the devices or at home. Also I've tried to update and delete each one but it still is not working. Even I have ticked when on body.
Wondering if anyone has had same or similar issues with Smartlock?
Sent from my SM-N975U1 using Tapatalk
Yes!! I thought maybe it was something I had done myself. I have mine set the same as you, buds, UE Megaboom3, work and home and it asks me about 90% of the time to unlock using fingerprint or pin when connected or at these locations...very frustrating. Used to work flawlessly before Android10. I thought it was because I was using Nova launcher but haven't tested stock launcher.
Sent from my SM-N975U using Tapatalk
ianmb said:
Yes!! I thought maybe it was something I had done myself. I have mine set the same as you, buds, UE Megaboom3, work and home and it asks me about 90% of the time to unlock using fingerprint or pin when connected or at these locations...very frustrating. Used to work flawlessly before Android10. I thought it was because I was using Nova launcher but haven't tested stock launcher.
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
Great to know! So I am. NOt going crazy!?! Lol... wondering if there will be an update or fix?
Sent from my SM-N975U1 using Tapatalk
Jiannu said:
Great to know! So I am. NOt going crazy!?! Lol... wondering if there will be an update or fix?
Sent from my SM-N975U1 using Tapatalk
Click to expand...
Click to collapse
I hope so, I'm tired of having to enter my pin when I'm at home every time I want to use my phone.
Sent from my SM-N975U using Tapatalk
ianmb said:
I hope so, I'm tired of having to enter my pin when I'm at home every time I want to use my phone.
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
Seems like alot of the features and the phone got $#@# up with android 10.
Sent from my SM-N975U1 using Tapatalk
Jiannu said:
Seems like alot of the features and the phone got $#@# up with android 10.
Sent from my SM-N975U1 using Tapatalk
Click to expand...
Click to collapse
Yeah, some good some bad.
Sent from my SM-N975U using Tapatalk
i have an unlocked phone bought from Australia and smartlock works just fine for me.
i have 3 - 4 devices added as Trusted and i never have to enter the password while connected to them via BT.
Jiannu said:
So I have been having issues with my Note 10+ ever since I've upgraded to Android 10. Did pretty much everything from a reset to a factory reset and delete amd still having issues with smartlock. I have it set to a few devices like my work van, earbuds ,beats and home. I keep getting asked to unlock it when hooked up to any of the devices or at home. Also I've tried to update and delete each one but it still is not working. Even I have ticked when on body.
Wondering if anyone has had same or similar issues with Smartlock?
Click to expand...
Click to collapse
I have a N975F Note 10 +,
Android 10 , February security patch.
Stock, no root etc.
Since i had my Note 10 +, from last year, August /October 2019
never had issues with Smart lock.
Presently, i have 8 devices registered with Smart lock.
I had found in general, my Gear S3 watch,
just works perfectly 99 % of time..!
Most of the time I forget that i have a lockscreen.... enabled...!
I have found that on body and location
most of the time have issues.
willcor said:
I have a N975F Note 10 +,
Android 10 , February security patch.
Stock, no root etc.
Since i had my Note 10 +, from last year, August /October 2019
never had issues with Smart lock.
Presently, i have 8 devices registered with Smart lock.
I had found in general, my Gear S3 watch,
just works perfectly 99 % of time..!
Most of the time I forget that i have a lockscreen.... enabled...!
I have found that on body and location
most of the time have issues.
Click to expand...
Click to collapse
What's the difference in models as I have the SM-N975U1 ?
Sent from my SM-N975U1 using Tapatalk
Jiannu said:
What's the difference in models as I have the SM-N975U1 ?
Click to expand...
Click to collapse
The SM-N975F is the international version, Europe etc...
Exynos, 1 x Sim and 1 xsd card. etc
I'm not sure to sure with the SM-N975U1
but i think its......
Snapdragon, Dual sim..?
USA unlock version etc
same here
I have the same issue on sm-n976v i also have noticed that if you have good lock with lockstar activated it also seems to mess with smartlock but i used to turn it off and would start working and now it just doesnt work at all.
Jiannu said:
So I have been having issues with my Note 10+ ever since I've upgraded to Android 10. Did pretty much everything from a reset to a factory reset and delete amd still having issues with smartlock. I have it set to a few devices like my work van, earbuds ,beats and home. I keep getting asked to unlock it when hooked up to any of the devices or at home. Also I've tried to update and delete each one but it still is not working. Even I have ticked when on body.
Wondering if anyone has had same or similar issues with Smartlock?
Sent from my SM-N975U1 using Tapatalk
Click to expand...
Click to collapse
Hej...
Same issue on my phone... I was thinking then is something wrong with mine device but like I see in not only my problem...
Jiannu said:
So I have been having issues with my Note 10+ ever since I've upgraded to Android 10. Did pretty much everything from a reset to a factory reset and delete amd still having issues with smartlock. I have it set to a few devices like my work van, earbuds ,beats and home. I keep getting asked to unlock it when hooked up to any of the devices or at home. Also I've tried to update and delete each one but it still is not working. Even I have ticked when on body.
Wondering if anyone has had same or similar issues with Smartlock?
Sent from my SM-N975U1 using Tapatalk
Click to expand...
Click to collapse
Yep, same exact issue, nothing in smart Lock works for me. Not trusted devices or trusted places. It's just useless. I have resorted to using bixby routines to keep the phone unlocked in trusted places and it seems to work way better than trusted places ever did. But the trusted devices thing is still irritating.
Edit: Just wanted to add this is on numerous Note 10 pluses (always want to try out different. Colors and special editions, lol) and ever since installing the first beta version of Android 10.
chetly968 said:
Yep, same exact issue, nothing in smart Lock works for me. Not trusted devices or trusted places. It's just useless. I have resorted to using bixby routines to keep the phone unlocked in trusted places and it seems to work way better than trusted places ever did. But the trusted devices thing is still irritating.
Edit: Just wanted to add this is on numerous Note 10 pluses (always want to try out different. Colors and special editions, lol) and ever since installing the first beta version of Android 10.
Click to expand...
Click to collapse
Yes I already came to that conclusion shortly after installing Android 10 official. Hopefully there will be a patch or fix soon
Sent from my SM-N975U1 using Tapatalk
Mine is fine when connected to my TicWatch or JBL headphones but NEVER works with location-based SmartLock. Never has, even on Android 9. Set address and GPS location, nothing works for location for me but never an issue with BT connected devices.
elogikal said:
Mine is fine when connected to my TicWatch or JBL headphones but NEVER works with location-based SmartLock. Never has, even on Android 9. Set address and GPS location, nothing works for location for me but never an issue with BT connected devices.
Click to expand...
Click to collapse
On Android 9 smart Lock worked better than it did on any of my pixel phones which was refreshing. Location and device both worked flawlessly. But not any more unfortunately.
Is there anything I can do with this tablet since its FRP locked? I've tried the recommendations here for 8.1 but that must not be whats on the system. I can't get past the opening screens and now I can't get talkback settings to work after I disabled explore by touch, any ideas?
twgib said:
Is there anything I can do with this tablet since its FRP locked? I've tried the recommendations here for 8.1 but that must not be whats on the system. I can't get past the opening screens and now I can't get talkback settings to work after I disabled explore by touch, any ideas?
Click to expand...
Click to collapse
Might be 7.0, sure you could find frp bypasses for that
Sent from my Pixel 4 using Tapatalk
Turns out it was on Android 7, 7.1 I thought but I used a service on eBay that unlocked it for me. Bit of a strange experience speaking to a really rude russian guy but its working!
twgib said:
Turns out it was on Android 7, 7.1 I thought but I used a service on eBay that unlocked it for me. Bit of a strange experience speaking to a really rude russian guy but its working!
Click to expand...
Click to collapse
Hell yeah! Well done
Sent from my Pixel 4 using Tapatalk
Hello, I need some advise please as I am unable to get Call Screen to work on my Pixel 6 Pro. Ironically it is working on my old 3 XL lol.
When I go into the settings for Call Screen it says to download a language update then says update isn't ready. Screenshot attached.
Any Ideas please?
Can't advise but having same problem so curious to see if anyone comes up with a fix!
Sorry I don't have anything helpful to add other than that it is working for me.
What version of the phone app do you have?
pahardie said:
What version of the phone app do you have?
Click to expand...
Click to collapse
Mine is using Version 71.0.404685116-publicbeta-pixel2021 on the Pixel 6 Pro and 71.0.404685116-publicbeta on the 3 XL
Prototypeuk said:
Mine is using Version 71.0.404685116-publicbeta-pixel2021 on the Pixel 6 Pro and 71.0.404685116-publicbeta on the 3 XL
Click to expand...
Click to collapse
Thanks I have the same! My pixel 5 has the same version and same warning so least I know it's not a pixel 6 thing
pahardie said:
Thanks I have the same! My pixel 5 has the same version and same warning so least I know it's not a pixel 6 thing
Click to expand...
Click to collapse
Ah ok so I wonder what it is then?
pahardie said:
Thanks I have the same! My pixel 5 has the same version and same warning so least I know it's not a pixel 6 thing
Click to expand...
Click to collapse
Are you outside of the US? Perhaps something like that?
TonikJDK said:
Are you outside of the US? Perhaps something like that?
Click to expand...
Click to collapse
Yes I am outside the US. I'm in the UK however it does work on my Pixel 3 XL and I know they have announced it was coming to the UK so I don't believe location is the issue. Where abouts are you located?
Australia here. Same issue. No fix to report though.
Having the same issues with mine and my wipes P6P and P6 ... It's a bummer because I know other people in Australia have it working fine.
It's working on my Pixel 6 Pro in the UK. It did say it needed to download a language pack but calling my number shows call screen and it works.
The error on mine disappeared this morning randomly - I didn't do anything. Can now see the voice options as well as the demo. Could only see demo yesterday with the error popping up wrt the download.
I can see the voice options today which were not there yesterday and when someone calls it shows call screen but it still doesn't work.
Does the transcript work ok on yours?
Called myself !
No it doesn't work. Press call screen it answers but then no transcript. Can't even hang up as buttons greyed out.
Actually tried it again and it worked ok.
First time defo didn't but each subsequent time working ok.
Bit weird.
It's working for me on Pixel 6 Pro. May be there's a setting somewhere that's messed up.
With this feature only just rolling out in the UK I think they're probably still enabling it etc at the server end. It'll likely just start working soon. Fingers crossed for everyone!
pahardie said:
With this feature only just rolling out in the UK I think they're probably still enabling it etc at the server end. It'll likely just start working soon. Fingers crossed for everyone!
Click to expand...
Click to collapse
Really bizarre it is still showing the same error but it is working at the moment lol.
Haha mine is showing the download message again now. But is working .
Oh well! Glad to hear yours is working now!