如何在TvInputService覆盖视图接收输入事件及相关开发疑问

Great question! Let's break this down clearly based on what you've discovered about Android TV's Input Framework (TIF) and that tricky permission issue.

First, Let's Confirm the Permission Constraint #

You're absolutely right about the com.android.tv.permission.RECEIVE_INPUT_EVENT permission:

• It's marked as signatureOrSystem in AOSP source code, which means regular third-party apps can't grab it via adb shell pm grant—that's why you got the SecurityException error.
• Only two types of apps can obtain this permission:
  • Apps pre-installed in the Android system image
  • Apps signed with the same certificate as the system component that declared the permission (in this case, the TV Input Framework)

How to Build a TV Input Service That Can Consume Inputs #

You don't have to compile your TV Input into the Android system image to develop and test it. Here are three practical paths:

1. Use a Custom AOSP-Based ROM (Full Development Workflow) #

This is the most robust option for full-featured development:

• Integrate your TV Input Service code into the AOSP codebase, typically in the packages/services/Tv directory or a custom module folder.
• Compile the entire ROM using the system signature, then flash it to your test device.
• Your TV Input will automatically get the RECEIVE_INPUT_EVENT permission, and you'll be able to handle InputEvents exactly as a system-level TV Input would.

2. Sign Your APK with the Platform Certificate (Testing Shortcut) #

If you don't want to compile an entire ROM, you can sign your TV Input APK with the system's platform certificate:

• Grab the platform signature files from your AOSP source (usually located at build/target/product/security/platform.x509.pem and platform.pk8).
• Use the apksigner tool to sign your APK:

  apksigner sign --key platform.pk8 --cert platform.x509.pem your-tv-input.apk
  

• Uninstall any existing version of your TV Input, then install the signed APK. Since it shares the same signature as the system, it will be granted the signatureOrSystem permission automatically.

3. Input Delegation (For Early-Stage Testing) #

If you can't access the platform certificate or AOSP source right now, you can still test your input handling logic:

• Build a regular TV app that receives InputEvents (most key events are accessible to standard TV apps).
• In your TV Input Service, forward any events you don't need to consume to the foreground TV app.
• Once your logic is solid, switch to one of the first two methods to get the system permission and integrate everything properly.

Critical Tips for Input Event Handling #

• Be intentional about which InputEvents your TV Input consumes (e.g., HbbTV-specific keys like colored function keys).
• For events you don't need, call InputEvent.consume(false) to let the system pass them to other TV apps—don't block normal user interactions.
• Make sure you properly implement the onInputEvent() method in your TvInputService.Session subclass; this is where all input event processing happens.

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