无触屏设备应用开发：遥控器无法导航软键盘问题求助

Absolutely feasible! I’ve built several apps for Android TV and other touchless, remote-controlled devices, so this is totally solvable. Let’s break down how to fix both the focus issue and remote navigation for the soft keyboard:

1. Ensure Your EditText Can Receive Focus #

First, some touch-optimized UI components don’t default to working well with remote navigation. Tweak your EditText’s XML attributes to make it focusable:

<EditText
    android:id="@+id/deviceNameEditText"
    android:focusable="true"
    android:focusableInTouchMode="true"
    android:imeOptions="flagNoExtractUi" <!-- Avoids full-screen keyboard which is hard to navigate with a remote -->
    android:inputType="textCapWords" <!-- Adjust input type to match your use case -->
    ... />

In your code, you can also explicitly request focus when the user selects the device name field:

// Kotlin example
deviceNameEditText.requestFocus()

// Java example
deviceNameEditText.requestFocus();

2. Get the Soft Keyboard to Pop Up & Respond to Remote Input #

Once the EditText has focus, you need to trigger the soft keyboard and ensure it’s navigable via remote:

• Use the system’s TV-optimized keyboard: If you’re targeting Android TV (or similar platforms), the system’s default keyboard is built for D-pad/remote navigation. Just make sure your app is configured for the right device category (add the android:isTV="true" attribute in your manifest if it’s an Android TV app).
• Force the keyboard to show: If it doesn’t pop up automatically when the EditText gets focus, use the InputMethodManager:

  val imm = getSystemService(Context.INPUT_METHOD_SERVICE) as InputMethodManager
  imm.showSoftInput(deviceNameEditText, InputMethodManager.SHOW_IMPLICIT)
  

• Handle remote key events (if needed): For custom behavior (like using the remote’s Enter key to submit input), add an OnKeyListener:

  deviceNameEditText.setOnKeyListener { _, keyCode, event ->
      if (event.action == KeyEvent.ACTION_DOWN) {
          when (keyCode) {
              KeyEvent.KEYCODE_DPAD_CENTER, KeyEvent.KEYCODE_ENTER -> {
                  // Handle submit action here (e.g., save the device name)
                  true
              }
              // Add other key handling as required
          }
      }
      false
  }
  

3. Troubleshooting Common Hiccups #

• Focus is stuck on other elements: Double-check your layout’s focus navigation. Use attributes like android:nextFocusDown, android:nextFocusRight, etc., to define clear focus paths between UI components.
• Keyboard won’t navigate: If the default keyboard isn’t cooperating, consider using a custom remote-friendly soft keyboard library designed for touchless devices—though the system keyboard should work for most cases.

The bottom line is that touchless devices are fully capable of supporting text input via remote control; you just need to configure your UI components to work with the system’s focus and input mechanisms.

内容的提问来源于stack exchange，提问作者Iseis