[APP][FIRETV][NOROOT] Launcher Manager (Change Launcher without Root)

[questionesse]

So there's no way to get this to run on latest firmware, only if downgraded, right?

Just checking back every once in a while - by skimming through it looks like there's still no way to get the launcher working again?

 

[pitsensas]

custom launcher for Fire OS 6.2.8.7,

No Root Required​

install wolf or other custom launcher
install total commander on amazon app store
open, go to installed app, copy somewhere default launcher if you want(backup), after that delete default launcher.
And now you can use custom launcher again.
enjoy

Hello,

I'm new in the FireTV world and I have bought a Fire TV Stick 4K with FireOS 6.2.9.3 (NS6293/4731).

I want to change the default launcher by another (Wolf or Leanback), so I have followed the instructions to save and after deleted the KFTV launcher app.

But now, when I go to Launcher Manager, I can see that the current launcher is com.amazon.firehomestarter.FireHomeStarterApplication

I found this topic.; https://forum.xda-developers.com/t/...er-without-root.4176349/page-51#post-86770371

Can I follow it without any risk ?
Because I'm not able to save com.amazon.firehomestarter and com.amazon.tv.launcher before to uninstall them and I do know if I can find the "right" launcher on this cloud : https://gist.github.com/JulyIghor/d3d3dd460527a1d2b5b67954160d4abf

Thanks in advance

 

[pitsensas]

Hello,

So, I have tried by disabling instead of uninstall but withtout success for com.amazon.tv.launcher and com.amazon.firehomestarter !

C:\androidSDK\platform-tools>adb shell
mantis:/ $ pm clear com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.tv.forcedotaupdater.v2
Success
mantis:/ $ pm disable-user com.amazon.tv.forcedotaupdater.v2
pm disable-user com.amazon.tv.forcedotaupdater.v2
Package com.amazon.tv.forcedotaupdater.v2 new state: disabled-user
mantis:/ $ pm clear com.amazon.firehomestarter
pm clear com.amazon.firehomestarter
Success
mantis:/ $ pm disable-user com.amazon.firehomestarter
pm disable-user com.amazon.firehomestarter
Error: java.lang.SecurityException: Cannot disable a protected package: com.amazon.firehomestarter
1|mantis:/ $ pm clear com.amazon.tv.launcher
pm clear com.amazon.tv.launcher
Success
mantis:/ $ pm disable-user com.amazon.tv.launcher
pm disable-user com.amazon.tv.launcher
Error: java.lang.SecurityException: Cannot disable a protected package: com.amazon.tv.launcher
1|mantis:/ $

 

[Finnzz]

So, I have tried by disabling instead of uninstall but withtout success for com.amazon.tv.launcher and com.amazon.firehomestarter !

Amazon patched FireOS 6.2.8.7, Launcher Manager doesn't work after that version unless you were already using it before the patch.

 

[pitsensas]

Amazon patched FireOS 6.2.8.7, Launcher Manager doesn't work after that version unless you were already using it before the patch.

Thanks for this precision !

As I can not select a custom Launcher anymore, Do you recommend me to update with FireOs 7x ?

 

[Finnzz]

As I can not select a custom Launcher anymore, Do you recommend me to update with FireOs 7x ?

FireOS6 FireTV devices can't be updated to FireOS7.

Amazon updates FireOS6 and FireOS7 in parallel. Custom Launcher use was patched in 6.2.8.7 and 7.2.7.3, which were both pushed out to FireTV devices last March.

If your Fire Stick is still within it's return period, my recommendation would be to return it, and buy a new one. The new stick will ship with old firmware (pre 6.2.8.7). Skip the setup firmware update, block updates, and then you can still use custom launchers with LM.

 

[pitsensas]

FireOS6 FireTV devices can't be updated to FireOS7.

Amazon updates FireOS6 and FireOS7 in parallel. Custom Launcher use was patched in 6.2.8.7 and 7.2.7.3, which were both pushed out to FireTV devices last March.

If your Fire Stick is still within it's return period, my recommendation would be to return it, and buy a new one. The new stick will ship with old firmware (pre 6.2.8.7). Skip the setup firmware update, block updates, and then you can still use custom launchers with LM.

Thanks. Custom Launcher is not a priority. I have putted the Wolf shortcut on the Homescreen, so a click on this one and Wolf menu appears !

So, I will keep this box !

 

