-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Face unlock switched to back cam | Awaken 1.3 | Poco F1 #16
Comments
Which ROM are you using ? |
Currently on Awaken 1.3 on a xiaomi poco F1 |
Try this- #14 If not then only follow the following steps (which require edXposed): |
I tried both steps. The first one, installed gcam from the link you sent and kept crashing (previously using the latest parrot gcam 7.6). I then tried edxposed and kept me stuck in bootloop (used sandhook). I'll try yahfa and keep you updated and see if it works. Thanks. Btw for pocof1 what should I edit (once i have weifu installed) and what to put. (Sorry beginner. Thank you) |
Tried both edxposed modules got stuck in loop. So both workarounds didn't work. Any other option? Thanks. If not that's fine |
Are you on android 11 from where did you install edxposed from? If on android R install edxposed from here |
Did you debloat the built in gcam ? |
Yes A11 tried from magisk and then tried directly downloading from the latest from github and both didn't work |
Yes both are meant for android Q .For android R you may use artifacts from the link above. |
I tried installing the artifacts above but it kept saying riru not installed, even though i have riru 22.0 already installed. I'll try working on that and check on that dev but i guess for now i will stick to not having face unlock. I've also tried talking with saikiran and reinz (dev and mainterner of the rom I'm using) and just waiting for their response and see if they can probably check on that for face unlock. |
regarding edxposed you need to use riru 21.3 (https://github.com/RikkaApps/Riru/releases/download/v21.3/magisk-riru-v21.3.zip) and not 22 .Ik these things are complicated .Edxposed for riru 22 is a work in progress Debloat builtin gcam ,go to recovery to clear cache and dalvik , re-enroll face So this didn't work ? |
I'll try again using 21.3. thanks for helping. |
Not sure if I did it correctly. But this is what I did. Also safety net is broken despite hiding everything in magisk hide even manager and hidden edxposed (from edxposed mañager) frok gms, and safetynet broken and phone became super slow and laggy. I'll close this case instead since its not worth having face unlock if the phone becomes unuseable |
Safetynet it tippled because of edxposed.Riru 22 has an hiding mechanism which is gonna help in safetynet pass, and edxposed for riru 22 is being worked out .Nevertheless removing edxposed from magisk will fix safetynet and it'll also remove the lag so don't worry simply remove the edxposed. It seems the motorola package cannot access the from camera setup when using the module. I'll take a look at the default build.props used in building your rom for beryllium and adding the missing flags to P4XLProps. |
Oh ok. Yeah I just saw that iraniroahn has the same issue. He actually has the same phone and rom (awaken 1.3) if I'm not mistaken. If you need anything else let me know. Thanks |
I think this may be the culprit ro.face.moto_unlock_service.cam_id=5 |
Can you test this ? added prop values from device_xiaomi_sdm845-common should fix the hdr and motorola face unlock. |
Hi. Tried flashing it but when I reboot i get stuck in the poco logo, won't proceed any further. I removed from and flashed on magisk again, this time i went to twrp first and cleared dalkiv and cache, still stuck in poco logo. Just wouldn't push beyond the poco logo |
Hi, sorry about that , can you try one more time ? |
yes just added ro.face.moto_unlock_service.cam_id=5 as you and this commit FreakyOS-Devices/device_xiaomi_beryllium@6f19705 suggested. |
I uploaded the build.prop here https://drive.google.com/folderview?id=13nalBR6Gh_25fCQm6SCdEhLV2NbN83Xb |
Check by adding the props related to camera there are 4 of them ro.face.moto_unlock_service.cam_id=5 save the edit reboot and check if the fixes though iam confused myself as the above thread suggest aux to be the second back camera module but it's there in build.prop so worth trying adding it. |
Still didn't work. |
Should I add # (hash)? |
those screenshots aren't uploaded so idk what was sent but no hash will comment that line |
Not sure why it's not uploading. My internet works fine though. Anyway i unzipped, then added it in the system.prop then zipped again. All works fine except face unlock still ro.face.moto_unlock_service.cam_id=5 |
You did't have to repack if the module is already flashed the system.prop file will be at /data/adb/modules/P4XLProps/system.prop |
I kept digging a bit and I'd like to ask if "ro.product.system.manufacturer=Google" is necessary for NGA? Because The reason I flashed the prop is to get NGA. Now, as I said I kept digging and found a different prop By Elon Musk, and found that his prop doesn't break face unlock and as noted in his git page that it's only for widevine L1 and not NGA. Long story short, I checked his prop and found that he did this: #ro.product.system.manufacturer=Google I tried it (although his redfin prop was only for september so safetynet fails since my rom is november patch) and it is spoofing as pixel 5 and it didn't break face unlock but aside from safetynet it didn't give me NGA. Do you think this could work? Or is that manufacturer line necessary for NGA? Thanks |
I'm not sure though if I have to make all "ro.product.system.manufacturer=Google" line as a comment and add "ro.product.system.manufacturer=Xiaomi" line below each google manufacturer line |
No it won't enable the NGA as the google app reads all these values from the build.prop file to enable the NGA.
|
The last commented prop didn't work too. No worries though, I'll keep using the prop, I can live without face unlock for now. The pixel prop has more benefits for me than face unlock. Thanks |
I'm not sure what happened, but when I initially installed the prop face unlock worked fine. For some reason it switched to using my back camera. Help pls
The text was updated successfully, but these errors were encountered: