Couple of issues with March update and remote

Help and Support Vero V
1

Greetings,

I wanted to ask a couple of questions regarding the March update and remote. I have updated my Vero V to the March update and I noticed:

1- Like other posts, I have encountered the same issue with the fast forwarding displaying a still image while the audio progresses. It seems that one of your devs has found a way to reproduce this issue so I’ll skip posting logs

2 - After the DV support with the last update, when playing a DV video file, the menus displayed on my LG CX when using my AV receiver (volume, picture info, speaker level adjustment, etc) have changed from a light blue tone to a magenta. I also use the V remote to adjust the volume, but that displays the AV receiver’s volume menu/bar as expected, with the same magenta tone. Other video files don’t display this light blue to magenta change, only DV. Is this expected?

3 - I used the V remote long press shortcuts, e.g., long press on Stop button to bring up the subtitle settings, long press the hamburger menu button to bring up the soundtrack settings. It seems that those don’t work anymore with the March update. Was this a planned change?

4 - Finally, the most frustrating issue: I had the Vero 4K+ and its remote was quite sensitive. Any key press had a quick response. With the V’s remote, it’s different, often requiring several presses. This to me is frustrating. I have read other posts and the reason for this being interference some other devices, but the V is in the exact same place as the 4K and didn’t any problem with interference from other devices. I know that the 4K had an external dongle and the V doesn’t. My question is, the remote + dongle you have on your store, is it the same as the 4K one? If I used that instead of the V, would the interference related response issues still apply?

2

do you find the remote works well for a period then suddenly becomes unresponsive for 5 seconds or so before returning to normal function? or is it just unresponsive in general for you.

3

Yes. If your AVR isn’t smart enough to convert its OSD to DV the colours will be wrong when playing DV profiles 5, 7 or 8. I don’t even know if any AVRs can do that conversion and merging. Mine doesn’t.

4

It does work well for most of the time, but suddenly stops registering clicks and requires repeating 2, 3 times then goes back to normal. I have tried adding an Xbox One media remote which works well too, however it’s direct line of sight and it must be about 8 or 9 years old so sometimes misses clicks too. Less frequently than the V one.
Just an aside, I do remember that the remote on my 4K+ (gave it to a friend of mine) still had the logo on the front even though I had it for 3, 4 years. The one on the V, it’s not even a year old and the logo is long gone.

5

yep that sounds like my experience.
hopefully an external receiver can resolve the issue.

6

Not sure how that will help unless you bought your device a very long time ago (August 2023) and have USB3 or WiFi equipment attached/near.

The remote for 4K+ and V (and the receiver) are different.

7

the “Improving remote performance” section on the VeroV wiki suggests “Attach (available separately) an external receiver to a USB extension cable”. Is this no longer valid advice?

OP and I are talking about the VeroV and its remote not working reliably, and the OP is comparing the performance of the VeroV to thier previous experience with the Vero4k+.

I purchased my VeroV in mid Feb25.
I am using the remote about 1m away from the Vero.
I have replaced the battery with a brand new energizer.
I have nothing connected to the Vero other than Power, HDMI and LAN.
I reinstalled OSMC 4 times yesterday which included the pairing step each time.

8

Nothing should have changed in this regard. If you could post a debug log this may shine some light on why you are seeing this behavior…

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • reboot the OSMC device twice(!)

  • reproduce the issue

  • upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

  • publish the provided URL from the log set upload, here

Thanks for your understanding. We hope that we can help you get up and running again shortly.

OSMC skin screenshot:

image
image960×539 41.4 KB

9

I’ve left this in place but it would not apply for your order anymore. USB3 devices attached will always have an impact, but less so now after some improvements. But we can’t fix peripherals that really leak (sometimes it is just the cable).

If it is not working from 1M away you must have something causing interference.

Maybe you could show us a photo of where the Vero is placed in your system?

11

Where I originally setup the Vero and first experienced issues with the remote. LOS about 1m from remote.

IMG_1002
IMG_10021920×2560 227 KB

Normal Location - in cabinet draw with powerboard, switch, appletv and backup mouse. (not ideal I know, however I experience the remote issues just as often as when on top of the cabinet during initial setup, appletv has no issues in there.)

IMG_0998
IMG_09981920×2560 353 KB

IMG_0999
IMG_09991920×1440 183 KB

Where I am testing now. So far I have not encountered a dropout in few minutes testing.

IMG_1001
IMG_10011920×2560 309 KB

