266 replies to this topic

[datrkmer]

Hello, will this skin be available on zgemma h3?

sorry for english >> google translator

[mrvica]

IMPORTANT NOTE: As stated above, GAFHD is designed to work well ONLY for receivers with a CPU higher than 750Mhz. This is an obligatory limitation due to the high resolution graphical nature of the skin which also makes the package large in size. For receivers with slower CPUs use at your own risk! Also,

[cobus]

When will this skin be available?

[Frenske]

In Develop it already is. I can’t tell whether it will be possible to add it in the present Release too.

There are others that can give more detailed information regarding adding this skin in Release 7.2.

[WanWizard]

It is already added to the release, so it will be available after the next build.

[MCelliotG]

Thank you! I already uploaded the other skins privately on my Github, testing the install scripts atm for file clashes.

[cobus]

The skin is great but it doesnt work great on the Vu uno 4k lag on channel change on the Multibox he works great super fast when channel change

[MCelliotG]

That's quite strange, there was no lag on channel change even on an "old" VuDuo2 I had tested it on! Maybe something else hinders the zap, or you use an older version of my skin?

Edited by MCelliotG, 7 January 2020 - 01:58.

[Pr2]

I test the skin on Duo4K and Solo4K and I had no problem.

The problem you have on your Uno4K is perhaps linked with a 3rd party plugin that you install.

Edited by Pr2, 8 January 2020 - 08:05.

[Frenske]

I tested this skin earlier and just now again. There is definitely a delay when switching channels. I tested on my Ultimo4k where, besides some default plugins no strange plugins are used. Only autotimer, het weer, youtube and lcd4linux. A picture tells more then 1000 words.

 

https://wetransfer.com/downloads/95ae5a680c695e59d67069e076170fef20200108083332/16d34922c3cc5a0f3ab49656f91d081820200108083332/8c798e

[cobus]

I test the skin on Duo4K and Solo4K and I had no problem.

The problem you have on your Uno4K is perhaps linked with a 3rd party plugin that you install.

No i have almost the same plugins as Frenske  Only autotimer, youtube and lcd4linux

[Pr2]

lcd4linux is probably the culprit it was already identified as a source of problem during zap on VU+ 4K boxes.

[Frenske]

You could be right but I won’t remove lcd4linux in my Ultimo4k. I always advice not to use lcd4linux on an Uno4Kse. 
Besides that, tastes are different so I personally will not use this skin although I appreciate the time McelliotG must have put in creating this skin.

If it’s necessary to remove Lcd4linux for testing purposes I will not hesitate to test this. 

[Pr2]

LCD4linux also cause troubles on the Duo4K.

[WanWizard]

Yup.

[Frenske]

I’ll test a random other box later this evening with this skin.

[Frenske]

I just installed the skin remotely and will test it as soon as I’m available. 

Attached Files

•  5533FAE5-1F8B-4D54-9BEE-9B0B52D275E2.jpeg   129.59KB   10 downloads

[MCelliotG]

Guys, thank you for testing my skin.

I'm currently testing the colored skins now, and I have encountered a little problem with the ipk standalone installers I make.

The skins use the same Converters/Renderers (as they should). Since the ipks should be working as standalone installers, file clashes are inevitable, when one skin tries to install when another is already installed.

 

On OpenATV I solved this problem easily with the Replaces flag in the control file. This will overwrite and replace only the common files, so if the user wants a second Glamour skin, everything should be fine. Additionally, I wrote a postrm skin that will prevent removing the Converters/Renderers if another Glamour skin is still in use.

 

On OpenPLI however the Replaces flag does not work as I expected. The new skin will completely uninstall the other first. As a dirty workaround I wrote an additional postinst script that initially copies the converters to /tmp and then overwrites the installed ones, but I don't like this way.

 

Should I leave it this way, or this will cause troubles in building from Github or even updating from it?

 

Why the Replaces flag in the control file works differently between OpenPLI and OpenATV?

Edited by MCelliotG, 8 January 2020 - 22:06.

[WanWizard]

The Replaces flag works on package level, so if you define that A.ipk replaces B.ipk, and B is installed, B will be removed when A is installed.

 

If ATV does something different, they either hacked something custom in, or they manually constructed the ipk outside of the normal bitbake build process, so files are not marked as "under version control", and included a postrm script to manually remove the files (or worse, don't remove them at all) when you remove the skin package. The fact that you talk about manually adding stuff to the control file hints at the second option.

 

Both however are equally bad and should be avoided at all costs.

 

The proper way to deal with this is to create two packages: the different skin packages, and a skin-common package that contains the shared files, and then define a dependency between the two, so that if you install a skin, the common package is installed too. And the common package will be automatically removed if you remove the last skin that depends on it.

[MCelliotG]

Thank you I was thinking the same thing!

Στάλθηκε από το Redmi Note 5 μου χρησιμοποιώντας Tapatalk