Universal Remote Only Turns the TV On: Fix a Partial Code
A universal remote that switches the TV on and does nothing else may not be faulty at all: it can be holding a code that covers only part of your TV's command set, because the auto-search is built to stop as soon as the TV reacts to a single command.
Quick answer
A partial code match means the universal remote is set to a code that carries only some of your TV's commands — usually power, and little else. Manufacturers reuse parts of a code set across models, so the auto-search can stop on a code that switches the set on but ignores volume, source and menu. The next step is to continue the search instead of saving the first code that responds, testing volume, source and menu on each candidate before you keep it.
- 1.Press the TV device key first, then retest — a wrong device mode looks identical.
- 2.Resume the code search from where it stopped instead of restarting it.
- 3.Test volume, source and menu on each candidate code before you save it.
First, check which remote you're holding
If the remote that only powers the TV is the one that came in the box, this isn't a code problem and nothing below will help. On many original remotes for current smart TVs, the navigation keys travel over a wireless pairing with the television while the power command does not; check your TV's manual to see whether its remote has to be paired. When the pairing drops, power keeps working and everything else dies — the same visible symptom from the opposite cause. That case is covered in our guide on an original remote where power works but the buttons don't.
This article is about the other situation: a third-party universal remote you programmed yourself — a GE or Jasco, an RCA, a One For All, a cable or set-top box remote, a hotel-style replacement — that now switches the TV on and stops there.
What a partial code match actually is
Universal remotes don't learn your TV. They store a large library of manufacturer command sets and replay one of them. Jasco, which makes the GE-branded remotes, calls the failure mode partial code functionality: the remote is running a code that controls only some of your device's functions. Their support documentation explains why it happens — manufacturers reuse portions of their codes across alternate models, so a code built for a sibling model can carry your TV's power command without carrying the rest.
Now look at how the auto-search is designed. You start the search, the remote steps through codes one at a time, and you are told to stop the moment the television reacts. The reaction the procedure asks you to watch for is the set switching off. That is a single command. Nothing in that test says anything about volume, input switching or the menu.
The result is a code that answers on power and fails on everything after it: not a faulty remote and not a mistake in the procedure, but a stop at the first partial match instead of the first full one.
Check these in order, most likely cause first
Work down the list. Each item either confirms or eliminates one cause, and they're ordered from the quickest to check to the most laborious.
- 1You saved the first code that responded. If you programmed by auto-search and stopped as soon as the TV switched off, treat this as a partial match until you've proved otherwise. It's the first thing to rule out before you look anywhere else.
- 2The remote is in the wrong device mode. On a multi-device remote, volume and source can be aimed at the cable box or DVD mode while power still reaches the TV. Press the device key for the television and retest before touching anything else.
- 3Volume is routed somewhere else on purpose. Universal remotes can lock or punch through the volume keys to a soundbar or receiver, in which case they will never move the TV's own volume no matter which code you find.
- 4The batteries are fading. If keys respond at arm's length but not from the sofa, or respond only intermittently, fit fresh batteries before you blame the code.
- 5Your TV never had that function. If only one or two unusual keys are dead — a sleep timer, a picture-in-picture key — the code may be correct and the feature simply doesn't exist on your set. Jasco lists this explicitly as a second cause of partial button response.
- 6The code library has nothing better. Uncommon, but if you've worked through the brand's full list and every code covers the same subset, that remote and that TV may not have a complete match available.
What responds tells you which cause it is
Note the exact pattern of working and dead keys before you start reprogramming. The pattern is diagnostic.
| What responds | Most likely cause | What to do next |
|---|---|---|
| Power only, nothing else | Partial code match | Resume the code search and test the full key set on each candidate before saving |
| Power and channel, but not volume | Volume assigned to an audio device, or volume lock is enabled | Look up your remote's volume-lock or punch-through setting and reassign volume to the TV |
| Power, volume and channel, but not source or menu | Partial match on a closely related code set | Work through the other codes listed for your TV brand rather than starting a blind search again |
| Everything works, but only from very close | Weak batteries or a blocked infrared path | Fit fresh batteries and clear the line of sight to the TV's infrared window |
| Nothing in one mode, everything in another | Wrong device mode selected | Press the device key for the television, then retest |
| One or two unusual keys dead, rest fine | The TV doesn't have that function | Nothing to fix — the original remote didn't have it either |
Test from about a metre away, pointed at the TV's infrared window, with the set already on.
Partial code match vs lost pairing vs wrong device mode
These three produce a nearly identical description — "it turns the TV on but nothing else works" — and need completely different fixes. Two questions separate them: which remote is it, and what happens when you press the device key.
| Clue | Partial code match | Lost pairing | Wrong device mode |
|---|---|---|---|
| Which remote | A universal remote you programmed yourself | The remote that came with the TV | Any multi-device universal remote |
| What the power key does | Works reliably | Works reliably over infrared | Depends which mode is selected |
| Pressing the TV device key | Changes nothing | Not applicable — no device keys | Everything starts working |
| Fitting fresh batteries | Changes nothing | Changes nothing | Changes nothing |
| Holding the remote closer | Changes nothing | Changes nothing | Changes nothing |
| What actually fixes it | Continuing the code search to a fuller code | Re-pairing the remote to the television | Selecting the right mode before each command |
If fresh batteries and proximity both change the behaviour, you have a power or line-of-sight problem, not any of these three.
How to run the code search without stopping too early
The procedure below is the general shape of an auto code search. Key names and timings differ by manufacturer, so pair it with the instructions for your exact remote — the point here is what to do at the moment the TV first reacts.
- 1
Turn the TV on by hand
Use the power button on the set itself, or the original remote if you still have it. Starting from a known-on state makes the search's signal unambiguous: the TV switching off means a code landed. Jasco's published auto-search procedure also begins with the television switched on.
- 2
Put the remote in TV mode before you start
Press the device key for the television first. On a multi-device remote every command you send afterwards belongs to whichever mode is active, and a search started in the wrong mode stores the result against the wrong device.
- 3
Look up your own remote's search procedure
The entry key varies — setup, code search, magic — and so does how many codes each press sends. Use the manual or support page for your exact model. While you're there, check one thing specifically: whether your remote can resume a search where it left off, or whether stopping means starting over.
- 4
Start the search and let it step through
Point the remote at the TV's infrared window and follow your model's stepping procedure. Allow the set a couple of seconds to react after each code before you decide it didn't respond — reacting slowly and not reacting look the same if you rush.
- 5
When the TV reacts, do not save it yet
This is the step that goes wrong. The search's only test was power. Treat the reaction as a candidate, not as an answer.
⚠ Confirming the code here is exactly what leaves people with a remote that does nothing but switch the TV on and off.
- 6
Test the full key set on the candidate
Volume up and down, mute, channel up and down, the source or input key, menu, all four arrows, OK, back or exit, and the number keys if your TV uses them. Any dead key means this code is a partial match and you are not finished.
- 7
Resume the search rather than restarting it
If your remote can continue from where it stopped, do that — it moves to the next code instead of dropping you back at candidates you've already rejected. If it can't resume, write down how far you got so you recognise the same code when it comes round again.
- 8
Repeat until a candidate passes the whole test
Manufacturers reuse parts of a code set across models, so the library may hold other codes for your brand that cover more of its functions. There is no fixed number of codes to reject before one passes, and no guarantee that a complete one exists for your set — the signs that it does not are further down. That's the process working, not failing.
- 9
Store the passing code, then write it down
Confirm the candidate with your remote's save step. If your remote or the brand code list exposes a code number, record it somewhere you'll find it — on some remotes a battery change wipes the programming and you'd otherwise repeat the whole search.
Three causes that get mistaken for a partial code
Before you start a code search, rule these out. All three produce the same complaint and none of them is fixed by finding a different code.
The remote is in the wrong device mode
A universal remote has to be told which device it's talking to before each set of commands. The device keys put the remote into the mode for one device, and it stays in that mode until you press a different device key — your remote's manual lists which key selects which device.
That's how you end up controlling a cable box with the volume keys while the power key still reaches the TV. The tell is instant — press the TV device key, then press volume. If it works, there was never anything wrong with your code, and the real habit to build is pressing the device key first every time.
Volume is deliberately routed somewhere else
Universal remotes commonly let you pin the volume keys to one device regardless of which mode you're in. One For All documents this for its Smart Control models as associating the volume keys with a particular device; other manufacturers describe the same behaviour as a volume lock or punch-through. It's a feature, and a good one when your sound comes from a soundbar.
It also means that if volume was assigned to an audio device — by you, by a previous owner, or by a setup routine — no TV code you find will ever move the TV's own volume. Check whether the soundbar or receiver is responding when you press volume. If it is, you're looking at a routing setting in your remote's manual, not at a code problem.
The batteries are on their way out
Weak batteries are a common cause of erratic remote behaviour, and they are worth eliminating first because it is the quickest check on this list.
The signature is different from a code problem, though. A dying battery gives you inconsistency: keys that work close up but not from the sofa, presses that sometimes land and sometimes do not, behaviour that degrades with use. A partial code match is perfectly consistent — the same keys work every time and the same keys are dead every time. If your symptom is consistent, batteries aren't your answer.
Mistakes that keep people stuck on this
- Restarting the search from the beginning after every rejected candidate, which walks you back into the same partial code repeatedly.
- Testing only the volume keys. Volume can be routed elsewhere, so it's the one key that can fail for a reason unrelated to the code. Test source and menu too.
- Judging the source key when only one device is connected — nothing visibly changes, so a working key looks dead. Test it with two inputs in use, or watch for the input banner on screen.
- Assuming the code printed next to your brand in the list is correct because the brand matches. Brands ship many code sets; the list is a starting point, not a guarantee.
- Testing from across the room with something in front of the TV's infrared window. Get within a metre with a clear line of sight while you're diagnosing.
- Confusing the TV's volume with the soundbar's. If the on-screen volume bar doesn't move but the sound does, the TV isn't the thing being controlled.
If you're programming from scratch rather than fixing an existing setup
The code search itself — how to program a universal remote when you have no code list at all — is a separate procedure with its own quirks. This guide assumes you already ran it once and stopped too early. The two go together: the search gets you to a candidate, and the full-key test tells you whether to keep it.
Signs this remote won't ever fully control your TV
Sometimes the answer is that you have the wrong remote for the job. These are the signals worth recognising before you spend another hour searching.
- Your TV's original remote has a microphone and few physical keys, and the set's main functions are reached through voice or an on-screen pointer. Infrared code libraries generally can't reproduce those.
- The television has no visible infrared receiver window and its manufacturer directs you to a phone app for control. A code-based universal remote has nothing to talk to.
- The universal remote physically lacks the keys you need — no dedicated source key, no coloured keys, no settings key. No code adds hardware.
- The remote is noticeably older than the television. Its code library was fixed when it was made and can't contain code sets published afterwards.
- You have worked through every code listed for your brand and every one of them covers the same limited subset. At that point the library genuinely has no better match.
The short version
A universal remote that only powers the TV is holding a code that covers part of your set's command list. It happens because the auto-search tests one command — power — and tells you to stop as soon as you see it, and because manufacturers reuse portions of a code set across related models.
The correction is a habit rather than a trick: when the TV reacts during a search, don't save. Test volume, source and menu first, and only confirm a code that passes all three. Before you start, rule out the wrong device mode, volume routed to a soundbar, and tired batteries: three causes that produce this same symptom without being a partial code.
Check these before you buy
- Check that the TV's main functions still work over infrared at all. If the original remote reaches the menu only through voice or an on-screen pointer, a code-based universal remote won't reproduce those.
- Confirm the remote has the physical keys you actually use — a dedicated source or input key and a settings key are the ones most often missing.
- Prefer a remote whose manufacturer publishes a current, searchable code list and a support page for your TV brand, rather than one that ships only a printed insert.
- Check whether the model can resume an interrupted code search. Resuming skips the codes you have already rejected instead of making you test them again; the manual for your model will say whether it is supported.
- If your sound comes from a soundbar, check that the remote supports assigning the volume keys to a chosen device, and that the procedure is documented.
Signs it will not fit
- The TV's original remote has a microphone and very few keys, and the set is driven mainly by voice or an on-screen pointer.
- The television has no visible infrared receiver window and its manufacturer directs you to a phone app for control.
- The universal remote physically lacks the keys you need, such as a source or settings key.
- The remote is clearly older than the television, so its fixed code library predates the TV's code set.
- Every code listed for your brand covers exactly the same limited subset of functions.
A visual match does not guarantee compatibility. Check the exact reference printed on your TV or on the original part before ordering anything.
Frequently asked questions
Why does the power button work if the code is wrong?+
Because the code isn't wrong, it's incomplete. Manufacturers reuse portions of their command sets across related models, so a code built for a sibling model can carry a power command your TV recognises while its volume, input and menu commands don't match. The auto-search only ever tests power, so a code like that passes the test and fails everything after it.
Do I have to start the code search from the beginning again?+
Not necessarily. Some universal remotes can resume a search from where it stopped, which skips the candidates you already rejected instead of making you test them again. Check your remote's manual for whether resuming is supported — it's the detail that decides how the rest of this procedure goes.
How do I know whether volume is going to my soundbar instead of the TV?+
Press volume and watch the television's own on-screen volume bar. If the bar doesn't move but the sound level changes, the remote is controlling the audio device. Universal remotes offer this deliberately — One For All calls it associating the volume keys with a device, and other makers call it a volume lock or punch-through — so the setting to change is in your remote's volume options, not in the TV code.
My original TV remote also only does power. Is this the same problem?+
No, and it's worth being precise about it. On an original remote for a modern smart TV, most keys travel over a wireless radio pairing while power stays on infrared. When the pairing is lost you get the same visible symptom from the opposite cause, and the fix is re-pairing the remote to the TV rather than hunting for a code.
Is it worth trying every code in the brand list one by one?+
It's a reasonable approach if your remote can't resume an auto-search, and it's often faster than it sounds because you're only testing three or four keys per code. Test volume, source and menu on each one. If you exhaust the list and every code covers the same limited subset, the library doesn't hold a fuller match for your set.
Will fresh batteries fix a partial code match?+
No. Batteries are worth changing first because it takes a minute and rules out a genuinely common cause, but the symptoms differ. Weak batteries give inconsistent behaviour that varies with distance and repetition. A partial code match is consistent: the same keys work and the same keys stay dead, every single time.
Sources
- Official source: Jasco — Universal Remotes FAQ (partial code functionality) · 2026-07-20byjasco.com
- Official source: Jasco — Auto Code Search procedure · 2026-07-20byjasco.com
- Official source: One For All — Associating the volume keys with one device (URC7955, URC7980) · 2026-07-20www.oneforall.com
Related articles
Related troubleshooting guides
Still not fixed?
Try the guided diagnosis for your symptom, or browse problems by category.