Database Users

[How-To] Block OTA Updates Without Root (or a router) on Fire OS 5

With the new Fire OS 5 update we can use the Debloater tool to disable APKs/services responsible for automatic updating. This was not previously possibly due to Fire OS 3 being built on Android 4.2.2 and the Debloater process needing Android 4.4.x+. No more worrying if your router is blocking everything properly. And of course... no root needed!
Disable Update w/o Root Steps:
1. Enable USB Debugging on your Fire TV (or TV Stick) (how-to here)
2. Setup adbFire on your computer and establish a connection to your Fire TV[Stick] (how-to here)
3. Setup Debloater tool (how-to here)
4A. In the Debloater tool, check off the APK below then hit the "Apply" button:
DeviceSoftwareOTA.apk (com.amazon.device.software.ota)
4B. Instead of using Debloater Tool you can just send the following ADB command:
Code:
adb shell pm hide com.amazon.device.software.ota
Unlike the pm disable command, hide disables the apk without root.
Click to expand...
Click to collapse
After hiding the apk your Amazon Fire TV or Fire TV Stick will no longer get OTA updates.
If you go into Settings > System > About you can no longer check for updates... yay.
To undo the block you can simply "unhide" each apk using the Debloater tool or run:
Code:
adb shell pm unhide com.amazon.device.software.ota
Click to expand...
Click to collapse
Be careful if you try to disable other system apps. If you disable something important and the device won't start up.. you'll have to perform a factory reset to fix the issue (not sure if possible with stick?). Have more apks to disable to reduce unneeded system processes? please share.
TL;DR
You gotta update to Fire OS 5.x in order to block updates without root (or router).
I know this defeats the purpose of blocking updates since you want to stay on old fw/sw... but science!
This may not work on all future Fire OS 5.x+ builds. Tested on FireTV Stick with Early Developer 5.0.3 build.

Thank you for this info.

Can anybody confirm this is working ? I have not received my AFTV2 yet.

Does this survive reboot?

Received my Firetv 2 and I can confirm it works, it even survives a reboot. To me this is the best method of blocking the Amazon updates.
Thanks mister LakituLives for writing this up

Does this work on the Firetv 1? Or only on the 4K fire TV. When I try to run debloater on the firetv 1 it keep saying unsupported. Thanks.

I assume you´re not running Fire OS 5 on the aTV 1. With Fire OS 3 this can´t be done this way.

slybas said:
Received my Firetv 2 and I can confirm it works, it even survives a reboot. To me this is the best method of blocking the Amazon updates.
Thanks mister LakituLives for writing this up
Click to expand...
Click to collapse
Can you run "pm list packages -d" from adb shell and paste the output? Does it do what @LakituLives describes which is give an error or otherwise not function as normal when you check for updates on the AFTV2?

I have done this and when i check for updates i get an error, don't know if it is working correctly.

zeroepoch said:
Can you run "pm list packages -d" from adb shell and paste the output? Does it do what @LakituLives describes which is give an error or otherwise not function as normal when you check for updates on the AFTV2?
Click to expand...
Click to collapse
Glad to help. The pm list packages -d (disabled packages) is empty because debloater hides the packages and not disables them.
Code:
[email protected]:/ $ pm list packages -d
pm list packages -d
[email protected]:/ $
There is nothing to see.
Code:
1|[email protected]:/ $ pm list packages | grep dcp
pm list packages | grep dcp
1|[email protected]:/ $ pm list packages | grep pico
pm list packages | grep pico
package:com.svox.pico
[email protected]:/ $
My version is now 5.0.3.1 because I unhid the packages and updated the machine, now the packages are hidden again and System --> About --> "installed Date" and "Last Checked" are both "Checking now......" and if I select Check for System Update I get an Update error. Perfect !

slybas said:
My version is now 5.0.3.1 because I unhide the packages and updated the machine, now the packages are hidden again and System --> About --> "installed Date" and "Last Checked" are both "Checking now......" and if I select Check for System Update I get an Update error. Perfect !
Click to expand...
Click to collapse
I get the same error now as well after running (as root):
Code:
pm disable com.amazon.device.software.ota
No idea if this actually blocks updates or just the checking. I guess we'll have to wait until the next update.

LakituLives said:
With the new Fire OS 5 update we can use the Debloater tool to disable APKs/services responsible for automatic updating. This was not previously possibly due to Fire OS 3 being built on Android 4.2.2 and the Debloater process needing Android 4.4.x+. No more worrying if your router is blocking everything properly. And of course... no root needed!
After hitting apply the Debloater tool should take a moment then show all apks "hidden" and your Amazon Fire TV or Fire TV Stick will no longer get OTA updates.
If you go into Settings > System > About you can no longer check for updates... yay.
You can simply "unhide" each apk using the Debloater tool if you should ever want to reverse this process.
Be careful if you try to disable other system apps. If you disable something important and the device won't start up.. you'll have to perform a factory reset to fix the issue (not sure if possible with stick?). Have more apks to disable to reduce unneeded system processes? please share.
TL;DR
You gotta update to block updates (without router or root).
I know this defeats the purpose of blocking updates since you want to stay on old fw/sw... but science!
And yes, Fire OS 5 makes the possibility of root even harder now that selinux is enabled.
Click to expand...
Click to collapse
Hi my firestick is running version 54.1.2.3_user_123067020 and it says it is not rooted and does not support block mode I have the latest version of deblocker and adbfire . windows 10

