Xtrend Tuner Issues not resolved on build 5.0.005

[satnut2]

Hi Guys

Up until a week ago I have been running on build 4.1.015 , I have kept on this build due to recording problems which I posted on the following thread a while back

http://www.world-of-satellite.com/sh...-build-4-2-005

I have been running on build 5.0.005 for a week , I thought the tuner problems of build 4.1.015 had been resolved but after further testing they are still present , all as explained in the link above

Could a '5.0.005' V2 build please be released for Xtrend owners with tuner drivers from build 4.1.015 , when I flash back to 4.1.015 all problems gone

I'm not really sure what I'm doing Ftp drivers from old builds to new builds to work around the problem

Any other Xrend owners had issues ? , I'm running with 4 tuners in my box

Any help appreciated

[twol]

There has been for some time a ET8000/ET10000 driver update coming which may fix this issue, but its in test elsewhere and probably brings Kodi with it ...... so the issue is not forgotten and in fact a lot of work has been done by ViX members to do what you suggest but .... if this driver update works then it will not be needed

[satnut2]

Thanks for the info twol , I'm not sure whats involved but I take it its not an easy thing to do for the vix team to remove the tuner drivers from build 5.0.005 and replace them with the drivers from 4.1.015 ?

Looks like I'm going to have to go back to build 4.1.015 tonight , although cant stay on this build forever...hope this problem is resolved soon

[twol]

All that was resolved but then ViX were told there was a driver change in test ..... and everybody waits for that.

[potterson]

I too have the same problem. Bought a xtrend et8500 couple of weeks ago with 4 tuners, one DVD-t2 and three Dvb-s2.currelntly on 5.0.009(Release).

[twol]

I too have the same problem. Bought a xtrend et8500 couple of weeks ago with 4 tuners, one DVD-t2 and three Dvb-s2.currelntly on 5.0.009(Release).

Then you need to raise your own thread because this has never been reported before .. and I haven't seen it on my ET8500 (3 tuners) .. which doesn,t mean you haven't an issue but it needs documenting exactly.
E.g. Config, what releases have you tested it with ...what symptoms
ET8000/10000 drivers are not the same as the ET8500 drivers.

[JonMMM]

Then you need to raise your own thread because this has never been reported before .. and I haven't seen it on my ET8500 (3 tuners) .. which doesn,t mean you haven't an issue but it needs documenting exactly.
E.g. Config, what releases have you tested it with ...what symptoms
ET8000/10000 drivers are not the same as the ET8500 drivers.

I think you are the one who needs his own thread, the OP posted in the ET8500 discussion section, which is where this thread is located, so I would have to think that he was discussing a ET8500

[ccs]

Then you need to raise your own thread because this has never been reported before .. and I haven't seen it on my ET8500 (3 tuners) .. which doesn,t mean you haven't an issue but it needs documenting exactly.
E.g. Config, what releases have you tested it with ...what symptoms
ET8000/10000 drivers are not the same as the ET8500 drivers.

... but this is a thread about ET8500's.

There has been for some time a ET8000/ET10000 driver update coming which may fix this issue, but its in test elsewhere and probably brings Kodi with it ...... so the issue is not forgotten and in fact a lot of work has been done by ViX members to do what you suggest but .... if this driver update works then it will not be needed

[twol]

Yep, I am totally wrong I was thinking of a different issue.... apologies.

[twol]

So having re-read everything ...and then checked the OE-A changes ..... build 5.0.005 missed the last ET8500 drivers changes ..... which included some tuner changes .... so it would be worth trying the latest build to see if that makes a difference.

[ccs]

Best read from end to beginning .....

