• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[MODULE]Fix broken Face Unlock

Search This thread

adrianmich

Senior Member
Dec 25, 2014
214
64
20
Kissimmee
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.

Update: It was broken on the June update... Sad for that. Then I read a post and installed the June update for Telstra only (via OTA) and it is working for now and pretty well. Waiting for the normal update to come out and will install it via OTA through ADB.
 
  • Like
Reactions: JuanCarlosJacome
Nov 5, 2018
10
1
Google Pixel 4
Face unlock broken after rolling back from beta 1

Update: It was broken on the June update... Sad for that. Then I read a post and installed the June update for Telstra only (via OTA) and it is working for now and pretty well. Waiting for the normal update to come out and will install it via OTA through ADB.
Did you tried locking the bootloader before updating again?, is the Telstra factory image working well in Ecuador?
 

adrianmich

Senior Member
Dec 25, 2014
214
64
20
Kissimmee
Did you tried locking the bootloader before updating again?, is the Telstra factory image working well in Ecuador?
Yes. Updated with locked bootloader. Will try to update to "normal" June update with locked bootloader again just to make sure... I am not in Ecuador though. I am in the USA and it works perfectly with Sprint network. It should work in Ecuador too, I think.
 
Last edited:
  • Like
Reactions: JuanCarlosJacome
Nov 5, 2018
10
1
Google Pixel 4
Face unlock broken after rolling back from beta 1 fixed with June Telstra OTA

Yes. Updated with locked bootloader. Will try to update to "normal" June update with locked bootloader again just to make sure... I am not in Ecuador though. I am in the USA and it works perfectly with Sprint network. It should work in Ecuador too, I think.

I flashed the ota image this afternoon and it's been working well, sorry i got confused, on your comment said you were from Guayaquil; anyway, thank you very much for the fix!
 
Nov 5, 2018
10
1
Google Pixel 4
Did you install the Telstra version or the normal one? Yes! I am from Guayaquil but living in the US, gotta update that haha.
Well, congrats on leaving this sinking ship, the corruption in the government makes me want to leave myself. I installed the Telstra one, first tried with the normal January one and it worked, I could set up face unlock, tried updating from settings up to the June update, the face unlock kept working but tried deleting the face data and couldn't set it up again, it gave me some error about missing hardware; then I tried the Telstra OTA and it worked perfectly, thanks for the tip!
 

d414d4

Member
Aug 1, 2020
6
0
July update itself fix the problem officially

I am using an orange Pixel4 mobile phone. After upgrading to 11, I went back to 10. The face unlock function cannot be used normally. I used the Telstra version in June and it cannot solve this problem. In addition, I tried to use the January/March/April and the latest July ROM, but the problem could not be solved. Using April's ROM and using this Magisk module also could NOT solve this problem. Does anyone know the reason? (And my white and black version of Pixel4 could solve the problem of face unlock when using the June Telstra version or the July ROM) Thank you.
 

Balino

Senior Member
Mar 3, 2011
1,714
590
27
Gaeta
I am using an orange Pixel4 mobile phone. After upgrading to 11, I went back to 10. The face unlock function cannot be used normally. I used the Telstra version in June and it cannot solve this problem. In addition, I tried to use the January/March/April and the latest July ROM, but the problem could not be solved. Using April's ROM and using this Magisk module also could NOT solve this problem. Does anyone know the reason? (And my white and black version of Pixel4 could solve the problem of face unlock when using the June Telstra version or the July ROM) Thank you.
There was another problem with the face unlock not working but I don't remeber what triggered It. I think it's Better to contact Google assistance
 

sonypete

Member
Jun 17, 2010
25
0
I had face unlock issue where it would just not sense my face in the circle after going to the latest August update. This module instantly let my setup face unlock after doing multiple factory refreshes. Google has failed me with both the Pixel 1 and Pixel 3 XL and now this. This might be my last straw. What exactly does this module change?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    Magisk module to fix broken Face Unlock on April and May builds.

    https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
    4
    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.
    3
    Magisk module to fix broken Face Unlock on April and May builds.

    https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP

    Thanks it works great
    3
    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.
    2
    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


    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.