Often spiner appears

[xrobertas]

Hello,
I'm using VU Solo 4k. Since that time as I have installed BH 3.0.6 I can see quite often a spiner on the screen. If I see a spiner, VU does not respond to the remote control. I thought that when I go through BH 3.0.7, it's going to change, but the spiner is still just as often. With BH 3.0.5 I spiner saw only when VU was booting. Where could be the problem?

Excuse my English.

 

[Matrix10]

Hello,
I'm using VU Solo 4k. Since that time as I have installed BH 3.0.6 I can see quite often a spiner on the screen. If I see a spiner, VU does not respond to the remote control. I thought that when I go through BH 3.0.7, it's going to change, but the spiner is still just as often. With BH 3.0.5 I spiner saw only when VU was booting. Where could be the problem?

Excuse my English.

You installed a clean image and you see a spinner ???
I'm sorry but I do not believe that.
You're adding something that causes a spinner.

There must be some reason and you can find out if you go step by step.
So you should know at what moment the spinner appeared.
And if you do not know.
Install again clean image without anything .
Only put SAT list or scan channels.

Clean image NO plug-ins , addons or backups
and test it.

 

[Thomas67]

I could replicate this with IPTV are you watching regular Sat tv or do you watch iptv?

If you watch iptv when creating bouquet chose DVB1 instead of 4097,5001 or 5002 as internal player.
DVB1 streams direct without any buffer all the other player even if set to no buffer stil start and stopp buffring for short moments

If you watch regular sat TV do as Matrix describes then it has to be a plugin or something working in the background

I try to read the rules about talking about IPTV and they where somewhat fuzzy so if i break any rules with this comment please just delte it.

 

[xrobertas]

Hi Matrix.
Yes, I installed clean BH 3.0.6 as well as 3.0.7 with USB. It's still equal. But it probably started in the case when I was in BH 3.0.6 skin "MX Black Sea" first, the basic version. Then they were issued edits, but the problem remained the same. It turned out when using the plug-in, only used in the "czech-slovak" area. Plugin called "ArchivesCZSK" when scrolling using the dial driver, spiner appears for 10-45 sec. sometimes even more. But time has also been transferred to other functions of the system. When I use EPG and scrolling, I find myself in the corner of the spiner and brake me. Sometimes the program can not switch to the selected program. If the spiner lights up, nothing can be done.

 

[AlexWilMac]

So, it seems that the responsible is this plugin, also unofficial.

 

[Matrix10]

Hi Matrix.
Yes, I installed clean BH 3.0.6 as well as 3.0.7 with USB. It's still equal. But it probably started in the case when I was in BH 3.0.6 skin "MX Black Sea" first, the basic version. Then they were issued edits, but the problem remained the same. It turned out when using the plug-in, only used in the "czech-slovak" area. Plugin called "ArchivesCZSK" when scrolling using the dial driver, spiner appears for 10-45 sec. sometimes even more. But time has also been transferred to other functions of the system. When I use EPG and scrolling, I find myself in the corner of the spiner and brake me. Sometimes the program can not switch to the selected program. If the spiner lights up, nothing can be done.

If I understand the plugin, it causes problems.
The plugin should not affect the entire system.So the problem of compatibility.
You should ask the plugin author to help.

 

[xrobertas]

So after uninstalling the "ArchivCZSK" add-on, the spiner appears constantly. New installation BH 3.0.7. from USB stick. The spiner appears constantly when switching channels from the satellite, or when moving in the EPG.

 

[Thomas67]

Try and re flash back to 3.0.5 and if problem is gone then format and mount a Usb memory stick on your STB. Activate OpenMutliBoot and install 3.0.7 and see what happens
Sound very strange your problem and you are sure you dont have any other third-party plugin installed that could cause problem with the new BH Image?

 

[AlexWilMac]

If you insist to install a plugin that causes such problems (and this is clear: does your image run smoothly after a clean installation?) there is nothing we can tell you. You should contact the author of this defective plugin.

 

[xrobertas]

So it was what encouraged the spinner to appear. Started to discover it in BH 3.0.6 when I installed skin "MX Black Sea". Then followed 3.0.7 and 3.0.8, but the spinner appeared still. So I decided to return the skin "MX Titanium C2" which I used the first time. And it became a wonder and a spinner did not hold me anymore. So even with the plugins I used before I can see spinner only when restart the system.

 

[Thomas67]

Strange since that skin is default skin in Blackhole but if you have fixed it its nice for you just sorry you uninstalled the skin would surtenly been nice if you have upload it so Matrix could have a look at it.
It could be in just the image for your type STB that there is a bug because i have no problem with that skin

He has version BlackSea and BlackSea_I do you remeber what version it was?

 

[AlexWilMac]

But it doesn't seem he edited the skin. Only, he changed the skin used from MX Black Sea to Titanium C2, if I did not misunderstood.

 

[Matrix10]

Your story looks like a fantasy
and without logs

How is it possible that no single user have a problem that you describe.
I have test skin on five different receivers
None of the problems you describe.

What does that mean.
Something that you add in the image causes spinner
not the other way round.

 

[xrobertas]

I do not know, I just thought I'd get back the skin I had installed before it started. Now do not do it anymore. I have no idea. Is it possible that there will be a bug in my Solo 4K?

 

[Matrix10]

I do not know either.
I just know I do not have with my receivers.

 

[superglud]

This can be caused by "not optimal" network settings.
Please double check your nameserver settings and "Test" your network settings.
Best regards

 

[AlexWilMac]

I think he answered a long time ago, already in post #4, that the cause of his problems is the plugin
ArchivesCZSK
(obviously, a not official one).
But he wants to use it at any costs...

 

[Matrix10]

I think he answered a long time ago, already in post #4, that the cause of his problems is the plugin
ArchivesCZSK
(obviously, a not official one).
But he wants to use it at any costs...

This is a very big plugin
with a lot of Python coding that can easily
cause the problem.
The question is where the plugin is based on PLI / OE-A images or on VU + coding.
I think it's based on PLI coding.The author @mx3L is active in Pli forum.
(in his Git stands clear >>fix instalacneho balicka (*.ipk) pre openPLi)
In that case, I recommend Open Black Hole image
for trial.
Or ask the author if he is able to make a plug-in based on VU + coding.
Which will almost certainly work well on the BH image.

So this is not an Black Hole image problem
but plugin incompatibility with VU + coding and all images based on VU+ coding

https://github.com/mx3L/archivczsk/releases

To be clear
if you install this plugin
he made big changes inside the image.
Deleting a plugin and all files and changes is difficult.
Which means you have to re-install image.