Hi all
Sorry if this is a repeat but hope not.
My AFTV updated to 5.0.5. Claims an installed date of 21 Jan 16, but only recently have I noticed a number of issues, so not sure why they took so long to show up, unless 21 Jan is actually the 5.0.5 build date, rather than install. So here's what I've found (on Fire TV and stick - got both).
1. First Llama stopped working - I used LLama events with Condition/Action setup to start Kodi whenever I started Ikono (and switched logos). Testing the condition appeared to work, i.e. Kodi fired up but the difference was that in the test BEFORE you used to see Ikono fire up for a few seconds then switch to Kodi. After the 5.0.5 the test just fired up Kodi. And then when you start Ikono in the normal way, Kodi does not fire. Same for all my other "shortcuts".
2. Wukong: would not work for a while, the mouse pointer showed up by clicks did not fire off any action on AFTV side. A few reboots and messing around solved it but even now a bit flakey, compared to solid before.
3. Side-loading: cannot side-load apps now! Can connect via ADB, but running "adb install xxxxxx.apk" results in a:
error: device not found
- waiting for device -
4. Apps that update themselves, e.g. ShowBox, are failing (probably for the same reason as 3)
So is this common? I'm assuming Amazon have put in a range of changes to lock-down the device? Are there any workarounds / fixes?
Jed
JedSpink said:
Hi all
Sorry if this is a repeat but hope not.
My AFTV updated to 5.0.5. Claims an installed date of 21 Jan 16, but only recently have I noticed a number of issues, so not sure why they took so long to show up, unless 21 Jan is actually the 5.0.5 build date, rather than install. So here's what I've found (on Fire TV and stick - got both).
1. First Llama stopped working - I used LLama events with Condition/Action setup to start Kodi whenever I started Ikono (and switched logos). Testing the condition appeared to work, i.e. Kodi fired up but the difference was that in the test BEFORE you used to see Ikono fire up for a few seconds then switch to Kodi. After the 5.0.5 the test just fired up Kodi. And then when you start Ikono in the normal way, Kodi does not fire. Same for all my other "shortcuts".
2. Wukong: would not work for a while, the mouse pointer showed up by clicks did not fire off any action on AFTV side. A few reboots and messing around solved it but even now a bit flakey, compared to solid before.
3. Side-loading: cannot side-load apps now! Can connect via ADB, but running "adb install xxxxxx.apk" results in a:
error: device not found
- waiting for device -
4. Apps that update themselves, e.g. ShowBox, are failing (probably for the same reason as 3)
So is this common? I'm assuming Amazon have put in a range of changes to lock-down the device? Are there any workarounds / fixes?
Jed
Click to expand...
Click to collapse
1) Lama does not work under OS5
2) Sometimes I have to reboot as well
3) go in settings/ Developer Options/and turn off and on ADB debugging a three times ....
bula1ca said:
1) Lama does not work under OS5
2) Sometimes I have to reboot as well
3) go in settings/ Developer Options/and turn off and on ADB debugging a three times ....
Click to expand...
Click to collapse
Thanks for confirming 1), I tried AutomateIt too and it seems to have the same problem, so I suppose it's some sort of OS-level blocking of the kind of hooks that Llama and others used in the past? Guess they could argue it was a security improvement as allowing one app to start another could be abused...
Re: Wukong and side-loading being blocked.... I played a bit more and similar results to you.... I don't think the OS is deliberately blocking / preventing but there may be a bug or issue. For example if I do a reboot of the box then, say, Wukong, will work fine but then tried:
adb kill-server
adb start-server
adb connect xx.xx..x.xx
and then quick test with: adb shell
and get the error: device not ready.
Do a reboot, don't connect Wukong and try the above commands and adb shell works (quick test) and then any commands like adb push / install work too. But then Wukong seems blocked, e.g. may connect as mouse pointer but using the click function does nothing, or may not connect at all.
I'll try your fix of the ADB debug off/on instead of reboot; and see how that goes.
Fun times!
Wukong seems working fine for me but the remote mouse for fire t.v. unable to click
did you carry on using your device as is with the same data from the old version?i.e. no factory reset after the update?
i ask because things often break after an OTA.
i factory reset my fire stick after the update and then again after kingroot(do not push super su on it yet if you want root-wait for a pre-rooted image if you want super su).
so after re-logging in, i enabled adb, sent kodi to the device and i can launch it from Apps on the left hand side, no need to go into settings anymore or even use llama. it's there. it won't be in the recent apps, i don't know why, but at least it shows up in apps.
i don't use wukong, but i have set up my rooted phone to be a bluetooth mouse, just encase or even use my ps4 touchpad.
El_Nino9 said:
did you carry on using your device as is with the same data from the old version?i.e. no factory reset after the update?
i ask because things often break after an OTA.
i factory reset my fire stick after the update and then again after kingroot(do not push super su on it yet if you want root-wait for a pre-rooted image if you want super su).
so after re-logging in, i enabled adb, sent kodi to the device and i can launch it from Apps on the left hand side, no need to go into settings anymore or even use llama. it's there. it won't be in the recent apps, i don't know why, but at least it shows up in apps.
i don't use wukong, but i have set up my rooted phone to be a bluetooth mouse, just encase or even use my ps4 touchpad.
Click to expand...
Click to collapse
Lama is broken in OS5. Are you sure about it?
bula1ca said:
Lama is broken in OS5. Are you sure about it?
Click to expand...
Click to collapse
i never said llama works under OS5.
all i said it's not needed anymore due to kodi being available to launch from the apps menu on the left hand side.
Zenroid said:
Wukong seems working fine for me but the remote mouse for fire t.v. unable to click
Click to expand...
Click to collapse
My remote mouse for fire tv works fine on OS5 prerooted rom
Zenroid said:
Wukong seems working fine for me but the remote mouse for fire t.v. unable to click
Click to expand...
Click to collapse
Hi that's what I get sometimes, shows mouse pointer but click does not work. I find a reboot of the fire box fixes... what i've noticed it that once you have got say Wukong working then adb will not do adb - install or push: gets the device not ready error. Again a reboot will fix but then, say, Wukong won't work properly.
So it seems like something is blocking the other process - hence why I was wondering if a bug.
Take on the point about doing a factory reset from @El_Nino9 but then I'll have to reinstall and setup Kodi and my other side-loaded apps from scratch?
Jed
JedSpink said:
Take on the point about doing a factory reset from @El_Nino9 but then I'll have to reinstall and setup Kodi and my other side-loaded apps from scratch?
Jed
Click to expand...
Click to collapse
as with all factory resets, you have to redo the setup. there are tools available to back up your setups and its easy enough to adb install apps. plus you might be able to push all the latest versions of the apps back on the fire if you haven't done so already.
it depends what you want to achieve and what you want to eliminate. it all involves doing some sort of work, however i understand the more little work you have to do the better it is. no need.
El_Nino9 said:
as with all factory resets, you have to redo the setup. there are tools available to back up your setups and its easy enough to adb install apps. plus you might be able to push all the latest versions of the apps back on the fire if you haven't done so already.
it depends what you want to achieve and what you want to eliminate. it all involves doing some sort of work, however i understand the more little work you have to do the better it is. no need.
Click to expand...
Click to collapse
You are right of course. Just being a bit lazy. It's mainly Kodi I worry about as I have a lots of add-ons and takes time to setup correctly. I know you can backup your Kodi configuration but never done a backup / restore of Kodi. Will take a look into it and if I can preserve my add-ons then will do factory reset and adb -install them again.
JedSpink said:
You are right of course. Just being a bit lazy. It's mainly Kodi I worry about as I have a lots of add-ons and takes time to setup correctly. I know you can backup your Kodi configuration but never done a backup / restore of Kodi. Will take a look into it and if I can preserve my add-ons then will do factory reset and adb -install them again.
Click to expand...
Click to collapse
i rooted my device and would use titanium back up. however kodi within itself has various tools.
they have an addon called back up and they also have other features.
however, on the stick, you can use storage easily unless you know how to adb well.
for simple use i would recommend titanium back up and then back up to a cloud service such as gdrive.
each user has different preferences.
if you aren't rooted just use the addon back up too or there is a 3rd party app that also does similar stuff which i've never used so can't help.
if you do decide to root, do not use supersume app after kingroot. stick to king root su until a rooted system image is released for the device. i used kingroot 4.1 from xda thread and despite it saying failed i had root.
if you're not comfortable don't do it
You can use Tasker instead of llama
I have been having some problems of Amazon updates downloading and trying to install on my FTV and FTV2 boxes. They are rooted and I tried to block using the router address blocks and using adb commands to block. However the last two days I have seen my FTV stuck at TWRP screen. I'm think the update tried to install and got stopped by TWRP.
Just wondering if there is any new methods for blocking these updates from Amazon?
Have you tried a system app remover or disabler?
If you look through your system applications, look for com.amazon.device.software.ota and attempt to uninstall it or disable it. I mostly disable packages within adb shell, su, pm disable com.amazon.device.software.ota. Just by getting rid of this package should give you an update error which is completely normal until there's a prerooted rom available for the Fire TV. Let me know if you need any help
Personally, I have an OpenDNS setup blocking stuff. I have 2 AFTV2 boxes, and much easier to setup the dns in the wifi settings, than to do other things.
Plus, I'm all set for any future devices I may get!
On a side note, I also use Blokada. And in the section to whitelist/blacklist, I came upon a 'All apps'....and it adds, just that! I did notice a lot of those same services in the mix, but unknown if I'd trust just using that to stop updates.
Hi everyone,
Iam running my G981B with Android 11 and One UI 3.1.
- I debloated it using the following post Ultimate Debloat S20.
- I reinstalled "com.samsung.android.knox.containercore" and "com.android.managedprovisioning"
When I try to setup Shelter I get the message "Device cannot be setup. If you need assistance please contact..."
When I try to setup Island I get the message "Setup of the work profile not possible. Security rules of your company..."
For Island there is the possibility to do a manual setup: Island Manual Setup
However, if I execute "pm create-user --profileOf 0 --managed Island" I get the most useless response "Error: couldn’t create User".
fw.max_users is set to 10...
Is that a common problem or do I just oversee anything else which I might have debloated and blocks the process right now ?
Thanks for any help !
Okay... obviously tripped knox prevents the device from creating a work profile.
Seriously...
So is there any viable workaround to get something like Shelter or Island running ?
I'll ask to move your thread to Q&A.
I kind of solved my problem by facilitating Samsungs' Dual Messenger functionality.
If dual messenger gets enabled it sets up a separate user profile which is used with a workprofile in order to run multiple messenger app instances.
The beauty is that you can use this to install any app within that profile using adb. So basically the feature is not limited to those few apps you can tick from the settings menu.
Credit goes to @VincentThacker who is describing the procedure here:
Add non-messenger apps to Samsung Dual Messenger?
So the creation of parallel workspaces is blocked in the Security Policy of 8.0, preventing multiple copies of the same app. However, Samsung's Dual Messenger still successfully copies apps it sees as messenger apps, and allows them to run just...
forum.xda-developers.com
One additional hint from my side:
- If you install aurora through ADB in the work profile all apps you install from this version of aurora automatically get installed on the work profile as well. So no need for installing apks through adb afterwards anymore.
flunkyball said:
Okay... obviously tripped knox prevents the device from creating a work profile.
Seriously...
Click to expand...
Click to collapse
Actually, it doesn't seem to be Knox related: If I setup the phone (Samsung S20) from scratch without FBE encryption (by flashing multidisabler), I can set up Island with the root way and/or by ADB.
If I set up the phone with encryption, Island can't be set up like described here.
gorthon said:
Actually, it doesn't seem to be Knox related: If I setup the phone (Samsung S20) from scratch without FBE encryption (by flashing multidisabler), I can set up Island with the root way and/or by ADB.
If I set up the phone with encryption, Island can't be set up like described here.
Click to expand...
Click to collapse
Good to know. However having the device unecrypted just to use Island is not an option. Currently Iam quite happy with facilitating Samsungs Dual Messenger functionality for it.
So this is an old android game. However, I have a patched version that'll run on more recent android versions. It requires you to have the data files with the downloaded updates because the servers are dead.
So far the game works on a 5T running LOS 18.1 and a S20 on stock.
However, on the 9 Pro with LOS18.1 the game says 'Update Checker' or 'Download these files' despite it already having the required files in 'Android/data'.
Also you're supposed to block the app in a firewall program or turn off WiFi and Mobile to prevent the 'Update Checker' from running. But despite doing both of those actions on the 9 Pro the game won't progress past either screen on the 9Pro.
I'm not sure how'd I'd go about solving this problem or if anyone has similar issues with old android apps.
Out of curiosity since I have two Fire TV Stick Max's on version 7.2.5.5, is the blockage from the higher firmware or from the incremental updates? One more thing. Has anyone got a logcat relating to the commands being blocked from switching launchers and disabling apps so that a potential workaround can be found?
Understanding system level access Amazon can only control I'm well aware of the commands being impossible to modify without root.