...when I check the resolution in Kodi it says i'm at 704x240, which I think is 240p? I can't change or adjust the resolution to get 480i.
Don't trust in the Kodi resolution here. It's an exotic adapter, and to my knowledge you're the first VGA 666 user on LE. You said "the VGA-to-SCART adapter expects a 480p signal". So obviously the VGA adapter delivers just that.
The VGA adapter makes no sense to me, if your TV has no VGA input. Anyway, do the adapter setup at config.txt:
I would like to ask, what is the motivation to use OpenGL ES instead of the Core Profile for main Generic x86 build.
Our smaller devices only support OpenGL ES. That means, those calls go directly to GPU (hardware accelerated).
OpenGL Core Profile for x86 would add another branch of development, which doesn't make sense for our needs (though it would make sense for yours).
Please post the output of dmesg.
Large logs don't crash the system.
Use cat /storage/.kodi/temp/kodi.old.log | pastebinit to get the log from previous session (after crash and reboot).
Maybe a stupid question: how do you start the RPi aftet shutting it down?
The concept is to connect two pins temporary. So it would be useful to buy a case with a push button.
Will be a weekend project. Would a totally blank install be favorable as well? So no extra themes, addons and configuration clutter?
Yes, I would prefer that. Makes the log smaller.
I suggest to have a look at the nVidia Shield forum. The Shield uses the Android variant of Kodi, and many Shield users are multimedia experts.
DAZN also doesn't work for me ATM (RPi3B+, LE 12.0.2).
Seems like the DAZN add-on from KodiNerds repo needs an update. I guess it's the HTTPS error.
2025-02-01 09:35:32.078 T:3159752 debug <general>: CZeroconfAvahi::doPublishService identifier: servers.eventserver type: _xbmc-events._udp name:carlsen port:9777
2025-02-01 09:35:32.078 T:3159752 debug <general>: CZeroconfAvahi::addService() named: carlsen type: _xbmc-events._udp port:9777
2025-02-01 09:35:32.078 T:3159752 debug <general>: CZeroconfAvahi::doPublishService identifier: servers.jsonrpc-tcp type: _xbmc-jsonrpc._tcp name:carlsen port:9090
2025-02-01 09:35:32.078 T:3159752 debug <general>: CZeroconfAvahi::addService() named: carlsen type: _xbmc-jsonrpc._tcp port:9090
2025-02-01 09:35:32.079 T:3159752 debug <general>: CZeroconfAvahi::doPublishService identifier: servers.webserver type: _http._tcp name:carlsen port:8080
2025-02-01 09:35:32.079 T:3159752 debug <general>: CZeroconfAvahi::addService() named: carlsen type: _http._tcp port:8080
2025-02-01 09:35:32.079 T:3159752 debug <general>: CZeroconfAvahi::doPublishService identifier: servers.jsonrpc-http type: _xbmc-jsonrpc-h._tcp name:carlsen port:8080
2025-02-01 09:35:32.079 T:3159752 debug <general>: CZeroconfAvahi::addService() named: carlsen type: _xbmc-jsonrpc-h._tcp port:8080
2025-02-01 09:35:32.080 T:3159752 debug <general>: CZeroconfAvahi::doPublishService identifier: servers.airtunes type: _raop._tcp name:A8A159E22714@carlsen port:36666
2025-02-01 09:35:32.080 T:3159752 debug <general>: CZeroconfAvahi::addService() named: A8A159E22714@carlsen type: _raop._tcp port:36666Port 8080 was added twice for different services. Not sure whether it results in conflicts.
dtech I think that's correct. A while ago I had a private conversation with curiousgeorge, and he said:
I opened it and the board says HD18Q-v2.0 thanks in advance.
Interesting. I only have one card on my RPi3B+ when using aplay. I was actually trying to conclude here.
So RPi4 and RPi5 offer two HDMI audio drivers, and that's what we see on aplay.
Why are card 0 and card 1 both linked to device 0?
If device 0 is only an offer from the driver, and not an existing physical device, then it's confusing labeling (driver vs. device).
According to aplay output, you've connected both RPi4 HDMI ports. Unplug HDMI-1.
We can stay on this thread. That post describes your issue, and also a possible solution:
