IssueTracker

Please share below details
1.  logcat logs
2.  adb -avd <NameofAVD> -verbose -show-kernel  (console logs)
3.  adb shell getprop | grep finger  (build finger print )

Hi, please check that it is what you need because I don't know what kind of logcat you need.

Thanks you.

Any news about this?

Hi guys, any news?

I'm sorry you are having problems with keyboard input.

This feature should be controlled by the "Enable keyboard input" checkbox, but it appears that you have tried that. This control is represented in config.ini as hw.keyboard. When "hw.keyboard=yes" the computer keyboard should be received by the AVD. But it appears that you have tried that, too. (And your attachments show that this is set correctly.)

I tried running with a configuration like yours, but did not see the problem.

Could you try with a "default" AVD? Please create an AVD by selecting Nexus 5X and API 27 (Google Play) and not changing any defaults. Then run the AVD and click on the Google Assistant and see if keyboard input works. If it does not, please attach your config.ini again.

Please also indicate the language setting of your keyboard. I will try to reproduce the problem using that setting.

Don't work T_T

This is my localectl status output:
   System Locale: LANG=en_US.UTF-8
                  LC_NUMERIC=es_ES.UTF-8
                  LC_TIME=es_ES.UTF-8
                  LC_MONETARY=es_ES.UTF-8
                  LC_PAPER=es_ES.UTF-8
                  LC_NAME=es_ES.UTF-8
                  LC_ADDRESS=es_ES.UTF-8
                  LC_TELEPHONE=es_ES.UTF-8
                  LC_MEASUREMENT=es_ES.UTF-8
                  LC_IDENTIFICATION=es_ES.UTF-8
       VC Keymap: us
      X11 Layout: us
       X11 Model: pc105

I'm using this keyboard https://www.amazon.es/Vortex-Race-Keycaps-Mx-Blue-Aluminium/dp/B072LZ3KP1

Thanks you :)

¡Nice keyboard!

I don't see anything in your system configuration or AVD configuration that could cause a problem.

Let me get more background.

Did this problem appear recently, or have you always had this problem with the Emulator?

Please launch your AVD and click on something that accepts text input.
Does the "soft" keyboard pop up on the device display?
Please click on that pop-up keyboard. Do the characters appear in the input field?
After clicking on the pop-up keyboard, please use your computer keyboard. Do the characters now appear in the input field?

Thanks :D yes is a nice keyboard jejeje

Answer your cuestions:
Please launch your AVD and click on something that accepts text input.
Does the "soft" keyboard pop up on the device display? - YES IT APPEAR
Please click on that pop-up keyboard. Do the characters appear in the input field? - THE SOFT KEYBOARD WORK FINE
After clicking on the pop-up keyboard, please use your computer keyboard. Do the characters now appear in the input field? - NOTHING, MY PHYSICAL KEYBOARD DON'T WORK BUT...

I normally use another AVD (API 26 with Google Apis) and to perform the tests that you have asked me, I started the emulator that you asked for (the emulator of the configuration file). I have pressed a text field, then I have pressed the "d" of the soft keyboard, and then I pressed the same on my physical keyboard and it WORKED !!! but ... after writing a bit I tried to start the emulator again but this time with a "cold boot" to repeat the tests and explain how to do it but ... IT DOES NOT WORK T_T.

I have observed that in the emulator of the configuration file, a keyboard icon appears at the bottom right and when I enter input options a physical keyboard appears but in the API emulator 26 the icon does not appear and in the physical keyboard it says no present.

YEEES I have catched it, I will make a video and sendyou because is a little strange XD.

I have been able to reproduce it twice but when I tried to record it it does not come out anymore... but i have discovered other things jajajaja XD when press space bar the emulator closes. I send you the video

Ok, now I have catched it, the problem is that I can to get the emulator focus. You can see that when I select the android studio de windows name, in the top of the windows change betwen gray (no focused) and white (focused) but the avd I can do the focus. You can see this in the next video.

Ud. eres gran detective.

I think we have three issues:

a) Window focus. The AVD accepts keyboard input only if it has focus.
Is this working correctly? Or does the AVD lose focus incorrectly?

