Chrome Version: 54.0.2837.0
Chrome OS Version: 8737.1.0 dev-channel cyan
Chrome OS Platform: Cyan (Acer Chromebook R11)


Steps To Reproduce:
(1) Enable Android apps / Play Store
(2) From a running Android application on the Chromebook, use the Android Configuration object to detect presence of a hardware keyboard, for example as from the following from within an "Activity" method:

return getResources().getConfiguration().keyboard != Configuration.KEYBOARD_NOKEYS;


Expected Result:

Given that the Chromebook has a hardware keyboard present, the Android API call should return other than Configuration.KEYBOARD_NOKEYS

Actual Result:

Android's Configuration API returns HARDWARE_NOKEYS despite the presence of a hardware keyboard attached to the Chromebook.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)  Always

What is the impact to the user, and is there a workaround? If so, what is
it?

It is difficult for an application to tell whether to display a soft keyboard programmatically because of inaccurate information provided by the Configuration API.


Cr-OS-Systems