ASUS USB-BT400 (USB, Bluetooth 4.0)

I/O Asus, Bluetooth, USB

ASUS USB-BT400 (USB, Bluetooth 4.0)
Linux compatibility:
5 votes, average: 3.8 out of 55 votes, average: 3.8 out of 55 votes, average: 3.8 out of 55 votes, average: 3.8 out of 55 votes, average: 3.8 out of 5
  ( 3.8 with 5 ratings)

Price: $ 12.00 (on stock)
(without shipping costs)

 Buy from


Price trend
Minimum: $ 8.99 
Maximum: $ 10.99  
Updated: 27/05/2016 01:56

Review of Linux Compatibility

The ASUS USB-BT400 is a USB adapter supporting Bluetooth 4.0.The stick has the USB ID 0b05:17cb:

Bus 003 Device 002: ID 0b05:17cb ASUSTek Computer, Inc.

ans is supported under Linux since kernel version 3.11.0-15 by the kernel module “btusb” (e.g. under Ubuntu 13.10). The stick is recognized and activated automatically when plugged in.

The stick bases on the BCM20702A0 chipset:

T:  Bus=03 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  6 Spd=12  MxCh= 0
    D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=0b05 ProdID=17cb Rev=01.12
    S:  Manufacturer=Broadcom Corp
    S:  Product=BCM20702A0
    S:  SerialNumber=000270000000
    C:  #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mA

If a older kernel version is used, the stick is not recognized, since the USB ID is not known to such Linux kernels. This can simply be corrected by adding the ID in the following way (comments have to be executed as superuser “root”):

modprobe -v btusb
echo "0b05 17cb" >> /sys/bus/usb/drivers/btusb/new_id

The following configuration of /etc/bluetooth/audio.conf was used to stream audio via the Bluetooth stick:

# Configuration file for the audio service

# This section contains options which are not specific to any
# particular interface

# Switch to master role for incoming connections (defaults to true)

# If we want to disable support for specific services
# Defaults to supporting all implemented services

# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI

# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.

# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)

# Set to true to support HFP, false means only HSP is supported
# Defaults to true

# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1

# Set to true to enable use of fast connectable mode (faster page scanning)
# for HFP when incoming call starts. Default settings are restored after
# call is answered or rejected. Page scan interval is much shorter and page
# scan type changed to interlaced. Such allows faster connection initiated
# by a headset.

# Just an example of potential config options for the other interfaces

Identified Hardware Configurations (5 Results)

This hardware component was used by Linux users under the following system configurations. These results were collected by our LHG Scan Tool:
Scan Date
blackPanther OS v16.2SE (Silent Killer) 4.9.20-desktop-pae-1bP - 29/06/2017
Ubuntu 16.04.2 LTS 4.8.0-51-generic - 03/05/2017
blackPanther OS v16.2SE (Silent Killer) 4.7.0-desktop-1bP - 17/04/2017
blackPanther OS v16.2SE (Silent Killer) 4.9.15-desktop-1bP - 12/04/2017
Ubuntu 16.10 4.8.0-27-generic - 24/11/2016

Similar Linux Hardware

scroll left scroll right


  • Comments

    Please use the comment section to submit corrections to the article as well as relevant excerpts of lspci, lsusb, lshw, dmesg e.t.c. Furthermore, use the section for the exchange of experiences with this hardware component or search for configuration help from other owners of this hardware.
    Email address will not be published.
    Submitting comment...