[ersan191]

FireOS6 FireTV devices can't be updated to FireOS7.

Amazon updates FireOS6 and FireOS7 in parallel. Custom Launcher use was patched in 6.2.8.7 and 7.2.7.3, which were both pushed out to FireTV devices last March.

If your Fire Stick is still within it's return period, my recommendation would be to return it, and buy a new one. The new stick will ship with old firmware (pre 6.2.8.7). Skip the setup firmware update, block updates, and then you can still use custom launchers with LM.

Unrelated to OS6, but I ordered two 4K Max sticks on Black Friday - one Refurbished and one New and they both came with 7.2.7.9 installed already. If anyone was trying to get a pre-block 4K Max you'll have to look elsewhere.

 

[SevenFXD]

where's the Wolf Launcher apk?

 

[arkvays]

https://apkpure.com/de/wolf-launcher/com.latestlaunchers.wolflauncher#menu

 

[Finnzz]

where's the Wolf Launcher apk?

Last version before development stopped.

 

[leodawson]

Darn... Tried it with the Fire stick 4k max, using Fire OS, version: 7.6.1.4. Doesn't work. I really appreciate this app though, thanks for creating it... I despise the stock amazon launcher, I hope there's an update in the future that'll make this work on newer Fire OS versions.

 

[linolino]

happy now.
Downloaded (wolf)Launcher App.
Used the Procedure to remap my (unused) Disney+ button on the remote for RemapperApp and when pressing the "Disney+" button on remote now the (Wolf)Launcher) opens up

 

[xnappo]

After a few hours, I managed to get instant home-key launching of Kodi (my preferred launcher) using Tasker and Termux. I think it is somewhat similar to @daavm 's method.

Quick demo:

I will edit this post as people find problems, sorry I did this over two days and I am sure I will miss something.

The key is to use Termux to launch the new launcher, and to run it twice.

Below you will need to install stuff inside Termux such as vi and adb.

1. Install Termux and Tasker
2. Install Android tools inside Termux:

   pkg install android-tools

3. Set up Termux permissions for Tasker:
   

   adb shell pm grant net.dinglisch.android.taskerm com.termux.permission.RUN_COMMAND

4. In Termux edit ~/.termux/termux.properties and uncomment the line:
   

   allow-external-apps = true