mifran said:
Hi my firestick is running version 54.1.2.3_user_123067020 and it says it is not rooted and does not support block mode I have the latest version of deblocker and adbfire . windows 10
Click to expand...
Click to collapse
You haven't updated to FireOS 5 which is required to use this.

Hmm, so fire tv stick didn't seem to get any root love other than soldering and man that stick is tiny for soldering. I'm debating if I want to let an update to latest then block. Anyone have any thoughts on if fire TV stick will ever get a software root?

Ludacrisvp said:
You haven't updated to FireOS 5 which is required to use this.
Click to expand...
Click to collapse
OK thanks I realised this now would updating to 5 mean re-installing kodi and firestarter and losing all the addons

Just chucked and there is no update for the UK version I have the latest installed
Sent from my Blade S6 using Tapatalk

mifran said:
OK thanks I realised this now would updating to 5 mean re-installing kodi and firestarter and losing all the addons
Click to expand...
Click to collapse
I didn't lose anything in my update from FireOS 3. If you revert from 5 to 3 then you have to lose everything.
mifran said:
Just chucked and there is no update for the UK version I have the latest installed
Click to expand...
Click to collapse
You have to opt-in for FireOS 5 from the Amazon developer account (free).

Thanks for the info will check it out
Sent from my Blade S6 using Tapatalk

I don't know if adbFire is connected, last night I was able to install FireStarter. This morning, I don't know if adbFire is connecting and Debloater isn't showing anything, or do I need to use USB to USB to do this?

Does this work on the Fire Stick? Also, what's the benefit of this method? I can't think of a reason to do this, unless you had a Fire TV on the old OS and hadn't a chance to root it yet?

5.0.5.1 - App Blocking

I've recently been digging in to what is causing launchers from being disabled and wanted to share my findings.
The culprit here is
Code:
/system/priv-app/com.amazon.tv.settings.apk
The service name is
Code:
com.amazon.tv.settings.tv.AppDisableService
There are currently two blacklisted apps in the 5.0.5.1 release:
Code:
com.altusapps.firedtvlauncher
de.belu.firestarter
If you are on 5.0.5.1, you can poke around the system partition by running on your computer:
Code:
adb pull /system
Looks like we have a cat-and-mouse game on our hands...

jkchr1s said:
I've recently been digging in to what is causing launchers from being disabled and wanted to share my findings.
The culprit here is
Code:
/system/priv-app/com.amazon.tv.settings.apk
The service name is
Code:
com.amazon.tv.settings.tv.AppDisableService
There are currently two blacklisted apps in the 5.0.5.1 release:
Code:
com.altusapps.firedtvlauncher
de.belu.firestarter
If you are on 5.0.5.1, you can poke around the system partition by running on your computer:
Code:
adb pull /system
Looks like we have a cat-and-mouse game on our hands...
Click to expand...
Click to collapse
Wow. Those sneaky bastards. I think there is a way to disable individual services.

rbox said:
Wow. Those sneaky bastards. I think there is a way to disable individual services.
Click to expand...
Click to collapse
I was thinking the same thing. I don't have the update so I can't test. But can't we do:
Code:
pm hide com.amazon.tv.settings.tv.AppDisableService
without root, and
Code:
pm disable com.amazon.tv.settings.tv.AppDisableService
with?

wouldn't hurt to try, would it?

rbox said:
Wow. Those sneaky bastards. I think there is a way to disable individual services.
Click to expand...
Click to collapse
Unfortunately the 'pm hide' command doesn't work to disable the service because it's for packages only, so non-rooted owners are out of luck. And yes, I did actually try it anyway. I expect the 'pm disable' command will work with root because it differentiates between packages and components.
Also, it doesn't look like they're doing anything special when disabling the two apps, so once we have a pre-rooted ROM, all we'll have to do is:
Code:
adb shell
su
pm disable com.amazon.tv.settings.tv.AppDisableService
pm enable com.altusapps.firedtvlauncher
pm enable de.belu.firestarter

AFTVnews.com said:
Unfortunately the 'pm hide' command doesn't work to disable the service because it's for packages only, so non-rooted owners are out of luck. And yes, I did actually try it anyway. I expect the 'pm disable' command will work with root because it differentiates between packages and components.
Also, it doesn't look like they're doing anything special when disabling the two apps, so once we have a pre-rooted ROM, all we'll have to do is:
Code:
adb shell
su
pm disable com.amazon.tv.settings.tv.AppDisableService
Click to expand...
Click to collapse
Did you verifiy with:
Code:
pm list packages -d
?

