Data study · published 2026-11-03

Phone as a TV remote: what breaks, by brand

About 1 in 13 attempts to connect a phone to a smart TV over Wi-Fi fails. The reason depends on the brand far more than on the phone: Samsung loses people at the on-screen prompt, Fire TV mostly does not answer, and nearly every Roku failure is one setting on the TV.

Source: aggregated usage data from My Universal TV Remote Control on iPhone and Android, 5 August → 3 November 2026. Shares only; method and limits at the end.

12 s

median from "search for TV" to a working session, among searches that connected that day

7.6%

of connection attempts fail (about 1 in 13)

69%

of automatic reconnection attempts complete without the person doing anything

50%

of people with a working session have a TV that speaks the Android TV / Google TV protocol

Finding 1

Which TVs people actually control from a phone

Share of TV selections in the app, by the manufacturer the TV reports on the network. Samsung and LG lead, but the long tail of Android TV brands (Xiaomi, Changhong, Skyworth and white-label sets) together outweighs either of them.

BrandShare of TVs pickedProtocolGuide
Samsung 18% Tizen Free Samsung remote app
LG 13% webOS Free LG remote app
Amazon Fire TV 11% Fire OS Free Amazon Fire TV remote app
TCL 10% Roku TV / Google TV Free TCL remote app
Xiaomi 7% Android TV —
Changhong 6% Android TV —
Skyworth 5% Android TV —
Roku 3% Roku OS Free Roku remote app
Hisense 3% Roku TV / VIDAA Free Hisense remote app
Sony 3% Google TV Free Sony remote app
Vizio 2% SmartCast Free Vizio remote app

Brands under 1% omitted. "Samsung" merges the two manufacturer strings Samsung sets report.

Finding 2

Android TV / Google TV is the largest protocol group (50%)

Share of people with at least one working session, by the control protocol the TV speaks. Every protocol here runs over the local network: this app needs the phone and the TV on the same Wi-Fi and has no infrared mode, so none of these connections happens without Wi-Fi.

Finding 3

Why connections fail: the TV, not the code

Pairing codes get the blame, but a wrong or rejected code is 6% of failures. The TV not answering, timing out or refusing the port is 43%, and a prompt dismissed on the TV screen is another 23%.

FailureShareWhat it usually means
TV did not answer 23% The phone found the TV but the TV never replied. Usually the set is asleep, on a guest network, or network control is off.
Pairing dismissed on the TV 23% The PIN or "allow this device?" prompt appeared on the TV and was closed, or timed out before anyone typed the code.
Timed out 13% The TV replied once and then went quiet. Common on 2.4 GHz networks and on TVs with "fast start" switched off.
Session dropped 13% A working session ended. Most of these come back on their own (see finding 5).
Control disabled on the TV 8% The TV is reachable but set to refuse remote control. The leading failure on Roku and Hisense sets.
Connection refused 7% The TV closed the port. The leading failure on TCL sets, where network control is off by default.
Pairing failed 6% A wrong code, or the TV rejected the handshake.
Other 7% Certificate errors on a few Android TV builds, generic errors.

Finding 4

Each brand fails in its own way

The leading failure inside each brand, its share of that brand's failures, and the fix that addresses it. This is the table to read before buying a new remote: on Roku and Hisense the problem is almost always one TV setting.

Samsung

35% · The "allow this device?" prompt on the TV is dismissed next: TV did not answer, 32%

Pick the phone from the TV prompt within 30 seconds; if the prompt never shows, turn on Settings → General → External Device Manager → Device Connection Manager.

Samsung Wi-Fi setup guide →

LG

36% · TV did not answer next: session dropped after working, 25%

Pairing itself rarely fails on webOS. Keep "Mobile TV On" enabled and the TV on the same 5 GHz band as the phone.

LG Wi-Fi setup guide →

Amazon Fire TV

76% · TV did not answer next: pairing dismissed, 15%

The Fire TV must be awake and on the same Wi-Fi as the phone; a sleeping stick never answers. When it does answer, a four-digit code appears on the TV and goes into the app once.

Fire TV remote not working →

TCL

31% · Connection refused by the TV next: pairing dismissed, 20%

TCL Google TV sets close the control port until network remote control is enabled; TCL Roku TV sets behave like Roku below.

TCL remote not working →

Roku

88% · Control disabled on the TV next: session dropped, 9%

Settings → System → Advanced system settings → Control by mobile apps → Network access must be "Enabled" (older Roku OS versions call it "Default"), not "Limited" or "Disabled".

Roku TV remote guides →

Hisense

52% · Control disabled on the TV next: session dropped, 14%

Hisense Roku TV follows the Roku setting above; Hisense VIDAA sets need the phone on the same network, no guest Wi-Fi.

Hisense remote not working →

Finding 5

Twelve seconds to connect, and most drops heal themselves

Of the people who started a TV search, 37% reached a working connection within one day (an ordered search → connection funnel), and among those the median wait from starting the search to a working session is 12 seconds. The other 63% did not connect within a day; the data does not say why.

Working sessions drop often, about 45 drops per 100 sessions over the window, typically when the TV sleeps or the phone leaves Wi-Fi. The app then tries to reconnect on its own, and 69% of those attempts complete without the person doing anything.

Try it on your TV

One app for Samsung, LG, Sony, TCL, Fire TV, Roku and Vizio sets over Wi-Fi. Free to use.

Download Free App
No 2-tap paywalls · No credit card · Basic controls free forever
Free on the App Store
4.8 App Store Rating
100% Free Basic Controls
No 2-Tap Paywalls
Wi-Fi · No Bluetooth

Method and limits

Questions

How was this measured?

From the app’s own aggregated usage events (Amplitude), both iPhone and Android, 5 August to 3 November 2026. A connection attempt is one try to open a control session with a TV the phone had found on the network. Each share uses the denominator named in its section: TV selections (a person counts once per brand) in finding 1, people with a working session per protocol in finding 2, failed attempts in findings 3 and 4, people who started a search in finding 5. Raw failure counts are not published because they only track how common a brand is.

Does a phone remote app work without Wi-Fi?

Not this app, and not any of the protocols studied here (Android TV, Tizen, webOS, Fire TV, Roku, SmartCast, VIDAA): they all run over the local network, and this app has no infrared mode. Some Android phones ship an infrared blaster that a separate IR app can use with older TVs; iPhones do not.

Why are Roku and Hisense failures so different from Samsung and LG?

Roku TVs ship with a "Control by mobile apps" setting that can be set to Limited or Disabled, and that single setting explains 88% of Roku failures and about half of Hisense failures. Samsung and LG have no such switch; their failures are the pairing prompt being missed or the TV not answering on the network.

Can I reuse these numbers?

Yes, with a link to this page. Cite the window (5 August to 3 November 2026) and the app (My Universal TV Remote Control, iOS and Android). The study is refreshed when the mix moves; the date at the top is the version.

All TV brand remote guides →