Posts by trogggy

Quote from ute

Ohhh I see what you are saying ...so the Rpi will have PVR add-ons but any of the device's that were android that we wrote LE to will not

Thanks for the clarification

If you're using kszaq's latest krypton build pvr addons are available - just look in the libreelec repo.

Quote from tipsek

kszaq: is there a wqy I can do some testing or somezhing to figure out how to fix the cracklicng/popping sound? Maybe an experimental build or something? I dont mind burning a new test version multiple times just to get rid of this crackling! I love LE but its really annoying, and if theres a way to get rid of it id like to help.

Or on what is it based? Do everyone have this issue and just ignore it or is it based on X? Whats X if yes? Tried to send you PM but you have it disabled

Nope.
Beelink minimxiii - no crackling.
The only time I've heard anything like that is when I plugged a cheap'n'nasty usb sound card in (which works on the pi).

Quote from outcave

So, if I understood, do you suggest to:
1. Reboot LibreELEC
2. Immediately after, unplug the ethernet cable
3. See on the screen what happens to Kodi?

No. Not at all.
Easiest way to restart (if it's not an option in your power menu) is:
Boot up libreelec. Make sure the network's up.
Log in via SSH (putty if you're on windows).
'systemctl restart kodi'
That restarts kodi but everything else (ie network) is still running.

But I suggest you follow millhouse's advice.

Quote from outcave

"Wait for network" should resolve these... Or it does not work as expected?

It should, but you said you had doubts. Re-starting would confirm either way because you know 100% the network's up.

Quote from outcave

Here the DEBUG log: NaUn8TWr

I have the feeling that some Kodi stuff starts, in LibreELEC, before the network goes UP, see for example the row 738 and some next. The "LibreELEC Addon" fails due to a "Temporary failure in name resolution". But from the shell I can correctly resolve releases.libreelec.tv
Also the MySQL connection is even before at row 481.. so how is it possible that it can connect to MySQL Server at that time (18:52:42) if later (at 18:52:44) cannot resolve an hostname?

So I think that most of the Kodi staff, in LibreELEC, wrongly starts before the network goes UP (my feeling).

That would be easy to check. Just restart kodi (as opposed to rebooting) and if it's down to the network not being ready on boot all the problems will disappear.

Have you checked the 'wait for network' box in libreelec settings?

Have you installed and configured the PVR addon already?

Brill. Nuclear option wins again!

Quote from infinity85

Thanks! I've tried it, but I don't get it working. LibreELEC can't boot as soon as I reformat the second partition.

I tried these two scenarios:

1. Flashed the current v7.90.008 ALPHA and booted it the first time. LibreELEC expanded the second partition as expected. Then I reformatted this partition with MiniTool Partition Wizard Free to ext4 with 4kb blocksize. Put the card into my odroid c2 again and it refused to boot (I expected it, because .config etc. was also on this second "storage" partition before reformatting)

2. I flashed the sd card from scratch with v7.90.008 ALPHA and then I reformatted the (now) unallocated space for the second partition (which is to be expanded during first boot) with ext4 4kb blocksize. It refuses to boot again.

What is the correct way to get a new installation of LibreELEC onto a manually formatted disk? Or how do you reformat only the second partition as suggested by escalade in the first reply?

You just motivated me to get around to sticking 7.9 on a pi3, so here's what I did.
1. Wrote the image file to the sd card (I use win32diskimager but it makes no difference).
2. Fired up MTPW. Deleted the 32MB ext4 mini-partition. Expanded the Fat32 partition (don't ask). Filled the rest of the sd card with an ext4 partition - primary, 4K sectors, label = LIBREELEC_DISK - leaving a bit of unallocated space at the end (handy if you're trying to restore an image to a card that's fractionally smaller).
3. Stuck it in the pi.

What do you see if you run:

ls -l /storage/.config/udev.rules.d

?
For reference I get:

-rwxr--r--    1 root     root          1599 Nov  4 02:28 99-btautoconnect.rules

What happens if you run
sh /storage/.kodi/userdata/scripts/switchtobluetoothprofile.sh post
?

Or is that what you did above?

All I did wasmake it in notepad++, sling it in and reboot, sorry.
Did you make it in windows? If so maybe run dos2unix /storage/.config/...?
Only other thing I can think is to run chmod +x /storage/.config/...etc.

Quote from Bloksel

Maybe this works better?

Bash

#!/bin/bash


PROFILE='1'


if [ $1 == "add" ]; then
  PROFILE='2'
fi


/usr/bin/kodi-send --action="RunScript(script.audio.profiles,"'$PROFILE'")"

Display More

I did think about combining, but I couldn't see an advantage. What am I missing?

Just to say I use this with audioprofilesswitcher, so instead of pointing to your bluetoothHandler.sh I use a couple of shell scripts to switch audio profiles.
eg as simple as

[code]
#!/bin/sh


/usr/bin/kodi-send --action="RunScript(script.audio.profiles,1)"

[/code]
It works great for me, many thanks for documenting it.

Quote from Cris_

The best would be to switch here automatically between the "Audio Profile swicher" profiles (more saved options in the profile1.json like video resolution, etc)!

Hope anybody here can light me up!

I have something like that going on. It's based on this.
My version of 99-btautoconnect.rules in storage/.config/udev.rules.d (trying a few BT receivers / headphones as you can see):

ACTION=="remove", SUBSYSTEMS=="input", ATTRS{name}=="00:11:67:85:63:60", RUN+="/storage/.kodi/userdata/favourites/scripts/audioscripts/switchtoHDMIprofile.sh"
ACTION=="add", SUBSYSTEMS=="input", ATTRS{name}=="00:11:67:85:63:60", RUN+="/storage/.kodi/userdata/favourites/scripts/audioscripts/switchtobluetoothprofile.sh"
ACTION=="remove", SUBSYSTEMS=="input", ATTRS{name}=="00:1F:81:08:25:AB", RUN+="/storage/.kodi/userdata/favourites/scripts/audioscripts/switchtoHDMIprofile.sh"
ACTION=="add", SUBSYSTEMS=="input", ATTRS{name}=="00:1F:81:08:25:AB", RUN+="/storage/.kodi/userdata/favourites/scripts/audioscripts/switchtobluetoothprofile.sh"
ACTION=="remove", SUBSYSTEMS=="input", ATTRS{name}=="E8:28:AB:12:83:30", RUN+="/storage/.kodi/userdata/favourites/scripts/audioscripts/switchtoHDMIprofile.sh"
ACTION=="add", SUBSYSTEMS=="input", ATTRS{name}=="E8:28:AB:12:83:30", RUN+="/storage/.kodi/userdata/favourites/scripts/audioscripts/switchtobluetoothprofile.sh"
ACTION=="remove", SUBSYSTEMS=="input", ATTRS{name}=="E8:28:AB:12:86:21", RUN+="/storage/.kodi/userdata/favourites/scripts/audioscripts/switchtoHDMIprofile.sh"
ACTION=="add", SUBSYSTEMS=="input", ATTRS{name}=="E8:28:AB:12:86:21", RUN+="/storage/.kodi/userdata/favourites/scripts/audioscripts/switchtobluetoothprofile.sh"
ACTION=="remove", SUBSYSTEMS=="input", ATTRS{name}=="CD:63:90:94:A0:AA", RUN+="/storage/.kodi/userdata/favourites/scripts/audioscripts/switchtoHDMIprofile.sh"
ACTION=="add", SUBSYSTEMS=="input", ATTRS{name}=="CD:63:90:94:A0:AA", RUN+="/storage/.kodi/userdata/favourites/scripts/audioscripts/switchtobluetoothprofile.sh"

So I'm using those to start one of two shell scripts...
switchtoHDMIprofile.sh:

#!/bin/sh


/usr/bin/kodi-send --action="RunScript(script.audio.profiles,1)"

switch to bluetoothprofile.sh:

#!/bin/sh


/usr/bin/kodi-send --action="RunScript(script.audio.profiles,2)"

Obviously my shell script locations won't work for you - just edit 99-btautoconnect.rules to point to wherever you want to stick them, add your MAC address(es), and change the audioprofile in the shell script to the required one for BT / TV.

I doubt this is an error. As far as I can make out installing addons is deliberately more difficult in krypton to make life harder for the build makers. Pre-krypton you could plonk an addon in the addons folder and on re-start it was working. Now it's installed but disabled.

It's not a recommendation, rather an observation, but I've been using mini-toolPW for years to format for openelec and libreelec with no issues.

Quote from loki69

is 32gb big enough of a sd card and level 10 40mb/s or should i get a 80mb/s one?

4GB is big enough for me - depends what you're doing with it but unless you're storing media you won't touch the sides of 32GB.
Fast enough? Give it a go and see. I would have thought so.
I've no idea whether an 80mb/s card would make a noticeable (or any) difference.
If you want the fastest experience install to NAND (after testing on sd). I haven't done this, many have.