[8.0.2e] LibreELEC 8.0 for S905/S905X

kszaq I understand that changing the default to be safer for majority of users is a useful and good thing, but could you add an option or tell us how to bring it back manually for those damned souls with a working suspend? Cheers!

Quote from kszaq

There are less options in power menu because I disabled suspend (again) - it fails for 95% of users and because it's default option for CEC behaviour on TV off, many people have frozen boxes after they turn their TV off. I don't want that.

Quote from kszaq

Nofan Tasi dvb_tv source is now up to date.

thanks, I start 64bit build.

kszaq Maybe its on my side but when I try to build the 8.0.2e I get this error while compiling linux

drivers/built-in.o: In function `spicc_set_mode':
hdmi_ao_cec.c:(.text+0x2b781c): undefined reference to `setb'
hdmi_ao_cec.c:(.text+0x2b781c): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `setb'
hdmi_ao_cec.c:(.text+0x2b7830): undefined reference to `setb'
hdmi_ao_cec.c:(.text+0x2b7830): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `setb'
hdmi_ao_cec.c:(.text+0x2b7844): undefined reference to `setb'
hdmi_ao_cec.c:(.text+0x2b7844): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `setb'
drivers/built-in.o: In function `spicc_cleanup':
hdmi_ao_cec.c:(.text+0x2b7a14): undefined reference to `setb'
hdmi_ao_cec.c:(.text+0x2b7a14): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `setb'
drivers/built-in.o: In function `spicc_set_clk.part.2':
hdmi_ao_cec.c:(.text+0x2b7aa4): undefined reference to `setb'
hdmi_ao_cec.c:(.text+0x2b7aa4): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `setb'
drivers/built-in.o:hdmi_ao_cec.c:(.text+0x2b7bb4): more undefined references to `setb' follow
drivers/built-in.o: In function `spicc_setup':
hdmi_ao_cec.c:(.text+0x2b7bb4): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `setb'
hdmi_ao_cec.c:(.text+0x2b7be4): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `setb'
drivers/built-in.o: In function `spicc_probe':
hdmi_ao_cec.c:(.text+0x2b7e18): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `setb'
hdmi_ao_cec.c:(.text+0x2b7e2c): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `setb'
hdmi_ao_cec.c:(.text+0x2b7e40): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `setb'
hdmi_ao_cec.c:(.text+0x2b7e54): additional relocation overflows omitted from the output
drivers/built-in.o: In function `spicc_hw_xfer':
hdmi_ao_cec.c:(.text+0x2b81b4): undefined reference to `getb'
drivers/built-in.o: In function `store_test':
hdmi_ao_cec.c:(.text+0x2b84d0): undefined reference to `setb'
hdmi_ao_cec.c:(.text+0x2b8544): undefined reference to `setb'
drivers/built-in.o: In function `spicc_work':
hdmi_ao_cec.c:(.text+0x2b86a0): undefined reference to `setb'
hdmi_ao_cec.c:(.text+0x2b86cc): undefined reference to `setb'
hdmi_ao_cec.c:(.text+0x2b877c): undefined reference to `setb'
make[1]: *** [Makefile:841: vmlinux] Error 1

But not sure if its on my side or something that recently changed.

Hey kszaq,

Great image!

Would it be possible to implement a hq-upscaler like lanczos?

SD upscaling looks very blurred. If i play the same file on TV media player it looks sharper.

Another possibility would be 576p HDMI output so that the TV does the upscaling, but I think Kodi don't support that?

Thanks

Hi kszaq,

I've been compiling your tree since v7.0.2.009 along with a `hostapd` package I wrote myself, and everything was working fine when setting up a network on `wlan0` (just had to ask `connman` to ignore this network device).

However since the 8.x upgrade trying to run `hostapd` on `wlan0` fails massively, the program segfaults and then the box (S905x) enters a boot loop. That makes no sense to me, as everything used to run just fine, I've tried downgrading `connman`, upgrading `hostapd` (2.5 → 2.6), using the proper DTB as opposed to the master one compiled… The only thing I haven't tried is downgrading the kernel because it's not as simple as changing the hash in the `options` file, and the `rtl8189es` driver hasn't changed anyway.

Do you have any hunch as to what could possibly be going on please ?

`hostapd` log:

random: Trying to read entropy from /dev/random
    Configuration file: /tmp/hostapd.conf
    drv->ifindex=3
    l2_sock_recv==l2_sock_xmit=0x0x750ae8
    BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
    Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=0 dBm
[…]
    Allowed channel: mode=2 chan=165 freq=5825 MHz max_tx_power=0 dBm
    Completing interface initialization
    Mode: IEEE 802.11g  Channel: 6  Frequency: 2437 MHz
    DFS 0 channels required radar detection
    RATE[0] rate=10 flags=0x1
    RATE[1] rate=20 flags=0x1
    RATE[2] rate=55 flags=0x1
    RATE[3] rate=110 flags=0x1
    RATE[4] rate=60 flags=0x0
    RATE[5] rate=90 flags=0x0
    RATE[6] rate=120 flags=0x0
    RATE[7] rate=180 flags=0x0
    RATE[8] rate=240 flags=0x0
    RATE[9] rate=360 flags=0x0
    RATE[10] rate=480 flags=0x0
    RATE[11] rate=540 flags=0x0
    hostapd_setup_bss(hapd=0x751170 (wlan0), first=1)
    wlan0: Flushing old station entries
    Segmentation fault

