I merged posts back to this thread.
Posts by chewitt
-
-
I don't have any Dreambox hardware, and in the several years since I added upstream support for _emanuel_ nobody has ever bothered to explain (or, here's a crazy idea, add some content to the open wiki to document) that Dreambox devices require some wonky boot arrangement to run the AMLGX image. That only became clear about a week ago, and If I'd have known that before I probably wouldn't have bothered creating and sending the device-trees upstream. Ho hum.
The latest Dreambox device(s) that _emanuel_ is now asking me to support are Android based, so that's been on my mind among other things. Yes of course the older stuff uses Yocto/OE to make something from the Android BSP from Amlogic. Regardless, the point still stands: If you want an OS where everything works, you need to run the vendor firmware image.
The AMLGX image is generally curated to use the best (or newer hardware, least-worst) default settings. You can use 4K VP9 as that works, but you will not get far with 4K HEVC because hardware decode is intentionally disabled to prevent the SoC crashing instantly when the V4L2 codec is opened, and that caps HEVC to 1080p max in software. Forcing EGL rendering instead of Direct-to-Plane only loses the benefits of DRMPRIME and makes things worse; and hence I stopped reading the 'testing' .. it's obviously a user flailing around with random settings in the hope of finding a magic combination that beats the negative but clear description of current state provided in release notes. Good luck with that.
-
Things moved forwards, but overall not much changed. Amlogic engineers recently submitted support for DRM (video output) and audio support on S4 devices (must-haves for an LE image) but all their patches are poor quality and require many iterations to adapt to upstream standards. They are also slow at iterating, so it will be a while before those changes get merged. I've made a note to ask Khadas for a VIM1S sample (S905Y4, so related to S905X4) to explore packaging.. but I have low expectations of doing much with the board for a while yet.
-
LE12 (12.0.0/12.0.1) extended CEC support to multiple HDMI connectors, but it has proven to be troublesome, so LE 12.0.2 removed this and CEC is now only supported on the HDMI connector nearest to the power connector.
-
Remove any boot config. Put Kodi in debug mode. Clean boot then share the URL generated by "pastekodi" please.
-
-
If everything works when navigating with the keyboard but not with Yatse, that sounds like an issue with Yatse, and you should report the problem to Yatse's creator.
-
-
I'm going to guess that Kodi settings is not in advanced/expert mode so while you enabled PT audio at the top level, you cannot see (and thus have not enabled) PT for individual audio formats like DTS, AC3, etc. so they are being correctly (as configured) sent as PCM audio.
-
Congrats. You spent ages looking at the log file and carefully extracted a segment that shows nothing. In a future post please share the entire debug log so we can understand actual system state and have something useful to look at.
-
Clean install an LE13 nightly and prove the issue exists there first.
-
Even if you can point to something in LE11 or LE12 the next thing we're going to tell you is "update to an LE13 nightly and confirm the issue still exists" .. so better to move forwards with testing than backwards.
-
I've not bothered to read the full contents of your test report. I stopped about 10% into the text; by which point it's obvious that you are a) expecting feature parity with Amlogic vendor kernel images, b) blindly changing settings expecting miracles. Please go read any recent LE release notes (anything from the last couple of years) which contains clear statements on the current state of mainline kernel Amlogic support (nothing has changed much in years). What worries me the most is users with wildly unrealistic expectations for the AMLGX image because they don't read.
NB: You are welcome to continue experimenting with AMLGX, but I don't need bug reports. The issues and current state are all well known (and documented). You are also welcome to continue using the factory Android image, which works, with all features.
-
To be specific, we want to see the system log (not a Kodi log). Run "journalctl | paste" after boot and share the URL.
-
Impossible to answer without seeing a Kodi debug log and system log .. preferrably copied to pastebin as downloading logs from the forum is a pain in the arse.
-
It's not clear to me what you are trying to do .. where do "rules" come from?
For context: not German so not using "radio.de" but Groove Salad is playing fine here using the "SomaFM" addon.
-
1. Yes; except for auto-update of the LE image itself (which you don't want as it doesn't contain the TBS driver).
2. Yes (to all Qs). Just scp the built image to /storage/.update on the box and reboot.
It's worthwhile learning the git basics of committing a change (that adds the patch) to a local topic branch so that you can later git fetch upstream changes (when we publish a maintenance release) and rebase the local topic branch against our upstream changes before rebuilding the image to include the upstream changes.
-
At first it seemed the playthrough was smoother but then the rpi4 started making noises I've never heard before. And I don't even have a fan. Nor heatsink. Just using the official case with the top off.
The boards are designed to run hot but will self-preserve by throttling back. You can't (and shouldn't) run overclocked boards without active or good passive cooling.
