balbes150

Mmmm... But help text on screen give all this clue)

Image update kernel 4.18 (catalog 5.44).
 
add tv-out  1440x900

with this command :
/root/bin/ffmpeg -vcodec h264_aml -i /root/Sintel.2010.1080p.mkv -vcodec copy /tmp/test.mp4
Works
But to transcode :
/root/bin/ffmpeg -vcodec h264_aml -i /root/Sintel.2010.1080p.mkv -vcodec h264 /tmp/test.mp4 -loglevel trace
Successfully opened the file.
detected 4 logical cores
[graph 0 input from stream 0:0 @ 0x558ccb3e80] Setting 'video_size' to value '1920x818'
[graph 0 input from stream 0:0 @ 0x558ccb3e80] Setting 'pix_fmt' to value '-1'
[buffer @ 0x558d12f620] Unable to parse option value "-1" as pixel format
[graph 0 input from stream 0:0 @ 0x558ccb3e80] Setting 'time_base' to value '1/1000'
[graph 0 input from stream 0:0 @ 0x558ccb3e80] Setting 'pixel_aspect' to value '1/1'
[graph 0 input from stream 0:0 @ 0x558ccb3e80] Setting 'sws_param' to value 'flags=2'
[graph 0 input from stream 0:0 @ 0x558ccb3e80] Setting 'frame_rate' to value '24/1'
[buffer @ 0x558d12f620] Unable to parse option value "-1" as pixel format
[buffer @ 0x558d12f620] Error setting option pix_fmt to value -1.
[graph 0 input from stream 0:0 @ 0x558ccb3e80] Error applying options to the filter.
 
look for solution ( but i have a doubt on this old ffmpeg )

1. You will not be able to build the Jesi version from the current BUILD. All repositories have changed a lot and become non-working. Try asking other users if someone has old images.
2. To build version 4.16, you need to enter the source directory, manually set the GIT state to the desired commit, and manually run the Assembly (either through the script in cross-compile mode, or not directly on the TV box).

Hi everyone,
I'm working on the task of using the fbdev GLES driver from Android 7.1.1 with the help of Libhybris for my KM8P on S912 for Armbian Ubuntu (Debian). In the framework of this task, I managed to build an legacy kernel 3.14.29 with the Mali driver r16p0. And also the mainline kernel 4.18-rc2 with the Mali driver r19p0. You can download the deb packages for the system update by clicking on the links above. 
For a start, it's enough to install the corresponding package linux-image-amlogics905x_5.44_arm64.deb for update of the system and also put mali.conf (taken from the LibreElec distributive) in the directory /lib/modprobe.d/ from the archive.
sudo dpkg -i linux-image-amlogics905x_5.44_arm64.deb After the system with the 3.14 kernel is upgraded, the device /dev/mali0 appears.
Unfortunately, this did not happen for the mainline kernel. It seems that the reason is that there is no description of the GPU in the device tree. I'm use gxm_q201_1g.dtb.
Next, I build a package of Libhybris from git. For the 64-bit version, I used the following commands:
git clone https://github.com/libhybris/libhybris cd libhybris/hybris git clone https://github.com/Halium/android-headers/ -b halium-7.1 ./autogen.sh \ --prefix=/opt/libhybris \ --build=aarch64-linux-gnu \ --host=aarch64-linux-gnu \ --target=aarch64-linux-gnu \ --with-android-headers=android-headers \ --enable-adreno-quirks \ --enable-mali-quirks \ --enable-debug \ --enable-trace \ --enable-arch=arm64 \ --enable-experimental \ --with-default-egl-platform=fbdev \ --with-default-hybris-ld-library-path=/vendor/lib:/system/lib To build the 32-bit version of Libhybris I installed two packages for cross-compilation: arm-linux-gnueabihf-gcc and arm-linux-gnueabihf-g++.
And compiled with the following parameters:
CC=arm-linux-gnueabihf-gcc \ CXX=arm-linux-gnueabihf-g++ \ ./autogen.sh \ --prefix=/opt/libhybris \ --with-android-headers=android-headers \ --enable-adreno-quirks \ --enable-arch=arm \ --enable-experimental \ --with-default-hybris-ld-library-path=/system/lib \ --enable-debug \ --enable-trace \ --with-default-egl-platform=fbdev \ --enable-mali-quirks Next:
make -j8 sudo make install Then copied the /system/lib directory from the Android firmware to the root of the file system.
 
Running /opt/libhybris/bin/test_glesv2, unfortunately, failed:
user@amlogic:/opt/libhybris/bin$ ./test_glesv2 library "libgui.so" wasn't loaded and RTLD_NOLOAD prevented it test_glesv2: test_glesv2.c:117: main: Assertion `eglGetError() == EGL_SUCCESS' failed. Aborted For some reason, the system could not create a surface, test_glesv2.c, s.117:
surface = eglCreateWindowSurface((EGLDisplay) display, ecfg, (EGLNativeWindowType)NULL, NULL); assert(eglGetError() == EGL_SUCCESS); assert(surface != EGL_NO_SURFACE); I hope that someone will be interested in this task and will achieve a better result.

