Homatics Box R 4K Plus

I’m dual booting NG with atv12 atm. Is there any point in waiting or will atv14 permanently ruin chances for FEL playback on the homatics? I’m not sure I’ve quite understood what exactly the upgrade to atv14 breaks on the CE side if someone wouldn’t mind explaining. Thank you!

When you need stable version of CE-NE, or use CE-NG for p7 fel, than you not update the android.
Under atv14, those 2 will not working.

@hungphutho, great collection of test files/clips. Are those available to download somewhere, or would you be willing to upload & share? Thanks.

Ok. VIDEO_TEST – Google Drive

2 Likes

Awesome, thanks! Recognize several from Kodi A/V samples, which I maintain, but nice to have others I didn’t have :).

Newbie here and I am really confused with all those DV Profiles, I have an older OLED that supports HDR10+ but no DV, if I dont want my device to show black frames as it does now on the stock android of the TV(My Homatics is on the way) What should I do? Does CoreElec do the job for me and tonemaps it to HDR10? Is the quality good also?
I see players as MPV using libplacebo too that automatically SW tone map the DV metadata too, so many questions. Sorry I know this has been explained a million times probably but searching only contributed to more questions and more confusion.
Thanks in advance.

HDR10+ and Dolby Vision formats are built on top of an HDR10 “base layer”. This means that when you play those formats on a TV that doesn’t have Dolby Vision or HDR10+, it will just play the HDR10 base layer. UNLESS it’s DV Profile 5, which uses a proprietary color space that doesn’t quite work the same way. Profile 5 is what’s used for streaming services, so if you are trying to play DV content from streaming services, then you will likely still have some issues.

Someone can correct me if I’m wrong, I’m not aware if CE can tonemap P5 by default.

1 Like

P5 require a DV compatible CE device to get shown in correct colours.

2 Likes

Forgot to post results of this. Unfortunately it didn’t help at all to the occasional stutter and audio delay after skipping. It just made normal playback much more stuttery.

Now after using the device for couple of weeks I can say that at least with the current high bitrate 4K show I’m watching the device skips frames during playback. It might happen every couple minutes or +10 min but it’s still noticeable and they happen on every episode. These frame skips didn’t occur at all before I with my PC on the same show. Hopefully the frame skipping not present in most my high bitrate 4K videos.

how to boot to atv 14 while in Ce-no without removing the ce-no os pendrive ? i seems cant make it to boot into android tv cos it will just reboot back to Coreelec.

Try this apk, in post no. 27

1 Like

reboottoandroidtv doesn’t work in ATV14 :frowning:

Currently all CE buggy in ATV14 , wait until the CE team fix that.

this zip no longer work with Ce-no on atv 14. i had to remove the usb flash drive to make the box reboot to android tv. if i use the zip addon it will reboot back to the corelec.

the zip addon worked with ce-ng and ce-ne but no longer with ce-no.

When I play the movie in Dolby vision format, the device shuts down. I’m not sure what the issue is. I’ve installed the dovi.ki file as usual, but there’s a problem I don’t know how to fix.
Homatics R 4K Plus coreelec-no

Afaik there is no dovi.ko for no

Yes there is:

1 Like

Ah, sry for outdated misinfomation then

Hey all, I am struggling to install/boot into CoreElec on my Nokia 8010.

About a month ago I was running the stable 21 Omega version without any problems until my usb drive died, fast forward to now, I have a new usb drive (warranty, yay!) and tried to do a fresh install but am getting completely stuck on the installation.

After doing the reset btn/toothpick method or using the app and a bunch of loading I eventually load into Recovery mode with a “No command” screen, and the logs have a bunch of repeating lines saying “… no such file or directory”.

What’s happened in the month or so I haven’t been using this? Any ideas on how I could resolve this?

I’ve tried:

  • Creating a bootable drive with both Rufus and Balena
  • Tried, 21.1.1-Omega (Stable), Nightly, and 20.5-Nexus (Final). For all I’ve copied sc2_s905x4_sei_smb_280 from the device tree and renamed to dtb.img in the root.
  • Using the toothpick method, and the app to start the install.
  • Edit: Tried both the USB 2.0 and USB 3.0 port. Am using a Sandisk USB 3.1 Ultra Fit 64GB

That’s the only way.
Try use other usb port, or other USB pendrive

1 Like