Posts by chewitt

Creds are stored in /storage/.cache/connman/<service>/settings .. where <service> is something unique based on the SSID used, etc.

However the file is "managed" by ConnMan so you need to stop the connman service to copy the file over and then restart connman. The challenge will be that when you stop or restart connman you may be disconnected. IMHO it's much easier to just re-enter the passphrase; and if you've chosen one that's long and complicated do it via SSH:

connmanctl

agent on

scan wifi

connect <service>

<enter password>

I reworked my codebase against LE12 earlier today and built an image (the 11.80.0 files in my webshare) .. which continues to work fine with both multi-channel PCM and PT audio. The only explanation that makes sense to me is that there's something off with the EDID data on your HDMI connection.

I have no futher plans to develop/work on the LE11 codebase so this thread has been locked and un-pinned. I hope you enjoyed the ride

The conversation continues on LE12: Official LE12 Test Images for Amlogic (Kodi-21)

This thread is for discussion of AMLGX (aarch64) development images for LE12 with Kodi 21 (Omega). There are no real-world "Amlogic" enhancements in LE12 over LE11 images so please read the previous disclaimers on what does and does not work in LE11 release announcements and avoid posting "bug reports" on hardware decoders; they are not complete code, there are known issues, and you should expect to find them. As a general rule there is a low pace of development and you should have similarly low expectations of fixes.

Official nightlies: https://test.libreelec.tv/12.0/Amlogic/

Experimental builds: https://chewitt.libreelec.tv/testing/ <= You will receive zero support on these images. They are experimental.

Enjoy

2023-09-03 11:54:33.398 T:1004    error <general>: SQL: Can't create database for copy: 'MyVideos121' (1007)

^ I'd guess the MySQL user has read/write permissions within the current DB but not rights to create/fork a new DB.

If you're using official LE11 images (release or nightlies) please update to https://chewitt.libreelec.tv/testing/LibreE….arm-11.0.3.tar and see if that makes a change?

Quote from frakkin64

Does anyone know how to do a clip and copy all of the problems with it? The original file is 2GB.

You can use 'dd' for that.

SSH can support certificate authentication instead of password authentication. Once certificates are set-up you can enable the "disable passwords" option. It's one of those IT things where the phrasing is both correct and terrible.

Nothing left out, but we switched from the third-party NTFS-3G driver to the upstream/in-kernel NTFS driver which seems to be a little more excitable at flagging unclean filesystems or similar things. You probably need to connect the drive to a Windows box and run checkdisk to have it mount.

PuTTY caches keys locally and you probably need to clear the cache. The disable passwords setting must be OFF too.

Quote from frakkin64

It would be a useful feature as Amlogic mainline also has MPEG2 HW decoding problems.

AMLGX includes this for a while now: https://github.com/chewitt/linux/…23a7a19f2d0ba9e

Add "textmode" to boot params and the board should boot to a local console instead of starting Kodi, and you can connect a USB keyboard to poke around and see if there are any interesting errors. You won't be able to start Kodi, but it will maybe help to prove/isolate whether the issue happens before or after Kodi start. I'd guess during/after.. but let's see.

This seems to hint at power issues: https://github.com/raspberrypi/linux/issues/4130

It's not possible to force connection to a specific band, the connection manager will prefer whatever provides the strongest signal. You might find that setting wireless regulatory domain helps the client device see all frequencies available on the router.

Any difference if the device is connected before power-on/boot? (prob. not, but will ask anyway)

Quote from quosek

Is there any other way of installing torrent client on LibreELEC ?

The danger of hijacking other people's threads is people get confused. The OP had an RPi3 .. and you have different hardware.

In both cases the current Linuxserver container appears to be armv8/aarch64 only which means it will not run on any current LE release. It will run on the LE12 nightly for RPi2(3) boards as we switched to aarch64 there. It will not run on any Generic image which needs x86_64.

There are probably other container sources out there if you look for them.

However this is the correct subforum and I already binned the other thread .. so you might want to revert your changes.