Just a quick update from my side of things.
For the time being I have had to revert to using Android on my Wetek Play 2. Running Kodi 17 RC 1 under Android works perfectly, no network drop outs whatsoever.
The problem with the network drop outs are absolutely isolated to LibreELEC.
Now whilst using Kodi through Android is a current workaround, I really would prefer to use LibreELEC if this rather serious bug can be resolved at all
After reading Jester's suggestion I too changed my PS to a 2.0A one.
However it has made no difference whatsoever. After watching a HD recording from my TVHeadend server for approximately 20 minutes via Ethernet, the network dropped out as it has been doing previously.
Back to the drawing board I guess
Would just like to say that I am having exactly the same problem.
I received my nice new Wetek Play 2 today & installed the latest Alpha 10 of LE to my SD Card.
Added my Movies & TV Shares via NFS and then set up the TVHeadend client from the Addons (TVHeadend server is a separate Linux PC on my LAN)
I began watching one of the recordings from the TVHeadend server but after 20 minutes or so the Wetek's network connection seemed to go down. Rebooting the Wetek did bring the connection back & I was able to finish watching my recording, however the exact same problem has happened 2 or 3 times since.
I have even tried using one of the community builds from over on the Wetek Forums that contains the stable LE 7.x builds but the same problem is occurring even on those builds.
If I unplug the Ethernet cable & exclusively use a WLAN connection then everything seems fine, no disconnects occur, but I really would prefer to use an Ethernet connection for the increased bandwidth it offers
Hi guys.
I use LibreELEC on my Wetek Play.
I don't have my original RCU as it stopped working a long time ago. I replaced it with the enigma2 RCU that is available for the Wetek Play.
In order to get the enigma2 RCU working with LibreELEC / Kodi I had to create a remote.conf file and place it in the /storage/.config/ folder. As I already had SSH access enabled this wasn't too much of a problem.
Now, fast forward to a couple of weeks ago. For whatever reason my LibreELEC installation became corrupted and I had to do a fresh install. It was at this point that I hit a bit of a problem, the fresh install obviously didn't contain the remote.conf file needed for my enigma2 RCU to work. With SSH not enabled by default on a fresh install either I thought I was going to be a bit stuck. Luckily I was able to locate a USB keyboard which I used temporarily until I was able to enabled SSH from the menu, copied my remote.conf file over, rebooted and then was able to use the enigma2 RCU again.
Anyway, it made me wonder why there isn't a remote.conf file included with the standard installation for LibreELEC. Sure I know there are plenty of different 3rd Party IR RCUs out there and it would be impossible to support all of them "out of the box" but surely it would make sense to at least support the official Wetek Play Enigma2 RCU straight out of the box, would it not?
I did email [email protected] a couple weeks ago with my idea but I didn't hear anything back.
Anyway, if any of you developers think this is a good idea I will leave my remote.conf file attached here for you to consider including in future releases of LibreELEC for Wetek Play. I have had to zip the file as the forum wouldn't let me attach a .conf file
I got round to deleting the Epg11.db file, rebooted and the same problem of slow boot up occured.
I then decided to delete the Epg10.db AND Epg11.db files. Rebooted this time and now it is MUCH quicker, so much so that it doesn't even have time to display the Kodi Jarvis Splash Screen.
Excellent stuff. Thank you very much for your advice Klojum
Yep I spotted that too 
So, what do I need to do? Should I delete that Epg11.db file? Where is it stored?
I used a shared MYSQL database, will this Epg11 data be being stored on there?
Hi there,
I have recently done an inplace upgrade from OpenELEC 6.0.3 to LibreELEC 7.0.2 on my Wetek Play.
I have now noticed a huge increase in boot times. Everything seems to freeze upon display of the Kodi Jarvis Splash Screen, but if left alone for long enough (5 or 6 minutes) it finally boots in to Kodi and everything is then usable.
Something is definitely wrong, could someone help shed some light on the problem?
Here's a link to the log file taken after boot up: aGfS
