balbes150

When started from the eMMC , the system uses the value "hdmimode" from the variable ENV (u-boot). You can change this variable using the "fw_setenv" utility (you can use the "fw_printenv" utility to read the variable), or you can use the UART console.

What options did you change in the in build ? What version image of the builds ?

Now checked on the image 20180406 switching from 1080 to 720. Opened file /boot/hdmi.sh, swapped the comment sign, rebooted, desktop resolution became 720.

The remote control requires a configuration file (which must be located in /boot/remote.conf). Commands do not update the kernel, dtb, and KODI.

All this is possible, but it will take a lot of time, but in the near future I do not have free time.

Turn on auto-login or remove the lightdm service from startup. Try out test versions of images with a 4.1x kernel

It's okay, I'll take your voice into consideration in the right category.

IMHO. the problem can be two things. 1. Not correct data in the dtb file. 2. There is no support in the kernel. With these problems you will have to deal on their own or look for those who have the same equipment.

In this survey discussed the use of u-boot that goes into the composition of the image Armbian, which is recorded on the SD card. When i'm create an Armbian image, the build system automatically adds the u-boot image. This u-boot (from the SD card) is used to start the system only when there is no u-boot loader in the TV box itself or it is corrupted. In all other cases, u-boot is not used on the SD card. There are several variants of u-boot for different platforms (s905 s905x s912). On the SD card when building the image (in the image Armbian) can only include one option. To use other options, you need to write it manually (replace the current one). Now, when i'm create an image, it gets a variant of u-boot for s912. This option can only work on models with s912. Therefore, I want to exclude from the u-boot image. If the user needs (when he has a serious problem with his TV box, when the regular u-boot does not work from the internal memory), he will be able to download the desired option (just for his platform) and write it to the SD card. In this embodiment, is used a regular u-boot from internal memory. This means your answer to question 2.

When building An armbian image, it takes a lot of time to create u-boot and I want to understand how it is necessary to include u-boot in the image immediately. If most people don't use it, I'll disable copying it to the image when I build it. For those who will need the image with the embedded u-boot, it is possible to easily add the right version of u-boot into the existing image.

If you do not see all the lines on the screen, try to open file on PC immediately after the image recording. /boot/hdmi.sh and switch the screen resolution from 1080 to 720 (swap the comment symbol "#" in the first lines with the specified digits).

You have a strange list of modules. I with the "modprobe dhd" necessarily pulled cfg80211 (as dependency).

Try all dtb files that start with gxl_p212_2g* and kvim_android https://yadi.sk/d/S9JRX68L3SGPYU

Display the output of the "ifconfig" command after loading the dhd module. use Armbian_5.41.1_S9xxx_Ubuntu_xenial_3.14.29_mate_20180406.img

If your Android does not have WiFi, it means that the firmware you are using has incorrect dt and u-boot parameters. Perhaps in this model the WiFi chip is different, not the same as in the model from which you use the firmware. Disassemble the case and look at the marking on the chip wifi. Have you tried the standard procedure for Armbian - download dhd module (modprobe dhd) ? IMHO for such projects do not need to take junk, which has no normal technical support. You need to use manufacturers that release their firmware and have a normal service to support their users.

Image update Armbian_5.41.1_20180406 kernel 3.14 (dir mali6/5.41.1-KODI-17.6). 1. In this version it is possible to use additional screen resolutions. For this, you need in file /boot/hdmi.sh instead of the standard value to specify the new value. A list of possible screen resolutions can be found at the end of the file /boot/hdmi.sh. Please note, not all of these values will work. 2. There is the possibility of fast editing of the parameters of the command line that is passed to the kernel at startup (without having to recompile the script s905_autoscript). Now these values are in plain text file uEnv.ini. If necessary, you can add your own values or change existing ones.

https://disk.yandex.ru/client/disk/Aarch64/Linux/ARMBIAN/mali-6

Use version 5.41

I'm now checked the Latest armbian image on Khadas VIM (S905x) load of ssv6051 module. The module has loaded normally. This Board doesn't have this WiFi chip, so it's not working. But the module is available and properly connected. What image of Armbian do you use ?

Have you downloaded the modules for WiFi ? Maybe your whole problem is solved with one command " modprobe ssv6051"

Use version Armbian with kernel 3.14

You don't need to disassemble the TV box. Try all the dtb files. According to the file with which the TV box will work, it will be clear which model you have.

Update images kernel 3.10.108 20180402. The main change - updated kernel (possible problems with some equipment).

New test version of the server image 20180402 with kernel 4.X. in this version the wired network works and it is possible to start system from the SD card or USB media.

So you don't have a broadcom chip. Perhaps realtek or qca9377. Find the brand of your Wi Fi chip and use the modules for it.