AFTVnews.com said:
Unfortunately the 'pm hide' command doesn't work to disable the service because it's for packages only, so non-rooted owners are out of luck. And yes, I did actually try it anyway. I expect the 'pm disable' command will work with root because it differentiates between packages and components.
Also, it doesn't look like they're doing anything special when disabling the two apps, so once we have a pre-rooted ROM, all we'll have to do is:
Code:
adb shell
su
pm disable com.amazon.tv.settings.tv.AppDisableService
pm enable com.altusapps.firedtvlauncher
pm enable de.belu.firestarter
Click to expand...
Click to collapse
It *IS* a cat and mouse game... but really all that has to happen is the authors of those programs just need to change the name of the package.

I was close. The command to disable the blacklist service is:
Code:
pm disable com.amazon.tv.settings/com.amazon.tv.settings.tv.AppDisableService
It survives a reboot. Here is my detailed guide for those who need it.

I've been playing with this on an unrooted box and found that I can crash the AppDisableService by sending an intent, followed by a force-stop of com.amazon.tv.settings:
Code:
am broadcast -a android.content.action.PERMISSION_RESPONSE_RECEIVED
am force-stop com.amazon.tv.settings
This *seems* to stop the AppDisableService since it never spins back up (since it never receives the BOOT_COMPLETED after it crashes), but this still leaves us with the problem of packages being disabled at boot and no way to enable them.
So, this led me to the idea that you could uninstall the apk and preserve the files, then simply reinstall it after the crash.
I tried to uninstall FireStarter and preserve data:
Code:
pm uninstall -k de.belu.firestarter
but on reinstall, it's still disabled (I'm guessing it preserves the disabled state with -k).
So I guess that's sort-of progress...

jkchr1s said:
I've been playing with this on an unrooted box and found that I can crash the AppDisableService by sending an intent, followed by a force-stop of com.amazon.tv.settings:
Code:
am broadcast -a android.content.action.PERMISSION_RESPONSE_RECEIVED
am force-stop com.amazon.tv.settings
This *seems* to stop the AppDisableService since it never spins back up (since it never receives the BOOT_COMPLETED after it crashes), but this still leaves us with the problem of packages being disabled at boot and no way to enable them.
So, this led me to the idea that you could uninstall the apk and preserve the files, then simply reinstall it after the crash.
I tried to uninstall FireStarter and preserve data:
Code:
pm uninstall -k de.belu.firestarter
but on reinstall, it's still disabled (I'm guessing it preserves the disabled state with -k).
So I guess that's sort-of progress...
Click to expand...
Click to collapse
I wonder what would happen if a device reset was done and your tweak were done?

king200 said:
I wonder what would happen if a device reset was done and your tweak were done?
Click to expand...
Click to collapse
Unfortunately a device reset would restart the AppDisableService. Causing the crash only stops it after you initiate the crash (meaning it would start up on next reboot). That's the problem with this approach...
My thought was to run a process to uninstall the disabled app(s), have a copy of the APK on the filesystem to re-install, and write an app that would initiate the crash and reinstall the apk on BOOT_COMPLETED. This approach is only good for keeping the app during a booted session, it would have to be re-run if the device was rebooted, and all app settings would be lost when the uninstall occurred.
Without initiating the crash, it appears they run an alarm task that essentially does a check every so often to disable any newly installed apps.
So it looks like they do the check on boot, then again at scheduled intervals. Initiating the crash causes the scheduled interval checks to not run, but a reboot means the app becomes disabled.

how about rename the app??? sorry if too stupid...

htchd2fix said:
how about rename the app??? sorry if too stupid...
Click to expand...
Click to collapse
Renaming the app works, but requires the source to be recompiled. Not easily done on device.

on the atvnews(dot)com website is a renamed version from firestarter for downlaod.
CU ulli01

[No Root] Remove the banner ad on the main screen

Wasn't sure if this has been posted before. Wanted to share.
Connect with adb and run...
Code:
pm uninstall -k --user 0 com.amazon.kso.blackbird
reboot
I'm not sure if the -k or --user 0 are necessary but its the same used on the kindle fire
I haven't tested but only way believed to return it is factory reset.

[email protected]:/ $ pm uninstall -k --user 0 com.amazon.kso.blackbird
Success
[email protected]:/ $ reboot
It seems to work, thanks!

Somebody sticky this.

