Startup to standby in case of timer wakeup

As getting a transponder time is now arranged in Standby.py
FastScan: try to solve gsod in case last_configuration is invalid
Revert "FastScan: try to solve gsod in case last_configuration is invalid"

This reverts commit 1e1918ff46a0a5ed0b62506b8d45bdab557a699b.

Have to look further into this issue as this is not the solution
Fastscan: Fix GSOD in case last configuration config is invalid

This did happen die to the provider table did recently change and e.g.
the AustriaSat provider was named differently. Aswell in AutoFastScan as
in the normal FastScan this could lead to GSOD.

http://openpli.org/forums/topic/33236-dm8000-wakes-up-from-standby-every-10-minutes/
fix for manual DVB-T scanning for tuner on position 0

Signed-off-by: Littlesat <littlesat99@yahoo.com>
return empty string instead None for non existing channel

Signed-off-by: Littlesat <littlesat99@yahoo.com>
FastScan: Reload fastscan each 24 hours as long box is in standby
Add timeshift protection to zap to previous service with '0'

Thanks Pr2
http://openpli.org/forums/topic/33259-timeshift-press-0-key-stop-it-immediately-without-any-prompt/
Fastscan: Start fastscan after 90 seconds in standby instead of 10 min

This allows somehowe the fastscan will also be performend for users who
put their settop box when into deepstandby as after a timer recording the box should boot instandby. I had to reduce this time to allow to perform the fastscan after the one minute tune to a channel for getting a correct transponder time
and before the tuning to the channel to record really starts.

Of course some timer recordings are required to allow the auto Fastscan to
be perfrormed. However I suggest most of us will use timer recordings.
Merge remote-tracking branch 'OpenPLI/master'