I’ve been trying to work out why my HDR-FOX T2 has been “running” when I’d expect it to be in Standby. (Where “running” = WebIf diagnostics show fan has been active; unexpected timestamps in Remote Scheduling; timestamps in activity.log; etc). I’ve had Power On/Off timers set to 17:30 and 23:00 respectively (though I appreciate their use appears to be deprecated on this forum).
Anyway, I’ve realised that on my HDR-FOX T2, if a Power Off Timer occurs whilst the unit is in Standby, then the unit boots to (and stays in) Half-Awake state. (Or is that Delinquent Half-Awake state?). Pressing the power button on the remote control turns the unit On, and pressing it again puts the unit into Standby.
Typically, we turn the unit off (via the power button on the remote control) before going to bed. So if we retire before 11pm, then the box “wakes up” at 11pm, and runs all night.
Many thanks to Black Hole for the suggestion to attach an LED light to the front USB port: it makes it very obvious that the box is not actually in Standby (since as he points out here USB power is not present in Standby).
Please forgive this post if this behaviour is common knowledge. (I didn’t really find any references when I searched the forum).
Humax version 1.02.32; Custom firmware version 3.13; Web Interface version 1.5.2-5
Anyway, I’ve realised that on my HDR-FOX T2, if a Power Off Timer occurs whilst the unit is in Standby, then the unit boots to (and stays in) Half-Awake state. (Or is that Delinquent Half-Awake state?). Pressing the power button on the remote control turns the unit On, and pressing it again puts the unit into Standby.
Typically, we turn the unit off (via the power button on the remote control) before going to bed. So if we retire before 11pm, then the box “wakes up” at 11pm, and runs all night.
Many thanks to Black Hole for the suggestion to attach an LED light to the front USB port: it makes it very obvious that the box is not actually in Standby (since as he points out here USB power is not present in Standby).
Please forgive this post if this behaviour is common knowledge. (I didn’t really find any references when I searched the forum).
Humax version 1.02.32; Custom firmware version 3.13; Web Interface version 1.5.2-5