Search the Community

TV Box Status Information Template Version 1.0 TV Box Name: MXQ Pro 4k 5G (fake 16GB RAM/128GB ROM) CPU: Allwinner H3 Armbian build file name: Armbian_21.08.1_Orangepipcplus_focal_current_5.10.60.img.xz / Armbian_21.08.1_Orangepipcplus_buster_current_5.10.60.img.xz (both works) DTB file used: <none> Kernel Version: 5.10.60 Distribution Installed: focal and buster Working Ethernet (Yes/No): yes Max Ethernet Speed that works (100/1000): 100M Does wifi work (Yes/No): yes Does bluetooth work (Yes/No): not available Does HDMI audio work (Yes/No): yes Additional Comments (provide any additional information you feel is important): all other functionalities for Orange Pi PC Plus is not available (eg OTG function of USB and no GPIO). You can also run "nand-sata-install" command to install armbian to emmc, works fine, no issues.

In Ubuntu 22.04 is Docker / Portiner broken then missing handles is disabled in the kernel # CONFIG_BPF_SYSCALL is not set. docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: bpf_prog_query(BPF_CGROUP_DEVICE) failed: function not implemented: unknown. Edit: It can also being problems with docker is using CGroupsV2 and that is not supported in all installations and need patching the system for using V1.

Rikomagic RKM V7 is an HDMI TV stick running Android 11 on a Rockchip RK3568 quad-core Cortex-A55 processor with 2GB RAM, 16GB flash, Gigabit Ethernet and WiFi 5/6 connectivity, as well as HDMI female port, and two USB ports. While the device could be used as a general-purpose Android mini PC, it is also suitable as a digital signage player with features such as RTC for time on/off control, screen rotation support, and a watchdog timer to ensure continuous operation even if a software crash occurs. Rikomagic RKM V7 specifications: SoC – Rockchip RK3568 quad-core Cortex-A55 processor @ up to 2.0 GHz with Arm Mali-G52 2EE GPU with support for OpenGL ES 1.1/2.0/3.2, OpenCL 2.0, Vulkan 1.1, 0.8 TOPS NPU for AI acceleration, 4Kp60 H.265/H.264/VP9 video decoding, and 1080p100 H.265/H.264 video encoding System Memory – 2 GB or 4 GB LPDDR4 Storage – 16 GB or 32 GB eMMC flash, [...] The post Rikomagic RKM V7 – A Rockchip RK3568-powered Android 11 HDMI TV stick appeared first on CNX Software - Embedded Systems News. View the full article

I need help, I don't quite understand how the support for this processor is, but I tried to find an image for the amlogic s905x3 and I can't find a specific one, so I come to you to see if you can send me a download link for this specific processor.

