yashsingh1/xdaforums huggingface dataset:
[Fire TV Themes and Apps] Y314K:
Will do, I decided to hook up my last FTVS to take the update but it's not its turn yet. First I did a Factory Reset on it. I was gonna see if it made a difference to update without FireStarter & then ES Explorer installing it. But since I don't know how long the update will take to reach this FTVS I'll go ahead & install FiresStarter on it.

This is a FTVS I got to not root & to try out & eventually gift since my main FTV's are rooted 1st Gen FTV's & I can't stand the speed of FTVS's. Got used to my FTV1Gen navigation speed.

I did ran into an odd thing on this FTVS. When I tried to install ES Explorer. it actually left it "Queued" for a long time. Over a minute. First time I've seen that. Guess their servers are a bit slow today.

---------- Post added at 03:08 PM ---------- Previous post was at 02:54 PM ----------

Also in #3 - Click ADB OFF/ON/OFF/ON/OFF/ON/OFF at leas 3 cycles. It made a difference when using one of the ADB programs before.

Also make the "Startup Application" option into "- No Action -". in FireStarter before your final restart.

And the "Home Button Single Click Application" option into "- No Action -" too.

We are trying to see if turning off any of the options in FireStarter lets it survive a restart.
[Fire TV Themes and Apps] drkbg:
So no firestarter anymore?
[Fire TV Themes and Apps] Kdog65:
My take is that 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.
[Fire TV Themes and Apps] dh3lix:
fyi:

* removed firestarter using adb

* pushed firestarter apk to aftv

* disabled ADB on AFTV and did a reboot just to make sure all ADB connections are srsly dead ;)

* installed firestater apk using es fileexplorer WITHOUT starting firestarter afterwards.

* firestarter is visible in the installed apps list in aftv

* rebooted aftv

* firestater is gone from installed apps and cannot be launched

* apk is still installed when checking with reenabled ADB.

--rgds marcO
[Fire TV Themes and Apps] guppieman:
I for one just like the look and ease of FireStarter better than the native home screen. I really hope the devs find a solution to bring this app back to use.
[Fire TV Themes and Apps] Y314K:
If you let your FTV(S) update then you will loose FireStarter for now.

The Kodi/SPMC install/update feature alone makes FireStarter a must have app. Even if I was to turn off all the home detection or other home button shortcut options. Being able to go to a starter that gets rid of all the system apps & that lets me change the order makes it more then worth it. I hope this gets resolve.

Might be something to try. But I hope it doesn't turn into a whack-a-mole solution. If Amazon can get away blocking FireStarter. Amazon will come after Kodi/SPMC next.

Here, here. :good:

---------- Post added at 01:27 PM ---------- Previous post was at 01:10 PM ----------

Yeah, we are trying to help by diagnosin the problem. Since we don't know when the developer will have access to the update.

Thanks for trying. So it seems that the new Amazon FW checks/blocks for FireStarter at boot/startup. To bad there is no way to check what changes are made in /Data since this update is going into non rooted devices.

I do wonder if it's related to KingRoot & the stuff it installs. And FireStarter just got group into it. Just a thought.

Wonder if it's time to start hammering Amazon support about what happen to FireStarter after the update.

Will let you know if I come up with any other ideas to test....
[Fire TV Themes and Apps] axxel6307:
firestarter problems

Been using this for months and it's been great. After I updated my fire stick kodi to jarvis last week, I've had some issues. Today, my firestarter disappeared and does not show up in settings. I went in es explorer and saw it in there and it could not open it. I uninstalled it and then reinstalled it with adb fire. I'm able to go into it and open it, but the settings don't work. When I set it to double click to take me to firestarter, it opens up my fire stick apps library, and when I restart my fire stick, it disappears again. I've already factory reset my fire stick and re installed firestarter, but it does the same thing.

Any suggestions?
[Fire TV Themes and Apps] MacSeoin:
I noticed the "Filtering Apps" pop up in manage installed apps too so firestarter has to be blocked somehow

---------- Post added at 08:45 PM ---------- Previous post was at 08:39 PM ----------

how can they block fully legal working apps? its the add-ons that are illegal so I doubt that will be possible.

