For anyone wondering, Xposed does work on the Fire TV. I have a module that prevents the "Unknown controller" popup and I'll try to upload the apk soon if anyone is interested.
I was just wondering if the xposed framework would work on this, that's good news!
once we get the amazon crap off of this fireTV, man this thing just SCREAMS potential.
rbox said:
For anyone wondering, Xposed does work on the Fire TV. I have a module that prevents the "Unknown controller" popup and I'll try to upload the apk soon if anyone is interested.
Click to expand...
Click to collapse
Don't tease us!
YES, we want it!
I just want to replace the damn launcher. However once this gets the full treatment and we have a custom ROM available I may have to pic up some extra...
When I get home I'll upload the apk.
As for the launcher, I haven't found the code that launches it yet. But you could try pushing a new launcher to /system/app and see if that allows it to replace the Amazon one.
I just posted How to: Enable installations from "Unknown Sources". Should make installing XPosed modules a lot easier.
So the good news is I was able to create an extremely awful Xposed module that switches the default launcher. I'm going to try to figure out why exactly it insists on using the amazon launcher and maybe create a better way to override it. As for the unknown controller module, I got distracted by the launcher stuff, so I'll see if I can get that uploaded tomorrow.
rbox said:
So the good news is I was able to create an extremely awful Xposed module that switches the default launcher. I'm going to try to figure out why exactly it insists on using the amazon launcher and maybe create a better way to override it. As for the unknown controller module, I got distracted by the launcher stuff, so I'll see if I can get that uploaded tomorrow.
Click to expand...
Click to collapse
I want, I want, me, me, me. Are you going to put it in the Xposed repo?
I really need to look into making Xposed modules.
I don't think I'm going to post it to repo. I really hate all the one-off crap in it. I've looked more into how the launcher is started and I have a better understanding of why the Amazon one always runs. I've spent this night trying to get adbd running as root, so I haven't got much work done on the launcher stuff. Maybe tomorrow night.
Xbmc on the home launcher? Lol
Sent from my Galaxy Nexus using Tapatalk
LiquidXed said:
Xbmc on the home launcher? Lol
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'd rather have XBMC *as* the home launcher (need to edit intents for XBMC). All apps can be accessed from there.
elmerohueso said:
I'd rather have XBMC *as* the home launcher (need to edit intents for XBMC). All apps can be accessed from there.
Click to expand...
Click to collapse
I've thought about that, would probably be the best thing to do since i rarely leave xbmc
As long as XMBC registers an intent for:
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME"/>
My mod will use it as the launcher.
LiquidXed said:
Xbmc on the home launcher? Lol
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I sideloaded Llama and used it to redirect an app (one i don't use called classic tv) to open XBMC when started.
HERE IT IS:
There is a alternative way to invoke XBMC from the FTV Home Screen using Llama. This method uses a “sacrificial” app that you have installed from Amazon that you will use to access XBMC. The app can be anything you have installed but don’t need to use; however, some apps behave better than others (some apps will enter a loop when exiting XBMC). One app that has been tested and works well for this purpose is “Classic TV”.
The advantage of this method is that using the sacrificial app you have Home Screen Access to XBMC and you can exit XBMC to the FTV Home Screen just as you would any other FTV app.
4.1 Prerequisites
Llama side loaded on your FTV.
The app called “Classic TV” from the Amazon app store.
One Llama Event (described below).
4.2 Procedure
Install / side-load Llama.
Install “Classic TV” app from Amazon app store.
Launch Llama (From FireTV - Settings > Applications > Llama > Launch Application).
Go to EVENTS on top menu and click '+' to add a NEW EVENT.
In your NEW EVENT select ADD CONDITION then, from the Menu select 'Active Application' and select 'Choose App’. Scroll through the list of apps until you find “Classic TV” and select this app. Doing this should return you to the Events Menu.
Next, select ADD ACTION and select 'Run Application' from the Menu list. From here, select whatever the name of your XBMC build is. That should create your event. At this point you can also name your event to distinguish it from others.
Now when you start the “Classic TV” app from the Home Screen, it should automatically open XBMC. Feel free to experiment with other apps from the FTV app store. Just be aware that some will loop back and re-start XBMC when you try and exit XBMC to get back to the FTV Home Screen.
amberkalvin said:
I sideloaded Llama and used it to redirect an app (one i don't use called classic tv) to open XBMC when started.
HERE IT IS:
There is a alternative ....
Click to expand...
Click to collapse
Yea, you took this from the xbmc wiki... I think what we'd all like is to completely replace the Amazon launcher. When I hit the 'home' button on the remote, I would like it to take me to XBMC's main screen, not the amazon launcher
craftyguy said:
Yea, you took this from the xbmc wiki... I think what we'd all like is to completely replace the Amazon launcher. When I hit the 'home' button on the remote, I would like it to take me to XBMC's main screen, not the amazon launcher
Click to expand...
Click to collapse
Exactly. I want XBMC to open when I hit Home, but I still want to be able to open FTV Launcher, as an app, when I want to access the store.
---------- Post added at 02:29 PM ---------- Previous post was at 02:22 PM ----------
rbox said:
As long as XMBC registers an intent for:
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME"/>
My mod will use it as the launcher.
Click to expand...
Click to collapse
Do you need a tester?
rbox said:
As long as XMBC registers an intent for:
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME"/>
My mod will use it as the launcher.
Click to expand...
Click to collapse
Looking at the manifest.xml for xbmc, it does not register android.intent.category.HOME:
Code:
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
We'd need to rebuild xbmc after modifying the manifest
craftyguy said:
Yea, you took this from the xbmc wiki... I think what we'd all like is to completely replace the Amazon launcher. When I hit the 'home' button on the remote, I would like it to take me to XBMC's main screen, not the amazon launcher
Click to expand...
Click to collapse
craftyguy said:
Looking at the manifest.xml for xbmc, it does not register android.intent.category.HOME:
Code:
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
We'd need to rebuild xbmc after modifying the manifest
Click to expand...
Click to collapse
I build xbmc for a bunch of purposes and have my 13.1 modified to be launcher.. however pressing the home key never brings up the dialog to switch.. try it with any launcher from the app store.. same thing.. i can share it here if you guys want to try but it makes no diff..
http://www.datafilehost.com/d/b703a710
this is pretty much a straight git pull of 13.1 with manifest edits for launching and fusion/superrepo/unity come built in as sources and there are a few settings defaults in advancedsettings.xml.
mastafunk said:
I build xbmc for a bunch of purposes and have my 13.1 modified to be launcher.. however pressing the home key never brings up the dialog to switch.. try it with any launcher from the app store.. same thing..
Click to expand...
Click to collapse
Interesting, I wonder if Amazon somehow removed the option/ability for setting a default launcher other than their own?
Related
Hi everybody. I'm not sure if this is the right forum for asking this.
I'm developing an app that behaves like a kiosk mode, so I have a variable that indicates if I'm on kiosk mode or "normal mode". I have an Activity registered as category.HOME, which manages what should the app do, depending on the "kiosk mode" variable.
Manifest sample:
Code:
<activity
android:name="com.stuff.kiosklauncher.MainActivity"
android:exported="false"
android:label="@string/app_name"
android:launchMode="singleInstance"
android:stateNotNeeded="true" >
<!-- This tag indicates the initial activity -->
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
If I press the Home button on my Android phone, my MainActivity is called, and there if we are in kiosk mode, I do nothing, but if I I have the kiosk mode set to off, I look for the preferred launcher (stored in a variable called defaultlauncher), and call it at the onResume() with:
Code:
if(!kioskMode){
Intent startApp = new Intent();
ComponentName component = new ComponentName(
defaultLauncher.getPackageName(),
defaultLauncher.getClassName());
startApp.setComponent(component);
startApp.addCategory(Intent.CATEGORY_HOME);
startApp.setAction(Intent.ACTION_MAIN);
startActivity(startApp);
}
Seems to work ok, but it has some issues, as the "standard" launcher doesn't behave as it should (it doesn't scroll back to the main page when I'm on the desktop, for example... or flicks a little like trying to load my app's layout when pressing continuously the home button). So I'm not sure if I'm doing this right, maybe an Activity shouldn't be the place to lad or not the launcher, but I don't know if I can make a service or a broadcast receiver to be called when the home button is pressed.
I've seen a lot of apps that behave this way (like a launcher on top of another one), but I don't know how they do it.
Again, sorry if this is not the place to seek this kind of help, if that's the case, I'd love to know where should I go. If this is the place, please help. Thanks!
I think that you will not be able to start a service or broadcast receiver.
One idea (I do not know whether it works): Try overriding the onKeyDown and onKeyUp methods for the home button and return true.
Look at this: http://stackoverflow.com/questions/2079691/overriding-the-home-button-how-do-i-get-rid-of-the-choice (especially the second answer)
Thanks, I'll take a look to that!
I had made a kiosk browser app, and it worked perfectly.
My trick was using <activity-alias> tag, as well as some notifications to user mention that, they must select the app as default home launcher if they were in "kiosk" mode.
Moon.lSd said:
I had made a kiosk browser app, and it worked perfectly.
My trick was using <activity-alias> tag, as well as some notifications to user mention that, they must select the app as default home launcher if they were in "kiosk" mode.
Click to expand...
Click to collapse
In your kiosk mode, you had some way to "exit" from it without forcing the user to change the launcher? This would be exactly what I'm trying to achieve, could you provide a little more info? I'm not sure how I could use <activity-alias> here :/
Thanks
pnikosis said:
In your kiosk mode, you had some way to "exit" from it without forcing the user to change the launcher? This would be exactly what I'm trying to achieve, could you provide a little more info? I'm not sure how I could use <activity-alias> here :/
Thanks
Click to expand...
Click to collapse
Well, you can't change an activity intent filter, so you are unable to make a activity from launcher to non-launcher.
But if you are using activity-alias instead of activity, you can disable or enable intent filter of that alias, and thus, by using a shortcut key (like press back 5 times continously), you can exit kiosk mode, disable filter of the alias and default launcher will be automatically called without ask user to do that.
FYI: <activitiy-alias> is a tag in AndroidManifest, just like <activity>, but if <activity> points to a real Activity class, <activity-alias> point to another <activity> tag.
Moon.lSd said:
Well, you can't change an activity intent filter, so you are unable to make a activity from launcher to non-launcher.
But if you are using activity-alias instead of activity, you can disable or enable intent filter of that alias, and thus, by using a shortcut key (like press back 5 times continously), you can exit kiosk mode, disable filter of the alias and default launcher will be automatically called without ask user to do that.
FYI: <activitiy-alias> is a tag in AndroidManifest, just like <activity>, but if <activity> points to a real Activity class, <activity-alias> point to another <activity> tag.
Click to expand...
Click to collapse
Thanks! I'll take a look to that solution, I think I'm getting the idea.
what you can do is get the default launcher as soon as installing the app and store it locally then when the user fires your launcher activity just do what you want to and fire up the home intent directed to the package of previous default launcher this should do it .
If you are doing some heavy duty work then launch a service from the activity and dump your work there this i guess should do it
sak-venom1997 said:
what you can do is get the default launcher as soon as installing the app and store it locally then when the user fires your launcher activity just do what you want to and fire up the home intent directed to the package of previous default launcher this should do it .
If you are doing some heavy duty work then launch a service from the activity and dump your work there this i guess should do it
Click to expand...
Click to collapse
Thanks!
A quick question though, what do you mean by dumping the work in a service? I don't understand completely why and how should I do that.
My first approach was indeed, once I launch my app look for the current default launcher. I even added an option in my app in case the user wants to change the "regular" launcher (looking for the installed packages with the ACTIVITY_HOME filter). The problem is, when I call the intent to the previous launcher, it works ok but not completely. For example, if I'm on the "regular" desktop and I call the home button, it should display the desktop thumbails, or go back to the default desktop, but instead of that, it does nothing (a quick flicker sometimes, I guess because its calling again the activity).
pnikosis said:
Thanks!
A quick question though, what do you mean by dumping the work in a service? I don't understand completely why and how should I do that.
My first approach was indeed, once I launch my app look for the current default launcher. I even added an option in my app in case the user wants to change the "regular" launcher (looking for the installed packages with the ACTIVITY_HOME filter). The problem is, when I call the intent to the previous launcher, it works ok but not completely. For example, if I'm on the "regular" desktop and I call the home button, it should display the desktop thumbails, or go back to the default desktop, but instead of that, it does nothing (a quick flicker sometimes, I guess because its calling again the activity).
Click to expand...
Click to collapse
Working in activities is not proffered as it causes lag on low activity devices
Flickr is probably due the reason you gave that it's being called again and again from the activity
Sent from my GT-S5302 using Tapatalk 2
Hit Thanx Button if i helped you!
sak-venom1997 said:
Working in activities is not proffered as it causes lag on low activity devices
Flickr is probably due the reason you gave that it's being called again and again from the activity
Sent from my GT-S5302 using Tapatalk 2
Hit Thanx Button if i helped you!
Click to expand...
Click to collapse
I see. I think I have an idea on how I can approach this. Thank you all guys, lots of great ideas, you helped me a lot. Sorry I can hit the thanks button only once per message
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
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
Hello, this is my first topic.
I have an amazon firetvstick 2nd blocked my amazon. I have try to find away to set HALauncher as default here on this forum. I have find a way to do this.
thanks go to @rainman74 for his modified apk now you can use HALauncher as default launcher or select in Hijackv3
1. Install Hijack v3
https://github.com/BaronKiko/LauncherHijack/releases
2. Install HALauncher USE @rainman74 modified apk
https://forum.xda-developers.com/fire-tv/development/app-halauncher-fire-tv-t3762950
3. Install Target Home Launcher IGNORE THIS
https://mega.nz/#!gRN2jbqT!mFBoAPRGsAaRIbJWjJ2XyXW_A33q0u9K019iyIz-Nx4
open hijack an set as default launcher the app target home launcher, now when your press the home button target launcher should pop up as default and it you can select halauncher. IGNORE use modified apk
this is my fireTVstick 2nd interface
Have fun.
if you have any questions feel free to ask me
sorry for my english
I am not able to set target home launcher as default launcher with launcher hijack.
xhostluv said:
Hello, this is my first topic.
I have an amazon firetvstick 2nd blocked my amazon. I have try to find away to set HALauncher as default here on this forum. I have find a way to do this.
1. Install Hijack v3
https://github.com/BaronKiko/LauncherHijack/releases
2. Install HALauncher
https://mega.nz/#!NMlUADYB!7-yC0MVEmR89RTYYn_d4oQ1-B7iQ6uLpa1OEG_2pock
3. Install Target Home Launcher
https://mega.nz/#!gRN2jbqT!mFBoAPRGsAaRIbJWjJ2XyXW_A33q0u9K019iyIz-Nx4
open hijack an set as default launcher the app target home launcher, now when your press the home button target launcher should pop up as default and it you can select halauncher.
this is my fireTVstick 2nd interface
Have fun.
if you have any questions feel free to ask me
sorry for my english
Click to expand...
Click to collapse
Looks good thanks for sharing
Sent from my LG-H910 using Tapatalk
download link for my custom background for apps
https://mega.nz/#!kU92UJ6B!-oD4ZzPReKts0bylXBPdFTgk_j6tU9w1q2o_wJrS4Ts
keep in mind is small resolution 1200x765
if someone make other backgrounds app please share it here
pacorey said:
I am not able to set target home launcher as default launcher with launcher hijack.
Click to expand...
Click to collapse
update link in first post, use halauncher modified by rainman
I love the new setup. Its not so cluttered and "NO ADS"! Sorry for the glare of the window.
Can't activate HAlauncher to be the default Launcher. When I try to activate it in both apps "Hijack v3" and "target Home launcher" it gets back to the stock Amazon Launcher. I can start HALauncher manually.
I use a Fire Tv 2 with root
EDIT:
Works! Need to set another Launcher after "target home launcher" was the default launcher. After that, I can choose HALauncher as default launcher!
starmagoo said:
Can't activate HAlauncher to be the default Launcher. When I try to activate it in both apps "Hijack v3" and "target Home launcher" it gets back to the stock Amazon Launcher. I can start HALauncher manually.
I use a Fire Tv 2 with root
EDIT:
Works! Need to set another Launcher after "target home launcher" was the default launcher. After that, I can choose HALauncher as default launcher!
Click to expand...
Click to collapse
update.. link in first post, you can use HALauncher modified by rainman, target home launcher not needed anymore,
I am on FireOS 5.0.5 and this method does not work, the home button detection just does not work, I can set the default launcher but home button does not bring you to it!
Reni10 said:
I am on FireOS 5.0.5 and this method does not work, the home button detection just does not work, I can set the default launcher but home button does not bring you to it!
Click to expand...
Click to collapse
try thoe modified apk by raiman.. link in first post
xhostluv said:
try thoe modified apk by raiman.. link in first post
Click to expand...
Click to collapse
Yes I did try that one originally and still does not work, any other ideas?
Reni10 said:
Yes I did try that one originally and still does not work, any other ideas?
Click to expand...
Click to collapse
can you be more specific? Hijackv3 is recognizing HALauncher as a launcher?? can you select it? if not try with target home launcher...
give more details
xhostluv said:
can you be more specific? Hijackv3 is recognizing HALauncher as a launcher?? can you select it? if not try with target home launcher...
give more details
Click to expand...
Click to collapse
I have now tried on 2 separate 1st Gen fire TVs and neither works using your method.
You can select the modified Hal launcher in launcher hijack but when you press the home button it does NOT bring you to the Hal launcher only the normal FireTV launcher.
I can't be any more specific than that and also the same with Target Launcher, you can select it but it will not bring you to it when pressing the home button
Does this work with FireOS 5.2.6.2 ?
I have the same problem as Reni10.
how the hell do you customize the lists? if i select an app and click add it says select a target group, if i click the group and an app it says the same. If i click a group everything under that category comes
edit: nvm can't edit the default groups.
Reni10 said:
I have now tried on 2 separate 1st Gen fire TVs and neither works using your method.
You can select the modified Hal launcher in launcher hijack but when you press the home button it does NOT bring you to the Hal launcher only the normal FireTV launcher.
I can't be any more specific than that and also the same with Target Launcher, you can select it but it will not bring you to it when pressing the home button
Click to expand...
Click to collapse
the question would be, if the amazon launcher is being loaded in the background consuming RAM. For a alternative launcher, test the very slim "AppStarter 4.0". Keen to know if hijack works with the latest FireOS Updates
AppStarter -> https://forum.xda-developers.com/fire-tv/themes-apps/app-root-home-launcher-replacement-app-t3118135
Sometimes it works perfect and sometimes this tool don't work with the home button.
Fire Stick 2nd Gen.
Just published a new release with full support for Fire TV's: https://forum.xda-developers.com/fire-tv/general/launcher-root-launcher-hijack-v4-t3877467
This post still redirects a few people over every week so thought it was worth mentioning.
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