Homatics Box R Lite 4K

i am trying to find a method to launch coreelec on this tv box device.
if anyone know can help me:
Manufacturer​: SEI Robotics
SoC: Amlogic S905Y4
GPU: ARM Mali-G31 MP2
2GB RAM - Storage 8GB
Only 2 USB 2.0 ports, No hard key to reset and no memory card slot

i tried using reboot.to.LibreELEC apk ,
When I open the app and select reboot to libreELEC , the device doesn’t reboot

And what happens if you run the app and then reboot Android? With USB stick attached with correct dtb.

SEI Robotics make many devices which don’t support CE TiVo, ONN, Chromecast come quickly to mind. You are also hijacking this thread.

Thats not Homatics box R 4k plus. Wrong topic.

Correct. maybe i was wrong
My machine is this.
Sorry for mistakes

That is not the 4K Plus with the S905X-4k not sure if it can boot CE.

1 Like

We can check with Homatics if there is support or not. As it’s a different SoC than the Plus version it will require another DT.

1 Like

First tests show that the Homatics R Lite 4k boots normally using s4_s905y4_2g dtb. The device has a reset button and a USB stick was used. microSD booting is till untested. Wifi and bluetooth will need some work and aren’t working at the moment.

2 Likes

s4_s905y4_2g dtb working with Homatics Dongle G 4K , bluetooth remote BT21 also working but it need to add hwdb

evdev:input:b0005v0957p0019*
KEYBOARD_KEY_c0041=enter
KEYBOARD_KEY_c009c=up
KEYBOARD_KEY_c009d=down
KEYBOARD_KEY_c0030=s
KEYBOARD_KEY_c008d=e
KEYBOARD_KEY_c0221=o
KEYBOARD_KEY_c0077=a
KEYBOARD_KEY_c0078=l
KEYBOARD_KEY_c0079=n
KEYBOARD_KEY_c007a=q
KEYBOARD_KEY_c0096=v
KEYBOARD_KEY_c01bb=z

this hwdb is different than the default one in repo files (changed p0006 to p0019) without this change the OK(enter) button not working

Wifi scanned when changed regulatory domain to global but cant connect > and now not showing any wifi networks its weird

I will add this remote to a file.
Is this some variant of B21 remote?

A bit late, sorry, but yes it is. It has a “person” button, located left from microphone button. Homatics users that have this remote (only came with Dongle 4k that has Google TV on it), have the problem that the shortcuts (Netflix etc.), don’t work. I tested that with that remote, and indeed, didn’t work.

So it is another variant for the B21 (and B25) remote; Future Google TV devices may include a User Profile button on their remote | AFTVnews

Hi, i am planning to purchase the box r lite 4k since there is a discount sale going on for it on a local ecom website. Is the ethernet port working with coreelec on this device? Anybody have tested?

Just got the device. Booted coreelec NE with a sandisk endurance microsd using reset hole method. dtb used is s4_s905y4_2g.
Wifi and ethernet are working. bluetooth does not. Need to do more testing, will update soon.
FYI device was already on android 12

1 Like

Can someone point to why bluetooth might not be working. I have attached android and coreelec dts(s4_s905y4_2g) along with dmesg.
dmesg.txt (95.7 KB)
android.dts (114.6 KB)
coreelec-original.dts (80.5 KB)

Update: bluetooth works with s4_s905y4_2g in coreelec-no nightly. i copied that dtb to ne installation and it worked somehow
Got bluetooth working with NE dtb itself with little modifications. Tested with homatics bt remote. Attached the file for anybody using this device.
dtb.img (66.1 KB)

Hi, Thanks for posting about the homatics lite R box. I have purchased same box which got amlogic s905y4 with 2 GB RAM and 8 GB storage. After plugging in the power and network cable, pairing the Remote, the box started with Android 14 upgrade automatically. Since I was not knowing the Android 14 vs Coreelec issues, I have waited patiently, let the system to update and reboot. Post reboot inserted the microSD prepared using rufus and respective dtb file (renamed to dtb.img). When I am pressing the reset button using the toothpick and powering the box by attaching the adapter cable, I am receiving Android recovery message. No CE logo or any activity at this stage. If I continue to hold the button, getting USB burning mode. If I press the reset button at this stage the box boots ino Android14.

I have already tried different USB sticks of Sandisk brand inserted in USB2 as well as USB 3. I am unable to see the coreelec at all. I have even tried the reboot to coreelec app from the stock android. Nothing happens after the reboot. I have tried different versions of the CE Nightly namely no, ng and ne. No success. Do I have to try any specific version of the image file?can you let me anything else is required?
Note: Recently I have tried CE on a China based box that got Amlogic S905X4 and even installed it from MicroSD to internal emmc of that box. It worked successfully. So I know how to rename the dtb as well as the reboot procedure.

Here is the state after my last post. I have bought same device again since the cost of a Google certified device is more justifiable than the random PCR android boxes that cost more than this device in my place. This time I have prepared the MicroSD card with NE image that is recommended by CE and followed the reboot instructions. I have not booted the box into Android at all. After USB Burning mode the prompt got changed and upgrade window popped for few seconds and then the CE logo started appearing. Some command lines started rolling down and the box booted into CE successfully.

With external USB based keyboard connected, I could get the Bluetooth Remote paired. Disabled all the software update settings to Manual within CE to prevent any future problems.

In previous box after the “USB Burning mode” it will be blank and will boot into Android. Now the stock Android (version 12) the box came with allowed the CE to boot.

The Audio via HDMI with default setting is working fine. However I would like to use this box as headless so tried to modify the Audio setting with PCM Analog port and testing Audio/music. Though the Analog option is selected, the Audio is routed via HDMI only and no sound is played via the 3.5mm/Analog port. I tried all the possible settings that appears under System → Sound, still no sound. Do I have to modify any other settings or use different driver or configuration? Can you please help?