Please check the operation of different codecs on rk3328 and rk3399 in the latest 20191210 images with kernel 5.
Add image 20191210 kernel 4
Please check the operation of different codecs on rk3328 and rk3399 in the latest 20191210 images with kernel 5.
Add image 20191210 kernel 4
Trying to install in TinkerBoard. Gave an incompatibility error and did not update...
You have a model with a chip rk32xx, it needs the appropriate images with the index 32xx in the name.
The new version of images 20191209. This version changes the DTB setting principle for the Odroid N2 model. Now the principle of setting is the same for all devices. You need to use two files (uEnv.ini) and (extlinux.conf). For models based on g12 (s905x2 s922), which have a problem not the correct color of the Kodi interface, you need to use the SD card to write the image and additionally download and copy the file to the SD card (u-boot.ext).
5. Add Index of / as installation path in the file manager.
6. install the ZIP repository.emby.kodi-1.0.6.zip via Add-Ons.
I tested another installation option, I did not use the 5 and 6 step. I don't add third-party repositories. Immediately chose the search for addon EMBY and put the found versions with dependencies (they will be correct, because collected with a new version of KODI and Python3). Everything is installed without errors.
but the EMBY client still doesn't install.
Can you write the steps you are doing ? I want to test them on the latest version with kernel 5.
Update version with kernel 5 (20191130).
Used the latest Kwiboo patches.
p.s. add image old kernel 4 (20191127)
If with the image I use for CORE and ALEX I can boot from the SD. Why with LIBREELEC from the SD card does not start ?. I have changed uEnv.ini to indicate my image. Should the image be dts or dbt ?. If it has to be dts, could someone change it for me?
Read carefully the first post of this topic.
Display MoreNot working
- Wifi, bluetooth (Is working on Manjaro Linux with 5.3 kernel)
- 10 Bit Color H264/H265
- Fractional frequencies 23.976, 29.97, 59.94hz not available
- HDR
- SD Xvid/Divx videos have corrupted blocks during playback
What is the new Boot Android from emmc options?
If in Manjaro did not change the kernel (did not add patches), in the kernel everything should be enough (you can try to take DTB from their image). WiFi requires several elements. Try adding firmware (you may need your own options for Rock PI 4). I don't have this equipment, I can't help you with finding bugs. Do not pay attention to the options, they do not work yet (designed for AML).
And also when using the YouTube Adon,
I checked, the youtube plugin works on kernel version 5 (20191125).
After that the normal LE configuration starts, but after selecting the language the configuration process stops.
I can only reboot LE or turn off the SBC.
The speed of the old flash drive will be low, so when you first start (when there is a parallel intensive process of various settings) you need to take your time. I never change the settings in the wizard, only when the system works at least 20-30 minutes, you can start changing the settings. Try slowly (without changing) to go through the wizard settings and change them in an already running system.
With kernel 4 I have a Kodi interface running in 4K mode (4026). On 5 core the interface in 4K mode is not switched yet.
EMBY is an AddOn -> EMBY
I checked the installation of the EMBY 4 addon itself on the latest version with kernel 5.
I haven't checked anything for playback, but the EMBY service is available on port 8096 from a PC from the network.
These are not official test images for the RK33xx and rk356x rk3588(s).
Pay attention. Starting from version (20200826), the configuration order for the used DTB changes.
Please note that the algorithm for initial configuration of the system for startup has changed. Instead of a file "uEnv.txt", the file "/extlinux/extlinux.conf " is now used. The rules for editing a file remain the same.
After writing the image, you must correctly configure the DTB used in the file uEnv.txt
kernel 5.
Images rk3328 and r3399 and 3288 are universal, when starting from USB media images are interchangeable (the only difference is used for the image u-boot and UART console output settings). Tar archives for updating are also universal.
Note that the new generic images now use a single download directory.
Important. Changed the directory location of the images. Now all images (for all supported platforms) are in one place.
Old (not support_
https://yadi.sk/d/xhf45z3bk-joga
Add u-boot to SD card
If you have any working system on the SD card that starts normally, you will be able to check the LE. You need to try to replace the u-boot in LE, on the version with a working SD card. You need to perform a few additional steps when preparing an SD card.
1. Remove from working SD card u-boot. This can be done with this command on a Linux PC.
dd if=/dev/<name_you_SD_works_card> of=u-boot-rockpro.img bs=1M count=16
2. Write LE to SD card, configure DTB and replace u-boot with taken from working SD card. U-boot replacement is performed by two commands.
dd if=u-boot-rockpro.img of=/dev/<new_SD_card_LE> conv=fsync bs=1 count=442
dd if=u-boot-rockpro.img of=/dev/<new_SD_card_LE> conv=fsync bs=512 skip=1 seek=1
After that, you can try running LE on RockPro. The last two commands write a working u-boot and save the existing partition table for the system written to the SD card. By the way, in the same way you can replace u-boot for Armbian system and check the start of any image.
Support model :
Firefly Station M1 (rk3328)
Firefly Station P1 (rk3399)
Firefly-rk3399 (rk3399)
Firefly Station M2 (rk3566)
Firefly Station P2 (rk3568)
NanoPC T4 (rk3399)
Quartz64 A (rk3566)
Quartz64 B (rk3566)
Banana Pi BPI-R2 Pro (rk3568)
Firefly Station M3 (rk3588s)
Rock 5b (rk3588)
Firefly ITX (rk3588)
Khadas EDGE2 (rk3588s)
Mekotronics R58x (rk3588)
Mekotronics R57 (rk3576)
What image to choose for odroid N2 and also possible install to emmc card?
The amlg12 image runs on N2. In the LE settings menu, there is an item to create a full eMMC backup before installation and an item to install LE in eMMC. For quick and easy testing of systems from different media (including USB flash drives), I recommend switching to SPIboot. The details there is in this topic previously.
EMBY
I'm sorry, I didn't understand what that means, what needs to be checked ?
The new version 20191123.
with updated some Addons.
New versions 20191123 with update Addons.
Added on site version of way of 20191120 with core 5 on base Panfrost. There is no HW decoder yet, but the performance of rk3399 is quite enough for SW video decoding with 1440p (1080p screen resolution). Tried with USB stick on the N6, all of the test videos worked.
Did you find a box? Looking for something with similar specs, only be using it to play mkvs from external hard drive. Could do with gigabit LAN as I have 1000mbps internet. I've done a lot of reading on this thread but feeling a bit confused... I suppose the simple solution would be a Minix U9 but that's almost Nvidia Shield money where I live!
Currently using a cheapo x96 s905x 1gb ram box that I had gathering dust in a drawer, it works but sometimes buffers or freezes with high bitrate 4k mkv's.
To date, a reasonable option for the ratio of costs\the result is Ugoos x2pro 4\32 or cube 2\16 (2 GB of RAM is enough to play media content). This model has full support for all elements (including WiFi) on core 5. If you don't need built-in WIFI and need maximum performance, you can use the AM6 (with metal body and excellent passive cooling system). These models use the best Android firmware (with long-term support for updates), with support for universal multi-boot. This means that you can immediately and easily run any modern system (LE, Armbian, Manjaro etc.) from external media (including USB 3.0 with a speed faster than eMMC and no volume limit of up to several terabytes) and fully retains the ability to automatically update the standard firmware via OTA.
Just for interest I looked into android_enable/disable scripts..shouldn't the correct echo-line be: echo "Start disable reboot from Android" in the DISABLE script like I altered in mine on the picture
This is the service information that remained after debugging and it does not affect anything.