yashsingh1/xdaforums huggingface dataset:
[Fire TV General] aaronm32:
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:

Install Tasker

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

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

In tasker, set up a Task for Wolf Launcher:

Application->Launch App: Wolf Launcher

Application->Kill App: Home (Amazon) Launcher

Create profiles to launch it:

Event->System->Device Boot

Event->Display->Display On

Event->System->Logcat *filter type: amazon.intent.action.HOME_PRESSED
[Fire TV General] meeeeeeeeeeeeeeeeeeow:
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
[Fire TV General] xnappo:
Right, the whole reason for Termux was the faster launching.
[Fire TV General] aaronm32:
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"
[Fire TV General] 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
[Fire TV General] xnappo:
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.
[Fire TV General] aaronm32:
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.
[Fire TV General] xnappo:
Really? That seems quite odd. Are you on recent firmware? Can you still get to settings etc?
[Fire TV General] 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.
[Fire TV General] aaronm32:
I'm on FireOS 6.2.9.5. At first, the settings didn't work and I thought I screwed it up, but after using the Launcher Manager's routines to disable the custom launcher and then enable it again, the settings are fully accessible by holding down the home button for 2 seconds.

After a successful uninstall, it's still in there (in system/priv-app), but not used.

adb shell pm path com.amazon.tv.launcher
>>package:/data/app/com.amazon.tv.launcher-Jk0koxTXoWoSioevG_m3DA==/base.apk
adb uninstall com.amazon.tv.launcher
>>Success
adb shell pm path com.amazon.tv.launcher
>>package:/system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk

Everything seems to be working fine and I can still get to settings, Prime Video, and App Store if i need to.
[Fire TV General] xnappo:
Oh, yeah you are golden on 6.x. Don't update... Actually it may stick with an update I don't remember. This whole discussion of Tasker started with 7.x.
[Fire TV General] fluffi444:
If he is talking about FireOS 6.2.9.5. this must be FireTV 4K - And this is the latest available - Just a few weeks/days old.

This would be insane! If this all works this would a nice solution for everyone (whom want custom launcher) on newer FW.

And it looks like it works as you reported... Maybe this needs more tests... Will try when I have the time...

Or is this working because you came from OS 6.2.7.3 (FireTV 4K) and did the steps with OS 6.2.7.3 also?
[Fire TV General] xnappo:
Indeed if this works that would be great. I suppose it is possible no one tried because it seemed no unlikely it would work? Sorry re: FW, I am on Cube 3 and didn't realize TV was still 6.x.
[Fire TV General] fluffi444:
The FireOS (and the Android Version) depents on the device. As far as I know Amazon never (?) jumps for an specific device to an newer Android version... Only system/app updates are provided - but no newer Android versions in general...

Amazon FireOS naming is strange anyway :)

They like to do only +1 than to follow official Android version numbers:

Fire OS 3 Mojito (Android 4.2 „Jelly Bean“)

Fire OS 4 Sangria (Android 4.4 „KitKat“)

Fire OS 5 Bellini (Android 5.1 „Lollipop“, API-Level 22)

Fire OS 6 (Android 7.1.2 „Nougat“, API-Level 25)

Fire OS 7 (Android 9 „Pie“, API-Level 28)

Fire OS 8 (Android 11, API-Level 30)

The FireTV 4K (FireOS 6) has since 2018 "only" Android 7.1.2 based system.

And it doesn't look like that they jump to FireOS 7 for that device some day....
[Fire TV General] xnappo:
Thanks for the info. So definitely we would need to try this on multiple devices.
[Fire TV General] haxnhaxn:
Sry offtopic: OS 7.xx downgradeable?
[Fire TV General] Finnzz:
This will only work on devices that were already using a custom launcher before the 2022 lockdown.

The reason it works is because com.amazon.firehomestarter is still disabled on these devices. Normally when you uninstall the data partition copy of Amazon Launcher, FireHomeStarter will automatically set the system partition copy as the new Launcher.

Launcher Manager can't disable/enable Amazon Launcher anymore, it's a protected package, and LM isn't reporting the errors it's encountering. It can hand off launcher status to the custom launcher, only if FireHomeStarter is disabled.

You can confirm this by typing ADB shell pm list packages -d to show you a list of your currently disabled apps. FireHomeStarter is likely included.

This doesn't help anyone with a new device, or device that didn't already disable FireHomeStarter before February 2022. FireHomeStarter is now also a protected package.

No, you need root access to downgrade.
[Fire TV General] haxnhaxn:
What a pitty. Thanks for the forum, guys!
[Fire TV General] aaronm32:
Yes, both my firesticks already had LM working before the update. I don't have a newer one to test with, but I wonder if anyone has tried to uninstall it for the user instead of disabling? I think the command would be:

