Pr2

I totally agree you should move forward, people are still use old no longer maintained plugins or skins. I read so many times that you cannot develop a proper solution because it will break plugin or some skins.
Switching to Python 3 is the good time to get rid of all of this old stuff.
Plugin developers or skin creators should also be ready to adapt there code, otherwise you cannot go forward.

SD card is mounted as /media/mcc/  so you need to define this path for recording.

If you read what is explained before there was a server failure and we are unable to restore the versionning of the package like it was before the crash, so what kind of miracle do you expect to fix it?

We warn the users that they need to flash (like we do when changing of major release) if you want to perform an online upgrade give a try (you probaly have to run it several times) but then don't blame us if it is not working as expected or if you cannot upgrade some packages.

Are those files played from a location where your box has read write access?

 

Copy the file into the /media/hdd/movie/ and play it from there and check it the resume point is working.

I have other boxes Hisilicon boxes connected with HDMI-CEC on and it is working, so you cannot say that HDMI-CEC is not working on all HiSilicon boxes.

It is working on both Panasonic and Sony.

 

 

in a nutshell , i want the same proportion on lcd in stand by and working mode like those use on Duo 4K SE .Ultimo 4k screen is larger and clock is too small in stand by mode. Also rec icon should be larger and picon. I watch tv from 3,5 meter and vu screen is harder to read.

The Friends of PLi should have all the decoders to fix everything, but it is not possible. Decoders that have a display like our vu + unfortunately need help from those who own it. For example, I have a 4K one if I worked on the .xml file to optimize everything. In your case you should do this job and turn them the optimized file like I did, in fact it was put in the reposity as good.

Il mio telefono!

 

You have absolutely right but why coders abandoned support for Lcd4llinux plugin ? On Duo 2 work great and now customer must show initiative pretending work of coders.Maybe time to create site or forum for tv sat hobbysts

 

 

OpenPLi is fully done by sat hobbyists!

 

I own a Duo 4K and Solo 4K and I am happy with the current LCD display.

 

Here is the thread where krimesis adapt the LCD display for OpenPLi:

 

https://forums.openp...4kse-lcd/page-3

why are you starting form the lamedb?

 

If you create favorites (aka bouquets) with the channels that you are watching, you will have immediately the right service reference in it.

So you will ease your life if you work from the userbouquet files than from the lamedb. 

i just perform a fresh flash without any restore and the values for dropbear are:
 

root@vuduo4k:~# cat /etc/default/dropbear
# Disallow root logins by default
DROPBEAR_EXTRA_ARGS=""
DROPBEAR_RSAKEY_ARGS="-t ecdsa -s 521"

So this is indeed working.

Duo 4K se has modular tuner may be you can purchase a non FBC VU+ tuner that support blindscan and plug it in (but check its compatibility first).

You can also have a look at external DVB-S2 USB tuner but then you should ensure that they are blindscan capable and that they are compatible with the Duo 4K se kernel version.

 

We should never assume anything when purchasing a STB, I have a VU+ Solo4K it has 2 cardreaders and 1 CI slot, I purchase later on the Duo 4K and was surprised to see that it has only one card reader. :-( (but 2 CI slots).

I purchase also other brand STB assuming that every dual tuners boxes are capable to perform Picture-In-Picture and stream but they are not.

 

Choosing the right STB is not an easy think, it is hard to find one that will fulfill all the requirements.

Vu+ is not supporting true MultiBoot nothing we can do about it. If you need to use MultiBoot you should have purchased a box that natively support it.
OpenMultiboot is just changing the mount point to allow to try other images but this can result in conflict between OE-Alliance images and OpenPli and this is what you experience here. Some image goes change some stuff in the common mounted part.
You cannot conclude anything about any image when using it with OpenMultiboot since you don't run the true full image.
I totally stop using OpenMultiboot due to all those problems.
If I want to test different image I flash them normally in the VU+ or I use the MultiBoot of the Gigablue Trio 4K.
So if you are unhappy with OpenPli feel free to use any other image that better fits your needs. That's the main advantage of our boxes.

Very good thing OpenMultiboot is not a true MultiBoot it just fake the folders so some image can corrupt the other one by writing into the common folders. Don't use it!

We don't know which box you have, what is your setup. Which provider you are watching, do you use a smartcard which softcam or do you use a pcmcia module.

I'd like to have LCD display on the STBs and that's why I am using VU+ Solo 4K and Vu+ Duo 4K for my daily usage.

To be really honest without you, I prefer the default LCD skin which already give me all the informations that I want and I'd like the current proportion.

So I could not find any benefits with your modified LCD skin.

Sorry it is a typo of course the file is:  channel_id_filter.conf

Hello,

 

I propose a new PR with the channel id filtering. I better describe the constraints that lead to implement this solution, it is slightly improved compared to the first version to avoid some confusing entries in log.

 

https://github.com/O...gimport/pull/53

 

This doesn't prevent to work on implementing the standard DVB language support into EPGImport so please view it as a Quick Win solution both solutions can live together.

 

End-users doesn't have to learn regex a simple cut and paste of the channel id will do the job (risk of false positive is really low and the log is clearly displaying the filtered "channel id" so debugging is easy). Moreover the content of this file for standard endusers will be explained by Doglover to easily fix there problem. Advanced users that test the solution already found benefits out of it. People can easily turn on/off one particular filter in the file since comments are allowed (line starting with a # are ignored).

The option to enable it or not on the custom.channels.xml is a specific request from Doglover.

 

I hope that it will be accepted because Doglover (Willy) is really waiting for it.

 

Regards,

 

Pr2