This only happens from 3.01 on, not on 3.0. Now tested on 3.02, same thing, when you move from 1 sat to another, SKIPPING a sat, (ex: going from 19 to 28 or even from 19 to 13, skipping 16) you will get a "no signal found on channel" altough it will get proper signal. Need to zap to channel above or below to get signal on the satellite.
Now funny thing is, when you zap to another satellite, and immediatly press the TV button to bing up list, and now wait .... you ll get SIGNAL and PICTURE this time, altough while sometimes pressing lame button you ll still find the "NO SIGNAL error box" beneith it.
Also zapping from 19 to 16, to 13, that works fine ... it seems when a signal is found, no matter what sat it is, the image thinks it has arrived ... which it obvious hasn't.
Very annoying. Besides that, it s just slower on zapping as the 3.0 image. The only drawback from the 3.0 image is that XML epg plugin won't work properly.
Hope this get's fixed... beauty bug : the moving rotor picture is gone now, setting on or off in "show moving dish" doesn t matter.
Cheers
Now funny thing is, when you zap to another satellite, and immediatly press the TV button to bing up list, and now wait .... you ll get SIGNAL and PICTURE this time, altough while sometimes pressing lame button you ll still find the "NO SIGNAL error box" beneith it.
Also zapping from 19 to 16, to 13, that works fine ... it seems when a signal is found, no matter what sat it is, the image thinks it has arrived ... which it obvious hasn't.
Very annoying. Besides that, it s just slower on zapping as the 3.0 image. The only drawback from the 3.0 image is that XML epg plugin won't work properly.
Hope this get's fixed... beauty bug : the moving rotor picture is gone now, setting on or off in "show moving dish" doesn t matter.
Cheers