Posts by GDPR-2

The Coolest please provide the DTS for any DTB's you modify as they need to be bundled with future releases in case there is changes to dts includes

Quote from rudi

GDPR-2

Thank you for your build. I am using it for Mecool K3 pro. I have a small problem with tvheadend. when using it for encrypted channels, it will continiously restart. Without any CA entry it is OK. When using a tvheadend build from K3 pro thread, it works. However, when stopping a recording tvheadends still thinkgs, recording is running. Any idea?

No idea sorry I don't have a dvb box, maybe afl1 can help.

Quote from hashmaker

Caro adamg hai notizie sul mio dtb.img? stavo postando il mio box-specs e il dtb.img da Android. Scusate non sarò fastidioso questo è solo per sapere notizie su di esso. Davvero grazie per l'interessante

io posso be a tester if u want

English please, I can't read a word of Spanish or whatever language this is

Quote from blackie

Where can I check the release notes for the new version 8.90.3 ?

No release notes for alphas or betas, you can look at the source code for recent changes, everybody tries to be as descriptive as possible with commit messages so you can view changes.

Quote from Tim_Taylor

Confirm - lcd is working

But - 4k video playback is broken - only 1080p works

4K is working with the latest Master with S912 (fixed by kszaq) but it presents us with other issues that I'm not prepared to introduce just yet because of the panic that is often created.

What source are you playing the movie from

Netwotk/USB?

If network are you using wifi or Ethernet? And are you using samba or NFS?

Quote from Adam86

Thought I'd take this build for a little test drive, however my Media Center remote doesn't appear to be working.

Running ir-keytable just says /sys/class/rc/: No such file or directory

Is this to be expected at this point? I.E this functionality hasn't come across yet?

Thanks

This is normal if you haven't installed crazycat drivers

Quote from AlexF

Does this mean S905X and other Amlogic devices may become officially supported Kodi builds (instead of community supported)?

Official Kodi no, Official LE yes and no, there will be a generic image but officially I think LE will only support SBC's

I can tell you from working on other VFD's that adding support for something like this is not easy or a simple request, it would be impractical for any developer to attempt to add support for this without access to the hardware.

Looking at the requirements for drivers to be added to LCDproc as well it looks unlikely that support for this device will be added for various reasons.

That doesn't tell us the CPU just the CPU family but I would steer clear, 512Mb just wouldn't suffice, it wouldn't even run Kodi under Android as it's minimum requirements for v17 if Android v5.0

Buy a tried and tested box, there is plenty of information within the forum already.

Quote from darioml

Hi!

I have just tried the following builds from adamg in a Vorke Z6 S912 box:

I installed the Add-on->Service->FD628 Display, but the LCD remains in "boot" the whole time.

I ran your test_lcd.sh without any error, but no change in the LCD. (BTW, give eXecutable permission to the FD628Service file in the zip). After a while I stopped it.

dmesg shows the following:

Code

[ 1528.063173@3] FD628: chars = ffffffc0b92e1f60
[ 1528.063185@3] FD628: chars->length = 5
[ 1528.063190@3] FD628: char #0: 4
[ 1528.063194@3] FD628: char #1: 3
[ 1528.063199@3] FD628: char #2: 2
[ 1528.063203@3] FD628: char #3: 1
[ 1528.063207@3] FD628: char #4: 0
[ 1528.063213@3] FD628: dot_bits = ffffffc0b92e1f90
[ 1528.063217@3] FD628: dot_bits->length = 7
[ 1528.063221@3] FD628: dot_bit #0: 0
[ 1528.063225@3] FD628: dot_bit #1: 1
[ 1528.063230@3] FD628: dot_bit #2: 2
[ 1528.063234@3] FD628: dot_bit #3: 3
[ 1528.063238@3] FD628: dot_bit #4: 4
[ 1528.063242@3] FD628: dot_bit #5: 5
[ 1528.063246@3] FD628: dot_bit #6: 6

Display More

Here is the content of the /proc/device_tree/fd628_dev in Android. I cannot find the dtb file. Where can it be? The /boot folder is empty.

Thanks for your efforts

Display More

The problem is there is no one size fits all where the DTB is concerned, it appears to be different for each brand/model of box. I will look at your files provided when I get chance thanks.

Quote from RayW

Whats wrong with the Tanix TX7 S905X box. Cheap and highly specced and supports UHD and gives HDR too though I only have a FHD TV with an excelletn picture quality right now as unable to afford to change TVs. I used the Beelink MXIII II S905X box before and that was even better but no longer available.

I'm also a fan of the Tanix boxes, the TX7 is probably the best one they made.

Quote from boot2k3

CEC problem solved in last devel build.

But the problem with my HDD still exist, it doesn't wan't to go in sleep mode after LE shutdown

May be some other fixes are not transferred to 8.90.x builds?

Did it enter into sleep mode in 8.2?

Quote from djnice

Please help!

Tvheadend service is not working, unable to connect to the server from web or local HTSP client.

This is the debug log: pastebin

KI Pro + LE 8.90.2 fresh install + plugins from the LE repository.

I have just done a fresh install tvheadend server 4.3 + tvheadend htsp client and no such issue, your problem is a configuration issue.

You can usually place the file inside of \\libreelec\Userdata

hashmaker upload your Android device tree and tell us which device you have, it can help narrow some things

Quote from alex0801

I have used 8.2, see link!

You wasn't very clear in your initial post, please wait for the next release as there will be a switch to the LE kernel which may solve your issue, it will require you using the 9.0 dtb then.

Quote from boot2k3

Display works, thank you. Locations are wrong, I will try to change them in dtb and will inform you about right locations later

Also in this build there are a lot of drop frames every second for IPTV simple

Code

[  306.835179@6] vidioc_qbuf skip: index:13041:13040
[  306.917115@6] vidioc_qbuf skip: index:13045:13044
[  306.935271@6] vidioc_qbuf skip: index:13048:13047

If you boot Android you should be able to get the original locations, The Coolest detailed how in a previous post, please post them when you have them so we can try to finalize this before the next build and make sure it's supported in future builds for you.