Add characters to the keyboard mapping to allow them
to be entered into the AVD from the developer's PC
keyboard.
This mapping supports the non-ASCII keys that appear
on the "US International" keyboard. Most of the Latin-1
characters (but not all) appear on this keyboard.
This change does not remove support for any keys.
b.android.com/200042
Change-Id: I65d54eb36183382b171c388b26848941eb0ff8d9
(cherry picked from commit dac57966a9ddc2e3dbd233c8b1e7b83f60e11373)
Add the App Switch (Recents) key.
Add media control keys.
These are needed to support Emulator UI
buttons for these functions.
Change-Id: I5d5d25a77625bfd831cf7b31c126fd342efc6c5b
Turns out they produce an SNES controller with the same VID/PID as
their NES controller. Just remap both at once.
Change-Id: Iba94fdd69fd846f99ca1b3205de9069989635c73
Now that we have "replace" key event support in the framework we can map
ESC as AltR+1.
Bug: 24504154
Change-Id: Ief8a50098fc5484171011f268ffc22a309cbba62
This adds special layout and character map for Pixel C keyboard (Dragon
base) that lacks several keys, such as ESC, bracket keys, tilda and
backslash, which are mapped various Alt-R combinations.
Currently we map:
[Shift]+AltR+2 -> ~ and `
[Shift]+AltR+O -> { and [
[Shift]+AltR+P -> } and ]
[Shift]+AltR+= -> | and \
ESC mapping requires additional changes.
Bug: 24504154
Change-Id: I24fc68efe7e2ddebee26a273838443b441491857
With this we won't try to run validatekeymaps.exe when you run
"USE_MINGW=1 mma".
Also it seems it's too much to run the validation for every mma/mmma.
Validation in just platform build (droidcore) should be enough.
Change-Id: I22431009d4c2dd765bbd14b24eb5c8729b53d6c1
Looks like Broadcom re-used the Rhodi PID since we never shipped.
Remove the keylayout so we don't accidentally use it for other
devices.
Bug: 17504946
Change-Id: Ia11ad40f8ba7d49f82e7f68d881cf7c9bfafcb37
This is to simplify Project Watson requirements and enable USB Audio
to easily implement similar functionality to the Watson headsets.
Change-Id: Idd0a0cd6c6ba4a977090fb338d9241046f0380e6
This consolidates all of the information that was in the native
KeyEvent and the KeyLayout files into the managed KeyEvent class.
It also moves the definition for all of the key names to the native
side, rather than having them in both places.
Change-Id: I172e3b554e7eb52c79ae2ec406ef4332e8b25ffa
These new keys behave in similarly to KEYCODE_POWER but do not
simply toggle between awake and asleep states.
Sleep puts the device to sleep if it is awake.
Wakeup wakes up the device if it is asleep.
Bug: 12938999
Change-Id: I260fb918cc858882fe06fa880910df5763a76c5d
Reverts commits 4567e40eb04589d211af82f2dcb16cb3955c605e and
a977707d6e7006d11cfde045f187e777b31b9e04, which added special case fallbacks
for game controllers in the Japanese locale.
Bug: 12923922
Change-Id: I229126e589e11fb5de86772ef9c59d09723af941
Turns out Snakebytes produce all 0s for their vendor / product IDs. This
somehow got the vendor / product ID of an international apple keyboard, which
will break them. Unfortunately, this also means we cannot map Snakebyte
controllers at all.
Relevant bug: https://code.google.com/p/android/issues/detail?id=58202
Change-Id: I59e134f8d1eb059fdf6823e65d6ce5387428029e
Rather than keeping a curated list where it's easy to miss things, just pick up
all of the possible key layouts, key character maps and input device configs in
framework/base/data/keyboards based on filename.
Change-Id: Iefa8eca491dcb6913e5b12bfda7096b6a5fedf18
(cherry picked from commit 9f5a6ee489f89c93491beef9bf64475fd2bfb0dd)
