Posts by kszaq

fatjanhushi  kostaman I have uploaded a .tar file with an update. Can you try using that one to update?

Mobigeek Thank you for the coffee! As for CEC, have you updated device tree? This is needed for both audio and CEC to work correctly.

Quote from quitroot

I do not know if this will help but I'm going to ask for the support of Videostrong. from which kernel the driver no longer fits?.

LibreELEC Amlogic kernl source: History for arch/arm64/boot/dts/amlogic - kszaq/linux-amlogic-le · GitHub

Some time ago I contacted Videostrong and they sent me some driver code (I am not allowed by Videostrong to share it) but it doesn't work - I don't know if only with current kernel or at all. This means that "some" driver source is not enough, the most important task is to make it really work. I have no knowledge of DVB drivers and so I will not work on internal DVB support.

Quote from quitroot

kszaq what about internal tuners (kii pro) would be future development? , or because the the kernel/driver issues it's stopped. Thanks in advance.

There is no driver for current kernel = no support.

Quote from Albundy

What is the difference dtb.img files between .008 & .009 builds. Aren't they standart structures for the hardware? Has Linux kernel way of reading dtb images changed between builds? Given the same hardware existing working dtbs should work on .008 or .009, right?

EDIT: unless you have changed dts file to add more hardware support...stock dtb image might have missing hardware definitions..i get it slowly

Amlogic is changing their drivers continuously, that's why device trees need to be updated. Take a look at commit log for device tree folder: History for arch/arm64/boot/dts/amlogic - kszaq/linux-amlogic-le · GitHub

Quote from zorrua

Thanks for the reply. I found this code: GitHub - gdachs/service.xbmc.amlogic-cec: CEC for amlogic devices

Could this code works with our devices?

Best regards.

It's probably for older devices using 3.10 kernel. Driver in 3.14 kernel is different.

Quote from kostaman

See screenshot.

It looks like the update wasn't successful at all. Can you try once again, this time without putting a device tree in Update folder?
[hr]

Quote from Miks

How difficult is add support for 912?
And please add information ram and rom amount, maybe in image name.

I do not have plans to support S912.

I don't have solution for this either but if you find a guide created for other device, like RPi I think you should be able to use it - we also use libCEC for CEC communication (although hardware implementation is Amlogic-specific).

kostaman Can you take a look at Kodi System Info screen? What Kodi version is shown there?

Quote from TheLegendOfMart

Is there any way of adding support for my TV tuner. It is a generic brand that is recognised as Geniatech T230 normally.

It might be supported by media_build drivers that are included in 7.0 builds.

OP updated with a new build. Main change is updated Kodi source, although not many changes will be visible. Amlogic hardware decoding is still a work in progress.

Quote from anthontex

I have a MXQ S85 and i've just updated from 7.0.2.5 to 7.0.2.7 and i noticed that now i get a dummy MAC address like 00:01:02 etc and not the original one: what could it be? Thanks

I suppose your bootloader adds that MAC address to kernel command line, doesn't it?
[hr]

Quote from felixob

I think the support for USB DVB-T dongles with Realtek RTL2832 chip is still broken. Is there a possibility to make it work in the near future?
I'm stuck at version 7.0.2.2 and I've tested al the newer versions without a hit. Maybe I'm missing something?

Sorry, I don't have RTL2832 device to test with. The issue is that the driver from media_build does not work and I don't think it's possible to include both media_build and regular drivers but I will check.

OP updated with a new build: fixed addons and bumped Kodi to latest master.

nemus It looks like there is an issue with writing device tree to internal memory. You can try installing LE to internal memory using recovery or keep running it from SD card.

Quote from Manahtar

It is for the S805 chip, but Kszaq copy-pasted the post for the s905 and didn't change it on the descritption

Whoops... Did not notice that. [emoji56]

Quote from jazzy

Where can I find device tree for 7.0.2.005?

There are no device trees for up to .005. You need a device tree from your Android firmware.

Quote from wkchick

Great, thanks. Hope the drivers source will be available soon and no more "ugly Hack" is needed.

Until someone ports the QCA9377 driver to compile in kernel tree, there will be the need to create the autostart.sh entries. The issue is that symbols in kernel-provided cfg80211 are different than in qca9377-provided cfg80211 and you need to load different cfg80211 depending on which wireless chip you have. I don't know a way to do this automatically and since most drivers use kernel-provided cfg80211, Aigalie chip uses will need to create that entry. You may ask why this works in Android? Because Android is built to support only one chip. My builds need to support multiple WiFi chips.

Quote from wkchick

Great, thanks. Hope the drivers source will be available soon and no more "ugly Hack" is needed.

The "hack" only involves adding a few lines to autostart.sh and you need to do this once.

Quote from atreyu

Nice, thanks.
Will you be adding access to the Libreelec repo / PVR addons in a next build ..?

Official LE addons repo is already included in both builds. I have just checked and I am getting 403 Forbidden error. Will look into this.

Quote from alon24

I had 008 on internal emmc.

I updated to 009 on my Internal emmc (not usb) but,
I did not put the device tree file in the update dir (stupid)
I now have no sound devices.
Can I fix this , or do I need to reinstall android and then install from sd card?

I am using Beelink M18

You can repeat the update procedure even if you're already running .009. That means that you can "upgrade" from .009 to any other build, even the same one.