Fingerprint sensor refreshes Chrome

[cash 10]

When holding my phone in certain positions, my hand rests against the fingerprint reader. When using Chrome, this constantly refreshes the page. I cannot find where this can be disabled.

[EskeRahn 5,421]

Not that it is an actual fix, but is a functional workaround: If you use a shell (or flip) case, the chance of accidentally triggering the fingerprint reader is practically eliminated.
(There is a loooong thread on (primarily) DIY cases here, a short summary is that any soft case fitting the Huawei P20 Pro, is likely to be a good base for a Pro1(X) case. I also made my own thread here.

[cash 10]

17 hours ago, EskeRahn said:

Not that it is an actual fix, but is a functional workaround: If you use a shell (or flip) case, the chance of accidentally triggering the fingerprint reader is practically eliminated.
(There is a loooong thread on (primarily) DIY cases here, a short summary is that any soft case fitting the Huawei P20 Pro, is likely to be a good base for a Pro1(X) case. I also made my own thread here.

Thanks. I've seen a few of your posts floating around. I did intend on getting some kind of case, although the phone was supposed to come with something in the box.

I cannot be the only one who holds their phone in this way and constantly activates the fingerprint sensor. I may end up having to disable it, if that's even possible.

[EskeRahn 5,421]

13 minutes ago, cash said:

Thanks. I've seen a few of your posts floating around. I did intend on getting some kind of case, although the phone was supposed to come with something in the box.

I cannot be the only one who holds their phone in this way and constantly activates the fingerprint sensor. I may end up having to disable it, if that's even possible.

Indeed. I struggled with the Pro1 initially, especially holding it in portrait in the left hand (for operating with the right), But as I almost immediately started using shells, and then flip-cases, the problem disappeared.
But without a case it is as aPple would put it: "You are holding it wrong" *LOL* It will simply take a while to getting used to a grip avoiding inadvertently touching the fingerprint-reader.

I'm pretty sure that if you delete all you fingerprints (Setting►Security►Fingerprint) it will effectively be disabled.

The slick design where the fingerprint-reader is almost entirely level with the rest, looks cool, but makes it more prone to inadvertently touches...

[Hook 2,940]

5 hours ago, cash said:

I may end up having to disable it, if that's even possible.

First thing I did on my Pro1 in 2019 😄

[Benni 183]

I'm using https://f-droid.org/en/packages/com.davidshewitt.admincontrol/ to disable fingerprint unlock - apps can still use it though.

[Name_not_avail 64]

12 hours ago, EskeRahn said:

I'm pretty sure that if you delete all you fingerprints (Setting►Security►Fingerprint) it will effectively be disabled.

I tried this.  I never even stored a fingerprint, but tried it anyway.  Fingerprint comes up under "Device Security", but then it demands "Choose your backup screen lock method".  Three options:  Fingerprint + Pattern, Fingerprint + PIN, and Fingerprint + Password.

There is no choice to disable the fingerprint sensor entirely.

The problem seems to affect all scrolling apps.  MiXplorer does the same thing when viewing the file list.

I'm about one step away from rooting and using ADB to get the Package Manager to disable anything "fingerprinty" at boot.  Think I'll try Benni's solution first.  

This phone is BIG.  The keyboard alone is as thick as my dying Blackberry Priv. A case would make it ridiculously fat.

[Name_not_avail 64]

No joy with Benni's suggestion.  Seemed to minimize the issue a bit in Chrome, but it's still there.  No reduction of the problem at all in MiXplorer.

I did get rid of that annoying camera shutter button with the Button Mapper app, though, so there's progress!  I hit the damn thing every time I open the keyboard.  Too bad Button Mapper doesn't control the fingerprint sensor.

[smammy 11]

We're experiencing this too! For what it's worth, Firefox is not affected.

Does anyone know why this happens? We don't particularly want to disable the fingerprint sensor.

[Name_not_avail 64]

Confirmed, Firefox is not affected for me either.  Thanks smammy.  

That's a good work-around for the browser, but clearly there is coding in multiple apps that will be affected (cf. MiXplorer).

[EskeRahn 5,421]

If you install "KeyEvent" you can see the reader generates a 135 / 470, maybe you can map that away similar to the camerabutton 27 / 212 ?

[smammy 11]

@EskeRahnwhich app is KeyEvent, exactly? There are a few in the play store that are named like that:

• "KeyEvent Display" (aws.apps.keyeventdisplay)
• "Key Event" (com.key_event.mobile)
• "keyEvents" (com.keybps.keyevents)

A direct link would be great. Thanks!

[VaZso 1,997]

1 hour ago, smammy said:

"KeyEvent Display" (aws.apps.keyeventdisplay)

This one (at least that is what I used).

[matf-kabouik 414]

This is a known issue that was fixed in a later update, that you should get by OTA soon, or through the testing program when they open it to all bravehearted users.

Edited August 14, 2022 by matf

[jangorecki 0]

Was it actually fixed? On pro1x we have the same issue.

[Casey 316]

2 minutes ago, jangorecki said:

Was it actually fixed? On pro1x we have the same issue.

Yes, this is fixed. You can find the firmware in the beta testing group: