Llama Way To (Sort Of Run Any Launcher) - Fire TV General

Hey guys so today I got un-rootable Fire TV for someone.
I had to figure out a easy way to always somehow get back to custom launcher....
Updated Video Posted Below.
Using Llama I did the following:
1) For "Recents" I linked Kodi (using Ikono TV)
2) I installed FiredTV newest verison in settings I selected -> "Disable Home Button Detection"
of course when we click go back to FireTV Home we won't be able to get back to FiredTV without going to settings -> all appliactions so I had to figure out a way to do it quick without going there..
Please note any other app you open within FiredTV will re-open FiredTV upon clicking "Home Button"
if something goes wrong and it does not go back to FiredTV just launch kodi and click Home button to go back to FiredTV.
I think it goes back because Llama is also configured for Kodi using IkonoTV icon replacer.
3) Step 3
Open Llama:
go to Events:
Add new one by clicking "+"
Add-Condition:
"when current app is KFTV Launcher" -- Active Application (KFTV Launcher)
Add Action now:
Select:
Kill Application - KFTV Launcher
do it again
Kill Application - KFTV Launcher
Add 3rd Action:
Run Application ( FiredTV)
Current Issues With This Method or Annoyances?
When you want to go back to Fire TV (Amazon Launcher) it goes way to quick back to FiredTV Launcher:
Solution I found:
You have to be real quick upon clicking Fire TV Home go back real quick to settings. (Once I was in Settings the Llama script) wouldn't go back to FiredTV Launcher until I scrolled back to any part of Amazon Launcher: example Home or I clicked Home Button.
In my video I didn't get quick ENOUGH to settings I only scrolled onto settings but didn't go the right ->>> to actual settings.
That's it!
Everytime you go to home within seconds you should be automatically set to go back to FiredTV launcher.
If you need to go back to Amazon Fire Screen without being booted back again to FiredTV screen click "home button 3 times quick and go to settings" this way you won't be automatically moved to FiredTV launcher.
Using this way also when I run Kodi then go back the FiredTV always re-launches itself. Which is what I wanted!
https://www.youtube.com/watch?v=zdLLazp4qC4&feature=youtu.be

Any Launcher
patt2k said:
Hey guys so today I got un-rootable Fire TV for someone.
I had to figure out a easy way to always somehow get back to custom launcher....
Using Llama I did the following:
1) For "Recents" I linked Kodi (using Ikono TV)
2) I installed FiredTV newest verison in settings I selected -> "Disable Home Button Detection"
of course when we click go back to FireTV Home we won't be able to get back to FiredTV without going to settings -> all appliactions so I had to figure out a way to do it quick without going there..
Please note any other app you open within FiredTV will re-open FiredTV upon clicking "Home Button"
if something goes wrong and it does not go back to FiredTV just launch kodi and click Home button to go back to FiredTV.
I think it goes back because Llama is also configured for Kodi using IkonoTV icon replacer.
3) Step 3
Open Llama:
go to Events:
Add new one by clicking "+"
Add-Condition:
"when current app is KFTV Launcher" -- Active Application (KFTV Launcher)
Add Action now:
Select:
Kill Application - KFTV Launcher
do it again
Kill Application - KFTV Launcher
Add 3rd Action:
Run Application ( FiredTV)
That's it!
Everytime you go to home within seconds you should be automatically set to go back to FiredTV launcher.
If you need to go back to Amazon Fire Screen without being booted back again to FiredTV screen click "home button 3 times quick and go to settings" this way you won't be automatically moved to FiredTV launcher.
Using this way also when I run Kodi then go back the FiredTV always re-launches itself. Which is what I wanted!
I can make a video if someone requests it.. but it's very simple.
Click to expand...
Click to collapse
It's been on youtube for ages

alandmo said:
It's been on youtube for ages
Click to expand...
Click to collapse
I didnt see a way to get back to custom launcher within few seconds. I only saw it boot on 1 st start.
Maybe i didnt see it before lol.
Sent from my SM-N910V using Tapatalk

I would love to see you make a video.
Sent from my SPH-L710 using XDA Free mobile app

jorv976 said:
I would love to see you make a video.
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
Sure I will tomorrow it will be on fire stick I returned the un-rootable fire TV it turned out it was a refurb/used.
So will do tomorrow!

Any luck with the video @patt2k ?

bigyin said:
Any luck with the video @patt2k ?
Click to expand...
Click to collapse
Yea I didn't have much time I will try to make it today and upload later on.
This method is great but remember if you USE amazon prime (on that fire stick we don't use it's for someone else that I did it for) so this is a perfect resolution.
If you do use PRIME you can use it but it's little trickier, because once you go to KFTV launcher it goes back to FiredTV launcher *using llama*.
Sorry for the delay guys!

This method does not work properly for me on the FireTV Stick.
I have it setup exactly as you have described but whenever I reboot my FireTV Stick it loads the Standard FireTV Launcher and NOT FiredTV!
Once you go into FiredTV from the Settings>Apps Menu it works everytime from there but does not work on initial Boot!
Is it working on Boot everytime for you?

Thank you so much! Will try this and report back when I get home.

Reni10 said:
This method does not work properly for me on the FireTV Stick.
I have it setup exactly as you have described but whenever I reboot my FireTV Stick it loads the Standard FireTV Launcher and NOT FiredTV!
Once you go into FiredTV from the Settings>Apps Menu it works everytime from there but does not work on initial Boot!
Is it working on Boot everytime for you?
Click to expand...
Click to collapse
I know I promised a video but I didn't have access to that stick... I will today lol..
Did you select in FiredTV to disable home button detection?
it has to load into standard launcher for few seconds but then goes to FiredTV Launcher real quick.
When you click Home inside FiredTV you will go back to FiredTV no matter what you do.
If you go to "Home" (Amazon Launcher) if it sees you are in "Home" you will be put back into FiredTV launcher within like 2-3 seconds.
I will do my best to provide a video today (around 9 pm EST Time)
Also another thing I never reboot that Fire Stick because there really is no point it's on 24/7

Disable home page detection is disabled in FiredTV settings.
I don't know how this can actually work on every boot as Llama does not load automatically so how can it trigger anything if it is not even loaded?
If this does not work on boot then it actually does not do anything that the Home Page Detection setting in FiredTV provides anyway???

Reni10 said:
Disable home page detection is disabled in FiredTV settings.
I don't know how this can actually work on every boot as Llama does not load automatically so how can it trigger anything if it is not even loaded?
If this does not work on boot then it actually does not do anything that the Home Page Detection setting in FiredTV provides anyway???
Click to expand...
Click to collapse
Well I can't 100% answer your question I shared what I set up and worked for me the only way would be to show you guys a video which I will today when I have access to that fire stick :highfive:

Here is the short video showing that it works.
Fire TV Stick Llama w/Fired TV: http://youtu.be/zdLLazp4qC4
Sent from my SM-N910V using Tapatalk

That works alright but that is only the same as having home page detection on in firedtv.
Does it work when the stick boots up without you having to start it?
That is the real issue not it just working after you boot and start it manually, this I thought was supposed to work as a start on boot method as what you have shown is already built into firedtv!

Thanks for this as it seems to work fine. Getting back to the Fire TV home screen by pressing the Home button three times also does return me back to that screen but....
Using it as it is how would I actually be able to change any of the settings for the Fire TV as soon as I go near that option then bang I'm back to the Fired TV home screen.
Accessing the settings from that icon on the screen will just kill the Fire TV launcher, as it is meant to do.
Using it on my Fire TV seems useful but only if I could get into the settings options for the few times that I need to do, putting the unit into sleep mode for example - but I would like to get to that screen without being thrown back into the Fired TV home screen . When my FTV is in sleep mode then my media server will hibernate, when th FTV is active so the server remains awake.

Reni10 said:
That works alright but that is only the same as having home page detection on in firedtv.
Does it work when the stick boots up without you having to start it?
That is the real issue not it just working after you boot and start it manually, this I thought was supposed to work as a start on boot method as what you have shown is already built into firedtv!
Click to expand...
Click to collapse
For it to boot up I think you just have to follow the old guide, I think the action was launch application and you would select firedtv launcher.
What I also discovered was if you cant get it to boot set ikono tv app with kodi you can run kodi from home screen.. When you exit kodi it should go back to firedTV launcher.
About settings what I found was if I am quick enough to scroll down to SETTINGS it won't move me to " FiredTV" on my video you could see I did scroll to settings but I didn't actually move to the right into the settings MENU.
By doing this when I was in "Settings" I would not be moved into FiredTV.. hope that helps!
Give it a try
Sent from my SM-N910V using Tapatalk

vimesUK said:
Thanks for this as it seems to work fine. Getting back to the Fire TV home screen by pressing the Home button three times also does return me back to that screen but....
Using it as it is how would I actually be able to change any of the settings for the Fire TV as soon as I go near that option then bang I'm back to the Fired TV home screen.
Accessing the settings from that icon on the screen will just kill the Fire TV launcher, as it is meant to do.
Using it on my Fire TV seems useful but only if I could get into the settings options for the few times that I need to do, putting the unit into sleep mode for example - but I would like to get to that screen without being thrown back into the Fired TV home screen . When my FTV is in sleep mode then my media server will hibernate, when th FTV is active so the server remains awake.
Click to expand...
Click to collapse
Add settings icon to firedTV launcher it might be hidden, when you click it might look like ita stuck i think you just have to press like left or right and you should stay at settings.
My fire tv is rooted so i discovered this by accident.
If i went to settings fast enough it wouldnt move me to firedtv launcher.
You gotta be quick
Sorry for any mistakes was typing from my phone.
Sent from my SM-N910V using Tapatalk

Related

[Q] Other way to default launcher?

Besides this, is there anyway to go back to go launcher ex as launcher (when using button savior), as I dummingly defaulted nook launcher in button saviour?
In this moment I don't have internet connection for the nook
Well managed to find a wifi connection and did the way from the previous post. If anyone has a better idea for future mistakes.
Another way is to install Relaunch with adb.
With this app, when you click on Home in the n button menu, you can start Relaunch and then start any app.
Gotta try that, mdall. I hope it doesn't happen again, but if it does, I'll have it around

[Q] "n" Key Long Press Default

I recently rooted my Nook Color with ManualNooter 5.02.19 and everything worked like a dream.
However, I accidentally made the default long press going to the B&N normal home screen, as opposed to the Zeam Launcher. Now, once I accidentally go to any screen that isn't associated with the Zeam Launcher, I can't get back into those keys! I'm such a dummy - if I reboot, and unlock the screen, there it shows me to get to the Zeam Launcher, so I can change settings, I just don't know where to go.
It popped up where I should go to change this, but unfortunately, I didn't catch it Can anyone please advise?
caseystain said:
I recently rooted my Nook Color with ManualNooter 5.02.19 and everything worked like a dream.
However, I accidentally made the default long press going to the B&N normal home screen, as opposed to the Zeam Launcher. Now, once I accidentally go to any screen that isn't associated with the Zeam Launcher, I can't get back into those keys! I'm such a dummy - if I reboot, and unlock the screen, there it shows me to get to the Zeam Launcher, so I can change settings, I just don't know where to go.
It popped up where I should go to change this, but unfortunately, I didn't catch it Can anyone please advise?
Click to expand...
Click to collapse
No sure where it is in stock, but you need to find where your app information is in settings and clear the default for B&N launcher. Then the next time you long press, it will ask what you want to do.
Sent from my Nook Color running ICS and Tapatalk
caseystain said:
I recently rooted my Nook Color with ManualNooter 5.02.19 and everything worked like a dream.
However, I accidentally made the default long press going to the B&N normal home screen, as opposed to the Zeam Launcher. Now, once I accidentally go to any screen that isn't associated with the Zeam Launcher, I can't get back into those keys! I'm such a dummy - if I reboot, and unlock the screen, there it shows me to get to the Zeam Launcher, so I can change settings, I just don't know where to go.
It popped up where I should go to change this, but unfortunately, I didn't catch it Can anyone please advise?
Click to expand...
Click to collapse
Once you reboot, and are in the Zeam Launcher, go to the app "NookColor Tools" --> All Settings --> Manage applications --> All --> Zeam Launcher --> Clear defaults. The next time you press home, you can reselect the one that you want.
Can you use Home Switcher with stock? That is what I used when this same process baffled me in CM7.
mateorod said:
Can you use Home Switcher with stock? That is what I used when this same process baffled me in CM7.
Click to expand...
Click to collapse
Yes, Home Switcher and Home Manager work with stock rooted. Either one easily allows you to change back and forth between home launchers and set the default. I don't believe either lets you change the short/long press action. For that you usually need to go into the settings.
Also if you are running Softkeys or Button Savior you may need to go into those settings and change the default action for short/long press of home to go to where you want for each.
JP

Is there a way to see recent apps and switch between them?

Is there a way to see recently launched apps and switch between them?
This function should be definitely included in default system. So useful!
Can't test it now but try it with long pressing the home button
Huberer said:
Can't test it now but try it with long pressing the home button
Click to expand...
Click to collapse
that goes to the twitch thingy unfortunately.
xd4d3v said:
that goes to the twitch thingy unfortunately.
Click to expand...
Click to collapse
Ok, didn't know. Thank you
I had the same idea but did not work lol.
I am not sure what you are looking for exactly, but the list of apps on the original launcher is always reorganized to show the most recently used apps first. Or are you using a different launcher?
Sent from my SM-N900V using XDA Free mobile app
The best way of doing this is with LMT Launcher using it's Pie feature. Install it, and set up an item as Activity -> System UI -> com.android.systemui.recent.RecentsActivity. This gives you the recent apps, which is normally non-accessible on the shield. You can then add a few others as you see fit. I've added the power menu for example, which gives you the full power off, reboot and sleep options. Not found that anywhere else. All works best with a mouse, so you're best using an alternative launcher like HALauncher. But I suspect most people are doing that anyway given how restricted and awful Leanback is.
It can be downloaded here.
this is like the third or fourth thread about this

FTVStick and Launcher

Hi
i was wondering if nobody tryed to disable the original launcher with llama or automate.
I actually use FTVStick with llama and 1 rule.
If the "Handy" restarts, launch Appstarter.
When FireTV is Turned on, a few seconds after Booting up, llama start Appstarter.
I dont need the Original Amazon menu and want to disable it all the time.
The idea is, a rule like "if ktv-launcher is foreground start appstarter", and if i push the "Home" button on remote, Amazon launcher start, llama will recognized that and start Appstarter.
So i dont need to root.
My problem is, llama is very old and not supportet anymore.
So the Rule "app in foreground" doesnt work, and i need to switch to another tool.
On a FireHD10 Tab i used Automate and it works to use a alternative launcher.
Every time i press the Home button, the amazon launcher appear, and after 1-2 seconds automate starts another launcher.
The problem, i cant use Automate on FTVStick, because i need a touchscreen to configure the tool.
I hope, anybody can help creating a Automate flow with the options to check if ktv-launcher is the active app and start appstarter,
or give me a hint how to do my idea without a touchscreen.
thanks
I was able to control automate using a mouse and keyboard but I don’t think you can monitor for foreground applications without access to accessibility services. I hope you can get it to work though as I would love this!
I use Appstarter and Launcher Hijack, and followed the "Disable bloatware..." thread...
Amazon Launcher is not on my device, home button works flawlessly to return me to "Top TV Launcher 2" and it used to work for AppStarter when that was my main launcher.
FTVS2
@TimmyP many Thanks.
LauncherHijack works Perfect.
It doesnt Start Firestopper on Boot, but it catch the Home Button.
I use llama with the "On Boot" Rule and LauncherHijack for Home Button.
Thank You !
happy to help

Any Launcher, No Root (Launcher Hijack V4)

Launcher Hijack V4
Allows a custom launcher on Amazon Kindle Fire's and Fire TV's
An early, insert seasonally appropriate celebration here, present from me. Adds support for Fire TV devices and the new Fire Tablets. Enjoy.
Please find instructions for use here (https://github.com/BaronKiko/LauncherHijack/blob/master/HELP.md#fire-tvs). Adb required for first time setup on Fire TV's.
Find the latest release here (https://github.com/BaronKiko/LauncherHijack/releases). I'm working on Aptoide and F-Droid releases for those that prefer those methods. Hopefully in the next few days.
If you want to look at my rushed and sloppy code then feel free to look here (https://github.com/BaronKiko/LauncherHijack)
Please send any issues here (https://github.com/BaronKiko/LauncherHijack/issues)
Feeling kind and want to donate? Find instructions here (https://github.com/BaronKiko/LauncherHijack/blob/master/README.md#donations)
Huge thanks to ParrotGeek1, Speeddymon and Urbanman2004.
ParrotGeek1 made V1 and without him I would have never started this project.
Speeddymon donated a 2018 Fire TV allowing me to implement Fire TV support. If you have a Fire TV you should thank him
Urbanman2004 created the lovely logo/app icon. Be sure to thank him too.
Finally I don't really check these forums often anymore so please head over to the github page and post there if you are having any issues. Usually I am pretty quick to respond there.
im not having any luck getting the accessibility function to work. i am on fireos 5.2.4.2
EDIT: I also have a fully updated firestick with the same issue. 5.2.6.7. hijack says accessibility needs to be enabled.
I believe I have a solution. I had to enable and disable some system accessibility settings to get the setting to take effect.
krsmit0 said:
im not having any luck getting the accessibility function to work. i am on fireos 5.2.4.2
EDIT: I also have a fully updated firestick with the same issue. 5.2.6.7. hijack says accessibility needs to be enabled.
I believe I have a solution. I had to enable and disable some system accessibility settings to get the setting to take effect.
Click to expand...
Click to collapse
You have to run an adb command to get it going on the fire tv's. Instructions explain it all.
The adb command alone wasn't enough. I use settings get... To verify it was there. But through several reboots it wouldnt work until I toggled other accessibility settings. This was the case for 2 different sticks.
Can you post what you did?
even with the adb command it still says accessibility needs to be enabled
huffmybrd said:
even with the adb command it still says accessibility needs to be enabled
Click to expand...
Click to collapse
Go into the standard fire TV settings and toggle.on some accessibility options. Then press home and see which launcher pops up.
Do you have the option in the settings? On the firestick 4k, fire tv (3rd gen?) and the cube (all running fire os 6.x) there are no options so you have to set it via adb. If you can do it through the system ui do it there I just thought all fire tv's didn't have the option.
Honestly I only own my fire tv because speeddymon donated it so that I could implement support for it, and I rarely use it as I have a computer hooked up to my tv making it entirely useless. In short I don't really know the in's and out's of the device.
Please do let me know what devices and fireos versions you are all running so I can update the instructions. Also what exact menu's you have to go through to get to the option.
As an aside you probably need to drop "secure" from the adb command to get it working on devices with the menu option but the system UI option is just better. Google changed it's category to stop you setting it without adb when they removed the menu option.
BaronKiko said:
Do you have the option in the settings? On the firestick 4k, fire tv (3rd gen?) and the cube (all running fire os 6.x) there are no options so you have to set it via adb. If you can do it through the system ui do it there I just thought all fire tv's didn't have the option.
Honestly I only own my fire tv because speeddymon donated it so that I could implement support for it, and I rarely use it as I have a computer hooked up to my tv making it entirely useless. In short I don't really know the in's and out's of the device.
Please do let me know what devices and fireos versions you are all running so I can update the instructions. Also what exact menu's you have to go through to get to the option.
As an aside you probably need to drop "secure" from the adb command to get it working on devices with the menu option but the system UI option is just better. Google changed it's category to stop you setting it without adb when they removed the menu option.
Click to expand...
Click to collapse
its not the home button option that needs to be toggled. like you say, its not there. but toggling some of the other options seems to get this to work after you have done the adb command. but doing the adb command alone and rebooting doesnt make this work. the system doesn't think it is enabled. toggling other accessibility options on and off finally made it work for me.
BaronKiko said:
Launcher Hijack V4
Allows a custom launcher on Amazon Kindle Fire's and Fire TV's
An early, insert seasonally appropriate celebration here, present from me. Adds support for Fire TV devices and the new Fire Tablets. Enjoy.
Please find instructions for use here (https://github.com/BaronKiko/LauncherHijack/blob/master/HELP.md#fire-tvs). Adb required for first time setup on Fire TV's.
Find the latest release here (https://github.com/BaronKiko/LauncherHijack/releases). I'm working on Aptoide and F-Droid releases for those that prefer those methods. Hopefully in the next few days.
If you want to look at my rushed and sloppy code then feel free to look here (https://github.com/BaronKiko/LauncherHijack)
Please send any issues here (https://github.com/BaronKiko/LauncherHijack/issues)
Feeling kind and want to donate? Find instructions here (https://github.com/BaronKiko/LauncherHijack/blob/master/README.md#donations)
Special thanks to ParrotGeek1 and Speeddymon. ParrotGeek1 made V1 and without him I would have never started this project. Speeddymon donated a 2018 Fire TV allowing me to implement Fire TV support. If you have a Fire TV you should thank him
If somebody with some artistic talent wants to make a logo that would be much appreciated as the little android guy looks out of place in my app drawer.
Finally I don't really check these forums often anymore so please head over to the github page and post there if you are having any issues. Usually I am pretty quick to respond there.
Click to expand...
Click to collapse
Awesome.. Thanks for the update. It seems to be a lot more robust then v3. I just got done doing some quick testing. Will detail what worked in my case on a separate post below.
I do have a request. Is there any chance you can take a look at keeping Launcher Hijack as it's own app. But also can you please take a look to see if you can create a fork of a merger of your Launcher Hijack latest version & the last GitHub release of AppStarter v4.0 (Found @ : https://github.com/sphinx02/AppStarter ). AppStarter is the best launcher for FireTV devices. But it is due for an update/upgrade. Adding your Launcher Hijack code would be great. Also updating the SPMC & Kodi link changes would be great. Also merging other opensource projects like On Boot AppStarter (Found @: https://bitbucket.org/Mirakel/onbootappstarter/src would be another). Another of the major things that will need change/updating is what the Settings button (The 3 lines button to the right of the Home button) does in AppStarter vs Launher Hijack. Since right now trying to open the FireTV long press Settings also opens the AppStarter App FireTV Settings popup. Giving you an extra thing to close after coming back from the long press Settings menu.
I can test & help in anyway you want. Let me know if something you are willing to take on. All the pieces are there. They just need to be merged & upgraded.
krsmit0 said:
im not having any luck getting the accessibility function to work. i am on fireos 5.2.4.2
EDIT: I also have a fully updated firestick with the same issue. 5.2.6.7. hijack says accessibility needs to be enabled.
I believe I have a solution. I had to enable and disable some system accessibility settings to get the setting to take effect.
Click to expand...
Click to collapse
You where right. Will get more specific in a separate post below.
BaronKiko said:
You have to run an adb command to get it going on the fire tv's. Instructions explain it all.
Click to expand...
Click to collapse
On FireTV devices below FireOS v6. It seems we need two steps to enable everything needed. Will give more detail of some testing below.
krsmit0 said:
The adb command alone wasn't enough. I use settings get... To verify it was there. But through several reboots it wouldnt work until I toggled other accessibility settings. This was the case for 2 different sticks.
Click to expand...
Click to collapse
I bet both FireTV Sticks are on FireOS v5 FW ?
TimmyP said:
Can you post what you did?
Click to expand...
Click to collapse
Will get specific below.
huffmybrd said:
even with the adb command it still says accessibility needs to be enabled
Click to expand...
Click to collapse
Info on how to successfully enable everything posted below.
krsmit0 said:
Go into the standard fire TV settings and toggle.on some accessibility options. Then press home and see which launcher pops up.
Click to expand...
Click to collapse
The ADB command is still needed first. Then the only accessibility option that needs toggling is "Screen Magnifier". Just toggle the setting like you are going to turn it on. The instructions screen should popup. Then just choose "TURN OFF MAGNIFIER" at the instructions screen. Hitting "TURN OFF MAGNIFIER" will opens up Launcher Hijack v4. There you can choose AppStarter or your chosen launcher. Then you are all set.
BaronKiko said:
Do you have the option in the settings? On the firestick 4k, fire tv (3rd gen?) and the cube (all running fire os 6.x) there are no options so you have to set it via adb. If you can do it through the system ui do it there I just thought all fire tv's didn't have the option.
Honestly I only own my fire tv because speeddymon donated it so that I could implement support for it, and I rarely use it as I have a computer hooked up to my tv making it entirely useless. In short I don't really know the in's and out's of the device.
Please do let me know what devices and fireos versions you are all running so I can update the instructions. Also what exact menu's you have to go through to get to the option.
As an aside you probably need to drop "secure" from the adb command to get it working on devices with the menu option but the system UI option is just better. Google changed it's category to stop you setting it without adb when they removed the menu option.
Click to expand...
Click to collapse
Right. It seems FireOS v5 devices need a two-step setup. In correct order both the ADB command & a ACCESSIBILITY Menu Toggle (Screen Magnifier ONLY) are needed for it to proper register everything. The good news is that it only needs to be done once. And it survives a FireTV reboot. Bad news is that if you deliberately stop the Launcher Hijack App. Then you have to do do the two step setup again.
I also tried dropping the "secure" from the adb command but got he following results:
Run Code:
Code:
settings put enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
And
settings enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Both gave the following return:
Code:
ty_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ <
Invalid namespace 'enabled_accessibility_services'
usage: settings [--user NUM] get namespace key
settings [--user NUM] put namespace key value
settings [--user NUM] delete namespace key
'namespace' is one of {system, secure, global}, case-insensitive
If '--user NUM' is not given, the operations are performed on the owner user.
[email protected]:/ $
Let me know if I should test anything else regarding this.
Will post specifics of what worked for me on a separate post below.
---------- Post added at 06:49 AM ---------- Previous post was at 06:44 AM ----------
krsmit0 said:
its not the home button option that needs to be toggled. like you say, its not there. but toggling some of the other options seems to get this to work after you have done the adb command. but doing the adb command alone and rebooting doesnt make this work. the system doesn't think it is enabled. toggling other accessibility options on and off finally made it work for me.
Click to expand...
Click to collapse
Right, thanks to your post I was able to narrow it down to a single Accessibility Toggle. Working on a post that explains everything now.
Y314K said:
Right, thanks to your post I was able to narrow it down to a single Accessibility Toggle. Working on a post that explains everything now.
Click to expand...
Click to collapse
Great, thanks. I wasn't sure what exactly was working, but i spent sometime on both sticks until it worked. I am on fireos 5 on both sticks. I think the issue i have now is i keep ending up back on the fire tv launcher. i think hijack or my launcher choice (TVLauncher) are getting kicked out of memory. Other then that this feels extremely stable and very consistent.
Guide for FireTV's on FireOS 5 FirmWare v0.5...
Guide for FireTV's on FireOS 5 FirmWare v.05
This guide should work on all FireTV devices on any FireOS 5. Rooted & Non-Rooted
**Will update guide with method to install Launcher Hijack from the FireTV itself.**
Tested on:
- FireTV 1 Box - Rooted with Bootloader fully unlocked.
- On PreRooted Fire OS 5.2.6.6 (617513220)
- Running without SuperSU which means NO Root access except in TWRP.
- Basically it runs like on stock FW with the option to enable root.
- Should be the same for all other FireTV's on FireOS 5 that have the Accessibility option in Settings.
Installation (Based on the Launcher Hijack GitHub Guide):
ADB Code Method
Navigate to this GitHub's downloads page (https://github.com/BaronKiko/LauncherHijack/releases) on your desktop/laptop and download the latest APK.
Install ADB on your desktop/laptop (Google will help you) and ensure a connection to your Fire TV.
Install Launcher Hijack with this command:
adb install <path to downloaded APK>
Click to expand...
Click to collapse
Ensure you have some Launchers installed.
Enable the Accessibility Service using these two commands (exactly in this order):
adb shell
Code:
settings put secure enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Then...
Code:
settings put secure accessibility_enabled 1
Click to expand...
Click to collapse
If this is a first/fresh install of LH (Launcher Hijack). LH will open.
Select your desired Launcher from the list provided
If you had previously opened LH & selected a desired Launcher.
Your previously chosen Launcher will open.
Reboot your device (Recommended but not required).
Congratulation, if all is working correctly your home button should now open your chosen launcher
Accessibility Toggle Method
Navigate to this GitHub's downloads page (https://github.com/BaronKiko/LauncherHijack/releases) on your desktop/laptop and download the latest APK.
Install ADB on your desktop/laptop (Google will help you) and ensure a connection to your Fire TV.
Install Launcher Hijack with this command:
adb install <path to downloaded APK>
Click to expand...
Click to collapse
Ensure you have some Launchers installed.
Enable the Accessibility Service using this command:
adb shell
Code:
settings put secure enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Click to expand...
Click to collapse
On your FireTV go to & click on [ Settings / Accessibility / Screen Magnifier ]
The Screen Magnifier instructions menu will popup.
Click on [ TURN OFF MAGNIFIER ].
If this is a first/fresh install of LH (Launcher Hijack). LH will open.
Select your desired Launcher from the list provided
If you had previously opened LH & selected your desired Launcher.
Your previously chosen Launcher should open.
Reboot your device
Congratulation, if all is working correctly your home button should now open your chosen launcher
Important, Accessing Settings and the Long Press Menu
Unfortunately for FireTV devices a compromise had to be made. To access the long press menu and with it settings you have to hold menu and home together. You can also get to the default launcher by simply pressing them together.
Troubleshooting
If you are having issues then there are some common issues you can check here:
Ensure you are using an Amazon TV device running Fire OS 5, compatible with all versions as of release (FW 5.2.6.7 = latest).
Ensure you have enabled the accessibility service with the command: adb shell settings put secure enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Ensure you can open your launcher directly i.e. Using any launcher, other than your chosen launcher, open you chosen launcher like any other app, this should open your chosen launcher.
Ensure you have selected your chosen launcher in Launcher Hijack.
Reboot your device after following all previous steps.
After clicking home initially wait 10 seconds and press home again. This happens when your chosen launchers process gets killed in the background and may happen from time to time, especially after a reboot. There are plenty of existing apps that already keep a chosen application in memory so try one of those if this is a reoccurring issue for you.
If all else fails try using one of the following launchers with known compatibility: AppStarter or HALauncher.
now, any working solution to keep the launcher in memory?
Y314K said:
Guide for FireTV's on FireOS 5 FirmWare v.05
This guide should work on all FireTV devices on any FireOS 5. Rooted & Non-Rooted
**Will update guide with method to install Launcher Hijack from the FireTV itself.**
Tested on:
- FireTV 1 Box - Rooted with Bootloader fully unlocked.
- On PreRooted Fire OS 5.2.6.6 (617513220)
- Running without SuperSU which means NO Root access except in TWRP.
- Basically it runs like on stock FW with the option to enable root.
- Should be the same for all other FireTV's on FireOS 5 that have the Accessibility option in Settings.
Installation (Based on the Launcher Hijack GitHub Guide):
Navigate to this GitHub's downloads page (https://github.com/BaronKiko/LauncherHijack/releases) on your desktop/laptop and download the latest APK.
Install ADB on your desktop/laptop (Google will help you) and ensure a connection to your Fire TV.
Install Launcher Hijack with this command:
Ensure you have some Launchers installed.
Enable the Accessibility Service using this command:
On your FireTV go to & click on [ Settings / Accessibility / Screen Magnifier ]
The Screen Magnifier instructions menu will popup.
Click on [ TURN OFF MAGNIFIER ].
If this is a first/fresh install of LH (Launcher Hijack). LH will open.
Select your desired Launcher from the list provided
If you had previously opened LH & selected your desired Launcher.
Your previously chosen Launcher should open.
Reboot your device
Congratulation, if all is working correctly your home button should now open your chosen launcher
Important, Accessing Settings and the Long Press Menu
Unfortunately for FireTV devices a compromise had to be made. To access the long press menu and with it settings you have to hold menu and home together. You can also get to the default launcher by simply pressing them together.
Troubleshooting
If you are having issues then there are some common issues you can check here:
Ensure you are using an Amazon TV device running Fire OS 5, compatible with all versions as of release (FW 5.2.6.7 = latest).
Ensure you have enabled the accessibility service with the command: adb shell settings put secure enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Ensure you can open your launcher directly i.e. Using any launcher, other than your chosen launcher, open you chosen launcher like any other app, this should open your chosen launcher.
Ensure you have selected your chosen launcher in Launcher Hijack.
Reboot your device after following all previous steps.
After clicking home initially wait 10 seconds and press home again. This happens when your chosen launchers process gets killed in the background and may happen from time to time, especially after a reboot. There are plenty of existing apps that already keep a chosen application in memory so try one of those if this is a reoccurring issue for you.
If all else fails try using one of the following launchers with known compatibility: AppStarter or HALauncher.
Click to expand...
Click to collapse
Many thanks for the detailed write up.
Can I just confirm that on the latest 4K firestick, there is no way to do the above without running the ADB commands? I recall using the launcher highjack on the 2nd Gen firestick WITHOUT running any ADB commands.
thanks again
Gosh that's a lot to break down.
Y314K said:
I do have a request. Is there any chance you can take a look at keeping Launcher Hijack as it's own app. But also can you please take a look to see if you can create a fork of a merger of your Launcher Hijack latest version & the last GitHub release of AppStarter v4.0 (Found @ : https://github.com/sphinx02/AppStarter ). AppStarter is the best launcher for FireTV devices. But it is due for an update/upgrade. Adding your Launcher Hijack code would be great. Also updating the SPMC & Kodi link changes would be great.
Click to expand...
Click to collapse
Merging the code into AppStarter would be a lot of work with no real benefit. Simply install them both separately and select AppStarter in Launcher Hijack. Also as I said in a previous post I honestly don't use my Fire TV so I don't really want to maintain AppStarter. I see more use in making the Fire TV a dedicated kodi/plex box with Launcher Hijack anyhow.
Y314K said:
Also merging other opensource projects like On Boot AppStarter (Found @: https://bitbucket.org/Mirakel/onbootappstarter/src would be another).
Click to expand...
Click to collapse
On Boot AppStarter is just a broadcast receiver which this app already uses to start on boot. Again there would be no benefit to a merge as it's not related to Launcher Hijack.
Y314K said:
Another of the major things that will need change/updating is what the Settings button (The 3 lines button to the right of the Home button) does in AppStarter vs Launher Hijack. Since right now trying to open the FireTV long press Settings also opens the AppStarter App FireTV Settings popup. Giving you an extra thing to close after coming back from the long press Settings menu.
Click to expand...
Click to collapse
Unfortunately this is the best compromise I could make and it effects whatever app you happen to have open. I chose this because generally the menu press is something easy to cancel (as you said you just press back or menu again). I could cache the menu press and activate it with a delay but that could break applications that depend on long press of the menu button (don't know any apps that do that but it's possible) so it's just not worth it. It would also be a whole lot of work when I'm busy trying to get another job as I tend to like eating.
Y314K said:
The ADB command is still needed first. Then the only accessibility option that needs toggling is "Screen Magnifier". Just toggle the setting like you are going to turn it on. The instructions screen should popup. Then just choose "TURN OFF MAGNIFIER" at the instructions screen. Hitting "TURN OFF MAGNIFIER" will opens up Launcher Hijack v4. There you can choose AppStarter or your chosen launcher. Then you are all set.
Right. It seems FireOS v5 devices need a two-step setup. In correct order both the ADB command & a ACCESSIBILITY Menu Toggle (Screen Magnifier ONLY) are needed for it to proper register everything. The good news is that it only needs to be done once. And it survives a FireTV reboot. Bad news is that if you deliberately stop the Launcher Hijack App. Then you have to do do the two step setup again.
Click to expand...
Click to collapse
That's totally bizarre, no idea why that would be the case. My assumption is the settings aren't being applied for whatever reason after the command. Would really like a purely adb solution.
Y314K said:
I also tried dropping the "secure" from the adb command but got he following results:
Run Code:
Code:
settings put enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
And
settings enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Both gave the following return:
Code:
ty_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ <
Invalid namespace 'enabled_accessibility_services'
usage: settings [--user NUM] get namespace key
settings [--user NUM] put namespace key value
settings [--user NUM] delete namespace key
'namespace' is one of {system, secure, global}, case-insensitive
If '--user NUM' is not given, the operations are performed on the owner user.
[email protected]:/ $
Let me know if I should test anything else regarding this.
Click to expand...
Click to collapse
Ok it's under secure then, I assume you don't get an invalid namespace error for the original command?
Oh boy there's a whole other post I didn't see before getting this far. Wont quote it as it's really long but I'm glad to see you have a reliable way to set it up. I found this command that may help if run first:
Code:
settings put secure accessibility_enabled 1
No idea if it will fix the issue I just saw it mentioned in a post over here: https://autotools.helprace.com/i98-control-accessibility-via-secure-settings It does seem like your trick could set this variable allowing it to work, I just don't know. Regardless I will update the instructions with your findings so others don't have such issues.
krsmit0 said:
Great, thanks. I wasn't sure what exactly was working, but i spent sometime on both sticks until it worked. I am on fireos 5 on both sticks. I think the issue i have now is i keep ending up back on the fire tv launcher. i think hijack or my launcher choice (TVLauncher) are getting kicked out of memory. Other then that this feels extremely stable and very consistent.
Click to expand...
Click to collapse
Launcher Hijack is a service so it shouldn't ever be ousted from system memory. It is possible but if it ever does happen then it calls my close function (there so code can wrap up) and the code simply starts a new instance. If it went down you would have to disable then enable the service via adb or reboot. If you just have to press home again it's the launcher. After some Googling there are "sticky intents" that may help but apparently they are not great to use as they can cause memory issues. It leads to the fundamental issue, is it a smart thing to fix? These devices don't have a lot of memory to begin with and the fact that your launcher is getting killed means the device has run out. In that case I would say the right thing to do is to kill the launcher an it can be started again later and it's better that what you are doing lagging badly.
If I find some time, big if there, I can see if sticky intents are the magic they seem to be, honestly I'm doubtful but, if so I can put it as an option via settings. Right now your best bet is to use a light weight launcher or simply press home again.
Been writing this for an hour now -_-
But finally can one of you with a Fire TV (or stick) running Fire OS 5 check that the settings menu in Launcher Hijack has "Hardware Button Detection", "Broadcast Receiver Detection" and "Disable while menu held" checked by default and the others off. You can load the defaults with the menu if you changed any of the options. Just want to make sure that the defaults are correct for your device.
Yet another post:
Intenti0n said:
Many thanks for the detailed write up.
Can I just confirm that on the latest 4K firestick, there is no way to do the above without running the ADB commands? I recall using the launcher highjack on the 2nd Gen firestick WITHOUT running any ADB commands.
thanks again
Click to expand...
Click to collapse
You can enable "Overlay Detection" in the Launcher Hijack settings to get it working like the old Launcher Hijack but it's just not as good and you can't use the long press menu so I don't suggest it.
krsmit0 said:
now, any working solution to keep the launcher in memory?
Click to expand...
Click to collapse
Have not had experience on this. I still use AppStarter v4.0. Which seem to be pretty good at staying in memory. Specially since I also use [NOROOT] On Boot AppStarter v1.0. For it to load on Boot. I don't remember it ever being closed. Unless I choose to close it.
Intenti0n said:
Many thanks for the detailed write up.
Can I just confirm that on the latest 4K firestick, there is no way to do the above without running the ADB commands? I recall using the launcher highjack on the 2nd Gen firestick WITHOUT running any ADB commands.
thanks again
Click to expand...
Click to collapse
Seems to be a new method found by the developer to work with the changes that Google/Amazon have made between FireOS 5 & FireOS 6 (Google's base Android code usually has the biggest changes). Harder to do when your dealing with two different versions of Android.
Y314K said:
Have not had experience on this. I still use AppStarter v4.0. Which seem to be pretty good at staying in memory. Specially since I also use [NOROOT] On Boot AppStarter v1.0. For it to load on Boot. I don't remember it ever being closed. Unless I choose to close it.
Seems to be a new method found by the developer to work with the changes that Google/Amazon have made between FireOS 5 & FireOS 6 (Google's base Android code usually has the biggest changes). Harder to do when your dealing with two different versions of Android.
Click to expand...
Click to collapse
To be clear you don't need AppStarter, this app does that on it's own for the selected launcher. Appstarter simply uses very little memory so it rarely gets kicked. It's also super quick to boot so if it does get kicked it can usually start in time.
Also you should have enabled the accessibility service on the old version too, I just use it more now and disabled the old method be default as it causes issues when both methods are running in parallel.
You can enable "Overlay Detection" in the Launcher Hijack settings to get it working like the old Launcher Hijack but it's just not as good and you can't use the long press menu so I don't suggest it.
Click to expand...
Click to collapse
I have enabled the "Overlay detection" and rebooted. After rebooted, the HAL launcher starts up automatically.
However, when I press the home key on the remote, it goes back to the default launcher.
is that expected?
Intenti0n said:
I have enabled the "Overlay detection" and rebooted. After rebooted, the HAL launcher starts up automatically.
However, when I press the home key on the remote, it goes back to the default launcher.
is that expected?
Click to expand...
Click to collapse
It probably shouldn't do that but I'm gonna say that feature just isn't supported on fire TV's. It's for 2017 and earlier fire tablets and you just don't need it on the TV's.
BaronKiko said:
It probably shouldn't do that but I'm gonna say that feature just isn't supported on fire TV's. It's for 2017 and earlier fire tablets and you just don't need it on the TV's.
Click to expand...
Click to collapse
OK thanks, I will try the ADB method then

Categories

Resources