Posts by chewitt

Quote from AHMEDLEILA

Do I need to rename dtb file into dtb.img

No. Please read the wiki article I linked.

Quote from iirigoyen

I would like to be able to put the operating system inside on the internal. I have a beelink gt 1 ultimate. Is there any option???? thanks for letting us keep using nexus. It would be great to be able to put it in the internal memory.

Not supported and no plan to support: https://wiki.libreelec.tv/hardware/amlog…s-android-boxes

Also note that there is no support for the internal DVB tuners (and that's unlikely to change)

Quote from AHMEDLEILA

Please help me to use LibreELEC on my almogic s912 box (MAGICSEE400 PLUS)

Which version should be used?

How can I install on my flash memory?

Thanks in advance.

You should be able to install the AMLGX "box" image, read https://wiki.libreelec.tv/hardware/amlogic

You will need to experiment with meson-gxm-* device-tree names in uEnv.ini as there is nothing specific for Magicsee 400+ right now. Most boxes are quite similar though, so it's easy to find something.

NB: We do not support internal installations on Android boxes and older scripts will (100% guaranteed) brick things if used.

If there was write protection on eMMC all writes would fail, so partial write (7%) means there is probably an issue with the eMMC chips, or the power supply which causes instability during writes. It's a common issue with older and cheaper Android boxes due to age/wear on eMMC chips and the low-bin/low-quality components used.

7% restored means that some boot code (u-boot) exists on the box now and this should be enough to boot LE from SD card. We don't support installs to internal storage on random Android boxes so you will need to run LE from an SD anyway. Use the AMLGX Android "box" image with the toothpick method to hook into u-boot. You will need to experiment with different device-tree filenames in uEnv.ini to find something that works with your box. If the box has Gigabit Ethernet the S905D vero4k-plus dtb will probably work. If the box has 10/100 Ethernet the p212 dtb should work.

Did you migrate the HDD from an older device to the newer one?

If yes, do "systemctl stop kodi && mv /storage/.kodi /storage/.kodi-old && systemctl start kodi" as an experiment to see if moving all the old config out of the way resolves something.

2023-01-30 20:58:25.001 T:770 debug <general>: CDRMUtils::SetMode - found crtc mode: 3840x2160 @ 60 Hz
2023-01-30 20:58:25.001 T:770 debug <general>: CGBMUtils::CreateSurface - created surface with size 1920x1080

^ that looks wrong to me

It's odd that it claims to have no ELD data, but then finds all the resolutions and there is HDMI audio showing. It might be a case where the upstream drivers are still work in progress.

I've flagged this internally. The debate will be whether we fix this in the settings add-on, or simply add comments to the release notes that nVidia users need to do a file-based manual update and not use the GUI. These days the number of nVidia users is low (and continues to trend downwards) so we're reaching the point where effort vs. reward doesn't always inspire effort.

Quote from Mario77

On Rpi2 if you update from LE addon it's downloading 10.0.4 instead of this.. and after update I was still on 10.0.4..

Select manual updates, change to the LE11 update channel, then select/download the 10.95.0 update and reboot.

Most improvements to Intel and AMD drivers come from the vendors themselves. And because none of the TV manufacturers are creating new TVs with 3D capabilities now (the 3D fad has passed) there's no "business" demand for 3D features; only from end-user consumers who don't puchase silicon chips in volume quantities and so aren't important.

Quote from f3jeff

Maybe someone in there wants to watch the new Avatar in 3D at their home, you never know 😛

These days almost no new TVs support 3D (the fad has passed) so that is probably the only hope of it being done.

Kodi is a player app running on video output hardware connected to your TV. If the video output hardware can connect to the DAC over USB then Kodi should be able to see/select the DAC as the audio output device. Kodi is not an audio server/streaming app so it will not be able to send/stream audio to the DAC over Ethernet.

There appears to be a Tidal add-on for Kodi https://github.com/arnesongit/plugin.audio.tidal2 but have never used it. The support thread in the Kodi forums appears to be active https://forum.kodi.tv/showthread.php?tid=200555

There was a Qobuz add-on but it appears there were changes to the service that broke it and the add-on doesn't appear to have been updated since, see https://forum.kodi.tv/showthread.php?tid=146568 and https://github.com/tidalf/plugin.audio.qobuz

The AMLGX image can support an S905W box but (to state it again clearly) it has no support for 3D media. The legacy kernel S905 image has some level of support for 3D media (but never tested by me .. I never bothered with 3D hardware or media) but here is no longer any support for the legacy S905 image and I doubt it works with a random S905W box.

It might not have been the "Yes, please purchase some cheap rubbish Android box and we'll make it work for you" answer you wanted, but if you want good 3D support on a cheaper device .. I gave you an option.

run "pastekodi" and share the URL please

The default Library is designed to scrape and add files but not auto-delete them. Installing the "Library Watchdog" add-on from the Kodi repo should give you what you want.

English language forum (es tut mir leid).

You moan wish is granted..

Quote from tinca

I am upgrading from 9.2.8 which worked fine. Now, after upgrade LibreELEC keeps crashing/rebooting until finally loads into safe mode.

So apparently your upgrade which worked fine, is not fine. This is self-inflicted punishment for ignoring all the DO NOT DIRECTLY UPDATE FROM LE9.x to LE10.x (or LE11.x) BECAUSE IT WILL CAUSE PROBLEMS type warnings and blog posts we made in the last 18-months since LE10 launched advising everyone to do a clean install. In 99% of cases the problem is older Python2 add-ons which are not compatible with the now Python3 only environment .. causing Kodi to crash when it loads them.

If you can SSH in "systemctl stop kodi && mv /storage/.kodi/addons /storage/.kodi/addons-old && systemctl start kodi" should solve the initial problem by removing all add-ons; allowing Kodi to start without crashing. Then you can (re)install them from compatible sources.