Groove On

I am unable to duplicate this problem in Armbian Buster / Odroid N2+. I've been running it today for around 2-3 hours with multiple reboots and it's working fine. XFCE installed via armbian-config. Linux odroidn2 5.10.34-meson64 #21.05.1 SMP PREEMPT Thu May 6 21:24:14 UTC 2021 aarch64 GNU/Linux But it's still happening on Armbian Focal / Odroid N2+ - screen goes off/into powersave mode? 2-5 minutes after booting up. After getting the screen back (on/off) it's fine and stays up.

If you're getting poor/bad audio performance from an audio VST on the N2+, it can sometimes be the context switching between the BIG.little ARM cores. In my case, Pianoteq was giving me a lot of x-runs and wide fluctuations in performance when it switched between the 2x low-performance and 4x high-performance cores. One way to get more stable performance is to assign the application to the 4x high-performance cores like this. taskset -c 2,3,4,5 'Pianoteq 7' On the N2+ the 2x low-performance are numbered 0 and 1. The 4x high-performance cores are 2,3,4,5. 'Pianoteq 7 STAGE' is the name of the application being assigned. This is more useful if you're using Hard Kernel's version of Ubuntu. Armbian handles context switching much more smoothly so depending on how hard you're driving the VST application, you might not need to do this on Armbian.

If anyone needs to get the 3.5mm audio jack working on the N2+, here's one method. 1. Edit or create /etc/asound.conf with these lines. Copied directly from the Hard Kernel Ubuntu setup. pcm.!default{ type hw card 0 device 1 } ctl.!default{ type hw card 0 } 2. Run this script to turn on the 3.5mm audio in alsamixer. The settings are listed in the same order as in alsamixer. #!/bin/bash # 3.5MM JACK, set to max gain amixer sset 'ACODEC' '255' # 3.5MM JACK - set in/out channels (src/sink) amixer sset 'FRDDR_B SINK 1 SEL' 'OUT 2' || true amixer sset 'FRDDR_B SRC 1 EN' 'on' || true # 3.5MM JACK amixer sset 'TOACODEC SRC' 'I2S C' || true amixer sset 'TOACODEC OUT EN' 'on' || true amixer sset 'TOACODEC Lane Select' '0' || true # SAVE NEW SETTINGS alsactl store

I have this same issue on the Odroid N2+, I was hoping the recent updates would solve it, but it's still happening (using Focal 21.05.1 / 5.10.34). I will be switching to Buster to see if I have better luck there. The monitor suddenly goes into powersave/suspend mode, like Arne pointed out it seems to happen shortly after switching on (within 2-5 minutes). It occurs on both my 27" Benq monitor and 5VU touchscreen both running over HDMI. The fix is simple enough, I can either turn the Benq monitor on/off to get back the connection or the 5VU will re-activate if I touch the screen. After reacquiring/reconnecting both monitors stay on just fine after that. I've had them both running for 24-hours straight without the monitors turning off. So it seems to be something that happens once after boot. For what it's worth, I've noticed it happens more often when I'm quickly switching to and dragging a window (for example moving Terminal to get to Firefox). Also if I double-click on the HDMI script that's in /usr/local/bin it can sometimes turn the monitor off (yes I know I'm not supposed to double-click the script, but old habits die hard). Otherwise, I wanna say, you guys have done a great job with Armbian on the N2+, aside from that issue, it's running really smooth for me. Armbian runs my audio software better than all the other ARM distros I've tried!