'''Note: The information in this page is not necessarily useful any more, because b-rad has added the advanced standby as an option inside WDLXTV (DEEP_SLEEP) starting with firmware 0.5.1.4. You may want to use that option instead of what is here.'''
 
'''Note: The information in this page is not necessarily useful any more, because b-rad has added the advanced standby as an option inside WDLXTV (DEEP_SLEEP) starting with firmware 0.5.1.4. You may want to use that option instead of what is here.'''
 +
 +
'''Note2: Here are some results when testing this on various firmwares: http://forum.wdlxtv.com/viewtopic.php?f=3&t=7321&p=61607#p61607'''
    
==Power consumption==
 
==Power consumption==
 
In order to fix the issue of non-working apps/OSD/plugins after you recover from Enhanced standby, there is a small tweak you can do to automatically reboot the wdtv when exiting standby. That way, you get low-power usage while in standby and full functionality when exiting standby. The price to pay is waiting about ~1m for the WDTV to boot again. To use this setup, follow these steps:
 
In order to fix the issue of non-working apps/OSD/plugins after you recover from Enhanced standby, there is a small tweak you can do to automatically reboot the wdtv when exiting standby. That way, you get low-power usage while in standby and full functionality when exiting standby. The price to pay is waiting about ~1m for the WDTV to boot again. To use this setup, follow these steps:
 
  config_tool -c POWER_DOWN_ACTION94='logger -t "power_down_action" "Preparing busybox"; cp /bin/busybox /tmp; /tmp/busybox sh /tmp/busybox logger  "Busybox test pid:$$" ; sync'
 
  config_tool -c POWER_DOWN_ACTION94='logger -t "power_down_action" "Preparing busybox"; cp /bin/busybox /tmp; /tmp/busybox sh /tmp/busybox logger  "Busybox test pid:$$" ; sync'
Exception encountered, of type "Error"