I understand them blocking the launcher but if they block the apps they will lose more custom than they currently do.
[Fire TV Themes and Apps] Swifty:
Is there any way to have a shortcut for prime video / prime music on the Fire TV using firestarter without having to show all system apps?
[Fire TV Themes and Apps] spotmark:
Really hope you guys get this working again. I managed to block the update on my bedroom Fire TVs, but my Living room box got updated. I hate the look of Amazon's home screen.
[Fire TV Themes and Apps] axxel6307:
Did anyone else factory reset and now and having trouble pushing kodi back to it? Before I realized it was an amazon update that broke firestarter, I wiped my fire tv stick to start fresh. Now, I'm trying to install jarvis back on it and it's going on 30 minutes now, when before would only take 10 seconds using adb fire.
[Fire TV Themes and Apps] Y314K:
[MENTION=3843473]dh3lix[/MENTION] & others with the update.

My FTVS just took the update. I had disabled most FireStarter options + ADB Debugging before the update. Sure enough, FireStarter is gone from menus. And it wont let me start it from within ES Explorer.

Plan to try some more stuff. We should test other launchers like Nova or Square Launcher to see if it's a Launcher wide ban/filter or just for FireStarter.

I am also going to do a Factory Reset after the update & after testing a few things. Including trying older versions of FireStarter.

Not at this time. It's All or None for now. I believe it's on the wishlist. But no news from the developer right now. Also he has bigger fish to fry right now, aka latest update.

Did you try older version of FireStarter ?

Well they could of had a pop-up saying that having FireStarter installed after the update can make functions malfunction. But they decided to just deny us FireStarter without any explanation or heads-up. Also Amazon already kicked Kodi out of their store. If they think they can get away with it. They would love to kick it out of their devices.

I really hate the new Amazon double tap Apps Library option. If you have not made your installed apps favorites. Then you have to go fish thru hundreds of apps if you have bought/added apps after you installed said app.

Really hope there is a workaround.
[Fire TV Themes and Apps] mortcw:
Exactly the same thing here
[Fire TV Themes and Apps] Y314K:
Try installing Kodi/SPMC thru ES Explorer. Or turn ADB ON/OFF/ON/OFF/ON/OFF/ON three cycles. Then try to use your ADB program. Let use know how it goes.
[Fire TV Themes and Apps] axxel6307:
Adb fire is still running and attempting to install it. Do I need to stop it and factory reset again before trying that?
[Fire TV Themes and Apps] Y314K:
You probably don't need to Factory Reset unless you want to. I plan to do a Factory Reset & use ES File Explorer to install Kodi/SPMC.

http://www.aftvnews.com/how-to-side...to-the-fire-tv-using-nothing-but-the-fire-tv/
[Fire TV Themes and Apps] mortcw:
Firestarter error when trying connect to adb 3 times :(
[Fire TV Themes and Apps] Y314K:
That is normal. After failing 3 times it turns off the ADB option in FireStarter Settings. No biggie.
[Fire TV Themes and Apps] jkchr1s:
Well I did some basic troubleshooting and here's what I found...

First I tired to launch over ADB shell:

shell@sloane:/ $ am start -n de.belu.firestarter/.gui.MainActivity
Starting: Intent { cmp=de.belu.firestarter/.gui.MainActivity }
Error type 3
Error: Activity class {de.belu.firestarter/de.belu.firestarter.gui.MainActivity} does not exist.

Hmm... that's strange. So I checked for disable packages:

pm list packages -d
package:de.belu.firestarter

Ah, so they just disabled it! Let's re-enable it...

pm enable package:de.belu.firestarter
Error: java.lang.IllegalArgumentException: Unknown package: package:de.belu.firestarter

Hmm... still disabled. Now let's try to unhide...

pm unhide de.belu.firestarter
Package de.belu.firestarter new hidden state: false

So now, surely we can enable it, right? NOPE!

pm enable de.belu.firestarter
Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=31637, uid=2000, package uid=10020

Logcat gives this security exception (shell/uid 2000 used to be able to do this):

D/AndroidRuntime(31637): Calling main entry com.android.commands.pm.Pm
E/Pm (31637): Error
E/Pm (31637): java.lang.SecurityException: Permission Denial: attempt to change component state from pid=31637, uid=2000, package uid=10020
E/Pm (31637):	at android.os.Parcel.readException(Parcel.java:1548)
E/Pm (31637):	at android.os.Parcel.readException(Parcel.java:1501)
E/Pm (31637):	at android.content.pm.IPackageManager$Stub$Proxy.setApplicationEnabledSetting(IPackageManager.java:3481)
E/Pm (31637):	at com.android.commands.pm.Pm.runSetEnabledSetting(Pm.java:1512)
E/Pm (31637):	at com.android.commands.pm.Pm.run(Pm.java:175)
E/Pm (31637):	at com.android.commands.pm.Pm.main(Pm.java:101)
E/Pm (31637):	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
E/Pm (31637):	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:256)
I/art (31637): System.exit called, status: 1
I/AndroidRuntime(31637): VM exiting with result code 1.

