Skip to content

README: explain why the default-launcher picker cannot work on Google TV - #130

Open
williavs wants to merge 1 commit into
leanbitlab-org:masterfrom
williavs:docs/google-tv-home-priority
Open

README: explain why the default-launcher picker cannot work on Google TV#130
williavs wants to merge 1 commit into
leanbitlab-org:masterfrom
williavs:docs/google-tv-home-priority

Conversation

@williavs

@williavs williavs commented Sep 2, 2026

Copy link
Copy Markdown

Method 1 cannot work on Google TV, and the README currently recommends it first. The reason is not a settings quirk: com.google.android.apps.tv.launcherx declares its HOME intent filter with priority=2 (setupwraith's recovery activity uses 1). Android's resolver (PackageManagerService.chooseBestActivity) returns the higher-priority candidate before it ever consults the preferred activity or the HOME role, and ComponentResolver.adjustPriority caps non-system apps at 0. So the picker records LTvLauncher as the HOME role holder and the Home key still launches Google TV. Same for cmd package set-home-activity.

Checked on a Hisense Google TV, Android 12:

$ adb shell dumpsys role | grep -A1 android.app.role.HOME
          name=android.app.role.HOME
          holders=com.leanbitlab.ltvL
$ adb shell dumpsys package -f resolvers activity | grep -B4 -A4 category.HOME | grep -E 'com\.|mPriority'
        com.google.android.apps.tv.launcherx/.home.HomeActivity ...
          mPriority=2, ...
        com.google.android.tungsten.setupwraith/.RecoveryActivity ...
          mPriority=1, ...
        com.leanbitlab.ltvL/.MainActivity ...            (no mPriority line = 0)

Home key with the picker set to LTvLauncher: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] ... cmp=com.google.android.apps.tv.launcherx/.home.HomeActivity} from uid 0.

This adds a short note under Method 1 pointing Google TV users at Method 2, with the two dumpsys commands to confirm it on their own device. Docs only.

The stock Google TV launcher declares its HOME intent filter with priority 2.
Android resolves the Home intent by priority before consulting the preferred
activity or the HOME role, and non-system apps are capped at priority 0, so
Method 1 records the choice and the system keeps ignoring it. Point people at
Method 2 and give the dumpsys commands to confirm it on their device.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant