Posts by Sholander

Quote from johnberg

wrxtasy , Sholander

Summary:

I installed 8.2.4 Subtitles-ff.tar on my H96 Pro+ 1000 Mb LAN 3g

When I use the attached device tree gxm_q200_3g.dtb my device won't boot anymore.

When I put the old device tree back it is booting fine again.

Video playback with srt is running like a charm now.

But I can't overclock the GPU to 792 MHz because I have the old dtb.img file.

I use 666 MHz but even on 400 MHz video/subtitles is playing perfect.

Am I right that the key to this great update is adding an important VSync Hardkernel ODROID C2 patch?? and that this overclocking does not make many difference to video (movie) performance?

Display More

Just FYI there is no subtitle stutter on "regular" GPU clock speed (500MHz) on new CoreElec devel version. All it needs to play without subtitle stutter with Harware Decoding is disabling all "Dirty Regions" via advancedsettings.xml.

Although it would be nice if wrxtasy could bring OC option to this devel version, for me THE BEST so far...

I uploaded one of my sample files with which I test new LE and CE versions. With this video clip one can easily check for any existant stutter.

Chose this clip because if this specific clip plays OK for me on my X92 box then 99% of my content will play OK.

The clip can be downloaded from HERE

Quote from johnberg

I made that command in Putty and it shows only 666 so not 400/666

OK I can try it with the q201 but this is actually for 100 Mbit LAN not the right intention I think.

Why does the H96 Pro+ not boot with the original device tree from Wrxtasy??

However it is, the movies are playing fine now with subs, using the old dtb file.

That is really a big improvement, but is this caused by overclocking or something else??

Maybe Wrxtasy can answer this question.

I am very interesting in the experience of other H96 Pro+ users

Display More

With old dtb.img selecting overclock option you get 666MHz, and without this option you should get 400MHz.

With new dtb.img you should get 500MHz without overclock and 792MHz with this option enabled...
You have to reboot the box after every change to take effect.

You can set 792MHz to Off and see how the subtitles behave for you.

Btw, why do you have to use 1Gbit Lan? I use only Wlan and keep Lan off...

Quote from wrxtasy

To everyone.

It's not just the AML S912 I am noticing strange, occasional downloaded external Subtitle Addon hangs with but other S9xx platforms that never had video playback Subtitle issues.

They too now occasional lock up Kodi. I suspect a Kodi update has messed with something.
Weird thing is it's not all external .srt Subtitles that do this.

If I remove the problematic .srt file from my external file server the previously Kodi crashing movie files playback fine.

I use all my external subs on an USB disk in the same folder as video, and NEVER had any issues, or misbehavior on X92 box.., your build just works perfect for me. It makes no difference playing with or without hardware decoding...

Quote from johnberg

I used 8.2.4 subtitles ff.tar and device tree gxm_q200_3g.dtb

After I took an other SD card and made a fresh install with the same files (img.gz) of course. And again the same problem, no boot.

Then I deleted the dtb file and pasted the old dtb file (used with 8.2.2.3) back and the the device was booting perfect again.

I could set the GPU clock to 792 Mhz in display> community extras.

Then testing it with some critical movies and wow!! for the first time no framedrops when enable external subs.

Sometimes the first sub is having the old evil, but after everything is playing fine and smooth, I read this before in this topic, no problem for me.

But... why does the H96 pro+ not boot with the dtb file as you advice?

I am happy allready but could it be more better if this adviced dtb file should work??

The CPU temerature is various between 54 and 61C

And clock speed is showing 1000 and sometimes 1500 Mhz

Display More

On my X92 box, if I don't use new dtb.img from 8.2.4 folder I don't get full 792MHz freq.

With old dtb.img, with which my box also boots, I get 400/666 freq and with new dtb.img I get 500/792MHz.

CPU clock freq is of no interest here, you should check GPU clock freq with comamand:

cat /sys/class/mpgpu/cur_freq

What is correct dtb.img for your box to achieve this OC freq I don't know.... Did you try with gxm_q201_3g.dtb?

I ask because my box boots with both versions q200 and q201...

@ChimeyJimmey

I just pointed out that it does not work FLAWLESSLY! so don't panic, and in future explain WHAT works FLAWLESSLY!
And I will delete my post, not to smudge the thread

1. Yes, use LE (Settings) Backup option to backup all LE-Kodi content. From .backup folder copy the backup.tar to a safe place. On new SD card install same LE version, copy backup.tar to .restore folder on new SD, and then use LE (Settings) Restore option to get all like on old SD card.

