Related
Enrolled in the google beta program but I'm not getting the ota for my pixel 2. It's been 72 hours. I got the ota for my pixel c within minutes. Anyone know how to force the ota or something?
It appears that people on the November security patch for 8.0 are not getting the 8.1 beta OTA pushed to them. Most likely need to wait for DP2 at this point.
Hopefully the preview 2 comes out soon.
I just signed up a few minutes ago, refreshed the system update screen on my pixel 2, and the update popped right up
flakmunkey said:
I just signed up a few minutes ago, refreshed the system update screen on my pixel 2, and the update popped right up
Click to expand...
Click to collapse
You were on November security patch?
gm007 said:
You were on November security patch?
Click to expand...
Click to collapse
Did the novembver security patch require any weirdness to get? I only ask because while i'm not sure if I had that installed, I do know for sure I had all of the most current OTA updates. I got the phone from Best Buy last Thursday and there was a software update when I first booted it. I check for new software this morning and it told me I was up to date. I then proceeded to sign up for the beta program, refreshed the update page that said I was up to date, and the 8.1 update was waiting for me
flakmunkey said:
Did the novembver security patch require any weirdness to get? I only ask because while i'm not sure if I had that installed, I do know for sure I had all of the most current OTA updates. I got the phone from Best Buy last Thursday and there was a software update when I first booted it. I check for new software this morning and it told me I was up to date. I then proceeded to sign up for the beta program, refreshed the update page that said I was up to date, and the 8.1 update was waiting for me
Click to expand...
Click to collapse
Some people didn't get November update and i read somewhere that they pulled the 8.1 preview for pixel 2 , that's why I'm asking.
http://www.androidpolice.com/2017/1...android-8-1-developer-preview-factory-images/
flakmunkey said:
I just signed up a few minutes ago, refreshed the system update screen on my pixel 2, and the update popped right up
Click to expand...
Click to collapse
Well I'm 4 days in and still no ota ?
Sent from my Google Pixel 2 using XDA Labs
mrnovanova said:
Well I'm 4 days in and still no ota ?
Sent from my Google Pixel 2 using XDA Labs
Click to expand...
Click to collapse
If it makes you feel any better I am in the same situation. 4 days no OTA. I am on the November Security patch.
Is it worth it to try flashing factory images to get back to September and then try to get the beta OTA?
I can confirm rolling back to September images does allow you to immediately get the prompt to download the 8.1 beta.
If you are impatient like me, it's worth a shot.
I will add this: Make sure your ADB and Fastboot are up to date! I ended up softbricked/stuck in the bootloader for awhile after flashing back to the September images. I finally figured out my old version fastboot was the problem. After getting the latest fastboot/adb it was a breeze.
I have a Pixel 2 with the bluetooth connection issues. When I go look for the Google Security Updates, it says that I am up-to-date. I did a factory reset and tried to get the update afterwards, but it has the same issue where it is not finding the update.
Has anyone successfully been able to find a way to get the phone to find the updates, or should I get a hold of Google to return the phone?
Thanks,
Mark
I have also not received the November security update, every time I check it says it is up to date. I bought the unlocked version from the Google Store and am using Verizon.
This reddit thread shows a way to potentially force it, i have not tried it yet -- https://www.reddit.com/r/GooglePixe..._on_september_security_patch_regular_pixel_2/
UPDATE: I have tried it, and it did not work
I also tried it and it didn't work. I would be more patient, but the Bluetooth issue is quite frustrating. I'll give it a few more days then will contact Google again for a replacement device.
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
thesebastian said:
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
Click to expand...
Click to collapse
Are the ones marked Verizon for the Verizon version, or also for people who bought the unlocked version and are using Verizon? My current version is OPD1.170816.010, which is not a Verizon version, so I guess I would want OPD1.170816.025 since the version I currently have is not the Verizon version? Still find it crazy that an update would come this late, never got them this late on my 5X. I never understood the point of if I manually check I cant just auto get the OTA (I know there was that article somewhat recently that they are moving to that though).
I got 023 over the air automatically on my Pixel 2. Haven't downloaded the OTA from the developer site some I got this phone.
OPD3.170816.023, Nov 2017, Verizon
I too bought unlocked from Google but using on Verizon. I was on .10 and waited weeks after release for a push, but it never came. So I manually flashed the .25 update. No issues, working perfectly, with the Nov security update.
I am still on september security update. Got a Pixel 2 (Verizon). Hope they hurry up. Its almost december
Sorry to bring up an old thread, but I have the same problem ever since I cleared the Google Play Services' data through the app's interface. The OTAs just stopped coming. I have been flashing full OTA images since August, but it is getting really annoying. I still didn't get the November's patch, nor the December's one. It always says my system is up to date. I didn't try clearing the Play Services Framework's data, as it isn't effective and only causes trouble. I tried clearing the Play Services' data though many times, but it doesn't help.
I am rooted with Magisk. Everything else is fully stock (rom, kernel, recovery) and I do pass the Safety Net test.
If anyone has a solution to this problem, please share it with the world. I don't believe that I am the only one with this problem.
Same here, rooted pixel 2, currently away from pc so would love to update from phone
Sent from my Pixel 2 using Tapatalk
I've had the same problem with my P2XL for the last couple of month. I have just been downloading the full updated firmware and flashing from my computer, but it would be nice to be able to update while travelling with no computer.
Details:
-Magisk rooted, everything else stock, including recovery.
-Google edition - I used to get updates, not sure what changed.
-Not on beta. I even tried signing up and then unsubscribing. No help.
-"Check for update" button does nothing.
-Clearing data on Google Services Framework doesn't help.
-I'm in Mexico on Telcel, but updates have worked in the past.
Haven't been receiving OTA updates since flashing the Pie factory image in August.
Device is stock apart from being rooted with Magisk.
Update button always says system is up to date, so I eventually sideloaded the latest OTA image at the end of November but still didn't receive any update notification in December.
I'm starting to suspect the update manager in Pie is detecting root or something, because I used to receive updates just fine on Oreo, and everyone else who has this problem also seems to be rooted.
hi,
yesterday I received a ota update.
new security patch level is 1 feb 2019
the update size was only 310MB.
nothing has changed
but I think optical image stabilisation is added for camera, and some minor camera changes.
mind you, this is not android one update.
my phone is A750FN
its a security patch with some fixes for front cam
Hmm, nothing here (Germany). Newest patch is the one from December
i recived that like 4 days ago, the 9.0 Pie update will come somewhere around April
Nothing here Brazil 1 November Patch Android 8.0 SM-A750G
PicoBS said:
Hmm, nothing here (Germany). Newest patch is the one from December
Click to expand...
Click to collapse
The same with me. And I had to put back a backup, because I got a problem with Magisk. So I will not install this December update.
(I rather would like to see some form of Lineage on our phone, to get rid of all kinds of apps I do not want to install on my phone.)
JoostA said:
The same with me. And I had to put back a backup, because I got a problem with Magisk. So I will not install this December update.
(I rather would like to see some form of Lineage on our phone, to get rid of all kinds of apps I do not want to install on my phone.)
Click to expand...
Click to collapse
There is AOSP if you want clean android
In Slovakia (Europe) there is no update till now. I have the newest from November.
android pie beta programm ended just yesterday in India so official one ui might be less than a week away atleast in india.
PicoBS said:
Hmm, nothing here (Germany). Newest patch is the one from December
Click to expand...
Click to collapse
Hi, I thought you were right. But actually there *is* a new 1 feb update that I already put on my phone. The phone will not recceive it ota, but you can install it using ODIN. Sammobile.com is a good source. I downloaded the Dutch version from there (I had another good source to check for the correct file) Sammobile is horrifyingly slow though.... You will need a couple of hours to download. And in fact it took me several hours too to get my phone back in order.
My A7 stuck on Samsung logo screen after updating to Android 9 Pie, any fix ?
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Displax said:
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
Thanks it works great
Displax said:
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
I still cannot get it to work. Installed, but I still get the error about cannot enroll.
Mine was working before I downgraded from DP3 back to Android 10.
AwkwardUberHero said:
I still cannot get it to work. Installed, but I still get the error about cannot enroll.
Mine was working before I downgraded from DP3 back to Android 10.
Click to expand...
Click to collapse
it seems like this is another related problem, but has a different reason.
This is in known issues: https://developer.android.com/preview/release-notes#user-facing_issues
Displax said:
it seems like this is another related problem, but has a different reason.
This is in known issues: https://developer.android.com/preview/release-notes#user-facing_issues
Click to expand...
Click to collapse
Thank you so much for the link to this!
I reported it as an issue right after I saw it, but had not heard back.
I appreciate you linking me.
This fixed my problem with face unlock. Thanks so much ?
What does this do exactly? My wife's face unlock works but she has a constant notification to re-enroll. I told her if she did that it most likely wouldn't work unless she factory resets. Honestly the notification being there annoys me more than her but she refuses to factory reset. I would just try it and see if it was my phone but I'll be sleeping in the backyard if I screw hers up for any length of time....lol
Worked perfectly on my phone! Spreading the word! Thanks for the module!
https://twitter.com/kingbri_aahs/status/1258148276513189888
Displax said:
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
Hey man thanks, I tried it. It didn't work for me. I wish you nothing but the best of luck with this fix bro. It's really needed. I miss my camera lol
Displax said:
it seems like this is another related problem, but has a different reason.
This is in known issues: https://developer.android.com/preview/release-notes#user-facing_issues
Click to expand...
Click to collapse
Anyone know if this will be fixed or are we stuck using 11 previews and betas if we want face unlock? I sent my pixel in under warranty like a lot of people suggested. Just got an update “device not repaired no issues found”.
This worked for me, Pixel 4 not XL
On may factory image
Thanks
TechOut said:
Anyone know if this will be fixed or are we stuck using 11 previews and betas if we want face unlock? I sent my pixel in under warranty like a lot of people suggested. Just got an update “device not repaired no issues found”.
Click to expand...
Click to collapse
i fixed this problem coming from android 11 by flashing january factory image .... works perfect again..... your welcome
It's working for me aswell on May version. Could you explain where Is the problem? What does this module?
tmoore3496 said:
i fixed this problem coming from android 11 by flashing january factory image .... works perfect again..... your welcome
Click to expand...
Click to collapse
So you are still on January update till know ?
I did the same here and worked but when i tried to update normally with OTA, the problem come back to me again
So I'm using January update and refusing update my phone for this reason
Okay there seems to be a lot of confusion from people in this thread so while I am not the OP I will try to clear things up.
Some people are having face unlock issues that can first be observed when setting the device up after flashing April and/or May images. During set up, it will say something along the lines of "Could not enroll face ID" or "Hardware not available" if dirty flashing one of the updates.
Some of us are having this issue even if we never upgraded to the Android R Developer Preview 3 or 4.
Others of us are having the issue after trying the DP 3/4 then rolling back to Android 10, April or May update.
The last monthly update that did not have Face Unlock issues for any of the above affected is March.
This module is created to help fix that and get Face Unlock working again and it is a Magisk Module that requires root to install.
However, a small few are still having issues even after trying this module (from my understanding).
You do not need this module if your face unlock works on April/May updates because this seems to be a kernel related issue that only affect some for a weird reason that I am too lazy to research right now. I'm sure this will be updated in the coming months.
So if you're Face Unlock doesn't work on April or May update, try this module. If it still doesn't work, you can use the March update and Face Unlock will work. There are no feature changes between now and March update. The March update include the auto dark mode, and the other feature drops from that month. Both April and May are only security patches and very minor fixes. While it is not the latest security patch you still have all the latest features.
Awesome!
Worked perfect on my pixel 4 xl. Flashed dev preview and got the enrollment error. Thanks for your module! working like a charm on May update
fuadtaufiq said:
So you are still on January update till know ?
I did the same here and worked but when i tried to update normally with OTA, the problem come back to me again
So I'm using January update and refusing update my phone for this reason
Click to expand...
Click to collapse
yeah April, May update breaks it, but magisk module fixes it. Temporary fix until Google fixes it.
anyone tried this on Jun update...
i will try, no need to wait
will report back...
---------- Post added at 04:14 PM ---------- Previous post was at 04:03 PM ----------
Adnansaeedhamed said:
anyone tried this on Jun update...
i will try, no need to wait
will report back...
Click to expand...
Click to collapse
i can confirm this working perfectly with me in Jun update
Hi! This happened to me today:
I installed the Android 11 Public Beta 1 today from June Android 10 version. I have an unlocked 4 XL. I flashed (trough fastboot) the June update and my facial recognition got broken. I did factory reset it but nothing was fixing it. I went back to Android 11 Public Beta 1 and it worked. Then I downloaded and flashed January Android 10 version and it is working right now. Will update if after setting it up and updating it to last update will still work.
basically what this does is patches sepolicy and adds the files required for face unlock. If you run a dmesg when trying to enroll there is something blocking the process from finding the files(likely sepolicy)
Hi, i have a Pixel 7 pro (no carrier, eu, stock, locked bootloader) and am experiencing the following:
until yesterday i was running:
security update: november
play system update: october
os: october
i tried with the pixel repair tool to no avail. so, yesterday i applied for the beta... installed, rebooted (many times) and... still stuck with the stable from october. i then downloaded the official ota and applied it... now i have
security update: december
play system update: october
os: december
now, why the play system won't update? also, the privacy and security settings are still separated... for what is worth, the free VPN has already been active for a few days.
is my OS broken? should i try with sideloading the update again? i'm not in the mood for a reset and i have many apps (banking too) which would be a hassle to config again.
ujh said:
Hi, i have a Pixel 7 pro (no carrier, eu, stock, locked bootloader) and am experiencing the following:
until yesterday i was running:
security update: november
play system update: october
os: october
i tried with the pixel repair tool to no avail. so, yesterday i applied for the beta... installed, rebooted (many times) and... still stuck with the stable from october. i then downloaded the official ota and applied it... now i have
security update: december
play system update: october
os: december
now, why the play system won't update? also, the privacy and security settings are still separated... for what is worth, the free VPN has already been active for a few days.
is my OS broken? should i try with sideloading the update again? i'm not in the mood for a reset and i have many apps (banking too) which would be a hassle to config again.
Click to expand...
Click to collapse
I updated yesterday to Dec.Release, I I'm with this. To be honest, don't know if is as expected
well, fair enough... it may be a slow rollout of single features...? -.-
ujh said:
Hi, i have a Pixel 7 pro (no carrier, eu, stock, locked bootloader) and am experiencing the following:
until yesterday i was running:
security update: november
play system update: october
os: october
i tried with the pixel repair tool to no avail. so, yesterday i applied for the beta... installed, rebooted (many times) and... still stuck with the stable from october. i then downloaded the official ota and applied it... now i have
security update: december
play system update: october
os: december
now, why the play system won't update? also, the privacy and security settings are still separated... for what is worth, the free VPN has already been active for a few days.
is my OS broken? should i try with sideloading the update again? i'm not in the mood for a reset and i have many apps (banking too) which would be a hassle to config again.
Click to expand...
Click to collapse
Android Pixel updates get rolled out in phases, meaning it's not available for everyone at the same time. Maybe you need to wait an hour, maybe a day, maybe a week.
If you feel the need to immediately update at the earliest time possible, you should look into ADB flashing.
Morgrain said:
Android Pixel updates get rolled out in phases, meaning it's not available for everyone at the same time. Maybe you need to wait an hour, maybe a day, maybe a week.
If you feel the need to immediately update at the earliest time possible, you should look into ADB flashing.
Click to expand...
Click to collapse
That's true... But about the settings tabs not yet unified?
ujh said:
That's true... But about the settings tabs not yet unified?
Click to expand...
Click to collapse
I updated to december and also have not gotten that "feature", it's likely that it's a google sided switch/ App update that is necessary to change that, meaning it's not at all necessary to update the firmware of the phone factually, but Google still wants the "feature drop" as a sales argument, hence the big focus on the firmware updates, even though the actual features could easily be delivered as in-app updates.
yeah... i read somewhere else that that "feature" and others will be available with an upcoming update within this month... lol
ujh said:
That's true... But about the settings tabs not yet unified?
Click to expand...
Click to collapse
I think that's part of the PermissionController APK, which is part of the PermissionController Mainline module. So I think Google needs to update that Mainline module before we get it.
However, you should be able to toggle the flag on with this adb command...
adb shell cmd device_config put privacy safety_center_is_enabled true