b) The keyboard icon. This should appear when the AVD has "hw.keyboard=yes". The AVD will accept input from the computer keyboard only if this icon is present. (The behavior with older APIs may be different.)
You see the icon sometimes and do not see it other times. This should be consistent for each AVD. If you see it with some AVDs and do not see it with other AVDs, please re-check the config.ini files.
If for one AVD you see the keyboard icon sometimes and do not see it other times, then that is a problem.

c) Using the 'space' key closes the AVD.
This should not happen (obviously).
We might get some information if you run "adb shell getevent -tlv" in a different window, and then use the computer keyboard for input to the AVD. This command will display the keyboard events that the AVD receives. Please try this with API 21 or older. (With newer API levels, the output from "adb shell getevent -tlv" is buffered, so we might not see the events we are interested in.)

Ok, well.... The B yes, with the currect AVD the keyboard is not check, I re-check and now appear the icon :D

The A and the B is the same, the problem is the focus. I have a "trick" to make it work, watch the video and see it. For some reason when I click on the emulator window it does not have the focus, the focus remains on the options side window.

The video have audio and I try to explain the problem, sorry for my english :P

Hi, this ticket continue with tag "NeedsInfo". Do you need more info about this?

Thanks you

Your video shows the problem very clearly.

I don't understand how this can happen. How can the AVD receive and act on click events without the window receiving focus?

Most puzzling is that clicking on the title bar does not cause focus. Clicks on the title bar (I believe) do not get passed to the application, so all windows should respond the same. But your "Cheese" window receives focus as expected and the AVD does not, so somehow the AVD does respond differently.

I tried to reproduce your results. I did not see them on Windows, Mac OS, or Ubuntu Linux. I wonder if this only happens on Manjaro Linux.

Finally, perhaps the Focus settings on your system can help. I think you can set the focus mode (Click, Mouse, other?) and other focus-related settings. It might be helpful to know if these change the behavior of the AVD.

Hi, the problem is with xfce desktop, Ubuntu use unity or gnome depends of the version, if you install xfce desktop you can reproduce it ;)

The avd have two windows in one, the device screen and the toolbar windows, for any reason the focus don't work very well with this two windows in one.

For example if you have click in the screen device windows and press space bar you can see that real focus is in toolbar windows.

Please install xfce environment desktop and you can reproduce it ;)

#17 is correct. This is easy to reproduce when using XFCE.

@Comment #14 - thank you for sharing the video. This behavior is differently odd.

Due to the large number of Linux desktops and windows manager versions, we currently have our development, testing and system requirements focused around Gnome and KDE on Ubuntu.  We can spend a little more time investigating on our side, but I can not promise this is a top issue at the moment.

I understand, thank you very much for the effort. A greeting and many luck!

Project: platform/external/qemu
Branch: emu-master-dev

commit c2f3545758cbd66a8e99e52bcaa8977c6ba52ed6
Author: Joshua Duong <joshuaduong@google.com>
Date:   Thu Apr 11 14:57:54 2019

    Fix XFCE keyboard issue.
   
    We should never raise the tool window. we either give the keyboard
    focus to the emulator container or the extended window. Not calling
    parent class's raise() will never let the tool window gain focus, which
    is desired.
   
    BUG: b/73261949, b/37094173
   
    Test: For all of the below scenarios, the emulator should still receive
    keyboard events and not shut down. This bug also had focus on the close
    button of the tool window, so if you hit Space, it would close the
    emulator, so make sure to include the Space key when testing:
    1) Boot emulator, type some characters, including space.
    2) Click somewhere on the tool window, then type.
    3) Open the extended window, then click on the emulator window, then
    type.
    4) Open/click the extended window, then click on the tool window, then
    type
    5) Minimize the emulator, then unminimize, then type
    6) Bring another window (anything unassociated with emulator to the
    front, then click on the emulator/tool-window to bring it back to the
    front. Then type.
    7) Resize the emulator, then type.
   
    Change-Id: I9cdeb370a5201e9b35ef639a36262eec951efd82

M       android/android-emu/android/skin/qt/tool-window.cpp

https://android-review.googlesource.com/943759
https://goto.google.com/android-sha1/c2f3545758cbd66a8e99e52bcaa8977c6ba52ed6