Posts by tahPhallus

Hi,

you can't install volumio on KODI, only as dualboot/multiboot alongside of KODI

Sure. I am at work at the moment.

Will do this when I get home tonight and will let you know

Of course

Quote from Jings

Thanks for that!
I was able to get the Netflix addon to play videos by doing this. Took a while to figure out how to compile & install, but well worth the effort

Good to hear, glad you got it working.

Now time for Netflix and chill

okay changed /storage/kodi/addons/http://service.lcdd/bin/lcdd.start

now the contents is just these lines, and it seems to work:

#!/bin/sh

. /etc/profile

oe_setup_addon service.lcdd

LCDd -f -c /storage/.kodi/addons/http://service.lcdd/config/LCDd.conf -d hd44780

when I restart the XBMC lcdproc addon after starting LCDd manually, my display works like before again, all functionality is back and it is working as it should

now just have to figure out why the LCDproc addon is not working as it should, and how to fix that...

anyone any idea?

another update:

the display works when starting LCDd manually like this:

LCDd -c /storage/.kodi/addons/http://service.lcdd/config/LCDd.conf -d hd44780 -f

But now, how to get this to run also on boot...?

update.

I checked in ~/.kodi/addons/http://service.lcdd/bin/ the file lcdd.start

there are some directory and variables in there, and I tried

to read out the values of those variables with

echo $ADDON_HOME

echo $ADDON_DIR

echo $LCDCONF $LCD_DRIVER

but it shows nothing.

So probably because they haven't been filled yet.

I also see a reference to a program called oe_setup_addon

I am just not sure what that program does... Does anyone know what that program is for?

Also, what should those variables; $ADDON_HOME, $ADDON_DIR point to?

Is $ADDON_DIR the directory of this addon, or the top directory of all addons?

Sames question for $ADDON_HOME...

Hopefully someone can point me in the right direction

Good to hear that the shortcut is working.

As far as the network option goes, I am not sure..

Maybe hook up another pc or raspberry pi or some thing and see if you can see that device, to make sure whether it is a libreelec thing or a Windows problem..?

Yes, everything seems to be configured the way it should. Strange...

Maybe just add a shortcut to the network share to your desktop and use that as a workaround?

the password shouldn't be a problem. Even if you wouldn't have a password, you should be able to see the devices. You just won't be able to access them...

is your file and printer sharing enabled in the settings of your network adapter?

also, in your services.msc, is computer browser enabled?

just install dualboot with volumio.
I have my machine automatically boot volumio, so I don't need the tv on when booting.
When I want to watch media, I select libreelec in my boot menu (grub).

works well enough..

if they are both WORKGROUP, then yes.

is there no windows firewall or anything active?

also, can you ping the hostname of libreelec?

default: libreelec

so: ping libreelec

if not, then maybe also try adding the hostname to the hosts file

C:\Windows\System32\drivers\etc\hosts

on the windows machine check the name in command prompt with:

Net Config Workstation

think so... without it I couldn't get it to work. I was able to browse netflix, just when starting a video it didn't start.

Maybe interesting to see what version of the addon we are running?

I am at work at the moment, I will check my version when I get home

computers are supposed to make things easier, so being lazy is a good thing

you should be able to change the workgroup name through the libreelec settings in the system menu.

the alternative is changing the workgroup name in windows. as long as they are both the same, should be good.

Okay that's good, so you can access and copy files over now.

For it to show up in the network list, the workgroup names do have to be the same.

That is only for it to show up.

It won't give you any further functionality though..

the workgroup/homegroup shouldn't make a difference.
I am using a variety of these names at home and it works fine.

Both machines just have to be part of the same subnet.

Check on the HTPC what IP it has, and also on the windows machine.

on the HTPC it is in system information in LE. On windows, just open a command prompt and type ipconfig

you can also try to ping the htpc from windows with ping <ip address>

exampje:
windows pc: 172.16.1.1
htpc: 172.16.1.2

and then ping from the windows pc to htpc with: ping 172.16.1.2
If that gives a reply, than the connection between both are okay.

Next open in windows your windows explorer and type in the address bar \\<ip address>\
example: \\172.16.1.2\
that should show the default samba share folders from LE.

You don't need to connect the machines directly, as long as they are connected through switch or router it should be fine.
IF they are in the same subnet.
That means that the first three octects of the ip address are the same.
In my example that is "172.16.1." the last number after the dot can be different.

so:
- what happens when you ping to the htpc?
- what happens when you try to connect through \\<ip address\
- what are the ip address that you now have in use?