Dear all,
I’m facing a problem with my ARTIK520.
After upgrading from version 1.24, the bluetooth doesn’t work anymore.
Is there a new version of resinOS who solve this issue?
Thank you very much.
Thank you. We are aware of the issue and a new version of resinOS for the ARTIK520 will be released soon, with a fix for bluetooth.
Thank you Afitzek,
could you please tell me the release date?
It was released just a couple of minutes ago (2.0.8+rev1). 
Thank you very much!
Hi Afitzek,
I installed the new version of resinOS on my ARTIK 520, but I still have problem with the bluetooth.
I installed bluez because I didn’t find the bluetooth service inside the "default"2.0.8 resinOS version.
I executed the following commands:
# agent on
# default-agent
and
# scan on
The result is:
No default controller available
Am I doing something wrong?
Thanks!
Can you also install rfkill and issue a “rfkill list”? And if bluetooth shows as soft blocked, can you do a “rfkill unblock bluetooth” and try again?
Hi! I found that:
root@2b4b970-2b4b970:/usr/src/app# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: brcmfmac-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
2: bcm4354 Bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
then
root@2b4b970-2b4b970:/usr/src/app# rfkill unblock bluetooth
root@2b4b970-2b4b970:/usr/src/app# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: brcmfmac-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
2: bcm4354 Bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
I restarted the bluetooth service, and repeat the bluetoothctl commands,but the result is still the same.
No default controller available
after rebooting ARTIK, the status of the bluetooth service is as follows:
root@2b4b970-2b4b970:/usr/src/app# systemctl status bluetooth.service -l
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Active: active (running) since Fri 2017-07-07 09:27:30 UTC; 1min 57s ago
Docs: man:bluetoothd(8)
Main PID: 151 (bluetoothd)
Status: "Running"
CGroup: /docker/b181d9339d5b880211b8f78b3a143d5e42bcd1f87848ec2080d3d1407ef8ed48/system.slice/bluetooth.service
└─151 /usr/lib/bluetooth/bluetoothd
Jul 07 09:27:29 2b4b970-2b4b970 bluetoothd[151]: l2cap_bind: Address already inuse (98)
Jul 07 09:27:29 2b4b970-2b4b970 bluetoothd[151]: network-nap: Invalid argument (22)
Jul 07 09:27:29 2b4b970-2b4b970 bluetoothd[151]: l2cap_bind: Address already inuse (98)
Jul 07 09:27:29 2b4b970-2b4b970 bluetoothd[151]: avrcp-controller: Protocol notsupported (93)
Jul 07 09:27:29 2b4b970-2b4b970 bluetoothd[151]: l2cap_bind: Address already inuse (98)
Jul 07 09:27:29 2b4b970-2b4b970 bluetoothd[151]: audio-avrcp-target: Protocol not supported (93)
Jul 07 09:27:29 2b4b970-2b4b970 bluetoothd[151]: Sap driver initialization failed.
Jul 07 09:27:29 2b4b970-2b4b970 bluetoothd[151]: sap-server: Operation not permitted (1)
Jul 07 09:27:29 2b4b970-2b4b970 bluetoothd[151]: hci0 Load Connection Parameters failed: Unknown Command (0x01)
Jul 07 09:27:30 2b4b970-2b4b970 systemd[1]: Started Bluetooth service.Let me look at it on my side too and come back to you.
Do you have a -dev image so you can access the host OS on the serial debug connection?
No, But I saw that the -dev version of the 2.0.8 is available.
I have to download it and flash it.
What are you looking for?
Can you install the .dev variant please?
On my end I seem to have bluetooth working on the host OS side. I would like to verify on your machine a few things once you have the -dev variant installed and you are connected on the serial debug connection to the host OS.
Hi!
I installed the .dev version and connected the device through the serial debug.
Which are the next steps?
What does “systemctl status brcm-bt-firmware.service -l” say?
Thank you, but now what I have to do? 
Wait for another release
I hope to have the 2.0.9 done sometimes on Monday
Hi @samsung.test0 we have released version v2.0.8+rev2 which should fix the bluetooth issue you reported.