No longer works on Fire OS 6.2.7.2

[brianclinkenbeard]

App has suddenly stopped working after an automatic update to Fire OS 6.2.7.2 (Insignia Fire TV). Tried to add permissions again to no avail. Home button and startup hijacking no longer work.

[LordingtheVoid]

Apparently the wrong time for me to try this but my Toshiba fire TV is also having permission issues.

[glassbase]

My Toshiba FireTV updated automatically and is not working now. One of my FireSticks is still working.

[neogeo71]

Any update on this issue?

[MrMazzone]

As of today, for me, this is no longer working. FireTV Stick 4K. Fire OS 6.2.7.3

Hoping you have a fix because I HATE the default FireTV launcher.

[ErikAbele]

I am aware of the issue but unfortunately I can't do anything about it (yet) because all of my FireTV devices are still on 6.2.7.1 – it looks like Amazon is still rolling out the updates and Germany hasn't received any yet.

So I will have to wait until the update pops up over here... I'm sorry.

[RubixSolver99]

Thanks @ErikAbele
You do amazing work!

[oathzed]

@ErikAbele please let us know when you get it, were at the edge of our seats 😅

[ErikAbele]

Ok, I also got the update yesterday and see that Amazon did re-work home button handling so I'll have to dig a little deeper.

Booting into your custom launcher should still work though; if not then try setting it up again in an ADB shell:

settings put secure enabled_accessibility_services de.codefaktor.ftvlaunchx/de.codefaktor.ftvlaunchx.HomeService
settings put secure accessibility_enabled 1

[oathzed]

Ok, I also got the update yesterday and see that Amazon did re-work home button handling so I'll have to dig a little deeper.

Booting into your custom launcher should still work though; if not then try setting it up again in an ADB shell:

settings put secure enabled_accessibility_services de.codefaktor.ftvlaunchx/de.codefaktor.ftvlaunchx.HomeService
settings put secure accessibility_enabled 1

Okay thanks a lot man, hopefully you can get it sorted out :)

[Tbo29]

On 2nd. gen Firestick the command adb shell pm grant de.codefaktor.ftvlaunchx android.permission.WRITE_SECURE_SETTINGS came back with a "package not found error". So I decompiled and changed the package name to com.codefactor.ftvlaunchx. Disinstalled and installed the changed apk. This time giving the new name the command worked without an error. Now to find out how Amazon changed the home button handling.

[oathzed]

On 2nd. gen Firestick the command adb shell pm grant de.codefaktor.ftvlaunchx android.permission.WRITE_SECURE_SETTINGS came back with a "package not found error". So I decompiled and changed the package name to com.codefactor.ftvlaunchx. Disinstalled and installed the changed apk. This time the command worked without an error. Now to find out how Amazon changed the home button handling.

Let me know if you can figure out the home button issue. I've tried to debug aswell, can't figure it out

[Tbo29]

Well the pressing of the Home button is an system event and can't be intercepted, thus I'm sure that Erik knows a lot more about how the Homeservice works. Now if you give the command secure accessibility_enabled 1 it always turns back to 0 after rebooting. Maybe this can be handled like before it did with Hijack and the app-debug.

[oathzed]

Well the pressing of the Home button is an system event and can't be intercepted, thus I'm sure that Erik knows a lot more about how the Homeservice works. Now if you give the command secure accessibility_enabled 1 it always turns back to 0 after rebooting. Maybe this can be handled like before it did with Hijack and the app-debug.

Yeah that same issue happened before.

I got my button mapper to say accessibility is enabled with an app I made to trigger it. But accessibility isn't actually enabled.

[Tbo29]

Well at least for now the stick boots into the custom launcher.

[oathzed]

Well at least for now the stick boots into the custom launcher.

Yeah I don't think Amazon could ever patch that

I also have an app that opens my launcher on wake

[oathzed]

any luck @ErikAbele ?

[MPenSol]

Ok, I also got the update yesterday and see that Amazon did re-work home button handling so I'll have to dig a little deeper.

Booting into your custom launcher should still work though; if not then try setting it up again in an ADB shell:

settings put secure enabled_accessibility_services de.codefaktor.ftvlaunchx/de.codefaktor.ftvlaunchx.HomeService
settings put secure accessibility_enabled 1

still not working with FireTV Stick 4K. Fire OS 6.2.7.3

[oathzed]

-You cant use Wolf Launcher.
-Reinstall everything. Use Tv Launcher 3 (VERY IMPORTANT USE THIS, DO NOT OPEN IT) Wolf is not selectable in the native FireOS launcher chooser.
-adb shell pm grant de.codefaktor.ftvlaunchx android.permission.WRITE_SECURE_SETTINGS (this is what you use for 4k\tank)
-adb reboot
-after reboot you should have FireOS native launcher chooser pop up. Choose TVL 3 and "always."

again, You cannot use Wolf Launcher for this. Its probably not even "all" FTV LaunchX tbh.

You can use the home button to launch tv launcher 3?

You don't need root right?

[oathzed]

Yeah you need root. Sorry should mentioned that.

Lol. Yeah this stuff is easy with root

[oathzed]

Nobody can get it but me and this other user on 6.2.7.3 rooted. I think its cause everyone is using Wolf. This app doesn't work straightforward with root anymore.

I also think Amazon may have specifically flagged Wolf since it did work. That could possibly help the dev of this.

Atv launcher pro (which wolf is based off) will work with root.

You can always probably change the package name of wolf if that is what amazon blocked.

[oathzed]

Well I use ATV Pro without root on 5.2.7.4 (Firestick 2nd. gen.) which works more or less like on the 4K.

settings put secure enabled_accessibility_services de.codefaktor.ftvlaunchx/de.codefaktor.ftvlaunchx.HomeService
settings put secure accessibility_enabled 1

Does not work without root. The last command always returns 0. I could however chose ATV as the default launcher. Home button of course always takes me back to the amazon home.

I've decompiled the native Amazon launcher and seen that they changed the way the Home button works, but this would not be a problem as you can also intercept the Home_BUTTON_PRESSED, which of course you can't without root as the accessibility system also has been reworked. So far ATV works, just to take care not to press the Home Button to leave an app.

Hopefully @ErikAbele can figure something out, but it's not looking good.

[Tbo29]

Well I use ATV Pro without root on 5.2.7.4 (Firestick 2nd. gen.) which works more or less like on the 4K.

settings put secure enabled_accessibility_services de.codefaktor.ftvlaunchx/de.codefaktor.ftvlaunchx.HomeService
settings put secure accessibility_enabled 1

Does not work without root. The last command always returns 0. I could however choose ATV as the default launcher. Home button of course always takes me back to the amazon home.

I've decompiled the native Amazon launcher and seen that they changed the way the Home button works, but this would not be a problem as you can also intercept the Home_BUTTON_PRESSED, which of course you can't without root as the accessibility system also has been reworked. So far ATV works, just to take care not to press the Home Button to leave an app.

[oathzed]

Its a legit solution. You can use "keymap editor" for kodi, to set it to back out with the back button from the home screen of Kodi.

Netflix exits out with back. So do both Silk and Youtube.

its not though, thats not seamless at all lol

[oathzed]

@ErikAbele any news? :(

[oathzed]

Sween wolf got a fix for us! https://forum.xda-developers.com/showpost.php?p=83468741&postcount=461

[tonyvr4]

Sounds like a clumsy work around. To access the firestick settings you have to enable the amazon launcher. Which defeats the purpose of an aftermarket launcher so that I never have to see the garbage amazon launcher.

[oathzed]

Sounds like a clumsy work around. To access the firestick settings you have to enable the amazon launcher. Which defeats the purpose of an aftermarket launcher so that I never have to see the garbage amazon launcher.

No you dont. All the important settings have shortcuts inside the settings app he made. You don't have to enable the amazon launcher..

[tonyvr4]

Sorry I was confused when the xda post mentioned "4 shortcuts are included in apps (important ones)
To access full settings you have to enable Amazon launcher just like you disabled it."

It appeared that there was no way to access settings unless you use the amazon launcher.
But it does state that only 4 shortcuts to settings are included.

[oathzed]

Sorry I was confused when the xda post mentioned "4 shortcuts are included in apps (important ones)
To access full settings you have to enable Amazon launcher just like you disabled it."

It appeared that there was no way to access settings unless you use the amazon launcher.
But it does state that only 4 shortcuts to settings are included.

It's ok I had the same thought. But yeah every setting that's important is in the settings app

[ErikAbele]

Guys, while I appreciate any information regarding the issues of FTVLaunchX, this is not a forum. Can we please take the discussion over to XDA so that we can keep it focussed here... I guess other people would also benefit from you input over there. Thanks!

[tonyvr4]

can not install settings app on any of my firesticks. I get "there was a problem parsing the package"
Also I really do not want the firetv logo on the top of the screen. The reason I wanted a replacement launcher is to get rid of the amazon junk and advertisements

Please fix FTVlaunchX so I can go back to using my fire sticks again

[brianclinkenbeard]

can not install settings app on any of my firesticks. I get "there was a problem parsing the package"

Also I really do not want the firetv logo on the top of the screen. The reason I wanted a replacement launcher is to get rid of the amazon junk and advertisements

Please fix FTVlaunchX so I can go back to using my fire sticks again

Read the above post.

[tonyvr4]

Any progress on getting FTVLainchX to work? I am so tired of the amazon propaganda garbage

[sweharris]

FWIW

pm disable-user com.amazon.firehomestarter
pm disable-user com.amazon.tv.launcher

Seems to work. But it has side effects, such as losing access to the Settings control.

[oathzed]

FWIW

pm disable-user com.amazon.firehomestarter
pm disable-user com.amazon.tv.launcher

Seems to work. But it has side effects, such as losing access to the Settings control.

This works with current ftvlaunchx on 6.2.7.3?

[sweharris]

It seems to work with:

ro.build.version.name=Fire OS 6.2.7.3 (NS6273/2773)
FTVLaunchX-1.0.1.apk
LeanbackOnFire_1.5-release.apk

on my firestick 4K and my Toshiba Fire-TV edition.

[PastelRobot]

It seems to work with:

ro.build.version.name=Fire OS 6.2.7.3 (NS6273/2773)
FTVLaunchX-1.0.1.apk
LeanbackOnFire_1.5-release.apk

on my firestick 4K and my Toshiba Fire-TV edition.

On my firestick 2nd gen it spits out the error
"Permission Denial: attempt to change component state from pid=13078, uid=2000, package uid=32069"

[tonyvr4]

How it going ? If you need some testing please let me know

[AndreStork]

Fire OS 5.2.7.7... Same problem, launcher opens at startup but home button doesn't work