Trex IPTV on Fire Stick: complete setup

Before you start

The Fire Stick is the device we set up most often, and the reason it earns its own walkthrough is not that it is difficult. It is that two of the six steps happen in menus Amazon keeps hidden, and people who have installed a hundred apps on a phone quite reasonably stall at the first of them. Everything below is the full sequence for getting Trex IPTV running on one, in the order it happens, with the places people get stuck marked as they arrive.

Have two things ready before you begin: the stick powered on and connected to your network, and the email carrying your server address, username and password. If that email has not arrived yet, it is worth checking the order first, because typing credentials that do not exist yet produces an error that looks like a setup mistake.

Step one: reveal Developer Options

On current Fire OS this menu is hidden until you ask for it. Open Settings, then My Fire TV, then About, put the highlight on the device name at the top, and press the select button seven times in a row. A small notice counts you down and then confirms the menu is unlocked.

Go back one screen and Developer Options is now sitting in the My Fire TV list where it previously was not. If it is still absent, you almost certainly clicked the wrong row — it has to be the device name itself, not the storage line or the network line underneath it.

Step two: allow one app to install

Inside Developer Options there is an entry for installing applications from outside the store. Newer builds phrase this per application rather than as a single global switch, and you will be shown a list of apps to grant it to.

Grant it to Downloader by name and leave everything else alone. This is the safer arrangement and it costs nothing extra: the permission travels with the one app that needs it rather than sitting open for the whole system. Leave it that way afterwards.

If you cannot see Downloader in that list, it is because it is not installed yet. Install it first from the Amazon store — it is free and it is the one part of this that comes from Amazon — then return to this screen.

Step three: fetch the Trex IPTV player

Open Downloader and you land on a URL field with an on-screen keyboard beneath it. You do not type a web address here. You type the short numeric code published on our apps page, which resolves to the correct file at the other end.

The code exists for one reason and it is a practical one. Typing a long address with a directional pad is genuinely unpleasant, and a single wrong character produces a not-found error that looks exactly like a broken download. A short number removes both problems at once.

Press Go. The file downloads, Downloader offers to install it, and the package installer takes over. Accept, wait for the confirmation, and then accept Downloader's offer to delete the installer file. Say yes. Usable space on a Fire Stick is tight, and a leftover package in the downloads folder is dead weight you will not think about again until something refuses to install in six months.

Step four: enter the credentials, carefully

Open the player and choose the Xtream Codes login option rather than the playlist option. These are the Trex IPTV details from your activation email, and they are case sensitive throughout. There are three fields:

• Server address — exactly as written in your email, including the port number if one is shown. No trailing slash.
• Username — case sensitive.
• Password — case sensitive, and the field that catches almost everybody.

This is where more setups fail than at any other point, and the cause is nearly always a capital letter that the on-screen keyboard did not produce. Two small habits help enormously. Turn off any autocorrect the keyboard offers. And if the player has a reveal option on the password field, use it and read the string back character by character against the email before pressing sign in.

If you find the remote unbearable, there is a shortcut worth knowing: the Fire TV app on a phone gives you the phone's keyboard as a remote, which turns two minutes of hunting into ten seconds of typing.

Step five: let the first load finish

The first sign-in is the slow one. The player pulls the entire catalogue and the programme guide before it shows you anything, and on a stick with modest memory that can take a couple of minutes. It is cached afterwards and you will never wait for it again on that device.

Do not interrupt it. A load killed halfway leaves a partial catalogue behind, which then presents as missing categories and sends people back to the login screen looking for a fault that is not there.

Once it settles, do three checks before you consider the job done:

• Open a channel from a group you actually watch, not the first row in the list.
• Open a high-bitrate channel and leave it running for a few minutes. Fast motion is where an encoder or a decoder is exposed, and a stutter every four minutes does not show up in a ten-second glance.
• Look at the programme guide on a handful of channels to confirm the schedule is populating.

When something is wrong, read the symptom

Trex IPTV faults on a Fire Stick sort themselves into four families, and the family tells you where to look.

• Sign-in is refused. The credentials or the server address are wrong, or the line is not active yet. Re-read the password with the reveal option on. If it still refuses, check the order state in your account before assuming a typo.
• Everything loaded, but one channel misbehaves. That is a source matter upstream of your account, your device and your connection, and nothing you configure will touch it. Report the channel name as your app spells it.
• Everything fails at once. Look at the connection allowance before anything else, then at expiry. The mechanics are set out in why playback sometimes refuses to start.
• Pictures play but the schedule is blank. That is the guide, not the stream, and the two travel separately. Your picture is perfect and the guide is blank explains the join that has come apart.

There is a fifth case that is specific to this hardware and worth naming. If a single 4K channel breaks up while everything else is immaculate, suspect decoding rather than the network. The reasoning is in resolution is the number that matters least.

The two upgrades worth making

Once it is working, two changes will do more for the picture than anything else available on this device.

A wired connection. A Fire Stick is wireless only unless you add an adapter, and the crowded 2.4 GHz band produces retransmissions that reach your player as jitter rather than as slowness. That is why a speed test can report a healthy figure while the picture still stops. An adapter is a small purchase and it consistently outperforms buying a newer stick.

A longer player buffer. If your evenings are the problem rather than your hardware, a slightly larger buffer trades a few seconds of delay for immunity to the brief stumbles that otherwise freeze the picture. It is a setting inside the player and it is worth choosing deliberately.

If the server address itself ever needs changing — which happens occasionally and has nothing to do with your device — the change-host guide walks through it without a reinstall.

If you would rather not do any of this

The walkthrough for every other device we support, including the ones where none of the above applies, is under setup. And if a step has gone sideways, send us the screen you are stuck on from the contact page rather than starting again from scratch. A photograph of the error beats a paraphrase every time, because players word their failures differently and the wording often identifies the cause outright.