kodiuser1 I think I may have a solution for automatic Aigale driver loading:
- remove all previous "hacks" - entries in autostart.sh and wifi.conf file
- update to this test build: 2016-11-17
kodiuser1 I think I may have a solution for automatic Aigale driver loading:
Hi!Maybe test a experimental build with this source helps or at least check the commits to see if the backports contains something interesting.
Is a Kodi 16 + a lot of backports + LE patches + patches from other projects like OSMC
It contains 122 commits over the official version of Kodi 16Comparing xbmc:Jarvis...asavah:Jarvis-amlogic · xbmc/xbmc · GitHub
Thanks, but these patches are actually LE patches from Wrxtasy and some from me. And as far as I can tell it will stutter on many videos (e.g. VC-1) because of a few patches that I already tested and ruled out... I think the approach in the latest test build is the best I've ever tested on my 50GB+ sample videos.
Actually what kostaman sees - skipping to next chapter - is correct behaviour.
Source is always available on my GitHub: GitHub - kszaq/LibreELEC.tv at 7.0.2.009
kodiuser1 Please collect and post logs. I don't have a device with Aigale WiFi chip and I have a look at what exactly happens.
kostaman Can you try this devel version with "The Grand Budapest Hotel": LibreELEC-S905.aarch64-7.0-devel-20161116235711-r23437-g73c3cef.img.gz
I also have that movie and what I noticed it that when you zap through chapters video sometimes freezes but if you wait a few seconds it starts working again. I think decoder needs to be fed with video packets to start working properly and it has to stay that way.
Everybody else can also test this build for a/v sync of buffering issues.
I have been trying to make the kernel module for Aigaile chips load automatically but unfortunately I couldn't make it. The only thing I achieved is an easier hack:
Please report if WiFi works "automatically" with this version and after following these steps.
I think he means my 7.0.2.009 build. It's based on LE 7.0 code.
That's because some people complained they don't want the box to reboot automatically. It's also easier to debug in case anything goes wrong.
Is this option available now?
Also, one bit of confusion. After nand install, is it still possible to boot from SD for testing future versions in the same manner? Does installtointernal still work the same way in this case?
Not yet. I've modified the script but I need to test it first. If you want to take a look at it or test:
wget http://kszaq.libreelec.tv/s905/devel/2016-11-15-script/installtointernal
chmod +x installtointernal
./installtointernal
Yes, as long as you have SD card with LE insterted your box will boot from SD, no matter which system you have on internal memory. I do this at home for testing: stable version for family on internal memory, testing from SD.
Misspellings are common in Chinese-sourced code, you will find many in Amlogic sources. Yes, remote.conf should spell "repeat_peroid" to work correctly.
Oh, I thought you already have a working build for DVB on K1. My mistake, I thought your binary builds already have support for DVB.Do you know anyone who already managed to integrate such driver ?
Not in the latest kernel. For the previous kernel there is a binary (closed-source) driver from VitMod.
1. I have been struggling with tweaking codes for my IR remote on my Venz V10 Pro (2GB / 16GB). Having first gone down the lirc route (as it works fine on my other media box which is x86-based and running libreelec Krypton alphas), I got very confused as irw wouldn't work for me and eventually I discovered that lirc wasn't even running and that the remote seemed to be being treated like a keyboard and was handled by the kernel directly. Can you confirm that on these AMlogic boxes lirc is no longer used and I shouldn't concern myself with it?
LIRC is not currently used but there is a plan to switch to it. For example, devices in current LE master branch such as WeTek Hub and WeTek Play have been switched to LIRC implementation and I think my builds will eventually switch to it as well. Before doing this, I will need to gather LIRC configs from different remote controls from users. At the moment the LIRC driver for built-in IR receiver is not compiled in my builds as it would conflict with Amremote driver.
However I noticed a couple of differences between my remote.conf and the one in /tmp. Are you "patching" some of the values, perhaps at startup? This info from your Jarvis build thread "fixed IR remote key code replacement script (e.g. remote button not working)" is leading me to believe this. Can I remove this script or override it if I wish? Is there a thread or other info you could point me to which would explain this newer way of handling remotes instead of using lirc?
Yes, I am patching the user-provided or extracted-from-internal-partition file. Here is the source code for the script: LibreELEC.tv/remote-config at libreelec-7.0 · kszaq/LibreELEC.tv · GitHub
If you want to override, you can load your file any time (e.g. in autostart.sh by executing /usr/bin/remotecfg [i]path_to_your_file[/i]
There are no guides that I know except for some information in some remote.conf files: LibreELEC.tv/remote.conf at master · LibreELEC/LibreELEC.tv · GitHub
2. I asked this question in the Jarvis thread, but it's so busy you may have missed it. I would like to know how the initial boot process on the box is patched to check the SD card / USB for the presence of a libreELEC image so that it boots in place of the Android system which is still installed on the internal flash. It's just my ignorance of Android showing!
This is done by modyfing bottcmd in u-boot: LibreELEC.tv/aml_autoscript.src at libreelec-7.0 · kszaq/LibreELEC.tv · GitHub
Sorry kszaq, I just realized that you are not reachable by PM. Could you please tell me if the following tree is ok ? There are no Kbuild files in the source code that I received. I just want to make sure that I have received the right stuff.
That's what I got from them but I haven't been able to make them work, at least not with short testing with users who have the box.
Hi! I have usb wifi dongle with rtl8812au chip.
How can I use it instead internal wifi chip?
I see there is drivers in amlogic kernel sourсes.
Have you tried simply connecting and using it? If it's not working there's a guide what you need to provide.
Following my post/reply #189
I have identified movie files with Chapter Markers causing the seek/skip 10 minute jump issue.
Anything with chapters will result in random minute jump like 2 minute 8 minute or 5 minute and not 10 minute.
Anything with no chapters seek/skips/forward 10 minutes perfect.
2016-11-14
I understand such seeking issues are not present in .009?
Same issue as kostaman above using my T95X box (S905X) and the test build. Unable to randomly select or jump around the timeline of the main movie. Image stalls and at times audio plays. This is over SMB network.
Which test build? 2016-11-13 or 2016-11-14? Please try the latest one if you haven't already.
Display More
Hi,I am trying to build kszaq's LE from git.
I am targeting K1 Plus with combo DVB S2+T2 (from VideoStrong) :
git clone GitHub - kszaq/LibreELEC.tv: 'Just enough OS' for Kodi
PROJECT=S905 ARCH=aarch64 make releaseIt works and I managed to install it on my box. However DVB is not enabled by default when you compile the source tree from git.
So I tried to configure the kernel with DVB support by modifying file projects/S905/linux/linux.aarch64.conf
I just put : CONFIG_AM_DVB=y
But this is not enough. During kernel build, it doesn't ask me which DVB frontend drivers I want to compile, etc.
Does anyone have a valid configuration/option file for building with DVB support ?
Thanks.
Driver for internal tuners is closed source and not available in my kernel tree. You need to obtain and add the driver to kernel source. Unfortunately I can't help on that matter.
[hr]
Display More
Hi @ all!
I am new to this nice forum![]()
Here is my first question:
I found that "boot from USB" is possible with S905 in this thread:
LibreELEC
*added a possibility to boot from USB*does this work with Odroid C2? If yes: how? Do i need to set up EMMC/SD-Card or something?
Hi andy5macht and a warm welcome.
Unfortunately my builds don't work for Odroid-C2.
You might be able to run LE from USB drive on C2 but you have to have eMMC/SD with bootloader every time: ODROID Forum • View topic - Can C2 Boot from USB Memory stick
Some hints to do it (not a solution!): burn C2 image from Wrxtasy or an official image to USB drive, change second partition label to e.g. "LIBREELEC_DISK" and modify your boot.ini to boot from USB by loading kernel from USB and change cmdline to BOOT_IMAGE=kernel.img boot=LABEL=LIBREELEC disk=LABEL=LIBREELEC_DISK. You will get further help at Odroid forums for sure.