Problems switching inputs on receiver


Recommended Posts

I have a Logitech "all in one" remote which is programmed to operate my cable box, TV, receiver, and blu-ray player.

Lately, the receiver or some other component has difficulty settling on a signal. For example, my Samsung TV seems to only work on a specific resolution when watching TV. When I press the watch TV button on the Logitech remote, the cable box, TV, and receiver turn on. Rather than display a picture, I get a blue background on the TV with a message that says 'not supported mode.' I have to turn everything off and back on again several times before I can watch TV. Other times, I have to wait a few minutes before the TV detects an input from the cable box.

When I want to watch a movie, I have a similar problem. The TV is searching for inputs even though the receiver is on and the blu-ray player is on. I have to cycle through the inputs on the TV to get the movie to display on the TV. Eventually the TV detects the blu-ray input and displays the movie.

Are these problems an indication of a bad HDMI port or is something else going on?

Try taking the receiver out of the equation and see if there are still problems. Plug everything in directly to the TV and see if you have any problems with any of the sources. If everything works correctly it's probably hardware going bad on the receiver. If it still doesn't work it sounds like a hardware problem with the TV.

This sounds like a 'handshaking' problem ... try this from a Denon thread on another forum ... (different amp I know but ... )

  Quote
HDMI handshake issues with cable/sat boxes are quite common (with any brand of AVR) and are usually always the fault of the cable/sat box not being designed to be connected to an HDMI repeater (ie. AVR) which is why they work without issue connected directly to the TV. The first thing to try to resolve the issue is to ensure the source device having the issue has the latest firmware installed and has been reset (ie. powered down, unplugged for a few minutes, then powered back ON again). Next try following this turn ON order: TV first, wait a few seconds, then the AVR, wait a few seconds, and finally the source device. If this doesn't resolve the issue, then in some cases you may resolve the issue by trying the HDMI HDCP reset procedure listed below. With the 2312CI/3312CI (1913/XX13 CI models) if you are having a video issue, try setting the "Resolution" setting to the resolution of the TV(eg. 1080p) rather than the "Auto" setting.

HDMI HDCP reset

1. With all devices powered on, remove the two HDMI cables at both ends from the source device to the AVR and from the AVR to the TV.

2. Power off all devices and disconnect power cables to all devices.

3. Wait 10-15 minutes.

4. Reconnect HDMI and power cables to all devices.

5. Power on the devices in this order ... TV, wait a few secs, AVR, wait a few secs, and then source device (although this is the generally recommended order, in some instances, you may have better luck powering on the AVR first and then the TV, then the source last ... bottom line if it's still not working, try a different power on sequence).

I wonder if you can put 'pauses' between commands on your Logitech remote to make sure the components come on in the right order?

or it could be a dodgy cable of course!

ref ... http://www.avsforum....l-owners-thread

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Windows 10 KB5062649 fixes Extended Security bug, unresponsive systems, and more by Sayan Sen Microsoft has released today the non-security preview update (also known as the C-release) for Windows 10. The update, under KB5062649 and Build 19045.6159, fixes some major bugs including one for Extended Security Updates (ESU), unresponsive systems, Secure Boot, and more. Since this is a preview update for next month's Patch Tuesday it is an optional release. Microsoft says that users reported that the ESU wizard would not work correctly when they tried to use the option to extend support for Windows 10 for another year; this bug should be fixed now. The company has also fixed "stability issues" with this release as it resolves problems in the core file system. Affected users reported unresponsive systems since the May 2025 Patch Tuesday. There are other improvements as well. The full changelog is given below: ​​​​​[Extended Security Updates] Fixed: An issue impacting the Windows 10 Extended Security Updates (ESU) enrollment wizard. Some users experienced a problem where clicking “Enroll now” caused the wizard window to open, begin loading, and then close unexpectedly. This occurred due to incomplete app registration, which prevented the wizard from loading correctly. This update addresses that issue to ensure a smoother enrollment experience. [Mobile Operator Profiles] Updated: Country and Operator Settings Asset (COSA) profiles. [Secure Boot] New! Adds the ability to deploy SKUSiPolicy VBS Anti-rollback protections through the Secure Boot AvailableUpdates registry key. [Core File Systems] Fixed: An issue observed in rare cases after installing the May 2025 security update and subsequent updates causing devices to experience stability issues. Some devices became unresponsive and stopped responding in specific scenarios. [Input] Fixed: A known issue with the Microsoft Changjie Input Method. Users were unable to select words after a recent update. Fixed: A known issue when searching for an emoji in the emoji panel. After a recent update, the search always returns no results. Fixed: An issue in which phonetic input methods, including the Hindi Phonetic Input keyboard and Marathi Phonetic keyboard do not work correctly after a recent update. You can find the official support article here on Microsoft's website.
    • Are there any foldable phones where you can't actually see where the hinge is on the screen? If not, I definitely will never use one until that's possible. That makes the camera cutout look good by comparison.
    • Recall has a completely different purpose and feature-set than Timeline though. It shares some similarities, sure, but Recall isn't an evolved version of Timeline.
    • Yeesh, still a privacy nightmare.
    • That doesn't contradict what I said though. I benchmarked some games some time ago and the actual performance hit came from VBS, not HyperV. With HVCI off, VBS was only knocking off a few FPS on average for me.
  • Recent Achievements

    • Week One Done
      SmileWorks Dental earned a badge
      Week One Done
    • Community Regular
      vZeroG went up a rank
      Community Regular
    • Collaborator
      Snake Doc earned a badge
      Collaborator
    • Week One Done
      Snake Doc earned a badge
      Week One Done
    • One Month Later
      Johnny Mrkvička earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      Michael Scrip
      197
    3. 3
      ATLien_0
      193
    4. 4
      +FloatingFatMan
      131
    5. 5
      Xenon
      122
  • Tell a friend

    Love Neowin? Tell a friend!