Unable to load window XML - Any Skin - Black Screen in SubMenu

Hello,
I don’t know if this is the right place to post this.

I am randomly having the following problem.
I start CoreElec and it starts correctly.
But sometimes (many times) when I enter a section of a menu (and this is random). It doesn’t load that screen, it stays empty OR sometimes, my TV goes completely black.
I can go back, and it recovers and I see the menu again correctly, but indefinitely, until I reboot.
Also, sometimes a reboot is not enough, and I have to reboot several times, until it is solved.

Here is the complete log:debug <general>: Thread LanguageInvoker start, auto delete: false2024-11-25 08 - Pastebin.com

I think the interesting thing is here:

2024-11-25 08:55:36.507 T:3921 debug : ------ Window Init (Settings.xml) ------
2024-11-25 08:55:36.507 T:3921 info : Loading skin file: Settings.xml, load type: KEEP_IN_MEMORY
2024-11-25 08:55:36.595 T:3921 error : Unable to load window XML: /storage/.kodi/addons/skin.cpm.estuary/xml/Settings.xml. Line 0
Failed to open file
2024-11-25 08:56:01.607 T:3967 debug : Thread JobWorker 3819909632 terminating (autodelete)
2024-11-25 08:56:01.608 T:3968 debug : Thread JobWorker 3811516928 terminating (autodelete)
2024-11-25 08:56:01.614 T:3986 debug : Thread JobWorker 3624923648 terminating (autodelete)
2024-11-25 08:56:01.618 T:3966 debug : Thread JobWorker 3764371968 terminating (autodelete)

I have connected via SSH, and indeed, that file does not open.

I’ve tried some other random files in that directory, and some I can see, but others get the error.

Any ideas, or other tests to carry out?
What is going on?

Thanks

Run dmesg command in ssh and you will see lot of filesystem errors.
Make fresh install.

Mmm…
you’re right, there are a lot of mistakes :frowning:
Although I don’t have much knowledge of that command:

I don’t know what to look at, and there are a lot of lines.

You say to do a clean install… ok, I’ll give it a try.
But these days, I seem to remember that I did one, and at some point the same thing happened to me, although I didn’t give it any importance in the beginning.

1 - If it happens again … Any other ideas?
2 - Is it possible that it’s a problem with the SD (even though it’s new)?
3 - I’m going to format the SD and install CoreElec with Rufus. Once started, i can restore my backup or don’t you recommend it?

Thanks

Use USB sticks, they are more dependable than uSD cards. Once you have new system running and tested that it works OK, then restore your backup. That will tell you all.

It would be a very good test to do the USB thing, but as far as I know, on the device I use:

I can only install CoreElect via the SD slot? :confused:

Or you could insert a USB into one of the slots and it could also load dual boot???

Thanks for the help!

Don’t know for sure, don’t own this box, but on similar, Nokia 8010, it works…

I understand…
But I see that this box doesn’t have SD slot… so, I don’t know if mine only works dualboot with SD or not…

In any case … if I could only use the SD, do you think it might be a good idea to try a different SD?

EDIT:

Ok, yes, I got confirmation from another site, that I can boot coreelect on my device with a USB stick.

Well, I’ll try it and tell you as soon as I get the results.

Well, mystery SOLVED.
After testing several times last night, I can confirm that the problem does not occur using a USB stick.

I can’t believe it… was going to drive me crazy.

EVEN MORE: Several days ago I commented that I was having trouble switching audio through playback on fullbluray ISOs. Well now I don’t have that problem anymore :confused:

Now I would like to know if the problem is my SD: Lexar 633x 64GB.

  • Not enough speed?
  • Is it too slow?
  • General problem on my device with SD?

For now I will do a clean install and try again with the SD.

Thanks so much

Super curious…
I tried another older 32Gb Samsung SD card that I had in a drawer, and it works perfectly.

I cloned the usb to the Lexar SD, just after booting, I had the same black screen error when loading submenus.

I cloned the usb to the Samsumg SD and everything worked fine.
I’m amazed…
To drive me crazy.

I don’t know if there is any program to verify what could be happening with this SD, although I understand that it is not the subject of this forum.
I’ve run it through chdsk and it doesn’t show anything faulty.

In any case, thank you all very much.

Maybe 64GB µSD aren’t supported?

Well, I don’t know, but it doesn’t say so in the specifications…
I understand that if it didn’t support 64 GB, nothing would work… no?

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.