rlpowell 1 Posted May 25 Share Posted May 25 Just got mine a little while ago, still getting used to it. Installed SwiftKey to fix the lack of auto-complete with the keyboard, which was my first major complaint. Now my biggest problem, by far, is the fingerprint sensor, because it keeps "detecting" any part of my hand coming anywhere near it, and ... I'm honestly not sure exactly what's happening at the software level, but unless I keep my *entire hand* *very* far away from it, anything involving input is basically unusable. This is with the physical keyboard closed, just using it in portrait mode like a normal phone. The soft keyboard will disappear every time it registers me touching the sensor, no matter what app I'm in. If I'm in Chrome, it will *reload the page* every time I brush the sensor even a tiny bit. Stuff like that. It's like it's responding to a brush on the sensor in a similar way to me sleeping and re-awakening the phone. I actually *want* to use the fingerprint sensor, even though I really don't like the location (years of BB KeyOne/Key2), but if I can't *grip my phone* and still use it because of this thing, I'm going to have to put tape over it or something. Quote Link to post Share on other sites
PoongZY 13 Posted May 25 Share Posted May 25 They should just do it under screen or at the back. Side finger print reader always at problem for me. Quote Link to post Share on other sites
Name_not_avail 55 Posted May 26 Share Posted May 26 Notorious problem in stock 2.1.2, then fixed in GMS-less 2.1.5, and for some reason LOS developers are not using that updated vendor blob for the current versions of LOS. Does anyone have a way to communicate this issue to the LOS devs? Seems like it should be a relatively easy fix, to just use the 2.1.5 stuff for LOS. Quote Link to post Share on other sites
rlpowell 1 Posted May 26 Author Share Posted May 26 What's LOS? 1 Quote Link to post Share on other sites
rlpowell 1 Posted May 27 Author Share Posted May 27 I'm on Android, though; shouldn't I have the firmware update? Quote Link to post Share on other sites
rlpowell 1 Posted May 27 Author Share Posted May 27 Also sometimes, for hours at a time, the fingerprint sensor just ... does nothing. ;_; Quote Link to post Share on other sites
Rob. S. 1,500 Posted May 27 Share Posted May 27 3 hours ago, rlpowell said: I'm on Android, though; shouldn't I have the firmware update? It's not official yet. I'm still on on the original Android, too. I don´t use one of the browsers which are affected from the bug, though, so that aspect doesn't bother me personally. Now I never found the original Pro1's fingerprint reader too reliable, but the one in the Pro1X indeed is even worse. The Pro1 had a tendency to fail with moist fingers, the Pro1X has a tendency to fail with dry fingers, which affects me more. Also, somehow it behaves as if the stored fingerprint data would somehow deteriorate, and the success rate of fingerprint recognition becomes lower and lower, until I re-train it. Also, some security-centered apps like for banking are unusable with the fingerprint reader because they either refuse the fingerprint method completely or, after a few usages, report a change in the fingerprint data (that never happened, at least not actively through me) and switch off fingerprint authentication. I'm still using the fingerprint reader, but I'm thinking about disabling fingerprints. Quote Link to post Share on other sites
EskeRahn 5,052 Posted May 28 Share Posted May 28 8 hours ago, Rob. S. said: The Pro1 had a tendency to fail with moist fingers, the Pro1X has a tendency to fail with dry fingers, which affects me more. Also, somehow it behaves as if the stored fingerprint data would somehow deteriorate, and the success rate of fingerprint recognition becomes lower and lower, until I re-train it. These are interesting observations. I have never seen this with neither the Pro1 nor the Pro1X. But at 60 I guess that my fingers are quite 'fixed' as-is. I have not 'retrained' the Pro1 since experiments in 2019. (I have the bug that the fingerprint reader sort of stops working on the Pro1, and needs a restart to work - it could be anywhere between a month and the same day, and I struggle to see any pattern in triggering it. MAYBE it is picking it up and attempting unlocking while it still is vibrating with incoming sms. And initially I tried retraining and al kinds of tricks, but for years I just accepted it) Quote Link to post Share on other sites
DieBruine 392 Posted May 28 Share Posted May 28 (edited) Inotice no difference in behaviour. Wet fingers or really dried ot fingers indeed do not register correctly. Mine stopped working once, reboot fixed that. Banking apps hangs sometimes and disables fingerprint reader. Apart from those 'common' (to a Pro1 user) no other issues. I do have a bumper around the phone and that helps a lot with preventing unnecessary registration. Any skin is detected as a registraion, so I do understand your frustration. I'm having less issues because of the bumper around the edges. Running latest LoS btw. Edited May 28 by DieBruine 1 Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.