[ET8x00] Poor SD image after flashing to 4.1.0.16

[kryton]

Sorry i left it to late to edit my post...
I would like to add that this is not a specific team problem as the same issue occurs with the latest verisons of openPLI.

So surely this is a kernal/driver problem?

Would be nice to see VIX sort this problem is possible as its my prefered OS

 

[birdman]

You could change the A/V option so that the TV does the scaling rather then the box or vice versa.

Can't remember the option at the moment....

...

Automatic resolution (under A/V-settings).

Has anyone with the problem tried this yet? i.e. checked the picture quality when the Vix box is doing the scaling against when the TV is doing it?

 

[Rob van der Does]

I can confirm I have already tried this, I can also confirm what judge said....as the receiver wouldn't even boot after putting the drivers from 4.1 onto 4.2 it just got stuck with et8000 on the front lcd , but thankyou for your input. it's driving me nuts now, i've spent more time flashing...adjusting...tweaking than even watching tv.

@Rob
Ive exhausted all your suggestions tonight,i cant see a EDID setting in AV, I've tried every possible video setting on the box and tv including "digital clean view" and "MPEG noise filter" in my samsungs picture menu.
I've rebooted the Xtrend and power cycled my tv between each setting change, I've powered the tv on first then the box and vice versa...
I've tried the scart socket....and even streaming to my tablet and mobile phone the vertical lines persist.

the only way to fix it is to alter the block noise reduction setting in the video enhancer plugin or run the script that I have (which does the same thing).
I'd be more than happy if I could find a way to execute the script when waking the receiver from standby or even being able to assign it to a hotkey on the remote so you didn't have to keep going through the menu's to run it.

the vertical lines show mainly on people's faces, heavy thick lines through the nose, jagged images on cartoons ,at times it's like your looking through a frosted window.

Drivers are build against a specific kernel. So drivers can only be swapped in images that use the same kernel

OK, I'm now completely out of ideas.

Only one thing: it should be possible to run a sript via a cron job. But not my area of expertise.

 

[kryton]

...
Has anyone with the problem tried this yet? i.e. checked the picture quality when the Vix box is doing the scaling against when the TV is doing it?

Sure have m8. Tried every video combination going...

@Rob
Ive already tried cron timer to m8.
Although it does work it doesnt have the desired effect..
The cron timer only works in minutes / hours
So if you set the timer to run for example 10 minutes the script is executed every 10 minutes passed the hour and not every 10 minutes....if that makes sense.
So when coming out of standby sometimes you have to wait for the timer to run the script..sometimes this could be a 40 or 50 minute wait before it works.
Ive searched and found a way to execute the script every so many minutes by using */5 * * * *
This is supposed to make the cron run the script every 5 minutes
But the cron manager doesnt seem to like this setting on enigma2 and doesnt work.

 

[ccs]

... maybe cron using 0,5,10,15,20,25,30,35,40,45,50,55 * * * * will work?

 

[kryton]

... maybe cron using 0,5,10,15,20,25,30,35,40,45,50,55 * * * * will work?

Quite possibly, Ill try it.
Cheers mate.

 

[twol]

@kryton sent you a pm

 

[kryton]

... maybe cron using 0,5,10,15,20,25,30,35,40,45,50,55 * * * * will work?

Same result m8.
Seems cron will only run every hour.

But thanks m8.

 

[birdman]

Seems cron will only run every hour.

Cron works for me with that syntax:

root@mbtwin:~# crontab -l
# Min Hr DoM Mth DoW Command....
0,5,10,15,20,25,30,35,40,45,50,55 * * * * date >> /home/root/cron-v1.log
*/5 * * * * date >> /home/root/cron-v2.log

root@mbtwin:~# cat cron-v1.log
Sat Oct 22 14:15:00 BST 2016
Sat Oct 22 14:20:00 BST 2016
root@mbtwin:~# cat cron-v2.log
Sat Oct 22 14:15:00 BST 2016
Sat Oct 22 14:20:00 BST 2016

 

