Right - but it turns out @vpeter was right ( not a big surprise lol ) and there seems to be an issue - my 21.3-ng coreelec installation always needs the reboot update option - i.e. the First Boot option and just starting up the box (or a regular reboot) causes bootloops. coreelec to boot but NOT initialize the display - i.e. the display stays white.
4 posts were merged into an existing topic: Learning about Dolby Vision and CoreELEC development
A post was merged into an existing topic: Learning about Dolby Vision and CoreELEC development
I went ahead and applied this patch to the amlogic-4.9-20 branch then used the resulting sha to build coreelec.
diff --git a/block/partition-generic.c b/block/partition-generic.c
index 09e61778700b..e1342eca8a89 100644
--- a/block/partition-generic.c
+++ b/block/partition-generic.c
@@ -337,6 +337,17 @@ struct hd_struct *add_partition(struct gendisk *disk, int partno,
else
dev_set_name(pdev, "%s%d", dname, partno);
+ /*
+ * make block special file using partition name
+ * instead of device name with partition number
+ */
+ if (!strcmp(dname, "mmcblk0") && info && info->volname[0]) {
+ pr_info("[%sp%02d] %20s offset 0x%012llx, size 0x%012llx add\n",
+ dname, partno, info->volname, start << 9, len << 9);
+
+ dev_set_name(pdev, "%s", info->volname);
+ }
+
device_initialize(pdev);
pdev->class = &block_class;
pdev->type = &part_type;
The boot behavior didnât change
ce-ng is already EOL, discussing it further wonât change anything, just give up.
A post was merged into an existing topic: Help, support CPM build
Turns out, this is an issue with how the box saves boot parameters.
I removed the coreelec usb drive and set the right preferences - i.e. donât start with dolby vision enabled and then i rebooted the homatics box.
After that I reinserted the coreelec usb drive (while in android) and just rebooted the box - and what do you know it booted correctly (without the white screen).
So, while the newer kernels in ne and no are able to initialize the output of the box at boot time even while in the DV state, configuring the box properly mitigates this!
A post was merged into an existing topic: Homatics Box R 4K Plus
Is Amlogicâs issue with real TV-Led dolby vision fixed on this release?
I think youâre a year late with that question.
Sorry! Just found out that it was fixed in March last year, thank you!
Eheh, no problem!
Hi all
I have windows 11 with Kodi 21.3 running on some machines but i have CoreELEC V21.1 nightly running on a Minix U22-XJ and would like to know is it safe to upgrade to version 21.3 Generic with Dolby Vision still working with the Dovi.ko file. I am going to run MySQL and run it on a windows machine as i want to be able to run the database on there so that if i add any movies or tv shows and stop playing a file it will remember on all front end devices which will be a mix of windows and android boxes.
I have been tolled to run the same kodi version on all machines to make this work as some different kodi versions can cause problems with the data base.
thanks
is 21.3 stable ? and has anyone use MySQL with front ends been mixed with windows and andriod
If you see in Kodi wiki: https://kodi.wiki/view/Databases
Different Kodi major versions use different db versions. To circumvent this problem I just use jellyfin as my media server and CoreELEC as media player. No more versions mismatches.
When playing any Dolby Vision video on am6b+ CE 21.3 , if i stop or exit mid-playback, or fast-forward/rewind, then resume playback or play another Dolby Vision video, the picture quality will suffer a slight downgrade. i have to reboot the entire box to restore full quality. Why does this happen? How can this problem be solved?
I look forward to and appreciate your reply!
CE 21.3 is not the latest testing version.
Plese create userfriendly guide at first post step by step for fel at CE 22 NO. I am disoriented as old user from many discussions.
sure.
step 1. flash boot device
step 2. copy dtb from device trees for your device in root of FLASH named as dtb.img
step 3. insert boot device into target device
step 4. reboot target device with âreboot updateâ
done.
For FEL ! It means which and where is DV file from. In discussion i see only ***.so patch, but this patch to which file ?