Some Tuner settings not remembered on 5.4.008

[bbbuk]

So I took out the changes(and replaced the .py on my Giga4K FBC) and at 1st glance it all seems to be OK.
https://github.com/OpenViX/enigma2/c...e9053cf29dbb1f
...

Thanks for confirming.

Ok, so I also used the commit immediately before the "[Satconfig] setup tuners FBCLink remove all 1.2 diseqc mode (#2857)" commit and so far okay.

For anyone wanting the commit immediately before this one then back-up existing files by renaming to something like .old instead of .pyo and extract files in attached rar to where these two files go...

/usr/lib/enigma2/python/Components/NimManager.py
/usr/lib/enigma2/python/Screens/Satconfig.py

FBCCommit_Reverted.rar

[JonMMM]

Will the fix go into a new update?

[ccs]

Will the fix go into a new update?

I've reported it on PLi as it is their commit causing the problem.

There's a pull request open to fix it on PLi.

[bbbuk]

There's a pull request open to fix it on PLi.

I've just tested their fix for it and in my tests it did indeed now read the defaults. However, a further issue I noticed was if I changed anything in one of those tuners (ie the scr channel) and did a reboot it defaulted back to 19.2 for that specific tuner.

PLi fix can be found here.

[Huevos]

Please test the new commits in ViX dev.

[twol]

I ran a build this morning and installed new image on my GBUE4K with FBC tuners, this has 28.2E on input A (so A, C,D,E) and 19.2E on input B (B,F,G,H) as well as 27.5W on tuners I/J (DVB-S2X).
Ran reboots, Gui restarts, drop into Standby and out - all looks OK.

[bbbuk]

I ran a build this morning and installed new image on my GBUE4K with FBC tuners, this has 28.2E on input A (so A, C,D,E) and 19.2E on input B (B,F,G,H) as well as 27.5W on tuners I/J (DVB-S2X).
Ran reboots, Gui restarts, drop into Standby and out - all looks OK.

Yes, the Pli commit, in my testing did remember the settings. However, once a settings was changed for a non-root Tuner (ie scr channel) then after reboot, it didnt save the settings correctly and instead resulted in just that tuner that had been changed defaulting back to 19.2

UPDATE: My bad, I see that a further commit has been done to force save it on vix only build, not Pli.

[JonMMM]

will this go to a general update?

[Huevos]

will this go to a general update?

Is that a serious question?

[JonMMM]

Is that a serious question?

Yes, I assume it will as its a good fix, but will it wait for a while for more upgrades?

[Huevos]

Unless something new is reported there won't be an upgrade, so it will filter down to the release image when that is next built.

[bbbuk]

I've just built this to try this fix out and noticed the plugin feeds for Vu Duo 4K SE havent been updated since January, whereas all the other plugin feeds were updated as recent as yesterday.

I know I can rebuild and make reference to local plugin feeds on my setup but would much prefer to use Vix's Dev plugin feeds if that was possible?

[Huevos]

I removed that machine from the build in January as none of the team members claimed it.

[bbbuk]

I removed that machine from the build in January as none of the team members claimed it.

Fair enough. I'll have to change things to use local feeds or just be patient and wait until next general release

[bbbuk]

Please test the new commits in ViX dev.

Confirm the new commits now does work as expected within current developer build