balbes150

The latest version of multi-boot is compatible with all previous versions of Armbian images.

It's not a glitch. I have a USB system 5.55 (presumably this is version 20180817, but it is not accurate). I don't remember exactly what actions I was doing with it, copied it and changed the advanced settings etc. But the fact is, it has 1080p video running smoothly, without friezes and brakes on the VIM2 S912. My test videos with 4K also work with almost no brakes, there are microfreezes that I write off to the USB drive from which I run it. In this version, the "mpv" itself differs in behavior, if during playback , move the mouse in the video window, there are no fading playback, which are typical when working in other images.

I may have "psychological glitches" but I have a feeling that the image version is 20180817 (after adding the settings file" /etc/mpv.conf") works better. Videos play smoothly, and in the version 20180819 there are noticeable artifacts. This is just me, isn't it ?

Image update 5.55 (20180819).

A prerequisite is the activation of a new multi-boot using an Armbian image and should not be in the env of the old multi-boot options that the CE uses. Without this, the system will not work from eMMC.

I tried to add the settings file "/etc /mpv.conf "with the parameter "vo=x11" , surprisingly, the video playback has become smoother. Even at S905 (Vega s95 Telos) when the desktop resolution to 1920x1080, play 1080p video full screen with a small microfriz, but quite watchable. On the S912 (Khadas VIM2) with the same settings and switching MPV to full screen, the video goes smoothly and without brakes. I didn't expect that one option could change the video playback behavior so much. Thanks for the tip, I'm not an expert on the features of video playback and do not know much.

Remove Coreelec and restore regular Android. Next, make sure that you follow the installation instructions.

Add new version 20180817. Add supports USB audio

http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/653167-bqeel-mvr9-rk3328-quad-core-64bit-cortex-a53-android-7-2-16gb-2-4ghz-wifi-bt4?p=740574#post740574 https://www.cnx-software.com/2017/08/18/bqeel-mvr9-nt-n9-tv-box-review-part-2-android-nougat-firmware-rkmc-youtube-4k-and-more/

Substantial progress. In the test image video version 1080 works via v4l-m2m and ffmpeg. But I do not publish these options yet. Who wants to watch, as this works on S905X, can take my LE-9 for Khadas VIM, and for S905 can find the about assembled by image on forum LE.

In the post above, I wrote about the full analogue of MVR9. Here are the specific links to this device. By the way, freaktab has several special themes for this model. For it released fresh firmware and Libreelec. http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/653167-bqeel-mvr9-rk3328-quad-core-64bit-cortex-a53-android-7-2-16gb-2-4ghz-wifi-bt4 https://www.amazon.de/dp/B07FT2LH22/ref=psdc_189155031_t2_B076BGBV4Y https://www.ebay.com/itm/Bqeel-MVR9-Android-TV-Box-Android-7-1-Supporta-Aggiornamenti-Firmware-2G-/282839333163?_ul=RU http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/686375-mvr9-rk3328-nougat-rom-by-mo123 http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/712961-mvr9-rk3328-libreelec-release I do not have RK hardware yet, so I will refrain from specific comments.

Yes, that's right. I have compiled scripts that allow you to create a table of MBR partitions in eMMC on a regular u-boot loader (it is saved). And then you can freely put the new kernel 4.18 in eMMC, as on a normal HDD \ SSD and work with eMMC as with a normal disk. It is possible to change sections under itself, but with restriction. The first FAT partition must be present and contain the emmc_autoscript system startup utility script. And do not change the partition table, or, if you need to recreate the partition table, perform a special procedure to write it to the eMMC. If you break the procedure, the u-boot in eMMC will be destroyed and will stop working. There is also an installation mode in eMMC of the latest version of u-boot-2018.

Read the instructions carefully, these images are only for writing to external media. Installation on the eMMC is performed after the system is properly started from external media. To do this, you need to build your new kernel.

I don't have any test samples yet, so I'm not ready to discuss the possibility or impossibility of the expected results. Describe in more detail what you mean by "modular approach". During the analysis, additional information appeared. The model https://www.cnx-software.com/2017/07/14/bqeel-mvr9-tv-box-review-part-1-specifications-unboxing-and-teardown/ is a complete analog, http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/663236-nagrace-nt-n9-rk3328-quad-core-android-7-2-16gb-gig-lan-2-4-wifi-bt4 the only difference is in the case. There is another model del link (not acktuale) with a power button, 1GB LAN and RAM size options (about it I have little information to assess the prospects of use).

http://www.linux-meson.com/doku.php

dtb.img

Read the instructions carefully. You need to copy the correct dtb file. To disable the monitor search, you need to build another kernel. The answer is similar to the previous one, you need to build another kernel.

