Thanks
Maybe I have to try a fresh install of the nightly build with the file you supplied.
Remote Conf “/storage/.config”
remote.conf (1.0 KB)
UR02 “/storage/.config/hwdb.d”
UgoosUR02.hwdb (546 Bytes)
1 Like
Thanks
I’ll try your remote.config in the location you provided.
I won’t be able now to try this for about 20hrs from now.
I appreciate the details
The UR02 is recognized via Bluetooth as an HID keyboard and HID mouse and sends standardized HID keyboard key codes (e.g., KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_ENTER, etc.).
The Linux HID driver (hid-generic) can automatically translate these codes into Linux keycodes. This is why the remote control simply appears in the system as a normal input device.
Accordingly, you will find the event devices for the remote control under
/dev/input/,
typically e.g.:
/dev/input/event5 → UR02 Keyboard
/dev/input/event6 → UR02 Mouse
Linux basically treats the remote control like a Bluetooth keyboard and mouse.
The hwdb.d file provided by crazyturk is used to remap HID scan codes to Linux key codes before they are processed by applications.
On a normal Linux system, such files would be stored under
/usr/lib/udev/hwdb.d/
or
/etc/udev/hwdb.d/
and then execute:
systemd-hwdb update
udevadm trigger
However, you only need to do this if you want to change the key assignment at the system level. This is usually not necessary for the UR02, as it already sends standard HID keycodes that are directly recognized by Linux and Kodi.
Regarding your actual problem:
If the remote control continues to display a red LED in Bluetooth mode, it sounds more like
an incompatible firmware.
Have you tried pairing the remote control via Bluetooth under the original Ugoos OS?
I would proceed as previously suggested:
Install/Reinstall the latest firmware from Ugoos
Then perform a clean reinstallation with the current CoreELEC Nightly build.
Regarding remote.conf:
The remote.conf file is only used by the IR driver (meson-remote).
When the UR02 is connected via Bluetooth, key inputs are processed via the Linux HID subsystem and the remote.conf file plays no role in this.
However, it can still be helpful because it allows you to continue controlling the box via IR if Bluetooth is not working.
For comparison, I tested connecting my AirPods via Bluetooth, and they worked immediately without any problems under CoreELEC. Therefore, I suspect a problem with the Firmware.
1 Like
Today I wiped my SDcard, installed today’s release of the nightly build, copied the remote.conf file into the correct location, performed the Bluetooth connection to my UR02 remote.
It’s no different to before, Bluetooth is flaky, system says it’s connected, I have no fly-mouse function, every button press is an IR function.
Bluetooth internal dongles are known not working reliable. Get a USB dongle:
I find it strange that several identical systems with untouched new installations exhibit different behavior when it comes to Bluetooth connections, but Portisch knows much more about this than I do.
What I would try to keep it as simple as possible and save time and money:
- Firmware update of the remote control itself. (https://ugoos.com/download-file?id=290)
- Test the remote control under the Ugoos OS (Android 14).
If you still can’t establish a stable Bluetooth connection, make use of your warranty or follow Portisch’s solution.
1 Like
If you do not place the UgoosUR02.hwdb file in the required location, Bluetooth will not work.
I use the UR02 controller with both the AM8 and AM9 Pro via Bluetooth.
1 Like
Hi,
I haven’t been around for a while and I’d like to ask if CoreELEC has been fixed for running on Ugoos AM9s with firmware 2.x, or is it still the issue that it allow video playback with firmware 1.x only?
I’m asking because Ugoos support asked me to update the firmware to the latest version. I reported the device randomly restarting to them. I enabled port monitoring on my router with notifications on my Android phone, and I can clearly see that the device is disconnecting from this port completely randomly: sometimes twice a day, sometimes only once every 3 days.
Yeah mate, update it. The AM9 works great with the latest nightly build and latest firmware
Thanks,
Firmware upgraded to 2.0.5,
CoreELEC updated to 20260314
Video playback works.
All good. Now fingers crossed to not see random restarts.
CoreELEC team is doing a really great job here. Thanks a lot, guys…
2 Likes
I think 206 is the latest, don’t know if there is any improvement. Might want to update it anyway
Hi everyone,
Following the discussion about the GUI rendering artifacts caused by the GBM libMali backend on the S905X5 Amlogic SoCs, I decided to take action and contact Amlogic to request a FBDEV libMali for Valhall GPUs.
I sent an email to support@amlogic.com, also CC’ing Ugoos support, explaining the issue and requesting either a FBDEV libMali binary or access to the relevant source code.
I would encourage other AM9/AM9 Pro users to do the same ; the more requests Amlogic receives, the more likely they are to act on it. I’ll keep this thread updated if I get a response.
Thanks to the CoreELEC devs for their outstanding work on this platform!
3 Likes
FYI
Update on my Ugoos Bluetooth journey
1 Like
Nightly 20260318 should have fixed rebooting from CE to CE when using uSD card.
USB needs more investigation.
6 Likes
Great, the issue with CE restarting from the SD card has been resolved.
Thank you, CE team
1 Like
14 posts were split to a new topic: UPnP not working anymore
I’m trying to install CE for the first time on my Ugoos AM9. The installation seems to get stuck in an infinite loop. Amlogic S905x5 logo appears, than “CE New Order” logo appears, then the screen goes dark for like 30 seconds and same thing repeats forever. I tried with alpha3, than also with the latest nightly build, same… Any idea?
Try installing the latest Ugoos firmware (2.0.6) and also using the s6_s905x5_ugoos_am9 dtb file.
1 Like
Oh really? I was even thinking of downgrading to Ugoos firmware version 1.2.0. I’ll try updating to 2.0.6.
Do you recommend the alpha version or nightly?