write(1, "hostapd_setup_bss(hapd=0x1f6170 "..., 50hostapd_setup_bss(hapd=0x1f6170 (wlan0), first=1)
    ) = 50
    write(1, "wlan0: Flushing old station entr"..., 36wlan0: Flushing old station entries
    ) = 36
    ioctl(4, _IOC(0, 0x8b, 0xfc, 0x00) <unfinished ...>
    +++ killed by SIGSEGV +++
    Segmentation fault

It definitely looks like a driver issue (because of the `ioctl` call), but I don't understand why this issue would completey lock the device up in a boot loop afterwards.

Thanks.

Quote from kszaq

Upscaling is done by hardware if HW decoding is enabled, for SW decoding S905 is not powerful enough to provide Lanczos.

OK, but it looks like in this file

linux-amlogic/vpp.c at amlogic-3.14.y · 150balbes/linux-amlogic · GitHub

there are different HW scalers.

Is there a possibility to use the different ones like COEF_3POINT_BSPLINE maybe through /sys/module/amvideo/parameters/ ?

Hi Kszaq,

First of all, thanks very much for your work. I still enjoy your 7.x build every day as it works flawlessly.

I was waiting to upgrade to v8, as i am using a (partly) IR remote with my bluid-in receiver (minim8s).

Happy to read buildin IR receivers should be supported in 8.0.2e, so i installed a fresh image.

Unfortunately, IR is still not working with this build. Totally unresponsive to remote commands with both a standard dtb and a lirc one.

Amy chance that IR will return to function as it did in v7..?

Regards,

Atreyu

I have a newbie question to ask.

I am successfully updating kzaq's versions with no issue at all. I do that by putting the .tar file into the update folder.

I would like now try to update the dtb file. How do i do that?

Thank you.

Quote from kszaq

If you don't use LIRC device tree, IR works exactly the same as in 7.x.

Thank you.

I copied a remote.conf from an identical box that still had Android on internal storage, put it in the .update dir and rebooted. IR now works

In my case, v17 is not ready for prime time yet, though as channel switching times are (very) slow still. Especially HD channels.

A very good build anyway, you do great things for amlogic users!

Quote from gxaris

I have a newbie question to ask.

I am successfully updating kzaq's versions with no issue at all. I do that by putting the .tar file into the update folder.

I would like now try to update the dtb file. How do i do that?

Thank you.

Procedures are described in detail by kszaq on the first page. You cant go wrong.

Let me help you out; just find the proper .dtb file from the location mentioned on the first page. Grab the proper one for your box (make sure memory and ethernet values match) and replace the file on your SDCard after burning the image. Boot. Done.

PS: Note that if you have a s905X box,or are using a existing device tree that works , replacing the device tree might not be needed. Just leave it.

Quote from lenormf

Hi kszaq,

I've been compiling your tree since v7.0.2.009 along with a `hostapd` package I wrote myself, and everything was working fine when setting up a network on `wlan0` (just had to ask `connman` to ignore this network device).

[…]

It definitely looks like a driver issue (because of the `ioctl` call), but I don't understand why this issue would completey lock the device up in a boot loop afterwards.

I tried using the upstream `amlogic-3.14` kernel, and the same issue doesn't occur, I reckon something in the patches added to the fork is causing these issues (using `wlan0` as a regular device seems to work).

Quote from 3legcat

Just tried spare usb controler and it works fine. It seems I can use original remote that came with the box to switch on the box but after that it doesn't work at all. I could use original remote to switch on the box and use my other usb remote for everything else but ideally i would like to use original remote only. still stuck don't know what to do

Try copying the remote.conf from the original Android source for your box to the .update folder of your current 8.0.2e install. The reboot. That worked for me.

The file should be in the /etc dir in Android.

Quote from atreyu

Procedures are described in detail by kszaq on the first page. You cant go wrong.

Let me help you out; just find the proper .dtb file from the location mentioned on the first page. Grab the proper one for your box (make sure memory and ethernet values match) and replace the file on your SDCard after burning the image. Boot. Done.

PS: Note that if you have a s905X box,or are using a existing device tree that works , replacing the device tree might not be needed. Just leave it.

Since it's about updating an existing running system it's a lot easier to just put the dtb file in the update folder, next to the update image/tar and reboot. No need to do anything manually with the SD card.

Quote from Forage

Since it's about updating an existing running system it's a lot easier to just put the dtb file in the update folder, next to the update image/tar and reboot. No need to do anything manually with the SD card.

True.

Was doing a fresh install myself that's what confused me

i have wetek play 2 i have test your version and is working ok what i notice i that max cpu is in 1536000 instated of 2016000 kszaq is it possible to onlooke it?