Hi, I have installed latest armbian linux OS into amlogix x96 max+ (S905X3) device. (op-hub link here) Would like to run chromium browser and play youtube videos etc., but I see videos are lagging, experiencing slowness and mostly it got crashed. Here is the command I used to run. chromium-browser --disable-software-rasterizer --disable-gpu-driver-bug-workarounds --disable-gpu-driver-workarounds --disable-gpu-vsync --disable-features=UseOzonePlatform --disable-reading-from-canvas --enable-accelerated-2d-canvas --enable-accelerated-video-decode --enable-accelerated-mjpeg-decode --enable-features=VaapiVideoEncoder,VaapiVideoDecoder,CanvasOopRasterization --enable-gpu-compositing --enable-gpu-rasterization --enable-oop-rasterization --enable-raw-draw --enable-zero-copy --ignore-gpu-blocklist --use-gl=desktop --num-raster-threads=6 Logs: [13757:13757:1115/170432.940814:ERROR:vaapi_wrapper.cc(3127)] Failed to initialize VAAPI libs [13757:13757:1115/170432.962938:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is desktop, ANGLE is [13757:13757:1115/170433.003383:ERROR:gl_angle_util_vulkan.cc(17)] Failed to retrieve EGLDisplay [13757:13757:1115/170433.003690:ERROR:vulkan_instance.cc(91)] Failed to get vkGetInstanceProcAddr pointer from ANGLE. MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load swrast driver If I run with sudo, I won't get 'cannot open shared object fil' error but still experiencing the same. Could you please share some insights on this ? version details in chrome -> https://ibb.co/TBBwTHN gpu in chrome -> https://ibb.co/Tmzp86c

Hello to everyone, i have a China no name tv box with s905 cpu. I try to install armbian but no success, don't have any experience in amlogic procedure. Can anyone point me to the right img file and some instructions please. My box is named as mxq pro 4g but i know its a fake one. Thank you very much.

Proposal to create a Community Supported config for Amlogic based TV Boxes to pickup the work that was done previously by balbes150 but is no longer supported by him. This also provides a place where development can occur within the Armbian framework since others on the internet are producing builds called Armbian that are not done from within the Armbian community. The strategy for Amlogic based TV Boxes has been to reuse the native u-boot that comes installed on the box on emmc. Through a process called 'multiboot enabling' a u-boot script is run to change the default u-boot environment to have the boot process look for a chain-loaded u-boot on either the sd card or usb. If found that 'u-boot.ext' file is loaded and the boot process continues on the armbian image on sd or usb via configs in the extlinux.conf file. So currently the armbian build process creates and installs a u-boot in the image, but that isn't actually used (as the boxes emmc u-boot is what is used). The 'chain-loaded' u-boots (u-boot-* , different ones for different cpus) are currently pre-built and included as binary blobs. The installation instructions currently exist in the forums.armbian.com TV Box forum and are the same as for the balbes150 builds that previously existed. (basically the user is requested to copy the appropriate u-boot-* binary to u-boot.ext for their boxes cpu and edit the extlinux.conf file with the appropriate dtb file for their box). Things seem to work about as well as they did with balbes 5.9 kernel based builds, although I generally focus testing on server builds and don't do too much with desktop builds, There is one issue that needs some sort of resolution however. On the s905x2 box I have (H96 Max X2) the armbian build kernel (meson64) can't read the sd card. However an unpatched mainline kernel works on this box. I have tracked down the offending patch to be: general-meson-gx-mmc-set-core-clock-phase-to-270-degres.patch Without this patch the box boots fine, with it it fails to boot. I'm not sure how to work around that. All comments are welcome. I essentially cloned the lepotato config. I choose aml-s9xx-box for the name, as that kind of follows jock's naming convention for rk based tv boxes, but am open to any suggestions. Changes to be committed: new file: config/boards/aml-s9xx-box.tvb modified: config/sources/families/include/meson64_common.inc modified: config/sources/families/meson-gxl.conf new file: packages/bsp/aml-s9xx-box/boot/aml_autoscript new file: packages/bsp/aml-s9xx-box/boot/emmc_autoscript new file: packages/bsp/aml-s9xx-box/boot/extlinux/extlinux.conf new file: packages/bsp/aml-s9xx-box/boot/s905_autoscript new file: packages/bsp/aml-s9xx-box/boot/u-boot-readme.txt new file: packages/bsp/aml-s9xx-box/boot/u-boot-s905 new file: packages/bsp/aml-s9xx-box/boot/u-boot-s905x-s912 new file: packages/bsp/aml-s9xx-box/boot/u-boot-s905x2-s922 new file: packages/bsp/aml-s9xx-box/root/fstab.template new file: packages/bsp/aml-s9xx-box/root/install-aml-s905-emmc.sh new file: packages/bsp/aml-s9xx-box/root/install-aml.sh Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number [AR-9999] How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Built and installed on s905w (TX3 Mini), s905w (X96 Mini), s905x2 (H96 Max X2), s905x3 (TX3-X3) [x] Tested install to emmc Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

For a beginner like me this is a difficult box to install Armbian on. Before attempting the installation I had managed to install Armbian on a NexBox A95X (S905), and a M8S (S812). I want to share my experience with others because even though every box is different, what I did to install Armbian may give other users ideas on what to try on their own boxes. It is also good to record what I did in case I have to do it again years down the road 😅 The problem with the unit is that it is heavily customized, specially the boot loader. Even though it has a reset button, the usual toothpick method always result in the built-in rescue, i.e., it ignores aml_autoscript. The Android 6 that came with it is also heavily customized and does not have the usual "Update & Backup" app that can be used to trigger aml_autoscript. Fortunately, the unit does have the JTAG connectors already soldered and ready to go, so I can see what is going on. I remembered that on some S905 systems one can do a "recuscue" of a bricked unit via a bootable SD card, using a program called BootcardMaker.exe supplied by AMLogic, which is a way to basically mimicking USB burn but without a USB link: https://chinagadgetsreviews.com/download-amlogic-burn_card_maker-v2-0-2.html For the burn to work one must use the correct u-boot.bin which I have obtained previously for when playing with the M8S from M8S_S812_2GB_26102015.zip via links I found in OTT M8 BCM4335 Bricked/Unbricked: https://forum.freaktab.com/node/550706 https://mega.nz/#!V08yhQ6C!e37b8y7F6mDCc_vQ0c_7IgNNeuHGhT1b5Ld2vwmTJa0 After all this work, I still cannot trigger aml_autoscript, but something did haapen and I see the following lines in the boot log: [mmc_init] mmc init success Device: SDIO Port B Manufacturer ID: 3 OEM: 5344 Name: SU02G Tran Speed: 25000000 Rd Block Len: 512 SD version 3.0 High Capacity: No Capacity: 1.8 GiB mmc clock: 25000000 Bus Width: 4-bit reading auto_update.ubt ** Unable to read file auto_update.ubt ** wipe_data=successful wipe_cache=successful So it look like the bootloader is trying to load from a file called auto_update.ubt. With nothing to lose, I simply copied aml_autoscript to auto_update.ubt and rebooted again. Lo and behold, I got into TWRP. By accident I left a copy of TWRP as recovery.img on the same SD card. This recovery.img is from TWRP_S905X_V3020_generic_AndroidPC.zip download from https://androidpctv.com/tutorial-install-twrp-android-tvbox-amlogic/ http://uploaded.net/file/48zxgple So I took the opportunity to backup my Buzz TV XPL3000.😁 After that I looked at the boot log again and I see that after loading auto_update.ubt it tried to look for a file called factory_update_param.ubt not finding it, it read recovery.img: reading factory_update_param.ubt ** Unable to read file factory_update_param.ubt ** reading recovery.img So I tried the same trick, this time copying the file s905_autoscript to factory_update_param.ubt and rebooted the unit. Now I am able to boot into Armbian. Victory!

I recently came into possession of a Z69 Android TV Box (3/32GB) with a S950X chip. I tried @SteeMan's Amlogic guide, but can't seem to find @balbes150 files referenced in the post (only RK/Allwinner). I then tried compiling an Armbian img from https://github.com/ophub/amlogic-s9xxx-armbian (build jammy; s905x; kernel 5.10.135_5.15.50). I tried amending the config file but found it quite different from the ones in youtube videos or on the forums. There was a "u-boot-s905x-s912.bin" which I renamed to "u-boot.ext". However, when I did the toothpick method, the S905x bootscreen came up, followed by the splashcreen of the android box. The screen was black for a while and then it booted into the normal android OS. The black screen seemed longer than when I booted the machine without pressing the reset button. I'm rather confused and just can't seem to find the right files from the guides. Would really appreciate any guidance here.

DISCLAIMER (PLEASE READ): everything you can find in this thread (binaries, texts, code snippets, etc...) are provided AS-IS and are not part of official Armbian project. For this reason not people from Armbian project nor myself are responsible for misuse or loss of functionality of hardware. Please don't ask about support or assistance in other non-community forums nor in the official Armbian github repository, instead post your questions in this thread, in the TV Boxes forum section (hardware related) or in the Peer-to-peer support section (general linux/software related). Thank you! This is CSC Armbian for XT-Q8L-V10 boards, also known as Chiptrip Q8, Vsmart Q8, ENY 3288 Q8, etc... All source code has been merged into Armbian mainline project. I still keep my personal public Armbian fork for experimental features: https://github.com/paolosabatino/armbian-build Nightly images: download directory Quick installation instructions on eMMC: Build or download your preferred Armbian image from Download directory and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn image to flash" from the menu, then select the destination device (usually mmcblk2) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the sd card, then push the power button for 1 second (the led will turn blue) After 10 seconds HDMI will turn on and you will get logging messages; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Boot from SD Card/USB stick (with Armbian already installed in eMMC, empty eMMC or no eMMC😞 Build or download your preferred Armbian image from Download directory; Burn the image on your SD card/USB stick; Plug the SD card/USB stick in the device; Push the power button for 1 second (the led will turn blue); After 10 seconds HDMI will turn on and you will get logging messages; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Boot from SD Card/USB stick (with original firmware or other firmware): In case your box has the original firmware installed, use the Multitool to erase the internal flash. Don't worry, you will not brick your box: once the eMMC is emptied, the box will automatically boot from SD Card. This is called Maskrom mode and is common to all Rockchip devices. Instructions and download links for the Multitool are at the bottom of this post. After erasing the internal eMMC, just follow the "Boot from SD Card" procedure above and then you are fine. Boot priority: Newer images (those with mainline kernel >= 4.14.50) now support booting from multiple devices. Priority is fixed and boot devices are probed in this order: External SD card External USB storage device (Any USB Stick/Hard drive attached to USB host ports) Internal eMMC This way even if you install armbian to internal eMMC, you can still easily test different images booting from external devices. Experts notes: when armbian is installed into eMMC you get U-boot installed too in eMMC. This is important to know because the box won't boot in Maskrom Mode, but instead will always boot the embedded U-boot, no matter if you put an sdcard/usb stick. In practice the embedded U-boot is totally responsible for the boot priority. If you want to restore the Maskrom Mode, just erase U-boot from eMMC using this command: dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=8128 conv=sync,fsync Current status: Wireless: works. pretty fast and stable, signal is strong on my box; Bluetooth: works. I was able to transfer files and stream audio without problems USB ports: works, with autosuspend too. A quick benchmark show that transfer rate is quite good (topped at 34 MB/s) USB OTG: works in host mode. Transfer rate is very good (> 40 MB/s) MMC: works and is perfectly accessible as storage device. The images above with "eMMC friendly" have been tested and work when installed in eMMC using the standard armbian-config eMMC installer SDCard: works. legacy kernel is limited to high speed, while mainline works fine in UHS mode too. A quick benchmark with a Samsung EVO card shows the promised 48Mb/s read speed. Gigabit Ethernet: works, fast and reliably HDMI: works perfectly Serial: works Audio: both HDMI audio and SPDIF connector works IR remote: works on legacy and mainline kernels Reboot/Suspend process: rebooting the device is a working in progress, at the moment sometimes it works and sometimes it doesn't. Suspend is still not available. Hardware acceleration: everything which works for rk3288 boards applies here too. This guide or maybe the Media Testing Script will help you gain an hardware accelerated X11 and Chromium (using GL4ES I enjoyed Quake 2 from the start till the end, but also Quake and Quake III Arena work flawlessy, here a quick how-to to compile and install GL4ES) Multimedia: On mainline kernel 3D acceleration is provided by Panfrost driver and is already enabled. Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/ Multitool: The Multitool is a small but powerful tool to easy operate on internal eMMC flash of RK3288 devices. Features: Backup the content of internal eMMC Restore a previously backed-up image to eMMC Erase the eMMC (via fast blkdiscard or zero-fill as fallback) Burn an Armbian (or LibreELEC) image directly on the eMMC Provide a recovery shell for manual maintenance Windows-friendly: everything is placed in a NTFS partition Image compression format autodetection: they are decompressed on-the-fly during burn process Network support for remote maintenance via SSH (instructions to access via network here) Instructions are simple: Download the image from here Burn it on an sdcard Open the NTFS partition with your preferred file manager Place the images you want to burn on the device in images directory (backups will be stored in backups directory) Plug the sd card in the RK3288 device Power the device and wait few seconds, the Multitool menu will appear on screen and can be navigated with the keyboard Last edit: 07/06/2020 - updated installation instructions

Amazon has just launched the “all new” Fire TV Cube streaming device with an Amlogic POP1-G octa-core Cortex-A73/A53 processor that we never heard of, but that appears to be almost the same as the Amlogic A311D2 processor that we reviewed in Khadas VIM4 SBC. The Amlogic POP1-G (aka Amlogic – AML Popcorn) also integrates an Arm Mali-G52 MP8 GPU clocked at 800 MHz, and the third generation Fire TV Cube features 2GB LPDDR4/x memory, 16GB storage, WiFi 6E and Fast Ethernet, as well as an HDMI port. Fire TV Cube 2022 specifications: SoC – Amlogic POP1-G (Amlogic AML Popcorn) octa-core processor with four Cortex A73 cores @ 2.2 GHz, four Cortex-A53 cores @ 2.0 GHz, Arm Mali-G52 MP8 GPU @ 800MHz with OpenGL ES 3.2 support System Memory – 2GB, LPDDR4/x – 4224 MT/s Storage – 16GB eMMC flash Video 1x HDMI output port up to 4Kp60 with HDR (HDR10, [...] The post Amlogic POP1-G octa-core Cortex-A73/A53 processor shows up in Amazon Fire TV Cube 2022 appeared first on CNX Software - Embedded Systems News. View the full article

We are developing an open source TeamViewer alternative called HopToDesk, it is built for ARM and runs on RPI and may work on other ARM-based devices, we hope to find some help testing on Banana Pi or Android TV devices. If anyone could provide us some feedback or point us in the right direction, it would be great.

Geniatech DB982 is a development board/motherboard powered by an Amlogic T982 quad-core Cortex-A55 processor designed for 8K televisions and equipped with an ATSC 3.0 TV tuner. The board ships with up to 4 GB RAM and up to 128 GB eMMC flash, and also includes three 4K HDMI inputs, LVDS and ultra-high-definition VX1 LCD screen interfaces, as well as Fast Ethernet and WiFI 5 connectivity. Geniatech DB982 specifications: SoC – Amlogic T982 CPU – Quad-core Arm Cortex-A55 processor up to 1.8GHz GPU – Arm Mali-G52 MP2 (2EE) GPU supporting OpenGL ES 3.2, Vulkan 1.1 and OpenCL 2.0 APIs AI accelerators – 2x NNA accelerators with INT8 inference performance up to 2.6 TOPS Manufacturing process – 12nm System Memory – 2GB (4GB optional) Storage – 16GB eMMC flash (8 to 128GB optional) Video Output 1x VX1 up to 8K resolution (CNXSoft: I suppose it stands for V-By-One interface) 1x 30-pin [...] The post Geniatech DB982 – An 8K TV motherboard with Amlogic T982 CPU, ATSC 3.0 TV tuner appeared first on CNX Software - Embedded Systems News. View the full article

i try to instal armbian in tv box ,but in the boot carpet didnt find dtb for h3 only for h5 or up

Amlogic S928X multi-core Cortex-A76/A55 8K media processor, which may have been initially known as S908X, is being showcased at ICB2022 in Amsterdam in the “SEI 8K Box” developed by SEI Robotics. Amlogic S908X/S928X was first discovered in a roadmap in 2019 and was expected to launch by the end of 2020 at the time. But after a long wait of nearly three years, the Amlogic S928X processoris finally showing in SEI 8K box with an HDMI 2.1a 8K video interface, supports for HDR and advanced audio codec like Dolby Atmos and DTS, and support for Smart Home functions through an IoT module with WiFi 6E, Zigbee and more. SEI 8K box preliminary specifications: SoC – Amlogic S928X multi-core Cortex-A76/A55 processor, next-gen GPU (likely Mali-G610?); 12nm process System Memory – 64-bit DDR Storage – eMMC flash Video Output HDMI 2.1a up to 8Kp60 (7680 x 4320 resolution) with HDR10+/HLS, Dolby Vision, [...] The post 8K TV box powered by Amlogic S928X Cortex-A76/A55 processor showcased at IBC 2022 appeared first on CNX Software - Embedded Systems News. View the full article

Hello, Thank you for the guide how you do that? I've succesfully installed armbian in my X96max+, but the "thootpick" doesnt work anymore, so cant use any usb_burning_aml to "rollback" into original android.

EDIT: This how-to is slightly out-of-date, because now the complete images for RK3318 boxes are available here. Thanks to community, especially to @jock. Hello all, I would like to summarize the required steps to boot armbian on device with RK3318 chip. I have a X88 Pro device already mentioned here. I am quite skilled but information are spread in many posts and I spent lot of time to have a clear picture. Note that instructions below are valid at this time when I am writing it - some things can change in the time... And hope linux is your friend... You need 4 files: Armbian image (Links to download armbian image is in the first post of this thread) - thanks to @balbes150 U-boot image and DTB file for RK3318 from here - thanks to @hexdump trust.img file from here - thanks to @caruso As you see - actually Armbian 20.10 builds are in the file. Select the image for installation according your needs: smaller files have no graphical desktop (only terminal/command line) bigger (desktop) files are full Graphical desktop releases buster and bullseye are the Debian releases focal and bionic are Ubuntu releases I selected the Ubuntu desktop. Uncompress selected image: xz -d Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img.xz Burn the uncompressed image to the SD card: dd if=Armbian_20.10_Arm-64_buster_current_5.9.0.img of=/dev/<yoursdcard> bs=10M status=progress Change <yoursdcard> as needed. In my case the SD card is /dev/sda so my command was: dd if=Armbian_20.10_Arm-64_buster_current_5.9.0.img of=/dev/sda bs=10M status=progress Then you need to burn U-boot and Trust Images: dd if=uboot-rk3318.img of=/dev/<yoursdcard> seek=16384 dd if=trust.img of=/dev/<yoursdcard> seek=24576 Again change <yoursdcard> as needed... Now flush the cached writes to the SD card. sync Now remove the SD card from computer and re-insert back. You should see the two partitions on SD card - BOOT and ROOTFS. Copy the DTB file (rk3318-t9-mainline.dtb) to the folder /dtb/rockchip/ in BOOT partition. And edit the file /extlinux/extlinux.conf in boot partition to use this DTB. You can remove commented lines (# at the beginning). My file looks like this - APPEND line is taken from RK3328 part: LABEL Armbian LINUX /zImage INITRD /uInitrd # rk-3318 FDT /dtb/rockchip/rk3318-t9-mainline.dtb APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff130000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 After editing flush the writes by sync command again, and remove the SD card from computer. Insert SD card to your RK3318 device and boot... You can experiment with different DTB files and settings... Good luck.

Hi all. May I ask here? Just found a mention of EMCP only here. I got such a board, not a single image is loaded from it. Allwinner H3 processor, jwa60 memory. I think it's all about memory. Advise what to do next? How to run an image from it ( foto

Hi, I am new to this site, so far I have not been able to find a newbie list of what type of hardware to start with. I do not have any device yet. I have been looking at the android tv boxes on amazon, and I want to start with a $30 box, to be able to load linux on it, and have a graphical interface (ie like a Gnome/KDE desktop view) and then be able to install a vnc server, so the device can be controlled remotely. I have two projects in mind: 1. a chromium based browser install, for viewing webpages and playing any videos embedded in those webpages. 2. later on, perhaps with different more robust hardware?, add the capacity to install a media player type interface, ie Kodi, so my elderly parents could watch home movies, or view photos, and listen to their aac music. The vnc desire/requirement is so that I could connect over the internet and upload new content to their storage device, and assist them with any problems they were having. If this forum has a topic that you can point me to, to understand what types of device I should start looking at, without getting too overwhelmed for a newbie, I would appreciate it. Otherwise, if you know of an Android tv box in the $30 price range that will work for project #1, please recommend it in the reply. and if you also have recommendations for project #2, i.e. what type of hardware device upgrade should I consider for movie playback (it is not 4k, even 720 or 1080 is good enough), I would also appreciate that, or even your commentary if there is no hardware upgrade needed. Thank you.

hello, i have a tvbox with ik316 processor. Can anyone give me a tip on how to install r armbian on it? Thank you very much in advance

Hi all. I just want to apologize for my English, I write everything through a translator. Can you please tell me how to turn on the TV output now? Previously, this was done via /boot/script.bin

Hola, tenia mi tv box como consola arcade con una microsd externa, despues me deshice dela memoria y utilice el tv box normal, pero a la semana se quedaba congelado en el logo de tx3 mini, despues intente instalarle un firmware por medio de una microsd, pero solo se quedo en pantalla verde, retiro la microsd y lo enchufo a la corriente electrica y no da imagen, solo enciende una luz roja en el aparato, ayuda porfavor. CS_905W_TX_2C_N_V1.6 2GB Y 16GB

It is now 2 weeks I run linux-image-current-meson64 with no problems. I manage to get rid of tearing while playing video with vlc by using wayland/weston instead of X11/openbox (picom did not help). While playing video cpu goes from around 40% in X11 to 20% with weston \o/. You can find vlcd.service, scripts and config files in attached files. TODO list : - Move vlcd.service to weston.service and try to replace vlc-xxxx.sh scripts with ~/.config/systemd/vlcd.service - format /boot in ext4 vlcd.service vlcd-start.sh vlcd-stop.sh weston.ini vlcrc.wl

In the first part of MECOOL KP1 smart projector review, I checked out the package content, projector design, and integrated HDMI stick running Android 11 TV, before going through the setup wizard, and trying the projector with Android 11. I’ve now spent more time with the device, so I’ll report my overall experience. The best way to install the projector is probably to mount it on a ceiling or a wall, but in my case, I just placed it on top of a shelf itself placed on top of a table to adjust the height for a comfortable viewing experience from our comfy seats. As we’ve seen before, the projector will boot directly to the Android 11 TV launcher from the included MECOOL KD5 TV stick. Android 11 TV OS runs on top of Linux 5.4.125, as we can see it’s a Hailstorm device that’s certified for Netflix and an [...] The post MECOOL KP1 projector review – Part 2: Android 11 TV OS and Full HD clarity appeared first on CNX Software - Embedded Systems News. View the full article

Allwinner H618 processor has started to show up in several TV boxes running Android 12, and capable of playing 6K/4K VP9 and H.265 videos with devices such as T95Z Plus and T95 Max, which may be confusing, as companies are reusing those model numbers over and over. Featuring a quad-core Cortex-A53 processor, an Arm Mali-G31 MP2 GPU, and 6K video support, the Allwinner H618 looks exactly like the Allwinner H616 processor except it can run the more recent Android 12 operating system. There’s not much public information about Allwinner H618 at the time of writing, but let’s check T95Z Plus specifications to see if we can find any other new hidden features: SoC – Allwinner H618 quad-core Arm Cortex-A53 processor @ up to 1.5GHz with Arm Mali-G31 MP2 GPU System Memory – 2GB or 4GB RAM Storage – 16GB, 32GB, or 64GB eMMC flash, MicroSD card socket Video Output HDMI [...] The post Allwinner H618 processor powers Android 12 TV boxes appeared first on CNX Software - Embedded Systems News. View the full article