Find tech advice for business here
Samsung: HDMI Problems on LN46A650
HDMI Problems on LN46A650
by DC5466 - 7/31/08 7:07 PMI purchased a LN46A650 in late June and hooked it up to a new Scientific Atlanta RNG200 box from Comcast via HDMI at HDMI 1. The Comcast box is outputting at 1080i.
I also connected a Sony DAV-HDX275 DVD Changer/Audio systems through an HDMI cable (at HDMI 2) and ran the digital audio out from the TV to the Sony.
For 3+ weeks it worked perfectly.
Last week I added a Wii through component video 1 (not sure if this is related). Several days later, when switching back to HDMI 1 for TV (and when the Comcast RNG200 box was still outputting at 1080i), I began getting a "Mode Not Supported" message from the TV. There are no problems with the DVD player though.
I've updated the firmware on the TV and trawled the internet but didn't really see any answers that worked for me (I've tried resetting, changing cables out, etc.). While I can work around this issue by running the cable box to the TV via component video/audio, I'd like to get the HDMI working again.
Any thoughts would be much appreciated!
Thanks!
HDMI
by ice82 - 8/8/08 10:29 AM In reply to: HDMI Problems on LN46A650 by DC5466There are still some handshake issues with HDMI.
Your better bet is to go with the component cables, but if you insist on HDMI, then I suggest you search for the tv receiver's compatibility with the Samsung.
Thanks and Update
by DC5466 - 8/8/08 11:03 AM In reply to: HDMI by ice82Thanks for the advice. I did some digging on the internet and found a post elsewhere (I believe Mr. Samsung was part of the chain) where someone replaced the box. Comcast gave me a new box and it works fine now.
Oddly, the old box worked on HDMI 4, but not on HDMI 1-3, when we tested it before swapping out.
Now hopefully it doesn't happen again (I was wondering if using the Wii had done something).
What is going to take to resolve the HDMI handshake issues?
by Georgia in MS - 8/8/08 11:06 AM In reply to: HDMI by ice82I have a 550 and had trouble with HDMI port 1. Unfortunately, the Samsung authorized service people were going to take 2 weeks or so to replace the port or whatever needed to be done. I had only had the TV for 2 weeks, so Amazon sent me a replacement, which I had in 3 days.
Are we all jumping the gun going for the HDMI? Is that why they keep increasing the number of ports, so if one fails, another is available (asked tongue-in-cheek)?
Handshake Issues
by DC5466 - 8/9/08 8:01 AM In reply to: What is going to take to resolve the HDMI handshake issues? by Georgia in MSIn your case I wonder if it is the handshake or something else? In my case as soon as we swapped the box, everything worked again. Did you try multiple HDMI input sources on port 1 to confirm it wasn't that one combination / try a different cable? (I'll assume yes, but have to ask). Also, did you flash your firmware with the newest TV firmware?
So many technology repairs - be it the electronics or cable, Fios or other fix - jump to "lets replace the component." I often wonder if it is just a software fix (for example, by doing a full reconfiguration of a cable box).
Port 1
by Georgia in MS - 8/9/08 8:11 AM In reply to: Handshake Issues by DC5466On my 550, the port seemed to be bad with a reddish tint to the picture for about 20 seconds and then to a solid red screen.
I first thought it was the cable box. Cable One walked me thru all various checks without resolution. I tried three different HDMI cables (two different manufacturers) and no resolution. I totally unplugged everything to let all reset; no resolution. I decided to try using Ports 2 and 3 for the cable box connection. Ports 2 and 3 were perfect. Went back to Port 1, and the reddish picture for 20 seconds and solid red screen returned.
I mainly asked the handshake question because I keep reading the phrase of "HDMI handshake" throughout comments about HDMI problems in various forums.
Handshake
by DC5466 - 8/9/08 8:43 AM In reply to: Port 1 by Georgia in MSI get it completely. I thought they had worked out a lot of the HDMI handshake issues at this point. I guess its part of the problem with shifting to an interoperable standard that allows devices to truly "communicate."
| Forum legend: | |
 |
Locked thread |
 |
Moderator |
 |
CNET staff |
 |
Samsung staff |
 |
Norton Authorized Support team |
 |
AVG staff |
 |
Windows Outreach team |
 |
Dell staff |
 |
Intel staff |
