so far its still pinging from work, next up a bunch of 4k demos that tend to crash it....
WT Play 2: NAND and SD - alpha 10: network disconnecting during playback (Solved)
-
Jester -
December 23, 2016 at 10:37 PM -
Thread is Unresolved
-
-
Give it some firm testing. Also check if speed is dropping. Ping me with the results and I will create a PR if that fixes it.
-
Give it some firm testing. Also check if speed is dropping. Ping me with the results and I will create a PR if that fixes it.Yeah, will do, i'll throw everything against it but the kitchen sink.
Can you put the diff somewhere so I can built against LE master ?
Thanks
-
I'll push it later/evening. Currently no access to my laptop. It's a pretty easy fix though.
-
i have your version from wetek i give a tri whit this one i have problems whit Ethernet to
-
So far, so good. Disabling EEE seems to have fixed the Ethernet crashing issue.
Excellent work guys
-
Update:
its been playing everything under the sun for about 6 hours straight, from SD to 4K, no issues, so I'm pretty sure we can claim its fixed.
You can push the PR now Raybuntu. -
Update:its been playing everything under the sun for about 6 hours straight, from SD to 4K, no issues, so I'm pretty sure we can claim its fixed.
You can push the PR now Raybuntu.Jester: Here is the commit: WeTek_Play_2: Add patch to disable EEE · Raybuntu/LibreELEC.tv@a83dc44 · GitHub
Pretty easy fix. -
Jester: Here is the commit: WeTek_Play_2: Add patch to disable EEE · Raybuntu/LibreELEC.tv@a83dc44 · GitHub
Pretty easy fix.Yup, that'll work, thanks.
I'll build from master and test there too, but its looking good. -
Jester you got a github account? I want to mention you in the PR.
-
Jester you got a github account? I want to mention you in the PR.Yes, thx, -> jester-xbmc (Jester) · GitHub
[hr]
PR is now in (thx Raybuntu) -> stmmac: Disable EEE to avoid rare network outage by Raybuntu · Pull Request #39 · LibreELEC/linux-amlogic · GitHubits working fine with Raybuntu 32bit built -> LibreELEC-WeTek_Play_2.arm-8.0-eee_off.tar
(if you go from 64 to 32 remember to put the .nocompat file in the .update folder or it will skip the upgrade)I'm compiling a 64bit built right now with the patch (slow built system so takes 4 hours....) just as an added test.
In short, looks like the issue is fixed
-
Just to confirm, its working fine under the 64 bit version.
I will keep compiling test builds.
LibreELEC WeTek Play 2 test builds
the 64 bit version which fixes the problem in this thread is here:
LibreELEC-WeTek_Play_2.aarch64-8.0-devel-20170119120948-r25248-gf27ddd2-patched-eee-off.img.gz -
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
-
I've included this fix in my recent build and I will be including it in future builds.
Long Press is no longer working because eventlircd is used. But now all the buttons work and can be remapped.
Its not ideal and I'm working on a fix. -
but where is the official libreelec fix ???? no beta for wetek devices ... it s**** ... sorry
-
but where is the official libreelec fix ???? no beta for wetek devices ... it s**** ... sorry
micha47259 There is a memory leak in the official aarch64 builds. Thats why there are no official. I have that fix included in my community builds. My builds and also kszaq's builds use 32bit (arm) for userspace. There is no memory leak in those builds.
I use official base for my builds so you should have almost the same experience. You can switch to official once its fixed. -
micha47259 There is a memory leak in the official aarch64 builds. Thats why there are no official. I have that fix included in my community builds. My builds and also kszaq's builds use 32bit (arm) for userspace. There is no memory leak in those builds.
I use official base for my builds so you should have almost the same experience. You can switch to official once its fixed.What difference is there using a 32bit user-space? Why 'should' I? (No problem - Just trying to work out the difference!)
-
I'm not forcing anyone. Its just an proposal.
-