115 replies to this topic

[Firex]

Problem with clock:

 

Did you try a full restart (not only restart GUI) of the box?

[shilev]

no, i didn't, but i find timezones.py file on pli site and replaced the one in the box and now it's ok!

[Erik Slagter]

The only solution is a bug fix in the drivers by VU+.

[Dimitrij]

The only solution is a bug fix in the drivers by VU+.

Let's look real.
This bug two years.
The only good method we possibly can accept is to create a patch on VU's bsp layer.

https://github.com/v...vuplus/issues/3

Erik help me do it.

[shilev]

i see some other bugs now, like green screen after stopping timer and green screen when pressing menu-setup-customize. this has never happened before.

i tried reflash with backup and put just new nimmanager py and pyo, without  "opkg install enigma2-src" and now it's ok. no timezone bug, no green screen and loop through works.

only ci+ support is missing to make this image perfect!

[Rob van der Does]

The only solution is a bug fix in the drivers by VU+.

VU has not accepted this as a bug, so that will never happen.

[littlesat]

i see some other bugs now, like green screen after stopping timer and green screen when pressing menu-setup-customize. this has never happened before.

i tried reflash with backup and put just new nimmanager py and pyo, without  "opkg install enigma2-src" and now it's ok. no timezone bug, no green screen and loop through works.

only ci+ support is missing to make this image perfect!

When did you flash the last time... from somehow beginning March re-flash your VU-box was mendatory.

[Erik Slagter]

 

The only solution is a bug fix in the drivers by VU+.

VU has not accepted this as a bug, so that will never happen.

The problem is twofold: the looping is the "wrong way around", which you may or may not call a bug, but also enigma needs a workaround to get it working, which I call a bug indeed.

[Rob van der Does]

The only solution is a bug fix in the drivers by VU+.

VU has not accepted this as a bug, so that will never happen.

The problem is twofold: the looping is the "wrong way around", which you may or may not call a bug, but also enigma needs a workaround to get it working, which I call a bug indeed.

I agree, but that doesn't help; as I said VU doesn't accept it as such.

[Erik Slagter]

If you want an image that workarounds everything unlimited you know the answer.

[deusex]

hello openpli community,

 

i just want to thank "Firex", it worked great! 

 

Cheers

[malakudi]

A patch for correct solution (allowing user to select internal or external loop manually and not trying to guess) is on the works. Please allow a couple of days because I am a bit busy right now.

Edited by malakudi, 18 April 2015 - 11:03.

[deusex]

A patch for A --> B and B --> A?

[malakudi]

The main tuner for Solo2 is B. This is where antenna has to be installed. With the patch, you would set Tuner A loopthrough to tuner B, type internal. The missing option currently is the "type internal" and this will be implemented with the patch.

[littlesat]

In fact Tuner B should be Tuner A and tuner A should be Tuner B....

They can fix the drivers.... but not fix the printing on the box

I hope someone can make a general patch.... indeed an new internal looping type could possibly solve the topic. So program the input on B, and put A on internal looping.... (don't care to which tuner).

Edited by littlesat, 19 April 2015 - 12:55.

[deusex]

Updating today broke loopthrough. I am going to re patch it manually.

[littlesat]

Every update will brake manual patches....

Edited by littlesat, 22 April 2015 - 10:45.

[Dimitrij]

Just wait for a patch to address this issue.
It will be done in any case.

[deusex]

It is ok i repatched it and its working again.

[Dimitrij]

It is ok i repatched it and its working again.

opkg remove enigma-src

and

repatched it and its working again