openvix: release 5.0.007
openbh: release 1.0.000.036
commit correct file name
fix default skin name
openvix: developer 5.0.007.002
fix enigma2-plugin-skins-mxtitanium
[sf4008] update driver -. dB Value corecture
openbh: release 1.0.000.035
remove mxhq9w skin / add mxtitaniumc skin
openvix: developer 5.0.007.001
[et8500] fix driver sum
Merge pull request #184 from kueken/patch-2
Merge pull request #183 from kueken/patch-1
Update and rename ffmpeg_3.2.2.bb to ffmpeg_3.2.4.bb
Update bitbake und Version Exteplayer3
openvix: release 5.0.006
Merge branch '4.0' of github.come-alliance/oe-alliance-core into 4.0
[dags] 7252 update drivers, optimise tuner zapping speed and add dvb-c support
openvix: developer 5.0.006.001
[zgemma] h3 fix tuner detection new dual
Merge branch '4.0' of github.come-alliance/oe-alliance-core into 4.0
[g300] update driver -. Fixed the displaying on the SNR % issue -. Fixed grep issue -. Fixed minor bugs on Tuner
openbh: release 1.0.000.034
Enable wvdial and wvstreams build, works fine
Enable wvdial
[xcore] update 4kmini drivers minor fixes
Merge branch '4.0' of github.come-alliance/oe-alliance-core into 4.0
[xtrend] et7x00 and et8500 update drivers -. Fixed the displaying on the SNR % issue -. Fixed grep issue -. Fixed minor bugs on Tuner
openvix: release 5.0.005

[satnut2]

Best read from end to beginning .....

openvix: release 5.0.007
openbh: release 1.0.000.036
commit correct file name
fix default skin name
openvix: developer 5.0.007.002
fix enigma2-plugin-skins-mxtitanium
[sf4008] update driver -. dB Value corecture
openbh: release 1.0.000.035
remove mxhq9w skin / add mxtitaniumc skin
openvix: developer 5.0.007.001
[et8500] fix driver sum
Merge pull request #184 from kueken/patch-2
Merge pull request #183 from kueken/patch-1
Update and rename ffmpeg_3.2.2.bb to ffmpeg_3.2.4.bb
Update bitbake und Version Exteplayer3
openvix: release 5.0.006
Merge branch '4.0' of github.come-alliance/oe-alliance-core into 4.0
[dags] 7252 update drivers, optimise tuner zapping speed and add dvb-c support
openvix: developer 5.0.006.001
[zgemma] h3 fix tuner detection new dual
Merge branch '4.0' of github.come-alliance/oe-alliance-core into 4.0
[g300] update driver -. Fixed the displaying on the SNR % issue -. Fixed grep issue -. Fixed minor bugs on Tuner
openbh: release 1.0.000.034
Enable wvdial and wvstreams build, works fine
Enable wvdial
[xcore] update 4kmini drivers minor fixes
Merge branch '4.0' of github.come-alliance/oe-alliance-core into 4.0
[xtrend] et7x00 and et8500 update drivers -. Fixed the displaying on the SNR % issue -. Fixed grep issue -. Fixed minor bugs on Tuner
openvix: release 5.0.005

Guys , Ive just checked my build and I'm actually running on 5.0.008 and the recording problem remains , I remember updating this quickly after I changed to 5.0.005 which had known lag issues when changing channels. Build 5.0.008 tunes the channels faster than 5.0.005 but both builds have recording issues where the picture pixelates as explained in my link above

The recording problem remains on build 5.0.005 and 5.008 and possibly all builds after 4.1.015

To confirm I am using an Xtrend ET8500

Noticed that build 5.0.011 is now available , which I may try , where can I find the release notes ?

[twol]

Yep it missed 5, but the driver sums were also incorrect so the drivers changes were not incorporated until OpenVix 5.0.007

[ccs]

Changelogs.... http://www.world-of-satellite.com/sh...l=1#post441787

[satnut2]

hi guys , well Ive now updated to latest build 5 .0.020 and the tuner problem described at the start of my thread still remains

Will Xtrend EVER fix this issue with the drivers ? everything went wrong after build 4.1.015

Looks like I'm stuck using build 4.1.015 forever , unless someone can release a one off 5.0.020 build for me with drivers from 4.1.015??

Frustrated I cant take advantage of improvements with latest builds due to a simple problem when recording multiple channels forcing me to stick with 4.1.015

Seriously considering selling the Xtrend and going back to VU

Any comments apprreciated