I think this behaviour may be a bit more subtle than simply a timeout value. On my system it's dictated by the exact state of the SB when the server system drops into standby (S3 suspend in my case).
1) If the SB is "off" (which on my device I have set to "blank" screensaver) when the Slimserver drops into standby, then turning the SB on again via the Power button on the remote will behave as per this thread. It cycles through "Waking Slimserver...", "Connecting to Slimserver..." and then reverts to a blank screen, after which you need to retry the Power button to activate. 2) If the SB is "on" (which I have set to a clock screensaver) and I then force the SS system into standby, the SB will drop back to "blank" - re-waking the SB after any period will then go back through Waking / Connecting but now it will re-connnect and return to a "clock" state. So I think that the SB may be simply reverting to its logical state when the system entered standby, rather than failing to connect. This may not be true in all cases, but it would certainly be welcome if re-awakening forced the SB into a logical "on" state rather than requiring the Power button to do this - although I can see that this may be quite tough to achieve. Brgds Phil -- florca ------------------------------------------------------------------------ florca's Profile: http://forums.slimdevices.com/member.php?userid=7486 View this thread: http://forums.slimdevices.com/showthread.php?t=23176 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
