Upload full log and ce-debug (this command should be executed via ssh) output again to check.
CE19 nightlies don’t have changes description at the bottom, but yes, patch included
Hello, is there an “Over-the-air” update planned (CE 9.2.6 -> CE 19.0)?
On the other hand, maybe it’s a slow SD-Card or USB-Stick. An original ng device cost around 30 €,
I am using the same SDcard on both boxes as comparison. Yeah I am sure new boxes are inexpensive but the point of going to Jeos CoreELEC is that I can utilize some of these relatively inexpensive boxes without using the power hungry Android framework. Linux is by far the most efficient in term of using power. I have several of these 1G/8G boxes.
I guess I can stick with Leia for a year before I am sure it will start to fade away due to idle development. I can always turn off all the power hungry bell and whistles in Matrix. I just don’t know what Matrix does that requires more CPU then Leia if I keep all settings/skins and such the same.
Hi, I upgraded from 9.2 to 19 Matrix yesterday with no problems. Run some files okay, moved one new file to the library on the external drive, tested no problems. Before going to bed yesterday moved two more files to the external drive with no moving problems. Switched on my TV today and was expecting to test but all dark. Removed power and restarted coreelec, get the matrix screen but for approx 1 minute the logo flashes, then the screen becomes just a quarter in the left top corner, i see a mouse pointer for 2 sec and then screen goes all black. See shortened video. Any idea what has gone wrong?
It’s recommended to perform a clean install!
1 Like
Remove calibration from guiseettings.xml
Thanks, missed that. Can I do that on a Odroid N2 which I bought as a package? With eme (wrong word…) memory?
So this by ssh into the machine, correct? I’m not so tech… but can figure out if that is what is meant.
The same topic some messages below
1 Like
Thanks, now I know how to do this. And you think this will do it? So it means I will not have to restore the emmc memory card from scratch! Still even if it takes 1 minute before the screen goes black?
/Dan
I missed the part that your screen is still black after quarter screen.
In that case you can try also to update to latest nightly and check again…
In case nothing helps it will be better to try clean install.
As for 1 minute delay it could be another config issue. Clean install should solve all of them.
1 Like
I have the following (minor) issue on both Matrix 19 and CoreELEC v9.2.6. This issue is not present with CoreELEC v9.2.5. I have performed fresh installs of both v9.2.6 and Matrix 19 on 2 different SD cards.
When powering off CoreELEC using the “shutdown” from the power menu, CoreELEC does power off correctly, but the source does not automatically switch back to the TV source. With CE v9.2.5, the HDMI source would auto switch to the TV when powering off CoreELEC.
All the other CEC options seem to work fine. As I said, this is a minor niggle for me. Correct me if I’m wrong but I don’t think a log would help as this happens after CE is powered off?? Any ideas? My CEC settings are identical across versions.
Thanks in advance for any guidance and kudos for the great job you all do!
PS. My kodi box connects directly to TV via HDMI - I have no AVR etc. TV is Toshiba 43U5863DB 4k and kodi box is X96 Max S905x2 4gb RAM 1gb Ethernet.
PPS. I just tried this on another box (s905x3 X96 Air 4gb RAM 1gb Ethernet) and this minor issue is not present. So it seems to be specific to the S905x2 X96 Max box - maybe a dtb issue?? Just guessing.
Hi Bindou, the upgrade to Matrix is manual as we don’t want to force remove anyone out of Leia.
1 Like
I received this from a Ugoos engineer
“ unfortunatelly, Dolby did not provided 64bit lib to Amlogic, due Amlogic have no 64bit SDK for their devices. we asked about it, we also connected with Corelec guys. but for now, such lib still not provided by Dolby”
Sounds unlikely we’ll get a 64bit DV library anytime soon.
So…how about that 32bit Coreelec build? 
Ok, as requested - debug log of Kodi choosing 60hz when playing at 25hz file using the 8/3 nightly.
dmesg - http://ix.io/2Sc6
kodi.log - http://ix.io/2Sc8
ce-debug - http://ix.io/2Sc9
…although I am having trouble loading the first two of from ix.io right this second…
You have enabled “Sync playback to display”
It should be switched off!!!
Err I haven’t. I have manually set that to off, definitely…and checked it, multiple times. I have literally never used that in 10+ years of using Kodi on a wide variety of platforms…apart from in a separate testing profile, recently, I use to try and keep things as isolated as possible.
If it is on in that log, it’s something to do with Kodi’s stupid profiles picking up settings across profiles. But even in the Master profile it has been set to off, for sure. So that shouldn’t be happening. But Kodi profiles are a right mess in that regard…
I will check it once again and manually edit the guisettings.xml on ALL profiles if I have to & post new logs. But am at work now, so won’t be till tonight…sorry.
ix.io is up and down like a yo-yo here (might be my ISP as they were doing works overnight…) - so I can’t even get to my own log, sigh, to read it.
videoplayer.usedisplayasclock: true
So it’s enabled…
After you switch it off all should work with correct refresh rate.
And ix.io normally works, so logs are visible.
No problem, take your time. It’s bedtime here 
Yep will do it again tonight. My ISP did ‘works’ overnight, so I probably need to reboot the cable modem to solve that…but yep can load ix.io fine here at work.
Thanks for looking at things, btw, it’s appreciated.
OK, new logs as promised.
dmesg: http://ix.io/2SdC
ce-debug: http://ix.io/2SdB
Kodi debug log - http://ix.io/2SdD
To note:
videoplayer.usedisplayasclock: false is confirmed…
…but Kodi still chooses 60hz, although it is now at least looking for the double refresh rate mode…
The mode it should choose is listed:
INFO <general>: Found resolution 1920 x 1080 with 1920 x 1080 @ 50.000000 Hz
But then:
2021-03-09 18:14:52.451 T:4678 INFO <general>: [WHITELIST] Searching the whitelist for: width: 1280, height: 720, fps: 25.000, 3D: false
2021-03-09 18:14:52.451 T:4678 DEBUG <general>: [WHITELIST] Using the default whitelist because the user whitelist is empty
2021-03-09 18:14:52.452 T:4678 DEBUG <general>: [WHITELIST] Searching for an exact resolution with an exact refresh rate
2021-03-09 18:14:52.452 T:4678 DEBUG <general>: [WHITELIST] No match for an exact resolution with an exact refresh rate
2021-03-09 18:14:52.452 T:4678 DEBUG <general>: [WHITELIST] Searching for an exact resolution with double the refresh rate
2021-03-09 18:14:52.452 T:4678 DEBUG <general>: [WHITELIST] No match for an exact resolution with double the refresh rate
2021-03-09 18:14:52.452 T:4678 DEBUG <general>: [WHITELIST] Searching for an exact resolution with a 3:2 pulldown refresh rate
2021-03-09 18:14:52.452 T:4869 DEBUG <general>: CVideoPlayer::ProcessVideoData size:17705 dts:7.040 pts:7.120 dur:40.000ms, clock:-0.196 level:82
2021-03-09 18:14:52.452 T:4869 DEBUG <general>: CVideoPlayer::ProcessVideoData size:6624 dts:7.080 pts:7.080 dur:40.000ms, clock:-0.196 level:82
2021-03-09 18:14:52.452 T:4678 DEBUG <general>: [WHITELIST] No match for a resolution with a 3:2 pulldown refresh rate
2021-03-09 18:14:52.452 T:4869 DEBUG <general>: CVideoPlayer::ProcessVideoData size:7134 dts:7.120 pts:7.160 dur:40.000ms, clock:-0.195 level:83
2021-03-09 18:14:52.452 T:4678 DEBUG <general>: [WHITELIST] Searching for a desktop resolution with an exact refresh rate
2021-03-09 18:14:52.452 T:4678 DEBUG <general>: [WHITELIST] No match for a desktop resolution with an exact refresh rate
2021-03-09 18:14:52.453 T:4678 DEBUG <general>: [WHITELIST] No resolution matched
2021-03-09 18:14:52.453 T:4678 INFO <general>: Display resolution ADJUST : 1920x1080 @ 60.00 - Full Screen (16) (weight: -1384935587840.000)
Seems to me it is actually searching for 1280 * 720 @ 50 - instead of what it should be looking for, which is 1920 * 1080 @ 50, right?
(…and for what it is worth, I was right about the previous logs - the master profile (sync playback left on) - was bleeding through to the actually used profile - where Sync Playback to Display was definitely off… In any case, it’s now off in all profiles, and just to be super duper sure, I rebooted and checked them all twice!)