Report about Amlogic S905X4 HK1 RBOX X4

Anyone here use the bluetooth remote ugoos ur-01 with CE. After pairing the device, everything works but the OK button did not (it works fine on Android).

Copying the remote.conf for UR-01 to Configfiles folder did not work either.
Here is my remote:

Any idea on this problem?

Thanks a lot.

This file is run in infrared mode, not related to bluetooth.
please use infrared mode for Ugoos UR-01

There’s a way to achieve this with the Bluetooth remote. There are posts scattered here and other forums of how to do it using evtest and .hwdb file.
I’ll post here later a small how to.

I wrote the configuration file for this remote myself and all keys but for the mouse and voice control should work. Maybe go through the troubleshooting steps (especially step 2) and see if that gets things going?

Quick update: I tested the file from the repo on Ugoos AM7 and it works as intended.

@hungphutho Thanks for quick reply but it did not address the issue as the UR-01 is in fact the Bluetooth remote. Is there any way to toggle the IR mode, if yes, we still have the problem with OK button in BT mode though.

@Vasco: Thanks for the hint. I have quite limited knowledge with remote and CE. Looking forward to your “HOW TO”.

@ Betatester: Thanks for the owner of very helpful config file for CE community (with that i was able to get the stock IR remote working). I ll try the troubleshooting steps and let you know. Believe that if it works with Ugoos AM7 then should be ok with Ugoos x4 pro.

@All: Thanks all for your always great support.

thanks for your suggestion , i have debugged the data for you which can guide someone who needs to do it

cat /proc/bus/input/devices
I: Bus=0005 Vendor=005d Product=0001 Version=0003
N: Name="UR01-BLE"
P: Phys=a0:67:20:e0:6f:47
S: Sysfs=/devices/virtual/misc/uhid/0005:005D:0001.0001/input/input6
U: Uniq=20:19:70:00:23:45
H: Handlers=sysrq kbd mouse1 event6 
B: PROP=0
B: EV=10001f
B: KEY=3007f 0 0 0 0 483ffff 17aff32d bf544446 0 0 70001 130ff3 8b17c007 ffff7bfa d9415fff febeffdf ffefffff ffffffff fffffffe
B: REL=143
B: ABS=1 0
B: MSC=10
cd /etc/udev/hwdb.d/
nano 10-ur01.hwdb

Content

evdev:input:b0005v005d*
 KEYBOARD_KEY_c0041=enter
udevadm hwdb --update
udevadm trigger -s input
reboot

ALL KEYS ON UR-01

