[GUIDE] Enable Fingerprint Selfie in Redmi 3S Prime

Search This thread

FrenzyR

Senior Member
Aug 20, 2014
385
528
chennai
i tried this on Redmi note 4 mido snapdragon AOSPextn rom not working
i have attached Generic.kl with screenshot
 

Attachments

  • Screenshot_20170926-125400.jpg
    Screenshot_20170926-125400.jpg
    277 KB · Views: 249
  • Generic.zip
    3.3 KB · Views: 7

Ajendra25

Senior Member
Oct 15, 2016
282
129
Vadodara
I've tried on my Redmi Note 3 Kenzo.. NOS 7.1.2 ROM
Here's a SS of KeyEvent.. Plz tell me it's supported or not??
 

Attachments

  • Screenshot_20171003-205732.jpg
    Screenshot_20171003-205732.jpg
    272.6 KB · Views: 114

31fahmi

Senior Member
Aug 12, 2013
197
12
South Tangerang
It's working with SnapCam and all others... only footej is not supported.

Again run that command and give me KeyEven Display app's screenshot. (See in 2nd post)

Here again
I think it's caused by different mFlags value, it's possible to change it?
 

Attachments

  • Screenshot_20171009-185614.jpg
    Screenshot_20171009-185614.jpg
    75.3 KB · Views: 65
  • Screenshot_20171009-185640.png
    Screenshot_20171009-185640.png
    79.1 KB · Views: 63

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    Here is a tweak for enabling "Fingerprint Selfie".

    Warning :
    This guide includes some steps which will modify system behavior. I'm not responsible for any consequences. Do it in your own risk. Take Nandroid Backup Before trying this. :p

    Prerequisites :
    1. Redmi 3S Prime with unlocked bootloader (You can also use Redmi 3S if it has fingerprint sensor :D)
    2. Rooted ROM
    3. Good File Explorer to Browse Root Files. I recommend ES File Explorer.
    4. Good Text Editor Which can edit root files. Try QuickEdit for this.

    How-to :
    1. Goto /system/usr/keylayout folder
    2. Find a file called Generic.kl
    3. Open Generic.kl with text editor (QuickEdit)
    4. Search for key 353
    5. If you find any line starts with key 353, comment it with # i.e. add # symbol before that line
    6. Add a new line with following
    Code:
    key 353 CAMERA
    Note: You can add this line anywhere in that file but its advised to follow the file structure. i.e. key numbers is in ascending order... just follow it add 353 after 352.
    7. Save the file and Reboot.
    8. Enjoy Fingerprint Selfie... :fingers-crossed:

    Explanation :
    Some users may experienced unwanted clicks or touches in screen when they touch fingerprint sensor while the phone is unlocked. That was caused by "key 353 DPAD_CENTER" line in Generic.kl. Here we used that for assigning that key for CAMERA (which will trigger the camera and take picture).

    WhatsApp Group : https://chat.whatsapp.com/EnJsSukWafaLuD9cMg6NYn
    Telegram : Devil7DK

    Note : I'm tested this in Redmi 3S Prime 3GB with Lineage ROM and its working perfectly without any problem.
    1
    Troubleshooting :
    For those who are reporting that This Tweak is Not Working. Try this....

    1. Install KeyEvent Display App
    2. Open it & Give Root Permission
    3. Then Touch Fingerprint Sensor. You should see something like this,
    GpmKEWs.png


    Code:
    ^*KeyDown:******action=0 code=27 repeat=0 meta=0 scancode=353 mFlags=8 label='' chars='null' number='' 
    ^*KeyUp:********action=1 code=27 repeat=0 meta=0 scancode=353 mFlags=8 label='' chars='null' number=''

    4. If it shows something like this when touching fingerprint sensor... it means your fingerprint sensor is working as button. So, Make sure the scancode is 353.
    5. If there is something Else i.e. any other number... use that number instead of 353.

    If you cant see anything when touching the fingerprint sensor. Then it means this won't work at all for you.:p
    1
    What to do now next. @dineshthangavel47

    Your fp is working well as button... So just follow the guide... Even it didn't work.. sent me the Generic.kl file edited by you.... In WhatsApp or telegram...
    1
    Update : For those Who reported that this trick is not working on XXXX ROM... I found the fix.