No problem. I kinda knew we were talking at cross purposes. 
I have tested the Nexus (CE20) nightlies and it’s the same. Only the 19.3 and previous (9.2.8) builds are working for me. It seems that it may be related to the newer kernel and recent Amlogic sound changes, but I’m getting good support from @vpeter and @Portisch. What makes me think that my hardware may be a contributory factor is that @Tim_Taylor has tested on his N2+ and he doesn’t have an issue. My N2+ is slightly crippled in that the USB3 ports are damaged, so I can’t use them reliably, although theoretically this should not affect HDMI sound playback. I can work around the problem, though, so it’s not a complete show-stopper for me.
Thought I’d give you some quick feedback - I think you have fixed it, thanks 
I have tested with various 5.1 and 5.0 files and GUI navigation sounds are played immediately after and I can switch between 5.1 and 2.0 audio files without any issues.
May I ask what has changed in the build? The logfile looks pretty similar, but I haven’t turned on any debugging.
Many thanks again for your time and efforts (and also to @vpeter).
1 Like
Hmm, an hour later and my N2+ seems to have stopped responding to my remote. I think it’s related to the continual kernel messages trying to start the USB3 hub. Here’s a snip of the tail end of dmesg.
[ 3109.071981@3]- usb 2-1: New USB device found, idVendor=05e3, idProduct=0620
[ 3109.071984@3]- usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3109.071985@3]- usb 2-1: Product: USB3.1 Hub
[ 3109.071987@3]- usb 2-1: Manufacturer: GenesysLogic
[ 3109.073845@3]- hub 2-1:1.0: USB hub found
[ 3109.074125@3]- hub 2-1:1.0: 4 ports detected
[ 3109.425791@3]- usb 2-1: reset SuperSpeed USB device number 31 using xhci-hcd
[ 3110.481765@3]- usb 2-1: reset SuperSpeed USB device number 31 using xhci-hcd
[ 3111.313698@3]- usb 2-1: Device not responding to setup address.
[ 3111.521136@3]- usb 2-1: Device not responding to setup address.
[ 3111.729118@3]- usb 2-1: device not accepting address 31, error -71
[ 3111.909194@3]- usb 2-1: reset SuperSpeed USB device number 31 using xhci-hcd
[ 3112.045087@3]- hub 2-1:1.0: hub_ext_port_status failed (err = -71)
[ 3112.225764@3]- usb 2-1: reset SuperSpeed USB device number 31 using xhci-hcd
[ 3113.409767@3]- usb 2-1: reset SuperSpeed USB device number 31 using xhci-hcd
[ 3114.449764@3]- usb 2-1: reset SuperSpeed USB device number 31 using xhci-hcd
[ 3115.649763@3]- usb 2-1: reset SuperSpeed USB device number 31 using xhci-hcd
[ 3115.788669@3]- hub 2-1:1.0: hub_ext_port_status failed (err = -71)
[ 3115.969762@3]- usb 2-1: reset SuperSpeed USB device number 31 using xhci-hcd
[ 3115.990267@3]- usb 2-1: device firmware changed
[ 3116.016623@3]- hub 2-1:1.0: set hub depth failed
[ 3116.124622@3]- usb 2-1: USB disconnect, device number 31
[ 3116.304714@3]- usb 2-1: new SuperSpeed USB device number 32 using xhci-hcd
[ 3120.641445@3]- usb 1-1: USB disconnect, device number 50
[ 3126.683448@3]s xhci-hcd xhci-hcd.0.auto: xHCI host not responding to stop endpoint command.
[ 3126.683452@3]s xhci-hcd xhci-hcd.0.auto: Assuming host is dying, halting host.
[ 3126.707666@3]s xhci-hcd xhci-hcd.0.auto: HC died; cleaning up
[ 3126.708403@3]- usb 2-1: unable to get BOS descriptor or descriptor too short
[ 3126.708455@3]- usb usb1-port1: couldn’t allocate usb_device
[ 3126.708465@3]- usb 1-2: USB disconnect, device number 3
Yes, it is.
I managed to borrow a UART adapter and got it connected, I am seeing the messages from the built-in bootloader but once it boots there is nothing, with a working system I get nothing until CE is up and I get a shell.
Is there some configuration/boot param that is needed ?
Thanks to @vpeter I have resolved my USB3 errors flooding dmesg by disabling it with a udev rule. The USB3 ports are faulty since I purchased the N2+ but I don’t use them in any case. It seems recent kernels are trying unsuccessfully to continually activate the USB3, but this workaround stops it.
Mod edit: This is the udev rule used to remove USB 3.1 hub on N2+ (file /storage/.config/udev.rules.d/01-disable-genesys-usb31-hub.rules):
ACTION=="add", ATTR{idVendor}=="05e3", ATTR{idProduct}=="0620", RUN="/bin/sh -c 'echo 1 >/sys/\$devpath/remove'"Hallo,
gibt es schon Neuigkeiten zu Uart Bridge?
Grüße
Hello,
is there any news about Uart Bridge?
Regards
I haven’t got around to it yet.
Danke und Frohe Ostern 
1 Like
Hi All,
I have kernel oops with my S905X device (Tronsmart Vega S9x) with all ng builds (coreelec 9.2.8 is rock stable).
I can reproduce it with 100% success rate:
- Open an extension what requires widewine drm
- Download chromeos recovery with inputstreamhelper.
- When download is around 50% device hangs and reboots after some seconds
Ramoops Panic Logger successfully captured the kernel oops:
ramoops logs: http://ix.io/3Wha
kodi logs pasted from gui: http://ix.io/3Wh9
Saw similar posts where they mentioned the Android 6 bootloader as the root cause.
I also have android 6 bootloader and no official upgrade. I tried to install generic images (aidan’s rom v9) with bootcard maker, but I got an android robot with red X only.
What is your opinion, is it relally related to the uboot version? If yes, are there any solution to upgrade it without usb burn cable?
Thanks,
madar
Yes, Android 6 is might the root cause. Try again with clean install and new boot media.
No, USB burn cable is not needed: coreelec:aml_burncard [Core Embedded Linux Entertainment Center for Amlogic Devices]
Already tried the bootcard maker, but I have only the original stock android 6 image. Custom roms got the Android robot + red x after booting to recovery.
Than you have to try any other firmware as CE only require the bootloader, not Android itself.
Or buy next time official supported hardware…
Can Entware be installed in Matrix without any issues?
Yes, and there can be some issues running programs from terminal. Maybe you will notice them, maybe not. Hard to tell.