1. Turning the slots (if left) is useful for the option if you put the Board vertically. The Board orientation option is vertically limited by the placement of the connectors on the short sides -> to put vertically (with support on one of the short sides) is unlikely.
2. In Odroid, the position of the fins is designed for the forced air flow (fan) option regardless of the position H1. Put H1 vertically (something to support the table was on the short side with connectors) with the movement of air along the ribs and the second option vertically, with support on the long side (vertical movement of heated air across the ribs). I don't know (it's hard to estimate the real size on the photo) how big these edges are, but according to the laws of physics, the higher the height of the edges, the more effect. By the way, I advise you to look at the cooling radiators for powerful sound amplifiers of good manufacturers, how they have ribs and what size they are on the back side of the amplifier.

This radiator will be inefficient. The main location of the Board \ radiator is horizontal and without a fan, with natural air circulation. Therefore, grooves, such depth and shape, along the long side, on the surface of the radiator is not needed. Such grooves will work only in the vertical position of the radiator (that the air would move along the grooves). But then it will be difficult to connect the cables to the connectors. If you make the radiator half the thickness (reduced by the height of the grooves) and with a smooth surface it will work better than this option and the cost will be half (less metal consumption and do not need to make slots in production). Or change the direction of the slots to 90 degrees (parallel to the short side). And do not varnish or paint the radiator surface.

There is no difference what kind of burn you get, from a solid surface or from a "striped".
If the calculations can surface temperature (of any size) more than 50-60 Degrees, in such cases, use a simple protection device - a grid (fence) with a large cell (by analogy, as using protection on the fans from falling on the blades).

I'm no guru at this but as far as I know the VPU does only video processing and the rendering is either done i SW or in the GPU if supported. I don't know about Balbes images but I remember him mentioning that the no-mali images have support for quadcore in Kodi.

Since I'm not familiar with the system I don't really know what to look for, but I connected a wired network, started some games and applications which all started fine. When I clicked shutdown I could see it stopping eth0 so appares that wired network works. Shutdown was completet.
 

It is even easier, but thank you for the advice.
 
I followed this easy how-to, now I can let it click as much as I want, it stops clicking and keeps working
KODI wiki: HOW-TO: Disable PulseAudio and use ALSA (without removing PulseAudio) for Ubuntu
https://kodi.wiki/view/PulseAudio/HOW-TO:_Disable_PulseAudio_and_use_ALSA_(without_removing_PulseAudio)_for_Ubuntu
 
Would be nice if others test it and report back !

seems that you're not the only one

We are ready to go https://gitlab.com/armbian  It was working extremely slow and took ages to register. I guess everybody wants to escape the monster ASAP 

Maybe you should explain why you want to reimage and what you want to do with the new image?

Yes, install ".deb"
KODI was only a part of the image versions with Mate and XFCE (up to version 5.44). Starting with version 5.44 I no longer include KODI in the images. Because:
1. There are several variants of KODI (17 and 18). Now users decide and install the version they need.
2. Now version Armbian start to use as a regular office PC, which does not need KODI.

2.) At Android/Settings/About Device/System/updates. Note: You may have the Update and Backup app in the App Drawer.
-From the Update and Backup App, under the UpdateLocale section, click Select, select aml_autoscript.zip, click update.
 
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905/tronsmart-ac/firmware-roms-tools-at/565449-running-linux-from-sd-card-or-usb-flash-drive-using-balbes150-method-and-files
 
http://forum.khadas.com/t/instructions-installation-multios-3in1-android-libreelec-linux-from-balbes150/2107

Update images version 5.44_20180515.
 
Please note that the content of MATE\Xfce has changed. Now there is no KODI in the composition of these images. KODI packages with dependencies are in separate directories on the site. To install them, you need to download all the files from the desired directory and install manually (with the appropriate commands "dpkg -i" and "apt install -f").

Added the image of Armbian Bionic Mate. There are bugs in this image. You need to manually add the panel "Mate Bar". The Bionic-deb directory contains packages with two variants of KODI. For both versions you must install the packages aml and "aml-codec" and "aml-mali7". "aml-amremote" package is needed for remote control operation in KODI-17 version.

Tried bionic, work fine(install package from repo, uninstall etc. mpv from default repo work fine). I did not find any bugs or problems.... thanks.

There is a great variety of different builds of KODI and Libreelec for different platforms (x86 , ARM, etc) and different models. This is a different system, description, for some not suitable to others. To operate your remote control, you need a settings file. See the example files (remote.conf) on a recorded medium. For KODI-17 from the composition of Armbian, the file must match the format of the driver amremote. For KODI-18, this is a different format (lirc).

The dtb file name contains all the necessary information. For which platform, how much RAM, type of network, etc. some have an indication of a particular TV box model.

All the time (work on this is underway).
 
To All
Upgrade images 20180426 with kernel 4.17_rc2_-next.

To be honest if they drive the chip at higher voltages like 1.3V like the Allwinner H3, I think they can hit 2GHz. However, power consumption, heat, and reliability become concerns. I think they originally tested at 2GHz and made all the marketing materials but had to scale back to make power consumption and other factors look pretty. Amlogic is pretty ahead of the curve in low cost quad-core A53 SoCs. We just started getting competitor chips last year which means Amlogic is almost 2 years ahead of the curve with S905.

Maybe someone will be interested in this information.
 
http://forum.khadas.com/t/armbian-kodi-ubuntu-debian-for-sd-usb-emmc/825/155?u=balbes150