Best to get support from the original the OE forums: OpenELEC Mediacenter - OpenELEC Forum - VPN Manager for OpenVPN (1/63)
Though first thing to try would be resetting the .ovpn files from the settings menu, that usually fixes any issues.
Best to get support from the original the OE forums: OpenELEC Mediacenter - OpenELEC Forum - VPN Manager for OpenVPN (1/63)
Though first thing to try would be resetting the .ovpn files from the settings menu, that usually fixes any issues.
That seems like an awful lot of faffing about to solve a problem that didn't exist on openelec.
I have been searching the openelec forums this morning and it appears that if i simply add sleep 25 to the begining of my autostart.sh it will delay the boot to kodi for 25 seconds, which may well solve my problem!
[hr]Hi J0nnymoe,
The problem is the network only seems to properly connect about 5 seconds after kodi has launched so i get 1-2 tvheadend client disconnected messages before it connects and starts syncing, so Kodi has well and truely started before the network connects.
Are you running tvheadend and mysql all on the same pi?
So does the sources.xml store the usernames and passwords for network shares? and if so does it store them as plain text or encrypted (i currently have them referenced from a seperate file and stored encrypted)?
Yes, i have left the wait for network enabled.The big problem though is that mysql doesn't connect on boot as it can't see the server so this PI doesn't have all the resume points etc sync'd that all the oters do.
I believe if they are password protected shares, there will be an additional file called passwords.xml. I would assume that it's encrypted but I would suggest to check.
Never had the issue myself with mysql not connecting with the wait for network enabled. In theory the boot method should be:
LibreELEC Boots > Waits for Network > Kodi Loading > MySQL connect.
If you are having some issues, post some logs and someone here can take a look,
Hi dave2318,
After reading through what you have said, I would highly suggest changing the method of how you have your pi's configured. There shouldn't be any need to mount shares via the autostart.sh. I have multiple kodi devices (Windows / Linux / rpi's) that all use the same 2 files for the configured (advancedsettings.xml & sources.xml). All I have to do with a fresh install is copy those files to the user_data folder and once rebooted, everything is back in sync.
Also the "wait for network" option I would advise to enable anyway as it doesn't hurt to have this option enabled.
@J0hnny,The last thing I see at the logfile is airplay related....could you try to disable that? Just for a test.
And I see you have connected some Bluetooth audio device. Is that the main audio device you are using? And if not, could you disable that, too please?
Will try these things tonight, though the Bluetooth is needed for my ps3 bd remote.
I will report back
Sent from my Nexus 6 using Tapatalk
Interesting thanks.
I had a friend running generic libreelec and they didn't have an issue with the skin. Could be platform specific.
Will monitor that other thread and see what they say
Sent from my Nexus 6 using Tapatalk
Hey,
Great work on LibreELEC so far! On saturday, I done a fresh install of my Pi's around the house, Everything working great other than one minor thing.
Tried to install Xperience1080 skin and it gives me a bootloop issue after the skin has been activated. Works fine on initial selection until reboot.
I have put the log file here: jeARTAvH
Device: Raspberry Pi 2 - Model B
Overclocked: N
LibreELEC Version: (Jarvis 16.1-RC2) v6.90.004
Any more info, please let me know.
Cheers