krsmit0 said:
Wasn't sure if this has been posted before. Wanted to share.
Connect with adb and run...
I'm not sure if the -k or --user 0 are necessary but its the same used on the kindle fire
Click to expand...
Click to collapse
nyln said:
[email protected]:/ $ pm uninstall -k --user 0 com.amazon.kso.blackbird
Success
[email protected]:/ $ reboot
It seems to work, thanks!
Click to expand...
Click to collapse
So no ROOT needed (no # in the instructions) ? What would be the input to reverse this? It's always good to have the antidote, just in case.

Y314K said:
So no ROOT needed (no # in the instructions) ? What would be the input to reverse this? It's always good to have the antidote, just in case.
Click to expand...
Click to collapse
Correct, no root. And without trying it, the only way to return it is a factory reset or a OTA update.

krsmit0 said:
Correct, no root. And without trying it, the only way to return it is a factory reset or a OTA update.
Click to expand...
Click to collapse
Well, if you're rooted, you could flash the same firmware again, I assume.
If you have root, couldn't you do:
Code:
pm disable com.amazon.kso.blackbird
instead?

Sizzlechest said:
Well, if you're rooted, you could flash the same firmware again, I assume.
If you have root, couldn't you do:
instead?
Click to expand...
Click to collapse
I don't have root.
This doesn't remove anything from system, so reflashing the firmware is overkill to return this. Just a factory reset should return it although I'm not sure why you would return ads to the stock launcher.

krsmit0 said:
I don't have root.
Click to expand...
Click to collapse
Someone who does should attempt that instead. I have root, but I already did the uninstall command.
EDIT: I had a FireTV that I hadn't upgraded to the latest rbox firmware. I upgraded it and ran "pm disable com.amazon.kso.blackbird" as root and rebooted. The ads are gone.

krsmit0 said:
Correct, no root. And without trying it, the only way to return it is a factory reset or a OTA update.
Click to expand...
Click to collapse
Cool. Should be great for my friends on non-Rooted FTVS1-2.
krsmit0 said:
I don't have root.
This doesn't remove anything from system, so reflashing the firmware is overkill to return this. Just a factory reset should return it although I'm not sure why you would return ads to the stock launcher.
Click to expand...
Click to collapse
Guessing it should also work on Rooted devices with TWRP. We can just do a Factory Reset in TWRP to get back to normal if needed. Or maybe backup the APK & reinstall it. Maybe you can look at the code needed to reinstall it with the right rights. The APK reinstall could be an option for those on non-Rooted devices that don't which to Factory Reset.
Since Rooted devices have the option to disable & enable then they don't need that option.
Sizzlechest said:
Well, if you're rooted, you could flash the same firmware again, I assume.
If you have root, couldn't you do:
Code:
pm disable com.amazon.kso.blackbird
instead?
Click to expand...
Click to collapse
I wonder if like with the Method 2 Update Blocking for Non-Rooted devices we can do this for non-Rooted devices:
Code:
[STRIKE]pm hide com.amazon.kso.blackbird[/STRIKE]
Code:
[STRIKE]pm unhide com.amazon.kso.blackbird[/STRIKE]
Will test it shortly...
UPDATE: The HIDE command did not work. It did not hide the ad before or after restarting the device. Maybe it's missing something. Not sure. Luckily I a am rooted.
Sizzlechest said:
Someone who does should attempt that instead. I have root, but I already did the uninstall command.
EDIT: I had a FireTV that I hadn't upgraded to the latest rbox firmware. I upgraded it and ran "pm disable com.amazon.kso.blackbird" as root and rebooted. The ads are gone.
Click to expand...
Click to collapse
Thanks for the confirmation. Will test this Method 1 Update Blocking for Rooted devices too in a minute.
All my testing will be on one the same rooted device but with different ADB Shell $ & # options. $ for non-Rooted & # for Rooted.

Y314K said:
Cool. Should be great for my friends on non-Rooted FTVS1-2.
Guessing it should also work on Rooted devices with TWRP. We can just do a Factory Reset in TWRP to get back to normal if needed. Or maybe backup the APK & reinstall it. Maybe you can look at the code needed to reinstall it with the right rights. The APK reinstall could be an option for those on non-Rooted devices that don't which to Factory Reset.
Since Rooted devices have the option to disable & enable then they don't need that option.
I wonder if like with the Method 2 Update Blocking for Non-Rooted devices we can do this for non-Rooted devices:
Code:
[STRIKE]pm hide com.amazon.kso.blackbird[/STRIKE]
Code:
[STRIKE]pm unhide com.amazon.kso.blackbird[/STRIKE]
Will test it shortly...
UPDATE: The HIDE command did not work. It did not hide the add before or after restarting the device. Maybe it's missing something. Not sure. Luckily I a am rooted.
Thanks for the confirmation. Will test this Method 1 Update Blocking for Rooted devices too in a minute.
All my testing will be on one the same rooted device but with different ADB Shell $ & # options. $ for non-Rooted & # for Rooted.
Click to expand...
Click to collapse
On the kindle fire, we found no way to return it without a factory reset. i have used this to remove com.amazon.device.software.ota com.amazon.device.software.ota.override, it wont allow me to check if there is a system update any longer. not sure of long term function. Amazon disabled hide at some point on its devices so it wont work on an unrooted device. This has led me to wonder what com.amazon.videoads is and whats its effect if its removed/uninstalled.

krsmit0 said:
On the kindle fire, we found no way to return it without a factory reset. i have used this to remove com.amazon.device.software.ota com.amazon.device.software.ota.override, it wont allow me to check if there is a system update any longer. not sure of long term function. Amazon disabled hide at some point on its devices so it wont work on an unrooted device. This has led me to wonder what com.amazon.videoads is and whats its effect if its removed/uninstalled.
Click to expand...
Click to collapse
Yeah, went to backup some system Apps & did find two of them kind of interesting. I am wondering what they would do if disabled.
com.amazon.videoads.app (Could be ads when playing free vids &/or on Prime , not sure)
Tried the following commands. Could not see any difference in UI layout:
Code:
pm disable com.amazon.videoads.app
Code:
pm enable com.amazon.videoads.app
So left it enabled.
Local Recommendation Service (Not sure if it is related to the recommendations on the big banner below the ad banner we just disabled but it probably has to do with the recommendations from other app like Netflix, etc)
Not sure I want to mess with this one...
Backup a few other System apps in ES File Explorer without any Root privileges. And all also included a .systag file too.

hi,
tried this .. pm disable com.amazon.kso.blackbird
removed the banner ad ok.
but when you try .. pm enable com.amazon.kso.blackbird
banner ad does not return ?

john321321 said:
hi,
tried this .. pm disable com.amazon.kso.blackbird
removed the banner ad ok.
but when you try .. pm enable com.amazon.kso.blackbird
banner ad does not return ?
Click to expand...
Click to collapse
Did you reboot? I don't know if it matters since I never tried enabling.

john321321 said:
hi,
tried this .. pm disable com.amazon.kso.blackbird
removed the banner ad ok.
but when you try .. pm enable com.amazon.kso.blackbird
banner ad does not return ?
Click to expand...
Click to collapse
From what I remember, enable did work for me. Make sure you are at # & reboot/restart your device. The banner will be back.
Sizzlechest said:
Did you reboot? I don't know if it matters since I never tried enabling.
Click to expand...
Click to collapse
I think it does matter for it to show again.

Is there a way to remove the new "sponsored" bar in the latest update? It crashes the UI if you scroll over it with the ads disabled/uninstalled

tofu- said:
Is there a way to remove the new "sponsored" bar in the latest update? It crashes the UI if you scroll over it with the ads disabled/uninstalled
Click to expand...
Click to collapse
I'm experiencing this too, I tried to uninstall again in case the update added back but it was not there to uninstall. The plus is the sponsored bar is now at the bottom and isn't in my way.

I too am having same issue, can we just get the file from someone on here and reinstall it via adb pm install?

same problem here.
UI crashing...
enigma7820 said:
I too am having same issue, can we just get the file from someone on here and reinstall it via adb pm install?
Click to expand...
Click to collapse

have you tried a factory reset? the apk isnt truly uninstalled so reinstalling probably wont work.

I used uninstall not disable, if someone could provide the file from op we can install it back on

[GUIDE][NO ROOT][STICK 2] Playing With Matches v1

I thought I'd share my relatively less dangerous methods to turn a Fire TV Stick 2 into an Android TV clone.
First up follow my GApps/Google Services installation guide. This will provide the necessary backbone to install every other application.
You can either install Backdrop as below or ignore those instructions and use my newly ported Android TV settings app to select your screensaver! (no root required!).
Get it here: https://github.com/rockon999/TvSettingsOnFire/releases
Note this settings app requires addition permissions that must be granted via adb. They are listed on the releases page.
First let's install Backdrop (this provides a chromecast-like screen saver for your Fire TV).
Here is the APK link.
adb connect [IP of FTV]
adb install [APK PATH]
adb shell
settings put secure screensaver_components com.google.android.backdrop/.Backdrop
Now you have the Android TV screensaver! Look here for how to configure the timing of the screensaver/sleep.
Now let's install the Leanback launcher. Unfortunately the only Leanback launcher that will load on the Fire TV (without root) is one circa ~2015 and it is *buggy*. To aid this guide (and my sanity) I've taken the decompiled sources of LeanbackLauncher, stripped them of Google services, added features, improved stability, and added Fire TV specific features. You can find that here.
Now let's install Google's TV search app. I've found a working 2.x series version that is better looking, more stable, and much faster. You can get the APK here. Unfortunately the latest version is incompatible but an older version works surprisingly well. I've found version 1.0.6.2108324 to be the most stable. You can download the APK here.
UPDATE: I've figured out how to get Google's voice search working! (this only works w/ voice remotes not apps)
Running this command will disable global Alexa and allow Google to work (if you're on an old enough firmware): adb uninstall -k --user 0 com.amazon.vizzini
And there you go! Your Fire TV Stick is an almost-Android TV stick.
Stay tuned because this guide and Leanback on Fire is being continuously updated!

Very good work!

Thank you, this is what I've been looking for.

rockon999 said:
I thought I'd share my relatively less dangerous methods to turn a Fire TV Stick 2 into an Android TV clone.
Click to expand...
Click to collapse
Could you also include that activities in your launcher-mod ?
Code:
com.amazon.tv.settings/.tv.applications.ApplicationsActivity
And for a rooted version of your launcher (just as an idea):
Code:
com.android.tv.settings/.MainSettings
For com.android.tv.settings/.MainSettings you need to simply install TvSettings.apk with root and you will get almost all functions of the standard Android TV settings menu!
Code:
adb push TvSettings.apk /sdcard/
adb shell su -c mkdir /system/priv-app/TvSettings
adb shell su -c chmod 755 /system/priv-app/TvSettings
adb shell su -c cp /sdcard/TvSettings.apk /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chmod 644 /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chown root:root /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c rm /sdcard/TvSettings.apk

rainman74 said:
Could you also include that activities in your launcher-mod ?
Code:
com.amazon.tv.settings/.tv.applications.ApplicationsActivity
And for a rooted version of your launcher (just as an idea):
Code:
com.android.tv.settings/.MainSettings
For com.android.tv.settings/.MainSettings you need to simply install TvSettings.apk with root and you will get almost all functions of the standard Android TV settings menu!
Code:
adb push TvSettings.apk /sdcard/
adb shell su -c mkdir /system/priv-app/TvSettings
adb shell su -c chmod 755 /system/priv-app/TvSettings
adb shell su -c cp /sdcard/TvSettings.apk /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chmod 644 /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chown root:root /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c rm /sdcard/TvSettings.apk
Click to expand...
Click to collapse
For the first suggestion app settings are accessible by pressing menu while on a specific application and selecting "App Settings". I think that's what you're after, but if not correct me. The issue with launching the settings activity itself is that it will crash (at least on my FTV Stick 2). I have solved crashes before, though, so I'll look into it. As for your second suggestion I can simply look into re-adding the default ATV settings code (which should interface with this app well). Unfortunately, I'll have no way to test this (I only have an un-rootable FTV sticks) so it may take longer.

rockon999 said:
For the first suggestion app settings are accessible by pressing menu while on a specific application and selecting "App Settings". I think that's what you're after, but if not correct me. The issue with launching the settings activity itself is that it will crash (at least on my FTV Stick 2). I have solved crashes before, though, so I'll look into it.
Click to expand...
Click to collapse
No, I actually meant the global app menu. With me this doesn't crash when I start it directly via adb, but via Confireator I get a crash.
So it works without crash:
adb shell at the start -n com. amazon. tv. settings/. tv. applications. ApplicationsActivity
As for your second suggestion I can simply look into re-adding the default ATV settings code (which should interface with this app well). Unfortunately, I'll have no way to test this (I only have an un-rootable FTV sticks) so it may take longer.
Click to expand...
Click to collapse
That would be great!

I tried the microphone. I held the microphone button on my remote and talked. it worked. I don't think you intended it to work at all. So you should probably update about that. And it feels good to have leanback. Also is the recommendations thing impossible?

Pix12 said:
I tried the microphone. I held the microphone button on my remote and talked. it worked. I don't think you intended it to work at all. So you should probably update about that. And it feels good to have leanback. Also is the recommendations thing impossible?
Click to expand...
Click to collapse
The normal leanback recommendations system will either 1) crash or 2) display recommendations w/o their images (neither of those things are particularly pleasant). Together they mean you end up with a bunch of giant grey blocks (that never update) on your screen. So, essentially, the best way forward (I think) is to attempt to completely rewrite the recommendations code from scratch so that it can function in the user space. There is maybe a 50/50 chance that it will actually work though as recommendations operate over the notifications system and with Amazon's notification systems and Google's recommendations setup on the same machine they don't like to get along.
Side note, I'm surprised the microphone worked as Amazon coded it to always go to Alexa. I have some questions
1) Have you debloated? If so, what?
2) Are you rooted?
3) Any special mods?
Thanks!

