manuti

https://www.reichelt.de/Bluetooth/LOGILINK-BT0015A/3/index.html?ACTION=3&GROUPID=5844&ARTICLE=170030&OFFSET=16&SID=96WDwXhKwQATMAAHrYxKs8aa7eb3331164bb14def41b33191fbf3&LANGUAGE=EN
 
I used this one this a RPI. I just have ported my a2dp server on bluez5/pulseaudio/nanopi air (internal BT chip)
 
- compatibility depends on bluez (and btusb kernel module) and not on board or distro, if customers report it works with "linux" or "ubuntu", then you will be able to have it working.
- better use a class I dongle if you want a good range - but you will anyway hardly reach more than a few meters because a2dp device are generally class II
- even better use a nanopi air : with eMMC and internal BT chip, you get the same price than an $8 board with crappy SD card and crappy dongle. Without antenna (not provided) this board is unusable, but with an IPX cheap antenna you get as good a range than with class I dongle for that usage.
- be aware that with bluez5, you need pulseaudio, you can only use one BT sink at a time and you need workarounds to handle bugs in (pulse, bluez, dbus), workarounds that may depend on device specific profile connection management.

- via serial console
- by mounting SD card on some linux and setting fixed IP in /etc/network/interfaces as this example:
auto eth0 iface eth0 inet static address 192.0.2.7 netmask 255.255.255.0 gateway 192.0.2.254

Check the right thread: https://forum.armbian.com/index.php/topic/2808-orange-pi-zero-went-to-the-market/
 
We use the same booting settings as with the small NanoPi NEO (which means these three boards take quite a bit time to boot but don't exceed 2W) and I managed using Armbian's h3consumption tool to get idle consumption as low as 0.5W. When H3 devices are busy consumption increases but also not that much -- see here for example: https://forum.armbian.com/index.php/topic/1748-sbc-consumptionperformance-comparisons/?p=13626
 
The problem with 'phone chargers' is that some do not provide more than 500 mA if the device in question doesn't speak one of the USB power delivery dialects (which no SBC does). And more importantly that many phone chargers simply suck. It might work but rule of thumb is 'a charger is not a PSU'. It should be noted that over 95 percent of 'Armbian problems' are related to either SD card or power supply issues

I tested Orange Pi PC on Orange Pi One, I don't know if this is useful:
uname -a shows:
orangepipc 4.9.0-sun8i #56 SMP Wed Nov 23 01:04:34 CET 2016 armv7l armv7l armv7l GNU/Linux armbianmonitor - u uploaded data to : http://sprunge.us/UPAE
 
I don't know if you also want such format for feedback, but here it is:
 
Card                        Boot         Network         HDMI         Install         Date                  Performed by
-----------------------------------------------------------------------------------------------------------------------------
Orange Pi One        yes             yes               no               yes            25.11.2016        manuti
 
I update the image and install docker from the default repositories, in the webpage from armbianmonitor I can't see the temperature and of course the HDMI is not working.
 

Orange boys are very busy nowadays new add-on board for 2$ for the Orange Pi Zero https://es.aliexpress.com/item/New-Orange-Pi-Zreo-Expansion-board-Interface-board-Development-board-beyond-Raspberry-Pi/32770665186.html?detailNewVersion=&categoryId=200004017
 
 

Sweet! I hope the pins on the TRRS jack are still the same (and the AV cable they sell is still wrong in the same way as before )
 
The next such HAT should add 2 JMS568 USB-to-SATA bridges and provide one normal SATA jack and one mSATA: The Zero NAS

Orange boys are very busy nowadays new add-on board for 2$ for the Orange Pi Zero https://es.aliexpress.com/item/New-Orange-Pi-Zreo-Expansion-board-Interface-board-Development-board-beyond-Raspberry-Pi/32770665186.html?detailNewVersion=&categoryId=200004017
 
 

Orange Pi PC. Worked without issue.

One minor remark: Based on some testing it seems like a great idea to use "-o compress=zlib" when transferring the files to the freshly created btrfs filesystem. Saves a lot of space and should even slightly improve filesystem performance on dual core or better equipped boards. Some details: https://github.com/igorpecovnik/lib/commit/b14da27a4181e8e232bd8f526e71d2a931a8252f

Hello all! My 1rst post.
I don't know how to post images (do I need approval, being a new user?).
 
https://drive.google.com/file/d/0B0b0OgoP5TmiMF9CR1VkUG8xb1E/view?usp=sharing

 
Edit by admin: image attached to the post

Armbian PCB

For video decoding acceleration you need to install only libvdpau-sunxi1, other packages will be resolved as dependencies.
You don't need to rebuild mpv on Jessie if I remember correctly, unless you want to use OSD and subtitles.
 
xserver-xorg-video-fbturbo is not related to video acceleration, but installing it (together with libmali-sunxi-r3p0 or without it) should enable additional Xorg related acceleration

The front page of armbian.com shows me a default nginx on Debian

IMO we should switch back to 'by date' as default. With current sorting new users accessing this page get the impression that this here is all about boring Bananas while the average potential new Armbian user searches for 'hot stuff' (like OPi Zero in this case).

Some success regarding Wi-Fi:
 
 
 
So currently it's necessary to blacklist dhd module (if not things get weird when trying to load xradio_wlan) and firmware files need a proper location. Since I'm not that much interested in Wi-Fi I'll stop here

Both options are now present, default is "by name" ... the text and buttons regarding switching are very minimal, don't have better idea.

We actually added a test Vanilla build which was soon removed. Reason: people failed to read that it's a preview image, where many thing does not work and that we don't provide any end user support. Further people failed to read, that I don't provide support via email or other private channels. To lower related frustration, we simply removed those images from the download and now they are accessible elsewhere, where is little harder to find. Technically those boards have (limited at this stage) mainline support.

I expect we'll put those images back soon, so I don't change this flag. Perhaps I should ? 

WiFi is planned, BT also.
 
Opi zero (and PC2) just arrived on my desk today and I got Armbian running on it in no time   We need to add wireless drivers and apply fine tuning ... PC2 will be tested later.
 

​Zero is out: https://www.aliexpress.com/store/product/New-Orange-Pi-Zero-H2-Quad-Core-Open-source-development-board-beyond-Raspberry-Pi/1553371_32760774493.html

FWIW - in case others have a similar issue, the problem was quite simple - the system 'disk' was full.  Even though there was enough space to do other tasks, and start the UI manually, it apparently didn't have enough to start at boot.  After space was cleared, it resumed working as expected.

As @Igor says in http://forum.armbian.com/index.php/topic/872-beelink-x2-with-armbian-possible/?p=16335
 
... only support booting from SD card and then flashing to eMMC with our nand-sata-install tool.

service nodm disable

edit :   /etc/network/interfaces
 
# start ###   # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).   # The loopback network interface auto lo iface lo inet loopback   # The primary network interface # allow-hotplug eth0 # iface eth0 inet dhcp   # Static IP address auto eth0      # ou auto enp0s7 (see  ifconfig) iface eth0 inet static         address 192.168.25.3         netmask 255.255.255.0         gateway 192.168.25.1   # end ###   and change :   /etc/resolv.conf   domain domain.name search domain.name nameserver 8.8.8.8 nameserver 8.8.4.4   # for your preference      

SOLVED  !!!   after dist-upgrade and before of reboot :   sudo apt-get install -f   be happy   thanks to   Igor and tkaiser

We (most work was done by Zador) just spent months to rework desktop that now have more features and its properly packed that can be installed on the top of CLI and upgrade, hopefully, works fine. We are releasing it within one week.
 
Armbian tends to focus on base problems, server / iot functionality, since most of those boards have problems in the ground level and it's irrelevant if we add on it's rotten base an "smooth, high quality desktop". This is what some board manufacturers might do to impress their potential buyers.
 
We are happy with current level of smoothness and quality of the desktop but project is open and we will support any initiative from outside.