Posts by sam_nazarko

Quote from frakkin64

I figured that would be coming, CE is ending support for S905x devices after 21 (at least that is the latest announcement, I think they were trying to end it with 20), so expecting it is coming to a close eventually on the OSMC side as well.

That's why part of my interest is in mainline and v4l2 video pipeline (unfortunately that's a slow road for Amlogic), but I boot Armbian as well on the device using the stock bootloader and modified boot scripts (similar to what LE does), just need some postinst triggers on the kernel to build a uImage (since they dropped that). The other part with CE is mainly to get access to bleeding edge Kodi with a fully working video playback. There are options for folks to repurpose the device, but would be nice to get mainline u-boot eventually (and then reformat the partition and install there). Chainloading mainline u-boot works fine, it's all the bl2 and bl3x bits.

Hopefully that will help folks experimenting with the toothpick method from having their eMMC install corrupted, it's fairly easy to recover using the recovery media. It's never been a big deal for me.

I'll try and keep things going for long as possible, but Kodi has become more resource hungry since we released the Vero 4K in 2017 and 7 years and counting of support is a good run, particularly as we only promised 5. Hopefully by the time we do stop supporting it the upstream state of the art will be in good shape for it to pick up.

The 6.6 AMLogic vendor kernel makes good progress with V4L2 but it is quite tightly coupled to GStreamer as that is the focus with RDK.

Thanks for the suggestion to improve the bootloader and corruption issue. I don't normally change environment variables on a working system on 4K/4K+, so the improvement will only be seen for those that conduct fresh installations. With that said, it's better than nothing

I will send some hardware to chewitt.

Hi frakkin64

Thanks for your comments.

I was only made aware of this post now.

I am going to support Vero 4K and 4K + for the v21 series at a minimum. See https://osmc.tv/2022/10/vero-4…turing-updates/.

It just won't get new features like Dolby Vision tonemapping which recently became available for Vero V (https://discourse.osmc.tv/t/testing-vero…onversion/96809).

>This, in my opinion, is because they (OSMC) didn't modify the default bootloader script to remove the "wipeisb" & decided to use multiple Android partitions in an LVM group.

Thanks for the report. This is fixed in this commit:

[package] [vero3-bootloader-osmc] Fix an issue where 'toothpicking' t… · osmc/osmc@4b64718

…he device renders the system unbootable due to instaboot partition being wiped. https://forum.libreelec.tv/thread/27727-liberelec-on-the-vero-4k/…

github.com

and will be part of the next stable update. We don't use LVM anymore on Vero V going forward.

I will have a chat with chewitt and ascertain what hardware he has and what to send him and see what is available. I know that he was responsible for upstreaming DTS support for Vero 4K + to the kernel.

Cheers

Sam

As discussed, I will send you a new remote receiver once back from my trip.

Upon receiving the USB dongle, you'll need to hold the Home and OK buttons for a few seconds after connecting the receiver to your Pi. This will pair the remote with the new receiver.

If you have any other issues, just reply to the support ticket which you opened rather than here as this is not a LibreELEC issue.

Cheers

Sam

Quote from Shivan

Hi Sam,

Firstly, I have to say I am really impressed with your dedication to customer support!

Secondly, I didn't downgrade LibrELEC, but I connected the dongle to my PC, and as you predicted, it didn't work. I also connected it to a different USB port on the Raspi, and the result is the same:

Code

[60044.193786] usb 1-1-port1: attempt power cycle
[60044.786729] usb 1-1.1: new low-speed USB device number 111 using xhci_hcd
[60044.806083] usb 1-1.1: device descriptor read/8, error -32
[60044.929098] usb 1-1.1: device descriptor read/8, error -32
[60045.553392] usb 1-1.1: new low-speed USB device number 112 using xhci_hcd
[60045.572445] usb 1-1.1: device descriptor read/8, error -32
[60045.696195] usb 1-1.1: device descriptor read/8, error -32

Same on my Vero:

Code

[  111.586583] usb usb1-port2: attempt power cycle
[  112.354675] usb 1-2: new low-speed USB device number 72 using xhci-hcd
[  112.385194] usb 1-2: device descriptor read/8, error -71
[  112.534859] usb 1-2: device descriptor read/8, error -71
[  113.304684] usb 1-2: new low-speed USB device number 73 using xhci-hcd
[  113.335845] usb 1-2: device descriptor read/all, error -71
[  113.335893] usb 1-2: the parent's name is usb1
[  113.335946] usb usb1-port2: Device no response
[  113.335978] usb usb1-port2: unable to enumerate USB device
[  114.144745] usb 1-2: new low-speed USB device number 74 using xhci-hcd
[  115.045324] usb 1-2: device descriptor read/all, error -71
[  115.914698] usb 1-2: new low-speed USB device number 75 using xhci-hcd
[  116.815672] usb 1-2: device descriptor read/all, error -71

Display More

And thirdly, of course I would be happy to receive a replacement, but from a technical point of view, it really seems to be a huge coincidence if the dongle stopped working exactly during the update, because I initiated the reboot for the update with the remote, and two minutes later, it didn't work anymore. So if there is any additional diagnosis I could do from my Windows desktop or one of the other devices, I would be happy to help, but if you think the diagnosis is clear, just let me know and I will contact your support.

PS: one thing I haven't mentioned so far is that I'm using the "HifiBerry" addon board on the Raspi. But that shouldn't cause USB problems in my opinion...

Display More

You're welcome.

The dongle is sensitive to spikes in voltage -- so if your power supply is not stable, this could have caused issues with the dongle.

I suggest trying an older version as suggested by CvH and if the problems remain, email me at [email protected] and I will take care of this for you.

Sam

Hi

Sorry to hear the remote is not working as expected.

Just to clarify: did you downgrade your LibreELEC version and did this make the dongle work again? Otherwise the dongle may have simply developed a fault at the same time you upgraded your system.

I'd recommend trying the remote dongle in another device (such as your PC). You should be able to scroll a web page with the up and down arrow keys if it's functional.

From what I can see, the dongle appears to be faulty and if you email [email protected], we can rectify this for you.

Cheers

Sam