Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't click part of the screen whenever a lynket bubble is on-screen #161

Open
nickurak opened this issue Jan 3, 2022 · 5 comments
Open

Comments

@nickurak
Copy link

nickurak commented Jan 3, 2022

Whenever a lynket bubble is on screen, part of the screen (usually over the c/v/b keys of the normal keyboard) is blocked from being tapped.

This semes to be the spot where the "trash" icon would be, so I'm guessing it's related to that.

Very annoying, as it blocks the middle home-screen bar button, and blocks typing lots of words, until i discard those bubbles.

@nickurak
Copy link
Author

nickurak commented Jan 3, 2022

BTW, this has been happening on (at least) Android 11 and 12 on my Pixel 4a.

@spoelstraethan
Copy link

I've also been seeing this issue under Android 12 on my 4a 5G for sure, I may have encountered it on Android 11 but hadn't correlated the issue to having inactive bubbles at the time.

@arunkumar9t2
Copy link
Owner

Thanks for reporting, will address it as part of next update.

@WillHick
Copy link

WillHick commented Jan 7, 2022

Any release date? Just seen reviews on the Playstore and would be keen to use it again

@dgw
Copy link

dgw commented Aug 3, 2022

Don't remember running into this until after my phone got an update to Android 12, middle of last month. This evening I did some testing and came to the same conclusion as OP; it indeed seems the trash icon for Web Heads blocks touch even when it's invisible.

Android 12 changed some touch behavior related to overlays, and I do see that Lynket uses FLAG_NOT_TOUCHABLE (specifically mentioned in the change description) in Trashy.java. If you haven't looked into this yet, that's a starting point.

(For my part, I'm just glad to confirm that it's a software bug and not the start of a hardware digitizer failure.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants