Remote not responding / 2 USB ports dead after Aug 25 upgrade

Thanks for that. I have the same issue and I am no further forward. I think a few of us have issues with USB just stopping.

@David: sorry to hear that :worried: - if you manage to get a solution, I’m sure a few of us with the issue would be very grateful, but it really does sound like a h/ware issue to me.

I hesitate to comment here given

  1. I love the vero v as a player, it has been the best I’ve ever had and has been exemplary with anything I’ve chucked at it.
  2. the support I’ve received has been fantastic, particularly recently on my hub issue.

That being said since then 1 1/2 weeks ago I received a third party hub, it worked fine…then I noticed tonight the drive attached to it had disappeared. Whether a powered or non powered drive, attached to the hub or straight in the usb 3 port no joy. Rebooting the machine didn’t help, but unplugging the hub and plugging into usb 2 both drives immediately appeared.

I’m just sharing this for interest - I can currently use the slower port and due to some personal issues (just lost a close family member) don’t have time or appetite for further investigation or troubleshooting.

Just to add, I did remove power from vero for 10s and issue persisted

I’ve been in contact with @mickb over the past few days, albeit slowly but due to how busy it gets this time of year.

I do not recommend that users open up devices to troubleshoot issues but rather get in touch properly.

My suggestion here would be to evaluate whether the supplied remote is working on your device.

Sam

Just for clarity - I only opened the device to relocate the remote dongle from the failed internal USB port to the only remaining active port (external USB2 ), after all other avenues to resolve the issue had failed.

I realise now that because of my actions, I have no recourse, & I either have to work around a partially-operational unit, or replace. I know others have the same issue, with no resolution, but it does worry me that devices are failing which are less than 18m old, & I can only hope the root cause gets identified.

I’m not aware of a common issue here, so I think it’s not fair to say that devices are failing after less than 18 months.

Unfortunately I can’t condone people opening their device to try and solve the problem. They should always contact or request support first.

Sam

1 Like

I did contact support prior to opening & moving the dongle. I’d be more than happy if a solution is found, has anyone else who has had issues with USB ports failing been able to resolve?

Funnily enough not currently.

I had changed the battery, hadn’t even realised it had a light until reading that here.

Light is on but usually I control with a harmony elite so hadn’t noticed. As before, don’t have much time/energy for troubleshooting atm so haven’t checked whether there’s something I need to do to re-pair it.

I have noticed a few posts regarding remotes or receivers failing, maybe I’m biased because mine also failed and less than 18 months. From the beginning, I noticed that the remote experience on the V was remarkably inferior to the 4K+ which I also had. The frequent misclicking (or whatever it the term is) was frustrating that I even went back to using a XBoxe One media remote. After ordering the new external dongle, the misclicking doesnt happen anymore.

I understand that to keep costs down and make the V affordable, the new receiver hardware was chosen, but in my opinion, there is something wrong with it, especially compared to the 4K+.

Nothing to do with costs.

The original remote dongle manufacturer went bust post COVID. The new remote solution worked well and was included on Vero 4K + for some time without issue

But as we implemented USB3 which the Vero 4K did not have, some poorly shielded devices and cables could reduce the range.

It is widely know that USB3 can have a significant impact on the 2.4Ghz spectrum.

Our aim is to allow the remote to work reliably without line of sight for distances of 8m as this comfortably covers most living rooms.

We have made improvements to the Vero V and the remote dongle itself to reduce potential USB3 interference, but it cannot be completely eliminated.

If you are experiencing issues with range, see Improving remote performance - Vero V - OSMC. I’d also be curious to know your order # so I can see what revision of Vero V and the remote you have.

I’m not sure it’s related to the issues reported here however.

2 Likes

I did supply my order number earlier. My remote worked for ages, then just stopped! That is why I thought it was software. Pretty sure my device is out of warranty, is my only fix to do what Mick did? I.e. open the device to relocate the remote dongle from the failed internal USB port to the only remaining active port (external USB2) ?

Still seems a few of us are having problems with the remote/USB:

Me
radek.dvorak
mickb
henryjfry
prohling (?)
dtech
dm999
Winters

I do not know if that will solve your issue for certain.

Please note that I am currently travelling so a bit slower on the emails / forum

Sam

It’s certainly not a ā€œsolutionā€, only a work-around which I had to use if I wanted to use the remote & a keyboard (via USB hub). I was hoping that it was s/w related, but as yet, nothing has resolved the issue (although I’m unable to install a previous version, just get root not found errors using microSD or USB sticks). Seems odd that several have had the problem coinciding with either the Aug or Dec update. Would be really useful if there were any Linux diagnostic commands which would interrogate / analyse USB ports to help give more info, could anyone advise on this?

Not to pile on here but add me to the chorus of users that have lost their remote with the most recent update. After update, remote control stopped working on my Vero V. Purchased way over a year ago, so pretty sure this is out of warranty, and was looking for a solution, landed here.

batteries good, used the home/select method to repair. Nothing. Am able to still use my iOS app on my phone to control, thankfully.

do not want to open up the unit. Still waiting for some sort of fix in the next update. Gladly take any suggestions.

Weirdly, I did see a Pulse Eight CEC adapter error. Wasn’t sure what that was about. It went by pretty quick. I don’t use CEC.

You could try installing an older version of OSMC but I can’t see this being software related as nothing has changed in the last update

Given that multiple users have units with failed USB ports, which seem to have been triggered by the s/w update process, is there anything in the process which could potentially result in a H/W error?

My offer still stands re returning my unit to base if detailed diagnosis could be done, to determine cause of failure & potentially help provide a solution which would benefit others here.

No, I’ve checked.

We’ve done extensive work on this.

If it was a software issue then installing an older version of OSMC would resolve it.

We’ve also looked at the hardware side.

Best,

Sam

My point was, as it seems to be a h/w failure, is it just coincidence that all of us who have this issue, it’s been directly coinciding with applying either the Aug or Dec s/w update? And would you expect this level of failure from such (relatively) new units, ie maybe 18-24 months old?

I’ve seen some reports of the remote not working in the past and we have investigated. I don’t think it’s related to the update.

As long as no one opens the device and gets in touch with support@osmc.tv, we should be able to take reasonable steps to remedy the issue.

Once a device is opened however, we won’t look at it. I received one back from a customer who had opened it and when I checked he had broken the WiFi module on the device.

Sam