Quote from danielosser on July 31, 2018, 11:05 am

Hi.

Then Therese might be something odd with my unit. No BT connectivity at all. Would be great if I could troubleshoot the system. 😉

 

looking forward to the post.

 

Quote from Zheng Han on July 31, 2018, 11:21 pm

@danielosser

Please check the following post for low level interaction with the audio subsystem

https://getoboo.com/community/topic/interact-with-audio-subsystem/

One way to test it is to install alsa-utils and run aplay -L when the audio system is switched to internal audio mode. Under this mode aplay -L will list available sound cards. If you don't see it showing the first time try switch back and forth a few time.

Let me know how it goes.

Quote from danielosser on August 1, 2018, 4:34 pm

@zhonion-io

I'm stumped. I can't find any sound device:

root@Oboo-Clock-50A0:/# aplay -l
aplay: device_list:268: no soundcards found...
root@Oboo-Clock-50A0:/# aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
root@Oboo-Clock-50A0:/#

and no uart device for bluetooth.

root@Oboo-Clock-50A0:/# dmesg |grep -i blue
[ 12.528456] Bluetooth: Core ver 2.21
[ 12.536759] Bluetooth: HCI device and connection manager initialized
[ 12.543215] Bluetooth: HCI socket layer initialized
[ 12.548176] Bluetooth: L2CAP socket layer initialized
[ 12.553332] Bluetooth: SCO socket layer initialized
[ 12.560949] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 12.566420] Bluetooth: BNEP filters: protocol multicast
[ 12.571735] Bluetooth: BNEP socket layer initialized
[ 12.781101] Bluetooth: HCI UART driver ver 2.3
[ 12.785623] Bluetooth: HCI UART protocol H4 registered
[ 12.790909] Bluetooth: HCI UART protocol BCSP registered
[ 12.800495] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 12.806600] Bluetooth: HIDP socket layer initialized
[ 12.866629] Bluetooth: RFCOMM TTY layer initialized
[ 12.871616] Bluetooth: RFCOMM socket layer initialized
[ 12.876907] Bluetooth: RFCOMM ver 1.11
root@Oboo-Clock-50A0:/#

Any more suggestions?

 

 

 

Quote from Zheng Han on August 1, 2018, 5:59 pm

@danielosser

Can you try the following commands and share the output?

gpioctl dirout-low 41

sleep 2

gpioctl dirout-high 41

sleep 2

gpioctl dirout-low 41

sleep 2

gpioctl dirout-high 41

sleep 2

gpioctl dirout-low 41

sleep 2

aplay -L

dmesg | grep AUDIO

Quote from danielosser on August 1, 2018, 6:33 pm

@zhonion-io

Output...

root@Oboo-Clock-50A0:~# gpioctl dirout-low 41
Using gpio pin 41.
root@Oboo-Clock-50A0:~# sleep 2
root@Oboo-Clock-50A0:~# gpioctl dirout-high 41
Using gpio pin 41.
root@Oboo-Clock-50A0:~# sleep 2
root@Oboo-Clock-50A0:~# gpioctl dirout-low 41
Using gpio pin 41.
root@Oboo-Clock-50A0:~# sleep 2
root@Oboo-Clock-50A0:~# gpioctl dirout-high 41
Using gpio pin 41.
root@Oboo-Clock-50A0:~# sleep 2
root@Oboo-Clock-50A0:~# gpioctl dirout-low 41
Using gpio pin 41.
root@Oboo-Clock-50A0:~# sleep 2
root@Oboo-Clock-50A0:~# aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
root@Oboo-Clock-50A0:~# dmesg |grep AUDIO
root@Oboo-Clock-50A0:~#
root@Oboo-Clock-50A0:~#
root@Oboo-Clock-50A0:~#
root@Oboo-Clock-50A0:~#
root@Oboo-Clock-50A0:~# dmesg |grep audio
[ 12.998738] usbcore: registered new interface driver snd-usb-audio

Quote from Zheng Han on August 1, 2018, 11:24 pm

@danielosser

Thanks for helping us debug here. Looks like the audio system is not responding. We will contact you tomorrow to get the exchange process started. Sorry for the trouble.

Quote from Brooke. on August 4, 2018, 3:42 pm

The speaker is pretty good, I'm wondering if it can be improved for voice. I listen to a lot of podcast and the vocals sound a bit "tinny". The other improvement I'd like to see is better switching between devices. Right now you must disconnect from a device before selecting the next device. It would be nice if it would switch between devices by selecting the "connect" on one would disconnect on another.

Quote from ckruetze on August 12, 2018, 11:20 am

I know this is "enable Bluetooth Audio" but is there a way to disable bluetooth completely?

As in turn it off, save battery, don't be reachable, ...

 

Quote from Zheng Han on August 13, 2018, 4:15 pm

@ckruetze

We don't currently have a way to completely turn off bluetooth. It's something we can look into later on.

Quote from sygyzy on March 20, 2019, 9:30 pm

Is there any way to at least set a new pin for the bluetooth? I have a neighbor connecting to it and playing music.