balbes150

Uploaded to the site fixed version 5.72 for S905. Now in the kernel 4.20 has gxbb (S905) work sound HDMI. Additionally fixed DTB from Tronsmart Vega S95 (Pro Meta Telos). Now these files work.
 
To the right of the button "Raw" View" etc
 
 

add 5.72 NEXT kernel 5.0 for s9xxx

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
 

If everything works at 5.0, there's no point in dropping to 4.20.

If everything works at 5.0, there's no point in dropping to 4.20.

How to extract DTB from an RK3328 TVBOX
The DTB is in the resource partition and it's less than 100 KB long in size.
With this scripts you can get it from a TVBOS. I've enabled USB debugging and Internet ADB in developer options within TVBOX setup. Change the IP in connect to fit your environment
ubuntu@ubuntu-Ci5:~$ adb connect 192.168.0.142:5555 connected to 192.168.0.142:5555 ubuntu@ubuntu-Ci5:~$ adb shell rk3328_box:/ # cd data rk3328_box:/data # cd media rk3328_box:/data/media # cd 0 rk3328_box:/data/media/0 # cd Download rk3328_box:/data/media/0/Download # dd if=/dev/block/by-name/resource of=resource.img bs=100k count=1 1+0 records in 1+0 records out rk3328_box:/data/media/0/Download # exit ubuntu@ubuntu-Ci5:~$ adb pull /data/media/0/Download/resource.img 393 KB/s (102400 bytes in 0.254s) ./extract-dtd.py resource.img And you get the dtb in the dtb folder

Hi @balbes150
Here you have my mx-10 internal dts
mx-10-from-box.dts

Have you implemented these guidelines ?
 
There can be no identical label. The installation script specifically changes the eMMC label and uses its eMMC value in the settings. Using UUID is a bad solution that is often used by those who do not want to properly design the installation system.
 

We are already working several months to adopt build system to be ready for such integration. Since there is very little help and huge demand from the community side, we are moving very slow.

First I want to say that all my tests are on a MX-10 4/32 Oreo 8.1. Kernel compilation an tests are done into the same machine. Mx-10 DOS NOT use ssv6051 wifi but rtl8723bs. Once this said I can help a bit with this. It seems sources are still forn android defaults
 
In drivers/net/wireless/rockchip_wlan/ssv6xxx/firmware/ssv6051-wifi.cfg  , change
firmware_path = /vendor/etc/firmware/ ----> firmware_path = /lib/firmware/ssv6051/ In drivers/net/wireless/rockchip_wlan/ssv6xxx/ssvdevice/ssvdevice.c change line 61
char DEFAULT_CFG_PATH[] = "/vendor/etc/firmware/ssv6051-wifi.cfg"; with
char DEFAULT_CFG_PATH[] = "/lib/firmware/ssv6051/ssv6051-wifi.cfg"; And drivers/net/wireless/rockchip_wlan/ssv6xxx/firmware/ssv6051-wifi.cfg must be installed in /lib/firmware/ssv6051 directory
You also need firmware file installed in this folder (ssv6051-sw.bin got from armbian for S905 3.14 Kernel)
ssv6051-sw.bin

The new version 5.71 20190118.
Updated kernel to 4.20.2.

Tell me, do you create problems on purpose ? I wrote you what you need to do on TV box, where you have already created a problem. And only after you find the right solution for the spoiled TV box, you can start experimenting with others.
 
What DTB did you use on the second TV box ?
 
Show the full contents of the "uEnv.ini " and " extlinux.config" after you have edited them.

Good news
Update version NEXT kernel 5.0.0-rc2 20190118.
Khadas VIM1 has WiFi And BT without any patches. Perhaps some of the other models Wi-Fi will work.

1. The structure that gparted shows is correct. The installation script is specially written so that it is as safe as possible to put the system in the eMMC. It keeps all the important data structure of the standard firmware in eMMC (u-boot env recovery boot etc). This allows you to use regular tools to restore native Android firmware in any TV box at any time.
2. When you renamed the file " s912-u-boot.img", you took the risk (I warned about this earlier in this topic) of replacing the regular u-boot-2015 with a new version of u-boot-2018. New version assembled and tested only on Khadas VIM2 (it I told). So when you replaced your u-boot-2015 with a new one, you got a problem. The new u-boot-2018 cannot work with standard firmware tools. It is not known whether the new u-boot is compatible specifically with your TV box model or not.
3. You may now have to perform special steps to restore the health of your TV box.
4. All new versions are specially launched from external media to check if everything works on your hardware correctly. Only then is the installation done on the eMMC. For example, in core 4.x there is no support for many Wi-Fi on some models does not work USB, etc.
5. If USB does not work, to restore the ability to control the system , you have to use either SSH through the network or UART. At that moent when you installed the new version into eMMC, but it is not working USB, have you had the opportunity small means to restore the system to its previous level, but again you hurried and did not wait for advice on how to do it.
6. I do not understand what the current state of the system in eMMC is. What happens if  turn on the TV box, which messages appear on the screen ?
 