[kryton]

Cron works for me with that syntax:

It was just a quick try before leaving for work, i must of done something wrong.
If i run root@mbtwin:~# contrab -l
Will this show me the log for ths script being executed?

And am i right that the syntax goes in the root file in the etc/cron /crontab folder?

 

[birdman]

If i run root@mbtwin:~# contrab -l
Will this show me the log for ths script being executed?

No - it will show the crontab entries that you have in place.
If you run "crontab" (no options) it will list it's options.

And am i right that the syntax goes in the root file in the etc/cron /crontab folder?

Pass. I just created a file of commands to run and ran "crontab filename". It knows where to put them so I don't need to know (and I've now remove it all so can't find out).
Wherever it is you can't just edit the in-place file to change things - you need to run the crontab command so that the cron daemon process gets notified to re-read the config files.

 

[kryton]

No - it will show the crontab entries that you have in place.
If you run "crontab" (no options) it will list it's options.

Pass. I just created a file of commands to run and ran "crontab filename". It knows where to put them so I don't need to know (and I've now remove it all so can't find out).
Wherever it is you can't just edit the in-place file to change things - you need to run the crontab command so that the cron daemon process gets notified to re-read the config files.

Ill give it another try later.
The cron shows in the cron timer menu on the box but doesnt appear to be executing when using */5 * * * * or 0,10,15 etc.

Maybe something im doing wrong, is there a way to see if the script has been executed every 5 minutes?

 

[birdman]

Ill give it another try later.
The cron shows in the cron timer menu on the box but doesnt appear to be executing when using */5 * * * * or 0,10,15 etc.

The Vix menu options only allow you to enter hourly/weekly/monthly entries. And it only really expects to see such entries when displaying them (so the above lines show up as H: .... i.e. marked as an hourly run).

You'll have to add this from the command line.

 

[kryton]

ok ive finally got cron to run the script every 5 minutes

Oct 23 00:15:37 et8000 cron.info crond[1619]: crond (busybox 1.24.1) started, log level 8
Oct 23 00:20:00 et8000 cron.info crond[1619]: USER root pid 1831 cmd /usr/script/line.sh
Oct 23 00:25:00 et8000 cron.info crond[1619]: USER root pid 2025 cmd /usr/script/line.sh
Oct 23 00:30:00 et8000 cron.info crond[1619]: USER root pid 2265 cmd /usr/script/line.sh
Oct 23 00:35:00 et8000 cron.info crond[1619]: USER root pid 2507 cmd /usr/script/line.sh
Oct 23 00:40:00 et8000 cron.info crond[1619]: USER root pid 2731 cmd /usr/script/line.sh
Oct 23 00:45:00 et8000 cron.info crond[1619]: USER root pid 2979 cmd /usr/script/line.sh
Oct 23 00:50:00 et8000 cron.info crond[1619]: USER root pid 3229 cmd /usr/script/line.sh

This may seem a bit of a long winded work around but it does work and now im happily running 4.2 build 009 with no more bloody lines lol.
I would like to see a more permanent fix by Xtrend as this is obviously a kernel or driver problem.

but would like to thank aido for making the script in the first place and also Twol, Rob, Birdman, Andy and all the guys that have given suggestions on this problem.

much appreciated guys.

 

[kryton]

Wherever it is you can't just edit the in-place file to change things - you need to run the crontab command so that the cron daemon process gets notified to re-read the config files.

Just for your own information mate the cron command to run the script is located in /etc/cron/crontabs/root
You can modify the "root" file with notepad, put it back in the contrabs folder and restart enigma2.

 

[birdman]

You can modify the "root" file with notepad, put it back in the contrabs folder and restart enigma2.

To use notepad, which writes DOS text files, you'd have to remember to use ASCII FTP transfers out and in.
And you'd still need a way to kick the crond to re-read the file (or wait until a reboot).