BoringName

I don't like my chances of any resolution to this problem but here goes. I'll start off by saying thanks for providing this repository, I recently went on holidays and was able to use my little magcubic box to watch content off my nas remotely. It was mostly great. One issue I have come across is most of my SD content (ripped from DVD) just displays a black screen. I encode it to 10 bit x265 the same as I do for blurays. Blurays at 1080p play fine, the DVD rips at 480p and 576p just display a black screen, audio works. When comparing them with MediaInfo the only real difference (aside from resolution) is the color primaries, transfer characteristics and matrix coefficient tags. Blurays are bt.709 and the DVD rips are bt.601. Also NTSC vs PAL for the blurays. I've also come across some files that I believe I downloaded at some point that are DVD resolutions, 10 bit x265 PAL that play ok. In MediaInfo these files are missing the all the tags mentioned above. I don't know how this is possible... To troubleshoot I've tried converting a non working file to 25 FPS (PAL) and setting the elements above to bt.709 but no dice. I've run mpv from the terminal in verbose mode and tried to compare a working file to non working file and nothing is really standing out. I think ffmpeg is just serving up black frames with v4l2 in certain circumstances, maybe when the color primaries are bt.601. I'm not overly confident the method I used above to set the bt.709 values would actually work. I installed mplayer and this plays the files ok but doesn't have hardware acceleration. This is why I think the issue is ffmpeg and v4l2. Probably not relevant but 2160p content plays (bt.2020). It really struggles with it but it displays an image. Any ideas would be great. At this stage I'm probably going to take a 10 second clip of a non working file and just run it through bunch of different encode settings until I get something that displays and work backwards from there.

I've been trying to get the LCD working on my box. I've used Nicks image - Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_xfce_desktop I've followed instructions for OpenVFD and tm16xx on these forums but both result in an Exec Format Error when I try to install the compiled module. From what I have read this is a version mismatch between the kernal and what the module was built with but when I compare uname -r with the vermagic of the module they match. I initially installed the linux headers from Nick's Github: linux-headers-edge-sunxi64_25.05.0-trunk_arm64_6.12.11. After I got the format error I tried installing headers from Armbian-config but get the same result. Make wouldn't work at all initially until I did a symlink between the relevant folders in usr/src and lib/modules. Maybe that stuffed something up?

Bookworm. But my point was the version 35.1 is what got installed when I ran the scripts in the first post. If the script installed 37 for you because you're on Ubuntu then I probably am on the wrong track. Yes I believe it does this. I was just pointing out that drm_prime works for me but I guess that could just be due to different hardware on the device. I'm not using an Orange Pi.

I was surprised when mine played H265 10 bit. I thought I'd read somewhere v4l2 was limited to 8 bit. Obviously that was incorrect.

I'm very new to Armbian so I could be off track here but I noticed your running MPV version 37. When I ran the instructions for the first time I already had mpv installed (version 40 or something) so it didn't get updated. I ended up uninstalling MPV and running the instructions again. Now I have version 35.1 which fixed the drm_prime errors for me. The version difference could be because you are on 26.2 of Armbian and I'm on 25.05, I haven't got my head around all the different versions of things yet. Maybe try uninstalling MPV and trying the commands again and see what version it gives you.

I don't know if this is known already and if its off topic for this thread. I did a search for moonlight in the allwinner section and nothing came up so I'm sticking it here I got moonlight running on H618 (actually it might be a H616....) box with no issues at all. Streamed a game from my main PC (with sunshine) at 1080p and it ran great. Makes for a cheap Steamlink alternative. I just followed the instructions here, It does mention v4l2 so maybe the v4l2request patch is required for it to work. There is an Embedded version that might work if you don't have v4l2 support.

I got emby installed and working. Made it launch with the ir remote, it was all perfect until I tried to play a video I've set it to use mpv but it seems the emby package has it's own version of mpv and ffmpeg baked in as the versions reported in the mpv.log are different and it fails to use drm, it seems the following errors are the problem. [ 0.028][v][libmpv_render/drmprime] drmprime hwdec requires at least one dmabuf interop backend. [ 0.028][v][libmpv_render] Loading failed. [ 1.422][v][ffmpeg] Unable to open any dma_heap device [ 1.422][e][ffmpeg/video] hevc: Failed to set destination format: S265 1920x1080 [ 1.422][e][ffmpeg/video] hevc: Failed setup for format drm_prime: hwaccel initialisation returned error. When I launch the same file directly in mpv, it plays fine and doesn't have the errors above. The system has mpv version 0.35.1 but emby reports using 0.38.0-dirty. Same with ffmpeg and all the associated lib files, they are all higher versions and I can't find duplicates in the system so I believe they are packaged as part of the emby app so I really doubt it's something I will be able to fix unfortunately. Tried Kodi and that's missing all the acceleration settings. Jellyfin client doesn't work with an emby server anymore. Just to attempt to keep this on topic, I don't suppose there is anything I can config with the image that might resolve the dma_heap errors? edit: I figured out a solution, emby lets you configure an external player. I just set that to /usr/bin/mpv and it works.