Looks like amazon is locking down the shell user... that sucks!

---------- Post added at 06:35 PM ---------- Previous post was at 06:28 PM ----------

Looks like they changed the permissions to no longer allow sandbox users (or shell, at that) to execute the adb command. This was the loophole the author used to detect home presses via the reliable method.
[Fire TV Themes and Apps] axxel6307:
I was able to install it with ES Explorer. However, now Kodi is not showing up in recent apps, as it was before this morning right after firestarter was broken, but before I factory reset it. It does show up in my Apps Library though. This will suffice for now.

Now to restoring my backup. Can this be done with ES?

I know there is talk of Kodi getting axed next, but it makes no sense that they would allow it to be listed in the apps library if they wanted kodi gone..... I do miss firestarter though. I loved my double click quick access to it to force stop kodi when I had issues and needed to reboot it, not to mention it looks better than the Fire Tv home screen.
[Fire TV Themes and Apps] Y314K:
Great amount of info. So out of all apps out there. They are starting with FireStarter. Guess it's pitchfork time for Amazon Support. Will probably start calling & chatting tomorrow.

---------- Post added at 05:45 PM ---------- Previous post was at 05:37 PM ----------

You should be able to use ES Explorer since your just copying & pasting & overwriting. Not as easy as ADB App programs but it works.

FireStarter was on the Amazon Apps menu before it was blacklisted. So that doesn't mean anything. I hope there is a workaround soon. But that will take a new APK. :mad:
[Fire TV Themes and Apps] mortcw:
On my second firetv stick firestarter works still fine - first run fire os 5.0.5.1 - second 5.0.5 - any chance to downgrade fire OS ?
[Fire TV Themes and Apps] jkchr1s:
Success! I got the project source, refactored to rename the package to "firestopper" and compiled. It installed and started right up. I rebooted and it was still there. So it appears the "block" is specific to the package name.

But the home button detection is being overwritten by the new Amazon launcher. Let me play around in logcat to see what I can figure out.

Edit: If anyone has a Fire TV lower than 5.0.5.1, can you send me the adb executable from the device? I think if we put that back in, it might just work. I'll try to pull one off my fire tablet and see if that works.
[Fire TV Themes and Apps] axxel6307:
I was able to restore my backup with adbfire. Wonder why that worked but pushing kodi with adbfire didn't?
[Fire TV Themes and Apps] mortcw:
Great keep going - fingers crossed :)
[Fire TV Themes and Apps] axxel6307:
Yeah I did and it was also uninstalled at reboot, and I left everything as "no action" in settings.
[Fire TV Themes and Apps] jkchr1s:
Man this build is much more locked down than previous ones. :(

I got a copy of adb from my FireTV running < FireOS 5, but I think it's too old.

Anyone without the latest build on FireOS 5, can you run from your machine:

adb pull /system/bin/adb

and pull the adb executable?
[Fire TV Themes and Apps] eXOBeX:
Got it (had to rename it to adb505 at the MacBook end to stop it stomping over ADB itself). Where d'you want it?
[Fire TV Themes and Apps] jkchr1s:
Just drop it on a fileshare site and PM me a link if you don't mind. :)
[Fire TV Themes and Apps] mortcw:
Well - need little help ? how to pull adb executable ?
[Fire TV Themes and Apps] jkchr1s:
eXOBeX got it. Thanks though :)
[Fire TV Themes and Apps] eXOBeX:
http://www.filedropper.com/aftv505

