I’m pretty sure soon AM9 will be fully supported by you as it is really powerful piece of hardware
I’m going to start testing CoreELEC after I played a while with Android installed there and definitely CoreELEC is the must to have here instead of Android
Good luck with adding AM9 to the list of devices tree…
Just some offtop,I was trying to boot emuelec and armbian and it turns out,the max kernel version they support is 4.9 and AM9 runs on 5.10+,so they won’t work until devs decide to add never devices support.
There is an EmuELEC (EE-NO - kernel 5.15) build that supports newer post 4.9 kernel SOCs like the s928x, A311D2, s905w2, etc, but it doesn’t currently support the s905x5 or s905x5m as you said.
The box is not 100% unmodified since CE won’t load on a virgin system. I guess you could reflash the Ugoos firmware but I suspect you will see the same issue. The AM9 is relatively new so you simply didn’t give Android a through test with the same files. It will be different then other Android Kodi players you have used in the past and there is no direct comparison.
Any chance getting 192khz flac or wav files pass-through to receiver? I tried different settings,still only 48khz pcm on receiver,source files are 100% 192khz and my receiver is configured properly,dts ma works fine though.
I found that the device would allow me to roll back to original firmware. I did this tested and the audio delay is still present. turned on AFR, still get the delays, Kodi settings now have rate switch and frame sync on, it has fixed the issue but….
I am looking forward to when this hardware is properly/fully supported.
Does the ceemmc tool work on this box? I am asking because other devices from this generation seem to have issues mounting the Android 14 data partition.
Also, is there any information regarding a J variant of the S905X5 SoC that supports Dolby Vision that ugoos can use on an upcoming pro version?
Did anyone manage to have the UR02 working with the nightly 22? I tried with the remote_ur-02.conf I found, but totally unresponsive. Bluetooth detected and paired, no reaction whatsoever for any button. The first time, it was like a button got stuck sound, but now nothing. Tried resetting and listening to cat /dev/input/event9 in bluetoothctl, it doesn’t see anything while pressing a button.