It's this image from @Nick A github. Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_xfce_desktop.img I had to copy over a few firmware files to get wifi/bluetooth working but otherwise it's unchanged.

I initially tried the instructions in the original post and it didn't work for me. On an allwinner h618 box with a mali-G31. I then spent pretty much all day today trying to find a fix. I came across a post on here stating the version of mpv that works with v4l2 needs to be compiled with the same package versions as ffmpeg or something along those lines. When I first tried the instructions I already had mpv installed and I remember it stating that it didn't update it. So for a hail mary I ran apt remove ffmpeg and apt remove mpv. Then I ran the instructions again and noticed first one didn't actually run successfully which could have been why they didn't work this morning.... When I copy pasted into the terminal it left the $ signs in there and caused errors. So I manually typed it out and got everything to run successfully. Now everything works. mpv is buttery smooth. Previously mpv stated drm was unsupported now it says "using hardware decoding (drm)". I had checked ffmpeg and it did list v4l2 as supported so maybe that didn't need to be reinstalled. Anyway, if it hasn't worked for you maybe try uninstalling ffmpeg and mpv and running the commands again.

And now I've hit a road block. I can't get video acceleration to work. VLC just displays a blank screen no matter what output I select and MPV playback is very stuttered. I wanted this box to act as an Emby client, got it all configured to load emby via the ir remote and got all the functionality working but when I play a video it's so choppy it's basically unwatchable. 576p is almost bearable, 1080p is not. I've spent all day on it and got nowhere. I've followed the instruction in this post but it made no difference - Repository for v4l2request hardware video decoding (rockchip, allwinner) edit: Ok the instructions in that post did actually work, I just didn't notice one of the commands had not run properly when I first tried it. Video playback in mpv is buttery smooth, now I just need to figure out how to get emby to do the same.

Installed to the EMMC with armbian-install and no issues it all. Took about 10 minutes and now boots from the EMMC with no SD card inserted. I think I paid $35AU for this thing and it came with the remote, a bluetooth keyboard, HDMI cable and power supply. Absolute bargain when you compare it to the current price of Rasperry PI's especially when it comes with it's own case and internal storage. Thanks to everyone who contributed to getting these images out there, it's fantastic. I've also got the IR remote working. I followed rafman's post but this didn't fully work for me. It allowed the remote to work and I could see it was working with ir-keytable -t but the desktop and any open apps wouldn't respond to it. The solution was to copy the toml file to /etc/rc_keymaps/magcubic.toml then edit /etc/rc_maps.cfg and add the following to the bottom of the file * rc-empty <whatever_name>.toml * rc-empty magcubic.toml Adding the line to the rc.local file was not required. I've attached a picture of the remote and the toml file I created. I didn't map the buttons in the top right section as this remote has a learning function and you're supposed to learn the codes from your TV remote. But here are the codes my remote was using for these buttons by default. Power 0x1f1 Set 0x1f2 TVIN 0x1f3 VOL- 0x1f4 VOL+ 0x1f5 Edit: If you are going to use on media player apps you will probably want to edit the toml file and change "KEY_OK" to "KEY_SPACE". OK doesn't let you select things with the OK button but SPACE does. magcubic.toml