rockon999 said:
Side note, I'm surprised the microphone worked as Amazon coded it to always go to Alexa. I have some questions
1) Have you debloated? If so, what?
2) Are you rooted?
3) Any special mods?
Thanks!
Click to expand...
Click to collapse
I debloated the FireTV, it's not rooted and I used Launcher Hijacker 3 to use as home screen. It might've been me using the
Code:
adb shell pm grant com.google.android.katniss android.permission.RECORD_AUDIO
command for the Google app to allow the microphone.

Pix12 said:
I debloated the FireTV, it's not rooted and I used Launcher Hijacker 3 to use as home screen. It might've been me using the
Code:
adb shell pm grant com.google.android.katniss android.permission.RECORD_AUDIO
command for the Google app to allow the microphone.
Click to expand...
Click to collapse
I'm guessing it's because your debloat removed the package that forces Alexa. Similar to how removing the launcher allows other launchers to work without modification apps. I'll poke around and see if I can replicate/find the package.

rockon999 said:
I'm guessing it's because your debloat removed the package that forces Alexa. Similar to how removing the launcher allows other launchers to work without modification apps. I'll poke around and see if I can replicate/find the package.
Click to expand...
Click to collapse
Yeah, I removed really everything Amazon. It showed the launcher menu.

Pix12 said:
Yeah, I removed really everything Amazon. It showed the launcher menu.
Click to expand...
Click to collapse
which is the package that forces Alexa?

