Hello everyone,
I’ve always had the triple-tap gesture enabled for the screen magnifier; it’s really handy for me when something is too small and my glasses are out of reach.
However, lately, whenever I’m typing quickly, the magnifier keeps activating accidentally. It’s getting annoying. The magnifier shouldn’t be triggering while I’m using the keyboard. This issue only started recently, though I can’t say exactly when. I’m also fairly certain there used to be a specific setting to prevent this, but I can’t find it anymore.
Am I just imagining things, or did that setting disappear in a recent update?
Thanks for any hint
Welcome to the forum 
Yes a very handy tool. I’m not seeing this problem. Which OS build are you running ?
Settings > About phone > Build number
Any idea of where it was (also under Accessibility > Magnification?) or what it might have been called?
Which magnification type do you use? If you’re using “Magnify part of the screen”, that might be the problem.
Which keyboard are you using? The default is Gboard.
I see that in Android 15 there was indeed a setting “Magnify typing” which allowed the magnifier to “follow the text”, but it didn’t affect the keyboard and having tested it, I can say it wasn’t very effective. A16 system is much better and follows the text being typed quite efficiently..
Hello,
thanks for the reply.
OS version is FP6.QREL.16.61.0
I am using magnifying the whole screen and the standard Gboard.
I have searched in all settings for the magnification and keyboard but was not able to find a certain setting for this kind of problem.
You do not have this problem? 
Interesting, although it’s unclear for me what conclusions can be drawn from this.
It would be good to find another user with 16.61 so as to confirm, but my conclusion is that a full reset would probably sort it, though that might not be necessary.
However before doing that, the first thing to check is Safe mode.
Ok. Good tip. 
Wasn’t aware of that Safe mode option.
Will give it a try.
Thanks!
Hmm. Last update to FP5.QREL 16.69.0 seems to have solved the issue.
Just want to let you know.
And again thanks for your help