jowjow wrote:
… Otherwise the software should not initialise the outputs etc. i.e. hdmi, optical out, usb etc. and sit in a low power state, similar to what it does when you turn it off via the remote after it turns itself fully on.
The infra red commands should trigger an interrupt which would wake the device, like the way it does currently if you have turned it off and then turn it on again using the remote.> * * *
But that’s not how these things were built. You’re describing the way they SHOULD work. I don’t disagree that’s the way it SHOULD work, but it’s not how it DOES work, and I believe it’s not possible to do it any other way because of the way the HARDWARE was designed.
In the “Standby” state for the WDTV Live +, the WDTV Live (Rev. 2) and WDTV HD Gen 2 (Rev. 2) the CPU and MEMORY are powered OFF. There is NO “Standby” state the way you describe it. The CPU is DEAD. The RAM is DEAD. There *IS NO SOFTWARE* running. No way to process interrupts. It’s GONE, a dead rock. The only thing powered up are voltage regulators and the MCU that controls the Infrared Receiver, and the receiver itself. The Infrared Receiver tells the MCU to activate the rest of the system and power up the rest of the guts. This hardware aspect was described some time ago by WD tech folks here in the forum. This is a known fact; not a guess.
That’s why it takes so much longer for the Live+, Rev 2 Gen2 WDTV, and Rev 2 WDTV Live to boot. They have to start from the ground up and bootstrap every time the power is turned on by the remote, even if the power PLUG has been there forever.
So, while what you describe *might* be possible, it’d only be possible for products that haven’t been manufactured for the last 7 or 8 months.
I’d be happy for WD to chime in and tell me I’m wrong ! :)
So, let’s say that they go ahead and write software the just keeps the output from being activated until the user hits the remote power button, which I agree is possible. Here’s what that would cause.
1- User plugs in the power.
2- There is NOTHING on the screen, and no LED indication. (but, unbeknownst to the user, the device is actually booting up.)
3- The user presses the power button the remote.
4- NOTHING happens. Still no picture, and LED is still dark.
5- User presses again.
6- Nothing happens. (But the device just hasn’t finished it’s 60-or-so second initialization.)
7- User unplugs the unit and plugs it back in.
8- Go to Step 2.
… followed by lots of posts here on the forum saying “My WDTV Live+ won’t turn on!”
and lots of answers:
“You have to wait at least 60 seconds after power-up before you can turn it on.”
followed by, “THAT is STUPID. I returned my box to the store thinking it was DEAD, and this is the third one I tried! Why don’t they at least put something on the screen and turn the LED on???”
Not only that, but since the REMOTE controls the same RESET-LINE as the Power-Plug does, this would happen, too: “I pressed the remote power button but it won’t turn on!” When, in actuallity, it IS on, but you just can’t tell until the box has initialized (because there is no STANDBY state.)
I would guess that the latter scenarios would outnumber the dozen or so people who want this other feature by a 100 to 1 margin…