is a new version of LeanbackLauncher coming soon?

rainman74 said:
is a new version of LeanbackLauncher coming soon?
Click to expand...
Click to collapse
I'm completely rewriting a lot of the database storage code (there are a lot of broken/missing database calls) and am close to done. I'm just trying to fix the favorites row at this point but moving apps elsewhere is working. I've also re-added the code to link to the native android tv settings app and I also ported the native android tv settings app to Fire TV (without root required!). In addition, I've gotten the leanback keyboard fully working! I'd say a day or two and I'll update the guide

rockon999 said:
I'm completely rewriting a lot of the database storage code (there are a lot of broken/missing database calls) and am close to done. I'm just trying to fix the favorites row at this point but moving apps elsewhere is working. I've also re-added the code to link to the native android tv settings app and I also ported the native android tv settings app to Fire TV (without root required!). In addition, I've gotten the leanback keyboard fully working! I'd say a day or two and I'll update the guide
Click to expand...
Click to collapse
WOW! :good::good::good:

rockon999 said:
I'm completely rewriting a lot of the database storage code (there are a lot of broken/missing database calls) and am close to done. I'm just trying to fix the favorites row at this point but moving apps elsewhere is working. I've also re-added the code to link to the native android tv settings app and I also ported the native android tv settings app to Fire TV (without root required!). In addition, I've gotten the leanback keyboard fully working! I'd say a day or two and I'll update the guide
Click to expand...
Click to collapse
Awesome work!

