Posts by kszaq

There are no DVB tuner drivers released from Amlogic. The drivers are closed-source and I don't have access to [legal] source code.

First you say

Quote from Dazzerderby

removed sd card...still same issue.at boot..anything i can do?

and then

Quote from Dazzerderby

if sd removed once booted kodi functions

Does it or does it not boot from internal memory?

Running from SD card and internal memory are separate system instances and don't share data.

If you run LE from SD card, your u-boot variables should have been updated during the "SD installation" and you should be able to run LE from internal memory after taking out the card, no further actions needed.

U-boot is not needed, this is handled by your manufacturer and my LE builds do not replace it. I guess it would be enough to provide an upadted kernel and you will probably see it in the next build. Also, I don't think that gxl is S905X, it's a slightly updated gxbb.

Quote from gdachs

A S905X box for the LE team.

Gerald

That would also be nice.

Quote from pigbait

kszaq is it possible to modify the LE auto update to link to your new builds when they are released? To make auto update work.

Would be cool.

This is something on my to-do list after more important things to do - thmashing bugs!

Hello everybody, I am back from my holidays.

I've been away from computer for 2 weeks an I have a lot of catching up to do so don't expect a new release very soon, I need at least a few days to merge all new code from other developers.

While I'm not responding now to tons of new posts in this thread, I have read all of then and I'm aware of issues you have.

You may also have noticed that before I left for holidays I uploaded 7.0.2.005 build - that one reverted some problematic changes from 7.0.2.004 and is a recommended build to use until I post a newer one.

The release thread has been separated from neverending thread to bring a clearer image for the newcomers.

Don't ask me what the plans for the new build are - plans are big but I don't want to promise something that cannot be done.

asmar Try using this simplified aml_autoscript. Keep the unlock_autoscript on card: aml_autoscript

You should note that your device is not tested/supported.
[hr]
Small update release:
7.0.2.4 7.0.2.4

Commits from 7.0.2.3 to 7.0.2.4: Comparing 7.0.2.3...7.0.2.4 · kszaq/LibreELEC.tv · GitHub
Kernel commits from 7.0.2.3 to 7.0.2.4: Comparing 058e38b...b09c854 · kszaq/linux · GitHub

Changelog:

• reverted kernel DVB backport patch for future Krypton compatibility - drivers from media_backports are sill included
• updated remote.conf remapping script with a few new mappings
• added 1 missing firmware to BT firmware loader
• added 2 missing 3D support patches from Koying (SPMC)
• added HPD check fix patch to Kodi

Announcement: I will be on holidays for the next 2 weeks (until 3 August). That means no support and updates from me. Development will resume and I hope to bring you more updates and fixes.

7.0.2.004 Work-in-progress build 004
7.0.2.004

Commits from 7.0.2.003 to 7.0.2.004: Comparing 7.0.2.003...7.0.2.004 · kszaq/LibreELEC.tv · GitHub
Kernel commits from 7.0.2.003 to 7.0.2.004: Comparing 9ed7c5b...012fbcb · kszaq/linux · GitHub

Changelog:

• Mali driver updated to r6p1
• added amvideocap kernel fix
• fixed CPU temperature reading on some devices
• added patches to solve some resolution switch issues
• updated remote.conf remapping script with a few new mappings
• added 2 missing firmwares to Bluetooth firmware loader
• added 2 missing 3D support patches from Koying (SPMC)
• added HPD check fix patch to Kodi
• enabled ZRAM for a little bit less memory issues
• tweaked default CEC parameters (applies to new installs)

Unfortunately reboot/poweroff issues have not been fixed yet and memory management issues may be still present. List of unknown issues remains the same.

Important announcement: I will be on holidays for the next 2 weeks (until 3 August). That means no support and updates from me. Development will resume and I hope to bring you more updates and fixes.

I would like to remind my request for bug reporting: I wrote guidelines to make bug reports easier to categorize for both users and developer(s). Sadly hardly anyone followed the guide. Please make use of it: LibreELEC

asmar Try using unlock_autoscript from your archive and keep aml_autoscript that is provided.

Quote from Meecrob

It it possible that we will see libreelec 8 (kodi 17) with the new inputstream.mpd-plugin on amlogic s805/905? Or is this not going to happen because of hard-/software limitations?

I would like to iron out the bugs in current stable LE/Kodi. When this is done, development will focus on LE 8/Kodi 17.

asmar Why do you use a non-standard aml_autoscript? Just prepare SD card according to instructions in the first post and don't replace the script.

alon24 Amlogic doesn't use Xorg, there is no setxkbmap for this platform unfortunately.

Quote from Sinusoid

- the "mouse button" (original remote control) does not work.

As far as I remember, there os no support for the "mouse" button in remote.conf from Android firmware. You can try using this configuration file: remote.conf

Quote from Sinusoid

