So, for the n-th time, my Vero 4k stopped working.
When I use the remote - and I’ve tried several, with and without an extra BT dongle - the screen just blinks. Any button makes the screen blink and stay blank for a few seconds before returning. And trying to play a video results in a perpetual blank screen.
Then, after a while, it wouldn’t even boot. It comes to several attempts of
[FAILED] Failed to start Bluealsa daemon.
and never gets past that.
Also, I’ve tried 6 (SIX!) different USB dongles with a new image, and every single one of them results in absolutely nothing happening when restarting the POS device. Nothing. Just a blank screen.
This is the n-th time I’ve had problems with this POS device, and I’m getting really sick of it. However, I’d like for it to be fixable, since I’ve not seen a good alternative.
Can you post a screenshot of your USB contents? From your post history, I can see that you used the wrong image last time when you had to reinstall as your device didn’t have enough free storage.
But since then, I don’t see any reports of an issue from you since September 2020. Did you open a ticket or support request?
I’m confident that we can get this solved for you promptly.
Sorry for the angry tone, but I sincerely find this frustrating, to say the least.
I’m using the OSMC installer, and selecting Vero 4k/4k+. It’s hard to get the wrong image then, I’d think?
However, the whole installation takes a few seconds (after downloading), which doesn’t seem right. And the USB pen is not readable on my windows computer afterwards, so looking at the contents isn’t an option.
I’ve no downloaded the Vero 4/4+ image directly, and selected to use the image from my local machine instead of automatically downloading. Let’s see if anything’s different…
So I created the install disk on another computer, where I was actually able to view the contents. Absolutely no change.
Also, quite excitingly - the error/failure when trying to boot the Vero with the existing file system changes/evolves even though change has been made. Yesterday, the error was this:
[FAILED] Failed to start Bluealsa daemon.
…and then eternal hang.
Today, the error is this:
Waiting for root filesystm device /dev/vero-nand/root
Impressive, really, that this changed apparently all by itself.
Anyway…the contents of the USB disk after creating the installer:
On the first attempt, the error when trying to boot from the USB disk was the same as without (waiting for root file system…). So it wasn’t registering the USB disk after all.
On the second attempt, creating the disk on another computer, the result is a totally blank screen, and the signal to the TV being gone.
No. Nothing at all happens when starting the device with the USB disk inserted. It simply doesn’t recognize any of the USB disks I’ve tried, and I’ve tried 6 different ones.
It simply isn’t able to recognize/read any USB disk.
I almost suspect there is a power issue on that device.
I have all the vero’s since vero 1 and only problem I had was when a power supply once died.
I suspect Sam is wanting to see if a log can be taken. But next time you boot, take a good USB power supply (2A at least) and power the vero through USB (Don’t put the other power supply in).
PS: When I image a new SD-Card/USB stick, I tend to format it first!
However, I seem to be talking about some buttont to hold in for 30 seconds, but I cannot find anything of the sort on the device. Nor can I find any info about it, and I don’t remember any such details.
and only problem I had was when a power supply once died.