Posts by kszaq

The fix is included in all device tree variants since .008.

OP updated with a new build. Two Amlogic-specific issues: mem leak and a/v sync are still under investigation.

People having issues with audio:

• have you seen "Updating device tree from [i]device tree name[/i]" on update screen?
• can you try manually replacing device tree if you run from SD card?

@thl87 Can you try the following in your autostart.sh (I know, it's an ugly hack...):

insmod /lib/modules/qca9377-aml/compat.ko
mount -o bind /lib/modules/qca9377-aml/cfg80211.ko /lib/modules/3.14.29/kernel/net/wireless/cfg80211.ko
mount -o bind /lib/modules/qca9377-aml/wlan.ko /lib/modules/3.14.29/kernel/drivers/amlogic/wifi/bcmdhd/dhd.ko

Quote from tipsek

Hello! Just a quick question: is there a way to boot to LE while in boxs default Android? I know the other way around is easy (wgile in LE I select reboot from internal) . I mean I can get to LE from android by going to the update tool, and selecting any zip. But I was hoping theres another way? Rebooting to recovery doesnt work (it reboots to recovery) . So is there another way?

Id like to have microSD card inserted all the time. Like I said once in LE I just select reboot from internal and boom Im in Android. How to do the opposite? Obviously im looking at an elegant solution without any resetting toothpicks or choosing any zip in update tool. Something like reboot to recovery (but like I said it doesnt work) . So any ideas, anyone?

After you run LE from SD card for the first time, your box will boot from SD card every time when the card is inserted unless you choose to reboot from internal. At that point the box will boot from internal only once.

Conclusion: to reboot from Android to LE simply reboot your box.
[hr]

Quote from fat-tony

kszaq - great work with the 008 build. I installed it on USB stick on my Venz V10 Pro (2GB RAM / 16GB flash). The manufacturer's android 6 build does not work well with Kodi properly (no multichannel PCM audio or DTS passthrough, no frame rate switching). Your build is pretty near perfect. No wifi on your Jarvis build, but that is not so important for me. Everything else is working well - multichannel audio, frame rate etc. Have tested 4k video and looks good - even on my non-UHD TV. Your Krypton build enables my wifi but was generally less stable (freezing requiring power cycle), so I have reverted to Jarvis for the moment. No sign of bluetooth functionality yet although the box says it supports it.

Have bought you some coffees via PayPal! Many thanks.

Thank you for the coffees. [emoji1]

There is no difference in WiFi drivers between the builds, it should work on both. Please post logs and I'll see what's wrong.

Quote from cHarOn

i will try it out tonight
kszaq should bluetooth also work with this driver?

I don't know. [emoji56]

@thl87 Can you tell if Bluetooth works as well?

Stimmenhotel There is no new feature for 3D, I only enabled one kernel option that may be needed to make 3D work.

You have to use a proper device tree for this build - from .009 folder - to make sound work. Unless I've done something wrong when compiling the trees... Can you by any chance use a different SD card and try a clean install to confirm whether it's wrong device tree issue?

@thl87 Doed WiFi work when the modules load properly?

I figured that the option might be needed for 3D to work properly. I cannot test it but you reported some time ago that it works.

Nope, the last 5 points of changelog have been "added" over 28.10 dev build, the kernel has also got the latest updates from Amlogic (courtesy of Codesnake).

You're right - this is not needed any more. Additionally you will see a message with device tree name on update screen.

Experimental (not tested) drivers for Aigaile chips added in 7.0.2.009.

Maintenance release:
7.0.2.7 7.0.2.7

Commits from 7.0.2.6 to 7.0.2.7: Comparing 7.0.2.6...7.0.2.7 · kszaq/LibreELEC.tv · GitHub

Changelog:

• fixed IR remote key code replacement script (e.g. remote button not working)
• reworked Kodi patches for demux buffering: vq stays high, high bitrate videos still able to play
• simplified updater-script for less errors when installing to internal memory in recovery
• updated AP6212 and added AP6212a firmware

Please report if you notice any regressions.

7.0.2.009 (2016-11-06)
Source code: GitHub - kszaq/LibreELEC.tv at 7.0.2.009
Kernel source code: GitHub - kszaq/linux-amlogic-le at ffa3f8ce0d0e00a4549df13a0f65eab6112db1e7
Downloads: 7.0.2.009

Further development builds available at: devel

Important: read this post first: LibreELEC

Important: please read Updating section below!

Changelog:

• kernel updated from latest LibreELEC Amlogic sources and cleaned up a bit, enabled 3D in kernel config
• fixed IR remote key code replacement script (e.g. remote button not working)
• reworked Kodi patches for demux buffering: vq stays high, high bitrate videos still able to play
• simplified updater-script for less errors when installing to internal memory in recovery
• added some GLES memory leak fixes from SPMC
• updated 4K scaling patches from LibreELEC master branch
• fixed analog audio for S905X
• allowed updating from any *.dtb file
• increased dynamic_buf_margin to fix playback of some HEVC clips
• switched to updated drivers for RTL8192EU and RTL8812AU (thanks to CGarces)
• updated AP6212 and added AP6212a firmware
• added experimental support for Aigaile WiFi

Known issues:

• Drivers for Aigaile WiFi need to be loaded in autostart.sh by adding the following lines:
  
  
  Code

  insmod /lib/modules/qca9377-aml/compat.ko
  mount -o bind /lib/modules/qca9377-aml/cfg80211.ko /lib/modules/3.14.29/kernel/net/wireless/cfg80211.ko
  mount -o bind /lib/modules/qca9377-aml/wlan.ko /lib/modules/3.14.29/kernel/drivers/amlogic/wifi/bcmdhd/dhd.ko

• Opening some high bitrate HEVC files/streams may lead to system lock - this is a bug in Amlogic hardware decoder memory allocation code.
• If you use S905X device with TV without HDR support the screen will be darker than normal on boot. It goes back to normal after you start/stop a video.
• Some clicks/pops can appear when no audio is playing.
• Built-in DVB tuners are not supported.
• Suspend doesn't work most of the times. Temporary solution: use poweroff.
• Temperature reading not available.
• Jerky playback of some 29.97fps videos and some Live TV channels (Amlogic HW decoder bug).
• CEC might not work when your box has incomplatible u-boot or your TV is not that well supported by Amlogic low-level CEC driver.
• DVB support is experimental, some USB DVB tuners don't work at all
• Lots of other things that I did not notice.

How to install
[hr]
I strongly recommend trying running this release from SD card/USB drive before installing to internal memory!

If you have WeTek Hub, you don't need to use toothpick method: update to latest Android version and make use of dual-boot feature!

How to choose a device tree:
You can download device trees blobs (images) from device_trees
Important: Do not use device trees from previous build! You also cannot use device tree from Android firmware as in 99% cases it won't work.

• S905: First look for device tree with your box name in it. In case there is no such image, download generic one. Device trees for S905 boxes start with gxbb.
  
  
  • example: for a box with 2GB of RAM and 100Mbit Ethernet, you should download gxbb_p200_2G_100M.dtb
  • example: for boxes with Gigabit Ethernet download gxbb_p200_1Gbit.dtb
  • for boxes with Realtek WiFi (e.g. K1 Plus or K2 Pro) download device tree with RealtekWiFi in name
• S905X: Device trees for these boxes start with gxl. You can leave a tree that is already present on SD card (fresh install only) or choose one according to your RAM amount.

SD card/USB drive:
Note: only 1 USB port is able to boot the box. You have to try them all. Some boxes are unable to boot from USB drive.

• Look at the beggining of this post and find Downloads link. Download file with img.gz extension.
• Burn the downloaded file to SD card or USB drive using Rufus. Alternatively you can use LE tool but remember that you have to download the image manually: Installation - LibreELEC
• After this you will see that drive capacity is 512MB. This is OK as there is a second (hidden) partition on the drive for LE userdata!
• Download a device tree, rename it to dtb.img and copy it to main folder of SD card/USB drive - replace the one that's already there.
• To boot the system for the first time you have to use one of the following:
  
  
  • toothpick method: disconnect the power supply, insert card/drive, use a toothpick to push reset button and connect the power while holding the button. Wait until LibreELEC logo appears and release the button.
  • recovery method: boot into Android, insert card/thumb drive and choose Reboot to recovery. Your box should boot into LibreELEC.
  • recovery method (take 2nd variant): if you have "Update" app pre-installed open it, insert SD card with LE/connect USB drive, and choose any ZIP file in the app for update. Your box should reboot to LE.

Internal memory (NAND/eMMC):
Recommended way: run LE from SD card first. If it runs fine, connect to your box over SSH, execute installtointernal command and follow on-screen instructions. This command wipes SYSTEM and DATA partition!

CAUTION: If your box has a non-standard partition layout, you will see an error when trying to boot from internal memory for the first time. To solve it, you need to boot one more time from SD card and run installtointernal again.

Alternative way of installing via recovery (not recommended):

• (This step is not needed when you have Android on internal memory) Download Android firmware for your box - you should get it from manufacturer or seller - and extract 2 files: recovery.img and dtb.img to your SD card.
• Download zip file from LibreELEC release folder.
• Unpack downloaded file to SD card/USB drive - you should now have 5 files on your card: aml_autoscript, factory_update_param.aml, a zip file with an update, dtb.img and recovery.img.
• Download a device tree for your box, rename downloaded file to ledtb.img and copy it to main folder of SD card.
• Insert SD card to your box and use "toothpick" method to install it. Alternatively you can boot into Android Recovery and install it manually.

To boot into recovery after installing LE to internal memory use this procedure:

• prepare a clean, FAT32-formatted SD card or USB drive
• copy recovery.img and dtb.img from your Android firmware to SD card (don't use dtb.img for LE!)
• use "toothpick" method to boot from SD card/USB drive

Updating
[hr]
Update by downloading img.gz to Update folder. You should also download a new device tree, and put in Update folder with an update file. You should have both files in Update folder before rebooting.
HOW TO:Update LibreELEC - LibreELEC

CAUTION:

• If you use a device tree from a previous build, you will experience audio stuttering issues and no passthrough.
• If you have a device with non-standard partition layout and have LE installed to internal memory, you have to perform a clean install.

FAQ
[hr]
Q: My remote control does not work, what can I do?
A: Grab remote.conf file from Android firmware (it's available in /system/etc) and copy it to Configuration folder: /storage/.config over SSH or \\your_box_IP\Configuration using Windows shares. You can also put that file to main folder of your SD card. You may need to remap some buttons.

If you like my work, you can buy me a coffee (or without PayPal account: link)

7.02.009 for S905 and 7.0.2.7 for S805 building now.

jmp1963 You are probably using someone else's build and in that case you need to create .nocompat file in Update folder in case you want to switch to my builds. The check is only present in LE 7.90 alpha are you trying to downgrade? In that case you have to make a clean build. And I'm afraid that most of the bugs from official releases are present in my builds - as soon as I find something worth upstreaming I create a PR to LE master.

Quote from azido

As we are already reached the weekend, i'll stick to 2nd option Will you use sources from krypton nightly on it?

(If there is a good turorial how to compile my own le build and the mentioned bind-mounting, let me know anyways, i'm always willing to learn something new)

I'm sorry but the build will be delayed at least until tomorrow. I have to make a clean build due to library bump in LE master and now my server is building 7.0 releases, no more power to build Krypton now.

Quote from doggyofone

Can anyone comment re: the need to keep the SD card in the box after running installtointernal?

If you keep SD card inside, your system will boot from SD card and not from internal. The reason why you are getting "120 sec" error with no SD card inserted is because you need to run installtointernal the second time to apply standard partition layout. This is explained in first post.

Quote from banditbanger

I need some help please. I'm trying to update my a95x (s905, 1GB/8GB) with the latest development build of 008. I downloaded and renamed to img.gz and dtb.img, put into Update folder via samba access, then reboot and I get an error saying "not find a valid system partition in image file" (see attached photo).

I'm sure it's a stupid mistake on my part - any help will be much appreciated....

Don't rename the update file, simply download it and put in in Update folder with the name it has.

Quote from luke_70it

Here you can find dmesg from Android: [ 0.000000@0] Initializing cgroup subsys cpu [ 0.000000@0] Initializing c - Pastebin.com

Hi luke_70it. My builds are missing NVRAM for your WiFi chip which is AP6212a. These files are not included in current Amlogic archives. Can you use a file manager in Android and provide me contents of /system/etc/wifi folder? You can also do this using LE running from SD card:

mkdir -p /tmp/system
mount -o ro /dev/system /tmp/system
zip -r /storage/downloads/wifi_fw.zip /tmp/system/etc/wifi

You will find the resulting files in Downloads folder over Samba.