Event: time 1657643216.407118, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0030
Event: time 1657643216.407118, type 1 (EV_KEY), code 116 (KEY_POWER), value 1
Event: time 1657643216.407118, -------------- SYN_REPORT ------------
Event: time 1657643216.619090, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0030
Event: time 1657643216.619090, type 1 (EV_KEY), code 116 (KEY_POWER), value 0
Event: time 1657643216.619090, -------------- SYN_REPORT ------------
Event: time 1657643231.953581, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0042
Event: time 1657643231.953581, type 1 (EV_KEY), code 103 (KEY_UP), value 1
Event: time 1657643231.953581, -------------- SYN_REPORT ------------
^[[AEvent: time 1657643232.110577, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0042
Event: time 1657643232.110577, type 1 (EV_KEY), code 103 (KEY_UP), value 0
Event: time 1657643232.110577, -------------- SYN_REPORT ------------
Event: time 1657643233.495497, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0045
Event: time 1657643233.495497, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1
Event: time 1657643233.495497, -------------- SYN_REPORT ------------
^[[CEvent: time 1657643233.651609, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0045
Event: time 1657643233.651609, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0
Event: time 1657643233.651609, -------------- SYN_REPORT ------------
Event: time 1657643234.249618, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0043
Event: time 1657643234.249618, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
Event: time 1657643234.249618, -------------- SYN_REPORT ------------
^[[BEvent: time 1657643234.405625, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0043
Event: time 1657643234.405625, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
Event: time 1657643234.405625, -------------- SYN_REPORT ------------
Event: time 1657643234.969681, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0044
Event: time 1657643234.969681, type 1 (EV_KEY), code 105 (KEY_LEFT), value 1
Event: time 1657643234.969681, -------------- SYN_REPORT ------------
^[[DEvent: time 1657643235.181686, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0044
Event: time 1657643235.181686, type 1 (EV_KEY), code 105 (KEY_LEFT), value 0
Event: time 1657643235.181686, -------------- SYN_REPORT ------------
Event: time 1657643256.132325, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0041
Event: time 1657643256.132325, type 1 (EV_KEY), code 353 (KEY_SELECT), value 1
Event: time 1657643256.132325, -------------- SYN_REPORT ------------
Event: time 1657643256.133301, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0041
Event: time 1657643256.133301, type 1 (EV_KEY), code 353 (KEY_SELECT), value 0
Event: time 1657643256.133301, -------------- SYN_REPORT ------------
Event: time 1657643269.028747, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0224
Event: time 1657643269.028747, type 1 (EV_KEY), code 158 (KEY_BACK), value 1
Event: time 1657643269.028747, -------------- SYN_REPORT ------------
Event: time 1657643269.029721, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0224
Event: time 1657643269.029721, type 1 (EV_KEY), code 158 (KEY_BACK), value 0
Event: time 1657643269.029721, -------------- SYN_REPORT ------------
Event: time 1657643269.754729, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0223
Event: time 1657643269.754729, type 1 (EV_KEY), code 172 (KEY_HOMEPAGE), value 1
Event: time 1657643269.754729, -------------- SYN_REPORT ------------
Event: time 1657643269.911722, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0223
Event: time 1657643269.911722, type 1 (EV_KEY), code 172 (KEY_HOMEPAGE), value 0
Event: time 1657643269.911722, -------------- SYN_REPORT ------------
Event: time 1657643271.093813, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0040
Event: time 1657643271.093813, type 1 (EV_KEY), code 139 (KEY_MENU), value 1
Event: time 1657643271.093813, -------------- SYN_REPORT ------------
Event: time 1657643271.249783, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0040
Event: time 1657643271.249783, type 1 (EV_KEY), code 139 (KEY_MENU), value 0
Event: time 1657643271.249783, -------------- SYN_REPORT ------------
Event: time 1657643272.746866, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00ea
Event: time 1657643272.746866, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 1
Event: time 1657643272.746866, -------------- SYN_REPORT ------------
Event: time 1657643272.948858, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00ea
Event: time 1657643272.948858, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 0
Event: time 1657643272.948858, -------------- SYN_REPORT ------------
Event: time 1657643274.591876, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e9
Event: time 1657643274.591876, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1
Event: time 1657643274.591876, -------------- SYN_REPORT ------------
Event: time 1657643274.793904, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e9
Event: time 1657643274.793904, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0
Event: time 1657643274.793904, -------------- SYN_REPORT ------------
Event: time 1657643277.708005, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0221
Event: time 1657643277.708005, type 1 (EV_KEY), code 217 (KEY_SEARCH), value 1
Event: time 1657643277.708005, -------------- SYN_REPORT ------------
Event: time 1657643277.708942, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0221
Event: time 1657643277.708942, type 1 (EV_KEY), code 217 (KEY_SEARCH), value 0
Event: time 1657643277.708942, -------------- SYN_REPORT ------------

10-ur01.hwdb (49 Bytes)

Thank you, you saved me some work tonight!

Hello everybody,

I don’t use CoreELEC yet, but since last year I started looking at the system due to my interest in EmuELEC.

So after following this topic I decided to buy a Vontar HK1 RBOX tv box and installed the nightly version 19.5 on it, with 4GB dtb, and it worked.

And on 07/08/2022 the trial version of EmuELEC (4;6) was released. I installed it, using the same dtb (which was not included in the device tree folder of that version) and it also worked perfectly.

I thank the CoreELEC and EmuELEC teams and everyone here who made this possible.

Thanks all for the helpful support. My bluetooth remote (UR-01) works fantastic now :slight_smile:

3 Likes

Wellcome onboard. The owner of this thread has been reporting COREELEC

Hi

I am looking to buy a device with S905X4 to use with Coreelec. It seems the main issue is that some devices have a yet not working gigabit chipsets. I would like to avoid it, as my setup uses Ethernet.

I would appreciate if @clarkss12 you could post where you bough yours as your gigabit Ethernet is working. Also, I would also appreciate if @emveepee , @siri25920 , @Kill_Bill , @kostas912 and @bululu you guys could share were you bought yours, as your gigabit Ethernet is not working.

Seems to me the new purchases all have the new gigabit, not yet working, chipsets, but it is worth a try.

Thanks

With S905X4 we support the Ugoos (AM7 and X4) and the Buzztv X5.

1 Like

Hi:

Mine worked as well from, 1Gbit Ethernet with 64GB Rom.

Hope it helps and good luck!

1 Like

Mine was Amazon, seller Susay. I suspect that they are purchased in batches and the batch rather then the dealer will be what matters.

1 Like

All those models are way over 100usd, compared to less than half the price for other brands. Apart from reputation and less probability of being scammed with a fake chipsets, are there any technical differences?

Also, I understand the benefits of more RAM, but I am ignorant about the advantages or tradeoffs of the amount of ROM. What is the deal with 32 vs 64 vs 128 GB models?

Yes, absolutely. Still worth trying to catch one from a 1 Gigabit working batch. I understand there are no guarantees, just trying to increase the odds of getting lucky.

I have a HK1 BOX 4G+128G (S905X3) and a HK1 RBOX X4 4G+32G (S905X4) so I’m not sure if this is the problem only on X4 or on all similar 32G devices:
On the box that comes with 32G eMMC, SDXC (>32G, <=2T) cards can’t be recognised, and Android/CoreELEC kernel will flood the kmesg with corrupted SD controller infos, I’ve tested this with 4 different Netac 64G cards, 1 Samsung 128G card and 1 Samsung 256G card and all result in the same error. And since these cards can’t be recognised by the kernel (u-boot still can), you can’t boot CoreELEC on a 32G model with a SDXC card. But this is not a big problem if you only use a SDHC card as boot drive and won’t store much data on it.
On the box that comes with 128G eMMC though, there’s no problem using SDXC cards, all of the previously mentioned SDXC cards work on it, both in u-boot and in Android/CoreELEC, kernel is happy with all of them.
My guess is they cheap out the MMC controller on all 32G models, and the controller can only work with SDHC cards (2G-32G) as a result

On my 64GB version I added an 128GB card which CoreElec runs.

Please remind buying “cheap devices” may result in some not working features and maybe the will not be working ever. Like there is already a s905x4 box with not supported eth chip so gbit lan is not usable. Don’t remember which one.

A lot of users wasted money and time in past on such cheap boxes… Just search the forum about the X… devices.

True, I personally wanted a Shield kinda old, and UGOOS is a brand I respect for supporting their products but was close to the shield’s price. I wanted a decent box with AV1 support, took a chance and went with the HK1 X4. The Tanix X4 is another box I tested (on android) and liked.

In China here you can get a Ugoos X4 directly from the manufacturer (since Ugoos is a China company, and most of CE’s partners also are) with 370 CNY + 13 CNY shipping, that’s only ~56.62USD. Never thought the product will get that much more expensive after exporting…

For me, I buy these cheap boxes for tinkering and development so I can worry less after burning the device (one for only ~200CNY, that’s ~29.6USD), but not for actual usage. I got other more expensive and robust devices for my acutal media and entertaining usage and I would not recommend buying these cheap boxes for your main CE/EE device.

1 Like