Not sure if you were replying to me but my install was a fresh install, obviously it’s auto-updated a lot since the original install though.
Thank you, and I confirm the box is working again.
There’s just a problem with the reboot.
There is green tint in DV and HDR . Someone has noticed too? Is it because of wrong tone mapping in NO?
No, it’s because you miss something in your setup.
No log - no error…
Follow the guides available on forum.
I noticed a problem that the built-in USB 2.0 hub is not detected randomly on the Ugoos AM8 PRO device: VIA Labs, Inc. USB2.0 Hub.
Often, after running lsusb, it only shows USB3.0 detection:
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
All you need to do is restart CoreElec (once or sometimes several times) and the USB2.0 hub is detected along with the device connected to it (radio remote control receiver):
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub
Bus 003 Device 003: ID 4842:0001 HAOBO Technology USB Composite Device
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
I rule out a hardware problem because:
- on the original Firmware v. 2.0.2 (Android 14) and earlier, this never happens,
- it worked correctly on old versions of CoreELEC NO 22.0-Piers, the problem appeared after the release of alpha1, I suspect it is related to the change of the kernel version from 5.15.153 to 5.15.170.
Has anyone encountered this problem and has a solution for it?
1 Like
I also have the same problem on my Ugoos AM8. After a restart it no longer recognizes the Logitech Unifying receiver. Sometimes I have to start it several times for it to work, sometimes it doesn’t work at all. The only thing that helped was connecting a USB OTG cable with USB C to USB A female on the back and connecting the unifying receiver there. The error only occurred since switching to the new kernel 5.15.170.
1 Like
@Portisch - have you had any time for further investigation on this? I have been downloading nightlies and checking change logs for any mention.
Joe
Any update on a fix for shutdown and restart issues on SC2 platforms. The issue started a few weeks ago and even with the latest nightly it just hangs after switching off the display through CEC (both power off and reboot options). Have to power cycle to start it again
Thanks!
Same problem with s4 (s905w2) platforms.
No, because of this: https://kodi.wiki/view/Settings/System/Audio#Output_configuration
Because this makes no sense for me.
Why to adjust the number of channels when using any other option than “fixed”?
And I think this solved it for you and the channel mapping did work than!?
This is just a crude “workaround” - it means that passthrough no longer works, so i can’t get DTS-HD Master Audio or Dolby Atmos to my AVR without manually changing audio settings. CE-NG automatically handles varying numbers of PCM channel layouts.
NG is EOL! Use NO! 
Then you will need to debug and make a PR by yourself.
My TV only support PCM 2.0, no LPCM as it have only HDMI2.0.
So I can’t test anything.
One day there will be an Upgrade…
You obviously haven’t been following this thread. I’m fully aware of the direction of CE development. The channel mapping issue is the only thing holding up my full time adoption of NO (from NG).
Ok - when you asked for a set of test files I assumed (obviously wrongly) that you were in a position to test modifications to the channel mapping. Thanks for replying. You may be right in that I will have to try and build a version for myself to test. It’s just a pity that essential basic multichannel sound support is not handled and that such effort is put into hacks to support the likes of Dolby Vision etc. which at best are “nice to have” features.
You do know different users want different things 
Of course, Peter. But I consider the 5.0 sound issue to be a bug in NO (as it works in NG), not a feature or enhancement.
Yes, until I realized my TV only support ARC, not eARC.
So I can not do any testing yet.
Passthrough is used mostly of the time and users - and there are no issues up to 8 channels.
1 Like
Just an FYI, I downloaded your samples and tested them here with my AV receiver and 5.1 setup. And I’m experiencing the same problems, center, quad and surround50 playing incorrectly with missing/silent channels or mixed up channels in some cases. The other files playback fine.
1 Like
I did find a fairly effective workaround, you can use the add-on call Audio Profiles.
I configured 2 profiles one with Fixed 5.1 layout and the other with Passthrough and Optimised layout, and using that add-ons auto profiles enabled the fixed one for music playback, and Passthrough for everything else.
Edit: Fixed does mean you are forced to resample the output which is a shame, would be good to see this issue resolved properly.
1 Like