Jus one more piece of news. After rebooting the device (I believe I had to reboot it twice), bluetooth started and I was able to pair it with a loudspeaker, working beautifully. On top of that, I was then able to set VLC to use OpenGL for embedded systems (which did not work before) and, with this configuration, some videos even played with 0 lost frames.
I also connected a 4G modem that supported the rndis driver through the USB and it was recognised without problem. I then installed SQM and cake-autorate to keep the latency in control and so far so good. It seems to be working quite stable. This little device seems to be quite promising, with several nice features at an unbeatable price...
Jus one more piece of news. After rebooting the device (I believe I had to reboot it twice), bluetooth started and I was able to pair it with a loudspeaker, working beautifully. On top of that, I was then able to set VLC to use OpenGL for embedded systems (which did not work before) and, with this configuration, some videos even played with 0 lost frames.
I also connected a 4G modem that supported the rndis driver through the USB and it was recognised without problem. I then installed SQM and cake-autorate to keep the latency in control and so far so good. It seems to be working quite stable. This little device seems to be quite promising, with several nice features at an unbeatable price...
First of all, I would like to congratulate and thank you all for the effort put in this initiative. Besides @Gunjan Gupta , special thanks to @pixdrift for making available a test image that we can play with, thus hiding the complexity of compiling the image ourselves.
Having said that, and with the intention of giving some testing feedback as you requested, here are some comments. I own a 4GB orange pi Zero 3 with extension board. I started playing with the first image a bit until you uploaded the second image, with which I played a little bit more.
With any of both images I did not seem to have good hdmi output initially. By "good" I mean that my monitor detected "something" but I suspect it was not able to synchronize properly. Unplugging the cable and plugging it again seemed to force some recognition and I was able to see the login prompt, but with a lot of flicker and unstability. I remember having similar problems when I played with the miniarch image. With your second image I believe it was worst and I was not able to see anything. So I logged in using the serial connection (see attachment for the boot log over serial). I followed the initial configuration steps and then here the two images seemed to behave differently. While I think the first image started the desktop environment after that, I had to run armbian-config with the second image to activate it. In the first image, once the desktop environment started, I got a good signal through HDMI, albeit in 600x800. I was able to change the resolution but after rebooting I lost the signal again. Getting into armbian-config, deactivating the desktop and activating it again seemed to fix the issue, probably because it activated also the autologin functionality. No browser seemed to be installed, so I installed chromium and I checked the playability of some videos in youtube and they were quite unplayable (not that I expected much, anyway).
With the second image, as I said, I had to go to armbian-config to activate the desktop. I selected xfce and it took a while to download and install the packages. After rebooting, nothing was displayed on the monitor. Again I tried the trick of disabling and enabling the desktop to activate the autologin and I was able to have a nice desktop on my monitor, although I had to wait maybe more than one minute until something was shown, and by default I had more than 10 display configuration windows already opened that I had to close (I know, really weird).
The usb ports on the expansion board worked nicely and the wifi was also working fine. I was not able to activate bluetooth, though. Maybe I was missing something there.
Anyway, I saw that firefox was installed and tried to run it, but it stayed on the task bar without being able to get maximized or anything. So I installed chromium and it behaved much better. It was much snappier than with the previous image. So I checked youtube and to my surprise the videos seemed to be quite playable. I installed then vlc, had to configure it in preferences-video to use xvideo output (xbc) and tested some 1080p sample videos at https://oliverx.link/samples/ . Two samples showed very few lost frames, while using a reasonable amount of CPU, which make me believe they were HW decoded: V206 AVI – MPEG-4 24fps – MP3 and V207 TS – AVC 24fps – AAC
So far so good. And I'd say this looks very promising.
After some experimentation with different options out there, I decided to create my own simple solution. I called it yafspiano (Yet Another FluidSynth Piano) and it is available in my github: https://github.com/fizban99/yafspiano
I must say I was surprised at the low latency you can get. I set jack to 2 periods of 64 frames (that's a theoretical latency of 2.6ms) and I don't seem to get xruns.
I included detailed instructions for installing it in Armbian, including how to install Armbian on the QPlus.