BeeLink GT King - CoreELEC-Amlogic-ng.arm-9.1-nightly - Generic

[Baderks]

@Vasco

Thank you for taking the time to do the tests.
Your results are similar to what I obtained. The note that was put in the release was because some team members had devices that had problems that made them almost unusable with ethernet. Beelink is addressing them. I (as you) obtain similar results in Android and CoreELEC so there’s only so much anything can be done. Obviously, the results with your Zotac are way better and that’s a question of hardware quality.
If the situation gets worse or changes in any way please feel free to post again

Recently, using the GT King as an alternative digital VCR, there were to my surprise moments that I was able to transfer files from my PC to the GT King with speeds of over 100 MBytes/sec. Furthermore I was able to record TV programs from all the 6 network tuners simultaneously without any so called “continuity counter” errors. I was running Amlogic-ng Generic nightly 20190818 at the time. As I had not done anything special to get these ethernet speed results, I was convinced that the CoreElec Team had somehow solved the ethernet problems of the GT King.
Unfortunately, after updating to Nightly 20190820, the ethernet party was over again. Maximum ethernet speeds drop back to 67 MBytes/sec and I got lots of “continuity counter” errors from TvHeadEnd42, even during single tuner recordings. Although the maximum speed of 67 MB/s is better than the 20 / 40 MB/sec it used to be, it was a disappointment, especially the TvHeadEnd errors. By the way, 67 MB/sec should be more than enough for single tuner TvHeadEnd recordings (10 MBytes/sec per tuner maximum needed at the moment). So it is not speed alone what causes the current ethernet problems of the GT King.
That I was able to get ethernet speeds of 100+ Mbytes/sec, suggests to me that it is not very likely that the GT King’s hardware is the cause of the ethernet problems. Remembering the iperf3 trick I used to bump the ethernet speed to 40 MBytes/sec a couple of weeks ago, I tried this trick again. And yes, it worked again, be it that this time this trick, after a reboot of the GT King, bumped the speed all the way up to 100+ MBytes/sec.
Somehow iperf3 changes the ethernet settings in such a way that after rebooting the ethernet performance is what it should have been out of the box. These altered settings survive reboots and power off-on cycles. Why the initial reboot is needed after running iperf3 before these iperf3 settings are actually applied, is beyond me.

I hope this information will help Team CoreElec to once and fore all solve the ethernet problems of the GT King. Let me know if I can be of help or if more info is needed.

TIA, Baderks

.