so its this one?LibreELEC-WeTek_Play_2.aarch64-7.95.3.tar I am wondering which 7.95.3 does have the network fix applied.
Or am I missing something?
Correct, that one.
so its this one?LibreELEC-WeTek_Play_2.aarch64-7.95.3.tar I am wondering which 7.95.3 does have the network fix applied.
Or am I missing something?
Correct, that one.
both the network fix and the longpress issue fixes are now merged into master/8.0
i've built a beta 3 straight from 8.0 master that includes both.
LibreELEC WeTek Play 2 test builds
why do you write 7.95.3 with patch ? it is a Version 9 with an Alpha version of kodi 18
No clue what you mean, LibreELEC-WeTek_Play_2.aarch64-7.95.3-patched-eee-off.tar is patched with the network fix described in this thread as it was not in the official version, it contains Kodi 17.0
[hr]
I'm not planning a PR, if you want you can go ahead and PR a backport.
Ok, I think I got it here:
Backport for LE8: WeTek_Play_2: Remap buttons in remote.conf by jester-xbmc · Pull Request #1324 · LibreELEC/LibreELEC.tv · GitHub
in the mean time the patch has been merged, so from now on any official release will have the it.
as for the longpress issue, GDPR-1, as its your patch, can you do a PR against 8 ?
That's low! Sorry for that. Indeed it was not nice.
Its fine, i'm sure they had many things on their plate.
[hr]
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
Correct, i'll see if I can pull that in if its not merged soon.
I created a PR. Should be includedin the next builld. 7.95.3 was a quick release for the mem fragmentation issue.
Thanks, I saw, they closed my PR with this fix before 7.95.3
Update to include latest amlogic kernel fixes by jester-xbmc · Pull Request #1270 · LibreELEC/LibreELEC.tv · GitHub
Any ideas why it's not? Would be kinda useful to get this into the next release properly...
The word was they had other kernel updates planned and wanted to wait to include all of these in one big pull but it seems that those have not yet been created yet so I think they "forgot".
No biggie, i'm running a compile right now.
Github isn't showing a 7.95.3 and i can't check it out.Any ideas how i'm meant to compile with my own patches for the latest beta for the C2?
Just check out the libreelec-8.0 branch.
The server that is down is our mirror for packages that are otherwise unreachable. It's just a brief outage till we sort things out.
Sure, however there seem to be packages that only reside on your mirror server (plymouth-lite-0.6.0.tar.bz2) so there is no fall-back.
good luck sorting out the issue.
No it doesn't help. We have actually 2 kind of problems here. Memory management in the kernel and a real memory leak. Because I'm using same 64bit kernel in my builds with 32bit userspace and I have no memory leaking.
So, its finally weekend, and time to play, while compiling another test build I was looking at kodi.bin using just top, it seems to eat more memory (and not freeing it) after displaying posters, I thought that texture release issue was fixed a while back ?
grrr, i just setup a new build system but ill patch manually for now.
maybe time for a sources mirror ?
Thanks for these and helping with the fix Jester.How can I go about rolling the EEE patch myself? (I've got some other changes I've made for testing at the moment) From what I can work out, It would have to be forking the linux-amlogic branch myself, adding the fix, then referencing that when building libreelec?
correct, or built a diff and put it in the patches dir.
Jester Current investigation shows it's unlikely to be an app level leak, more like something related to memory management in the kernel.
Thanks, I was just about to ask that, so we can rule out kodi ? and focus on the kernel ...which needs updating anyway....
I see some work being done to upgrade from 3.14.29 to 3.14.79, did somebody try an image based on 3.14.79 to see if this fixes the mem leak?
So, about that memory leak issue that is stopping a LE release for the WeTek Hub, WeTek Play 2, and Odroid C2 ...
I'm sure the dev's are chatting on slack about it but i'm wondering if "we" can help ?
I've made a debug build with valgrind for the Wetek Play 2 (here LibreELEC WeTek Play 2 test builds) it would be nice if dev's can chime in on the status of this issue so we don't reinvent the wheel
Just trying to help.
Thanks.