Posts by lrusak

You will most likely have to modify the regex depending on the name of the files you want to use also.

Quote from dummys

Yes But there is not all possible variables. Did you have such documentation ?

No

Quote from Tec79

The problem still exits in 7.95.3, but I can provide additional information:

The issue disappears if I deactive IPv6. Is it possible that "Wait for network" stops waiting if IPv6 connections are possible even IPv4 aren´t? IPv6 is "automatic", IPv4 is "DHCP" - so it is possible that the IPv4-Stack waits for an DHCP response while IPv6 is working?

This is possible yes.

Must be wrxtasy builds....

Hmm, the device should be supported by default

Add TP-Link devices · Mange/rtl8192eu-linux-driver@56ccb6b · GitHub

I'm not really sure what to tell you. can you post your dmesg?

[code]
dmesg | pastebinit
[code]

try adding ip=dhcp to the end of cmdline.txt

I've experienced this as well. I haven't found a solution yet though.

That all looks pretty good to me.

can you post the output of the following command?

pactl list short sinks | pastebinit

Also can you make sure the volume in kodi isn't muted (dumb question but you never know).

Also a kodi debug log while playing something through the bluetooth speakers would be great

pastebinit /storage/.kodi/temp/kodi.log

You'll just need this

PKG_NAME="mt7610u_wifi_sta_v3002_dpo_20130916"
PKG_VERSION="2ecaea4"
PKG_URL="https://github.com/luben93/$PKG_NAME/archive/$PKG_VERSION.tar.gz"

There is some documentation here, LibreELEC.tv/README.md at master · LibreELEC/LibreELEC.tv · GitHub

Quote from dummys

I put a lot of debug string in the build, and I found that the faulty one was md5sum. I'm sure of it...

Edit scripts/get and put "set -x" at the top

then call the script directly

PROJECT=<someproject> ARCH=<somearch> ./scripts/get configtools

then post the output here

• I'm not sure. There maybe scripts in the unofficial builds you are using to try and boot from external storage.
• using HFS+ formatted disks in linux will mount them read only when journaling is enabled. So you have two options:
  
  
  • disable journaling (not recommended)
  • format the external drive to exfat (useable on all operating systems) (you'll have to move all the data on the disk, format and move the data back).

Did you disable lirc in the LibreELEC settings add-on under the services section? (Only in LibreELEC 7.95.1 or newer)

You can't. Flirc will pick up any MCE remote.

When using flirc lircd isn't even used unless you have a separate IR receiver

Quote from Tim_Taylor

I did it and it works running kodi on ubuntu linux

Please don't tell me I'm wrong unless knowing all facts.

Please try it on LibreELEC and report back

LibreELEC != Ubuntu

I don't know what to tell you. Clean up your install and try again. Remove whatever you have in your autostart.sh file and do what I did. If it doesn't sleep 30 seconds then something is broken on your installation.

Quote from ramses3

Thanks for your reply dude, i tried the autostart.sh sleeptime also with 30 seconds..no function at all.
can you explain me what the thing does what you posted on aKZc ? i can see its doing a 2 sec sleep , but on what point? as you can see on the log i posted, no matter where i put delays before (autostart.sh, wait for network on kodi) it doesnt change anything.

I just tested with

echo "sleep 30" > /storage/.config/autostart.sh

and my system waited 30 seconds on the splash screen.

The kodi-waitonnetwork.service file adds a "sleep 2" command that runs after connman-wait-online detects a network.

Quote from Frisk

Does the led of your xbox 360 controller blink or not? Because I encounter problems with this actually on s905 libreelec build.

Do you know how can I fix this?

Thanks

It's because of the old out of date 3.14 amlogic kernel. This has been fixed IIRC in the upstream kernel.

Not sure if the xpad driver can be backported.

Quote from Klojum

What value is set in the "wait for network" option?
Perhaps the default 10 seconds is not enough.

Klojum, the wait for network is basically a timeout now, so if you set it to 10 seconds that will be the max time waiting if connman doesn't detect a network. If a network is detected it will just continue.

ramses3

can just sleep in the autostart.sh

sleep 10

We use the connman-wait-online utility. So if it detects a network then there isn't much we can do other than sleep for a few seconds.

You could also try this

wget -O /storage/.config/system.d/kodi-waitonnetwork.service http://sprunge.us/aKZc

then make use "wait for network" is enabled and reboot. This adds an extra two seconds after connman-wait-online detects a network connection.