I am an average user and have slogged through some of the pages of the lengthy threads on the _V update and its problems. But I confess it’s tough for me to figure out what the current status is.
My WDTVLIVEPLUS, when accessing the device update through its menu and internet connection, tells me that there is no update, that my player has the most current firmware. I have the _B firmware. Did WD take down the _V via this update method?
With regard to the Video Resolution, I am one of those who cannot get anything other than 720P for my 1080P Panasonic Plasma HDMI to HDMI connection (auto, manual, doesn’t matter). I am reluctant to start fooling around with my TV’s firmware. Is this still an unresolved issue? I read in one thread that there was a fix of somekind depending on how the HDMI cable was plugged in to the TV (power status of TV or Player at time of HDMI connection, can’t remember the details). Unless this fix a) actually works and b) will survive a power outage, it’s not practical for me as the TV is hung on a hangar in a built in, and accessing its connections in the back is a three man job — two to lift the TV off its hangar and move away from the backer board, and one to fool around with cables.
Is there going to be a fix for the resolution problem at some point?
Tony, thanks. I’ll get the data using the freeware. But here’s another question. In your example, you found that your new TV was telling the player that the native resolution was 720p (which is clearly revealed in the screenshot you provided) and that was wrong.
But does the freeware — or any other procedure — allow you to change which resolution is designated as “native” on the TV?
Exactly. If that tool allowed me to edit the EDID data, I’d probably get myself into a lot of trouble!!!
I have a Tech Support request in to LG… When I was still learning my TV and sent them questions, they typically responded within 12-24 hours with an answer. It’s been about a week since I sent them this one… I can only hope that means it’s being escalated. I am surprised that if this is an oversight that it hasn’t been corrected. I can’t be the first one to have reported it, but we’ll see.
