fix: fix keyboard unusable on android-36#84
Merged
senzhk merged 1 commit intoApr 23, 2026
Conversation
Rezisn
changed the title
Owner
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ADB Keyboard stopped receiving am broadcast intents on newer Android versions (including API 36 emulators) because dynamic BroadcastReceiver registration did not follow API 33+ rules and only ran when the soft input view was created. This change registers the receiver when the IME service starts and uses the correct export flag so shell/ADB deliveries work.
Files changed
keyboardservice/src/main/java/com/android/adbkeyboard/AdbIME.javaTesting
Video
Screen.Recording.2026-04-23.at.11.51.27.mov