Posts by kszaq

Quote from vlaves

PS I guess this build is 32Bit only? Hope you will stay on 32Bit as there is no mem leak reconizeable at all

As far as I know there is a memory leak in 32-bit builds but much less recognizable and therefore not noticeable at all. That said developers with much more skills are looking into fixing the leak.

Quote from vlaves

PPS In this thread here in the Kodi Forum a Kodi 18 build is mentioned where the inputstream is working again with Amazon Video, any chnace to get those changes into your build?

The mentioned Kodi version is for Android and uses WeTek's DRM capabilities in Android. In LE you can try using unofficial plugins: LibreELEC

Quote from Pitou

I would like to report that since beta2, the IR remote with my Wetek Hub doesn't work anymore.

Thank you.

Pitou!

Have you upgraded from official LE or Raybuntu's build? If yes, you probably did not update your device tree. Official LE uses LIRC for the remote, whereas my builds use amremote. On my WeTek Hub remote is working.

Quote from blinkmxq

The playback stutters. However upon further testing, 25fps (at 50hz or 60hz) is also just as bad no matter whether automatic refresh is enabled or disabled.

Make sure you don't have CPU-intensive tasks/addons running in background. In Kodi 17 + Amlogic smooth playback depends a lot on free CPU resources.

Melittamann The log is full of information on resync messages, this could mean too slow network connection. Please try using one of the previous builds and also provide a sample that I can reproduce the issue with.

cHarOn The issue with many devices is that they don't accept flashing device tree from LE because of some u-boot level lock. I suspect this may have something to do with not being able to write u-boot variables at runtime. This will be fixed in a next build and then you can try installing to internal again... In case it fails I might look into providing a different device tree again.

Quote from sYCO

I tried to install several addons from the Superrepo
or Fusion repositories, but they do not seem to work
on a Libreelec/Kodi build. They even fail to install.

You may need to have a look at this: Official:Forum rules/Banned add-ons - Official Kodi Wiki

Quote from blinkmxq

Do these updates fix 23.97 automatic refresh playback?

Edit: it doesn't.

It's already been fixed in beta1. What's there to fix?

Quote from Hans Gruber

I've just installed beta 2 and I'm not sure deinterlacing is working as it should. It's not showing scanlines most of the time but it feels like it should be smoother, and sometimes as camera shots change you'll briefly glimpse the scanlines. In the "video settings" menu "deinterlacing method" is set to "off" but greyed out. I've just upgraded from 7.0.3.012c and that seemed ok. This is while watching Live TV (Freeview HD in UK DVB-T2).

I tested deinterlacing on a few samples that I have and noticed no such behaviour. Can you provide a sample? Also make sure that you don't have any deinterlacer module parameters set in autostart.sh.

Quote from dazed

Your mediaportal pvr addon is still out of date GitHub - kodi-pvr/pvr.mediaportal.tvserver at Krypton should be v2.4.14 not the v2.4.12 that is in the LibreElec repo

Like I said before, I'm still recompiling addons, this is a long process and I need to fix any build errors that show up from time to time.

Quote from fat-tony

kszaq - I noticed you had updated to beta2, so I loaded it and remote works fine for me now (same as stopping eventlircd earlier) - many thanks. Was there a mapping change somewhere?
Following on from this , does it mean that mapping of remote buttons (built-in IR remote) could now be tweaked by users using the Lircmap.xml etc. methods? Or is this a future feature?

In beta1 some buttons were not working because keys were parsed by eventlircd rather than sent directly to Kodi.

For future builds I plan to add a possibility to switch internal IR receiver driver to LIRC so that you would be able to use any IR remote with built-in receiver. The downside of this approach is a bit slower button parsing than with amremote driver and not being able to use remote.conf files - you would have to configure every button on fresh install. That's why this will be optional and not default behaviour in my builds.

@all 7.90beta2 build posted in OP - fixes and improvements included.

Really big thanks to Peak3D who redesigned AML decoder in Kodi Krypton. Thank to his hard work and patience we can now have near-perfect HW-accelerated video playback in Kodi Krypton!

I'm currently rebuilding addons and will update repositories soon.

Quote from juramusger

as for lircd, I entered "systemctl stop eventlircd" and as kszaq said, all buttons on the packaged remote (that I don't normally use) work ok afterwards (p.e. home does not before). but top still says "/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd" is consuming around 35 % of CPU.

This is the main Kodi process, lirc is only an argument that points Kodi to lirc in case you wanted to use it. The usage is completely normal.

Quote from juramusger

finally, what is the difference between the suggested "fw_setenv hdmimode 1080p50hz; fw_setenv outputmode 1080p50hz" and what I'm doing now: "echo 1080p50hz > /sys/class/display/mode" ?

The first one switches initial display mode: u-boot level, splash screen and in Android. The latter switches display mode at runtime.
[hr]

@all 7.90beta2 build posted in OP - fixes and improvements included.

Really big thanks to Peak3D who redesigned AML decoder in Kodi Krypton. Thank to his hard work and patience we can now have near-perfect HW-accelerated video playback in Kodi Krypton!

I'm currently rebuilding addons and will update repositories soon.

Gregoir3 Centurione BT Audio problems with MiniMXIII II may be due to low baud rate used in hciattach. I will bump it in the next build. This will either fix BT Audio or break BT completely.
[hr]

Quote from fat-tony

Thanks kszaq - in the meantime, I have a question about default framerate. When my box (s905x 2GB) boots up it seems to default to 1920x1080p60. I would prefer if it it used 1920x1080p50 as most of the stuff I watch is TV or DVD from Europe. I know the framerate will adapt depending on the source material, but I would like it to default to 50Hz. Seems to be a property of the .dtb?

This is set by u-boot. Try fw_setenv hdmimode 1080p50hz; fw_setenv outputmode 1080p50hz.

The fix for remote buttons is ready for the next build. Meanwhile you can temporarily fix it by running systemctl stop eventlircd.

Quote from Melittamann

kszaq:

I installed your last build 7.0.3.3 on a MXQ AllBlack, ( s805 1,5 MHz 1GB/8GB ) from USB-Stick ( like SD Card )
works fine but the Pic get stuck and the Audio Plays after a plently of Time, when the amcodec ist on.

Anny ideas to get that fixed?

I will not look into this issue because I ignore all reports with no or incomplete logs and no sample to reproduce it. Just like it's said in "Reporting bugs" sticky post.

Quote from pawnthep

Hope this NAND-installation-error issue can be fixed sooner or later

I have one idea how to make it use recovery rather than unreliable scripts... I have to implement and test it.

sonofdibnah "Reboot from internal" is only available in Estuary Skin but should be always available.

Quote from Merziyas

Hello Kszaq (and others), my problem with the newer builds (all builds after 7.02.005) is that I don't have sound, nothing at all. Now I managed to figure out what the problem is. I cannot select "ALSA" sound output in the new builds. The last build which let me select ALSA is 7.02.005. The sound works good with ALSA but when I select PULSE even in .005 build the sound wont work. Why cant I select ALSA audio output in the new builds? Any workaround for this? Thanks in advance.

You haven't updated the device tree correctly.