I've managed to downgrade my TVHeadend server back to a version that is compatible with the current version of the pvr.hts addon so my recordings are accessible again now.
It would still be nice to know how to compile addons from source if someone could explain it to me sometime 
Hi there,
First off, I wasn't too sure whether to put this in this part of the forum or the Development area. Please feel free to move if you think it would be more suited in the Development area.
Anyway, now on to the problem that I am having. I have recently updated my TVHeadend server to the latest available source from GIT.
Since doing this, both of my Kodi clients (a Wetek Play 2 and a Raspberry Pi 2, both running LibreELEC) are unable to see any new recordings that have been recorded by the TVHeadend server since it's upgrade. Older recordings are still visible and playable.
Having done some reading around, it looks like I need a more up to date pvr.hts addon, specifically version 4.0.15 or newer.
I have tried building the latest version of the addon available from source, but frankly I'm not really sure what I'm doing.
Does anyone have the latest version available as an installable zip file or could someone give me a bit of a hand with building it myself from source?
Many thanks
I think this issue is different.
When this crash happens, I am no longer able to use the GUI, it is completely frozen.
I am however still able to access the Wetek Play 2 over the network, for example via SSH.
I know of the eee bug that you mentioned, but I believe this was fixed from something like 7.95.3 onwards, I don't experience any network drop outs anymore. Just this random GUI freezing issue now. If it's any help to anyone trying to diagnose this, it only seems to happen after the Wetek Play 2 has been left to idle for a while
And again at 11.08pm tonight
Happened again at 6.54pm this evening
Kodi log: RWFY
Another day, another freeze overnight
Kodi.log
cTdZ
What's the official line of advice here? Shall I stick with this & supply daily Kodi logs every time it crashes / freezes? Or is no one actually interested in solving what seems to be quite a serious bug?
This cannot be called a stable release as it is locking up at least once a day (it actually locked up yesterday afternoon as well but I didn't have chance to post about it here)
Shall I just go back to using Raybuntu's releases that do not suffer with these problems?
Unfortunately I don't have any coding skills so I am unable to offer any suggestions for a fix, hence why I am posting here to report the bug.
Thought I'd open a separate thread about this. I'd originally posted about it over here: thread-3214-post-34262.html#pid34262Basically when using LibreELEC 7.95.3 on my Wetek Play 2 the Kodi UI will freeze up after a random amount of inactivity (it normally happens sometime during the night)
I am still able to access the Wetek Play via SSH.This same freezing was also present in the 7.90.10 alpha release. It is NOT present in any of Raybuntu's releases that I have tried.
I have grabbed the kodi log file here: ZZWA
This exact same behaviour is still present in the official 8.0 release.
The UI froze overnight again, access via SSH is still possible. The gdb command is consuming 100% of CPU time, so basically one whole core.
Here's the latest Kodi.log dump:
AaLL
Is there anything else I can do to help debug this?
Thought I'd open a separate thread about this. I'd originally posted about it over here: thread-3214-post-34262.html#pid34262
Basically when using LibreELEC 7.95.3 on my Wetek Play 2 the Kodi UI will freeze up after a random amount of inactivity (it normally happens sometime during the night)
I am still able to access the Wetek Play via SSH.
This same freezing was also present in the 7.90.10 alpha release. It is NOT present in any of Raybuntu's releases that I have tried.
I have grabbed the kodi log file here: ZZWA
Good morning guys
Are we sure the memory leak bug is fixed in this latest release?
I've just switched my TV on this morning to discover that Kodi has frozen at some point in the night, in fact I would imagine that it happened at 21:43 as that is what time the onscreen clock has stopped at.
This has happened with past official builds, I just assumed that it was because of the memory leak issue.
Interestingly I am still able to access the WP2 via SSH. Issuing a top command reveals the system has been up for 12 hours & 44 minutes. Also, there is a process running called gdb that is using exactly 100% of CPU time.
Has anyone else experienced this? Again, I have to point out that this has not happened whilst I was using any of Raybuntu's releases.
Is there anything I can do to help get to the bottom of what's causing this?
It you could do that'd be great. It's pretty much a deal breaker for me & stopping me from going back over to the official releases.
Having to break out the Kodi Remote App on my phone just to delete a recording that I've finished watching is a bit of a pain 
7.95.3 with patch is here:
Long press on buttons isn't working in this release, just giving you a heads up, I guess whatever fixes the long press issue hasn't been merged in to the official LibreELEC code yet as it works fine on Raybuntu's releases
I have "upgraded" back to the fixed 64 bit version provided by Jester.
One thing I have noticed is that holding down the OK button on the Wetek Play 2 remote no longer brings up the context menu.
This same problem is also present on the fixed 32 bit version provided by Raybuntu.
This problem wasn't present on the last official LE Alpha release.
I wasn't sure where to post about this problem given that these releases by Jester & Raybuntu aren't considered official releases, so I just thought I'd mention it in this thread
So far, so good. Disabling EEE seems to have fixed the Ethernet crashing issue.
Excellent work guys
You are correct, I had upgraded from aarch64.
I have now got the TVHeadend client working so I shall give it a test and see if I experience any network dropouts.
I am aware that this is to be considered as test / potentially buggy software so if I run in to any other problems other than network drop outs I won't mention / complain about them at this stage
Here you go: LibreELEC-WeTek_Play_2.arm-8.0-eee_off.tar
I disabled eee hw cap. I have currently no way to try itEdit: I've tested it with iperf and 16 parallel Threads and I have Gigabit connection. I never had that issue before so please test it then I can send the patch upstream.
ethtool to query eee gives a Operation not supported.
Just gave this version a try myself but unfortunately the TVHeadend client doesn't seem to work in this version so I can't really test it to see if it has resolved the network drop out issues for me
see my post Play 2: network disconnecting (hardware failure ?) - Page 3 - WeTek Community Forum
and add
ethtool -s eth0 speed 100 autoneg off
to /storage/.config/autostart.sh
Just to confirm I have tried this method and it does NOT work for me.
Applied the "fix", rebooted Wetek Play 2, started watching a live SD channel from my TVHeadend server. Somewhere within the region of 20 to 30 minutes later the network controller crashed again.
Back to Android for now again
Still no issue, but still testing, and i've made no changes, just a compile from the current github master, Commits · LibreELEC/LibreELEC.tv · GitHub
I've put up a test build here if people want to try, it works fine on mine, but don't blame me if stuff breaks (it shouldnt, but still)
Excellent, I shall try this out when I am home later on this evening.
Is it for SD or NAND? Or will it work on either?
That sounds interesting Jester. Is there anything different about your build that you know of?
Would it be possible for you to share your build for more of us to test it?
