I can live without the ambilight for a while.
I’ll give it a few weeks and see if anyone else comes out of the woodwork before going the reinstall route.
Try a cold boot without the external USB receiver attached. We turn off the internal port when the external receiver is detected but we might be doing something incorrect.
I see the icon for the SD in his photo. It is the USB 3 port being reported as non-functioning.
Hello. A couple of questions:
- Is there a fix on the way?
- Can I revert back to 20.5?
After more than six months of crappy, unresponsive remote performance, including waiting for the new one for two or three months, I’m back where I was before. It was nice to have a functional remote for three months. Honestly, and excuse my passion, I want to throw the remote at the wall. It’s just a simple remote, a simple thing that works on dozens of devices since decades, and it still does not work. At this point I’m willing either to revert back to 20.5 and maybe have a fully functional device or return it. It’s been I think a year for me with Vero V, and the remote worked only for 2-3 momths, in the gap between me receiving the dongle after three months of waiting for it and the new awesome 21.1.
Excuse the rant, excuse the language, but this is really silly and not professional. And it really pains me to say this. I love Kodi, love OSMC and overall love my Vero. Despite it being unable to do this really simple thing. I’ve received a email that there’s a new super remote coming up. But can we PLEASE first make this one work, once and for all? Thank you.
A pretty damn frustrated customer.
Sorry – I’m a bit confused. Your last post was in February and I am not sure what your post here is regarding.
There haven’t really been reports of remote issues for some time; particularly since we refreshed the receiver (dongle) hardware. There haven’t been reports of remote performance degrading with Kodi v21.
Are you saying that after receiving a replacement remote receiver, it worked well until updating to Kodi v21?
I don’t really know what you want fixed.
Of course, you can do so by going to Download - OSMC.
Unfortunately you’ve sort of just jumped on this post and I don’t know what issue you are exactly experiencing or the full story behind your situation.
Sorry. My post is regarding the fact, that after 21.1 my remote came back to its old, buggy, laggy self. Before this, you and I exchanged many emails about me being unable to receive the replacement dongle for three months and you sending it thrice, or I was mislead there. I’m a owner of Vero V for almost a year and in that year, the remote was functional only for two months? That is the period after I received the dongle and before the 21.1 broke the remote.
Yes. That’s why this topic was started I think.
I would want a functional remote. As I said above, and in my emails from when I was waiting for the dongle, it has worked as advertised for two months out of twelve.
I wrote my issue in the 21.1 release topic. After this you separated it to a different one to deal with it properly. My post is the opening one. To sum up again:
Bought Vero V. Remote was laggy as per known issue.
Waited three months for the replacement dongle to arrive.
Dongle arrives, remote finally works as promised for two months, the suddenly…
21.1 update arrives, remote is back to the laggy, before-the-replacement-dongle performance.
Tried all of the two usb ports. New battery, re-pairing.
Do you have a ticket number?
Sam
We mailed under a thread called “Your OSMC order is now complete [#803999]”, if that’s what you’re asking. Thanks.
Can you upload logs so that it can be checked that the dongle is detected.
This thread is about where the USB got issues it might be similar in your case, a log would tell.
Yes, it was, thanks. It can be hard to correlate an email address with a forum user name as they usually differ.
I have checked the ticket.
You ordered a replacement receiver on 17th February and we shipped you one on 18th February to your address in Poland.
Definitely not mislead. We tried to get this dongle to you a few times.
On 18th April 2024, after we had sent you a replacement as you had not received the item, we received one of the dongles back. The item was returned to us as unclaimed and the Post Office stated they could not contact you. I sent you a photo of the returned item.
My understanding is that after sending this item a third time, with your contact number, you received the dongle in early April and were happy with the results.
We haven’t changed anything in v21 that should be impacting your remote. You are welcome to downgrade to Kodi v20.5; but I don’t think this will be the cause of the issue. Please provide a lot as @fzinken has suggested.
If the receiver is functioning correctly, we should see this in your logs:
External OSMC Remote USB receiver detected - internal receiver disabled.
Thanks
Sam
My supplied remote has also stopped working with Vero V. Latest update applied. Had recently become laggy, but now, with latest update the remote is completely unresponsive. New battery tried, no change.
Logs:
https://paste.osmc.tv/xeqihemawi
p.s. nothing plugged into the USB ports at all. Tried re-pairing remote on a fresh battery and the blue led (inside remote) lights after holding Home + OK for a few seconds and remains lit 20 seconds+ before going out. No change in remote behaviour. Still not working.
Just to add to the above, my Harmony remote has stopped working completely twice since the upgrade, requiring a repair via myosmc. Has anything changed with bluetooth?
No.
The remote dongle is not being detected.
Can you plug in another USB drive like a thumb drive and see if it’s detected?
Sam
Hi Sam,
Thanks for taking the time to respond. I remembered a similar issue some years back with my v4 box and have since taken the usb remote dongle from it (external plug-in) and plugged it into the Vero V. Following a reboot my remote is working again. I’m aware this is something of a hack as it hasn’t solved the problem with the Vero V’s internal remote receiver, but it does at least prove that the USB 2 port is working. Hope this helps with the trouble shooting.