I get this from the other forum, but here is one corrected version.
please help, I go all steps but when I run in ssh ir-keytable -a /storage/.config/rc_maps.cfg -s rc0
I get this errors:
' not recognised, no mapping for scancode 0x041d022e
' not recognised, no mapping for scancode 0x041d0206
' not recognised, no mapping for scancode 0x041d0204
' not recognised, no mapping for scancode 0x041d0211
' not recognised, no mapping for scancode 0x041d020c
' not recognised, no mapping for scancode 0x041d020e
' not recognised, no mapping for scancode 0x041d024d
' not recognised, no mapping for scancode 0x041d020a
' not recognised, no mapping for scancode 0x041d0208
' not recognised, no mapping for scancode 0x041d024c
' not recognised, no mapping for scancode 0x041d0201
' not recognised, no mapping for scancode 0x041d0250
' not recognised, no mapping for scancode 0x041d0202
' not recognised, no mapping for scancode 0x041d0203
' not recognised, no mapping for scancode 0x041d021f
' not recognised, no mapping for scancode 0x041d021e
' not recognised, no mapping for scancode 0x041d0218
' not recognised, no mapping for scancode 0x041d021a
' not recognised, no mapping for scancode 0x041d021b
' not recognised, no mapping for scancode 0x041d0214
' not recognised, no mapping for scancode 0x041d0216
' not recognised, no mapping for scancode 0x041d0217
' not recognised, no mapping for scancode 0x041d0210
' not recognised, no mapping for scancode 0x041d0212
' not recognised, no mapping for scancode 0x041d0213
' not recognised, no mapping for scancode 0x04bf0e
' not recognised, no mapping for scancode 0x04bf44
' not recognised, no mapping for scancode 0x04bf43
' not recognised, no mapping for scancode 0x041d0219
' not recognised, no mapping for scancode 0x041d0251
' not recognised, no mapping for scancode 0x041d0215
' not recognised, no mapping for scancode 0x041d0255
' not recognised, no mapping for scancode 0x041d0254
' not recognised, no mapping for scancode 0x041d0259
' not recognised, no mapping for scancode 0x041d025c
' not recognised, no mapping for scancode 0x041d0209
' not recognised, no mapping for scancode 0x04bf0d
Old keytable cleared
Wrote 1 keycode(s) to driver
Protocols changed to
bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev//rc_keymaps/protocols
I found out what the problem is, my TV LG G29 is connected to the soundbar LG DS95QR via eArc and all other sources are connected to the TV. In the audio menu is set under extended passthrough for the sound. I came to it because the TV has always brought the error message. Now I connected CoreELEC directly to the soundbar for testing and it works.
I must thank you for your effort and sorry if I was annoying.
2 Likes
I requested the new firmware via support and they pushed it to my device (Homatics). All working well now on alpha 2 including DV. May stay on alpha 2 unless the judder requiring 10 second jump back is fixed or anything else significant (that’s the only issue I’ve had).
1 Like
What was your route to requesting the new firmware via support ?
I asked the Homatics support when the new firmware will be available.
They answered me today:
“Start pushing out today and needs about 1 week to reach everyone.”
I was already able to perform the update.
I received the firmware 5310 yesterday for dune also…
Any .5310 news from nokia users?
A sample video made using DoVIBaker, Fel layer is baked into BL and RPU is converted to 8.1.
1 Like
No Update yet
and Dolby Vision in CoreElec works for you, because not for me in firmware 5310
I just used the webform on the website.
Don’t know for sure… My old Philips OLED don’t support Dolby Vision… HDR10 is working.
Sorry, can’t help…
Just updated nightlies, got a warning about Android firmware being incompatible with Dolby Vision, went into Android and it flashed for a split second no updates but then started downloading an update with a hilariously detailed filename.
Had to do the reset trick to get back into CoreElec again, but it all seems to be working.
Unrelated: why is it that Dolby Vision movies usually look like crap in HDR10, while HDR10-only movies tend to look a ton better?
is there anyone who has Dune firmware 5310 and can’t do Dolby Vision in coreelec 21.0-Omega_nightly_20230705
1 Like
Runs perfectly
it already works, wrong img.dtb
1 Like
Hi
For me also the DV format did not work under CE after updating DuneHD. The solution was to delete the dtb.img file that was previously on the USB. Then I copied the sc2_s905x4_sei_smb_280.dtb file from the device_tree folder of a current img file and placed it as dtb.img file to USB.
Maybe did the dtb file changed
in the meantime and I had the old on my USB?
1 Like
Have a Homatics R 4K Plus - rebooted into Android today, received the OTA update, rebooted into CoreElec using toothpick method, accepted the nightly download, installed it, and have DV files playing fine.
3 Likes