Hello. I'm still testing, I want to post a howto/script when I have some more results.

1. Universal multi-loading is a prerequisite.
2. The installation process is simplified, now it is enough to run one installation script, it contains all the steps (which were previously in two scripts).
 
 
I left until the previous version of the steps, perhaps someone will use the first versions of the images.

Okay, so just to avoid hijacking this thread, we can continue the discussion about this in a new one. I'll tag you when I start it. I'm very interested in this topic too.

Update 5.71 . Please note that there are no big changes in these images, for those who already have the system running do not need to update.

Yes, I noticed that if you launch it just like "kodi", it won't start here, unlike the RK3399 where it worked.
 
The cause seems to be that "standard" mali midgard T86x binaries have the necessary GBM symbols that Kodi uses, while in the case of utgard 450 you need to use the specific binaries for GBM.
 
Solution: launch it in one of these two ways:
LD_LIBRARY_PATH=/opt/libmali-gbm kodi or:
kodi-gbm-wrapper  

Congratulations, great job.
 
Quick check on MVR9
the browser now shows videos in full screen all up to 4K, the only limitation is the channel in the Internet.
MPV-also shows everything in full screen
KODI -  not yet started up, complains that it is impossible to create the GUI (this is not critical, KODI is LE, everything works)
I haven't checked the rest yet.
 
 

We will test 
 
 

Hello community, I am very grateful with the Armbian forum, since I have all my arm boards with this operating system and now I have the tv box https://es.aliexpress.com/item/MX-TV-caja-Android-8-1-9-0-mx10-4-GB-DDR4-32-GB-64-GB/32858434465.html?spm=a2g0s.9042311.0.0.7e6863c02aoLoU and I have it working all right server mode, here I share the backup of android 9 MX10 4G-32G  .
http://www.mediafire.com/file/55p1pffcjooaoc5/backup_image.img/file
 
 

THE MEDIA SCRIPT IS NOW DEPRECATED, IN FAVOR OF THE OFFICIAL MULTIMEDIA FRAMEWORK. PLEASE REFER TO THIS TOPIC:
 
 
And, for last,  the first version of:
The UN-official, UN-supported, UN-expected
RK3328 MEDIA TESTING SCRIPT
 
This is the first release of the RK3328 media testing script. The script provides a functionality similar to its RK3288/3399 equivalents, except for the OpenCL related stuff, which is not supported by the SoC. So it includes:
Installing all the libraries and system configurations necessary for GPU accelerated X desktop, Chromium WebGL, full VPU video play acceleration up to 4k@60 10-bit HEVC (the maximum supported by the SoC), and GLES 2.0 support. Three video players supporting full VPU acceleration (RKMPP) and KMS display (GBM or a X11 DRM "hack", as described by the authors), namely: MPV, Gstreamer and Kodi. A library that will act as an OpenGL to OpenGL-ES wrapper, allowing you to run programs that use OpenGL 1.5-2.0. Two additional features, that have no big interest from the Armbian development prospective, but I find them interesting to play with: Chromium browser with support for Flash and DRM-protected commercial web video streaming (tested with Amazon Prime, should also work with Netflix, Hulu, etc.), and a simple Pulseaudio GTK equalizer using LADSPA.  
Here is a more thorough documentation:
 
 
 
>>> DOWNLOAD LINK <<<
 
Prerequisites:
You need a fresh Armbian Bionic desktop image with default kernel installed. 
 
Instructions:
Download the file above Untar it: tar xvf media-rk3328_*.txz cd media-script ./media-rk3328.sh  
Notes:
This script is not officially supported by the Armbian project. It is just a community effort to help the development of the main build, by experimenting with a possible implementation of the media capabilities of this particular SoC. Therefore, questions about the script should not be laid out as support requests, but as commentaries or community peer-to-peer assistance. That being said, all commentaries/suggestions/corrections are very welcome. In the same way, I will do my best to help solve any difficulty that may arise regarding the script.  
Enjoy!

two S905x converted in linux machines :-)
 
using
 
Armbian_5.67_Aml-s9xxx_Ubuntu_bionic_default_4.19.6_desktop_20181207.img
 
one for DHCP and DNS server, and other lan stuff, second for zoneminder ip cameras controlling
 
two are modded for heat dissipation with aluminium heatspreader and ceramique2 thermal paste, more than 80°c in full, to 56°c full...
 
https://drive.google.com/open?id=1dJJ3gR2iOlKDB4s1O8BMBRZQtKtqoOLc
 
https://drive.google.com/open?id=1lKWpTCbooglkXVeCaTMWEECsJ3aBWcnu

I was very pleased with Gstreamer. ON 4K TV, you can scale any video to any size on your desktop. (now can use any player or write your own). 
 
Now I test different videos in MPV Gstreamer KODI and browser on TV 4K (4096х2160), impressive performance RK3399 .