Bluetooth now working, no compiling required via hciattach. I don't know how much of this is necessary because I generally don't know what I'm doing. But here goes. Apparently hciattach is a legacy app that requires the firmware to be in /etc/firmware so I made a folder and setup a symlink before running the hciattach. <NOT REQUIRED> sudo mkdir -p /etc/firmware <NOT REQUIRED> sudo ln -sf /lib/firmware/aic8800_sdio/*.* /etc/firmware sudo hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep <NOT REQUIRED> sudo hciconfig hci0 up Bluetooth should be available now. You can test it with sudo hcitool -i hci0 scan This will display any devices in the area the bluetooth adapter has detected. I had installed armbian-firmware package so that might also be required but I doubt it. I will flash a new image and start from scratch just to make sure everything I've stated works on a fresh install and then update the thread. Edit: I tested it on a fresh image and the only command required for bluetooth to activate was the hciattach line. I couldn't figure out how to do strikethrough in the code block so I just listed added the "NOT REQUIRED" info. I didn't want to remove them in case it helps someone else. The firmware files I mentioned in a previous post need to copied over and the device powered down before running the hciattach command. The hciattach commands do not persist through a reboot so I need to figure out how to get this to run on startup, hopefully the easy part. Thanks for all the help. Hard to beat that feeling when you spend hours troubleshooting something and it fires up for the first time!

We have progress, sorry I feel like I'm spamming this thread a bit but at least I have a result. Wifi is now working. Still no bluetooth. For anyone playing at home with this box, to get to this point I installed x98h image from Nick's github. I then downloaded the following files from walnutpi's github fw_patch_table_u03.bin fw_adid_u03.bin fw_patch_u03.bin fmacfw.bin aic_userconfig.txt I copied these files to the device and placed them in /lib/firmware/aic8800_sdio/ Then shutdown the unit and powered it back up. Doing a restart isn't enough, you need to shut it down. So just bluetooth to go. The only related message seems to be sdio_err: <aicwf_sdio_bus_pwrctl,1380>: bus down Which I expect will probably require me to update the dtb settings as previously discussed. Happy to settle with just the wifi working but I'll take a shot at getting bluetooth going because I may as well finish what I started. Thanks for the help thus far. edit: I've tried decompiling the /boot/dtb/allwinner/sun50i-h618-x98h.dtb file but I can't find any of the relevant info to change in the dts file. It's like the sections listed in the patch file linked earlier are not there at all. I understand it's in a different format but as an example. The following section line 278 to 297 +&uart1 { + pinctrl-names = "default"; + pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>; + uart-has-rtscts; + status = "okay"; + + bluetooth { + compatible = "allwinner,sunxi-btlpm"; + // max-speed = <1500000>; + + clocks = <&rtc 1>; + clock-names = "lpo"; + vbat-supply = <&reg_dldo1>; + vddio-supply = <&reg_dldo1>; + enable-gpios = <&pio 6 19 GPIO_ACTIVE_HIGH>; /* PH19 bt_power */ + reset-gpios = <&pio 6 13 GPIO_ACTIVE_LOW>; /* PH13 bt_rst_n */ + device-wakeup-gpios = <&pio 6 17 GPIO_ACTIVE_HIGH>; /* PH17 bt_wake */ + host-wakeup-gpios = <&pio 6 16 GPIO_ACTIVE_HIGH>; /* PH16 bt_hostwake */ + }; +}; I've tried searching the dts file for "uart1", "bluetooth", "bt", "btlpm", "lpo", the hex equivalent of the values above, all the different value names etc... of the small amount of results that do show up, most of them are not even remotely close to matching anything above. "usart1" does have a section detailing the pins and rtscts but it seems that bluetooth section just isn't there. This is just one example, lines 87 to 102 don't appear to be there either. There is some values for vcc-3v3 but that's it. I'll probably have to look at updating the values in the patch file and building an image.

Excellent, thanks. One more thing. I just reloaded the x98h image. When I previously loaded this image, I didn't check dmesg like I did with the other images. They had no mention of Wifi at all but this one does. It seems to start enabling wifi but then fails here rwnx_load_firmware :firmware path = /lib/firmware/aic8800_sdio/fw_patch_table_u03.bin rwnx_load_firmware: fw_patch_table_u03.bin file failed to open wrong size of firmware file aicbt_patch_table_alloc fail edit: So lib/firmware/aic8800_sdio/fw_patch_table_u03.bin does not exist which probably explains that error. I'll see if I can get my hands on that file and see if that fixes things before I worry about compiling/decompiling stuff.

Ok, just so I'm following you correctly. This line in my DTS dump bt_rst_n = <0x23 0x06 0x13 0x01>; In decimal is <35 6 19 1> In the patch you linked the line above should be matched to these values at line 293? reset-gpios = <&pio 6 13 GPIO_ACTIVE_LOW>; /* PH13 bt_rst_n */ So I should change this to reset-gpios = <&pio 6 19 GPIO_ACTIVE_HIGH>; /* PH13 bt_rst_n */ Repeat for all the other values to match the DTS dump then build the image? Is there a way to set these values at the command line without having to build an image? edit: Actually my high low flag is 0x13 which is 0001 0011. This is read from right to left isn't it? So Bit 0 is actually a 1 which means in the example above I should set it to the following? reset-gpios = <&pio 6 19 GPIO_ACTIVE_LOW>; /* PH13 bt_rst_n */ Sorry I'm probably getting in a little over my head....

