AuXBoX: This looks like a hardware issue to me. Try: using a different HDMI cable and switching audio output in Kodi - if you had Analog selected switch to S/PDIF and vice versa.
Posts by kszaq
-
-
nigelg Some plugins may prevent a safe shutdown process. As far as I know this is the issue not only with my builds but with Kodi in general. That's why I recommend using 'Suspend'.
Poida V3_1 boards not waking is an u-boot issue that I wasn't able to work around so far... I have tried many things and nothing worked. There are 2 ways this can be solved: a brilliant new idea for a workaround comes to my mind or I get u-boot source code from manufacturer. I'm wondering which one is more possible...
-
When in the Android settings (not kodi android) i can change the resolution settings and that is what is used in libreelec, even if i run from nand. Also it's greyed out at the same time.Some boxes have hardware flaws that prevent them from reading EDID correctly. You can work this around by using disp_cap_hack
-
Which path should be copied remote.conf from Android firmware mxq s805 with red strip to LE 7.0.1.4( but I dont know where to copy it to and how ? )Thank you
There is a hint in the first post. If you don't have original Android firmware in ZIP, you can follow the guide from this post: LibreELEC
Keep in mind that some buttons may still not work after doing this.
So now need another clue in order to make a image of debian to boot in MXQ like LibreELEC.
Can you guide me to find the right process?
Thanks again.You need to hook up a serial console and use u-boot scripting. Standard Amlogic u-boot doesn't have boot.ini support so you need to execute commands from it manually. I can't promise it'll work, I've never tried running anything other that OE/LE on these boxes.
Poida Can you test if this build reads a correct MAC for you: LibreELEC-S805.m201d.arm-7.0-devel-20160614205642-r23062-gbbc99e4.tar
I've also added a small change that might make remote control wakeup work. Can you test it as well? I don't have access to the box right now and I'll be grateful for results. -
Off-topic (in that I'm using an s905) but I'm looking for a hint or two...
I'm booting from sd card, so I have SYSTEM, kernel.img, dtb.img and aml_autoscript in the root of the card.
Could you tell me...
1) where the pointer to the storage partition is in all that lot, and...
2)How easy it would be (or not!) to change that to another partition.In general pointers to kernel and system image are in kernel command line. I haven't released anything for S905 yet so I don't know how the build you're using works. Better ask the person who built it.
-
It just seems strange that, posts here suggest this is ONLY an issue for 3_1 boards yet, from what I read elsewhere, it is normal practice to look at efuse for the MAC address, at least with Amlogic boards. I wonder why the other revision boards are not affected?Other TV-Box boards store MAC address in "NAND key" and that's where kernel in my builds read it from. It's been working well until V3_1 boards appeared.
-
kszaq - Sure is
I will try to patch kernel to take MAC address from efuse as this seems to be the right place. I need to prepare a patch and test it on other boards to make sure it doesn't break things. This will take a few days since I'm very busy with my regular job and assembling a S905 build (preview coming soon
).
But i wanna try to use LibreELEC with x11 , i think will expand the possibilities of use applications ahead of multimedia.
can guide me on any clue?
i have been modified the options file in the MXQ directory enabling the x11 and the window manager, without sucess.First of all, Mali drivers that are used in LE for Amlogic are Fbdev and for X11 you need to use a different set of libraries. You can get X11 libraries from buildroot (get it from Index of /download/ARM/filesystem) from package/opengl folder. As I never played with X11 I can't help you further but you may want to look at Hardkernel forums for hints as their Odroid-C1 uses the same SoC.
-
Many thanks kszaq, for your efforts with thisCan you login to one or your boxes over SSH, execute cat /sys/class/efuse/mac and tell me if the address is equal to the sticker on the box?
This device is being sold in Croatian market in Interspar Hypermarkets. It looks like some kind of a clone of MXQ. Remote doesn't work and I'm getting CEC errors in dmesg every second or so. Turning off CEC with fw_setenv cecconfig cecf doesn't suppress the messages.To make remote work you need to copy remote.conf from Android firmware unless this box uses a different remote driver.
All LE builds use libCEC driver and CEC can be turned off in Kodi settings. If your TV supports CEC and doesn't recognize the box, try using a different HDMI cable.
-
Poida You can burn MAC address to the box using USB Burning Tool - that's why I don't see the MAC issue with my V3_1 board. I need to figure out if you can do this without flashing the whole firmware, I'll let you know if I succeeded. I am still waiting for a reply from manufacturer - I emailed them again yesterday - as they seem to use a different method of reading MAC address in their Android ROM. This is one more issue that could have been solved long time ago if they wanted to cooperate...
-
staripper Are you sure you have burned image to SD card properly? Can you see all the files that are needed when you put SD to your PC? When you want to boot from SD, your box shouldn't boot to recovery, it should boot straight to LibreELEC. What is your SD card capacity? Can you check if it's visible in Android?
PatrickJB Thank you for sharing your knowledge and helping people!
Poida I'm looking into the MAC issue but I'm afraid my V3_1 board is not good to try different ways of reading MAC address as I've burned MAC reg when flashing some other firmware...
-
It turns out that this is quite a major issue. Your attention to it would be greatly appreciated. Even assigning the devices different static addresses results in me not being able to use both boxes simultaneously.Is there maybe a script I can run, to change / spoof the MAC address of one of the boxes?
I also begin to wonder if the problem is confined to v3_1 boards. Can anyone confirm that they have purchased multiple boxes of the same motherboard version and have different MAC addresses assigned to each, with these builds?Can you reboot the box, grab log and post it here please?
Incidentally, the Wifi cards are not recognised with these boards (doesn't bother me, but was one of my attempts to get a unique MAC address)Probably you have SSV6051Q WiFi. Until I get a working driver source it's not going to work. Both box and chip manufacturer have not responded to my multiple e-mail requests.
-
kszaq hi kzsaq, longtime user of your openelec builds here, since 5.0.8.20. Having a small problem here, I bought my second MXQ recently and loaded Openelec 6.0.1.4 (hd18) to it, and noticed its a 512mb ram box. I then loaded Libreelec m201d build (7.0.1.4) from NAND and it boots up but the remote is not working. Remote working perfectly in 6.0.1.4. I tried the remote.conf method from android etc folder to the configfiles folder but it is not working properly. any guidance? is there anyway to load libreelec 7.0.1.4 with the remote config from openelec 6.0.1.4 hd18? thanks for helping all us mxq owners out, it is much appreciated!!!If you have a remote that worked with HD18Q build, you should use remote.conf from that build: remote.conf
kszaq Thank you for your help.I have MXQ s805 with red stripe,used update method to migrate from OE to LE(2016-05-25:7.0.1.2)Ewriting worked perfect.I installed your latest LE version7.0.1.4 but I noticed a bug. My remote control does not work and the blue led is constantly on.Any suggestions?Would really appreciate the effort.Thank you.Double-check that you have downloaded a build for correct device. Remote configuration has not changed in my builds for a very long time.
kszaq ...which device would you recommend for your new S905-build?At the moment I can give no recommendation. If I ever publish S905 builds, I want to make them work on as many S905 devices as possible.
-
Poida I have seen the same on the V3_1 board I have. I have plans to look at it later, now I'm busy trying to make my first S905 build boot.
-
Why is this Build not mentioned as a Community-Buid in this forum?
Because I don't make these builds: [ROM] Unofficial OpenELEC for MXIII-G & Tronsmart MXIII+ - FreakTab.com
-
There are imho (minimum) two possibilities why it's not working: The correct module in kernel is missing and/or the bluetooth service can't determine the correct firmware. I am not sure how to continue delimiting the problem.You may also want to try toggling rfkill before running firmware loader. This should be done by kernel module but who know, maybe it's not working for your device: brcmfmac_sdio/aml: No need to toggle rfkill as it's done by kernel mo… · kszaq/OpenELEC.tv@e296023 · GitHub
Related to the suspend problem, I will try but I really don't like the include from "arch/arm/mach-meson8/include/mach/pm.h" into "arch/arm/plat-meson/power.c". I am big fan of more general solutions.^^That's exactly my feeling and it's the reason why it's a patch file in project folder and not commit in kernel tree. I'm too lazy to code and export these functions for every meson target in kernel and I don't know if it works for other platforms so I figured out that project patch would be the best solution for it.
-
Does someone have a some knowledge with u-boot? I am asking me how I can adjust it related to the reboot/suspend/power off behaviour? There must be another way to fix these problems instead of patching the kernel (I hope).I recommend staying out of modifying u-boot as these are very device-specific and your box may brick if you put a wrong u-boot on it. It's something that you can easily recover from using USB Burning Tool but I advise strongly against flashing modifying bootloader unless you have source code from manufacturer specific to your device.
U-boot source from Amlogic FTP is here: GitHub - kszaq/u-boot
From my experience on most boxes you can make suspend work by modifying kernel code, that is at least true with S805 boxes.
As for Bluetooth, you may want to look inside your device to see what chip is used. If it's Realtek 8723BS, support for Bluetooth has been added in my 7.0.1.3 build.
-
kszaq did as u said and yes it boot to recoveryDo you have a file named recovery.img on card you wish to install from? It shouldn't be there.
If toothpick method when card is inserted does not work, you can boot to recovery without SD card, insert card afterwards and install LE from *-update.zip. After installing manually you may want to wipe data partition manually as well ("factory reset").
-
Bugfix release:
7.0.1.4 7.0.1.4Commits from 7.0.1.3 to 7.0.1.4: Comparing 7.0.1.3...7.0.1.4 · kszaq/LibreELEC.tv · GitHub
Kernel commits from 7.0.1.3 to 7.0.1.4: Comparing 83ba060...543ae83 · kszaq/linux · GitHubChangelog:
- reverted old CPUfreq table to fix stability issues
- default CPU governor is now interactive for better overall performance
- fixed (some) CEC disconnection errors
Known issues:- V3_1 board cannot wake up from suspend/power off by pressing remote power button (u-boot bug)
- 29.97 progressive videos may stutter
- power LED on not officially supported boxes may not work as intended (too many boards to support them with a single build)
- no HD-Audio passthrough and multichannel audio output
- DVB support is experimental, some USB DVB tuners don't work at all
An extra note: with this release reported CPU temperature may be a bit higher due to a small change in calibration code - this is nothing to worry about.