The change doesn't affect receive speeds.
I have tested my SMB rates and I always got >100MB/s throughput when transferring to /dev/null with 7.0.2.007.
The change doesn't affect receive speeds.
I have tested my SMB rates and I always got >100MB/s throughput when transferring to /dev/null with 7.0.2.007.
New development build to test: 2016-09-28-devel
Changes from previous build:
Remember to use an updated device tree.
Please try the latest development build - I have added a revised way to switch output_rgb: 2016-09-28-devel
Remember to use updated device tree to avoid audio issues.
Patch used: drivers/amlogic/hdmi: make output_rgb a device parameter · kszaq/linux-amlogic-le@4fd3d70 · GitHub
Once I get my S905X box I will make my builds work. There is no need to create a separate forum for these devices.
Also if someone wants to create a maintained build - with source code, updates and support, I will happily stick the thread.
You have to find TWRP for your device and use it to make a backup.
edit4ever RTL8211F is Ethernet chip. You are looking for something else. Perhaps you have an Aigale chip, like Beelink GT1? Beelink GT1 4K TV Box Review – Part 1: Unboxing and Teardown
plikmuny You have to update your device tree for the development build, this has been said a few times already.
Thank you for kind words.
And don't worry, these devices are not being abandoned - there is a plan to merge S805 support into LE master in the future.
Now suspend appears to be fixed would it make more sense to map the power button to XBMC.Shutdown rather than XBMC.Suspend() by default? That way it'll follow whatever's set for power in kodi settings rather than needing a new .xml to map it.
Good suggestion. Will apply.
At this point not much is exposed in Kodi, you can play with decoder and post process manager parameters using sysfs. The only "documentation" I know is kernel source code. I haven't played much with these settings, maybe someone here knows more about it.
No one here provides a build for MX2, you should ask a person that provides the build.
That said you should be able to make a backup using TWRP or ClockwordMod if you can find one for your device.
Yes, I'm sure. RPi2 is arm, RPi3 is aarch64 but uses arm build (32-bit userspace).
I think your next question will be: can't we use 32-bit userspace? Well, I'm not sure. I'll have to see if we have all needed binaries.
cHarOn Some bad news: as of now widevine doesn't work with LE on S905. There are developers much more skilled than me working on it but there's no guarantee it'll work.
/dev/disk/by-label is not available for init script.
Kodi 17 build is not yet available. I don't have enough free time to work on both Kodi 16 and 17.
My plan is to start work on PRing S805 and S905 support to master LibreELEC branch after I release 7.0.2.008.
I extracted the dtb myself, and I've used it for months launching Armbian, so I know it is correct.
You know it is correct for Armbian. In my builds >= .006 I am using an updated kernel that needs many modifications of previous device trees. That's why I dropped aml_autoscript magic and require users to choose a tree from provided ones.
afl1 This would break booting for everyone having SD card at mmcblk0. I think LABEL based solution is better, I only need to see if there's anything else that should be applied, e.g. a delay to wait for SD card mounting.
I'm not giving any buying recommendations.
I've bought the cheapest S905X box available only to solve boot issues and then throw the box back to its packaging.
The only thing I can say is that if you want a bit better support, you should prefer S905 over S905X as this is what good quality products use (WeTeks and Odroid-C2).
I've also heard that S905X doesn't support 60fps 4K H.264 videos, although this is yet to be checked.
You should choose S905X only if you need hardware VP9 decoding and/or armv8 crypto extensions.
I don't know if the delay is present or where does it come from. You have to call the postal company which delivers my S905X box and tell them to hurry. [emoji14]