Streamline behavior for recordings coming from deep standby
Remove obsoleted isNextRecordTimerAfterEventActionAuto config

As far I can see this is not required anymore after the previous commit.
I could not find any plugin or so that did still ise it, but it cannot
ensure that if might be required by some plugin.

If so it could be possible we need to revert this commit.
gdi/bcm: Remove static struct

ioctl appears to wait for completion, so no reason to use a static
array here. Put it on the stack, so that multiple calls can be
prepared concurrently.
ecanvas: Prevent using hardware blit/fill

When large enough, the code will use hardware blit or fill routines. This
appears to malfunction, so put it back the way it used to be.
VideoFinetine: cleanup and add full hd testscreen

The full HD testscreen is most likely only in full HD for hardware that
supports full HD skins.
Add testscreen.png in Makefile.am

Sorry I forget this one in my previous commit
Finetunes for recordings from deepstandby

Stop service at first standby when the clock/time is known
Add flag to go only to deepstandby when the first standby was initiated by
coming from deepstandby
VideoFinetune: Toggle with OK through all test screens
Do not increase standby counter when coming from timerwakeup
rcinput: add workaround for VU+ duo2 remote control driver.

This adds the vuduo2 to c50c3502146be124e2e82f47e8c40b59ae51c396.
gdi/bcm: Make instruction sets static again

Just an experiment to see if this solves the weird display problems
on some dreamboxes.
Further improvements for recordings coming from deep standby

Handle Auto and Do Nothing correctly (also for normal standby)
Do not poll for time/date found for services started when in standby just
stop that service before the timer is handled.
Streamline do not increase standby counter

A lot of credits to Dima73 for all comments.
Merge branch 'master' of git://git.code.sf.net/p/openpli/enigma2

Conflicts:
	Navigation.py
	RecordTimer.py
	data/skin_default/Makefile.am