Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Excessive clipboard access

See original GitHub issue

Short description

Not really a bug, simply bad design. The keyboard accesses the clipboard on every keypress. I only noticed because I get a toast every time an app accesses the clipboard, but I’m assumming this excessive access makes performance worse

Steps to reproduce

N/A

Environment information

FlorisBoard Version: 0.3.7
Install Source: Fdroid
Device: OnePlus 3T
Android version, ROM: Havoc Os 3.12 Android 10

https://user-images.githubusercontent.com/45497981/108467180-13014800-7285-11eb-93b9-17b99c27aa08.mp4

Issue Analytics

State:
Created 3 years ago
Comments:12 (6 by maintainers)

Top GitHub Comments

4reactions

patrickgoldcommented, Feb 21, 2021

Off topic: It’s kinda scary that every application can literally access the clipboard any time without a permission that you must explicitly grant. (Or is this because Florisboard is an IME?)

FlorisBoard, if the default IME in your system, has full clipboard access given by Android automatically. Other apps can read your clipboard only if they have input focus (e.g. not in the background) or if they define the android.permission.READ_CLIPBOARD permission, which gets automatically granted on install. Great security, isn’t it… You as a user can revoke that permission from apps, but with the exception of some custom ROMs only via adb. Because of this, at some point FlorisBoard will get an internal clipboard manager which has the ability to not sync with the system clipboard to prevent this from happening.

1reaction

Vendicatedcommented, May 23, 2021

the issue does not happen anymore! 😃

On May 23, 2021 3:26:52 PM UTC, Patrick Goldinger @.***> wrote:

Since February 27th a lot of time has passed and FlorisBoard has changed a lot. Could you try out if this issue still occurs on the latest stable release v0.3.12? Thanks in advance!

– You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/florisboard/florisboard/issues/376#issuecomment-846580638