208 replies to this topic

[malakudi]

Indeed, remote is now unable to enter numeric values in numeric inputs. This was working ok with previous drivers. Maybe VU+ changed something in order to try fix the issue and made it worse?

 

Numeric input still works in quickzap or as shortcuts in menus.

Edited by malakudi, 27 May 2013 - 09:36.

[MiLo]

Indeed, remote is now unable to enter numeric values in numeric inputs. This was working ok with previous drivers. Maybe VU+ changed something in order to try fix the issue and made it worse?

 

Indeed, the input is completely borked. Even a USB keyboard won't work properly on the latest version of their kernel/drivers (It only types "G" characters).

[bunbun]

Er zijn al een week geen updates meer voor de Solo2. Weet iemand wat er aan de hand is? Ik ben zelf een build aan het maken maar heb problemen om de streamproxy via cvs binnen te halen. Die repository lijkt niet meer te bestaan maar naar git gemigreerd te zijn.

Edited by Frenske, 1 June 2013 - 22:10.
This is the English section. ;)

[rodak]

Er zijn al een week geen updates meer voor de Solo2. Weet iemand wat er aan de hand is? Ik ben zelf een build aan het maken maar heb problemen om de streamproxy via cvs binnen te halen. Die repository lijkt niet meer te bestaan maar naar git gemigreerd te zijn.

And in English?

[bunbun]

Er zijn al een week geen updates meer voor de Solo2. Weet iemand wat er aan de hand is? Ik ben zelf een build aan het maken maar heb problemen om de streamproxy via cvs binnen te halen. Die repository lijkt niet meer te bestaan maar naar git gemigreerd te zijn.

And in English?

Sorry. Posted in the wrong section :-)
The last update dates from over a week ago. Anybody know why? Build problems? I'm trying to build an image myself but have problems getting streamproxy from cvs.

[rodak]

Indeed, remote is now unable to enter numeric values in numeric inputs. This was working ok with previous drivers. Maybe VU+ changed something in order to try fix the issue and made it worse?

 
Indeed, the input is completely borked. Even a USB keyboard won't work properly on the latest version of their kernel/drivers (It only types "G" characters).

Any news about this? Will it be solved or do we have to wait for new drivers from vu? Thanks in advance

[lnbr]

Hi all!

 

Just back from a VTI image (that worked fine, a bit slow though), hoping that my solo2 would take advantage of Openpli last version! 

So, upgraded to today's version (12/06). 

Right, disappointed!!! Can't input anything with the remote!   

[lotar]

is possible to use twin tunner? recording and see another channels dosen`t works

[Trial]

Hi,

 

is possible to use twin tunner? recording and see another channels dosen`t works

of course. How is your box connected and what are the settings?

 

ciao

[hemertje]

Hi all!

 

Just back from a VTI image (that worked fine, a bit slow though), hoping that my solo2 would take advantage of Openpli last version! 

So, upgraded to today's version (12/06). 

Right, disappointed!!! Can't input anything with the remote!   

 

tes, thx to VU+, you should thank them, not us!

[lotar]

Hi,

 

is possible to use twin tunner? recording and see another channels dosen`t works

of course. How is your box connected and what are the settings?

 

ciao

the same config in VIX works

sat cable to tuner B; and tuner A loop througth tunner B

[littlesat]

Vix seems allowing patching enigma2 to work-a-around the vu's driver issues...
We simply refuse this as enigma2 should be independed from the box it is running on.
In short we should not get thinks such as "if vubox then" and/or special unrequired config possiblities to work-a-round defects in drivers.
Possibly due this allowence vu does not have the urge fixing it....

Edited by littlesat, 15 June 2013 - 12:22.

[lnbr]

@hemertje

@littlesat

Well, I perfectly understand your position.  I really like Openpli that worked perfectly well on my DM 7020. But on the solo2 it's far from working as it should do.  As a basic user, I just want an image that works, I suppose you can understand... So, knowing that emailing Vu+ is useless (I've done it twice: they never answered), the only possibility left for us, OpenPli lovers , is going to another image, hoping one day Vu will fix their drivers... In the mean time, perhaps, as someone suggested in this forum, it would be better to clearly announce that OpenPli developers will stop supporting solo2 until Vu fixes the drivers...

[littlesat]

the only possibility left for us, OpenPli lovers , is going to another image,

Another solution might be.... buy another box....

In the mean time, perhaps, as someone suggested in this forum, it would be better to clearly announce that OpenPli developers will stop supporting solo2 until Vu fixes the drivers...

This means that there is no need for VU to fix the drivers...

Edited by littlesat, 15 June 2013 - 17:13.

[Trial]

Hi,

fix driver is the wrong word as they are working in their own image. Change the driver would be more correct.

 

ciao

[lnbr]

the only possibility left for us, OpenPli lovers , is going to another image,

Another solution might be.... buy another box....

 

Yes, that's what I would have done, if OpenPli had not supported solo2 ! (But anyway, this box is a great box!)

 

In the mean time, perhaps, as someone suggested in this forum, it would be better to clearly announce that OpenPli developers will stop supporting solo2 until Vu fixes the drivers...

This means that there is no need for VU to fix the drivers...

 

Sorry, I can't see why... But I don't want to argue anymore. Once again, I perfectly understand your position and I am perfectly aware of the amount of work needed. But we, basic users just want an image that works fine with our boxes.

[littlesat]

Yes, that's what I would have done, if OpenPli had not supported solo2 ! (But anyway, this box is a great box!)

We do support also DMM, ET and XT at this moment.... For Vu's manufacturer image this is not required. But if they do adapt E2 to their drivers they are in fact not E2 compatible....

Edited by littlesat, 15 June 2013 - 22:40.

[braunbär]

In the mean time, perhaps, as someone suggested in this forum, it would be better to clearly announce that OpenPli developers will stop supporting solo2 until Vu fixes the drivers...

Hopefully, OpenPLi isn't going that way. For my basic needs, my Solo2 works quite well at OpenPLi, and I'm very thankful for the hard work and future updates of the  PLi-Team.

Of course I'm angry about the bad VU+-divers: But, as others refered before, I never got a reply for my appeals and bugs from Vu+ ever. I won't forget this at future buying decisions.

Edited by braunbär, 16 June 2013 - 05:51.

[Robinson]

Actually, a friend of mine thinks of buying a Solo2.

I have ET9000 with OpenPLi 3.0 and I thought he would be happy with OpenPLi on Solo2 too. However, seeing that, I'm not sure whether he should go for Solo2 or for a different box. If he goes for Solo2, it looks like it would be better for him to use a different image.

Anyway, can anyone of you, Solo2 users, please sum up the points which are not working well due to bad drivers?

And are these things working well in any other decent image?

[lotar]

openvix works great in solo2; i love openpli but openvix is a good alternative until vu fix the drivers;