Well that was fun. Termux wouldn't load so I found an older version from 2022 thinking that version is older than the box so has a higher chance of working. That also wouldn't open until I went a bit silly and attempted to open it multiple times. Just like Mustafa in Austin Powers, once I attempted to load it 3 times in a row it would show up. Bizarre but I now have a dump of Device.DTB How do I view it properly? I opened it in notepad++ and most of it is gibberish but I can make out a few details that are a bit surprising. Namely - allwinner,h616 arm,sun50iw9p1 The label on this thing says H618 but it appears to be a H616. Where do I go to from here? Edit: I have attached the dtb file and two dumps of the file. One using fdtdump and the other using dtc. It seems the btlpm section has the same values of a device Nick referenced on page 4 of this thread. I don't know if that means anything.... Edit2: I tried "Armbian-unofficial_25.05.0-trunk_Transpeed-8k618-t_bookworm_edge_6.12.11_xfce_desktop.img" this boots ok, ethernet works but again, no wifi/bluetooth. I'm a little surprised every image I've tried so far has mostly worked. I guess these vendors just throw together whatever parts they can get cheap but the core of the units is the same. Thanks. dtsdump.txt fdtdump.txt device.dtb

I didn't mention earlier but after I ran the update/upgrade commands I also manually updated the locale file. During the original setup I accidentally selected the wrong locale, I went into armbian config, deselected the wrong one and selected the correct one but the incorrect locale was still being referenced constantly. So I manually removed it from etc/default/locale. I thought this may have been a reason for it no longer booting and not the update/upgrade commands. I'm just explaining that so you understand why I also tried update/upgrade with the x98h image. Turns out it wasn't me messing with the locale that stopped it booting as this image also will not boot now after apt-get update, apt-get upgrade. This image originally booted ok and it seems the ethernet works better. Downloading from the commands listed above took about 20 seconds vs 30 minutes on the vontar image. But wifi/bluetooth still will not work. One other difference is when I select the bluetooth manager app it actually loaded whereas the vontar image would state something about a service not running. The app loaded but had no devices listed. I'll see how I go with termux. The play store doesn't work on it but I was able to sideload a couple of apps.

I tried apt-get update and apt-get upgrade thinking it might grab what it needs but that was a bad idea as it will not boot at all now. So I may as well start from scratch and try the x98h image. The wifi chip is the same but item 3 on mine is samsung and item 7 is an FD650 which is referenced on that page as a possible alternative. It might be worth noting the units digital clock display was blank using the vontar image, I expect that was due to the chip mismatch. I'll see how the x98h image goes, if that fails I'll look into termux. No wifi isn't the end of the world as I can find a use for it just using ethernet but wifi (and bluetooth) would be nice. Thanks.

This is a great thread. I've had a magcubic android 12 box I've been using for a while just to watch things off a USB when we stay at hotels. It looks like the one in this video but the chip ID's are different. Mine seems to be running with Samsung memory, the clock chip? is FD650 instead of FD6551 and the wifi chip is labelled as HK5236F. Most hotel TV's don't support modern video codecs so this has worked ok. But I want to look at accessing my NAS remotely and this box is a bit of a dud if you want to install your own apps. Play store doesn't work, aurora store doesn't work. Tried sideloading Tailscale and it just crashes. While doing some research I noticed it also seems to be sold under the Vontar brand so I flashed @Nick A "Armbian-unofficial_25.05.0-trunk_Vontar-h618_bookworm_edge_6.12.11_xfce_desktop.img" to an SD card and it booted up. Happy days. It appears to have ethernet but I have not plugged it in yet. No wifi though. I just have 2 questions. 1. Is there any way this can be made to boot from internal storage or do I need to keep the SD card in if I want to run Armbian on it? 2. Is there a driver available for this wifi chip and do I need to mess around updating the boot image or can I just run a command for it? I'm not a regular linux user but I've got a bit of experience messing around. I don't currently have an environment setup to build my own image but I've played around with WSL before so I could probably set something up. Thanks for everyone that has contributed to this. It's good to make use of these boxes considering how cheap they are.