Thank you @smvzombie
1 Like
Hi,
I Have an Homatics R 4k Plus, rosegold/white color, firmware 12.8.5394.
I used file : CoreELEC-Amlogic-ng.arm-21.1.1-Omega_nightly_20240827-Generic.img.gz
And device tree : sc2_s905x4_4g_1gbit.dtb
First start without problem, wlan and wifi works.
Since then, there have been several nightly updates and I no longer have ethernet functional, whether with sc2_s905x4_4g_1gbit.dtb or sei.
Only the 2.4GHz wifi works.
Strange, right? It seems to me that these issues had been resolved since 
boot to Android and back to CoreELEC and ethernet will work.
fresh install.
Changelog (20240924) Mon Sep 23 19:39:11 2024 +0200 – Amlogic-ng: enable Motorcomm YT8531 phy (Peter)
I know this trick but it’s far from practical…
But I didn’t have any issues with the first nightlies unlike other people.
And now that they’ve fixed the problem for other people, it’s at my place that it’s not working xD
I will try to do a clean installation with the latest release and another one with the old version that worked 
Go back and try all the nightl builds to see exactly when it failed your case.
We don’t own all possible devices to check ourself.
That’s what I was thinking of doing, yes, to properly reinstall the first one that worked and then add them one by one to see from which one it stopped working.
In addition to not being able to test all the cases, if the manufacturers change the components inside during production, it becomes even more complicated…
To me, not getting ethernet at first, was at that time resolved by changing from the ‘sei’ dtb to the ‘1gig’ dtb, as recommended at the time.
After this I had ethernet connection BUT at that time I booted to Anroid first (overlooked replugging usb stick…).
Ethernet now indeed worked, after having inserted the usb stick and booting to Elec via the .apk…
Now I tried the provided test .dtb by vpeter and shortly after copied the ‘sei’ dtb, extracted from the new images (by vpeter).
After this fix I changed back to the nightlies, using the same ‘sei’ dtb from the test images.
I am unsure if later updates (nightlies) replace that dtb but in your case, start with a working situation.
Maybe the step of replacing the ‘1gig’ dtb, after having gained ethernet, back to the ‘sei’ dtb, extracted from the test image, was needed before actually updating the image itself.
To be clear. No need to boot Android in between after the fix from ‘sei’ → ‘1gig’ (boot to Android, forgot usb) → ‘vpeter test dtb’ → ‘sei’ (extracted from vpeter test image).
The last step for me was manual update to latest nightly.
For troubleshooting, use the ‘paste’ command as used by me (ssh to elec, use wifi to connect) to be able to share the provided URL, already uploaded for review.
A post was merged into an existing topic: Homatics Box R 4K Plus
A post was merged into an existing topic: Homatics Box R 4K Plus
I followed all of these instructions and everything is working great except the remote, I have the dune box and downloaded the remote.conf but I don’t have any storage folder on my USB to put it in.
A post was merged into an existing topic: Homatics Box R 4K Plus
The installation instructions mention that, but how do you get that firmware version if it didn’t come with it? I don’t have that number listed anywhere in the “About” panel.
in LGTV setting
picture → Aspect Ratio Settings → Just Scan
If you turn this feature On, you can view the content in the aspect ratio that is in the broadcast signal or content source. If the edge of the screen is not clean, please turn it Off.
anyone else having horrible playback on dv p7 +fel + true hd, cant post log cause they get too big or the device freezes while showing a single color
In solution you linked, you have created .toml but you are not using/loading it.
In your rc_maps.cfg you are doing
meson-ir * KEYMAP
to load .toml you would need to do
meson-ir * KEYMAP.toml
How did you manage to get shutdown and boot bact to elec working ? Is it through CEC or Nokia remote ?
When I posted that I was not aware of not actually adopting .toml.
In hindsight it was simply using the other solution where I seemlingly did not realize that this was always the configuration I used.
I aimed to get the Nokia 8010 remote to work besides the native TV remote, which works via CEC out of the box.
Also, I fear I need to nuance the working of the power off-on when within CoreElec, as this seems to be linked to CEC wakening the 8010.
The powerbutton only works when having shutdown within Android.
I did not yet find the energy to see why waking the CoreElec session works via CEC (through receiver/tv) and how to map a key to do the same, fe forcing the receiver to wake and let it wake the tv/mediabox.
CEC is always tricky so for now I just boot to Android within CoreElec and shutdown from there (as it now will wake with powerbutton of the 8010 remote).
Would it be possible for you to post your CEC settings from coreelec (Input → peripheral → CEC) ? And also how exactly are you closing coreelec, are you using shutdown button or simply pushing turn off on tv remote ?
I cannot get it to work 
Excuse the delay. I do not get any notifications…
I did not change any default setting in (Input → peripheral → CEC).
I recall vaguely having read that for the 8010. activation after shutdown was tricky (I mention it to let you know you are likely not an idiot when it will not work as you intended it to).
As I read/captured the output from the 8010 remote (by pressing all the buttons, using provided shell commands), this also allows using KeyMapper to change the functions (within CE).
I had to assign some functions to the color-buttons to get the menu-interactions to show.
Shutting down via the power-button works by default, within CE, but I did not validate the route.
It could be I simply initiate the CEC command to sleep/shutdown to the receiver, which will shutdown the TV and in the end put the 8010 in sleep mode,
That would also explain why forcing the source on the receiver, to the 8010, actually wakes it (over full shutdown).
As validating/testing takes a lot of effort, I just took to loading Android (reboot within CE) at the end of my session. Purely to get to wake up the device by remote (as it does not wake when having powered-off within CE).
As I also actively use other apps as Prime, Plex, iptv, this is hardly an issue as I also have Kodi installed for generic media streaming usage.
(so this is currently also my advised usage, especially when not fully aiming to only use CE)
So getting the device to sleep works in both Android and CE but only when having shutdown within Android, I get to easily wake the device via the remote.
For a CE shutdown (sleepmode?) I had to actively select the HDMI source on my receiver to awake the device.