what I have noticed:
-Seems to occur after a period of rapid clicking - like during setup, happened pretty frequently (every few minutes) during my repeated reinstalls yesterday. though I guess you would expect to notice a malfunctioning remote more often when using it vs not.
-Seems to happen sometimes after picking up remote, like it is waking from a disconnected sleep state.
-Turning off unnecessary rf devices (AppleTV, PC w/ wireless KB/Mouse, Mini Remote KB) doesn’t resolve issue.
-Haven’t turned off WIFI or LG TV Remote - not feasible.
-Tested with HP-MCE rc6 IR remote to confirm it wasn’t kodi freezing, also tested with the mini rf keyboard attached and it responded instantly when the remote wasn’t - so pretty sure it is remote and not kodi.

If the remote works correctly with the Vero on the side table I’m fine with purchasing an external receiver and putting it on the end of a usb extension cable on the table.

This is not a show stopper for me compared to the issues that have plagued Kodi on Windows HTPC for the last few years, more of the final 1% issue that once corrected would make the VeroV damn near perfect.

12

There is a known issue since the upgrade to Kodi v21.2 where skipping in between scenes (using arrow keys) isn’t working as well as it should be. This didn’t seem to be an issue with v21.1.

This is being investigated and will get solved. So make sure that you don’t conflate this issue with remote performance. I even made sure in the other post where this is reported that keys are being registered and they are.

OSMC remote should get you a good 8-9M range. Operating it from short distances (1M) is one we haven’t focused on recently. I’ll take a look

Sam

13

Yes I commented on that keyframe seeking issue. Not conflating the 2, this happens most often when navigating menu screens/lists. I don’t use the remote much while actually watching videos.

14

Thanks for confirming.

Please confirm at the medium distance in the new setup. I appreciate you can’t do this immediately

Sam

15

Issue still happening after:

  • Tested with Vero on side table 0.5m from remote.
  • Tested with Vero 1.8m from remote.
  • Turn off/Unplugged every RF device I can: WiFi AP, PCs, Microwave, AppleTV, Moved AppleTV Remote to different room, Removed batteries from LG Remote.
  • Disabled CEC input peripheral in Kodi System Menu

It presents in 2 ways: as a single missed button press, or more rarely as repeated button presses missed for about 5 seconds.

16

After enabling logging and rebooting twice, I wasn’t able to reproduce the long press issues I described. It was repro before the rebooting because I use those 2 long press functionalities quite often. Sorry for the ‘false alarm’ and thank you for taking the time to reply.

1 Like
17

I bought it in April/Mayish 2024 and I do have a Wifi router and NAS nearby. Maybe a USB3 HDD plugged in but very rarely. Same location as my 4K+ was when I had it and didn’t have any response issue with its remote/receiver hence my question regarding the combo on your shop.

18

If you still have a problem, then I would try the USB3 drive in the USB2 port temporarily to see if it improves things. If it does, then consider changing the USB3 cable to the drive.

Sam

19

I can try that but the response issue happens even without any drive connected to the V. As I mentioned, only very rarely I have a USB drive connected to the USB port.

20

When testing prototypes, I found that mashing the remote buttons was counter-productive although the intuitive thing to do. If you’re getting a poor response, best to let the remote do nothing for a second or two. That seems to re-set the frequency bands it uses - hopefully away from any interference. Production remotes are definitely better than those prototypes but may have a similar behaviour.

21

I have the same issue with remote. Sometimes it hangs when pressing OK. Need to press is 3 times and then i works.

I opened the remote and the VCC and GND are good(2.9V). The WIFI-BT chip i use is a BK2452. I am thinking of maybe replace this with a BK2433 which can better handle noise.

What i also noticed that my remote randomly gives a “click”. Could be the chip or other IC component.

Finally i tried to test the remote via evtest(sudo evtest /dev/input/event5) and while testing couldnt find any issue, but replicating is difficult.

Event: time 1742214850.067545, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70051
Event: time 1742214850.067545, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
Event: time 1742214850.067545, -------------- SYN_REPORT ------------
Event: time 1742214850.187533, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70051
Event: time 1742214850.187533, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
Event: time 1742214850.187533, -------------- SYN_REPORT ------------
Event: time 1742214850.627534, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004f
Event: time 1742214850.627534, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1
Event: time 1742214850.627534, -------------- SYN_REPORT ------------
Event: time 1742214850.795515, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004f
Event: time 1742214850.795515, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0
Event: time 1742214850.795515, -------------- SYN_REPORT ------------
Event: time 1742214851.339518, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70050
Event: time 1742214851.339518, type 1 (EV_KEY), code 105 (KEY_LEFT), value 1
Event: time 1742214851.339518, -------------- SYN_REPORT ------------
Event: time 1742214851.531504, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70050
Event: time 1742214851.531504, type 1 (EV_KEY), code 105 (KEY_LEFT), value 0

Need to do some more testing…