Aroma IPTV: what to do when a channel stops

Work outwards, not inwards

Almost every playback complaint is one of four things: that channel, that device, that network, or the line itself. They are listed in that order on purpose, because that is the order of how likely they are, and testing them in that order takes about five minutes and settles the question without anybody guessing.

The instinct is to start at the far end - to assume the service has failed and to open a support thread first. It is an understandable instinct and it is usually wrong, which matters because the thread then takes an hour to arrive at information you could have had in five minutes. Aroma IPTV support will ask for the results of these tests anyway, so running them first is simply the fast route to the same place.

Test one: another channel

Open two or three other channels, preferably from a different group. If everything else plays, the line is live, the credentials are correct, the network is adequate and the device is fine. One channel out of a large line-up is a source problem at the far end, and it is the single most common report there is.

A source that has gone down is usually restored without anyone having to ask, because it affects everybody on it rather than only you. Reporting it is still worth doing, but do it knowing that the rest of the service is working, because that framing gets a useful answer much faster than a message saying nothing works.

Test two: another device

If nothing plays at all, try the same credentials in a player on a phone. This is the reason it is worth keeping a player configured on a phone even in a household that only ever watches on a television: it takes ten seconds to answer a question that otherwise takes an evening.

If the phone plays and the television does not, the line is fine and the fault is in the television, its player or its connection. If the phone also refuses, on the same Wi-Fi, the test has not separated the network from the line yet, which is what the third test is for.

Test three: another network

Turn Wi-Fi off on the phone and let it run on mobile data. This is the most valuable single test in the whole list, because it is the only one that steps outside your own house.

If channels play on mobile data and not on the home connection, the line is healthy and something between your router and the outside world is the problem - congestion in the evening, an overloaded router, or a connection doing something to streaming traffic. If nothing plays on mobile data either, the line itself is the thing to report, and now you can say so with evidence rather than with a hunch.

When changing host is the right fix

Occasionally the server address on your line stops answering well from where you are while the account behind it is perfectly healthy. The symptom is distinctive: the player connects and lists the catalogue, but channels refuse to start or start and immediately stall, and it behaves the same way on every device in the house including one on mobile data.

That is what the host change tool on the change host page exists for. It swaps the server address while the username, password and expiry stay exactly as they are, so nothing else about the subscription changes. It is worth being disciplined about this, though: changing host is the right answer to that specific pattern and the wrong answer to a single dead channel, where it will achieve nothing and cost you the time it takes to retype the address on four devices.

Buffering that only happens in the evening

Buffering confined to peak hours is rarely a fault anywhere in particular. It is contention: your connection, the local exchange and the source are all busier between eight and eleven at night than they are at three in the afternoon, and a live stream has nowhere to hide because it cannot buffer minutes ahead the way an on-demand app does.

Three things help, in descending order of effect. Put the television on a cable instead of Wi-Fi, which is worth more than every other change combined. Play a lower-resolution version of the same channel where the group offers one, since a 4K stream and an HD stream of the same event ask very different things of a connection. Finally check what else in the house is running, because one large upload can ruin an evening of live television and nothing in the player will tell you so.

Things that look like faults and are not

Several common complaints have nothing wrong behind them at all:

• A programme guide that is empty for the first few minutes, which is a player still downloading it
• A guide that is correct but shifted by several hours, which is the timezone set on the device
• A first catalogue load that takes a minute or two on television hardware, and never takes that long again
• A stream that drops whenever a second device starts playing, which is a connection limit on the plan rather than a fault
• Softening and dropped frames on 4K only, which is a device decoding in software because it has no hardware support for the codec

Each of those is fixed on the device or on the plan rather than by anyone at this end, and each of them is reported as a broken service several times a week.

What to send support

When the tests point at the line, the difference between a fast answer and a slow one is entirely in what the first message contains. Send:

• Your order number, which identifies the plan and the line without anything else
• The exact channel or channels affected, by name
• What the other channels did, which is the result of test one
• What happened on a second device and on mobile data, which is tests two and three
• The device and the player, by name and platform

That message can be answered in one reply. A message saying that it is not working cannot be, and the thread then spends its first hour collecting exactly the five items above. The contact form keeps them together in one place, and WhatsApp is faster if you have the order number to hand.

Four questions that follow a bad evening

Does a reinstall ever help? Rarely, and it costs you the configuration. Reinstalling replaces the player, but almost nothing on this list is a player fault. Exhaust the three tests first.

Should I change host straight away when something breaks? No. Change host answers one specific pattern: catalogue lists, channels refuse, every device affected including one off the home network. Outside that pattern it changes nothing.

Is a VPN worth trying? Sometimes, and only after the mobile data test has shown that the home connection is doing something the mobile one is not. A tunnel adds a hop, so it can just as easily make buffering worse.

Can support see what my device is doing? No. Everything that reaches this end is the state of the line and the record of the order. That asymmetry is exactly why the five items above matter so much.