If this can be solved on the rust layer, it will be better/faster. The second option is to hack a touch sensitivity solution on notedeck itself. The Google dev path is something you can start for "future generations" but don't expect anything back in time to matter.
Case in point, there was a bug on AOSP's default keyboard that I had to reverse engineer the keyboard to understand how character pixel rounding was working differently than other keyboards. The "bug" (unspecified API) has been there for over 10 years now.
I don’t even think this is a touch sensitivity thing. I can’t press it fast enough to only register a single key. It looks like android-activity has some vendored gamesdk glue code it copied over that has bugs. Going to try to get the latest upstream of that at least. If all else fails I will have to do some super hacky thing that detects this and fixes it proactively. Ew
> If all else fails I will have to do some super hacky thing that detects this and fixes it proactively
Sounds defensive nostrability coding
🫂
Thread collapsed
Thread collapsed