diff options
| author | Jared Henderson <jaredh.microsoft@gmail.com> | 2019-08-21 15:37:59 -0700 |
|---|---|---|
| committer | Siarhei Vishniakou <svv@google.com> | 2019-08-22 21:18:57 +0000 |
| commit | f829b5df5ed8f80ef41fe54cc4deb70fd8ff914e (patch) | |
| tree | 50088e14465f5313548e9d3a453866df9534f5c1 /tests/Codegen/src/com/android/codegentest/SampleDataClassTest.java | |
| parent | 2214ede1ec975875268fe36d35fb3ab94e9344bd (diff) | |
Update Xbox BT controller mapping to support upcoming controller firmware update
The Xbox controller (product id 0x2fd) is going to have a new firmware update this fall that sends a different keycode (316/BUTTON_MODE) for the Xbox button. The goal is to enable the Xbox button to make it to apps on all Android versions -- with our without a controller-specific key mapping file.
Unfortunately, the new Vendor_045e_Product_02fd.kl key mapping file that was added to Android Q maps the pre-firmware-update Xbox key code (172) to BUTTON_MODE, yet it makes no mention of key 316. This results in apps getting a raw 316 scan code instead of a BUTTON_MODE KeyEvent when using a controller with the latest firmware on Android Q.
The fix is to add an additional key mapping for 316 that *also* maps to BUTTON_MODE. With both mappings in place, both pre and post firmware-updated controllers will get the correct behavior for the Xbox button on Android Q.
Test: AFAIK, no CTS tests exist for Xbox controller key mappings; we'll need to add some at a later date. I was unable to test this change because I'm unable to write to the system directory on any of my devices, but I know that mapping 316 to BUTTON_MODE will fix the issue.
Change-Id: I8600ea79a0aa8557267d6ca712e5d56680e7a98b
Signed-off-by: Jared Henderson <jaredh.microsoft@gmail.com>
Bug: 139372370
Diffstat (limited to 'tests/Codegen/src/com/android/codegentest/SampleDataClassTest.java')
0 files changed, 0 insertions, 0 deletions