2. Yes

@wrxtasy

Had time today to test your latest "LibreELEC-S912.arm-8.2.4-Subtitles-ff" version without GPU OC (normal 500MHz speed), and still all my critical samples played without stutter. Gui is a little slower, but the temp is 4-5°C lower...

Quote from CacheMeOutside

I was interested in the Overclocking and patching the reported subtitle issue. I already have 8.2.3. I will update to regular 8.2.4 first.

No need, just drop "LibreELEC-S912.arm-8.2.4-Subtitles-ff.tar" in the .update folder together with correct dtb.img from here

We are talking here about 8.2.4_OverClock build from @wrxtasy (MEGA)

Nothing to do with with "normal" 8.2.4 build. (Index of /releases/archive/8.2.4)

Which buld interests you?

Quote from Pinki

Still yours 8.2.4 Subtitles-ff is the best stable build of Kodi LE.

We see how much time you spend to fix many problems, thank you

Thinking back through the steps I did yesterday, yes "vfd.conf" is probably the reason. Not the file itself, but my stupidity; I think that yesterdy I copied the file to wrong folder, not like today to correct -> /storage/.config/

Quote from The Coolest

Yep, I believe that with this version by adamg, you can run sh uninstall.sh followed by systemctl restart fd628 and stick to the built in driver, as it is identical.

It did not work until I run through your installing procedures.

Anyhow, that was just a test version that I don't intend to use.

Quote from Sholander

Will try tomorow again with v.8.2.4_OC images.

Tried again with my instalation (not new install) of "LibreELEC-S912.arm-8.2.4-Oclock-GPU.img" updated with

"LibreELEC-S912.arm-8.2.4-S912-Subtitles-fix.tar", same as yesterday's trials.

First uninstalled "service.fd628", deleted driver from .local/share and "vfd.conf" from .config -> rebboted.

Then copied and renamed x92-vfd.conf to .config and run your "install.sh" from unpacked "FD628 Display.zip"

It finished with "something" = 1 and BUM -> corect time was displayed! Finaly SUCCESS.

Did not install service.fd628, because clock display is all I realy need.

Just don't know what was going wrog yesterday. I know how silly and frustrating it feels when you know for sure that something works, but it does not work for a person you are trying to help.

So THANK YOU VERY MUCH for staying with me at times of lost faith, CHEERS

Already did that, tnx

Used this version "https://libreelec.adamg.co.uk/releases/archi….2-8.2.4.img.gz"

I did it now with files for "normal v.8.2.4" (not OC version) with correct files.

After boot I get almost a correct display and this is the output:

Using username "root".
[email protected]'s password:
##############################################
#                  LibreELEC                 #
#            https://libreelec.tv            #
##############################################

LibreELEC (community): 8.2-8.2.4 (S912.arm)
LibreELEC:~ # cd radni
LibreELEC:~/radni # chmod 0755 FD628Service
LibreELEC:~/radni # sh test_led.sh
No command line options were found, showing usage instructions.

Usage: FD628Service [-t] [-dt TYPE] [-h]

        -t              Run FD628Service in display test mode.
        -dt N           Specifies which display type to use.
        -co N...        < D HH:MM > Order of display chars.
                        Valid values are 0 - 6.
                        (D=dots, represented by a single char)
        -h              This text.

