Remote pairing issue

Help and Support Vero V
1

Hi i’m used to use the kodi remote from my phone so never really used the remote provided with the vero V.
But I now need it for my childrens.
But it doesn’t work.
my remote seems ok, so does the battery as the led blink blue on every and each key press.
when trying the re-pairing process (holding home+OK for 5+s) it’s fix blue for a couple of sec.
but nothing more.

here are the 2 usb checks i’ve made:

osmc@salonV  ~  lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
osmc@salonV  ~  dmesg | grep -E “usb|2017”
[ 0.704683] usbcore: registered new interface driver usbfs
[ 0.704731] usbcore: registered new interface driver hub
[ 0.704762] usbcore: registered new device driver usb
[ 0.890171] meson-mmc: mmc driver version: 3.02, 2017-05-15: New Emmc Host Controller
[ 1.118643] usbcore: registered new interface driver cdc_acm
[ 1.118689] usbcore: registered new interface driver usb-storage
[ 1.118763] usbcore: registered new interface driver usbserial
[ 1.118800] usbcore: registered new interface driver usbserial_generic
[ 1.118823] usbserial: USB Serial support registered for generic
[ 1.119318] usbcore: registered new interface driver uvcvideo
[ 1.119971] usbcore: registered new interface driver btusb
[ 1.121916] usbcore: registered new interface driver usbhid
[ 1.121919] usbhid: USB HID core driver
[ 1.158582] amlogic-new-usb2-v2 fe03a000.usb2phy: USB2 phy probe:phy_mem:0xfe03a000, iomap phy_base:0xffffff80081dd000
[ 1.158861] amlogic-new-usb3-v2 fe03a080.usb3phy: USB3 phy probe:phy_mem:0xfe03a080, iomap phy_base:0xffffff80081fe080
[ 1.654458] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.654462] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.654465] usb usb1: Product: xHCI Host Controller
[ 1.654468] usb usb1: Manufacturer: Linux 4.9.269-93-osmc xhci-hcd
[ 1.654470] usb usb1: SerialNumber: xhci-hcd.0.auto
[ 1.655927] usb usb2: We don’t know the algorithms for LPM for this host, disabling LPM.
[ 1.655997] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 1.656001] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.656003] usb usb2: Product: xHCI Host Controller
[ 1.656006] usb usb2: Manufacturer: Linux 4.9.269-93-osmc xhci-hcd
[ 1.656009] usb usb2: SerialNumber: xhci-hcd.0.auto
[ 1.658552] dwc_otg: usb0: type: 2 speed: 0, config: 0, dma: 0, id: 0, phy: fe03a000, ctrl: 0
[ 1.658557] dwc_otg_driver_probe host only, not probe usb_otg!!!

I also browsed the forum and found that some just got the dongle inside the vero V to plug it outside.
My vero V is from November 6, 2023 so definitely out of warranty.
Is opening the vero and try that the next recommended step, of can I made extra tests, just to confirm this not something just disabled or never enabled?
Thank you!

2

According to the information you provided it seems clear that you are unfortunately affected by a hardware failure that was thoroughly detailed in the following post. I would suggest to not open the device to get the internal dongle but rather contact support and have a conversation with Sam about how you should proceed.

3

Thank you so much.
I saw that thread, but stop reading after the moment they said that they fixed it by opening the box and plug the dongle outside.
I did the tests and you are right, this is exactly what my vero V has.
So I’ll send an email and see which advise sam will give to me.
Even if I think opening is my best option, I’like to confirm if I need to pay attention to some specific steps while doing it.
That would a shame to damage the whole box for just a usb dongle issue.
Anyway, one more time, thank you for pointing me to that response in the thread!

1 Like