You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,10 +101,17 @@ This customized version introduces usability enhancements and some UX improvemen
101
101
### Method 1: Via Built-in Settings (Recommended)
102
102
This is the easiest and native way. Go to **Settings -> Accessibility -> Set as default launcher**. This will open the system home picker or default apps settings directly where you can select **LTvLauncher** as your default home app.
103
103
104
-
### Method 2: Remap the Home button
105
-
This is the safest fallback if your device blocks changing the default launcher. Use [Key Mapper](https://github.com/keymapperorg/KeyMapper) to remap the Home button of the remote to launch LTvLauncher.
104
+
### Method 2: Home Button Fix (Google TV / Fire TV)
105
+
If your device blocks changing the default launcher (common on Google TV and newer Fire TV updates), you can use our built-in Home Button Fix:
106
+
1. Open **Settings -> Accessibility**.
107
+
2. Tap **Home Button Fix (Google TV)**.
108
+
3. Turn on the accessibility service for **LTvLauncher** in the system settings.
109
+
Once enabled, the launcher will intercept Home button presses to automatically return to **LTvLauncher**.
106
110
107
-
### Method 3: Disable the default launcher via ADB
111
+
### Method 3: Remap the Home button
112
+
This is another fallback if the built-in options don't suit your setup. Use [Key Mapper](https://github.com/keymapperorg/KeyMapper) to remap the Home button of the remote to launch LTvLauncher.
113
+
114
+
### Method 4: Disable the default launcher via ADB
108
115
**:warning: Disclaimer :warning:**
109
116
110
117
**You are doing this at your own risk, and you'll be responsible in any case of malfunction on your device.**
0 commit comments