haajee

Thanks for your info Igor. Because i didn´t have the problem i didn´t know there was a bug. If i read so looks like the problem is with non-headless setups? But a fix is on the way with the next kernel.

Hi, I have the same configuration like you: OrangePi OnePlus, I run on my one: Domoticz, Mosquitto, Apache, traccar, PiHole, MariaDB and it runs all fast and stable! I use it with this power supply from Aliexpress. I thought that when i used it with the USB-DC 5V cable with a lot of adapters i also has strange freezes. I recommend a real 5v power supply. :) Beside the powersupply did i also has a lot of problems with a few SanDisk SD cards. Now i run a few Samsung SD card cards and no corrupted SD cards. I need to say that Igor als has broken Samsung cards but i think he use it a little bit (a lot!!) more than i do. :) So maybe try a real 5v power supply or a another SD card? :)

Maybe a stupid comment and i have the OnePlus with H6 without USB3 ports. But it looks like after i install lshw also lsusb -v gives a lote more information. Maybe it could help in troubleshooting? And if it didn´t help sorry for my interrupt.

Hello everyone, I want to do something simple with my OrangePi One Plus. That is to connect a bluetooth speaker and play wireless from the Pi with a CSR8510 A10 USB dongel. The dongel works and i can pair with every device. Even with my JBL Go 2 bluetooth speaker: hj@PLUS-OrangePiOne:~ $ sudo bluetoothctl [NEW] Controller YY:YY:YY:YY PLUS-OrangePiOne [default] Agent registered [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Discovery started [CHG] Controller YY:YY:YY:YY Discovering: yes [NEW] Device XX:XX:XX:XX JBL GO 2 [bluetooth]# scan off Discovery stopped [CHG] Controller YY:YY:YY:YY Discovering: no [CHG] Device XX:XX:XX:XX TxPower is nil [CHG] Device XX:XX:XX:XX RSSI is nil [bluetooth]# trust XX:XX:XX:XX [CHG] Device XX:XX:XX:XX Trusted: yes Changing XX:XX:XX:XX trust succeeded [bluetooth]# pair XX:XX:XX:XX Attempting to pair with XX:XX:XX:XX [CHG] Device XX:XX:XX:XX Connected: yes [CHG] Device XX:XX:XX:XX UUIDs: 00001108-0000-1000-8000-00805f9b34fb [CHG] Device XX:XX:XX:XX UUIDs: 0000110b-0000-1000-8000-00805f9b34fb [CHG] Device XX:XX:XX:XX UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Device XX:XX:XX:XX UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Device XX:XX:XX:XX UUIDs: 0000111e-0000-1000-8000-00805f9b34fb [CHG] Device XX:XX:XX:XX ServicesResolved: yes [CHG] Device XX:XX:XX:XX Paired: yes Pairing successful [CHG] Device XX:XX:XX:XX ServicesResolved: no [CHG] Device XX:XX:XX:XX Connected: no [bluetooth]# connect XX:XX:XX:XX Attempting to connect to XX:XX:XX:XX Failed to connect: org.bluez.Error.Failed But, as you can see above, i can´t connect to the JBL Go2. If i open the bluetooth service i read: hj@PLUS-OrangePiOne:~ $ sudo service bluetooth status * bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2019-11-10 14:53:35 CET; 1h 9min ago Docs: man:bluetoothd(8) Main PID: 732 (bluetoothd) Status: "Running" Tasks: 1 (limit: 1021) CGroup: /system.slice/bluetooth.service `-732 /usr/lib/bluetooth/bluetoothd Nov 10 15:42:13 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:43:20 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:43:36 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:43:44 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:43:53 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:44:03 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:44:09 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:44:11 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:44:18 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:59:28 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Off course did i look on Google and i read something with pulseaudio but that should be installed also the ´pulse-module-bluetooth´ module. i have no idea to fix this. Btw: connecting to non-audio bluetooth devices works. Connecting to the JBL Go2 from Armbian-config does also not work... Does someone of you a sugestion to make a2dp working?

Oh i think you use the SD cards indeed al little bit (mean a lot!!) more intensive then i should do. Otherwise is in the dashcam's my idea also that the Samsung's has a longer lifetime than the Sandisk. But i agree with you: the only correct way to check it is to buy a lot and do all the same things and see how long the SD cards live. Offcourse with originals. But even then could there be a bad batch of a brand... 'SD cards are consumable items' do i read somewhere on the internet. And i think we should agree. Btw: is the lifetime of a onboard eMMC better than a SD card?

Hi all, When i trie to install ISPconfig with softy all goes very well. And when the installation is finished i should be login on https://orangepi-PC:8080/login/index.php . But every what i trie (i read it should be admin/admin at the first start) nothing worked to login. Does anyone know what is the default password or what is the problem van not loging in? Kind regards!

I used for a longer time not Samsung ProEndurance SD cards and the quality looks a lot higher. Not even 1 Samsung card is broken instead of a few Sandisk cards... I read on another Raspi forum that Samsung cards functions the best. So it looks it does! Maybe a tip when you doubt to choose a SD brand.

Yes i know that it´s just a problem with the other H6 boards.

The OrangePi One Plus just run´s just perfect for a long time! In my opinion it´s stable? Oh on the official download page on https://www.armbian.com/orange-pi-one-plus/´ i read: ´USB3 sometimes doesn’t detect high-speed devices properly´. But thatś with the One Plus not a (big) deal because the One Plus doesn´t have USB3 ports?

I just want to say that my OrangePI One Plus runs perfectly with the release candidate! :) Good job all! I have also give a little donate. Hope that could help you all in the future! Thank you.

Welcome to ARMBIAN 5.87.190519 nightly Ubuntu 18.04.2 LTS 5.1.3-sunxi64 analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 244 us. hardware limits: 480 MHz - 1.49 GHz available frequency steps: 480 MHz, 720 MHz, 816 MHz, 888 MHz, 1.08 GHz, 1.32 GHz, 1.49 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 1.49 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 888 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:87.91%, 720 MHz:1.92%, 816 MHz:1.00%, 888 MHz:2.43%, 1.08 GHz:1.51%, 1.32 GHz:0.78%, 1.49 GHz:4.45% (26822)

yes sinds the last 2 nightly releases that was also my question a few posts above

I am running 5.1 to. The room temperature is arround 23 degrees celcius. I have the Orange Pi One Plus H6 in a plastic case. Simple copper heatsink. Test with and without fan. Round 1 with fan Time CPU load %cpu %sys %usr %nice %io %irq CPU 18:09:44: 720MHz 0.72 3% 1% 0% 0% 1% 0% 26.9°C 18:09:49: 1080MHz 0.66 1% 0% 0% 0% 0% 0% 26.8°C 18:09:54: 1488MHz 0.69 14% 1% 9% 0% 1% 0% 29.6°C 18:10:01: 1488MHz 0.96 72% 1% 70% 0% 0% 0% 41.0°C 18:10:07: 1488MHz 1.28 89% 2% 86% 0% 0% 0% 38.9°C 18:10:14: 1488MHz 1.50 91% 2% 88% 0% 0% 0% 43.0°C 18:10:19: 1488MHz 2.04 83% 1% 81% 0% 0% 0% 39.4°C 18:10:24: 1488MHz 2.27 89% 2% 86% 0% 0% 0% 40.4°C 18:10:30: 1488MHz 2.49 97% 5% 91% 0% 0% 0% 40.9°C 18:10:35: 1488MHz 2.61 91% 1% 89% 0% 0% 0% 38.5°C 18:10:40: 1488MHz 2.73 71% 3% 67% 0% 0% 0% 40.5°C 18:10:46: 1488MHz 2.75 88% 5% 83% 0% 0% 0% 40.9°C 18:11:11: 720MHz 2.93 97% 28% 26% 0% 42% 0% 31.2°C 18:11:16: 1080MHz 12.37 5% 1% 0% 0% 2% 0% 28.8°C 18:11:21: 888MHz 11.38 2% 0% 0% 0% 0% 0% 28.8°C Round 2 with fan 18:11:26: 888MHz 10.47 4% 1% 2% 0% 0% 0% 28.4°C 18:11:31: 1080MHz 9.63 1% 0% 0% 0% 0% 0% 28.4°C 18:11:36: 888MHz 8.86 1% 0% 0% 0% 0% 0% 28.1°C 18:11:41: 1320MHz 8.15 1% 0% 0% 0% 0% 0% 28.0°C 18:11:46: 1488MHz 7.50 15% 1% 12% 0% 1% 0% 30.6°C 18:11:53: 1488MHz 7.22 83% 1% 80% 0% 0% 0% 42.5°C 18:11:58: 1488MHz 6.95 86% 1% 84% 0% 0% 0% 39.7°C 18:12:05: 1488MHz 6.71 93% 1% 91% 0% 0% 0% 43.7°C 18:12:11: 1488MHz 6.50 81% 1% 79% 0% 0% 0% 40.3°C 18:12:16: 1488MHz 6.13 89% 2% 87% 0% 0% 0% 40.7°C 18:12:21: 1488MHz 6.04 95% 2% 92% 0% 0% 0% 39.3°C 18:12:26: 1488MHz 5.88 89% 1% 88% 0% 0% 0% 36.8°C 18:12:31: 1488MHz 5.57 73% 2% 71% 0% 0% 0% 40.7°C 18:12:36: 1488MHz 5.36 86% 2% 83% 0% 0% 0% 40.6°C 18:13:31: 1320MHz 11.18 98% 47% 11% 0% 39% 0% 33.7°C Round 3 with fan Time CPU load %cpu %sys %usr %nice %io %irq CPU 18:13:36: 720MHz 28.50 3% 0% 1% 0% 1% 0% 29.6°C 18:13:42: 1488MHz 26.30 47% 1% 44% 0% 0% 0% 40.7°C 18:13:47: 1488MHz 24.51 95% 1% 93% 0% 0% 0% 44.4°C 18:13:52: 1488MHz 21.43 82% 2% 78% 0% 0% 0% 42.1°C 18:13:59: 1488MHz 20.04 94% 1% 93% 0% 0% 0% 44.8°C 18:14:04: 1488MHz 18.83 80% 2% 77% 0% 0% 0% 41.5°C 18:14:09: 1488MHz 17.88 90% 2% 87% 0% 0% 0% 41.8°C 18:14:16: 1488MHz 16.85 94% 2% 91% 0% 0% 0% 44.8°C 18:14:22: 1488MHz 15.82 78% 1% 76% 0% 0% 0% 40.6°C 18:14:27: 1488MHz 14.80 85% 2% 81% 0% 0% 0% 41.1°C 18:14:33: 1488MHz 13.06 90% 3% 87% 0% 0% 0% 41.5°C 18:14:40: 888MHz 14.57 91% 20% 37% 0% 32% 0% 31.7°C 18:14:45: 1080MHz 13.41 1% 0% 0% 0% 0% 0% 30.1°C Round 1 without fan Time CPU load %cpu %sys %usr %nice %io %irq CPU 18:18:33: 1488MHz 1.69 86% 3% 82% 0% 0% 0% 47.6°C 18:18:39: 1488MHz 1.95 95% 1% 93% 0% 0% 0% 52.2°C 18:18:44: 1488MHz 2.25 78% 2% 75% 0% 0% 0% 49.2°C 18:18:51: 1488MHz 2.47 93% 4% 87% 0% 0% 0% 50.7°C 18:18:58: 1488MHz 2.76 95% 3% 91% 0% 0% 0% 54.0°C 18:19:04: 1488MHz 2.94 77% 1% 75% 0% 0% 0% 49.9°C 18:19:09: 1488MHz 3.03 88% 6% 81% 0% 0% 0% 52.1°C 18:19:15: 1488MHz 3.18 96% 11% 84% 0% 0% 0% 52.4°C 18:19:23: 1320MHz 4.37 91% 16% 35% 0% 38% 0% 42.4°C Round 2 without fan Time CPU load %cpu %sys %usr %nice %io %irq CPU 18:20:24: 1488MHz 1.60 40% 1% 38% 0% 0% 0% 49.9°C 18:20:30: 1488MHz 2.20 94% 1% 92% 0% 0% 0% 55.8°C 18:20:35: 1488MHz 2.34 84% 2% 81% 0% 0% 0% 52.6°C 18:20:41: 1488MHz 2.48 94% 1% 93% 0% 0% 0% 57.0°C 18:20:47: 1488MHz 2.60 79% 2% 77% 0% 0% 0% 53.9°C 18:20:52: 1488MHz 2.71 90% 2% 87% 0% 0% 0% 55.2°C 18:20:58: 1488MHz 2.90 94% 2% 91% 0% 0% 0% 58.6°C 18:21:04: 1488MHz 3.06 80% 1% 78% 0% 0% 0% 54.9°C 18:21:09: 1488MHz 3.13 84% 2% 81% 0% 0% 0% 55.2°C 18:21:14: 1488MHz 3.28 89% 2% 87% 0% 0% 0% 56.1°C 18:21:24: 720MHz 4.14 93% 13% 37% 0% 41% 0% 46.4°C 18:21:30: 720MHz 4.16 1% 0% 0% 0% 0% 0% 43.6°C Round 3 without fan Time CPU load %cpu %sys %usr %nice %io %irq CPU 18:21:55: 1488MHz 2.98 42% 1% 39% 0% 0% 0% 55.1°C 18:22:01: 1488MHz 3.06 95% 2% 92% 0% 0% 0% 60.0°C 18:22:06: 1488MHz 3.30 82% 2% 79% 0% 0% 0% 56.5°C 18:22:13: 1488MHz 3.20 94% 1% 92% 0% 0% 0% 61.6°C 18:22:18: 1488MHz 3.02 80% 1% 77% 0% 0% 0% 57.3°C 18:22:23: 1488MHz 3.18 89% 2% 86% 0% 0% 0% 58.3°C 18:22:30: 1488MHz 3.40 93% 2% 90% 0% 0% 0% 62.1°C 18:22:36: 1488MHz 3.33 80% 1% 78% 0% 0% 0% 59.1°C 18:22:41: 1488MHz 3.22 85% 2% 82% 0% 0% 0% 58.8°C 18:22:47: 1488MHz 3.20 90% 2% 87% 0% 0% 0% 60.1°C 18:22:54: 1080MHz 3.59 94% 21% 44% 0% 27% 0% 50.4°C 18:22:59: 888MHz 3.70 3% 1% 0% 0% 1% 0% 46.9°C Round 4 without fan Time CPU load %cpu %sys %usr %nice %io %irq CPU 18:23:35: 1488MHz 2.54 54% 1% 52% 0% 0% 0% 57.2°C 18:23:40: 1488MHz 2.74 95% 1% 94% 0% 0% 0% 62.0°C 18:23:45: 1488MHz 2.76 81% 2% 78% 0% 0% 0% 59.0°C 18:23:52: 1488MHz 2.86 94% 1% 93% 0% 0% 0% 63.6°C 18:23:57: 1488MHz 2.79 79% 2% 77% 0% 0% 0% 59.6°C 18:24:02: 1488MHz 2.73 90% 2% 87% 0% 0% 0% 61.4°C 18:24:09: 1488MHz 2.75 94% 2% 91% 0% 0% 0% 64.0°C 18:24:15: 1488MHz 2.94 79% 1% 77% 0% 0% 0% 60.7°C 18:24:20: 1488MHz 2.94 84% 1% 82% 0% 0% 0% 61.6°C 18:24:25: 1488MHz 2.87 90% 3% 86% 0% 0% 0% 62.4°C 18:24:33: 1488MHz 3.28 94% 22% 46% 0% 24% 0% 55.4°C 18:24:38: 1080MHz 3.09 7% 1% 2% 0% 2% 0% 48.9°C

30 degrees with standard use. Not fully idle or maxed. What tool did you use for a full load test?