Here is a view from my perspective.
My last box was a Chromebox CN60 (2014) with a 1.4 GHz dual-core [Intel Celeron 2955U] - I never had a problem
At the same time that I bought the Vero 4k+ my friend bought an Nvida Shield (because it was a known brand) and he has no problems.
I recall that we had this conversation in November.
The Vero 4K/4K+ can provide 0.5A per USB port as per USB 2.0 specs. This will not be sufficient to power a 3.5" drive, but usually suffices for 2.5" drives and should suffice for a USB thumb drive.
In future iterations of hardware where we implement USB3, we can provide 1.5A per port.
Hopefully this clears things up
Can i help?
I also have this same issue.
After a while i don’t have image from the Vero when switching to the correct HDMI port.
I have Denon receiver and a Sony tv connected with each other.
When i power down the Vero, it reboots and everything is oke.
What can i do help?
This could be CEC related.
Are there any other devices connected to the receiver / TV?
Hi Sam, Yes. But on the other device(s) CEC is disabled.
So i think that shouldn’t be the case.
Quick update from my set up, since setting the GUI on my 4K TV to 1080p I’ve yet to have this issue reoccur. I’ll report back if it happens again. Hope everyone else has some luck in getting this annoying bug sorted soon.
My GUI is set to 1080p from the beginning. The issue occurs every 120 hours (5 days) approximately.
From my side, after 2 restarts (as been told as a possible option in this thread), the vero is still running nicely.
I will update my side of this ‘story’ within a couple of days.
Still no reoccurrence of this issue for me with GUI set at 1080p
Still going strong here…!
Unfortunately had this occur twice again when set to 1080p. Any new ideas on what’s causing this?
Does unplugging and re-plugging the cable help?
No, it does not.
Can you confirm HPD lock is disabled?
Yes, it is disabled.
Can you upload some logs?
I just need to check version information.
I have been able to reproduce on an LG TV here so am investigating.
Thank you for your time.
As I have said in my first posts while the “grab-logs -A” command" seemed to work for the first couple of days returning a https://paste.osmc.tv/abcdefgh address, when the problem occurs 5-6-7 days later, it once again returns the https://paste.osmc.tv/html_ response. It seems that due to the log file size (?) it fails if the debug stays on for a certain extended time.
So I am not able to provide a log file that includes the issue this way, unless it occurs within e.g. 48 hours.
What I can do now, since I am away, is to provide some logs that I have available from this period that the problem is present.
https://paste.osmc.tv/ufanahixir
https://paste.osmc.tv/uhuyepabor
Hope to help.
PS. I am in version 19.3.
Any progress?
I can no longer reproduce this issue on the latest version of OSMC.
Sam
So, in what version did you reproduce the issue on an LG TV?
I am in version 19.3 with the latest December update and I still have the problem since August.