search

ayush5harma / PixelFeatureDrops

Magisk Module for Pixel Feature Drops that adds the system files for the same and spoof using the latest device fingerprint from Google Pixel .
MIT License
341 stars 16 forks source link

Face unlock switched to back cam | Awaken 1.3 | Poco F1 #16

Closed mecoromeo closed 3 years ago

mecoromeo commented 3 years ago

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

ayush5harma commented 3 years ago

Which ROM are you using ?

mecoromeo commented 3 years ago

Currently on Awaken 1.3 on a xiaomi poco F1

ayush5harma commented 3 years ago

Try this- https://github.com/ayush5harma/P4XLProps/issues/14 it might fix your issue if it is caused due to inbuilt gcam.

If not then only follow the following steps (which require edXposed): 1.Install module WeiJu and activate it in the edxposed manager.

  1. Enable showing system apps in it and add your face unlock to it.
  2. Choose edit variables to override the prop values set my this module with your device default. video for this - https://github.com/ayush5harma/P4XLProps/issues/10#issuecomment-701601857
mecoromeo commented 3 years ago

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)

mecoromeo commented 3 years ago

Tried both edxposed modules got stuck in loop. So both workarounds didn't work. Any other option? Thanks. If not that's fine

ayush5harma commented 3 years ago

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)

Are you on android 11 from where did you install edxposed from? If on android R install edxposed from here : https://ci.appveyor.com/project/ElderDrivers/edxposed/builds/36319004/artifacts

ayush5harma commented 3 years ago

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)

Did you debloat the built in gcam ?

mecoromeo commented 3 years ago

Yes A11 tried from magisk and then tried directly downloading from the latest from github and both didn't work

ayush5harma commented 3 years ago

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. Did you debloat the builtin gcam ? Debloat builtin gcam ,go to recovery to clear cache and dalvik , re-enroll face and check it that fixes

mecoromeo commented 3 years ago

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.

ayush5harma commented 3 years ago

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 (https://github.com/ElderDrivers/EdXposed/pull/623)

Debloat builtin gcam ,go to recovery to clear cache and dalvik , re-enroll face So this didn't work ?

mecoromeo commented 3 years ago

I'll try again using 21.3. thanks for helping.

mecoromeo commented 3 years ago

Screenshot_20201120-203356_Pixel_Launcher

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

ayush5harma commented 3 years ago

Screenshot_20201120-203356_Pixel_Launcher

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.

mecoromeo commented 3 years ago

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

mecoromeo commented 3 years ago

I think this may be the culprit

ro.face.moto_unlock_service.cam_id=5

ayush5harma commented 3 years ago

I think this may be the culprit

ro.face.moto_unlock_service.cam_id=5

Can you test this ? P4XLProps.zip

added prop values from device_xiaomi_sdm845-common should fix the hdr and motorola face unlock.

mecoromeo commented 3 years ago

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

ayush5harma commented 3 years ago

I think this may be the culprit

ro.face.moto_unlock_service.cam_id=5

Hi, sorry about that , can you try one more time ? P4XLProps-beryllium.zip

mecoromeo commented 3 years ago

Screenshot_20201121-020638_Pixel_Launcher Screenshot_20201121-020458_Pixel_Launcher Screenshot_20201121-020519_Pixel_Launcher Screenshot_20201121-020634_Pixel_Launcher

Tried flashing the new prop you gave and while I got in, the rear cam is still being used though

ayush5harma commented 3 years ago

Screenshot_20201121-020638_Pixel_Launcher Screenshot_20201121-020458_Pixel_Launcher Screenshot_20201121-020519_Pixel_Launcher Screenshot_20201121-020634_Pixel_Launcher

Tried flashing the new prop you gave and while I got in, the rear cam is still being used though

yes just added ro.face.moto_unlock_service.cam_id=5 as you and this commit https://github.com/FreakyOS-Devices/device_xiaomi_beryllium/commit/6f19705be931df28f0fd5dca59459b05cc97913e suggested. Can you sent your default build.prop at /system

mecoromeo commented 3 years ago

I uploaded the build.prop here

https://drive.google.com/folderview?id=13nalBR6Gh_25fCQm6SCdEhLV2NbN83Xb

ayush5harma commented 3 years ago

Check by adding the props related to camera there are 4 of them

ro.face.moto_unlock_service.cam_id=5 persist.vendor.camera.perfcapture=1 camera.disable_zsl_mode=true vendor.camera.aux.packagelist=org.codeaurora.snapcam,com.android.camera,org.lineageos.snap,com.motorola.faceunlock

save the edit reboot and check if the fixes though iam confused myself as

https://forum.xda-developers.com/nubia-z17/how-to/guide-enable-aux-camera-party-camera-t3846325/page2

the above thread suggest aux to be the second back camera module but it's there in build.prop so worth trying adding it.

mecoromeo commented 3 years ago

Ok us this right? ![Uploading Screenshot_20201121-024500_Pixel_Launcher.png…]()

mecoromeo commented 3 years ago

![Uploading Screenshot_20201121-024500_Pixel_Launcher.png…]()

mecoromeo commented 3 years ago

![Uploading Screenshot_20201121-025029_Pixel_Launcher.png…]() ![Uploading Screenshot_20201121-024500_Pixel_Launcher.png…]()

mecoromeo commented 3 years ago

Still didn't work.

mecoromeo commented 3 years ago

Should I add # (hash)?

ayush5harma commented 3 years ago

those screenshots aren't uploaded so idk what was sent but no hash will comment that line

mecoromeo commented 3 years ago

![Uploading Screenshot_20201121-024500_Pixel_Launcher.png…]()

ayush5harma commented 3 years ago

it's still the same uploading image You must have added it right bro maybe just try clearing the dalvik cache from recovery or something else need to done to fix it .If you use face unlock often remove the pixelprop module for the time being ..

mecoromeo commented 3 years ago

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 persist.vendor.camera.perfcapture=1 camera.disable_zsl_mode=true vendor.camera.aux.packagelist=org.codeaurora.snapcam,com.android.camera,org.lineageos.snap,com.motorola.faceunlock

mecoromeo commented 3 years ago

it's still the same uploading image You must have added it right bro maybe just try clearing the dalvik cache from recovery or something else need to done to fix it .If you use face unlock often remove the pixelprop module for the time being ..

Ok no problem. Thanks for the help

ayush5harma commented 3 years ago

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 persist.vendor.camera.perfcapture=1 camera.disable_zsl_mode=true vendor.camera.aux.packagelist=org.codeaurora.snapcam,com.android.camera,org.lineageos.snap,com.motorola.faceunlock

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 you can make a change directly to this file then save and reboot.

mecoromeo commented 3 years ago

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

ro.product.system.manufacturer=Xiaomi

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

mecoromeo commented 3 years ago

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

ayush5harma commented 3 years ago

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

ro.product.system.manufacturer=Xiaomi

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

No it won't enable the NGA as the google app reads all these values from the build.prop file to enable the NGA.

P4XLProps.zip (added device/xiaomi/sdm845-common values from your original build.prop hope doesn't end you up in bootloop and fix the face unlock )

mecoromeo commented 3 years ago

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