rockon999 said:
I'm completely rewriting a lot of the database storage code (there are a lot of broken/missing database calls) and am close to done. I'm just trying to fix the favorites row at this point but moving apps elsewhere is working. I've also re-added the code to link to the native android tv settings app and I also ported the native android tv settings app to Fire TV (without root required!). In addition, I've gotten the leanback keyboard fully working! I'd say a day or two and I'll update the guide
Click to expand...
Click to collapse
Awesomeeeee!!!!!!!!!:laugh::laugh::laugh:

UPDATE: I've figured out how to get Google's voice search working! (this only works w/ voice remotes not apps)
Running this command will disable global Alexa and allow Google to work (if you're on an old enough firmware): adb uninstall -k --user 0 com.amazon.vizzini

rockon999 said:
UPDATE: I've figured out how to get Google's voice search working! (this only works w/ voice remotes not apps)
Running this command will disable global Alexa and allow Google to work (if you're on an old enough firmware): adb uninstall -k --user 0 com.amazon.vizzini
Click to expand...
Click to collapse
working perfectly with the newer apk from OP

ALPHA 2 OF LEANBACK IS OUT AND ATV SETTINGS APP PORTED
https://github.com/rockon999/Leanbac...leases/tag/0.2
NOTE: You must completely remove Alpha 1 (and clear its storage - instructions on the release page) as Alpha 1 had database storage bugs that make Alpha 2 inoperable.
The first alpha of my port of Android TV's settings app, TvSettingsOnFire, is also available (note the permission requirements)! https://github.com/rockon999/TvSettingsOnFire/releases
Also, if you've ever actually wanted to see what your were editing while you were typing Leanback Keyboard works perfectly in conjunction with my TvSettings port! You can grab it here.

Debloat Samsung A51 (No root) and get crazy performance!

Hello fellow A51 users today i want to share with you a debloat guide so you can get the max performance out of you new smartphone without Samsung clutter.
All credits goes to Khlam and his Samsung Oneui debloat list:
https://github.com/khlam/debloat-samsung-android
I tested it on my device with uninstalling the complete list and it works great.
You do lose some functionality so be careful with what you delete this does only delete the apps one your install of the OS doing a factory reset will reset all apps back to normal this will not void any warranty so i suggest making a backup and trying it on a fresh install and see if you like it.
This guide will strip Oneui to its bare bones so its not for everyone but if you like speed over functionality than give it a try.
Guide:
The following instructions assumes you are familiar with using a command-line interface.
1. On your phone, enable Android's "Developer Options"
2. In "Developer Options", turn on "USB Debugging"
3. On your computer, download Android SDK Platform-Tools for your OS.
https://developer.android.com/studio/releases/platform-tools
4. Extract Android SDK Platform-Tools and start a command-prompt/shell session in the extracted folder's directory.
(The way i do this is putting the platform tools folder in My Documents and en opening the folder then type cmd in the navigation bar and hit enter this will open a command prompt in the folder directory.)
5. Connect your Samsung Android phone to your computer with USB debugging enabled. Verify that adb sees your device and the daemon is running with the following command
adb devices
You should see the device name listed as a "device".
At this point your device should prompt you to accept USB debugging from your computer. Tap "Allow".
6. Enter your device's shell with the following command: adb shell
Once in the device's shell, copy and paste all desired commands from:
https://raw.githubusercontent.com/khlam/debloat-samsung-android/master/commands.txt
(What i do is making a notepad file and copying the whole list in notepad file removing the spaces then copy and paste the whole list in the command prompt.)
Let the script run and when the command prompt reaches the last command you only have to hit enter ones the finish the script.
Thats it you now have a fast bare bone debloated A51 you can close the command prompt and disconnect your phone from your pc.
Enjoy if this all sounds to difficult i suggest you read up on the following articles/guides
https://github.com/khlam/debloat-samsung-android
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
They explain it in more depth if you have any questions please put them bellow and im happy to help.
Zoqy :laugh:

Amazing, was looking for this.
Thanks.

very cool... thx for sharing this

I'm not able anymore to access "Sound quality and effects" in the settings.
Anyway to reinstall?
I found out what the solution was.
So when deleting
pm uninstall -k --user 0 com.samsung.aasaservice
And reinstalling
pm install-existing --user 0 com.samsung.aasaservice

How to fix sms app?
pm install-existing --user 0 com.samsung.android.messaging
it's not helping

senq87 said:
How to fix sms app?
pm install-existing --user 0 com.samsung.android.messaging
it's not helping
Click to expand...
Click to collapse
The ADB-Command for reinstalling is:
adb shell pm enable com.samsung.android.messaging

I get a popup message when trying to edit a picture from the gallery app. It asks to download a picture editor but when i click on download it says "no apps availbe to do this action".
edit: got it myself. this fixed it:
pm install-existing --user 0 com.sec.android.mimage.photoretouching

Just found another one today:
upday for Samsung - Zeropage
a51:/ $ pm uninstall -k --user 0 de.axelspringer.yana.zeropage
Success

tried, broke, fixed
ran this script on the sm-a515u verizion. Lost signal, data, and my nova google companion (no edge swipe). Factory reset works as normal again.

this deletes pretty much everything on your phone, including things like image cropping, youtube or the "find my galaxy" thing
some of these functions are much needed so would sort out whatever you need from that list before attempting to do that
I only deinstalled what I really didn't need, what was about 20 apps and services

seems that one of these packages depends on calling and texting. i'm on a spectrum mobile device and after running the entire script i can use mobile data but can't make or recieve phone calls and text messages. of course a factory reset does the trick but i wonder what app is causing this?
EDIT: i finally got around to troubleshooting it. it was most likely these services i had to re-enable again (through adb shell cmd package install-existing <package name>:
com.sec.ims
com.sec.imslogger
com.sec.imsservice

I am getting frequent reboots and will have to factory reset.

FBK2904 said:
The ADB-Command for reinstalling is:
adb shell pm enable com.samsung.android.messaging
Click to expand...
Click to collapse
This did not help, messaging app crashed. But text message retrieval works.
---------- Post added at 20:26 ---------- Previous post was at 20:23 ----------
AOD no longer works.

Frau Son said:
this deletes pretty much everything on your phone, including things like image cropping, youtube or the "find my galaxy" thing
some of these functions are much needed so would sort out whatever you need from that list before attempting to do that
I only deinstalled what I really didn't need, what was about 20 apps and services
Click to expand...
Click to collapse
would you share those 20 apps and services?

settings not opening. what is the solution to that?

albusdanbledore said:
would you share those 20 apps and services?
Click to expand...
Click to collapse
did you get it ?

hhniloy said:
settings not opening. what is the solution to that?
Click to expand...
Click to collapse
Same here, after Update to Android R (11). My Settings still crash. I reinstalled the bloated s***. then settings works again. But I will try which app it caused.

albusdanbledore said:
would you share those 20 apps and services?
Click to expand...
Click to collapse
for me exactly the same question. Please answer.

I suggest using this debloater instead. More recent, covers many more things (not just Samsung specific) and every single setting is documented and tested. The Samsung Debloater uninstalls things that are better left alone if you don't want an unstable device.

chrisimre747 said:
Same here, after Update to Android R (11). My Settings still crash. I reinstalled the bloated s***. then settings works again. But I will try which app it caused.
Click to expand...
Click to collapse
The app which cause the crash is:
com.osp.app.signin
Tested on my Galaxy A51.