The AMD APU doesn't support x265 hardware decoding, it doesn't support UHD.
Posts by The Coolest
-
-
You don't need to change the Sound output from 2.0 when you enable Passthrough.
The point of passthrough is that audio is passed through the device and out to the receiver as digital data, no processing takes place in LE/Kodi.
I think I read that you actually should keep it at 2.0 to prevent any extra processing, but I could be wrong about this.
-
Thanks for the correction, got confused with the S812
-
You can't do that with an Odroid C2, as far as I know it uses S905 which doesn't support HEVC 10 bit decoding. -
-
You can also use Notepad++ to edit the files, go to Edit -> EOL Conversion -> Unix (LF), then save the file and copy it to the appropriate place in the shared config folder.
You still need Putty to run the commands, SSH basically gives you your box'es (linux) command line through Putty.
-
Make sure that Amcodec is enabled in Video settings.
-
Make sure that you use the X92 DTB. Index of /releases/dtb/S912
Edit: As far as I'm aware, the main difference between Q201 and Q200 is the ethernet connection (100M vs 1G).
[8.90.4] LibreELEC 9.0 Alpha for S905/S912 devices
gxm_q200_3g_x92.dtb should get the clock working,
-
Thanks for the photos. The chip is FD628, in the first pic.
My box, T95m, has the same chip and display (FD628 and the same display).
I believe the Tanix TX3 have the same display, but boxes like the ABOX A1 Max (or A95X R2) and the X92 have different displays.
Sometimes the chips can be FD628 compatible, like HT1628 or something else, but in the end they all work the same way. The main challenge is to figure out the correct configuration the manufacturer used in their implementation.
Again, to get your icons working, you need the Kodi add-on, just go to add-ons and search for 'FD628', it should come up with one result, install it, and you should see the icons.
T95Z is supported, it has been tested and working by other users.
-
To get the icons to work you need to install the fd628 service add-on from the LE repository.
-
Starting with GDPR-2 's 8.90.6 build and all CoreELEC builds, the display system has been changed.
You don't need a 'custom' DTB anymore, but you will need to update to the newest DTB available in the SD card root/device_trees folder. All that is required now is a vfd.config file with the appropriate configuration placed in /storage/.config/ or Configfiles from the Samba share.
There is a repository with known and supported boxes, which you can access here: GitHub - arthur-liberman/vfd-configurations: vfd.config - A collection of configuration files for linux devices with a front facing display.
You can see examples from the existing files, and there is an extensive explanation about how this file should be configured.
So essentially, you can do it yourself, as long as you know the configuration of your display. If you do create a new configuration for a box that is not in the list, please create a Pull Request to the repository with the new file, or at least post it here so I can add it for everyone's benefit.
The FD628 Service Kodi add-on has been updated as well, check out the configuration dialog to see the new features.
I'm working on adding support for the front displays that many Android TV boxes come with to LibreELEC.
In Android they always work, but in LE most of them don't. We began changing this with adamg's 8.90.4 release.
So I'm looking for people who have boxes with front displays that don't work at all or work incorrectly in LibreELEC to add proper support for them into future builds.
Currently known boxes that work:
T95m, T95Z, X92, Vorke Z6, Tanix TX3 (mini), ABOX A1 Max.
* If the display works, but you're missing the additional icons (ie. wifi, lan, usb, etc.), first of all make sure that you install the FD628 Display service add-on from the LibreELEC repository.
If you have a model that is not in the list and you'd like to have it supported, I will need the following:
1. Exact model and SoC version of your box.
2. The DTB from the built-in Android. How to extract DTB from Android.
3. Which DTB you are using with LibreELEC.
4. Only if possible, I need to know what display controller chip your device has. You'd have to disassemble it, or find a review where it's disassembled. It's a chip found close by to the display, like this example (only make sure the text on the chip is visible or write it down)
-
kostaman.
EgoIggo S95X Pro Android 6.0 TV Box Smart TV Box mit 2GB Ram+16GB eMMCgxl_p212_2g_nand.dtb or gxl_p212_2g.dtb this normal my correct device tree
-
Yes, but you have to realize that Leia builds are currently pre-alpha. They can be unstable and "high-maintenance".
Some boxes need to have new remote configurations made for them, for example.
You also must update the DTB when you upgrade to Leia, and I don't know if you can later downgrade. You couldn't downgrade when going from LE7 to LE8.
So if you want to try it, first create a backup of your current setup, so that you can go back to it later if needed.
-
He answered that question many times. He's no longer working on these builds.
He's helping with Leia builds.
-
Then there's no way to tell for certain. There are video patterns you could run and try to see the difference between 8 bit and 10 bit, but it's not very effective.
-
-
Have you went into audio settings (Settings -> System -> Audio, make sure you're set to Expert) and select the correct audio device with the proper passthrough configuration?
-
There is no 'best settings', these settings are used when you have compatibility issues with your TV (RGB) and the 10 bit options are good for 4K HDR TVs.