- I cannot acces the internal memory

You have to mount internal storage manually, e.g. add these lines to autostart.sh:

mkdir -p /media/internal
mount /dev/data /media/internal

Quote from Sinusoid

- most important for me, I cannot setup LibreElec for SD video output (800x600, for an old video projector)

There is no support for 800x600 in video driver at the moment. Amlogic doesn't use X, it uses EGL and there is no xorg nor xrandr.

Quote from tommymsw

Can this run from a USB? I am not even sure how to run LE from a SD.

You cannot run my builds from USB. First post explains how to run from SD card.

Quote from acemaxtec

hi, it is s905, not s905x.... and the spec is 1g ram, 8g rom.....so we have to put the correct remote.conf in the package, right?
many thanks
(the first photo is ok and is it normal? sorry for the questions.)
tks

My builds don't contain remote.conf, it is copied from Android on first install. If you don't have Android with proper file in internal memory, you have to provide remote.conf by yourself.

Quote from envagyok

Can anyone confirm to me, the built in tuners are supported, or not, or will be supported this build of libreelec?

Build-in tuners are not supported, it's already said in first post. Unless you can provide me a driver (source code, not kernel module from Android) they will not be supported.

Quote from acemaxtec

hi, kszaq, first thanks for your hardworking on the boxes for s805 and s905.
today i tried to reflash the s905 build of Liberelec on MXQ PRO 4K,
succeed reflashing,
but when power on,
1. some strange words,
2. and remote control also not working.(the right one is the original one for the MXQ PRO 4K)
pls kindly refer the attachments.
ANY COMMENTS
many thanks

Display More

What version of SoC does the box have? S905X is not supported yet and that may be the cause. For working remote you need a proper remote.conf.

Quote from kamacnik1

Thanks Kszaq for Your work, as allways

just installed LE on Mini MX 1G/8G on sd card and everything run smoothly, no problem so far

speaking of problem, I have one interesting situation and dont know how to solve it

I'll try it 3 different android firmware ( 105L1 , 106L1 , 107L1 ) and wifi is not working on neither, in network settings wifi device is set ON, but box doesnt find any available network , on wire is all ok
that doesnt happen in LE, wifi network is find and wifi is fully functional

what could couse this problem, and how to solve it ?

This would be an issue with Android firmware, I am not familiar with it.

Quote from anthontex

I think I have the same issue in s905 003 build, could it be?

Yes, S805 and S905 share many Amlogic-specific Kodi patches. When it's fixed, it's be fixed for both.

Quote from tommymsw

1. " Before using my builds I strongly recommend to install original Android firmware to internal memory to make sure you have a proper device tree " I am not sure what this mens? Does it mean to just make sure that you have Android on the device before you start? I just got my box and it has Android on it... Is that enough?

Yes, this is enough. The point is to have original factory firmware on NAND to ensure that you have a working device tree.

Quote from tommymsw

2. I would love to just try this, but is there a way to go back to the stock Android if for some reason I do not like it?

Run LE from SD. When you take it out, your box will boot into Android.

Quote from bnj86

I tried the sd version... and the issue seems not there.

I think the issue might be that you had wrong default framebuffer resolution in device tree. For the boxes with issue this was fixed in .003 aml_autoscript but you'd have to re-apply the script. Now that you applied the script for SD installation, NAND version may run OK. I am aware that issues are still there. I hope they can be addressed at least to some degree when I apply updates from latest Amlogic kernel release.

These are community supported builds so please post all bugs/issues in this forum area only.

Please also note that most community builds are supported by only one person and you have to be patient. We are not wizards and some hard to solve bugs may never be solved.

How to report a bug:

• Always post full log., not only the part you think is relevant. Bug reports without logs or with incomplete logs will be ignored unless logs cannot be collected. Bug reports about video playback have to include a short sample that allows to reproduce the bug.
• Read a list of known bugs for the latest release. Is it a known bug? If so, there is no need to report it.
• Search subforum - the bug has been probably already reported by other users.
• Create a thread in Amlogic subforum for every new bug so that users can easily find solutions and help.
• Help identify your situation:
  
  • include device type (S805/S905 etc.) in thread topic
  • write which build you are using and which device tree
  • include brand and name of your device
  • provide a step-by-step information how to reproduce the bug.

How to provide support logs:

You can follow visual guide from "Via Samba/SMB" tab: how_to:provide_logfile [LibreELEC]

Or:

1. Enable debugging in Kodi: Log file/Advanced - Official Kodi Wiki
2. Turn off the box in Kodi menu.
3. Unplug the power and power the box again.
4. Reproduce your issue.
5. After reproducing your issue, go to \\LibreELEC\Logfiles shared folder and grab zipped logs from there
6. If you're unable to access the share, you can also SSH to the box, execute createlog and download zip file with logs over SFTP from /storage/logfiles