nibelung Please try updating to 7.0.3.3a and let us know if it fixed your issue: Index of /s805/7.0.3.3/SD or Update/
Posts by kszaq
-
-
kszaq
How much space is required to build LE. Last time I ran the build on RPi (old model with 8gb sd card) and it stalled after 15 hours because there was no space left out of 4.7gb?
My S805 build folder is 12GB.
And how I can make filesystem read/write because while building it? I want to use it as headless server when not using as media player.
The idea of LE is to have read-only system partition image as squashfs. I don't have a way to modify it.@all If anyone is having issues with non-working sound on boot and it starts to work after replugging HDMI, 7.0.3.3 build has been updated to 7.0.3.3a with a fix for that issue.
-
7.0.3.012c build available with fixed Docker support. It will also be fixed in a next Krypton build.
-
Thanks kszaq for the new 7.0.3.012b build.Just tried this on Nexbox A95X (amlogic S905X 2/16 gb)
- now tvheadend server with my dvb-t2 usb (mygica t230) working flawlessly
- will test more later, especially docker
Docker doesn't work in 7.0.3.012b. I will upload 7.0.3.012c today with the only difference being fixed Docker support.
[hr]
If it's not too much to ask could you please compile your next build for 'installtointernal' directly as well. I need to update several friends MiniMX-G boxes that are using Alex's old 7.0.2.005 build and I would prefer to do so directly via recovery. Sorry if I'm out of line by asking, I appreciate all your hard-work greatlyI can upload the build but with no support. You are aware that installing in recovery wipes user data? You can also try a direct update - put img.gz in Update folder along with a device tree. This should work because as far as I'm aware Alex's builds are based on my sources.
[hr]
@all OP updated with 7.0.3.012c build. The only difference from 7.0.3.012b is fixed Docker support. A build with disabled temperature sensor is also available. -
Nono, this requires recompiling the kernel. I will post an updated build today or tomorrow.
-
I think I'm missing some CGROUP kernel options in my builds. I will fix this for in next release.
-
@all I have uploaded a new version with a few changes to test. This build is not tested by me (I switched to Krypton testing), please experienced users only! In case anything goes wrong, you can always downgrade by simply putting a previous version in Update folder and rebooting.
Changelog over 7.0.3.012a:
- fixed Bluetooth using hciattach (e.g. Realtek 8723BS)
- new QCA9377 WiFi driver
- new QCA9377 Bluetooth driver
- added an udev rule in hope to fix non-working WiFi on boot (you no longer have to toggle it in settings)
Edit: Please use a newer version from OP.Version with temperature sensor disabled will follow if this build is confirmed to work well.
-
Probably this will solve your issue: Ensure the IEEE HDMI identifier is set even when the EDID cannot be read by samnazarko · Pull Request #33 · LibreELEC/linux-amlogic · GitHub
I will implement it in a next build.
-
I have identified an issue that prevents some BT chips from working in 32-bit build. I have a fix for this, will do some tests and hopefully publish a new build quite soon.
-
For S905.arm-8.0-devel-201612231, you should use device trees of 7.0.3.011 instead of 7.0.3.012There is no difference in 7.0.3.011 and 7.0.3.012 device trees.
-
Do the skins classify as Add-ons that need to be re-installed after updating from 64 to 32 bit?
Everything seems to be working fine. I use the box only for movies, so I don't have any DVR add-ons. My weather updates fine and Library Watchdog seems to be working.
No, skins don't have to be updated. Only binary addons, which means most of addons from LE repo.
Also, does this release fix the issue where the audio is out of sync on some movies? I have to move it to -0.250ms every time and it's fine.
The fix may be a side effect of a corrected buffering patch.
I was running the alpha 7.90 alpha build for the S905, and I updated the retroarch addon provided by Jokerz and it worked perfectly. But I have a few problems with the alpha build.Now when I go back to this version and I run the same exact add-on I get this error: "error while loading shared libraries: libavcodec.so.57" is there a way I can install those libraries to this build of Libreelec or do I need to keep using the alpha build?
You cannot downgrade from LE 7.90/8 to 7. If you did this, that may be the reason for not working shared libraries. -
afl1 Thank you for your builds and it's good to see the positive effects of your continuous efforts.
I need to remind you that LE and Linux kernel are software licensed under GPL and that means that you really need to publish your source code. We don't expect you to create a beautiful commit history and push it all to GitHub but everyone should be able to reproduce your builds in case someone wanted to compile themselves, improve the software etc. I know that you use a driver with a source you cannot share because of its licensing - in that case you can share pre-compiled object files. Please let me know if you need any help in this.
-
dssnobie The "Unknown command" should not be an issue. Make sure you enable Bluetooth in LibreELEC Settings first.
-
No, there is no list and I don't think anyone can create such list because the builds use 3.10 and drivers backported from the latest kernel - so even if the tuner works with latest Linux kernel it may not work with this build.
You can ask other users which tuners work.
-
Make sure that you connect your box to HDMI 2.0 input and use a cable that is capable of transporting HDMI 2.0.
-
Also I see there is a newer thermal driver version available from Amlogic. Or maybe you already tested it?aml_thermal-2016-08-18 (http://openlinux.amlogic.com:8000/downlo...s/?C=M;O=D)
Newer than...?
This driver is not intended for the kernel we are using.
-
A good example is LibeELEC generic advancedsettings file (which is not used for Amlogic projects!):
LibreELEC.tv/advancedsettings.xml at libreelec-7.0 · LibreELEC/LibreELEC.tv · GitHub -
did anyone find out what's up with this pixel shift? I'm pretty sure it happens with every file that is hardware decoded, on one file I even saw a red line of pixels on the right. it's just that this test file shows it clearly. I found it also on youtube, so you don't need to download the whole suite of files from the link I provided earlier.also, can other users test this please to find out whether it's common or just with my box?
thank you!
I've been doing some tests and I can confirm that there is a slight pixel shift. Unfortunately it can't be easily fixed - in fact I wasn't able to fix it using sysfs parameters. This looks like HW decoder bug and I'll put it on my (long) todo list of things to look at.