208 replies to this topic

[Dan Daemon]

Hey guys,

Do I need to do any special steps before update to OpenPLi 3.0 with my new VU+ SOLO2?

I tried update receiver today but got no luck. The update process stucks on first step,
LED screen shows something like:
1. Erasing
2. Flashing
3. UBIFS Update
...
and then stuck on step 3.

No reading data from USB, no other actions.

What can it be?

[Dan Daemon]

Change the USB stick resolved the issue.

[Dan Daemon]

But number keys still does not work in latest version.

[redribo]

yes rc number keys doesnot work,
i think tha must be there red plate ,until someone(vu) fix the problem

[hemertje]

to every VU+ user: mail your problems to VU+ and notice them your problems

[ims]

there in menu as hotkeys and for channel selection numbers works... but f.eg. set IP is not possible.

[Dan Daemon]

I updated my SOLO2 online today and the receiver stopped starting.

[Ivan]

to every VU+ user: mail your problems to VU+ and notice them your problems

done
http://vuplus.com/su...ReportWrite.htm

[Dan Daemon]

to every VU+ user: mail your problems to VU+ and notice them your problems

There are not any problems with VU+ original firmware. There are the problems with OpenPLi only.

Do you suggest us to send them OpenPLi relating complains too??

[littlesat]

Yep

[Dan Daemon]

OK deal. But may I ask you to explain me why? Just curious? VU+ team bought/hire OpenPLi team? Or OpenPLi team is going to stop create VU+ images?

[hemertje]

VU+ does not use international standards, instead they imagine and think what they can build themselves so that the basics got broken when using other repositories

[Dan Daemon]

Clear! Thank you!

[Rob van der Does]

VU+ does not use international standards,

Can you point me to those standards? That would make it more easy and objective to communicate with VU+ and make them clear what exactly is wrong.

[hemertje]

Again, this discussion with SatKiekerd aka Rob vd Does aka VU+NL leads nowhere.
All is said allready.

Stop spamming our forum!


Topic closed.

[Rob van der Does]

You're wrong: atm I'm in contact with VU+ and would like to use the opportunity to drop as many as possible flaws on their desk.
The better I'm informed, the better the info I provide them will be. Being able to point to (international) standards can only improve this process.

Edited by SatKiekerd, 30 January 2013 - 08:29.

[hemertje]

see our earlier forumtopics, all is said many times before and we don't like to repeat ourselves.
so suit yourself...

[Rob van der Does]

I did so (again), although I'm quite familiar with the contents already, and I couldn't find any (cross-)reference to any standard at all.
And again: being aware of any standard could be a great help in trying to help you in the often repeated request to inform VU+ about driver issues.

[Rob van der Does]

LOL: I just got a reply back from VU+ stating that in their image and also in the images based on that, there seems to be no problem.
Now you and I know the cause of this, but I really need to have some strong arguments as to why in images with an other basis there is a (driver related) problem indeed. My statement 'it doesn't work in PLi' doesn't seem to be very impressive. The more (objective) arguments I can give them, the more chance we have in getting this fixed.

[WTE]

LOL: I just got a reply back from VU+ stating that in their image and also in the images based on that, there seems to be no problem.
Now you and I know the cause of this, but I really need to have some strong arguments as to why in images with an other basis there is a (driver related) problem indeed. My statement 'it doesn't work in PLi' doesn't seem to be very impressive. The more (objective) arguments I can give them, the more chance we have in getting this fixed.

Does this mean you say that VU+ doesn't care about our request and find support of "PLi" not important point?