208 replies to this topic

[littlesat]

Possibly thanks due to Vix work-a-round fixes VU does not have the need to fix their dirvers....

[speed]

i can remember before the numbers where also not working on solo2, vu+ didnt fix the drivers, but openpli made a workaround

so openpli theirself also contributed to this situation

[littlesat]

We didn't make any work-a-round.... The PLi based images made work-a-rounds....

Edited by littlesat, 16 June 2013 - 17:42.

[speed]

Here is a fix for RC numeric keys with the best regards to OpenPli team.

diff -u --recursive --new-file a/rc.cpp b/rc.cpp
--- original/rc.cpp 2012-08-19 17:26:07.000000000 +0400
+++ new/rc.cpp 2013-02-02 21:59:17.000000000 +0400
@@ -148,6 +148,9 @@

bool eRCInputEventDriver::isKeyboard()
{
+ /* this ugly fix for solo2 */
+ if (strcasestr(getDeviceName().c_str(), "remote") != NULL)
+  return false;
  /* check whether the input device has KEY_A, in which case we assume it is a keyboard */
  return hasCap(keyCaps, KEY_A);
}

 

and we do like ugly code, do we? https://www.nluug.nl...tract/ab21.html

 

 

Milo did commit something today that might fix the issue in a more ellegant way

[littlesat]

That fix is indeed ugly... VU has also an remote with alphanumeric characters.... then you block this...

 

What they should do is add an option to the drivers so you can tell the driver what remote is used... via a config in enigma2... Then enigma2 can read back if KEY_A is possible then we have a remote with alpanumeric charactors, otherwise only numbers.

 

E.g. ET is doing the same with the options to select Dreambox Remote or VU remotes....

[speed]

problem is they dont

you say it yourself vu+ is not gonna fix it because of these workarounds

 

so why not help the solo2 users and add an option to select this in the image

or any other option that would work that would be more easy for fix this problem

[littlesat]

And they possibly don't because there are colleague images around that are willing to add ugly patches.... something we don't....

so why not help the solo2

It only could lead to introduce bad patches anywhere... Where is the end?

I think when VU did not run on all OpenPLi based images... they already fixed it...

So who in the endeffect does help VU users?

 

or any other option that would work that would be more easy for fix this problem

You can also patch yourself... and repatch after each update...

Edited by littlesat, 16 June 2013 - 18:12.

[pieterg]

problem is they dont
you say it yourself vu+ is not gonna fix it because of these workarounds

Just give them some time. With the latest drivers, they clearly demonstrated they are willing to make changes to the way in which the input devices are presented. They just didn't yet quite get it right this time.
So allow the VU+ developers the time to figure it out, and finally fix this issue.

[speed]

new drivers available

any chance in having fixed remote now?

 

driver update
20130621
- Fix TS Playback problem
- Fix i2c error handling
- Turn off LCD at standby by default(duo2)
- Change default LCD brightness(duo2)
- Support DVB-T external antennae(duo2)

[betacentauri]

See here...
http://sourceforge.n...c396/log/?path=

[malakudi]

New drivers didn't fix anything input related, still completely broken (even USB keyboard doesn't work).

 

Since above patch has been implemented, may I suggest a different approach? We could just add a generic option in the remote control (dreambox native) configuration, where we can define manually if the remote features A-Z characters. So it is just an override of the autodetected settings. I can provide such patch if needed.

[pieterg]

In fact, with the previous driver update they managed to create an even bigger mess, by adding EV_ABS in the caps.
So e2 (rightfully) thinks it is dealing with a pointer device.

The vu+ developers do not seem to care, so we gave up waiting for them to fix their stuff.
Earlier today Erik Slagter has put a HACK in place to work around this.

The solo2 rc should now behave like as a normal rc, without alphanumerical keys.

[speed]

i just updated

but still nothing is working?

no numbers and no letters

[betacentauri]

Do an update tomorrow.

[littlesat]

...as the build server should be run first post the commits....

[Kuddelfisch]

Hello,

 

after todays online update the remote works all right at last.

Thank you.

[Firex]

The vu+ developers do not seem to care, so we gave up waiting for them to fix their stuff.
Earlier today Erik Slagter has put a HACK in place to work around this.

The solo2 rc should now behave like as a normal rc, without alphanumerical keys.

 

Thank`s a lot to the PLi-Team!!!

 

Regards

[speed]

and finally a working remote

thanks pli

[dirac]

    Thanks  

[braunbär]

The "Show full remote" doesn't work at my Open Webif.