Emulator Issues #13400
openChromebook keyboard input not detecting some keys
0%
Description
Game Name?
[Put Game Name here]
Game ID? (right click the game in the game list, Properties, Info tab)
[Put Game ID here]
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
[Put MD5 Hash here]
What's the problem? Describe what went wrong.
Using the android version of dolphin emulator on chromebook and the input does not detect every key.
What steps will reproduce the problem?
Any chromebook with appstore should have the same problem
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
5.0-19870
Is the issue present in the latest stable version?
Yes
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
[First broken version number here (if applicable)]
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]
What are your PC specifications? (CPU, GPU, Operating System, more)
Google Chrome OS Version 118.0.5993.124 (Official Build) (64-bit)
Intel(R) Celeron(R) N4020 CPU @ 1.10GHz (2 threads, 2.80GHz)
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
[Anything else here]
Files
Updated by JosJuice about 1 year ago
- Status changed from New to Accepted
- Operating system Android added
- Operating system deleted (
N/A)
Known broken since the Android input overhaul (5.0-18920). The cause seems to be that the following method returns incorrect results on ChromeOS: https://developer.android.com/reference/android/view/InputDevice#hasKeys(int[])