Assemble the image is not a problem. My goal is somewhat wider. Develop a comprehensive system (image, set of scripts, instructions, etc.) for the end user, which will allow the average user to easily run Linux on the TV box. A typical user should have an easy-to-play set of system startup steps. Downloaded. Unpacked. Recorded image (possibly performed a simple operation to copy additional files). Launched a TV box. Performed a simple operation (or simple steps) on an existing system. And get a ready working system. Everyone has their own criteria for a reasonable price. I have been working with different TV boxes and other electronic devices for a long time and I know well what to pay attention to in order not to regret the time spent (money). Let's try to count. The model you are referring to has serious (for me) cons. 1. LAN 100 MB. 2. Power supply 2A. This means that you will not be able to fully use all the features of the device. So have to spend money to buy a new PSU. 3. Cooling system. Without it, to use all the features of iron is not possible. To power the fan will have to either use a USB port or an external power source. 4. In the set there is no cable for firmware. More expenses. 5. The quality of the components used and the Board (marking all elements that points to Maskrom and UART). This ensures that all models are identical and the manufacturer does not make a "team hodgepodge" of what was at hand. 6. The manufacturer pays great attention to technical support and is ready to cooperate (this is important for me). 7. The presence of the OTG port. Specifically about this model I can't write yet (I don't have it yet). If you unplugged the PSU, all parameters are reset. If the electricity flashes, the TV box will turn on itself, without your desire. By the way, for this reason I like the Vega S96 it has an additional battery (as in the BIOS on the PC) and is not afraid of power failure. Don't sacrifice. Producer already showed interest and offered to send me a sample. By the way, this indirectly suggests that the manufacturer is interested (and understands) the importance of expanding support for different systems in its products. So that customers who buy its products can use it much wider than just a TV box.

I found an interesting model with good parameters. http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/663236-nagrace-nt-n9-rk3328-quad-core-android-7-2-16gb-gig-lan-2-4-wifi-bt4 http://store.elezoo.com/nt-n9-rk3328-ultra-4k-tv-box-player-9 1GB LAN network. There is a button to turn on (this is important for models to run Linux without a remote control). There are contacts for connecting the fan (this is important for real Linux operation, especially as a server in 7\24 mode). Quality Board and components. DDR4 memory with increased speed. The manufacturer is ready to cooperate (this is important for the development of the system and obtaining important information about the equipment).

I was interested in the process of running Linux on the RK platform. Perhaps someone has recommendations on what models it is better to pay attention in the first place ?

Install Armbian to eMMC. 1. Be sure to activate multi-boot using the new image. If multiboot previously activated is required to repeat activation using files in a new image. 2. Run Armbian from external media, run "ddbr" and create full backup eMMC. 3. Execute script “/boot/create-mbr-linux.sh” 3. install Armbian on eMMC execute script “/root/install.sh”. Please note, this is a test installation, which was tested only on a few models. Possible errors (Armbian will not boot) when you are working on unverified models which used non-standard distribution of partitions in the eMMC. Therefore, be sure to back up the "ddbr" utility before running the scripts.

Information in this topic is very outdated see this topic. The start system in Coreelec is not compatible with LibreELECE Armbian etc. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems. The new version 5.55 of images. In this version, images with a single DE (XFCE) and a server in composition are as close as possible to the official versions. Version with a Mate and Icewm will probably be later and the gathering will be from another branch GIT (specially adapted for this DE). Since now all the images will be collected using the main kernel "4.1 x", have a common structure for the entire line of s9xxx and differ significantly in steps when configuring the system, I open a separate topic for this direction. https://yadi.sk/d/pHxaRAs-tZiei https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ The primary steps to capture an image, activate multi-boot, and select a dtb file are common with the previous images. Please note that starting with the version number version 20180928. Major change. A new algorithm for the use of the dtb. Starting with this version, you no longer need to copy the dtb files and rename it to "dtb.img." In order to specify which dtb file to use, you need to edit the file 'uEnv.ini" (specify the desired file name for use dtb). This is a plain text file and can be easily edited. This change will make it easy to update the kernel from the "deb" file in the future. The new algorithm is now used in the eMMC system installation script. Be sure to activate multi-boot using the new image. If multiboot previously activated is required to repeat activation using files in a new image. Pay attention. To use the system with u-boot-2015 (regular firmware Android), you need to edit the file "uEnv.ini" When using u-boot-2018, you need to edit the file "/extlinux/extlinux.conf" For those who doubt or do not know what u-boot is used, you can specify the desired name in both files at the same time. To change the used MAC address. 1 options You can add the required parameter to the startup files (uEnv.ini and extlinux.conf). To do this, at the end of the line with the launch parameters, you need to add a parameter specifying the desired MAC address. For example, mac=xx:xx:xx:xx:xx or ethaddr=xx:xx:xx:xx:xx Old info multiboot https://sourceforge.net/p/amlogic-s9xxx/code/ci/master/tree/ add info https://medium.com/@vysmol/how-to-install-ubuntu-on-s905w-and-simular-tv-boxes-ru-eng-7aca3e1011a5 Install Armbian to eMMC. 1. Be sure to activate multi-boot using the new image. If multiboot previously activated is required to repeat activation using files in a new image. 2. Run Armbian from external media, run "ddbr" and create full backup eMMC. 3. install Armbian on eMMC execute script “/root/install.sh”. Please note, this is a test installation, which was tested only on a few models. Possible errors (Armbian will not boot) when you are working on unverified models which used non-standard distribution of partitions in the eMMC. Therefore, be sure to back up the "ddbr" utility before running the scripts.