5. mkdir ~/.termux/tasker
6. cd ~/.termux/tasker
7. vi ~/.termux/tasker/runKodi
   (if you don't know vi, use nano)
8. runKodi contents:
   

   adb shell am start -n "net.kodinerds.maven.kodi/.Splash"

   (I *think* the command for Wolf Launcher is "com.wolf.firelauncher/.screens.launcher.LauncherActivity")
9. Save file
10. Test running 'runKodi' launches Kodi
11. In tasker, set up a TaskerFunction->TermuxCommand:
    

    TermuxCommand(/data/data/com.termux/files/home/.termux/tasker/runKodi,,,false)

12. Copy/paste so this runs twice
13. Test task works
14. Give Tasker permissions:
    

    adb shell pm grant net.dinglisch.android.taskerm android.permission.READ_LOGS
    adb shell pm grant net.dinglisch.android.taskerm  android.permission.SYSTEM_ALERT_WINDOW
    adb shell am force-stop net.dinglisch.android.taskerm

    
    
15. Assign profile to launch it, I am using the logcat looking for:
    

    amazon.intent.action.HOME_PRESSED

Good luck!!

 

[mai55]

Привет, ребята!
Я работаю над темой.

 

[rety20]

The android TV version seems to have broken my installation of the latest version of lineageOS on raspberry pi 4B.

Enabling custom launcher immediately disabled my controls (back, home, directional navigation, select etc). And current launcher changed to something along the lines of "select default home launcher dialogue box". Mouse controls still worked, and selection of "enable, disable, options" was possible, but clicking on them did nothing. After restarting the device, it won't boot past a completely blank gray screen with mouse cursor. Some system components are working (or not) as "unable to connect to WiFi" notification appeared briefly.

Looks like I'm gonna have to reinstall Android TV to fix this. Would suggest that those running lineageOS on raspberry pi refrain from using this app until this major issue is resolved.

 

[mai55]

Finished working on the theme "Wolf&Glass". 150 transparent banners. Wallpaper included. It is better to use dark wallpaper, plain. Banner sizes are adjusted in the launcher.

P.S. You can order the missing custom banners

 

[meeeeeeeeeeeeeeeeeeow]

After a few hours, I managed to get instant home-key launching of Kodi (my preferred launcher) using Tasker and Termux. I think it is somewhat similar to @daavm 's method.

Quick demo:

I will edit this post as people find problems, sorry I did this over two days and I am sure I will miss something.

The key is to use Termux to launch the new launcher, and to run it twice.

Below you will need to install stuff inside Termux such as vi and adb.

1. Install Termux and Tasker
2. Set up Termux permissions for Tasker:
   

   adb shell pm grant net.dinglisch.android.taskerm com.termux.permission.RUN_COMMAND

3. In Termux edit ~/.termux/termux.properties and uncomment the line:
   

   allow-external-apps = true

4. mkdir ~/.termux/tasker
5. cd ~/.termux/tasker
6. vi ~/.termux/tasker/runKodi
   (if you don't know vi, use nano)
7. runKodi contents:
   

   adb shell am start -n "net.kodinerds.maven.kodi/.Splash"

   (I *think* the command for Wolf Launcher is "com.wolf.firelauncher/.screens.launcher.LauncherActivity")
8. Save file
9. Test running 'runKodi' launches Kodi
10. In tasker, set up a TaskerFunction->TermuxCommand:
    

    TermuxCommand(/data/data/com.termux/files/home/.termux/tasker/runKodi,,,false)

11. Copy/paste so this runs twice
12. Test task works
13. Give Tasker permissions:
    

    adb shell pm grant net.dinglisch.android.taskerm android.permission.READ_LOGS
    adb shell pm grant net.dinglisch.android.taskerm  android.permission.SYSTEM_ALERT_WINDOW
    adb shell am force-stop net.dinglisch.android.taskerm

    
    
14. Assign profile to launch it, I am using the logcat looking for:
    

    amazon.intent.action.HOME_PRESSED

Good luck!!

Man, you are the best! Maybe you could alter the tutorial for first time Termux users:

They have to run the

pkg install android-tools

command to be able to use adb shell and also after the first time running an adb shell command you get a prompt where you have to accept (and tik the message box once), then run the same command again.

And also the steps 10 - 11 have to be repeated after creating a profile.

Which event would you choose to start the task after the boot/wake up from standby? Currently I'm using the Launch At Boot app which allows to start an app after the boot / wake up. It would be more convenient to use just different profiles instead of different apps for every use case.

 

[xnappo]

Man, you are the best! Maybe you could alter the tutorial for first time Termux users:

They have to run the

pkg install android-tools

command to be able to use adb shell and also after the first time running an adb shell command you get a prompt where you have to accept (and tik the message box once), then run the same command again.

And also the steps 10 - 11 have to be repeated after creating a profile.

Which event would you choose to start the task after the boot/wake up from standby? Currently I'm using the Launch At Boot app which allows to start an app after the boot / wake up. It would be more convenient to use just different profiles instead of different apps for every use case.

Thanks for the input! It was hard to think about Termux stuff since I already had it installed for a while. I am a bit confused about what you mean by repeating 10-11 after creating the profile? I just pointed the profile to that task?

Glad it worked for you. For the boot case I am using a profile:
Event->System->Device Boot

Also - instead of running twice, I now use something to check if the first time worked, and only then do it again. I can provide these details if the running twice isn't reliable for others. I think most are using Wolf instead of Kodi, so not sure how well this works.

@Falcon_X FYI

 

[meeeeeeeeeeeeeeeeeeow]

Thanks for the input! It was hard to think about Termux stuff since I already had it installed for a while. I am a bit confused about what you mean by repeating 10-11 after creating the profile? I just pointed the profile to that task?

Glad it worked for you. For the boot case I am using a profile:
Event->System->Device Boot

Also - instead of running twice, I now use something to check if the first time worked, and only then do it again. I can provide these details if the running twice isn't reliable for others. I think most are using Wolf instead of Kodi, so not sure how well this works.

@Falcon_X FYI

I was not able to link the task to the new profile, instead I had to create a new one. It would be nice if you provided the alternative way. I'm using it with Wolf Launcher.

I'm no tasker pro but is there a way to disable the notification for the task? Also is there a way to minimize the delay (I know it has to be written into/read out the log first, but maybe there is a delay inside tasker)?