Posts by kszaq

pulsar Thank you for your findings! I think there is no special treatment needed to make the build work on both S905 and S905X after your kernel config changes. I have built a new build with my 4K fixes included, I'd be great if you can try if it works:
s905x-test1

Quote from pawnthep

In case I try install on NAND and brick, will it still be possible to boot from sd card?

If you install above test version, you should still be able to boot into recovery without SD card inserted or into LE from SD card. Try SD version first to confirm if it works.

Quote from Nofan Tasi

I built alex's LibreELEC-Amlogic.aarch64-MiniMX-7.0.2.003 to boot from sdcard.
(his image is supposed to run from nand, alex kindly instructed how to adjust kernel CONFIG_CMDLINE)

good: unlike your LibreELEC-S905.aarch64-7.0.2.006, it does play spdif audio (even when output HDMI selected).
not so good: unlike your LibreELEC-S905.aarch64-7.0.2.006, it does not load dvb_usb_v2

No wonder that SPDIF works as Alex uses my 005's kernel. I will test optical out at my side. You need to give me a few days, more important things than development planned.

In S905 builds I include DVB drivers from media_build, the same as in S805 builds. The tuners should be supported although there may be some issues with i2c-mux. If you posted a full log we may see what's happening.

And if you downloaded 006 in the first day it was available, make sure you re-download it as there was an issue with kernel modules not in the right place.

If you use SD card to boot, it always picks dtb.img that is currently on SD card. If it is not present, it uses dtb from internal partition (= when you still have Android on internal partition with old device tree LE won't boot). I am preparing a next build with slight changes to device trees and audio system that might solve your issues. Will be out this week.

Quote from jkeijner

is there any way to make an sd that boots into recovery or something?

Can you try putting only recovery.img and dtb.img from Android firmware on a clean SD card (without LE installation files) and use toothpick method to start your box?

Quote from PatrickJB

The question is:
Does the tethered wifi function work for anyone? I've tried switching it on and my box will no longer play any streams yet strangely the weather info can be updated. If I try and connect to the wifi hotspot/tethered wifi with my other box it throws up an error and won't connect.

It's not a big deal as your build is pretty perfect now but I just thought having the tethered function working might be helpful for some people.

I'm not sure if LE/my builds contain libraries to do that. I think you can't get internet connection over WiFi and share it wirelessly at the same time, you might be able to share your cable connection. I will need to check this.

Quote from jkeijner

i have the same problem. In my case it happened after trying to go back to back to 7.0.2.005 on the NAND
now it cant boot anymore (only black screen) I used the exact method as described above for 006 to prepare the SD again. just wont boot the SD anymore for install. also the old method for 005 doesnt work. and no recovery mode
any advice how get 7.0.2.005 or 7.0.2.006 installed back to NAND? my device is ott mxq pro 4k
thnx!

If you want to flash anything to NAND you have to have recovery.img and dtb.img from original Android firmware on your SD card.

Quote from pulsar

I have used your linux.aarch64.conf and it was already set to comple as a module.

I meant not compile as module. This was suggested to me by Alex who said it fixed ethernet for him on S905X

Try this kernel config: EQiF

You can also try updating libamcodec to latest buildroot code: gggF

balbes150 This is with boot=LABEL=BOOT disk=LABEL=DISK, right? I'm curious to see whether it actually fixes any issues.

kostaman This is from post #5. I don't check the names of boxes, I simply follow what users posted here.

Quote from pulsar

To get the current 006 branch running one will need to change the serial port to from ttyS0 to ttyAMA0, I did that in the LE S905 project kernel config (CONFIG_CMDLINE). Perhaps it would be sufficient to do that change in initramfs/platform_init -> cmdline

Quote from pulsar

Serial Console is "read-only", I presume LE does not know about ttyAMA0 and thus wont start a shell here. (root-fs and/or ramdisk)

Serial port ttyS0 is serial console and this is a parameter passed by bootloader. Kernel tells to run console on tty0 which is screen. I don't think there's ttyAMA0 on Amlogic. If you want to have system console on serial port, you need to add a service: serial-debug.service

Quote from pulsar

Wired Network does not work (DHCP or fixed IP). Cable / media sensing works though. (kernel, PHY driver?)

To make Ethernet work you can try unsetting CONFIG_AM_PHY and changing CONFIG_AMLOGIC_PHY to "y" from "m" in kernel config.

Quote from pulsar

opengl-es implementation not compatible? using gxbb, not aware of gxl specific impl?

There is no gxl-specific opengl implementation, driver is the same. The name is "gxbb" as it was first used for S905.

Quote from pulsar

kszaq - can you post some details about your build-environment / steps?

I only run PROJECT=S905 ARCH=aarch64 make amlpkg. No issues here in building from scratch.

Quote from pulsar

Where does "opengl-meson-gxbb-r6p1" come from?

These are libraries from Amlogic buildroot repacked. You can find buildroot here: Index of /download/ARM/filesystem

For S/PDIF can you try using device tree with other name: gxbb_p200_2G_iNepo_Q?

Call me tired... I entered wrong framebuffer parameters in platform_init. This should fix it: 2016-08-23-test6

Sorry, this is correct link for the latest test version: LibreELEC-S905.aarch64-7.0-devel-20160823222143-r23289-g475b5e8.tar

@Gadui Can you please check this version for LE splash screen resolution (all previous fixes are there as well): 2016-08-23-4K-test5

You're right: it seems. My OE and LE builds use exactly the same WiFi driver since 6.0.3.3.

Splash screen resolution depends on parameter passed by u-boot and that is last resolution set in Android. I have prepared a patch that fixes 1/4 screen splash at 4K so Gaudi please wait a bit, I need to compile and upload it. I'd appreciate if you can test it.

jkeijner Please don't double-post. 8189ES driver is included from the version 001 and it works flawlessly on my device - I'm getting 100Mbps throughput on WiFi. I would say you are having hardware issues.
[hr]

Quote from Szymon_Zy

do you have any idea how to fix a95x poweroff/reboot troubles? Is there any way we can help by ripping something directly from the device? BTW: what is your nationality? - of course if it is not a secret I ask becouse maybe i could lend this device to you for some time

The issue with Nexbox is that they have a broken u-boot as it doesn't allow to wake up the device in any way from suspended state. When you "power it off" in Android the only thing it does is turning off the screen, not true suspend. Implementing that in LE might be possible but I don't want to waste my time on it for manufacturer that doesn't care about community at all - multiple messages to them have all hit the wall and not only from me but from other developers as well. I don't understand why they broke u-boot in the first place yet they are known for many weird choices.

It would be easy to borrow a device from you since we live in the same country - but I don't want a Nexbox.