LibreELEC:~/radni # dmesg | grep FD628
[   14.520222@4] FD628: vfd_gpio_clk:           #0 = 0x00; #1 = 0x41; #2 = 0x00;
[   14.520242@4] FD628: vfd_gpio_dat:           #0 = 0x00; #1 = 0x40; #2 = 0x00;
[   14.520249@4] FD628: vfd_gpio_stb:           #0 = 0x00; #1 = 0x42; #2 = 0x00;
[   14.520259@4] FD628: vfd_chars:              #0 = 0x04; #1 = 0x00; #2 = 0x01; #3 = 0x02; #4 = 0x03;
[   14.520270@4] FD628: vfd_dot_bits:           #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x05; #6 = 0x06;
[   14.520278@4] FD628: vfd_display_type:       #0 = 0x02; #1 = 0x00; #2 = 0x01; #3 = 0x00;
[   14.520288@4] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 65, offset = 220
[   14.520294@4] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 64, offset = 219
[   14.520301@4] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 66, offset = 221
[  251.455227@0] FD628: vfd_gpio_clk:           #0 = 0x00; #1 = 0x41; #2 = 0x00;
[  251.455241@0] FD628: vfd_gpio_dat:           #0 = 0x00; #1 = 0x40; #2 = 0x00;
[  251.455249@0] FD628: vfd_gpio_stb:           #0 = 0x00; #1 = 0x42; #2 = 0x00;
[  251.455258@0] FD628: vfd_chars:              #0 = 0x04; #1 = 0x00; #2 = 0x01; #3 = 0x02; #4 = 0x03;
[  251.455269@0] FD628: vfd_dot_bits:           #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x05; #6 = 0x06;
[  251.455277@0] FD628: vfd_display_type:       #0 = 0x02; #1 = 0x00; #2 = 0x01; #3 = 0x00;
[  251.455285@0] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 65, offset = 220
[  251.455291@0] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 64, offset = 219
[  251.455297@0] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 66, offset = 221
[  282.954994@1] FD628: vfd_gpio_clk:           #0 = 0x00; #1 = 0x41; #2 = 0x00;
[  282.955009@1] FD628: vfd_gpio_dat:           #0 = 0x00; #1 = 0x40; #2 = 0x00;
[  282.955017@1] FD628: vfd_gpio_stb:           #0 = 0x00; #1 = 0x42; #2 = 0x00;
[  282.955026@1] FD628: vfd_chars:              #0 = 0x04; #1 = 0x00; #2 = 0x01; #3 = 0x02; #4 = 0x03;
[  282.955037@1] FD628: vfd_dot_bits:           #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x05; #6 = 0x06;
[  282.955045@1] FD628: vfd_display_type:       #0 = 0x02; #1 = 0x00; #2 = 0x01; #3 = 0x00;
[  282.955053@1] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 65, offset = 220
[  282.955059@1] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 64, offset = 219
[  282.955065@1] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 66, offset = 221
[  347.826214@1] FD628: vfd_gpio_clk:           #0 = 0x00; #1 = 0x41; #2 = 0x00;
[  347.826229@1] FD628: vfd_gpio_dat:           #0 = 0x00; #1 = 0x40; #2 = 0x00;
[  347.826237@1] FD628: vfd_gpio_stb:           #0 = 0x00; #1 = 0x42; #2 = 0x00;
[  347.826246@1] FD628: vfd_chars:              #0 = 0x04; #1 = 0x00; #2 = 0x01; #3 = 0x02; #4 = 0x03;
[  347.826257@1] FD628: vfd_dot_bits:           #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x05; #6 = 0x06;
[  347.826265@1] FD628: vfd_display_type:       #0 = 0x02; #1 = 0x00; #2 = 0x01; #3 = 0x00;
[  347.826273@1] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 65, offset = 220
[  347.826279@1] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 64, offset = 219
[  347.826286@1] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 66, offset = 221
LibreELEC:~/radni #

After running "sh test_led.sh" command the display correctly displayed time with no additional icons.

After reboot it first displayes only correct time (no icons), and when Kodi comes up it messes up the display time and lights up almost all icons.

Will try to fix this, but if not, the correct time is what I seek, icons are not needed...

edit: Choosing "Defaults" in Settings for FD628 Display FIXED everything. And all works correct after reboot.

Will try tomorow again with v.8.2.4_OC images.

Quote from wrxtasy

Ahh Slide animations. Yes I see it now.

I don't like them either to be honest, they waste time navigating the GUI.

In fact I'm going to Nuke that option in future S912 releases.

It does just not work for me...

Fresh installs of "LibreELEC-S912.arm-8.2.4-Oclock-GPU.img" (even done once with your dtb.img file)

Running install.sh from your "FD628 Display.zip" results with:

Using username "root".
[email protected]'s password:
##############################################
#                  LibreELEC                 #
#            https://libreelec.tv            #
##############################################

LibreELEC (kszaq-wrx): 8.2.4-Oclock-GPU (S912.arm)
LibreELEC:~ # cd radni
LibreELEC:~/radni # sh install.sh
LibreELEC:~/radni # Open device failed.
: No such file or directory

LibreELEC:~/radni #

Nothing on display. Rebbot

Installing your service.fd628.zip (from FD628 Display.zip) -> nothing on display. Reboot

Placed vfd.conf in .config -> nothing on display. Reboot

Trying all posible driver configurations -> nothing on display

Tried several dtb.img files for old kernel and the only time I get something on display is when I use your "gxm_q200_3g_x92.dtb". But then the display looks like this: Image

In this case no settings can change anything on the display...

I'm giving up