adb shell "pm uninstall -k --user 0 com.amazon.firehomestarter"
[Fire TV General] Finnzz:
It was tried many times after it was discovered here

Works if FireHomeStarter is already disabled, doesn't if it's enabled

I misread that, thought you meant Amazon Launcher. FireHomeStarter is only on the system partition, you can't uninstall it. All the '-k' option does over a regular uninstall is clear the app data too. Clearing FireHomeStarter's data/cache has no effect on its function of automatically making Amazon Launcher the default launcher.

If Amazon ever pushed out a standalone FireHomeStarter app update, it would automatically re-enable FireHomeStarter. Then anyone using a custom launcher utilizing this bug would instantly lose that function forever.

It's a bit of a surprise Amazon hasn't done this already. And it's a reason to block updates via DNS/Firewall/router.
[Fire TV General] xnappo:
Ah - okay now the world makes sense.
[Fire TV General] Fakex:
Can anyone confirm, that this works?

Is this only functionable with Projectivy Launcher or can I also use Wolf?

I am using a 4k Max (unfortunately with the latest SW-Version).
[Fire TV General] Dronzerr:
It's working for me only with Projective & you can directly boot in to projective launcher on system boot that too without any delay

unfortunately I have only one device so can't conform for sure.
[Fire TV General] xnappo:
Do you see any indication the normal launcher is still there, like a quick flash of it? Given that it needed the accessibility permission, I am thinking it is doing something similar to the Tasker work-around. Would be nice to know exactly what.. @spocky12 ?
[Fire TV General] Dronzerr:
a quick flash of the S#it launcher after pressing the home button for 1-2 sec is there, is there any workaround?
[Fire TV General] xnappo:
Don't think so, confirms Spocky12(Projective dev) is probably doing the same thing as the Tasker solution, triggering on home screen being active then launching. If you use PiHole it might be faster if you block the Amazon ads servers. I saw them listed somewhere.
[Fire TV General] Fakex:
So it might be worth giving it a try.

I just wonder if the Accessibility Manager works with the newest FTV Version. In the linked thread it is said, that it is only functionable with older versions.
[Fire TV General] Dronzerr:
I tried to find the Amazon ads servers list to block Amazon's S#it launcher ads but couldn't find anything, Can you please help me out here!?
[Fire TV General] xnappo:
See here:

Pi-hole Blocklist for Smart TVs

Pi-hole Blocklist for Smart TVs. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

I have NOT tried it.
[Fire TV General] aaronm32:
I have an idea on how to maybe disable the stock home activity on the most recent fireOS - my firestick 4k Max is 7.6.2.4 at the moment.

I noticed that Amazon Kids (com.amazon.tahoe) can still be disabled and it also has a home activity. If the home activity could be set to the tahoe home activity and then disable the app, perhaps it would break it and then go back to the Wolf Launcher or whatever custom launcher app is installed.

I tried just setting it directly, but got an error:

adb shell cmd package set-home-activity com.amazon.tahoe/.ftv.HomeActivity
>>java.lang.IllegalArgumentException: Component ComponentInfo{com.amazon.tahoe/com.amazon.tahoe.ftv.HomeActivity} cannot be home on user 0

I tried launching it, but seems to be locked down too:

adb shell am start -n com.amazon.tahoe/.ftv.HomeActivity
>>Starting: Intent { cmp=com.amazon.tahoe/.ftv.HomeActivity }
>>Error type 3
>>Error: Activity class {com.amazon.tahoe/com.amazon.tahoe.ftv.HomeActivity} does not exist.

I also tried running the EnableHomeActivity and it requires MANAGE_USERS permission, which I can't seem to give it:

adb shell am start -n com.amazon.tahoe/.ftv.deviceadmin.activities.EnableHomeActivity
>>Starting: Intent { cmp=com.amazon.tahoe/.ftv.deviceadmin.activities.EnableHomeActivity }
Security exception: Permission Denial: starting Intent { flg=0x10000000 cmp=com.amazon.tahoe/.ftv.deviceadmin.activities.EnableHomeActivity } from null (pid=2040, uid=2000) requires android.permission.MANAGE_USERS

Just thought I'd throw it out there if anyone had suggestions - or if someone already has a subscription to Amazon Kids and could enable the kids home and then disable the app via adb and see if it breaks the home app at reboot. Command to disable would be:

adb shell pm disable-user com.amazon.tahoe

To enable it back:

adb shell pm enable com.amazon.tahoe
[Fire TV General] Dronzerr:
Blocked all that crap from the home screen with "next DNS + Router's IPV6 Config" (since I don't have pi-hole), Unfortunately, though it doesn't improve load time to my custom launcher
[Fire TV General] HipHopAnonymous3:
Thanks dude! Works as advertised :)
[Fire TV General] asif9t9:
What breaks with Prime Video?
[Fire TV General] HipHopAnonymous3:
It looks like it disabled the app altogether. But if you run the debloater app you can select which individual aspects you'd like to turn off. So if you want Prime Video, uncheck it and you should be good. I don't use it though, so not 100%

--------------------------------------------------------------------------------------------------------------------------------

Update: I actually use a fire tv omni that's hooked up to an antenna for local channels. After running the debloater app I could no longer access my antenna channels. At that point I ran the debloater app again but unchecked all apps (essentially rebloating my fire tv). Afterward Projectivy still functioned as expected.

Moral of the story, you can still use Projectivy as your home screen replacement without debloating. Just give it the right permissions and accessibilities and select "Override Current Launcher" within the app.
[Fire TV General] MulderX33:
Hi, I've a problem with an app and Wolf Launcher:

Runtime TV (com.ammo.runtime.tv).

It runs fine from the apps list and other launchers, BUT it can't run from the Wolf/ATV Launcher.

Why? Any solution?... Thanks.
[Fire TV General] MrTooPhone:
So I went to update Background Apps and Process List today and could not get the Amazon App Store to stay open. It opens, then closes within a second or two. I am curious if this might be due to me using Wolf. Anyone else? Thoughts?
[Fire TV General] Finnzz:
Does it run from any other Launcher other than Amazon's Launcher? Taking a quick look at the app, the main activity that launches the app appears to be restricted. My guess is it's some security feature that's tied to the Amazon Launcher.

The App Store will open and stay open fine with Wolf Launcher set, but searches don't work and cause the Store to force close.

There are a lot of interdependencies among Amazon Apps. If you have blocked updates and you are on an older OS version but then updated the system apps, that can lead to instability

What are your OS and App Store versions?
[Fire TV General] MulderX33:
Thanks for reply

Yes, the app works fine:

- from any other launcher (flauncher, tvlauncher, projectivy launcher, original firestick launcher, original androidtv launcher...).

- if run directly from settings/applications/runtimetv/run.

- if the application is run from "installed apps" of file explorers like Filemanager Plus, XPlorer...

It just doesn't work from the wolf/atv launcher.

PS: Tested too on the free (and very old) version of ATV Launcher and it works fine. But in "pro version" (or wolf launcher) it doesn't work.

PS2: tested on various Wolf versions and... app only work ok in 0.1.6.
[Fire TV General] alex61194:
I could uninstall amazon launcher with project ivi and works perfect and prime video works
[Fire TV General] Dronzerr:
How?
[Fire TV General] MrTooPhone:
I can force App Store to open if I open a link before the App closes. But as you mentioned, I am now unable to search. I was able to search maybe a month ago or so.

My OS is 6.2.9.5

App Store 8.5015.5

Stock Launcher was deleted long ago.
[Fire TV General] safetyp1:
I followed all of this, but its still quite slow. At least 3-4 seconds until Wolf Launcher appears to load after pressing the Home button.

Any tips to make it faster?

Also some steps were mising for me:

1. Install Termux (install AptoideTv via Downloader app, and search Termux in AptoideTv, install first entry) and Tasker. Tasker wasnt in AptoideTv.

4. I had to create this folder and file, it did not exist.

mkdir ~/.termux/

Then:

~/.termux/termux.properties

And paste:

allow-external-apps = true

8. runKodi contents - it seemed faster withour "adb shell"

am start -n ""com.wolf.firelauncher/.screens.launcher.LauncherActivity"

10. You need to

chmod +x runKodi

, then to run it:

./runKodi

11. In tasker, set up a TaskerFunction->TermuxCommand. Skip through the wizard, dont enter anything. Clear the first textbox entry, and paste:

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

14. Best to do step 14 right after step 10. I ran into permissions issues in Tasker.

15. Add profile: Event -> Logcat. Then enter

amazon.intent.action.HOME_PRESSED

under "Filter"

This method was simpler, and actually had less delay than Termux method for me, about 3 sec delay. I didnt run this step "d. Debloat Toolbox (FireOS 6 & 7) (from the current thread)" at all, and it all still worked. When i gave permissions to Projectivy app, i got an exception for all of them, but it still seemed to work.
[Fire TV General] Finnzz:
You are on using the newest firmware and app store version, I don't know why it might be crashing.

I'm using the latest version of FireOS7 (7614/3337) and the latest app store version, with LM/Wolf Launcher. The app store doesn't crash on me.

Search in the app store has never worked while Amazon Launcher was inactive/disabled. Search requires a functional Amazon Launcher. You can however browse the app store.

If Amazon Launcher is functional, it regains default launcher status.

I'm not sure, Wolf might have a better idea. He already said a long time ago that he wouldn't make any more edits/releases of Wolf Launcher. If there aren't any features missing in 0.1.6 that you care about, you could just use that version.
[Fire TV General] Dronzerr:
You can further reduce the launch time to 2 sec. If you debloat the system.

