Related
EDIT: updated with step-by-step instructions.
Step 1. Download the Android SDK (http://developer.android.com/sdk/)
Step 2. Make sure to configure the ADB usb interface drivers (search the forums for more information on this if you're confused.)
Step 3. Plug your G1 into your computer (via usb). (Settings -> Application -> Development -> USB Debugging, must be enabled [it is enabled by default in JesusFreke releases i think])
Step 4. Open command prompt and enter the following:
Code:
> adb -d shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=0 where name='lock_pattern_autolock';
sqlite> .exit
# exit
Step 5. Now power off the phone, and turn it back on. Tada! No more pattern lock.
Sorry, Im speaking on behalf of the simpler folk, but how exactly do you go about doing this, and if so can you make an update.zip that would do this?
hey haykuro, probably you should post this in the development sub-forums..
anyways great stuff man..the code looks so simple lol..i am sure you toiled hard tho!
thanks again.
Joeriginal said:
Sorry, Im speaking on behalf of the simpler folk, but how exactly do you go about doing this, and if so can you make an update.zip that would do this?
Click to expand...
Click to collapse
None of this is done on the phone itself. It's done using the adb utility for your computer. Just download the adb.exe file and the USB drivers then repeat the commands shown above at your command prompt.
whats the point of this?
The Great NY said:
whats the point of this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=485903
Yay! Now I can finally use that stolen G1!
J/k I already got rid of the previous owner's account by flashing DREAIMG.NBH
(No, I did not really steal a G1 )
interesting to know
thx.
Could be useful if you forget your own pattern Maybe we can remove the regular lock screen now?
As a follow-up, how difficult would it be to replace the regular lock screen with a different one (non-pattern based)? I struggle with the pattern one, because it's pretty easy for anybody to hold the phone up to the light to see the pattern. Would be useful to have a different, more secure lock screen.
That would be awsome if you could get rid of the first unlock with hitting menu
ICBM said:
As a follow-up, how difficult would it be to replace the regular lock screen with a different one (non-pattern based)? I struggle with the pattern one, because it's pretty easy for anybody to hold the phone up to the light to see the pattern. Would be useful to have a different, more secure lock screen.
Click to expand...
Click to collapse
what the hell are you talking about? hold the phone up to the light to see a DIGITAL screen unlock pattern? maybe if you leave giant greasy fingerprints all over the screen...
Yes that's exactly right. The low-tech, looks at the fingerprint pattern works like a charm. Don't believe me? Try it yourself. I don't consider myself particularly greasy, but if you use the G1 as is, without screen covers or anything, you can usually see enough to figure out what the unlock pattern is.
cboy007 said:
what the hell are you talking about? hold the phone up to the light to see a DIGITAL screen unlock pattern? maybe if you leave giant greasy fingerprints all over the screen...
Click to expand...
Click to collapse
That's what he meant. And it's very plausible to do, even if your fingers are a little greasy. Try it.
This is nothing revolutionary. All you are doing here is hitting the "Require pattern" switch to off, just doing it the more "intrusive" method.
This is not any sort of insight to replacing the lock activity.
as far as that goes, you'd have to completely rebuild the OS.
Code:
>adb shell logcat -d V | grep -i lock
D/KeyguardViewMediator( 54): wakeWhenReadyLocked(82)
D/KeyguardViewMediator( 54): pokeWakelock(10000)
D/KeyguardViewMediator( 54): pokeWakelock(7000)
D/KeyguardViewMediator( 54): pokeWakelock(10000)
D/KeyguardViewMediator( 54): pokeWakelock(5000)
D/KeyguardViewMediator( 54): pokeWakelock(7000)
this is the action of turning on the screen.
for further information on REPLACING the lock screen you can follow up in this thread http://groups.google.com/group/andr...b512cb203b/8324f7ff7ed232b3?#8324f7ff7ed232b3 (this is just one of the many i googled up.)
yea.. another issue with the lock is that as it may be confusing and magical to a non G1 user.. but i tell you.. .. if a g1 user sees you put your code in... its easily retained to the "allready used it, understand how it works" mind.
two things: since you enter an adb shell does this mean you can do this from a terminal on the phone?
also, cool thing i found,
first you need to have an unlock code set
then you need to have mybackup from the market,
create a backup up of your system settings
do a wipe/factory reset (i dont know if you had to but thats what i did when it happened to me)
now restore your system settings
now you will have an unlock screen that opens with ANY pattern even if its only one dot
haitiankid4lyf said:
two things: since you enter an adb shell does this mean you can do this from a terminal on the phone?
Click to expand...
Click to collapse
yes. but if you are on the terminal of the phone, i'd guess you wouldn't need to bypass the lock screen now would you?
haitiankid4lyf said:
also, cool thing i found,
first you need to have an unlock code set
then you need to have mybackup from the market,
create a backup up of your system settings
do a wipe/factory reset (i dont know if you had to but thats what i did when it happened to me)
now restore your system settings
now you will have an unlock screen that opens with ANY pattern even if its only one dot
Click to expand...
Click to collapse
cool
i got a quick question, if the phone is locked out how do u get into the settings to turn on usb debugging
wesgarner said:
i got a quick question, if the phone is locked out how do u get into the settings to turn on usb debugging
Click to expand...
Click to collapse
haykuro said:
Step 3. Plug your G1 into your computer (via usb). (Settings -> Application -> Development -> USB Debugging, must be enabled [it is enabled by default in JesusFreke releases i think])
Click to expand...
Click to collapse
Just update the phone using JF v1.42 update.zip and you should be good to go
If you remove the HTC Lock Screen the screen no longer turns on when you plug it in or unplug it
(Make sure and reboot after removing it)
^ Shift Faced
Removing the lock screen is the only way to go. I just wish there was a way to remove the default pull down answer screen when the phone is in lock mode. Half the time it takes me 10 swipes before the phone answers, I hate the sense side down answer.
How do I remove it?
you have to be rooted, but once you are it's fairly straightforward. you need to open up the adb shell, and from there type in:
Code:
rm system/app/HtcLockScreen.apk
the first time I tried, it told me permissions denied, even with su in front, so added busybox to the front of the command:
Code:
busybox rm system/app/HtcLockScreen.apk
and make sure you reboot your phone!
I think your alarm clock may not be able to be silenced/snoozed if you remove this. You will probably have to use a different one from the market.
that is rather annoying, thanks for the heads up >.<
anybody who has clockwork mod2.5 (green version) can download the Vanilla lockscreen .zip from the AwesomeRom thread and it will remove HTCLockscreen and the alarmclock and another one of the apps that stops working and replaces them with the vanilla alternative.
just thought you should know. works on both deodexed roms and odex roms.
I disabled the lockscreen a while ago. It worked okay but sometimes the graphics on the lock sliders flaked out or were missing until you touched the screen. I went back.
Many times when I pull the phone out of my pocket while its ringing I slide it up or down. Most of the time dropping the call.
griffindy said:
you have to be rooted, but once you are it's fairly straightforward. you need to open up the adb shell, and from there type in:
Code:
rm system/app/HtcLockScreen.apk
the first time I tried, it told me permissions denied, even with su in front, so added busybox to the front of the command:
Code:
busybox rm system/app/HtcLockScreen.apk
and make sure you reboot your phone!
Click to expand...
Click to collapse
I'm lazy and just removed it with Titanium.
^ Shift Faced
jesusice said:
I'm lazy and just removed it with Titanium.
^ Shift Faced
Click to expand...
Click to collapse
I removed with Titanium, but I like the generic lock screen even less. I backed up the HTC Lockscreen with Titanium, but can't restore.. It has check with backup date.. Any easy way back?
Removing stock lockscreen + installing WidgetLocker 1.2.4 =
I managed to get the stock Sense lock screen back. Retrieved the apk from a Rom. Moved it to the Titanium backup folder, restored it..
so its confirmed that you cant shut the htc alarm clock off if you remove the lockscreen? can you still shut if off through the alarm app or when you unlock the screen?
t0esh0es said:
so its confirmed that you cant shut the htc alarm clock off if you remove the lockscreen? can you still shut if off through the alarm app or when you unlock the screen?
Click to expand...
Click to collapse
Yes, I have no issue turning mine off. All I have to do is unlock the screen and the notification is up.
In this Noob Series we explore How To Change the Kindle Fire Lock Screen and Eliminate the Annoying Double Lock Screen. When you complete this Tutorial you will be able to have the Lock Screen look the way you want it to look. The software we use to replace the Kindle Fire Lock Screen is Magic Locker. We decided on Magic Locker since it is well supported and it offers several hundres Themes, so the Lock Screen can look the way you want it to look. If you do not like to work on the Kindle, our new software, Kindle Fire First Aide will automate this process in the next version - Production Version 4.2.4. You can obtain a copy of the software here: http://forum.xda-developers.com/showthread.php?t=2096888 - Version 4.2.4 will Root your Kindle Fire, Install Google Play, Install Google Apps, Install this Custom Locker, Automated ADB Driver Install and an Additional 40 other Automated Operations! We attempt to keep this tutorial updated regularly - adding information from the end users experience. We have recently upgraded the storage servers to increase uptime, you now have two options for the downloads both are ad free. Option one is a Dropbox Storage Server and Option two is a Ubuntu One Storage Server, if one is under maintenance you may use the other download link. When you are done with the tutorial, please take the time to post feedback, this is very important to us - without your feedback, we have no way of knowing if we are doing our job. Finally, if you feel we did a decent job, please think about donating to us using the "Donate to Me" button - this is how we make a living, without your kind donations we would no longer be able to do this for a living.
If you prefer and are into your own custom Photos you may edit the photos in the original Kindle Fire HD and 2 Lock Screen. This requires a solid knowledge of Photoshop or some other picture editor like GIMP that can change the photo size to 1280x800. If this is your preference, move down to Post #2 below. Post #1 will allow you to do just about anything to the Locker and you do not need Photo Editor knowledge plus Post #1 supports over 1000 Themes.
Prerequisites:
1. Kindle Fire HD 7", Kindle Fire HD 8.9" or Kindle Fire 2
2. Rooted Kindle: http://forum.xda-developers.com/showthread.php?t=2069117
3. Google Play: http://forum.xda-developers.com/showthread.php?t=2069329
Custom Locker Step 1. Using Google Play, search for "No Lock". Download and Install No Lock - You may use this link to verify the software: https://play.google.com/store/apps/details?id=org.jraf.android.nolock&hl=en
Custom Locker Step 2: DO NOT Open No Lock, it will fail. Next, go to the Kindle, open up ES File Explorer or Root Explorer
Custom Locker Step 3: Be sure to enable Superuser on ES File Explorer. Navigate to /data/app, find org.jaf.androidnolock-1.apk - long press on the APK, select Move or Move To. Next, Move org.jaf.androidnolock-1.apk from /data/app to /system/app.
Custom Locker Step 4: Next find org.jaf.androidnolock-1.apk in /system/app. Long press and Choose Permissions (on Root Explorer) or Properties (on ES File Explorer). Change the Permissions to: Owner: Read Write Group: Read Others: Read - Click OK to apply the Permissions.
Custom Locker Step 5: DO NOT Open No Lock. Pull down the Upper Status Bar, Select More+, Select Sounds & Display and change the Screen Timeout to: Never and then reboot the Kindle.
Custom Locker Step 6: Once the Kindle is back to the desktop, open No Lock which is found in the Kindle Apps, select "Locking disabled".
Custom Locker Step 7: Using Google Play Search for MagicLocker Main which you can find here: https://play.google.com/store/apps/details?id=mobi.lockscreen.magiclocker - Download and Install Magic Locker Main
Custom Locker Step 8: Be sure to enable Superuser on ES File Explorer. Navigate to /data/app, find mobi.lockscreen.magiclocker-1.apk - long press on the APK, select Move or Move To. Next, Move mobi.lockscreen.magiclocker-1.apk from /data/app to /system/app.
Custom Locker Step 9: Next find mobi.lockscreen.magiclocker-1.apk in /system/app. Long press and Choose Permissions (on Root Explorer) or Properties (on ES File Explorer). Change the Permissions to: Owner: Read Write Group: Read Others: Read - Click OK to apply the Permissions.
Custom Locker Step 10: Using Google Play Search for MagicLocker Theme - Download and Install a few Themes that interest you. I use Starry lock screen and Jelly Bean lock screen.
Custom Locker Step 11: Launch MagicLocker Main, click on Next, Next, Next - You will now see a popup, click Next and choose Clear Defaults until it Grays Out, click on the picture of a house (Home Button), you will be asked which Launcher to Use, you choose MagicLocker Main <Select Default>.
Custom Locker Step 12: Launch MagicLocker Main, sometimes you are taken to your regular Launcher App, if this happens repeat Step 11. Select "Lost Robot Music" and click Apply. Next MagicLocker applies the Theme and asks if you would like to Customize it, answer Yes or No depending on your interests. I selected No so we can move on. You can always customize it latter.
Custom Locker Step 13: Next MagicLocker will show you an example of the Theme. Unlock it by pulling down the circle in the Android Picture.
Custom Locker Step 14: Now we need to customize the way MagicLocker reacts when you unlock to the Left which is a Phone Call and when you unlock to the Right which is a SMS Application. Unlock straight down just unlocks the screen.
Custom Locker Step 15: OK, lock the Kindle by depressing the Power Button for 1 brief Second until the screen turns black. Depress the Power Button briefly again, you will see the lock Screen. Unlock to the Right, next you are asked which is your SMS Software, I use Go SMS Pro. Check the Box to "Always use this application". Unlock to the Left, next you are asked which is your Phone Software, I use Google Voice and Groove. Check the Box to "Always use this application".
Custom Locker Step 16: Next, let's install the Themes. Find the name of the Themes you downloaded in Step 8. In this example we picked Starry lock screen and Jelly Bean lock screen. So go into the Apps. Find Starry lock screen, click on Starry lock screen and select "Install this theme". The installer will process and you will be back at the MagicLocker main Theme Menu. Exit MagicLocker, then go to Apps, find Jelly Bean lock screen, click on Starry lock screen and select "Install this theme". The installer will process and you will be back at the MagicLocker main Theme Menu.
Custom Locker Step 17: Now we need to let MagicLocker know what is your Default Launcher, so launch MagicLocker, find Preferred Home Launcher, click on Preferred Home Launcher and select your Launcher, we use Nova Launcher Prime.
Custom Locker Step 18: Let's eliminate the Ads from ever appearing again. Open either ES File Explorer or Root Explorer, navigate to /system/app find the dtcp_apk.ap, long press dtcp_apk.apk select Rename. Rename dtcp_apk.apk to dtcp_apk.old.
Custom Locker Step 19: Reboot the Kindle.
Custom Locker Step 20: Whenever you reboot, the Kindle Fire Framework starts before anything else, so you may see the Kindle lock screen at Reboot IF you do not let everything start. If you can not wait 5 to 10 minutes, unlock it and let all the services start, usually 10 minutes is sufficient. Once you unlock it, you will notice there are no more Ads! After 10 minutes No Lock Service kicks in and disables the Kindle Fire Lock Screen. We have attempted to play with the start-up timing and ended up with Framework missing, so Amazon was smart when they thought out this function. Also, the service that controls the lock screen is part of the same group that displays the Kindle Framework when you unlock it. Finally, if you do wait 10 minutes you will never see the old Kindle Fire Lock Screen!
That is it! Next we will offer you a solution with the stock lock screen but you will need high resolution photos to make it function properly. Be sure to look at our new Backup and Recovery Software for the Kindle Fire Series: http://forum.xda-developers.com/showthread.php?t=2096888
[HOW TO] Keep The Original Kindle Fire Lock Screen and Change The Photos
Reserved for new tutorial
add an "r"
... to https://play.google.com/store/apps/d...een.magiclocke
prokennexusa said:
Reserved for new tutorial
Click to expand...
Click to collapse
Whenever I try to open magic locker main I get the force closed error message?
I'm using NovaLauncher could this perhaps affect it?
Edit: Actually I rebooted the KFHD and the problem went away! Good guide thanks
Thank you for the tutorial, ill give it a whack tomorrow. The slide lock doesnt bother me much,i actually prefer it... but i wanna disable it just because i wanna have full control of my device. Take that amazon!
please delete. question was answered already once reread.
Thank you for this guide. I took the Golocker instead of the Magiclocker and it worked as a charm as well.
The only issue I still have, is the “star“ favorite button in the lower right corner. Although the “home“ button has been disabled within the locker software, the star is still active. Think, it's the same with Magiclocker, isn't it?
Soft keys?
nakedtruthishere said:
Thank you for this guide. I took the Golocker instead of the Magiclocker and it worked as a charm as well.
The only issue I still have, is the “star“ favorite button in the lower right corner. Although the “home“ button has been disabled within the locker software, the star is still active. Think, it's the same with Magiclocker, isn't it?
Click to expand...
Click to collapse
Are you referring to the soft keys? There's a nifty fix for that pesky soft key bar. Get rid of it! ...
I used this method. It works great! Just follow the directions carefully.
Yes, I am referring to the lower right soft key. But - I'm glad with it (honestly I'm used to it) and don't want to change the bar.
A possible solution is to empty the favorite function, but maybe there is another one...
Gave this a whirl last night. Sweet. Thanks for this tutorial. After following the instructions in the OP I waited at least ten minutes for all the services to start. I am finding during a reboot the Kindle lockscreen appears; no ads. Unlock and use as normal. It is after the Kindle enters sleep mode then the Magiclocker lockscreen appears and I never see the Kindle lockscreen. Is this functioning correctly. I may have mis-read but thought the Kindle lockscreen will never appear (presumed this to be true after rebooting as well).
blklab49 said:
Gave this a whirl last night. Sweet. Thanks for this tutorial. After following the instructions in the OP I waited at least ten minutes for all the services to start. I am finding during a reboot the Kindle lockscreen appears; no ads. Unlock and use as normal. It is after the Kindle enters sleep mode then the Magiclocker lockscreen appears and I never see the Kindle lockscreen. Is this functioning correctly. I may have mis-read but thought the Kindle lockscreen will never appear (presumed this to be true after rebooting as well).
Click to expand...
Click to collapse
There's a chance that on reboot the original lock screen will appear. You should see it when the dpi is below 180.
Way to still view offers without lock screen
This worked great for me thanks. I am wondering though if there is a way to view offers under the offers section with the amazon launcher, but not in the lock screen. I wouldn't mind knowing some of the special offers when they are books.
Thanks
Link Error
Krsmqn said:
... to https://play.google.com/store/apps/d...een.magiclocke
Click to expand...
Click to collapse
Krsmqn,
Thank you for pointing out the mistake. we just fixed the link, thanks Krsmqn!
Magic Locker Force Closes
Callum77 said:
Whenever I try to open magic locker main I get the force closed error message?
I'm using NovaLauncher could this perhaps affect it?
Edit: Actually I rebooted the KFHD and the problem went away! Good guide thanks
Click to expand...
Click to collapse
Callum77,
Yes, we are aware of this problem. If you Open Magic locker before we instruct you to do so, it breaks Magic Locker. This is why we state to NOT open Magic Locker until we instruct you to open it. We use Nova Launcher as well, it works beautifully with Nova Launcher.
Please DO NOT open Magic Locker until you are instructed to open the application.
Follow Up - Feedback
drugfreejonnyxxx said:
Thank you for the tutorial, ill give it a whack tomorrow. The slide lock doesnt bother me much,i actually prefer it... but i wanna disable it just because i wanna have full control of my device. Take that amazon!
Click to expand...
Click to collapse
drugfreejonnyxxx,
Thank you for taking the time to post your comments drugfreejonnyxxx. I can completely understand and agree, I too want full control of our Kindles!
Post Mistake
meddle70 said:
please delete. question was answered already once reread.
Click to expand...
Click to collapse
meddle70,
No worries meddle70!
Kindle Fire HD and 2 - Go Locker Option
nakedtruthishere said:
Thank you for this guide. I took the Golocker instead of the Magiclocker and it worked as a charm as well.
The only issue I still have, is the “star“ favorite button in the lower right corner. Although the “home“ button has been disabled within the locker software, the star is still active. Think, it's the same with Magiclocker, isn't it?
Click to expand...
Click to collapse
nakedtruthishere,
I am glad you used this thread with your preferred software. That is the idea, to spark someone to do something different.
I do have to say, Magic Locker will force the Kindle locker to diable, I am not sure if Go Locker will perform the same task. Post your results when done.
No, Magic Locker does not disable the Home button. Magic locker uses the Home button directly and routes your Launcher through Magic Locker.
Kindle Fire Buildprop Edits
Krsmqn said:
Are you referring to the soft keys? There's a nifty fix for that pesky soft key bar. Get rid of it! ...
I used this method. It works great! Just follow the directions carefully.
Click to expand...
Click to collapse
Krsmqn,
Now I see why you wanted the Factory USB Cable! Anyone who plays with the build.prop file needs backups! You should see your cable in a couple of days. Did you get a tracking number from Paypal?
Does Magic Locker Disable The Home Button? No!
nakedtruthishere said:
Yes, I am referring to the lower right soft key. But - I'm glad with it (honestly I'm used to it) and don't want to change the bar.
A possible solution is to empty the favorite function, but maybe there is another one...
Click to expand...
Click to collapse
nakedtruthishere,
I have been thinking about it, Go Locker will not work like Magic Locker. You see, Magic Locker manages the overall Framework, thus Blacklisting any application from attempting to lock the screen. Maybe you can integrate the Home button into Go Locker? Magic Locker leaves the Home button in tact.:good:
Kindle Fire HD and 2 Original Lock Screen Behavior
blklab49 said:
Gave this a whirl last night. Sweet. Thanks for this tutorial. After following the instructions in the OP I waited at least ten minutes for all the services to start. I am finding during a reboot the Kindle lockscreen appears; no ads. Unlock and use as normal. It is after the Kindle enters sleep mode then the Magiclocker lockscreen appears and I never see the Kindle lockscreen. Is this functioning correctly. I may have mis-read but thought the Kindle lockscreen will never appear (presumed this to be true after rebooting as well).
Click to expand...
Click to collapse
blklab49,
The Kindle Lock screen will appear on the first boot if you quickly unlock it, after this first reboot Magic Locker takes over and you should never see the Kindle Lock screen unless you quickly unlock it after a reboot. Magic Locker is a service, so it has to initialize which take a few seconds after startup. Having said this, if you reboot and quickly (1-2 seconds) attempt to unlock the Kindle you may see the old lock screen. After my first reboot, I never saw the Kindle Lock screen again, it is gone!
Thank you for taking the time to post your comments.
I have a rooted NST with Mod Manager, I checked the box to remove the swipe screen savers but it still shows up upon booting the device. Is there anyway to get rid of this first swipe?
collin_schupman said:
I have a rooted NST with Mod Manager, I checked the box to remove the swipe screen savers but it still shows up upon booting the device. Is there anyway to get rid of this first swipe?
Click to expand...
Click to collapse
Not sure about this because it may yield the same result, but there has been past mention in the forum of "No Lock" (PlayStore). This supposedly disables the lock screen and awakening would default to a press of the "N" button. Is that what you want?
Anyway, the PlayStore tells me that the app is not compatible with the NST although the Android level required is 1.5 and higher , so you'd need to get it elsewhere and sideload it to try it out. Clearly some forum members have gotten some version to work in the past.
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