balbes150

1. There are two kinds of updates - a standard (which can be installed by conventional means) and not standard (which are formed at the time of imaging or scripts when you first start). If You are familiar with Linux, you can upgrade to install yourself (for not standard you will have to copy files, run commands, etc.). 2. The procedure for installing to the internal memory makes the minimum changes to u-boot, so it will be possible to start the system from removable media and restore in ddbr. But it is in theory, in practice, your model may have some nuances that are not known to me and I can't guarantee the work of the restoration without tests. Restoring using a USB cable and it should work (but then again, I have no guarantees).

A new version of the images Armbian 20170805. They include experimental support for installing to the internal memory. While this is only tested on one model with eMMC (Tronsmart MXIII Plus). Note that installing to the internal memory can turn TV box into a brick and will need to be restored. To install you need to run as root script "/root/install.sh". We strongly recommend to run the installation script to perform a full backup using the utilities ddbr (ddbr_nand_*).

Update images 20170803. Added support for remote control. To use it you need to add the correct file "remote.conf" in the /boot directory or /etc/amremote. By default, a part of the image includes several predefined files (in the /boot directory). To use it you need to rename one of the files in "remote.conf". Additionally uploaded the site to the directory the deb package "amremote.deb" , which can be installed in the old system (do not download the whole image). After installing this package you need to run service "amlogic-remotecfg" and add (rename) the correct file 'remote.conf".

1. The system can be installed in NAND, but still need to perform several manual operations and to be ready to restore if the installation process goes wrong. 2. In the next month I plan to collect a new image. Activate the multi-boot and you will be able to run external drives any system (Armbian , LE etc). The contents of NAND will remain unchanged.

There is a problem. In the Odroid kernel sources there is no support for the chips s905x and s912. No support for equipment parts (food, sound, etc.), which is used in TV boxes. To enable support for different video modes to the kernel from armbian, it takes time to analyze and create patches. If you run your system with dtb from VegaS96 is a file to S912. Most likely You have a model not s905x. In the last images to run KODI you need to use the standard selection menu of the graphic shell at the login screen the system (2 line KODI). In this case, no switching is required between the terminals. When you exit KODI, the system automatically returns to the login screen. This is good information, in the following images I will try to use it.

How long are you waiting after turning on ? What kind of monitor is connected to the TV box ? As far as I know, no s805 trigger activation, multi-boot and run the system with the USB.

Judging by the description, Armbian should work. But without a real test there are not any guarantees.

On this model TV box is the mode of "recovery" button translation in this mode ?

1. To install in eMMC you need to use another command "/root/install.sh" (before running you need to switch to root "su -"). In this thread it was discussed many times. 2. Try to connect SD card with Armbian and run with it. If the system can be run in multi-boot mode, you can either completely erase the internal memory and then you can earn program the firmware via USB. Either you will be able to immediately perform the correct installation of the system in eMMC.

If You are still running on the Debian version 8, I see no reason to rush to upgrade (when there is no access to the device).

Version 20170705. Changed algorithm activation HDMI. It now runs in two stages. Pay attention, changed the kernel image to be installed in the internal memory. In the image name removed KODI, as all desktop images by default with KODI.

Test Assembly for s912. https://yadi.sk/d/HWf1_w123KhtER

IMHO. You have a problem not the right build u-boot (possibly not used the correct GCC or src). I don't recommend to change (flash) u-boot and dtb, if they are collected using source not from the manufacturer of the TV set-top box.

Request to all, who have the opportunity. Check run this test video in KODI on the last image 20170702. I am interested in the behavior of the system when playing on different TV boxes (with different dtb data). https://yadi.sk/d/AROh6_rH3KfJ5c According to the test results to write the model and result (reproduce or not).

login root paswd 1234 to All update Mate\XFCE + KODI v20170702

Update images kernel 3.14.29. (20170701) Changes - added driver for qca9377. Its use is similar to the module "dhd" and "wifi_dummy". To check loaded, with the command "modprobe qca9377" if a WiFi network will work with it, write its startup in /etc/modules. I checked on the model Tronsmart S96 (s912) - with this module the WiFi and BT working. By the way, I didn't even need to manually copy the dtb file, the system could earn with regular dtb from the internal memory. I wonder how on other models, to run these images without manually adding the dtb file.

Image update Mate\XFCE+KODI 20170630 (bug fixes). For those who already have images 20170628 you can only refresh the kodi package (download from the directory the deb on the website and install via "dpkg -i"

Image update Mate\XFCE+KODI 20170628. Updated libs. Now has less to hang.

As far as I know, Alsa is not able to output sound via BT. So Pulseaudio is part of my images.

ver 20170625

IMHO it is better not to use "sudo" . All teams who need a level of "root" to execute after the transition mode the "root" (using the command "su -").

What version of image (date) you have worked with WiFi ?

Module "dhd" the same behavior ? Have you tried to configure and connect, wait 5 minutes after enabling the module ? To ALL Error found in latest version of Armbian+KODI (20170623) and images that can be repaired without downloading a new image (in which these errors are corrected). 1. Freeze sound. To resolve is to edit the file /etc/pulse/default.pa the line load-module module-udev-detect (remove the tsched=0). 2. In a lengthy video playback in the main system turns on the screensaver and artefacts to video. The solution is to disable or uninstall the screensaver. Or use a separate graphics desktop and launch KODI. To do this, remove the package "nodm", install package "lightdm". This will allow at the entrance of the system to choose which system to run Mate\XFC or KODI. In the upper right corner of the login screen (lightdm) there is a button to select Mate or KODI. To run KODI you need to choose the second option in the menu.

Module loade ? sudo modprobe wifi_dummy or sudo modprobe dhd For autostart WiFi Add 1 new line to /etc/modules wifi_dummy or dhd