It's working for me, your mileage may vary !
[Fire TV General] MulderX33:
Some new (and very useful/important) features are missing from previous versions (shortcut to "app info" for example, very useful to force stop, clear data/cache...).

I don't understand why that particular app doesn't work with the latest versions of Wolf/ATV, and it works without problems with old versions or with any other launcher (tested on firestick, androidtv stick, android pc emulator, tablets, tv boxes , xiaomi mi tv... with android 9, 10 and 11).

If there is no solution... I will have to stop using the app, or use another launcher or an older and less useful version of wolf.

Thanks for reply.
[Fire TV General] MulderX33:
How did you manage to have the firestick updated and not lose the functionality of using Wolf as the main launcher?

My 4k max is outdated because I blocked the initial update on first boot when I bought it, so I can have Wolf as the main launcher.

Can I update without losing wolf launcher as default launcher?

Mi version is: 7.2.4.8 (PS7248/2011)
[Fire TV General] MrTooPhone:
I don't block updates. I did delete the stock launcher sometime ago.
[Fire TV General] SweenWolf:
its caused by how the launcher opens the application.

to solve this

create a shortcut of the app, wolf and atv pro support shortcuts

or​

Hide the Runtime TV application (do not uninstall), then download and install the attached apk (Runtime TV - Helper) and it will open the Runtime Tv Application just fine.

Launcher Manager (Alpha)​

Its an alpha build so some feature might not work (I have opened the project after few months so i really don't remember the changes, but it might contain some broken code)

Like the other apk it reads logcat and starts the custom launcher, but it does that by adb (like some of you are doing it).

A friendly reminder, only one app/pc can connect to a port at a time, for wireless adb it is 5555, so if any other app is using the port it will fallback to how my previous app opens the launcher (which will take 5 seconds to start the launcher), when the port gets free it will use adb to launch the app.

I recommend uninstalling older LM first (or the app may behave abnormally) (do not uninstall your custom launcher)

After installing enable the following View attachment 5858611

then go to the last option (Custom Launcher Options) and select "Active Launcher"

and reboot once.

I know the ui is cluttered but i will try to organize it.
[Fire TV General] Finnzz:
Awesome update, It's very fast! I think this might be a little more responsive than the tasker implementation, maybe because LM is more lightweight.

Confirming it works on the 2nd gen Cube. It's not working on the 3rd gen Cube, I think the trigger needs to be adjusted.

My 2nd gen Cube is rooted. Try out the new custom launcher method above for a week. If you are happy with it, you could upgrade. But you will also lose the ability to block updates (disabling the OTA APK) after you update past PS7273. You'll have to use a DNS or firewall to block updates.
[Fire TV General] MulderX33:
Could you tell me the eaxct path and files that I have to delete, before activating the updates, so as not to lose Wolf Launcher as the main and default launcher?

com.amazon.tv.launcher?... com.amazon.kso.blackbird... ?

Do I delete the files, activate the updates, update the firestick, restart it... and that's it... can I continue using Wolf as the default launcher and have the firestick updated?...

I'm having problems with the wifi mesh connection and I think it's because it's not updated, because a 3gen firestick I also have (updated:( ) works perfectly with the wifi mesh repeaters I use.
[Fire TV General] Finnzz:
I would really recommend using the new Launcher Manager for a few days before you decide to update.

The reason why some people could keeping using a custom launcher after PS7273 is because they were already using Launcher Manager, which disables the FireHomeStarter APK. And after FireOS updates, FireHomeStarter remains disabled, which is enough to keep using a custom launcher. But this is a very fragile solution because Amazon could break this very easily with an update.

There are many posts about deleting the Amazon Launcher. What this really does, is delete the second copy of Amazon Launcher on FireTV, which should trigger FireHomeStarter to set the system copy as the new Launcher, but FireHomeStarter is still disabled, allowing a custom launcher instead.
[Fire TV General] ranseyer:
Wolf Launcher ist 0.1.7-FireTV (and i own a Fire TV Stick 4K)
[Fire TV General] SweenWolf:
Install this on your stick, this is pulled from my Firestick 4kView attachment 5190187
[Fire TV General] ranseyer:
Thanks, this is the exact the same version i got this morning via update. The behavier changed. When i start it, it pops up for 1 second an than it is closed. After that im back in thne launcher :-(
[Fire TV General] Finnzz:
@SweenWolf Thank you again for all your work on this launcher, it really makes FireOS a lot more bearable for someone coming from AndroidTV.

Would it be possible to make the wallpaper rotate through a folder of wallpapers (daily or some other time interval). It's a little bit of a frivolous request, but I think it would really add to the user experience.