[Fire TV General] harlekinrains:
With my AFTV2 currently broken down about one day after I set it up - I mentally went through some of the steps I'm likely to repeat very soon and - also seeing that some people in here still are struggling with some aspects of it, that I already learned long ago how to cope with - I thought I share some of my reflections. :)

This is by the way not meant to be a usability review - or tips guide of Amazons own interface - which I find abysmal for the most part. Let them struggle on their own - and also, for some reason there already are in depth "reviews" of it on aftvnews (which I came to slowly accept and even somewhat like.. ;) ) - which mostly highlight aspects of it deemed positive. ;) Bravo and lull Amazon into false confidence I say... ;)

So here we go.

1. Best launcher (rooted or not) still is Firestarter. Basically because of its deep integration to app settings - which allows you to stop apps, delete their data or uninstall them in the fastest way possible. You'll need it more often than you think and its great that its there.

Change icon PPI to 144 and for your own sake - change the background to something more uplifting and also enable the text background bubbles so you get a higher text contrast, regardless of the BG image you chose.

2. Fire OS v5 and its limitation to one adb connection only isnt the enormous setback I thought it would be. Firestarter literally changes its default automatically within the first 3 seconds of it not being able to access adb - and the one click>double click combo to launch it from anywhere is good enough. Also in OS 5 there are no screen transitions, so switching to Firestarter feels more "instant".

Not having Firestarter use adb frees up you using adb from different devices. Once you are connected via adb from a PC f.e. you can also open different shells, or transfer a file and simultaneously perform another action in the shell - so thats a non issue. Also I rewrote all the scripts I use to cleanly exit adb with adb disconnect - and ultimately that works fine.

Through the two days of setting the Fire TV up and testing use cases I got a "cant connect via adb" error (because there already was another process using it) only twice - which in return can be promptly fixed by toggling adb on and off - and again - Firestarter provides a shortcut to that menu as well - so its fast, and if you use adb disconnect as intended, you dont need it very often.

3. Drop adbFire or equivalent "Helper Tools" as fast as possible - because they prevent you from learning even the simplest command line instruction, that will speed up your life in the long term. Seriously - just do it.

Also, explore the file structure of Kodi and the Fire TV (as in "look at it", try to make sense of it - not as in "I wander what happens if I delete this..."), so you can actually learn how they work. This again brings me back to the do not use adbFire or other "prepackaged" (and poorly laid out and documented) tools.

4. If you transfer single files - and most of them you usually want to drop to /sdcard/ first, you use the adb push command, because it simply turns out to be the fastest way to move stuff - at least if your OS allows you to drop a file onto the command line window to autopopulate the filepath.

If you want to transfer files and folders not directly located in /sdcard/ - either use something more GUI orientated - like AAFM ( https://github.com/sole/aafm ) (Windows cant use it to its fullest extent in its current state (on Windows you can use Total Commander (Windows Version - this time it will cost you something :) ) - which also has an adb plugin available) and or - zip the folder you want to transfer locally, then push it to /sdcard/ and then use Total Commander to unzip it into its desired location on the Fire TV.

Transferring .zip files wirelessly ultimately almost always turns out to be faster than transferring the individual files themselves. That also goes for zipping files on the AFTV using Total Commander, and then backing them up to a PC.

5. Use Total Commander. No seriously, download it from the Amazon App Store today. I know how popular ES File Explorer became from being the only free filemanager left, that was popular back in the day - but its approach to be iconographic to a fault and hiding away features in sub menus hurts its usability on any device where you try to perform actions with a remote. TC is simply better suited for the usecase.

TC also can write to the sdcard1 partition in Android 5 - either using root, or using a scripted workaround - so you generally dont have the "its not writable" issue. Also adb shell with su can write to it as well - so also use that if you need to.

You can also install Total Commanders LAN plugin ( http://www.ghisler.com/androidplugins/ ) and thereby access network shares.

6. There even is a usecase for the Amazon Voice button - because from Kodi - you can use it to launch Total Commander with just three button presses (say: "Total Commander") - which is faster than it was before - and you can also exit back to Kodi with only a few presses of the back button. Other than for this, the voice button of course is entirely useless - as we generally arent especially interested in how bad the Amazon Store is stocked (at least over here in europe... ;) ).

7. Dont use the RC3 of Kodi 16 (Jarvis) right now. With Kodi 14.2 and 15.2 you can pause a video, drop back to Amazons launcher, then into Firestarter - then launch another app, then leave it and return to Kodi - with the video (usually - if you have enough free memory) still being in the paused state. In RC3 for Kodi 16, the video auto stops as soon as you switch away from Kodi - which in the long run causes much frustration and the need for additional button presses. Just remember to manually stop a video if you dont plan on returning to it anytime soon so Kodis bookmark your current position feature triggers.

8. If you want to install a Kodi repo - its much faster to download it as a .zip file and then adb push it to /sdcard/ where Kodi can find and install it - than to "start typing" anything in Kodi itself.

At some point - create a shell script for your pc that allows adb to connect to your Fire TVs IP address by just typing adb.sh (for example) - so you dont have to type in your Fire TVs ip address each time you want to connect to it.

9. If you dont already have a NAS -get an old router with an USB port that runs dd-wrt and has NTFS support (= all newer firmwares with at least 16mb package size should have it integrated - if you use ddwrt, even some with a 8mb package size). You get a very low power NAS that also can mirror as an FTP server (faster file transfers), and can become a torrent box in case you use that stuff. The negative only is - that with 4.5-6MB/s transferspeeds tops (WLAN, but actually limited by the individual routers CPU - they are low powered, remember) compressed 1080p is the most you can wish for - out of a 10-30 USD device. Preferably run it as a stand alone and not as your main router (reboots can be performed without bringing down your whole network, processor load, ...).

edit:

10. Kodi runs a little faster on the AFTV2 than on the Fire TV Sticks - which turns out to cut out just the right amounts of seconds on Kodi plugins with an "lets aggregate everything" approach. :)