CoreELEC 8.95.5

DVB Adapters not found!
The problem of the DVB-S adapters continues, I just tested.
KI Pro.

Which driver package are you using?

It was the IP address to connect to the tvheadend server app for the HTSP Client to connect to.
The server was running on the same device as the Client hence 127.0.0.1, but this gave the

error. Changing the address to the actual IP address of the server (same as client) allowed the HTSP Client addon connect to the server.

I hope that is more clear that what I previously posted :wink:

Tx3 Mini Auto Update installed. Addon Migration in progress left for half an hour. Still please waitā€¦ I SSH into box with reboot command. Box reboots. Same addon Migration in progress. SSH reboot. Same thing. Canā€™t get past Addon Migration. Copied 8.95.5 .tar and pasted to update folder. SSH reboot. Normal update procedure. No errors. Same Addon Migration in progress please waitā€¦
Thatā€™s where Iā€™m at. No further.

Installed the update this morning i have 3 boxen two s912 3g booth did stop at updating addons but worked great after reboot. The s912 2g box did reboot fine but have incompatible plugins did not find a way to fix other the software reset and reinstall now all the boxes works great.

I run from internal emmc on all boxes of it makes any diffrense

Thanks for the good work, this is great

Does this build have auto color space and color depth switching or should I remain on 8.95.4.42 if I want those features?
Thanks

Please try with installation on external media. Itā€™s well known that thereā€™s no support offered for CE installed to internal storage

It does not.

IR remotes do not work for me with this build. First time Iā€™ve had this problem wiht any build.

@rodriguezd There will be more test builds with the auto switching soon. If you are interested in helping test that feature. It just needed to be removed from the main release until it has been a bit more polished.

Iā€™ve just got home after 5 hours. Turned on TV and noticed Kodi had started. Event log shows 10.42am start. No idea what time I turned TV off . So looks like it was sooo sloooow.

I do not understand automatic switching works fine with this latest version?

@Bindou

Thanks but, Ido not understand.
On version 9.95.5, it works well automatic switching (color et Hz). Why try a version of this switch that works less well? What should this new version of automatic switching bring?

Automatic color depth and color space switching is NOT SUPPORTED in 8.95.5, as itā€™s using the 8.95.3 kernel.
This has nothing to do with resolution and refresh rate automatic switching, which has always worked fine, and still does.

Ok thank you, however, the automatic resolution switching and refresh rate, no longer worked after 8.95.3. with 8.95.5, everything came back in order. And for me, switching the color space goes from 8bits to 10bits automatically.

In this version 8.95.5, when I try to watch something from the tvshow library, system get crashed and freezes, I have to unplug my H96 Pro + S912 to get back to the system. It didnā€™t happen in the previous versions.
This is what I get from kodi.log

17:44:21.213 T:4090232768 NOTICE: VideoPlayer::OpenFile: special://profile/addon_data/plugin.video.ONU/videolibrary/TVSHOW/condor [tt6510950]/1x01.strm
17:44:21.214 T:3104772912 NOTICE: Creating InputStream
17:44:21.217 T:3104772912 NOTICE: Creating Demuxer
17:44:21.247 T:3104772912 NOTICE: Opening stream: 0 source: 256
17:44:21.250 T:3104772912 NOTICE: Display resolution ADJUST : 3840x2160 @ 60.00 - Full Screen (16) (weight: 0.000)
17:44:21.409 T:4090232768 NOTICE: CVideoPlayer::CloseFile()
17:44:21.409 T:4090232768 NOTICE: VideoPlayer: waiting for threads to exit

Post a debug log.

Hi @TheCoolest, hereā€™s debug log
Kodi.log

Thanks. I just wanted to make sure that the changes introduced in iptvarchive didnā€™t break anything. Looks like it hasnā€™t in your case.
Since there was a Kodi version bump, and possibly a version bump in some addons, I suggest you try to reproduce this problem with Kodi Beta5 for Windows/Linux with the same version of the addon, and see if the problem happens there too.