Related
Since root has been obtained and an alternative launcher can be installed, as has been mentioned there is really no need to stay on 5.0.0 anymore. I would recommend updating to 5.0.1. However, this procedure can still be applied to 5.0.1 and hopefully it'll prevent any future updates. (As of writing it 5.0.1 is the latest).
The steps are basically as follows:
Enable ADB by going to Settings> Device Options. Keep tapping on the Serial Number field until the Developer options field appears.
Under Developer options Enable ADB
Hook the Fire up to your computer and do the following commands:
adb shell pm hide com.amazon.otaverifier
adb shell pm hide com.amazon.device.software.ota
adb shell pm hide com.amazon.settings.systemupdates
I don't know which of three is the magic one, But you can not longer go to device options > system update. It also never appears to pull down the update in the background.
Rivethread23 - good work and many thanks for this
I know that you have the original Fire 7 with no system update but I wanted to see if any of your commands will work on 5.01. My device is on 5.01 has been in aeroplane mode since purchase, I have been using OTG Ethernet for connectivity and I have not signed into Amazon. Google Play is installed - basically a standalone device on 5.01 with no association with Amazon.
After running the commands and the ADB shell gave a [True State] after each command. Rebooted the device:
System Updates now gives the following error message: [The requested action is not permitted. Check Parental controls settings and try again]. As my device is not associated with Amazon parental controls have not been configured - so I browsed to a few proxy sites and such to confirm no filtering on web browsing etc
I've tried various launchers from Play store and every time the default Fire Launcher kicks back in again.
SD Card issue is still there.
When you tried the System Update button did you get the same error message as me? If so, I wonder if the Adb Shell command to disable OTA works on 5.01 as well?
Update 1: [adb shell pm hide com.amazon.firelauncher] disables the default Amazon launcher. I picked another launcher at random from Google Play. Halo installed and it worked with the default launcher hidden, however using the minimise middle button on the device forces the Parental Control Popup to appear.
So it is possible to hide the default launcher on 5.01 using ADB but it is causing issues. We need a better work around.
Unfortunately this only blocks the update from occurring. I ran into another issue on the 5.0.0 tablet in that I can't get Google play store working. It just says cannot connect. So I don't know if one of the above things broke it. It was getting late so I went to bed. I'll keep plugging at it and see what I can do.
I might finally take both of mine out of the box today, can more people confirm this is working? @Rivethread23, did you get the play store sorted out?
Couldn't wait, dove in. On an out-of-box Fire, running 5.0.0, these do in-fact keep the OTA updates from firing. I have been online, installing apps and customizing the tablet for over an hour with many reboots, no prompts or attempts of an update.
With this, and ads disabled, and the play store turned on we have a usable tablet!
F-Droid works as well, just sideload their APK to get access to lots of software:
https://f-droid.org/repo/org.fdroid.fdroid_96150.apk
Still stuck on Play Store in 5.0.0 *not working* for now.....same problem as OP
I can confirm that the Google Play Services, Login Services, and Framework are (at least partly) working, even though the Play Store is not. I sideloaded Gmail, and it automatically had my info, and downloaded my email.
Wait, I'm confused. In 1 post you say play store is on and working, then you're saying it's not...
Aside from the play store, it sounds like everything else is working fine! Is that correct. I'm asking because I'm thinking about buying a 2nd one of these, only if I can have it working 100% the way I have it now with my tablet, just with the ability to use a different launcher.
With the original 5.0.0 firmware, if you prevented the OTA update to 5.0.1:
+Can change launcher
+Can write to SD from apps
-Can't get Play Store to work (so far, but can manually side-load GApps (Gmail, Hangouts, etc))
In the other thread, people that have gone to 5.0.1:
-Locked to amazon Launcher when using HOME button
-Manual SD writing is disabled
+Google Play Store can be installed and 90% of the GApps work
--------
The key to take away is that if you get another one, and you do the fix in this thread to prevent OTA updates, you can simply wait til everyone gets things fixed and figured out. You can safely use it and not worry about getting pushed to a firmware that might be even more locked down.
On the other hand, if you're not worried about OTA updates breaking stuff, and want a working store, go to 5.0.1 and follow SD_Shadow's instructions in his thread on that subject.
Hopefully root comes soon and we can fix all these problems properly, but until then it's kinda hit and miss depending on what version you got.
Hope that helps.
Thanks Tufkal was going to post something along those lines but you beat me to it.
Essentially you can prevent updates from further locking down the tablet. Who knows what future updates bring? I'll wait and update as thing warrant.
I have two one on 5.0.0 and another on 5.0.1. While I like being able to use the launcher of my choosing on 5.0.0, the working google store and updated amazon store and apps have me using the 5.0.1 one. I am keeping the other on 5.0.0 until development starts then I'll try my hand at making a ROM.
Your device that is on 5.0.0 Firmware have you signed into Amazon and associated your device? Or is it standalone like mine?
Was on Amazon for a day. Factory reset it and am using it sans Amazon. Mostly using the 5.0.1 one myself.
Yep same here. 5.01 with no amazon sign in.
I've been playing around with the launcher again. Tried changing the hardcoded buttons and also with ADB Shell am force-stop pm disable on com.amazon.firelauncher to stop dependent services, ie hard buttons. All to no avail.
root definitely needed for this
I figured out a way to access some hidden functions within the OS last night. Seeing where this leads after work today Apparently I can cast the screen and access the home function disabled in 5.0.1. Problem is the home function doesn't override the hard coding.
Most interesting is something called Prod and Devo Switch that give "Access Denied" when I try to activate it. Hmmmm........
Here's what I have discovered. It's easier done on 5.0.0 but can be done on 5.0.1. You'll need another launcher like Nova installed. Installed "Anycut" from the google store. It'll let you put a shortcut on the desktop for any "activity". There are alot of items there not normally accessible. You can cast to a Chromcast for example (it works). The reason you need another launcher is the Amazon launcher doesn't support shortcuts I guess as they don't appear. They appear on Nova's desktop when created.
Most interesting is a shortcut called "Prod and Devo Switch" which if you look at the info refers to the "Amazon Device Settings" app.. ( com.amazon.device.settings?). It's separate from the user settings. If you try to access it it will say "Access Denied" on 5.0.1. Or "Permission denied" on 5.0.0. Makes me wonder if what needs to happen the app needs some additional permissions to be run. I was looking through the list of permissions via ADB and there are a number of permission groups that are android.xxxxx. However there are only a few permission groups that are amazon.xxxxx one of which is amazon.permission-group.settings. Listing the settings in the group shows a large list. Maybe using ADB pm grant com.amazon.device.settings the correct permissions could unlock this? Thoughts?
Here's what I got from a logcat when I click on the shortcut in novalauncher:
I/ActivityManager( 454): START u0 {act=android.intent.action.VIEW flg=0x1000000
0 cmp=com.amazon.device.settings/.DevoProdConfigActivity bnds=[300,168][400,310]
} from uid 10017 on display 0
W/ActivityManager( 454): Permission Denial: starting Intent { act=android.inten
t.action.VIEW flg=0x10000000 cmp=com.amazon.device.settings/.DevoProdConfigActiv
ity bnds=[300,168][400,310] } from ProcessRecord{9460965 1138:com.teslacoilsw.la
uncher/u0a17} (pid=1138, uid=10017) requires com.amazon.dcp.permission.DISPLAY_D
EBUG_UI
E/Launcher( 1138): Launcher does not have the permission to launch Intent { act=
android.intent.action.VIEW flg=0x10000000 cmp=com.amazon.device.settings/.DevoPr
odConfigActivity bnds=[300,168][400,310] }. Make sure to create a MAIN intent-fi
lter for the corresponding activity or use the exported attribute for this activ
ity. tag=ShortcutInfo(title=Prod and Devo Switch intent=#Intent;launchFlags=0x10
000000;component=com.amazon.device.settings/.DevoProdConfigActivity;sourceBounds
=300%20168%20400%20310;end id=15 type=Shortcut container=-100 screen=1 rank=-1 c
ellX=3.0 cellY=1.0 spanX=1.0 spanY=1.0 dropPos=null user=UserHandle{0} modelGene
ration=-1) intent=Intent { act=android.intent.action.VIEW flg=0x10000000 cmp=com
.amazon.device.settings/.DevoProdConfigActivity bnds=[300,168][400,310] }
E/Launcher( 1138): java.lang.SecurityException: Permission Denial: starting Inte
nt { act=android.intent.action.VIEW flg=0x10000000 cmp=com.amazon.device.setting
s/.DevoProdConfigActivity bnds=[300,168][400,310] } from ProcessRecord{9460965 1
138:com.teslacoilsw.launcher/u0a17} (pid=1138, uid=10017) requires com.amazon.dc
p.permission.DISPLAY_DEBUG_UI
Tried granting that specific permission to Nova launcher or the Fire launcher but both do the same thing:
com.amazon.firelauncher com.amazon.dcp.permission.DISPLAY_DEBUG_UI <
Operation not allowed: java.lang.SecurityException: Package com.amazon.firelaunc
her has not requested permission com.amazon.dcp.permission.DISPLAY_DEBUG_UI
Maybe someone with more knowledge than I create a program with that permission that calls the intent in question?
Again good work on this
I picked up another new device yesterday morning. OTA updates disabled, Fire OS 5.0, no association to Amazon and connectivity via WiFi. Just like you I got Gmail, YouTube and other Google associated apps to work with the exception of the Play store. It finally let me sign in but comes up every time with the [Connection Retry] error.
I followed your instructions and installed AnyCut - and I have been playing around as I thought it might be possible by using shortcuts to load my Google account onto the device.
Shortcut [Add an account] - and the "Couldn't sign in - google server error" came back so not working for now.
Shortcut [Testing] - allows us to pull up more info on the Fire 7 with the 4 below options
Tablet Information - not working
Battery Information - working
Usage Statistics - working
WiFi Information - working
Shortcut [IP Settings] - gives us advanced WiFi options
A lot of the options try to load or there is a visible presence of starting to load and you can clearly see the device stopping them from loading. Basically we are trying to load Android Apps that are locked down by Fire OS which sits on top of Android.
Other apps with Permission Denied
[Log Manager]
[Crash Manager]
[Metrics Debug UI]
Looks like Amazon do not want us to have access to their inbuilt log files on their device
As I do not have access to Google store I have been using F-Droid for my apps. I have installed APK Extractor and it lists all the current APK's on the Fire 7. What is interesting about this is that there are APK's that where not findable using [AnyCut] but show up in APK Extractor.
Will update more in a bit
Here's an interesting note..... I'm on 5.0.0 and trying to get the Play Store working (I believe that 5.0.0 w/ Play Store is a better avenue to attack than trying to fix the launcher in 5.0.1)
For testing reasons I'm on an older version of the Play Store where the search icon is visible.
On the play store screen where it says no connection with the retry button, I hit the search icon and start typing "clas" It autofilled in clash of clans. Then i did "hang" and I see hangouts dialer. The play store app is communicating it would seem.....
tufkal said:
Here's an interesting note..... I'm on 5.0.0 and trying to get the Play Store working (I believe that 5.0.0 w/ Play Store is a better avenue to attack than trying to fix the launcher in 5.0.1)
For testing reasons I'm on an older version of the Play Store where the search icon is visible.
On the play store screen where it says no connection with the retry button, I hit the search icon and start typing "clas" It autofilled in clash of clans. Then i did "hang" and I see hangouts dialer. The play store app is communicating it would seem.....
Click to expand...
Click to collapse
What is the version of your Play APK please? As I have the latest version with no search - but still on 5.0.0
k3ll0gs said:
What is the version of your Play APK please? As I have the latest version with no search - but still on 5.0.0
Click to expand...
Click to collapse
I'm trying all kinds, the one i was using for that test I got here:
https://onedrive.live.com/redir?res...4&authkey=!AIVXLFXAOWDeM0Q&ithint=folder,.apk
I'm with you I tried some work arounds on the 5.0.1 tablet but if we can get the play store working on 5.0.0 it seems to offer more opportunities.
Yep same here - it makes more sense to get Play store to work.
I think I might know what the issue is causing and I believe it is down to the Google Service Framework (GSF) on 5.0 not installing correctly and causing the sync issue when trying to connect. I installed [Device ID] app on 5.0 and there is no serial listed for GSF at all - on my 5.1 tablet GSF would load up on the screen and you could view settings but on 5.0 it does not.
When trying to open the Google Play some I found the following error in Logcat [.onClick: b/5160617: Reinitialize account] this relates to the GSF serial not being present. Logs also show permissions and api errors as well. The only
Looking into a GSF workaround if possible. It might be on the wrong track but I am going to see what else I can find out.
I thought I had found a back door into Google signin. Using an App calling [Applications Info] which I used to pull up the GoogleServiceFframework apk. From there I started to play around with the launch options for the applicable services.
Selecting launch on [Legal Services] takes you to Google Sign In - keyboard was not working for this so I had to adb shell input text of my gmail & password. Unfortunately the same old Google error was appearing even after I cleared the cache and re-installed Gapps.
The last screengrab shows that the System Updates on installed Google Service Framework is corrupt and not working properly. I have also launched other Gapps dependent activities from the services in [App Info] and again they either fail to load of abundance of errors. So installation issues for all of the Gapps in one way or another on Fire 5.0
Obviously there is a difference between the 5.0 Rom + 5.01 Rom that is stopping Gapps from working. Due to the amount of errors in Logcat and in Application Info and dependent services not working. My gut is saying that when we have root on 5.0 we have a better chance of getting Gapps working as we will have the ability to play around with not only System files but System commands too.
If anyone has any ideas or what else we could try please chip in.
rivethead23 said:
Hook the Fire up to your computer and do the following commands:
adb shell pm hide com.amazon.otaverifier
adb shell pm hide com.amazon.device.software.ota
adb shell pm hide com.amazon.settings.systemupdates
Click to expand...
Click to collapse
running those commands will prevent any future update?
Right now I have 5.0.1 and I'm happy with it, I would like to avoid any bad surprises.
redst said:
running those commands will prevent any future update?
Right now I have 5.0.1 and I'm happy with it, I would like to avoid any bad surprises.
Click to expand...
Click to collapse
yes updates would be blocked until you run the unhide commands.
Sent from my KFFOWI using Tapatalk
***This will NOT work on FireOS 5.4.0.1 If your device hasn't updated to that version, it is advisable to IMMEDIATELY 'uninstall' DeviceSoftwareOTA.apk.***
I can confirm this is working on the Fire HD 8 . Here is the article from XDA with detailed instructions for newbies. Like all other hacks or tricks, I cannot be held responsible for any possible permanent damage you may cause to your devices.
**NOTE**
A factory rest will restore all SYSTEM/Amazon apps you 'uninstalled.' So if you mess your tablet, you can at least start over.
**WARNINGS**
1) If you plan on installing 3rd party apps to replace the Amazon apps you uninstalled, please install and setup your 3rd party apps BEFORE uninstalling Amazon apps. In many cases, installing replacement apps after the uninstalling of Amazon apps, causes some 3rd party apps to malfunction. You will then have to uninstall the 3rd party app or do a reset. Once you uninstall an Amazon app, you CANNOT install it again. Not even from the Google Play Store. The only way to restore any uninstalled system apps is to do a factory reset.
2) Uninstalling Fire Launcher, Retail Demo, and the Oobe settings apps, *WILL* disable your home button. If you uninstall any parental controls, your camera picture roll will not work. Recommend installing replacement camera and gallery before uninstalling Amazon's. As of July 27, 2017 9:20am a *pre uninstall* fix exists to make sure your home button stays functional. If you already uninstalled the apps listed in the following link, you will have to perform a reset and download the tool linked just below, or if you prefer manually uninstalling the apps, *avoid uninstalling*: com.amazon.kor.demo, com.amazon.firelauncher and com.amazon.kindle.otter.oobe. You can also edit the tool's .bat to keep the apps you want. This link lists all the apps you can uninstall, that will NOT affect the home button. The three listed at the top should NOT be uninstalled.
** Gloating **
1) A tool has been created that allows this process to happen automatically. A huge thanks to 'savvytechwinner' for helping for months to get us to this stage and an even bigger thanks for creating the tool, something I have no idea how to do.
2) A little gloating: We've scored a great write up on Liliputing!
You can use an app like App Inspector to view the package name of each app, rather than list all of them in a shell window. Nonetheless, I kept the list command in the code.
Here you go:
Code:
adb shell
$ pm list packages
$ pm uninstall -k --user 0 <name of package>
Example: (this removes Amazon video)
Code:
adb shell
$ pm list packages
$ pm uninstall -k --user 0 com.amazon.avod
Success
Why do you keep the data and cache directories?
This is a good thing, however, as it means that these applications truly aren’t being uninstalled from the device, they are just being uninstalled for the current user (user 0 is the default/main user of the phone). That’s why, if you omit the “–user 0” and “-k” part of the command, the command won’t work. These two commands respectively specify that the system app will only be uninstalled for the current user (and not all users, which is something that requires root access) and that the cache/data of the system application will be preserved (which can’t be removed without root access). Therefore, even if you “uninstall” a system application using this method, you can still receive official OTA updates from your carrier or OEM.
Click to expand...
Click to collapse
Source: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Hallo32 said:
Why do you keep the data and cache directories?
Source: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Click to expand...
Click to collapse
Fine by me. I wonder if the same method can be applied to install apps and if so, into system? This could be the chance to replace Amazon's apps with forever broken ones while we can, if possible.
Work on my Fire 7" Gen7 with 5.4.0.0.
Thank You!
DragonFire1024 said:
Fine by me. I wonder if the same method can be applied to install apps and if so, into system? This could be the chance to replace Amazon's apps with forever broken ones while we can, if possible.
Click to expand...
Click to collapse
Into system should not be possible, because you need root rights to mount /system as write able.
Hasn't there been a few tries to install modified Amazon apps which are broken? I think I have read there something on xda.
--> Firelauncher aplk https://forum.xda-developers.com/am...-remove-default-launcher-amazon-fire-t3288310
Hallo32 said:
Into system should not be possible, because you need root rights to mount /system as write able.
Hasn't there been a few tries to install modified Amazon apps which are broken? I think I have read there something on xda.
Click to expand...
Click to collapse
Yes. Another member and I have been trying to do just that. We've been trying to modify Amazon apps to either bring out block parts of that APKs software, or stop the apps from functioning at all. The closest I got was somehow managing to delete all User AND system app data and storage. Great eh? I thought so too. Until I realized I couldn't download or install anything. I tried, but haven't been able to repeat the process. So far that's as far as we've gotten.
Hallo32 said:
Into system should not be possible, because you need root rights to mount /system as write able.
Hasn't there been a few tries to install modified Amazon apps which are broken? I think I have read there something on xda.
--> Firelauncher aplk https://forum.xda-developers.com/am...-remove-default-launcher-amazon-fire-t3288310
Click to expand...
Click to collapse
That works to an extent. I tried it, replacing launcher with whatever Amazon app. It uninstalls it, but then is immediately reinstalled to another folder...usually from /system/priv-app/ to /data/app and with a different name. Though this might have been how I got all app and system app data erased...by screwing around with the DeviceOTA apk.
See edit above. ^^
But what does this mean in relation to the ota apps? Are the ota updates also deactivated?
Hallo32 said:
See edit above. ^^
But what does this mean in relation to the ota apps? Are the ota updates also deactivated?
Click to expand...
Click to collapse
I would've presumed that to be a yes, given nothing could be downloaded and or installed anymore. Everything worked fine aside from that and being able to uninstall apps. What little bit I could find on the web, no one mentioned the cause and most of them ended up with permanently damaged internal SD cards. I waited a few days after posting a thread and no one replied. So I factory reset it and everything was fine again. I wish I could repeat it.
Can we disable "special offers" using this method? Or is that part of the launcher?
If we "uninstall" the launcher, will it ask if you want to use a different installed launcher to map to the home button?
deepdvd said:
Can we disable "special offers" using this method? Or is that part of the launcher?
If we "uninstall" the launcher, will it ask if you want to use a different installed launcher to map to the home button?
Click to expand...
Click to collapse
I did special offers. Haven't tried the launcher yet.
DragonFire1024 said:
I did special offers. Haven't tried the launcher yet.
Click to expand...
Click to collapse
Does it actually remove them from the lock screen or just make the app not work?
deepdvd said:
Does it actually remove them from the lock screen or just make the app not work?
Click to expand...
Click to collapse
I don't know. I didn't have the ads.
on my kindle fire 7 on 5.3.2.1, this gives the error Failure [DELETE_FAILED_INTERNAL_ERROR].
EDIT: nevermind, i must have missed a step
I have removed most user facing apps. i have not tried the launcher or appstore.
I can confirm that you can remove everything whisperplay and the stock fire keyboard. I install the gboard before i removed the fire keyboard. I have rebooted after removing this.
Does anyone have more than their own profile on their tablet? I'm wondering if this extends to all profiles. So far, Nova, Activity Launcher, Brevent And NetGuard all say all the Amazon apps I uninstalled are gone. Has anyone tried root after nuking Amazon?
If you keep blocking individual Amazon IP addresses like I do with NetGuard, I'd keep a few apps. As long as one app keeps blocking IPs, then your firewall will still work. Otherwise I'm not sure how to block incoming connections.
Is there a list of packages which can be removed without problems?
I will need to restart from a factory reset because now the launcher crashes happily a few times after closing an app.
Hallo32 said:
Is there a list of packages which can be removed without problems?
I will need to restart from a factory reset because now the launcher crashes happily a few times after closing an app.
Click to expand...
Click to collapse
This will list all installed packages. I'm not sure if a safe list has yet been made.
Code:
adb shell
$ pm list packages
It will be a long list. Remove at YOUR own risk. One person's safe list may not be the same as yours.
DragonFire1024 said:
This will list all installed packages. I'm not sure if a safe list has yet been made.
It will be a long list. Remove at YOUR own risk. One person's safe list may not be the same as yours.
Click to expand...
Click to collapse
I've removed quite a bit so far, appstore, freetime, kindle store and app, content management because Amazon has no right to manage any of my content, managed provisions though I'm not sure that did anything, video and Amazon shopping, and a few others i can't recall at this moment. I am hoping removing prime photos later will allow me to use live wallpapers.
If this is the closest we ever get to root or a custom rom, I don't think we could've asked for something better.
@DragonFire1024
You may mention at the first post, that a factory reset will bring back the automatic update stuff if the method has been used to deactivate it.
Worst case:
* factory reset
* enable wlan conection
* tablet gets updates and installs them
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.
And if not would doing a reset of just the settings probably fix it?
Also tried things like clearing cache partition, I didn't really want to do a whole wipe if possible but clearing cache hasn't worked.
It's doing it daily, sometimes a couple of times per day in different apps.
Are there any event logs that would tell me what happened at the point of the restarts?
If I did a while wipe would my settings and apps be restored after? I can't remember about settings but I know it tries to get back your apps but from previous experience you end up with a load you didn't want any more and a load it missed for some reason.
What does anyone think is best?
Thanks
James
A factory data reset might fix it. I would take it to a local repair shop and see what they say. It might be a hardware malfunction in which if so, claim warranty.
I had a problem once with constant restarts, i finally found the problem. I was removing bloatware with ADB and the apps called ANT i removed. They sere somehow linked to the security folder. Once i reinstalled those apps everything was fine.
Also in Device Care you can check if there's an jssue with any apps. (Which May Or May Not Be Related)
my s10 constantly restarts
Darkat70 said:
I had a problem once with constant restarts, i finally found the problem. I was removing bloatware with ADB and the apps called ANT i removed. They sere somehow linked to the security folder. Once i reinstalled those apps everything was fine.
Click to expand...
Click to collapse
Hi
How do I use ADB to remove apps? how can I find out which app is the culprit?
I dont want to factory reset my phone, as I will lose a lot of data, I cant back it up, since it restarts as I start backing app, no matter which app I use
Thanks!
acetrip said:
Hi
How do I use ADB to remove apps? how can I find out which app is the culprit?
I dont want to factory reset my phone, as I will lose a lot of data, I cant back it up, since it restarts as I start backing app, no matter which app I use
Thanks!
Click to expand...
Click to collapse
To get a list of apps
adb shell pm list packages
To uninstall a package
adb shell pm uninstall --user 0 (package name)
Reinstall
adb shell cmd package install-existing (package name)
What is causing is difficult but if you have removed ant services for example, then afterwards setup secure folder access this will cause a loop reboot.
Try remembering if you have recently removed anything.
Root Method (Works on Fire TV Stick Tank, Fire TV Stick 4K, and other Fire TV's with Root Functionality)
adb connect (your ip address or through usb adb)
adb shell
su
cd /data/data/com.amazon.tv.launcher/databases
rm mbcache.db*
touch mbcache.db
touch mbcache.db-shm
touch mbcache.db-wal
chmod 0 mbcache.db*
After its fully typed in, type ls -all and the three files should stay as zeros
Reboot and check your memory
Non-Root Method (2020 Fire TV's supported, 2016 Tank, along with other Fire TV's although the mbcache.db will fill up quickly as I recommend rooting the 4K or Tank, ADB Debugging required)
adb connect (your ip address or through usb adb)
adb shell pm clear com.amazon.tv.launcher (Success should be noticeable and the launcher may freeze up for a second as well as the recents row of your apps are gone but won't delete your apps data)
Reboot and check your memory (It'll build up sadly so I prefer entering this command like every so often it fills up)
I hope this helps anybody with the memory shortages with the stick.
Anybody with the newer launcher let me know if it's working correctly. This guide was the older interface before the 6.2.8.0 4K Stick update.
Skel40 said:
Root Method (Works on Fire TV Stick Tank, Fire TV Stick 4K, and other Fire TV's with Root Functionality)
adb connect (your ip address or through usb adb)
adb shell
su
cd /data/data/com.amazon.tv.launcher/databases
rm mbcache.db*
touch mbcache.db
touch mbcache.db-shm
touch mbcache.db-wal
chmod 0 mbcache.db*
After its fully typed in, type ls -all and the three files should stay as zeros
Reboot and check your memory
...
I hope this helps anybody with the memory shortages with the stick.
Click to expand...
Click to collapse
Does this have any adverse effects? I want to make it unwritable, but concerned the launcher would get messed up. Here you actually talked about restoring this:
Fire TV Stick 4K (mantis) Debloated Rom 6.2.7.1 93/6.2.7.7
Debloated Rom For The Fire TV Stick 4K 6.2.7.1 93/6.2.7.7 Revised NOTE: Firmware versions after 6.2.7.7 will not work with this debloated rom. It's been a few months since I've updated this guide so be cautious with installing this. The latest...
forum.xda-developers.com
bibikalka said:
Does this have any adverse effects? I want to make it unwritable, but concerned the launcher would get messed up. Here you actually talked about restoring this:
Fire TV Stick 4K (mantis) Debloated Rom 6.2.7.1 93/6.2.7.7
Debloated Rom For The Fire TV Stick 4K 6.2.7.1 93/6.2.7.7 Revised NOTE: Firmware versions after 6.2.7.7 will not work with this debloated rom. It's been a few months since I've updated this guide so be cautious with installing this. The latest...
forum.xda-developers.com
Click to expand...
Click to collapse
No it won't mess up. If you're doing the non-root method it'll reset the launcher without any consequences. If you're doing the root method, it'll show a launcher memory error (which is normal) so the process is the same whether it's clearing the cache with and without root but preferably would go with the root command solely for more memory so you're safe
Skel40 said:
No it won't mess up. If you're doing the non-root method it'll reset the launcher without any consequences. If you're doing the root method, it'll show a launcher memory error (which is normal) so the process is the same whether it's clearing the cache with and without root but preferably would go with the root command solely for more memory so you're safe
Click to expand...
Click to collapse
So I deleted my via root and re-created it:
Code:
adb shell
su
rm /data/data/com.amazon.tv.launcher/databases/mbcache.db
cd /data/data/com.amazon.tv.launcher/databases
touch mbcache.db
chown u0_a97:u0_a97 mbcache.db
chmod 600 mbcache.db
After a reboot, it deleted all the other mbcache.db* files that I did not delete myself. This one [mbcache.db] now stays at zero. No interface errors. Very weird. Everything seems to work as before.
Skel40 said:
Root Method (Works on Fire TV Stick Tank, Fire TV Stick 4K, and other Fire TV's with Root Functionality)
adb connect (your ip address or through usb adb)
adb shell
su
cd /data/data/com.amazon.tv.launcher/databases
rm mbcache.db*
touch mbcache.db
touch mbcache.db-shm
touch mbcache.db-wal
chmod 0 mbcache.db*
After its fully typed in, type ls -all and the three files should stay as zeros
Reboot and check your memory
Non-Root Method (2020 Fire TV's supported, 2016 Tank, along with other Fire TV's although the mbcache.db will fill up quickly as I recommend rooting the 4K or Tank, ADB Debugging required)
adb connect (your ip address or through usb adb)
adb shell pm clear com.amazon.tv.launcher (Success should be noticeable and the launcher may freeze up for a second as well as the recents row of your apps are gone but won't delete your apps data)
Reboot and check your memory (It'll build up sadly so I prefer entering this command like every so often it fills up)
I hope this helps anybody with the memory shortages with the stick.
Click to expand...
Click to collapse
Thank you for your helpful posts with instructions/ codes etc.
I thought I will post here even though the last post in this thread was in 2020.
I am on a fire stick 4k max (not rooted) which came with Fire OS 7.6.0.3 (PS7603/3110) for about a month using techdoctoruk app cache cleaner and it seemed to be working. Just today, available memory seem to go the opposite way. I had 1.05 GB free and this time it showed 860MB available and after running that app again, about 780 available and prompted me to find the adb codes to clear the cache and came across this thread.
Then I used the non-rooted method code that you posted to clear com.amazon.tv.launcher which gave me "success".
Now after reset, it shows 560MB available.
Is this a known issue? Is there a solution to clear and regain the memory?
"adb shell pm trim-caches 999G"... and all caches from all its gone.
Or... use the (paid) TDUK app on Amazon or the Google Play Store.
In all honesty this guide is one of the older ones I've posted and if any users here are able to try this out to see if it works then let me know if it does. There's TDUK Update Wiper and TDUK tools that help out with low memory
Another reason why your memory is low is because with the root method it forces the mbcache and other files to zero and with the non-rootable 7.6.0.3 (PS7603/3110),the memory fills up after clearing the files due to Amazons control over their os. @boxster03