Obsolete
Status Update
No update yet.
Comments
bi...@google.com
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
da...@tekeye.biz
While I'm not, currently, using emulated devices that have a camera button (e.g. Galaxy Camera) or a DPad, I notice there are no shortcuts for those listed.
When using an emulated device with keyboard enabled, and the onscreen keyboard opens, what is the shortcut to use the '123?'/'ABD' and 'search' (magnifier) keys?
Is it possible to stop the emulated device registering keys that are pressed when the Ctrl key is held (volume up/down), Just as alpha keys are ignored when control is held?
Thanks.
When using an emulated device with keyboard enabled, and the onscreen keyboard opens, what is the shortcut to use the '123?'/'ABD' and 'search' (magnifier) keys?
Is it possible to stop the emulated device registering keys that are pressed when the Ctrl key is held (volume up/down), Just as alpha keys are ignored when control is held?
Thanks.
bi...@google.com
1. There currently is no camera button. The DPad can be found on one of the pages in the extended settings, and as we verify and add support for more hardware buttons, they will likely go there as well.
2. Neither of those keys currently have keyboard shortcuts. I'm aware of a hard key for the search button, so adding a keyboard shortcut for that is possible, but I'm not aware of a hard key for the "ABC" button that replaces the "123?" button.
3. Certain key combinations (like Ctrl-= and Ctrl--) are now used for the keyboard shortcuts we used to have custom keysets for, so it all depends on what those shortcuts are.
It may help if you could give some context of a particular problem you are having?
2. Neither of those keys currently have keyboard shortcuts. I'm aware of a hard key for the search button, so adding a keyboard shortcut for that is possible, but I'm not aware of a hard key for the "ABC" button that replaces the "123?" button.
3. Certain key combinations (like Ctrl-= and Ctrl--) are now used for the keyboard shortcuts we used to have custom keysets for, so it all depends on what those shortcuts are.
It may help if you could give some context of a particular problem you are having?
mr...@gmail.com
I don't mind having to switch to the mouse for some operations. The primary context is accessibility for the small minority of disabled users who need to drive the emulator using the keyboard (I work in a University with mainly Windows PCs). Most of the emulator input has keyboard short cuts but there are a few omissions. The following assumes AVD PC keyboard input is enabled (the default setting).
1. When the AVD starts tab cannot be used to cycle through the screen icons. To get tab to work either:
Press an alpha char (search bar opens), delete it (backspace) and use Back (Ctrl Backspace).
Or:
Press tab then Home (or Ctrl-H).
Now tab can be used to cycle through screen items (and Enter to activate them). Would be good is tab operated immediately.
2. The Ctrl Shift D opens the direction pad but what keys drive it? (The old keysets had keys defined.) Not sure how important this is with few devices now supporting D. Pads.
3. Tabbing around and operating the Extended Controls dialog by keyboard is difficult because of missing visual clues.
4. On Windows Alt-F4 closes the emulator (x) but there is no shortcut for minimising (-) the emulator. The normal windows flag key with down arrow does minimise Studio dialogs but not an AVD window.
A shortcut for toggling 123?/ABC when the on screen keyboard is open is probably not required as all the symbols can be accessed using the shift key anyway. People just need to know that.
1. When the AVD starts tab cannot be used to cycle through the screen icons. To get tab to work either:
Press an alpha char (search bar opens), delete it (backspace) and use Back (Ctrl Backspace).
Or:
Press tab then Home (or Ctrl-H).
Now tab can be used to cycle through screen items (and Enter to activate them). Would be good is tab operated immediately.
2. The Ctrl Shift D opens the direction pad but what keys drive it? (The old keysets had keys defined.) Not sure how important this is with few devices now supporting D. Pads.
3. Tabbing around and operating the Extended Controls dialog by keyboard is difficult because of missing visual clues.
4. On Windows Alt-F4 closes the emulator (x) but there is no shortcut for minimising (-) the emulator. The normal windows flag key with down arrow does minimise Studio dialogs but not an AVD window.
A shortcut for toggling 123?/ABC when the on screen keyboard is open is probably not required as all the symbols can be accessed using the shift key anyway. People just need to know that.
bi...@google.com
1. It is curious that tab does not work immediately - I'll take a look into this.
2. We recently put in a fix that ensures the arrow keys can ALWAYS be used, since the directional pad actually sends those exact same keys (the center button and the return key seem to be functionally the same). D-pad support is largely for Android TV.
3. We're looking into why the focus / UI highlighting seems to be off in some of the extended UI. Jim, any progress on this?
4. Keyboard shortcuts for close and minimize are tricky because most systems have their own predefined shortcuts. There's a chance that the Qt UI framework is doing something tricky with Windows + Down Arrow, and if it has to do with the fact that we have multiple windows, that should also be fixed in a future version by merging the toolbar with the main window.
5. I'm not sure how we would make a visual indication that using modifier keys (like shift) can be used when host keyboard input is active. That may be something that needs to go into the AVD creation flow.
2. We recently put in a fix that ensures the arrow keys can ALWAYS be used, since the directional pad actually sends those exact same keys (the center button and the return key seem to be functionally the same). D-pad support is largely for Android TV.
3. We're looking into why the focus / UI highlighting seems to be off in some of the extended UI. Jim, any progress on this?
4. Keyboard shortcuts for close and minimize are tricky because most systems have their own predefined shortcuts. There's a chance that the Qt UI framework is doing something tricky with Windows + Down Arrow, and if it has to do with the fact that we have multiple windows, that should also be fixed in a future version by merging the toolbar with the main window.
5. I'm not sure how we would make a visual indication that using modifier keys (like shift) can be used when host keyboard input is active. That may be something that needs to go into the AVD creation flow.
bi...@google.com
Updates here:
1. The tab key does not function immediately on a physical device using a keyboard plugged in via USB - the same steps have to be taken as described here, so that is working as intended. However, the arrow keys DO work right away, which should handle any problems with opening an app purely via keyboard.
2. The arrow keys should now ALWAYS be active, regardless of whether or not the AVD is configured for Dpad.
3. Trackb.android.com/206580 for updates.
4. It seems that Qt itself is not responding to those shortcuts. Because they can be changed by any Windows user, I don't think its a good idea to build them into our UI.
I'm going to close this bug since most of the problems have been resolved / are tracked in a separate issue.
1. The tab key does not function immediately on a physical device using a keyboard plugged in via USB - the same steps have to be taken as described here, so that is working as intended. However, the arrow keys DO work right away, which should handle any problems with opening an app purely via keyboard.
2. The arrow keys should now ALWAYS be active, regardless of whether or not the AVD is configured for Dpad.
3. Track
4. It seems that Qt itself is not responding to those shortcuts. Because they can be changed by any Windows user, I don't think its a good idea to build them into our UI.
I'm going to close this bug since most of the problems have been resolved / are tracked in a separate issue.
[Deleted User] <[Deleted User]>
I've started working on a new app that allows me to use the emulator and I find the change for Back from Escape to cmd-del to be really difficult. It goes from a (natural) one-hand, left tap, to a 2-handed, cross-keyboard operation. Can we please customize keyboard shortcuts?
gr...@google.com
Yes, I plan to add ability to customize keyboard shortcuts in a future release.
Description
Android SDK Tools:25.1.1
Host Operating System:Windows 10 64 bit
Steps to Reproduce Bug:
1. Create a new AVD (emulator) with default settings (enable keyboard input is checked in Advanced settings), e.g. Nexus 6P API 23 (Marshmallow) x86
2. Start the AVD/emulator, the emulator loads in a window with control bar next to it.
3. Try to use the keyboard commands defined in the default.keyset file.
Expected Behavior:
The PC keyboard actions defined in default.keyset work.
Observed Behavior:
Most PC keyboard actions defined in default.keyset do not work.
More details - Using command 'emulator -help-keyset':
"on startup, the emulator looks for 'keyset' file that contains the configuration of key-bindings to use. the default location on this system is:
C:\Users\JDoe\.android\default.keyset
if the file doesn't exist, the emulator writes one containing factory defaults. you are then free to modify it to suit specific needs."
This default.keyset existed from previous version of the SDK:
BUTTON_CALL F3
BUTTON_HANGUP F4
BUTTON_HOME Home
BUTTON_BACK Escape
BUTTON_MENU F2, PageUp
BUTTON_STAR Shift-F2, PageDown
BUTTON_POWER F7
BUTTON_SEARCH F5
BUTTON_CAMERA Ctrl-Keypad_5, Ctrl-F3
BUTTON_VOLUME_UP Keypad_Plus, Ctrl-F5
BUTTON_VOLUME_DOWN Keypad_Minus, Ctrl-F6
TOGGLE_NETWORK F8
TOGGLE_TRACING F9
TOGGLE_FULLSCREEN Alt-Enter
BUTTON_DPAD_CENTER Keypad_5
BUTTON_DPAD_UP Keypad_8
BUTTON_DPAD_LEFT Keypad_4
BUTTON_DPAD_RIGHT Keypad_6
BUTTON_DPAD_DOWN Keypad_2
TOGGLE_TRACKBALL F6
SHOW_TRACKBALL Delete
CHANGE_LAYOUT_PREV Keypad_7, Ctrl-F11
CHANGE_LAYOUT_NEXT Keypad_9, Ctrl-F12
ONION_ALPHA_UP Keypad_Multiply
ONION_ALPHA_DOWN Keypad_Divide
Some of the expected commands did not work:
BUTTON_POWER F7
BUTTON_VOLUME_UP Keypad_Plus, Ctrl-F5
BUTTON_VOLUME_DOWN Keypad_Minus, Ctrl-F6
CHANGE_LAYOUT_PREV Keypad_7, Ctrl-F11
CHANGE_LAYOUT_NEXT Keypad_9, Ctrl-F12
Deleted this file and the following default.keyset was created when the AVD was started:
BUTTON_POWER Ctrl-Escape
BUTTON_VOLUME_UP Ctrl-Equal
BUTTON_VOLUME_DOWN Ctrl-Minus
BUTTON_BACK Ctrl-Backspace
BUTTON_HOME Ctrl-H
BUTTON_MENU Ctrl-M
Ctrl-Escape did not work, used by Windows to bring up start menu
Ctrl-Equal and Ctrl-Minus does work but also registers = and - on the emulated device.
Ctrl-Backspace, Ctrl-H, Ctrl-M works.
Changed the file to:
BUTTON_POWER F7
BUTTON_VOLUME_UP Ctrl-F5
BUTTON_VOLUME_DOWN Ctrl-F6
BUTTON_BACK Ctrl-Backspace
BUTTON_HOME Ctrl-H
BUTTON_MENU Ctrl-M
CHANGE_LAYOUT_PREV Ctrl-F11
CHANGE_LAYOUT_NEXT Ctrl-F12
The following errors were observed:
BUTTON_POWER had to use Ctrl-P (as per control bar icon tooltip)
BUTTON_VOLUME_UP used Ctrl-= (as per control bar icon tooltip, = read by device)
BUTTON_VOLUME_DOWN used Ctrl-- (as per control bar icon tooltip, - read by device)
CHANGE_LAYOUT_PREV used Ctrl-Left (as per control bar icon tooltip)
CHANGE_LAYOUT_NEXT used Ctrl-Right (as per control bar icon tooltip)