Posts by kszaq

Latest development build uploaded: 2016-09-25-devel

I may have fixed suspend in this one (for both Broadcom and Realtek WiFi). A fix was trivial yet I spend almost 3 days looking for it...

Latest dev build should have sound issues fixed (please use 7.0.2.007 device trees): 2016-09-25-devel

Here's a test build with some new CEC patches: 2016-09-25-devel

I make no promises on it as I'm not familiar with CEC implementation on S905 boxes.

Please test a build with different approach on setting output_rgb: 2016-09-25-devel

Here's a build with patches from pec and chbmuc: 2016-09-25-devel

First, please read the rules on reporting bugs: LibreELEC

You shouldn't have posted this bug in General Support area since a) these are "Community" builds, not supported by LE team and b) I never look at General Support Forum.

In most cases I need full system log to look at the issue, Kodi log is not enough.

A workaround for you would be to use 1080p60 instead of 720p60 for GUI.

Follow instructions: HOW TO:Update LibreELEC - LibreELEC

I will post an image without a boot issue and working sound today (I think).

There are some improvements to CEC implementation from Kwiboo that are scheduled for the next build. I will ask you to re-check when the build is ready.

Quote from oksmb

The S912 is basically a rip off in my mind. The only reason box makers are putting it in their boxes is to make a buck off people who don't read the specs. There is no real advantage over the S905X for watching videos or viewing pictures, yet it costs much more because of the increased core count and "gaming" GPU.. Bottom line is if you want a premium TV box you are better off spending your money on a well-supported S905 box like the Wetek Hub rather than a generic S912 box. The problem you are facing is more likely related to software limitation/bugs than hardware. The hardware of the S905 is capable of 4k.

Another factor is that all of this development is tied to what is going on with the Wetek boxes and the Odroid. Neither of those players are jumping at the S912 (because it is a stupid chip to put in a TV box) so there is no development happening whatsoever for that chip and I wouldn't expect any in the future. If Odroid or Wetek build anything with the S912 I will be very surprised.

While I agree that there is no reason to buy S912 over S905 for LibreELEC I have to disagree on development tied to WeTek and Odroid devices: these vendors do drive development for Amlogic - Codesnake working for WeTek on improving Kodi support, WeTek and Odroid donating devices and providing great support, working on kernel improvements - but as long as Amlogic provides source code and binaries for the newer chips it should be relatively easy to build LE for them. All you need is someone who takes his free time and devotes to making it work. Example: my builds for S805.

Looks like you have a multi-dtb file. Maybe there's a tool for that but what I do is I look for D0 0D FE ED magic in Hex editor and then use dd to cut the file. For example, first device tree is always at 0x800 so you want need run dd bs=2048 skip=1 if=source.dtb of=dest.dtb.

Quote from Pelican

Could you be more specific?
Not now or never?
What's wrong with the S912?
Not even if somebody send you an S912 player?

It means that I hardly have enough time to support S805 and S905. You have to remember that I have a family and a day job.

Quote from dareks79

Hi kszaq,

Last week you have promised version with DVB driver for K1plus.
Could you let know what is the status of that?

Best regards
Darek

Promise is a strong word in my language and I only said I will try.

I don't have a device with built-in tuner so I did some testing with envagyok and so far none of the drivers worked. I'm very short on time recently so the process is slow. I think I will try 2 more approaches to this and hopefully one of them works. If none of them does, I will give up on trying to make internal tuners work.

edit4ever Can you please post the zip file with log when you use the latest device tree?

ippon Can you try running this command over SSH: echo "44.1k" > /sys/class/amhdmitx/amhdmitx0/aud_mode?

Joint dtb is available in SD card image already. I provide separate dtbs as some vendors remove multi-dtb support from u-boot.

1280x1024 is not available in kernel.

You can try using gxl_p212_1g.dtb or gxl_p212_2g.dtb from device_trees for HD Audio. I will add channel mapping-related changes later.