Entire /system/bin/, last chance to grab it as my AFTV's offering the update.
[Fire TV Themes and Apps] jkchr1s:
Thanks! :)
[Fire TV Themes and Apps] eXOBeX:
No worries. Pulling all of /system/ now in case anything comes in handy down the line.
[Fire TV Themes and Apps] jkchr1s:
It worked with that adb file. :)

Let me set up a fork repo and I'll link you guys to it.
[Fire TV Themes and Apps] eXOBeX:
Like FireStarter, but different. Not so much FireStarter as Twisted FireStarter :)
[Fire TV Themes and Apps] jkchr1s:
Source here: https://github.com/jkchr1s/FireStarter/tree/master/FireStarterProject

Let me know if it works and I'll send sphynx02 a pull request. All I did was change the package name to de.belu.firestopper to get around the amazon blacklist and bundle adb.

Note: This will NOT work with FireStarter automatic updates! Not sure about Kodi updates, but at least the launcher works again.

EDIT -- Removed APK and sent [MENTION=3172973]sphinx02[/MENTION] a pull request with a proposed patch to work around this. :good: :D
[Fire TV Themes and Apps] dcol456:
?

I'm confused. My firestarter is gone but KODI works fine. Do I really need firestarter?
[Fire TV Themes and Apps] Y314K:
Good to know.

After the FireOS 5 update. ADB apps have been a bit odd. That is why there is a rule of 3 in play. To make sure ADB dissociates from a prior program when trying to use a ADB based tool.

Great work. This was my thought. That as long as Amazon can not do a fluid block on specific packages. Then [MENTION=3172973]sphinx02[/MENTION] or someone that wants can just change FireStarter enough to let it install/run. And Amazon will have to release a new update to block those. But at the same time I wouldn't want multiple FireStarter APK versions being release by more then two folks. But branching should be fine.

Are you trying to downgrade ADB. I don't think it will make a difference. But I could be wrong.

I think the better solution will be to just change the double tap button to something like the Setting (3 lines button to the right of the Home button) as the double button option. Although if the single Home button option works fine. Them maybe the double home tap button can still work. Or maybe it can become a Triple Push Home Button Option.

I do wonder if Amazon disabled it because FireStarter likes to be the only ADB instance running at one time.

keep us posted. I know we want a fast option to get FireStarter back. But would like to hear from [MENTION=3172973]sphinx02[/MENTION] regarding what his plans & options are. Even if he doesn't have the update yet. You have given him enough info to figure out a quick solution & a long term solution too.
[Fire TV Themes and Apps] jkchr1s:
I agree, I don't want multiple versions floating around either. I just sent [MENTION=3172973]sphinx02[/MENTION] a pull request. I'll remove the APK I uploaded and let him decide if that's the path he wants to take. I was able to reboot and keep the starter auto-launching and ADB home button detection worked wonderfully.

A double press is loading Amazon's app launcher now, so I think we're going to lose the home button double-press functionality from FireLauncher.
[Fire TV Themes and Apps] Y314K:
Reasons for me to still LOVE FireStarter even with the new FireOS 5.0.5.1 features ...

Install/Update Kodi/SPMC directly from their developers with just 4 clicks of the remote.:good:

Change order &/or hide installed apps shortcuts at any time.

Custom background wallpaper.

Easy to switch back and forth between Launchers.

It's my freaking device & I will install what I want on it.:mad:

Probably forgot a few others. But the first two are VERY important to me.

Great, will test out installing Kodi & SPMC thru it.

Guys make sure you uninstall the other version of FireStarter thru ES Explorer or thru an ADB tool before installing this one. So there are no extra conflicts. :eek:
[Fire TV Themes and Apps] jkchr1s:
Let us know if the patched version works for you. I pulled the APK to avoid confusion with auto updates and such, hopefully [MENTION=3172973]sphinx02[/MENTION] will see what I did and patch his version. We really don't need different variants floating around.
[Fire TV Themes and Apps] dcol456:
I'm new to all of this. All I know how to do is put firestarter on my stick and install KODI (and use it). Once you figure out a fix will you post instructions on how to do it?
[Fire TV Themes and Apps] jediknight111:
Amazon are annoying idiots.

Would love an apk for the fixed version if someone can upload

---------- Post added at 01:30 AM ---------- Previous post was at 01:30 AM ----------

Amazon are annoying idiots.

