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

[xnappo]

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)?

That is weird, for me when I create the profile, then back out, it asks my to link it to a task, and the task I created was on that list...

 

[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

Ok the wake up event is: Event -> Display -> Display On.

 

[xnappo]

Ok the wake up event is: Event -> Display -> Display On.

Yep - sorry I was thinking boot - Display On is also super useful - I actually use this to do some other various stuff too (sometimes my projector doesn't turn on, so I send a network command to turn it on).

 

[eXtremeDevil]

Quick question, right now I have the package com.amazon.firehomestarter disabled (it was disabled before the system update that prevent disabling packages) and com.amazon.tv.launcher enabled, so right now I can use any launcher and I'm in fact using Wolf Launcher. But what I can NOT do is launch stock launcher. Do you guys know of any command like "launch com.amazon.tv.launcher/ActivityX" to bring up the stock launcher?

Thanks!

 

[meeeeeeeeeeeeeeeeeeow]

Quick question, right now I have the package com.amazon.firehomestarter disabled (it was disabled before the system update that prevent disabling packages) and com.amazon.tv.launcher enabled, so right now I can use any launcher and I'm in fact using Wolf Launcher. But what I can NOT do is launch stock launcher. Do you guys know of any command like "launch com.amazon.tv.launcher/ActivityX" to bring up the stock launcher?

Thanks!

Don't you have a backup of the original launcher apk? I think if you go this way you are not able to use the original launcher. You have to install the old file or reset your Fire device

 

[eXtremeDevil]

Don't you have a backup of the original launcher apk? I think if you go this way you are not able to use the original launcher. You have to install the old file or reset your Fire device

I do have the original launcher installed and enabled, only the firehomestarter package is disabled (but also installed).

 

[Finnzz]

I do have the original launcher installed and enabled, only the firehomestarter package is disabled (but also installed).

am start -n com.amazon.tv.launcher/.ui.HomeActivity_vNext

But I'm pretty sure it won't work for people who uninstalled the Amazon Launcher to set Wolf back to the main Launcher. It doesn't seem to matter that the system partition copy of the launcher is present and enabled.

It's probably why it hasn't set itself back as the main Launcher.

What do you need to access from the Amazon Launcher?

 

[eXtremeDevil]

pm start -n com.amazon.tv.launcher/.ui.HomeActivity_vNext

But I'm pretty sure it won't work for people who uninstalled the Amazon Launcher to set Wolf back to the main Launcher. It doesn't seem to matter that the system partition copy of the launcher is present and enabled.

It's probably why it hasn't set itself back as the main Launcher.

What do you need to access from the Amazon Launcher?

I just wanted to have the possibility, although is not strictly necessary. What do you guys mean by "uninstalled"? I never uninstalled the launcher or any other system app, it is only disabled (homestarter, not the launcher).

EDIT

I tried the command and it's giving me this:

Unknown command: start

EDIT 2

Seems like the correct command is "am", now I get this:

Error type 3
Error: Activity class {com.amazon.tv.launcher/com.amazon.tv.launcher.ui.HomeActivity_vNext} does not exist.

 

[Finnzz]

Sorry, corrected, yes am not pm

It's not going to be possible to access the homescreen for those that are hanging on to WL because FireHomeStarter is still disabled. Download Activity Launcher and check KFTV (Amazon Launcher), it will show you all the activities, and you can click on them to try them, but none of the accessible ones will take you to the homescreen.

If you really need the Amazon homescreen, you can look into the home button remapping method that people have been mentioning here and on other threads. It keeps KFTV accessible but it has downsides and I think you are better off with what you have now.

If you re-enable FireHomeStarter, then you will never be able to go back to that method. It's a one way street.

 

[eXtremeDevil]

I know that, I don't want to enable HomeStarter by now, I will keep it this way. Thanks for the info!

 

[bluedisc]

wrong thread

 

[aaronm32]

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.

Doesn't seem like Termux is required if you have a separate computer connected to issue the ADB commands. This is what worked for me with just Tasker:

1. Install Tasker
2. 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
3. Remove Amazon Launcher permissions:
   adb shell cmd appops set com.amazon.firehomestarter READ_EXTERNAL_STORAGE ignore adb shell cmd appops set com.amazon.firehomestarter WRITE_EXTERNAL_STORAGE ignore adb shell cmd appops set com.amazon.tv.launcher READ_EXTERNAL_STORAGE ignore adb shell cmd appops set com.amazon.tv.launcher WRITE_EXTERNAL_STORAGE ignore
4. In tasker, set up a Task for Wolf Launcher:
   Application->Launch App: Wolf Launcher
   Application->Kill App: Home (Amazon) Launcher
5. Create profiles to launch it:
   Event->System->Device Boot
   Event->Display->Display On
   Event->System->Logcat *filter type: amazon.intent.action.HOME_PRESSED

 

[meeeeeeeeeeeeeeeeeeow]

Doesn't seem like Termux is required if you have a separate computer connected to issue the ADB commands. This is what worked for me with just Tasker:

1. Install Tasker
2. Give Tasker permissions:
   adb shell pm grant net.dinglisch.android.taskerm com.termux.permission.RUN_COMMAND 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
3. In tasker, set up a Task->Application->Launch Wolf Launcher
4. Create profiles to launch it:
   Event->System->Device Boot
   Event->Display->Display On
   Event->System->Logcat *filter type: amazon.intent.action.HOME_PRESSED

Then you don't need the Termux permission in paragraph 2. Also the application launch task in Tasker is really slow compared to Termux command task

 

[xnappo]

Then you don't need the Termux permission in paragraph 2. Also the application lauch task in Tasker is really slow compared to Termux command task

Right, the whole reason for Termux was the faster launching.

 

[aaronm32]

Then you don't need the Termux permission in paragraph 2. Also the application launch task in Tasker is really slow compared to Termux command task

Thanks for pointing that out. I removed the command from the post. Anyway, it's not that delayed for all the trouble it takes to get Termux working. Also, the Termux script is issuing the command through ADB, which is going to make the command slower - especially when it needs to make a connection. Since the shell script is run directly from the device, just execute directly (no need for adb):
am start -n "com.wolf.firelauncher/.screens.launcher.LauncherActivity"

 

[Dronzerr]

I have changed the default launcher on the Latest Fire TV (Kinda...)


I purchased Latest Fire Tv Stick Lite yesterday (First-time fire tv user)
Received & applied multiple updates (OS + Remote Update)
I'm on Fire OS 7.6.2.4 (PS7624/3337) / Fire TV Home Version 6420030.1

What I did is
1st Install the Following apps
a. Accessibility Manager v1.8 (from This Link)
b. Permissions Manager - 1.0.3 (from the current thread - Just in case)
c. Projectivy Launcher-4.24
d. Debloat Toolbox (FireOS 6 & 7) (from the current thread)

Now using Debloat Toolbox (FireOS 6 & 7) Debloat the system as much as I can (selected all the apps on the default window & hit apply), I don't use Prime Video so I don't care if it breaks.

Given Accessibility permission to Projectivy Launcher from Accessibility Manager v1.8


Given all permission to Projectivy Launcher from Permissions Manager - 1.0.3


Go to Projectivy Launcher > Projectivy Launcher Settings > General > Tick "Override Current Launcher"

Additionally, you can give various other permission to Projectivy Launcher in the launcher settings (explore yourself)

now press the home button on the remote (wait for 2 sec) boom!!! you are in Projectivy Launcher

Long press on the home button to access system settings

 

[xnappo]

Thanks for pointing that out. I removed the command from the post. Anyway, it's not that delayed for all the trouble it takes to get Termux working. Also, the Termux script is issuing the command through ADB, which is going to make the command slower - especially when it needs to make a connection. Since the shell script is run directly from the device, just execute directly (no need for adb):
am start -n "com.wolf.firelauncher/.screens.launcher.LauncherActivity"

Launching it using adb is also part of the speedup if I remember correctly. Did you try it both ways? Understand some people might not care about the 2-3 second delay, but it annoys me and the Termux thing is really not that hard and it is super useful for other stuff anyway.

 

[aaronm32]

Launching it using adb is also part of the speedup if I remember correctly. Did you try it both ways? Understand some people might not care about the 2-3 second delay, but it annoys me and the Termux thing is really not that hard and it is super useful for other stuff anyway.

I ended up just uninstalling com.amazon.tv.launcher through adb (surprised it let me) and now the Wolf Launcher with Launcher Manager is working again. Seems like the best solution.

 

[xnappo]

I ended up just uninstalling com.amazon.tv.launcher through adb (surprised it let me) and now the Wolf Launcher with Launcher Manager is working again. Seems like the best solution.

Really? That seems quite odd. Are you on recent firmware? Can you still get to settings etc?

 

[QuiDC96]

It's frustrated...
Since March 2022 still not has any solution to improve the boot delay on my Fire TV 4k Max while use wolf launcher.