Hi, I bought a used Pixel 4, and when I tried to configure faceunlock I got a "Certificate has expired" error. To resolve the error, I tried to flash all versions of Android Os available for this device, including Beta 11. Can anyone know the solution to my problem?
I have the same problem. Anyone can help?
delete the face and add again
just don't use the face unlock for now, taking off your mask to unlock is not practical anyway.
I have the same error now. Any help?
abeninski said:
I have the same error now. Any help?
Click to expand...
Click to collapse
Hi there! Just wanna share some useful information about how to fix Face Unlock error on Pixel 4. Someday i noticed that Facecontrol just throw you an exception, like "face enrollment error" etc. And I also tried everything: hard reset, to flash an old android 10-11 builds - nothing helps. Then i started experimenting. So you need to uninstall updates from several Gaps (First 6 on screenshot): carrier services, motion sense bridge, adaptive connectivity service, device personalisation and device gealth service. Better to remove it one by one cheking Facecontrol become alive after every uninstallation. Not sure how these apps works, but removing patches from them solved this problem, at least in my personal case. The main thing is that your current OS build don't matter, for example my brother got this issue on android 10. If it'll cure your Pixel, make a backup of working build. Hope this post will be helpful
Related
I came off WP7 at the end of last week to try out some new Roms on Android. Before I had absolutely not trouble setting up my phone, I must have done it easy half dozen times in one day alone. over weekend I did a factory reset on my laptop so I downloaded the Windows Phone Development Tools and it installed without problem. I run through the setup as I had many times before, Chevron unlocked but when I tried to sideload the .xap tools needed it failed Toms and with Application Deployment I received this code:
"Receiving the COM class factory for component with CLSID {250BEABB-55E8-43BB-AC97-2D95674ECE14} failed due to the following error:
800 Class not registered (exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))."
I completely removed Windows Phone Development Tools, wiped not needed files, rebooted and reinstalled. I also reinstalled WP7 and tried from the beginning.
I am thinking that maybe Microsoft has put something in the Development tools which will prevent sideloading in WP7.
Is this an error on my part, any help appreciated.
That almost looks more like a .NET 4 error, try re-installing .NET 4 ...
Use the new custom roms. Auto unlocked.
The truth is.... THEY CAN'T STOP US. We represent too much of an investment that they simply can't afford to loose us and loose the DEV community who brings them more and more user and keep them alive!
don't know if this only happened to me,but suddenly my phone tells me for the twitter app that is has been revoked by Microsoft and that I should uninstall it.Did Microsoft somehow load kind of a new update on the phones through Zune? Or has it something to do with the upcoming Nodo?
Maxey said:
don't know if this only happened to me,but suddenly my phone tells me for the twitter app that is has been revoked by Microsoft and that I should uninstall it.Did Microsoft somehow load kind of a new update on the phones through Zune? Or has it something to do with the upcoming Nodo?
Click to expand...
Click to collapse
The phone re-locks every two weeks if I'm not mistaken. Even when it does, it lets you have 3 apps sideloaded.
Just re-unlock with Chevron and you should be good to go. keep in mind that every time you connect the phone to the computer it will re-lock itself.
I think putting in airplane mode solves the re-locking issue for the mean time, but the forums have a more robust method to prevent it from happening in a long-term way.
I've installed the latest version of Lineage OS on my 2013 nexus 7 (Flo), following all in the instruction including the wipes.
Lineage booted ok, but the set up wizard keep stopping when you click next after setting the language.
I have used he trick to enter the setting , then set up my wifi and google account, but this still does not work.
If seen some comments on the net abut needing 7.1.2 gapps , but there only appears to be version for 7.1 the minor version is not indicated.
The files i have used are
OS
lineage-14.1-20170919-nightly-flo-signed.zip
Gapps
open_gapps-arm-7.1-nano-20170923.zip
Any ideas where to go next ?
Many Thanks
tried a few more things.
If you delete the setupwizard.apk , then you get straight to the home screen, but you cant configure multiple users (probably other functions as well but only seen users)
If you try to use the stock (non nano) gapps there is no space in /system
fast running out of ideas
I also tried the the permissions on the phone and contacts but that did not work
I have a solution but will only work in my situation.
what did work was a completely fresh install of an older version of lineage
and installing micro gapps
The files i used were
lineage-14.1-20170801-nightly-flo-signed.zip
open_gapps-arm-7.1-micro-20170924.zip
the device is currently patching its self back to the latest version.
Not sure where the correct place to report is , and i cant prove its a regression issue
XDAdeveloperHTC said:
I've installed the latest version of Lineage OS on my 2013 nexus 7 (Flo), following all in the instruction including the wipes.
Lineage booted ok, but the set up wizard keep stopping when you click next after setting the language.
I have used he trick to enter the setting , then set up my wifi and google account, but this still does not work.
If seen some comments on the net abut needing 7.1.2 gapps , but there only appears to be version for 7.1 the minor version is not indicated.
The files i have used are
OS
lineage-14.1-20170919-nightly-flo-signed.zip
Gapps
open_gapps-arm-7.1-nano-20170923.zip
Any ideas where to go next ?
Many Thanks
Click to expand...
Click to collapse
I had the same problem, but I detected that this error is a problem with the day and time in my Nexus
I set the day and time manually ( I disabled the automatic date & time on android) and then I return to the wizard setup and I was able to continue with the installation without problem.
The files that I used:
lineage-14.1-20170919-nightly-flo-signed
open_gapps-arm-7.1-micro-20170922
The issues has apparently (not tested) been fixed as a regression issue with Lineage OS. there were also other people with the same issue.
Hi everyone,
I would have post this in the developer section, but I'm new, so I can't. I'm asking your help because of a problem that seems to hit some xiaomi devices: wifi and bluetooth at one point don't work anymore. Sometimes they decide to work again and after a while, again, the stop working. I tried to change ROMs, the problem seemed to be fixed, but after 1/2 day it comes back. In internet there are files for fixing this specific problem, often called "wifi_and_bt_fix" and you can find them for almost all Xiaomi models. The one I need, having a Redmi 3, is the "ido" one (I can't post link, neither, being knew. But if you want I can post a link to the file I'm talking about).
You have to flash it in EDL mode. But when i try to flash it, all MIflash versions i used, kept giving me the error "0x8000ffff max buffer sector is 32". When i try a newer version of Miflash, the error changes: "index out of the limits of the array". I already tried all version of miflash, on windows 10 and windows 7. I really don't know what to try anymore.
Anybody knows what to do? If the file it's incorrect? o how to solve the main problem with wifi and bluetooth?
(sorry for my english, I'm italian)
Pardon me, don't worry about your English, it's not that bad, at least I'm still understand about your main issue
Btw, could you give us more details about:
1. The type of your phone (I assume IDO, but better to make it sure 1st).
2. The firmware used on your phone, the version of it too.
3. How do you change ROM? Have you perform clean install by deleting the system partition 1st?
From details nb.2 and 3, we could localize if the problem come from software or hardware instead (hopefully).
Hi,
This last days I have stranges things with my phone, and it is the first time that happened.
When I reboot after install magisk modules or adaway file host, my phone cannot be unlocked.
I type the pin code for unlock my sim card, and after the pin code for unlock the phone.
At this moment I have a black screen and I must retype my code ever and ever.
Nothing to do, just reinstall all the rom. Unable to use a clean backup, this is the same problem.
If anybody knows this issue and can save my life, you're welcome.
Thanks a lot, cordialement
I found the issue.
I can install magisk and reboot normally.
But when I install modules everything is locked.
If anyone have infos?
Lethalben said:
I found the issue.
I can install magisk and reboot normally.
But when I install modules everything is locked.
If anyone have infos?
Click to expand...
Click to collapse
Hello, I am updating my mom's phone and saw your post.
Unfortunately that bug has been around for a few months, I have a quick temporary fix for you but unfortunately the bug will return, if you can live without a screen lock that may be you only solution for now.
Lock Screen ( delete the lock)
Boot to Recovery
Go to Recovery File Manager
Navigate to the /data/system folder
locate and delete the file called : locksettings.db
Now you no longer have a screen lock and you can easily get into the phone.
FYI : If you want the lock again , simply create a new key or pattern
This issue could be anything such as corrupted permissions, It seems that it pops up after installing audio mods and substratum. But I don't think it is caused by either one.
If your phone gets hot while experiencing this issue flash the thermalfix 7 file, located on the thermals thread https://forum.xda-developers.com/showpost.php?p=78717015&postcount=18
This morning I've formated my phone to be sure is not an error from me. I will try your solution if it happens again.
Thanks for your response my friend!
Is it possible f2fs formating data partition is the issue?
Lethalben said:
Is it possible f2fs formating data partition is the issue?
Click to expand...
Click to collapse
It's very likely that this is the origin of the problem. It happens to me too, and have F2FS formated data too.
Forsaken75 said:
It's very likely that this is the origin of the problem. It happens to me too, and have F2FS formated data too.
Click to expand...
Click to collapse
I'm go back to ext4 and everything is OK.
I saw a magisk module who's made for stop this issue.
If there is a magisk module for that I think the problem is f2fs!
Lethalben said:
Is it possible f2fs formating data partition is the issue?
Click to expand...
Click to collapse
I don't think so because I only use Ext4
Well, I think I finally found the true origin of this problem: Magisk Hide interferes with newer Webview implementations, as explained here:
https://www.didgeridoohan.com/magisk/MagiskIssues#
I also found several workarounds:
1) Disable Magisk Hide. I need some banking apps, so for me this is not an option.
2) Use Chrome Beta and select its engine as default Webview in Developer Options. Chrome Beta signature is not buggy, so it works as it should. This is the solution that I've chosen, by the way.
3) Ask our developers @codeworks @mosimchah and the others if they could include this commit that fixes invalid signatures in their future releases:
https://github.com/LineageOS/android_vendor_cm/commit/a3a76f5d1cc233ad8024ffdc74bb3a786e1605c3
Hi all:
Have you managed to solve the screen lock problem? I did not achieve it and I followed all the instructions you mentioned.
A greeting.
txiscoman said:
Hi all:
Have you managed to solve the screen lock problem? I did not achieve it and I followed all the instructions you mentioned.
A greeting.
Click to expand...
Click to collapse
It's some app compatibility issue with Android Pie/Webview for sure. In my case was my banking app, changing to Chrome beta fixed the problem (app still crashes from time to time, but I'm not having the damned screen lock problem anymore)
You can try using Webview component alone from Play Store (I notice that in my case it's working too) or do some research to find out which app is causing the issue and uninstall it (if you can live without it, of course)
Deleted
Hello,
i still did not find any direct solution for sound output dilemma, but i think i found a less elegant way by downloading an sound-output/input App, i dont know the english word exactly.
therefore the system (.... I guess in the Kernel? or in the Stock Android? or something like this... ) has wrong settings.
I had to switch output to speaker permantly, works ok for most of the time.
And the problem described is just a symptom, whether it is zdroid or lingeage, does not matter!
system ist not stabil! Sometimes it is, and then the apps close by thereself or system is rebooting without any reason or apps freeze etc. pp. ...
I do have just 8-15 apps, you know. You can exclude all those things you can search here or through google easily, i did this for a week, ok.
So i just needed a os which is very stable and very easy (performance first) and an hint from you all regarding the main cause (see above)?
For example i followed the advice of an user here, by installing stock android, i did, works, and the gapps/flashing os bei twrp (new version). done done...
what is the f** problem? I am so frustrated ,because i did these procedere maybe 6 times with other data / os(roms), you know?
So i need clear information about this cause.
And beyond that the device id is n/a or unknown if i boot my system. This device is not blabla... You know this screen?
(Problem Lineage + zdroid, does not matter) ...
Also the warnings ( i think google trust) <--- registering Google ID works through google.de website, but did not solve it (+ freezing system --> i flashed the best stable versions out there!!!)
Can you advice me, thanks Sir