Would love an apk for the fixed version if someone can upload
[Fire TV Themes and Apps] eXOBeX:
Working well here. I installed it alongside FireStarter then kicked off the update, so if anything's going to go wrong it's here :)

Took a while to update (black screen, pulsing white LED) but eventually kicked in. Using the config backed up from the original FireStarter a single home press (not the double as originally set) launches FireStarter, with a FireTV Home icon at the top (previously hidden) which will return to Amazonville.

Happy days!

---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------

Working well here. I installed it alongside FireStarter then kicked off the update, so if anything's going to go wrong it's here :)

Took a while to update (black screen, pulsing white LED) but eventually kicked in. Using the config backed up from the original FireStarter a single home press (not the double as originally set) launches FireStarter, with a FireTV Home icon at the top (previously hidden) which will return to Amazonville.

Happy days!
[Fire TV Themes and Apps] jediknight111:
Amazon are annoying idiots.

Would love an apk for the fixed version if someone can upload

Or a way to stop that particular update

---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------

Amazon are annoying idiots.

Would love an apk for the fixed version if someone can upload

Or a way to stop that particular update
[Fire TV Themes and Apps] jkchr1s:
Awesome, glad it worked. Please, don't spread the APK around until [MENTION=3172973]sphinx02[/MENTION] catches up on what I've found, or if he's okay with distributing it. I'm pretty sure since the package name has to change anyway, in-app updates will have to be re-implemented.
[Fire TV Themes and Apps] eXOBeX:
No worries.

Looks like it lost a lot of its settings, I think importing the config retained the background but bugger all else. I'm sure sphinx02 will get it all sorted (he's only turned his back for two minutes FFS :) ).

Oh, and FireStarter (the proper one) was being listed by FireStopper until I uninstalled it through ADB. Interesting.
[Fire TV Themes and Apps] jkchr1s:
Yeah, since the package name changed, you will unlikely be able to restore your settings (totally different directory on the file system). You'll have to set up as new.
[Fire TV Themes and Apps] Y314K:
Cool. I would of tried to open the original one from within the modded one just for kicks. :laugh:

Guys, [MENTION=6289000]jkchr1s[/MENTION] only posted the apk to test & verify the solution. Out of respect for the FireStarter developer [MENTION=3172973]sphinx02[/MENTION] the link was taken down. We hope [MENTION=3172973]sphinx02[/MENTION] can release an official update soon. He is on the other side of the world from us so he will probably won't see this until later today. Hope you all understand.

I myself run 1st Gen AFTV's so I don't even run FireOS 5 & we are only trying to help with testing & ideas. NOT to take over or fork the project. Please be patient for an official update from [MENTION=3172973]sphinx02[/MENTION] . TY :fingers-crossed:
[Fire TV Themes and Apps] loughrey101:
I highly doubt Amazon disabled Firestarter even though jkchr1s discovered it as a disabled package after the new update. What most likely happened was Firestarter conflicted with the remote coding for the new update features and the Fire TV defaulted to accomodate the new update by auto disabling in app that was conflicting with it. It'll probably be a matter of Sphinx patching the issue in a new update in such a way that it doesn't bump up against the update's new remote features. I don't really see why Amazon would have issues with a sideloaded app utilising ADB since the feature is merely a developer feature that is not an essential aspect of the general usability of the device that conflicts with Amazon's direction for the device. It's more likely a coincidence that this update broke Firestarter. Fortunately I remained on 5.0.5 and am still able to enjoy the Firestarter.
[Fire TV Themes and Apps] jkchr1s:
Unfortunately, yes they are actively disabling it. If that wasn't the case, changing the package name would not have resolved the issue.

Using a launcher puts you outside of Amazon's walled ecosystem -- you are less likely to purchase Prime / rent movies if you aren't in their launcher and constantly seeing ads and recommendations. It makes complete sense for Amazon to actively block it. The less you use their launcher, the less likely you are to purchase your content from them.

Edit - you can prove this by uninstalling FireStarter, reinstalling it, then rebooting. The app will be hidden and disabled again, and you cannot re-enable it unless you uninstall.

On top of that, they removed adb from the device to prevent home press detection. Android natively throttles activity launches on home press from activities not blessed as the active launcher. This is why the fallback method has ~ 5 sec delay. Using adb locally on the device is a loophole because this puts you as the "shell" user (who does have permission to launch activities at any time).