VU+ Solo² Remote Keypress repeat issue

  • Thread starter Thread starter CodyX
  • Start date Start date
C

CodyX

Hello!

I have OBH 4.3.037 on the Solo². When I use (for example) the number keys on the remote to jump some time over the playback, I can only press 4 times fastly to each other. The fifth keypress is ignored. Then I must wait some seconds and the next keypress (in most cases only one) is accepted.

When I use two or more different keys (e.g. 3, 6 and 9 for jump forward), this effect is less but stay here.

I have tried to finetune the settings under menu > configuration > system > input devices > dreambox advanced remote control. It feels like a litte bit better but not really good.

Is there anonther setting to change this behavior?

Greets
Cody
 
After a lot of time I think to isolate the problem. Its caused by the "Input device setup" mechanism. In any list, for example the stations or recordings list, I press the down key at the remote once. It will move the selection down once. I will press the down key one more time, nothing happens. I press the up key, selection go up once. Next press up again and nothing happens. Absolutely reproduceble. It is impossible to press-and-release a remote key more than one time.

When I open the list again and press-and-hold the down key, it will move the selection down and down and down, works correct. When I now release the down key and press it again, the selection go down once. When I press the down key one more time, it works furthermore. No problems until i press the Up key next time. Then the problem appears again. Please understand me right: This happens on any key on the remote, I have only described it on the basis of Up and Down key.

The issue is only related to the remote device. When I attach an USB keyboard to my Solo2, I can move the selection absolutely perfect as expected.

This is definitely not a hardware issue. I'm sure this is caused by software. Looks like a bug in "Input device setup" for key press repeat. I've found a lot of similarly bug reports on different VU+ forums from Blackhole over VTi to OpenPLI and OpenViX. Some of the affected users has finally their VU thrown in the scrap. This is weird! I think, the problem was programmed a while ago in the common base of all of these Images. As I remember, the last BH image on my Solo2 without this issue was an 2.9.x. But unfortunately I cant try it out because I havent the image anymore and here in the download area are no such old images available.

My hope is, together we can find out when and where this issue was happen first time. I'm not familar with VU+ image development, so I cant look into the codes myself. Please support me, thanks!

Greets
Cody
 
Finally I've found the solution myself. The box and the remote are working again.
 
My Solo2 was originally shipped with a type 2 remote. Then after months of frustration I bought an Uno4kSE shipped with a type 6 remote. Then I had compared both and exchanged the remotes, using type 2 on Uno4kSE and type 6 on Solo2. Surprise: Type 2 works on the Uno4kSE with original image but with OBH 4.4 the same sh*t as with my Solo2. On the other hand, the type 6 works fine on the Uno4kSE with original image and OBH 4.4 and... drumroll... also with the Solo2 and OBH 4.4! After this, I bought an second type 6 remote and used it with my good old Solo2.

I think the entire problem is that OBH 4.4 (or the OpenVIX on which is based on) was never tested with an type 2 remote. Otherwise, it should have been noticed that type 2 does not (good) work. Then I've tested both remotes with a arduino IR decoding. Here I can see that both remotes uses the same codes but different timings. The type 6 is faster. And this is the cause why OBH 4.4 fails with the older type 2 remote: The faster timings are hard-coded in the image. Any change in the settings menu does not have an effect.
 
I have been using the same remote i think from VU+ uno for several years
on all boxes from VU + Uno to 4k boxes.
So that problem is still specific to your case.
 
I've always used only type 2, although with two different remotes, on three boxes and OBH has never shown this issue.
 
I cant say whats happen, I'm not the OBH developer. In fact I've tried more than one type 2 remote both with the same issue. And if you seek for "VU+ Solo2 Remote slow" you will find some other people who has the same problem on a wide range of different images over the years:

https://www.opena.tv/english-section/2805-remote-bit-slow-try-vu-solo2.html?langid=1
https://www.vuplus-support.org/wbb4/index.php?thread/96059-vu-solo2-zu-langsam/
https://www.world-of-satellite.com/showthread.php?41205-Solo-2-remote-very-slow-and-doesn-t-respond
https://www.linuxsat-support.com/thread/84831-slow-to-react-to-remote-commands/
https://www.nachtfalke.biz/f198-vu-...ehrere-aufnahmen-gleichzeitig-unmoeglich.html
https://harmony-remote-forum.de/viewtopic.php?t=10381&start=15
https://vuplus-community.net/board/threads/slower-changing-channels.15550/

Most of them had the same long time misery like me because the behavior looks like an box or image issue, not an remote issue. They and I had tried a lot of configuration, plugins and so on but finally the remote was the problems source. Dont ask me why, I dont know. I've seen a lot of weird hints like LED light bulbs intereferencing and so on. But finally you can see it very easily when you set up an simple Arduino IR decoder and/or logic analyzer. Type 2 and type 6 remotes (i have no other types to check) uses the same key codes but different timings. When I have more spare time, I will set up an Arduino IR transmitter to evaluate on which timing levels this issue will happen in OBH 4.4.
 
You must log in or register to reply here.
Back
Top