-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't install since newest Amazon Update (5.0.5.1) #50
Comments
Exactly the same here on an FTV Stick, worked prior to today's update which has removed it. Have also tried reinstall via ES and adb, both methods say successfully installed but app does not appear in applications and launching via adb gives the same error as above. |
I am having the same issue. I checked in es explorer and it shows firestarter in apps. it just won't run. Obviously amazon blocked it. Super lame. |
Confirmed here too. I have found a way to get it reinstalled though. Using adb, I uninstalled the apk 'de.belu.firestarter' (you can choose to keep the settings). Then I rebooted FireTV and reinstalled firestarter again once it's booted up. Firestarter now appears in your Settings>Applications>Manage Installed Applications. NOTE: If you reboot your FireTV, you WILL lose Firestarter again. EDIT: By the way, you lose the double click home button feature in this latest update. When using the double click home, it now opens up your Recent Items menu. |
Can not yet confirm as none of my 3 devices has already received the 5.0.5.1 update. If your reports are true, this is a really unfair measure by Amazon. The question is: what is the trigger for the uninstallation of the App. Either it is a special characteristic or functionality which is triggering the uninstallation or they really start to blacklist Apps on the FireTV. If this is really true I do not want to think of which App is the next one being placed on their blacklist .. Kodi?, SPMC?? On one side the new built-in double-click home-button feature kind of replaces a part of the App but on the other side this step by Amazon drastically restricts the possibilities the user have on the FireTV and will in future lead to more rooted / jailbreaked FireTV's. As soon as one of my devices has received the 5.0.5.1 update, I will further investigate and see what I can do. But this time this really sucks as it seems to be a measure targeted especially against this App. |
Thanks for looking into it when you are able to. Let me know if I can be any help testing, etc. |
Double clicking the home button now takes me to the Amazon Your Apps Library screen on the Fire TV. |
Since the update I notice that non Amazon apps show up on the recent list and on the app list on the main page. |
I have the same problem. The update is not comming on every Device. |
A little further piece of information just in case it helps you. I left Kodi running overnight as I always do. Woke up this morning and everything was fine and nothing appeared at fault. Pressed the home button on my remote to take me to -- what I thought would be -- the FireStarter main menu but instead, it took me to the Amazon home screen. I wondered where FireStarter had gone so clicked on the icon in the Recent menu. FireStarter didn't open! I got this message: "Cannot Open App. The installed version of FireStarter cannot be opened. Please check for an available update on your library." Now, things had been running fine since I managed to reinstall FireStarter the first time (my post above) but this time, the Fire TV HAD NOT rebooted and it has still managed to stop the functioning of FireStarter. Does this mean that the Fire TV is doing some sort of interval checkup to see if FireStarter is installed and if it is, it disables it? Weird. I have managed again to reinstall FireStarter and it's working ok. I will check to see if this happens again either today or overnight. |
All of the Amazon Fire TV boxes being sold directly from Amazon site will arrive with the new update once you install FireStarter & reboot the system, the system will update & remove FireStarter. It did it on all of the 5 boxes I received from Amazon on 04-02-16. Even if you master reset the box to factory original FireStarter will not stay after reboot. |
The new FTV firmware introduces an amazon native double-click function that takes you to your apps library which is probably behind the firestarter removal. It also introduces the ability to see sideloaded apps in recents which is a pretty cool enhancement. With the new recents functionality I'm starting to wonder why I would need firestarter anymore. |
@Kdog65 The kodi updater is awesome as well as the possibility to sort the apps manually. That are two important features of fs! |
Agreed, I'm sure they will get it fixed. sent from my google nexus 5
|
FireStarter als Komplett-Ersatz unter 5.0.5, man müsste dazu nur die wesentlichen "Fire TV Einstellungen" in FireStarter selbst abbilden oder aufrufen können (z.B. WLAN-Settings) :-) 1 pm hide com.amazon.tv.launcher ("Fire TV Einstellungen" lassen sich dann leider in FireStarter nicht mehr öffnen, das ADB-Menü geht aber) @sphinx02: hast Du ein Idee wie man an die "Fire TV Einstellungen" kommen kann mit deaktiviertem amazon.tv.launcher? Oder wie wäre es eine standard Settings.apk in FireStarter zu includieren? |
Same as @irn-bru, I did the uninstall-reboot-reinstall method on one of my FTV Sticks and it worked initially, left it powered on overnight as usual but have come back to try it again tonight and get the "Cannot Open App. The installed version of FireStarter cannot be opened. " etc. message so it definitely isn't only checking on boot. |
The update just got pushed through on my Fire Tv box which disabled FireStarter just like the rest of you guys. Seems like FireStarter is being BLACKLISTED because I just installed AGK LAUNCHER and It works, but compared to FireStarter it just doesn't stack up. Guess I'll be using it for now until FireStarter is back. |
@sphinx02 if you rename the package name (I tested with de.belu.firestopper) it appears to persist across reboots. However, home button detection no longer works (adb was removed from /system/bin, fallback method does not work). See log output: http://forum.xda-developers.com/showpost.php?p=66197586&postcount=524 |
Submitted PR with working build on FireOS 5.0.5.1. See #52 |
If Amazon looks at the package name to determine whether to blacklist it or not, can a random package name generator be used on install or by the end user before installing? |
Hay just a thought but don't we own the hardware, and therefor have the right to install what we want on the stick. |
The app is being blacklisted from There are currently two blacklisted apps:
So the good news is that they are hard coded, and a firmware update is required to update the list. The bad news, obviously, is that Looks like we have a cat-and-mouse game on our hands... |
So, maybe refactor the installation to be in the |
That might work, but it's just as likely that they would be more exact on package names next update. That won't be a permanent solution either. |
I'm thinking everyone can use the current code that's out there and then refactor under a name that they make up so it is not publicly disclosed. Amazon would be hitting only the known targets and all the unknown targets would still stay running. |
Any idea what the purpose of
|
How about creating an install app/script that either creates a random string for the application ID or asks the user to provide their own? Thus defeating the cat and mouse game before it really gets going. I don't do much android development myself, but since the APK is just a zip file - can the app ID be edited from the extracted zip and then the contents be rezipped? The goal being to eliminate or reduce the dependencies from the installer app. |
Probably not. You had to do this to every source file aswell, and they're compiled and therefore not possible to do "on the fly". I could be wrong tho. |
Blacklisting appnames is a comically poor idea... why not self evidently to all? Can the app provide an option for user to provide the new package name? so functions break less?
My understanding is that updates only happen once internets access is provided. . The anti"piracy" frippery of some android roms is easily overcome with an Xposed plugin |
applying anticracking against amazon |
I got pushed an Amazon update this morning, and I can't get FireStarter to install at all. Had it working well until the newest update (5.0.5.1), but all traces of it seem wiped from my FTV2. Have tried both methods (ES Explorer and adb).
When running the last step, adb gives:
The text was updated successfully, but these errors were encountered: