balbes150

On the VIM2 everything is working correctly. Try downloading the image again and rewriting the media.
 
In the settings screen, change the settings to a lower resolution (1920x1080).

Is version 5.55 (20180819) version 5.59 (20180820). Small fix.

Image update 5.55 (20180819).

@balbes150 
 
upd
 

On mainline - compile kernel, v4l2 m2m etc. with custom patches or wait when it merge to stable. For 3.14 use kodi. For 3.14(and software decoding in mainline) and x11 - partial solution --vo=x11 and --sws-scaler=fast-bilinear or equal if you don't use mpv.  It cause high cpu usage but give you playable 720p and some 1080p video.  Most problem with mpv - it use by default vo=opengl, it cause huge framedrop(yep, soft mesa) so if you want soft decoding use special flags or vo=x11
upd @Baloven
 

Add new version 20180817.
Add supports USB audio

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.

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

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.
 

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.
 

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.
 
 

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.
 
 

Hello everybody!
I assembled a video player c2play, created by crashoverride, with the possibility of hardware decoding and rendering for a boxes on the S912 SOC. To achieve this, was used EGL and GLES libraries from Android, libhybris, libamcodec and ffmpeg with the support of the above library, as well kernel package with Mali driver for T820 GPU. All this was integrated into the firmware of Ubuntu Armbian 16.04 Mate Desktop, building by balbes150. You can download this firmware from here.
c2play perfectly playing, both local and network video H.264 and H.265 10-bit, checked up to 4K. Declared support of MP4, MKV and AVI containers.
A small help to managing the c2play from the keyboard:
ESC - to finish playing, LEFT - 30 sec. back, RIGHT - 30 sec. forward, DOWN - 10 min ahead, UP - 10 min. back. SPACE - pause.
To play video, open the terminal window or go to the virtual console (Ctrl-Alt-F1). enter the command: c2play <path to your video>. Or, assign c2play as the default application for the desired file type. More details here or here.
In the folder /opt are deb-packages with libhybris and kernel 3.14.29 with the driver Mali.
For those who want to build c2play itself, I bring links to resources on the github.
Libhybris: https://github.com/libhybris/libhybris.
Libamcodec: https://github.com/osmc/libamcodec.
FFMPEG: https://github.com/roman-rybalko/FFmpeg-aml.
c2play: https://github.com/OtherCrashOverride/c2play.
 

Interestingly ,the number of views of this theme exceeded 300 000 .... Turns out the anniversary ...   

The official git armbian\build adds the tvboxes test branch. Everyone is invited to participate in the development , testing and maintenance of different models of TV boxes.
 
https://github.com/armbian/build/tree/tvboxes
 

The official git armbian\build adds the tvboxes test branch. Everyone is invited to participate in the development , testing and maintenance of different models of TV boxes.
 
https://github.com/armbian/build/tree/tvboxes
 

Yes.
there is not enough time for everything
 
 
By the way, interesting news, I managed to run the version of Manjaro on TV Box Amlogic, everything starts and works. But while it has to be done in semi-manual mode (i'm need to rebuild the new image with full support for TV boxes). I hope soon there will be another version of the Linux distribution (Manjaro) for the platform Amlogic.
 

so with : Armbian_5.44_S9xxx_Ubuntu_bionic_4.18.0-rc5_server_20180727.img.xz
dtb.img with p281 dtb
 
OK to compile i add some time -j4 and some time -j3
because the swap don't work and the system freeze -j3 use less memory ( ihave only 1GB )
if you have a trouble (freeze) to compile something :
in th rep of the compil
mc -e C.sh
put the compil
chmod 755 C.sh
in console (not ssh, not in telnet ) lanch
./C.sh &
 
i add "--enable-hardcoded-table" to have some cpu gain
 
i don't put x265 (i must have an eyes on the errors after if you want it , add --enable-libx265 at the ffmpeg compile at the end )
 
sudo apt-get update -qq && sudo apt-get -y install \
  autoconf \
  automake \
  build-essential \
  cmake \
  git-core \
  libass-dev \
  libfreetype6-dev \
  libsdl2-dev \
  libtool \
  libva-dev \
  libvdpau-dev \
  libvorbis-dev \
  libxcb1-dev \
  libxcb-shm0-dev \
  libxcb-xfixes0-dev \
  pkg-config \
  texinfo \
  wget \
  zlib1g-dev
 
mkdir -p ~/ffmpeg_sources ~/bin
 
cd ~/ffmpeg_sources && \
wget https://www.nasm.us/pub/nasm/releasebuilds/2.13.03/nasm-2.13.03.tar.bz2 && \
tar xjvf nasm-2.13.03.tar.bz2 && \
cd nasm-2.13.03 && \
./autogen.sh && \
PATH="$HOME/bin:$PATH" ./configure --prefix="$HOME/ffmpeg_build" --bindir="$HOME/bin" && \
make -j4 && \
make install
apt-get install mc
apt-get install locate
 
cd ~/ffmpeg_sources && \
wget -O yasm-1.3.0.tar.gz https://www.tortall.net/projects/yasm/releases/yasm-1.3.0.tar.gz && \
tar xzvf yasm-1.3.0.tar.gz && \
cd yasm-1.3.0 && \
./configure --prefix="$HOME/ffmpeg_build" --bindir="$HOME/bin" && \
make -j4 && \
make install
 
cd ~/ffmpeg_sources && \
git -C x264 pull 2> /dev/null || git clone --depth 1 https://git.videolan.org/git/x264 && \
cd x264 && \
PATH="$HOME/bin:$PATH" PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure --prefix="$HOME/ffmpeg_build" --bindir="$HOME/bin" --enable-static --enable-pic && \
PATH="$HOME/bin:$PATH" make -j4 && \
make install
 
sudo apt-get install libx265-dev libnuma-dev
 
cd ~/ffmpeg_sources && \
git -C libvpx pull 2> /dev/null || git clone --depth 1 https://chromium.googlesource.com/webm/libvpx.git && \
cd libvpx && \
PATH="$HOME/bin:$PATH" ./configure --prefix="$HOME/ffmpeg_build" --disable-examples --disable-unit-tests --enable-vp9-highbitdepth --as=yasm && \
PATH="$HOME/bin:$PATH" make -j4 && \
make install
 
 
cd ~/ffmpeg_sources && \
git -C fdk-aac pull 2> /dev/null || git clone --depth 1 https://github.com/mstorsjo/fdk-aac && \
cd fdk-aac && \
autoreconf -fiv && \
./configure --prefix="$HOME/ffmpeg_build" --disable-shared && \
make -j4 && \
make install
 
cd ~/ffmpeg_sources && \
wget -O lame-3.100.tar.gz https://downloads.sourceforge.net/project/lame/lame/3.100/lame-3.100.tar.gz && \
tar xzvf lame-3.100.tar.gz && \
cd lame-3.100 && \
PATH="$HOME/bin:$PATH" ./configure --prefix="$HOME/ffmpeg_build" --bindir="$HOME/bin" --disable-shared --enable-nasm && \
PATH="$HOME/bin:$PATH" make -j4 && \
make install
 
sudo apt-get install libopus-dev
 
cd ~/ffmpeg_sources && \
git -C aom pull 2> /dev/null || git clone --depth 1 https://aomedia.googlesource.com/aom && \
mkdir aom_build && \
cd aom_build && \
PATH="$HOME/bin:$PATH" cmake -G "Unix Makefiles" -DCMAKE_INSTALL_PREFIX="$HOME/ffmpeg_build" -DENABLE_SHARED=off -DENABLE_NASM=on ../aom && \
PATH="$HOME/bin:$PATH" make -j2 && \
make install

cd ~/ffmpeg_sources && \
wget -O ffmpeg-snapshot.tar.bz2 https://ffmpeg.org/releases/ffmpeg-snapshot.tar.bz2 && \
tar xjvf ffmpeg-snapshot.tar.bz2 && \
cd ffmpeg && \
PATH="$HOME/bin:$PATH" PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure \
--prefix="$HOME/ffmpeg_build" \
--pkg-config-flags="--static" \
--extra-cflags="-I$HOME/ffmpeg_build/include" \
--extra-ldflags="-L$HOME/ffmpeg_build/lib" \
--extra-libs="-lpthread -lm" \
--bindir="$HOME/bin" \
--enable-hardcoded-tables \
--enable-v4l2_m2m \
--enable-gpl \
--enable-libaom \
--enable-libass \
--enable-libfdk-aac \
--enable-libfreetype \
--enable-libmp3lame \
--enable-libopus \
--enable-libvorbis \
--enable-libvpx \
--enable-libx264 \
--disable-libaom \
--enable-nonfree && \
PATH="$HOME/bin:$PATH" make -j3 && \
make install && \
hash -r
 
i am waitind the end of the ffmpeg compile ...
(  all compile take one hour )

I boot !
i start ffmpeg v4.01 compil

Updated images kernel 3.14 and 4.18.
 
Add dtb for p281 (S905W).
 
Please note that installation in eMMC, a system with kernel 4.18, is possible only when using u-boot-2018 and formatting the eMMC in normal disk mode.

Add to the parameter string (in the file "uEnv.ini") parameter " mac=00:ac:3f:75:c0:ff"

The official git armbian\build adds the tvboxes test branch. Everyone is invited to participate in the development , testing and maintenance of different models of TV boxes.
 
https://github.com/armbian/build/tree/tvboxes
 

The official git armbian\build adds the tvboxes test branch. Everyone is invited to participate in the development , testing and maintenance of different models of TV boxes.
 
https://github.com/armbian/build/tree/tvboxes
 

I am not sure if this is what you want to know, but:

- Debian.org or Ubuntu.com officially does not support any of those boards/boxes,
- Armbian userspace has many small but vital performance or security adjustments,
- Armbian fancy some kernel development and a lot of its maintaining. Debian relies on upstream sources for ARM hardware which can be years behind and/or lack of many functions,
- Armbian userspace is lean, clean but 100% Debian (or Ubuntu) compatible
- many stock Debian bugs are fixed on the way, "better than original :)"
- a build system is a central part of this whole ecosystem. You can DIY. Debian much harder.
- dedicated support forums per boards/boxes
- plug and play vs. complicated install scenarios on Stock Debian
- unified development scenarios and user experience vs. mess of different setup instructions scattered all around
 
I must have forgotten many other important points