lwfinger / rtl8723au_bt Goto Github PK

As-is, the package doesn't contain dkms support files. Here's a simple patch for dkms support, based on your 8723au WiFi driver code:

new file mode 100644
index 0000000..f874a95
--- /dev/null
+++ b/README.dkms
@@ -0,0 +1,14 @@
+
+To get DKMS to work:
+
+- Install dkms
+- Copy this source to the directory /usr/src/8723au-0.1/
+- Run (as root):
+
+    $ dkms add -m 8723au -v 0.1
+
+- Test a build:
+
+    $ dkms build -m 8723au -v 0.1
+
+From now on this drive should be available for any new kernels.
diff --git a/dkms.conf b/dkms.conf
new file mode 100644
index 0000000..bc588d2
--- /dev/null
+++ b/dkms.conf
@@ -0,0 +1,6 @@
+PACKAGE_NAME="rtl8723au_bt"
+PACKAGE_VERSION="0.1"
+BUILD_MODULE_NAME[0]="rtk_btusb"
+BUILT_MODULE_NAME[0]="rtk_btusb"
+DEST_MODULE_LOCATION[0]="/kernel/drivers/bluetooth"
+AUTOINSTALL="yes"

Makefile:15: set of instructions for "all" not possibel
make: *** [all] Errore 2

This is the error i get compiling rtl8723au_bt on 4.2.0-19 Kernel Ubuntu 15.10 Gnome

Maybe can be useful

Using Linux Mint 15 and I'm getting really slow download speeds.

I get about 30Mb download speeds on windows/vmware running linux mint 15. When booting to linux mint and using this driver I get about 1Mb download speeds. The weird thing my upload speeds are normal, just the download speeds are bad. I've tried disabling ipv6 but still get horrible download speeds.

Please let me know what I can provide.

Hello.
I am using ArchLinux now with 3.17.6-1 kernel and Lenovo yoga 13 ideapad.
My bluetooth is not working. As I explained here lwfinger/rtl8723au#53 about wifi, I have blacklisted r8723au, and then probed 8723au. My /etc/modprobe.d/mywifi.conf is the following

#blacklisting kernel's wifi
blacklist r8723au

#probing aur's wifi
8723au

Now I am trying to get bluetooth work.
I have git cloned this repo, made it and installed. By the way, it says

[root@yoga ~]# modprobe btusb 
libkmod: kmod_config_parse: /etc/modprobe.d/mywifi.conf line 5: ignoring bad line starting with     '8723au'

for some reason...
If I run #bluetoothctl there are not any controllers shown.
Please, help me.

I have tried to compile the driver using make, but I get the error

/home/carlos/tmp/rtl8723au_bt/btusb.c:3220:20: error: ‘HCI_BREDR’ undeclared (first use in this function)
 hdev->dev_type = HCI_BREDR;

This happens both on the kernel and test branches. I'm on 4.8.6-1-ARCH in Arch Linux

The other branches give me errors related to struct hci_dev (has no member reassembly).

Hello!

I installed Ubuntu 15.04 and with it the 4.0 RC6 Mainline Kernel. I compiled rtlwifi-new and rtl8723au_bt from the troy branch. I got bluetooth to work but every time after suspending or rebooting I have to install my bluetooth mouse again. From the taskbar I can see that the mouse is trying to connect with my computer (connection lasts for less than a second every time I move the mouse).

I also tried the kernel branch of rtl8723au_bt, but the same thing happens.
Any recommendations on how to get bluetooth working like it did with the previous Ubuntu version?

EDIT: Is it possible that it's related to Ubuntu switching to systemd as default?
EDIT2: Booted with upstart, but nothing changed.

This line:

It was not clear to me which branch I should use for RTL8723BU with a 3.19 kernel.

Testing I found the 'new' branch worked, but it would be nice if it were documented in the readme which branch should be used when. I'd be happy to open a pull request if someone can provide an outline of the purpose of different branches.

Not working in my laptop which is running Ubuntu 16.04 LTS 64 bit with kernel 4.4.0-47-generic.
My wireless device is RTL8723BE

Another problem is that it is not uninstalling

sudo make uninstall

rm -f /lib/modules/4.4.0-47-generic/kernel/drivers/bluetooth/btusb.ko*
depmod -a /lib/modules/4.4.0-47-generic
depmod: ERROR: Bad version passed /lib/modules/4.4.0-47-generic
Makefile:51: recipe for target 'uninstall' failed
make: *** [uninstall] Error 1

generic details:
kernel-4.4.0-36-generic
Linux mint 18 sarah.
wifi driver rtl8723be
bluetooth driver: rtl8723au
Things attached: Dmesg log, journalctl log, systemctl log.
Things that get the bluetooth device started are modprobe -rv btusb, modprobe -v btusb.
Module installed from kernel branch rest all throw errors.
boot-Config:: http://pastebin.com/6xnXMByS

Problem: I have installed rtlwifi .
My phone scans the laptop after updating bluez to the latest version, unable to pair/connect and hcitool scan fails.
After modprobe commands the bluetooth is visible for a rough 30 secs.
I've read all the issues on your kernel thread alspo still couldn't find a way to keep this stable
could you guide me on how to fix this.
I know you're very busy but a little help would be sufficient for me.

dmesg log and journalctl log
.
.
.
.
.
.
.
systemctl log

lsusb and insmod

EDIT: after following this thread #39 I got the device up and running and stable but it doesn't find any devices but still this persists.

Edit1 : downgraded bluez to .23 Still can't find devices

make -C /lib/modules/3.19.0-15-generic/build M=/home/zheka/rtl8723au_bt modules
make[1]: вход в каталог «/usr/src/linux-headers-3.19.0-15-generic»
CC [M] /home/zheka/rtl8723au_bt/rtk_btusb.o
/home/zheka/rtl8723au_bt/rtk_btusb.c: In function ‘btusb_intr_complete’:
/home/zheka/rtl8723au_bt/rtk_btusb.c:164:3: error: implicit declaration of function ‘hci_recv_fragment’ [-Werror=implicit-function-declaration]
if (hci_recv_fragment(hdev, HCI_EVENT_PKT,
^
cc1: some warnings being treated as errors

As far as I know, the Realtek 8723 hardware is capable of Bluetooth 4.0 Low Energy/Bluetooth Smart mode.

I haven't been able to figure out for sure whether or not this driver supports this operation by playing around with hcitool lescan or grepping for LE/4.0/Smart in the code... perhaps this is not something that needs to be implemented in a device-specific driver?

no bnep0 device created no networking possible.
Works with some other bluetooth stick i have.

Hi There!

I have this combinated WIFI/Bluetooth-Adapter on my HP ProBook 450 G2. And it worked for a long time, since Kernel 4.0 (i think i remember correcktly)

Now it stopped working on Debian stretch with kernel 4.6.0-1, also with Kernel 4.5

# lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 062a:4101 Creative Labs Wireless Keyboard/Mouse
Bus 002 Device 003: ID 05c8:0374 Cheng Uei Precision Industry Co., Ltd (Foxlink) 
Bus 002 Device 002: ID 0bda:b001 Realtek Semiconductor Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I compiled and installed the rtlwifi from the troy-branch, and i can see my laptop on my mobile-phone, but i'm not able to pair the devices. The laptop does not recognize the mobile-phone on bluetooth.

Installing this driver nothing happens.

Do you need more infos

Best regards

Jakob

The hci_recv_fragment function has been removed in Linux kernel 3.18.

cf. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0097db06f5ab2df1756bc4cbf4395593024d87a1

This leads to build errors in both master and new branches.

rtk_btusb.c:164:3: error: implicit declaration of function ‘hci_recv_fragment’ [-Werror=implicit-function-declaration]
   if (hci_recv_fragment(hdev, HCI_EVENT_PKT,
   ^

btusb.c:376:3: error: implicit declaration of function ‘hci_recv_fragment’ [-Werror=implicit-function-declaration]
   if (hci_recv_fragment(hdev, HCI_EVENT_PKT,
   ^

Linux_BT_USB_2.11.20140423_8723BE/rtk_btusb.c:143:3: error: implicit declaration of function ‘hci_recv_fragment’ [-Werror=implicit-function-declaration]
   if (hci_recv_fragment(hdev, HCI_EVENT_PKT,
   ^

Hi (;
I have rtl8723be wifi and bt card. Wifi works ootb on 4.2 kernel, so I tried to install bt driver, but terminal gave me error messages. Output here → http://pastebin.com/NEvmhN9s

On kernel 316 wifi and bt didn`t work, I installed master branch from https://github.com/lwfinger/rtlwifi_new. Only wifi worked.
Then after reboot i installed kernel branch from https://github.com/lwfinger/rtl8723au_bt. Then i install troy branch of it and wifi and bt works good.

What I need to do to have bluetooth and wifi working on 4.20??

I can give all config files, outputs etc if need (;

Hello!
I spend many time, but can't solve problem with Wi-Fi. When laptop enter in sleep mode, after wakeup wifi does not work. It always need reboot the system.
I use new brahch of your driver. master branch not work for me.

cat /etc/modprobe.d/rtl8723be.conf
options rtl8723be ant_sel=2 fwlps=0 swlps=0 ips=0

uname -r
3.16.0-4-amd64

uname -v
#1 SMP Debian 3.16.7-ckt25-2 (2016-04-08)

lspci | grep RTL
08:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter 09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 0a)

BT also not working, but I solve this broblem with long audio cable.

Laptop:
HP Pavilion 15-ab225ur, P3L10EA

Please help.

Hello,

I'll just give you output, it's not that long and it has all I did.

[root@localhost rtl8723au_bt-kernel]# make
make -C /lib/modules/3.19.8-100.fc20.x86_64/build M=/home/k_georgiev/work/rtl8723au_bt-kernel modules
make[1]: Entering directory /usr/src/kernels/3.19.8-100.fc20.x86_64' Building modules, stage 2. MODPOST 1 modules make[1]: Leaving directory/usr/src/kernels/3.19.8-100.fc20.x86_64'
[root@localhost rtl8723au_bt-kernel]# make install
depmod -a /lib/modules/3.19.8-100.fc20.x86_64
installed revised btusb
[root@localhost rtl8723au_bt-kernel]# modprobe -rv btusb
rmmod btusb
[root@localhost rtl8723au_bt-kernel]# modprobe -v btusb
insmod /lib/modules/3.19.8-100.fc20.x86_64/kernel/drivers/bluetooth/btusb.ko
[root@localhost rtl8723au_bt-kernel]# lsmod |grep -i btusb.
btusb 45899 0
[root@localhost rtl8723au_bt-kernel]# rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
[root@localhost rtl8723au_bt-kernel]#

And on the user interface on gnome I see no bluetooth functioning.
I saw issue 'bluetooth not working while wifi is on' so I stopped the wifi but got same result.

Thanks

I tried to setup bluetooth on Radxa Rock using rockchip 3166 SoC and the rtl 8723au WLAN/Bluetooth combi adapter.

WLAN and BT setup on Radxa Rock is explained here:
http://wiki.radxa.com/Rock/Wireless

WLAN works with the 8723au kernel module.

For Bluetooth I cross-compliled rtl8723au_bt with arm-linux-gnueabihf-gcc-4.7 on debian 64bit PC. After insmod on the ARM device, "hcitool dev" shows the hci0 adapter, "hcitool scan" shows the remote bluetooth device. But pairing fails inevitably.

"bluez-smple-agent hci0 addr" (& Co) never come back instead of asking for the PIN, blueman and bluedevil say "failed" without any further comment, "hcitool cc addr" times out.
I only managed to connect a bluetooth GPS adapter on /dev/rfcomm, without a pairing procedure. My bt headset and my mobile phone I could not pair.

Bluez 4.101 is used, but I also tried down- and upgrading to Bluez 4.66-3 and Bluez 5.5-1 (armhf debian packages).

Radxa Rock uses kernel 3.0.36+ which is customized so I cannot just upgrade.

Did someone ever try the kernel module out on an ARM device or does anyone have an idea what might be wrong?

Alex

Greetings, I wonder - are you planning an update for kernel 4.4 for the release of the new version of Ubuntu? I'm running 16.04 beta 2 right now, and I'm debating if I should downgrade or just wait a little longer

Thank you very much for your work, you saved my new machine from an otherwise unavoidable windows configuration

I have tried the kernel and the new branchs. dmesg shows a complaint that the firmware is for 8723 but card is 0x4ce1. Both branch's work on 3.19.x for me, on the 3.19.x branchs hciconfig -a hci0 show the LMP subversion as 0x4ce1 but there is no complaint about this in dmesg. I brought the bluetooth stack from the 3.19.x and replaced it with 4.0.4's, this came the closest to working i actually get a mac address and the bottom info from the hciconfig -a hci0 command. But even tho it tries without error hcitool scan plus gui tools are unable to find anything. I have made sure I have the correct firmwares in correct folders /lib/firmware /lib/firmware/rtl_bt I even put the firmware in both places for each driver respectivly. Thank You;
PS originaly i could never get these drivers to work unless I also used lwfingers wifi driver. What seemed to happen is bluetooth would try to use non existent antenna (my card has only one antenna port for both wifi bluetooth, not sure if all 8723be cards are like this) and have tried both stock and lwfingers wifi driver

Been fooling with these drivers trying to get them working on my (newish) laptop. bluetooth device always showed up as:

0: Toshiba Bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
3: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

and poking it with lsusb showed the device as

Bus 001 Device 010: ID 0930:0222 Toshiba Corp.

prodding it for more info returned the following. Nowhere did it mention realtek chipset so I figured maybe it wasn't being recognized properly and maybe Toshiba had a custom version made for this line of laptops:

Bus 001 Device 010: ID 0930:0222 Toshiba Corp. 
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass          224 Wireless
  bDeviceSubClass         1 Radio Frequency
  bDeviceProtocol         1 Bluetooth
  bMaxPacketSize0        64
  idVendor           0x0930 Toshiba Corp.
  idProduct          0x0222 
  bcdDevice            2.00
  iManufacturer           1 
  iProduct                2 
  iSerial                 3 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          177
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              4 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              4 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0000  1x 0 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0000  1x 0 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       1
      bNumEndpoints           2
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              4 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0009  1x 9 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0009  1x 9 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       2
      bNumEndpoints           2
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              4 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0011  1x 17 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0011  1x 17 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       3
      bNumEndpoints           2
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              4 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0019  1x 25 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0019  1x 25 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       4
      bNumEndpoints           2
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              4 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0021  1x 33 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0021  1x 33 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       5
      bNumEndpoints           2
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              4 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0031  1x 49 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0031  1x 49 bytes
        bInterval               1

Anyway, after scratching my head I figured I'd just throw caution of the wind and poke at the btusb source. I changed the following starting at about line 309 (from the latest -kernel git branch)

Original:

/* Additional Realtek 8723AE Bluetooth devices */
{ USB_DEVICE(0x0930, 0x021d), .driver_info = BTUSB_REALTEK },
{ USB_DEVICE(0x13d3, 0x3394), .driver_info = BTUSB_REALTEK },

New:

/* Additional Realtek 8723AE Bluetooth devices */
{ USB_DEVICE(0x0930, 0x021d), .driver_info = BTUSB_REALTEK },
{ USB_DEVICE(0x0930, 0x0222), .driver_info = BTUSB_REALTEK },
{ USB_DEVICE(0x13d3, 0x3394), .driver_info = BTUSB_REALTEK },

After recompiling and re-inserting the module, dmesg showed:

[    6.000307] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
[    6.000314] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin

So I assume that means it's loading the firmware now. And bluetooth works. So yay!

Anyway, thought I'd share my success and hope someone else finds this useful.

System:    Kernel: 4.2.0-16-generic x86_64 (64 bit) Desktop: Gnome 3.18.0 Distro: Ubuntu 15.10 wily
Machine:   System: TOSHIBA product: Satellite L15W-B v: PSKVQU-002002
           Mobo: TOSHIBA model: MA20 Bios: TOSHIBA v: 1.30 date: 05/22/2015
Network:   Card: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be

I've got a Realtek 8723be, wifi and bluetooth chip, and a bluetooth keyboard and mouse.

If I lock the screen (Fedora 22, gnome-shell), and unlock the screen, the bluetooth devices disconnect -- but only after unlocking.

gnome-shell powers down just about everything on lock. It's not a full suspend, but the screen and other devices are powered down. Dunno how to stop that.

So here's in more detail:

1. login
2. bluetooth is paired
3. lock (gnome-shell powers down)
4. unlock (type password using bluetooth keyboard)
5. wait a few seconds
6. keyboard and mouse disconnect

To fix:
7. rmmod btusb
8. modprobe btusb
9. stays connected until next lock.

While the disconnect is happening, you can see the devices constantly connecting and disconnecting, every two seconds or so.

Dunno if this is this driver, wifi driver, bluetooth or gnome-session problem, but I'm logging it here first because I'm using an out-of-kernel driver. The devices seem to work fine on another laptop.

Brief hardware list:

Chip: Bus 001 Device 002: ID 0bda:b001 Realtek Semiconductor Corp.
Keyboard: logitech dinovo edge
mouse: logitech m555b (tried other mice too)

Brief software list:

Fedora 22
kernel 4.0.7-300.fc22.x86_64
rtl8723au_bt (9024cea)
rtlwifi_new (fe8e96938599e97cf4f76d22e6ab00066ff05ec5)
bluez-5.29-2.fc22.x86_64
gnome-session-3.16.0-1.fc22.x86_64

Brief logs:

dmesg:

on wakeup, lots of this stuff (there's about 15 bluetooth devices in reach):

[ 7148.016262] Bluetooth: hci0 ACL packet for unknown connection handle 3
[ 7174.226519] Bluetooth: hci0 ACL packet for unknown connection handle 5
[ 7207.261043] Bluetooth: hci0 ACL packet for unknown connection handle 6

on rmmod btusb/modprobe usb:

[ 7232.536244] usbcore: registered new interface driver btusb
[ 7232.540978] Bluetooth: hci0: hci_ver=06 hci_rev=0e2f lmp_ver=06 lmp_subver=9f73
[ 7232.540982] Bluetooth: rtl8723b: assuming no firmware upload needed.
[ 7236.924712] Bluetooth: hci0 ACL packet for unknown connection handle 1
[ 7242.934595] Bluetooth: hci0 ACL packet for unknown connection handle 2
[ 7258.531170] Bluetooth: hci0 ACL packet for unknown connection handle 3
[ 7265.538093] Bluetooth: hci0 ACL packet for unknown connection handle 4
[ 7272.158524] Bluetooth: hci0 ACL packet for unknown connection handle 5
[ 7294.762926] hid-generic 0005:046D:B009.0007: unknown main item tag 0x0
[ 7294.762979] input: Logitech Bluetooth Mouse M555b as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:1/0005:046D:B009.0007/input/input35
[ 7294.763348] hid-generic 0005:046D:B009.0007: input,hidraw0: BLUETOOTH HID v4.19 Mouse [Logitech Bluetooth Mouse M555b] on c4:8e:8f:c1:99:7a
[ 7305.194917] Bluetooth: hci0 ACL packet for unknown connection handle 2
[ 7311.863486] hid-generic 0005:046D:B309.0008: unknown main item tag 0x0
[ 7311.884072] input: Logitech diNovo Edge as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:3/0005:046D:B309.0008/input/input36
[ 7311.884277] hid-generic 0005:046D:B309.0008: input,hidraw1: BLUETOOTH HID v1.1b Mouse [Logitech diNovo Edge] on c4:8e:8f:c1:99:7a

from messages (journalctl):

I'm trying to find out if the following is immediately on lock. I'm pretty sure it's before unlock:

Jul 17 09:59:22 sieve-deschouwer-co-za /usr/libexec/gdm-x-session[2352]: (II) config/udev: removing device Logitech Bluetooth Mouse M555b
Jul 17 09:59:22 sieve-deschouwer-co-za /usr/libexec/gdm-x-session[2352]: (**) Option "fd" "38"
Jul 17 09:59:22 sieve-deschouwer-co-za /usr/libexec/gdm-x-session[2352]: (II) UnloadModule: "libinput"
Jul 17 09:59:22 sieve-deschouwer-co-za /usr/libexec/gdm-x-session[2352]: (II) systemd-logind: releasing fd for 13:80

after rmmod/modprobe:

Jul 17 10:11:33 sieve-deschouwer-co-za kernel: usbcore: deregistering interface driver btusb
Jul 17 10:11:33 sieve-deschouwer-co-za kernel: Bluetooth: hci0 urb ffff88044aefa000 failed to resubmit (2)
Jul 17 10:11:33 sieve-deschouwer-co-za /usr/libexec/gdm-x-session[2352]: (II) config/udev: removing device Logitech diNovo Edge
Jul 17 10:11:33 sieve-deschouwer-co-za /usr/libexec/gdm-x-session[2352]: (*) Option "fd" "39"
Jul 17 10:11:33 sieve-deschouwer-co-za /usr/libexec/gdm-x-session[2352]: (II) UnloadModule: "libinput"
Jul 17 10:11:33 sieve-deschouwer-co-za /usr/libexec/gdm-x-session[2352]: (II) systemd-logind: releasing fd for 13:81
Jul 17 10:11:33 sieve-deschouwer-co-za bluetoothd[1315]: Endpoint unregistered: sender=:1.53 path=/MediaEndpoint/A2DPSource
Jul 17 10:11:33 sieve-deschouwer-co-za bluetoothd[1315]: Endpoint unregistered: sender=:1.53 path=/MediaEndpoint/A2DPSink
Jul 17 10:11:33 sieve-deschouwer-co-za systemd[1]: Stopping Load/Save RF Kill Switch Status of rfkill3...
...
Jul 17 10:11:37 sieve-deschouwer-co-za systemd[1]: Reached target Bluetooth.
Jul 17 10:11:37 sieve-deschouwer-co-za systemd[1]: Starting Bluetooth.
Jul 17 10:11:37 sieve-deschouwer-co-za systemd[1]: Starting Load/Save RF Kill Switch Status of rfkill4...
Jul 17 10:11:37 sieve-deschouwer-co-za kernel: Bluetooth: hci0: hci_ver=06 hci_rev=0e2f lmp_ver=06 lmp_subver=9f73
Jul 17 10:11:37 sieve-deschouwer-co-za kernel: Bluetooth: rtl8723b: assuming no firmware upload needed.
Jul 17 10:11:37 sieve-deschouwer-co-za systemd[1]: Started Load/Save RF Kill Switch Status of rfkill4.
Jul 17 10:11:37 sieve-deschouwer-co-za audit[1]: pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill@rfkill4 comm="systemd" exe=
Jul 17 10:11:37 sieve-deschouwer-co-za bluetoothd[1315]: Failed to obtain handles for "Service Changed" characteristic
Jul 17 10:11:37 sieve-deschouwer-co-za bluetoothd[1315]: Endpoint registered: sender=:1.53 path=/MediaEndpoint/A2DPSource
Jul 17 10:11:37 sieve-deschouwer-co-za bluetoothd[1315]: Endpoint registered: sender=:1.53 path=/MediaEndpoint/A2DPSink
Jul 17 10:11:41 sieve-deschouwer-co-za kernel: Bluetooth: hci0 ACL packet for unknown connection handle 1
Jul 17 10:11:47 sieve-deschouwer-co-za kernel: Bluetooth: hci0 ACL packet for unknown connection handle 2
Jul 17 10:12:00 sieve-deschouwer-co-za audit[1]: pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/syste
Jul 17 10:12:03 sieve-deschouwer-co-za kernel: Bluetooth: hci0 ACL packet for unknown connection handle 3
Jul 17 10:12:10 sieve-deschouwer-co-za gnome-session[2413]: (gnome-settings-daemon:2538): housekeeping-plugin-WARNING *: Failed to enumerate children of /tmp/systemd-private-4202f6ed28b246f
Jul 17 10:12:10 sieve-deschouwer-co-za gnome-session[2413]: (gnome-settings-daemon:2538): housekeeping-plugin-WARNING *: Failed to enumerate children of /var/tmp/systemd-private-a59bc1cb7d6
Jul 17 10:12:10 sieve-deschouwer-co-za gnome-session[2413]: (gnome-settings-daemon:2538): housekeeping-plugin-WARNING *: Failed to enumerate children of /tmp/systemd-private-4202f6ed28b246f

I've successfully compiled the kernel branch of the rtl8723au_bt repo on Raspbian 4.1.12-v7+

The driver seems to be installed, as I can see the bluetooth device. However running hcitool scan returns no devices found. When I instead use a different USB bluetooth dongle, it does find the other device (my phone).

I can see the device with hcitool dev, and I get the following information with hciconfig -a:

hci0: Type: BR/EDR Bus: USB
BD Address: 5C:F3:70:1F:9B:23 ACL MTU: 820:8 SCO MTU: 255:16
UP RUNNING PSCAN ISCAN
RX bytes:618 acl:0 sco:0 events:37 errors:0
TX bytes:426 acl:0 sco:0 commands:35 errors:0
Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'RTK_BT_4.0'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.0 (0x6) Revision: 0xb
LMP Version: 4.0 (0x6) Subversion: 0x8723
Manufacturer: Realtek Semiconductor Corporation (93)

The dmesg | grep -i bluetooth command returns this:

[ 14.234287] Bluetooth: Core ver 2.20
[ 14.234449] Bluetooth: HCI device and connection manager initialized
[ 14.234482] Bluetooth: HCI socket layer initialized
[ 14.234501] Bluetooth: L2CAP socket layer initialized
[ 14.234543] Bluetooth: SCO socket layer initialized
[ 14.287272] Bluetooth: RFCOMM TTY layer initialized
[ 14.287319] Bluetooth: RFCOMM socket layer initialized
[ 14.287348] Bluetooth: RFCOMM ver 1.11
[ 14.312958] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.313061] Bluetooth: BNEP filters: protocol multicast
[ 14.313097] Bluetooth: BNEP socket layer initialized

Running hcidump --raw when scanning shows no other devices:

HCI sniffer - Bluetooth packet analyzer ver 5.23
device: hci0 snap_len: 1500 filter: 0xffffffff
< 01 01 04 05 33 8B 9E 08 00

04 0F 04 00 02 01 04
04 01 01 00

I'm probably missing something obvious, any help would be much appreciated.

Some other data that may be of use:

lsmod | grep btusb

btusb 24309 0
btbcm 5128 1 btusb
btintel 2314 1 btusb
bluetooth 327465 26 bnep,btbcm,btusb,rfcomm,btintel

lsusb

Bus 001 Device 008: ID 0bda:b720 Realtek Semiconductor Corp.

Hello

I successed porting rtl8723bu bluetooth driver on Beaglebone black with kernel version 3.13.6.

And this time I used kernel branch.

But can't compile bluetooth driver on kernel version 3.8.13 with kernel branch.

Without kernel version up, Are there any method to porting bluetooth driver on kernel version 3.8.13?

I've been using the rtl8723au_bt/kernel driver while hacking on a Bluetooth LE application.

I've noticed that hci_read_rssi always gives "-90 dB" as the RSSI using the rtl8723au adapter. Wireshark's packet dissection shows something like this for every response:

No.     Time               Source                Destination           Protocol Length Info
     29 20:28:31.416504000 controller            host                  HCI_EVT  10     Rcvd Command Complete (Read RSSI)

Frame 29: 10 bytes on wire (80 bits), 10 bytes captured (80 bits) on interface 0
Bluetooth HCI H4
    [Direction: Rcvd (0x01)]
    HCI Packet Type: HCI Event (0x04)
Bluetooth HCI Event - Command Complete
    Event Code: Command Complete (0x0e)
    Parameter Total Length: 7
    Number of Allowed Command Packets: 2
    Command Opcode: Read RSSI (0x1405)
        0001 01.. .... .... = Opcode Group Field: Status Parameters (0x0005)
        .... ..00 0000 0101 = Opcode Command Field: Read RSSI (0x0005)
    Status: Success (0x00)
    Connection Handle: 0x0010
    RSSI (dB): -90

At first I thought the rtl8723au firmware must just not be able to measure RSSI, but then I noticed that the LE advertising packets show a fluctuating range of RSSI values:

No.     Time               Source                Destination           Protocol Length Info
   1284 20:54:04.689747000 controller            host                  HCI_EVT  69     Rcvd LE Meta (LE Advertising Report)

Frame 1284: 69 bytes on wire (552 bits), 69 bytes captured (552 bits) on interface 0
Bluetooth Linux Monitor Transport
    [Adapter ID: 0]
    [Opcode: HCI Event Packet (0x0003)]
Bluetooth HCI Event - LE Meta
    Event Code: LE Meta (0x3e)
    Parameter Total Length: 67
    Sub Event: LE Advertising Report (0x02)
    Num Reports: 2
    Event Type: Connectable Unidirected Advertising (0x00)
    Peer Address Type: Random Device Address (0x01)
    BD_ADDR: TomtomSo_17:62:b1 (e4:04:39:17:62:b1)
    Data Length: 29
    Advertising Data
    RSSI (dB): -74
    Event Type: Scan Response (0x04)
    Peer Address Type: Random Device Address (0x01)
    BD_ADDR: TomtomSo_17:62:b1 (e4:04:39:17:62:b1)
    Data Length: 16
    Advertising Data
    RSSI (dB): -60

For comparison, I also tried a CSR8510 Bluetooth 4.0 dongle, and it does not have this deficiency (hci_read_rssi gives a range of values).

Kernel version 3.0.35
WiFi part of device is working properly and stable.
actually my 0x8723 bluetooth is working , but tricky.
if just insmod compiled from master repository driver , the device is appearing in hcitool dev, but could not see any device in hcitool scan.

So, I switched branch to 'new' and compiled driver from 'Linux_BT_USB_2.11.20140423_8723BE' folder, then insmod it and received:

[ 885.951900] rtk_btusb: download_data done
[ 885.952264] fsl-ehci fsl-ehci.1: reused qh e45d1600 schedule
[ 885.952291] usb 2-1: link qh1-0001/e45d1600 start 0 [1/0 us]
[ 885.953844] usb 2-1: unlink qh1-0001/e45d1600 start 0 [1/0 us]
[ 885.953882] rtk_btusb: check_fw_version : read_ver_rsp->lmp_subver = 0x9f73
[ 885.953901] rtk_btusb: check_fw_version : patch_entry->lmp_sub = 0x8723
[ 885.953926] rtk_btusb: Rtk patch end 0
[ 885.953989] fsl-ehci fsl-ehci.1: reused qh e45d1600 schedule
[ 885.954012] usb 2-1: link qh1-0001/e45d1600 start 0 [1/0 us]
[ 885.954316] rtk_btusb: btusb_open end pm_usage_cnt(0x0)
[ 886.952479] hci_cmd_timer: hci0 command tx timeout
[ 887.962477] hci_cmd_timer: hci0 command tx timeout
[ 888.972483] hci_cmd_timer: hci0 command tx timeout
[ 889.982478] hci_cmd_timer: hci0 command tx timeout
[ 890.992479] hci_cmd_timer: hci0 command tx timeout
[ 892.002480] hci_cmd_timer: hci0 command tx timeout
[ 893.012478] hci_cmd_timer: hci0 command tx timeout
[ 894.022479] hci_cmd_timer: hci0 command tx timeout
[ 895.032478] hci_cmd_timer: hci0 command tx timeout
[ 895.952509] rtk_btusb: btusb_flush add delay
[ 895.962547] rtk_btusb: btusb_close
[ 895.972851] usb 2-1: unlink qh1-0001/e45d1600 start 0 [1/0 us]
[ 896.042460] hci_cmd_timer: hci0 command tx timeout

after I did rmmod this driver and immediately insmod first one driver. And this is the only way after my device is starting to discover BT devices. Driver from "master" branch is loading '8723a.bin' firmware, and driver form "new" branch is loading "rtl8723b_fw".

I have msi ms-16gp laptop pc and realtek wifi-bluetooth combo card. My problem is bluetooth couldn't work. Last time I complied branch :kernel

lsusb
Bus 002 Device 002: ID 13d3:3394 IMC Networks Bluetooth`
```

```
lspci
01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723AE PCIe Wireless Network Adapter 
```
```
dmesg
[ 1727.543496] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=1200
[ 1727.543504] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723a_fw.bin
[ 1992.416036] usb 2-2: reset full-speed USB device number 2 using ohci-pci
[ 1994.084086] Bluetooth: hci0 command 0x2005 tx timeout
[ 1996.099967] Bluetooth: hci0 command 0x200b tx timeout
[ 1998.115928] Bluetooth: hci0 command 0x200c tx timeout
[ 2006.083701] Bluetooth: hci0 command 0x2005 tx timeout
[ 2008.101116] Bluetooth: hci0 command 0x200b tx timeout
[ 2010.115687] Bluetooth: hci0 command 0x200c tx timeout
[ 2018.782952] usbcore: deregistering interface driver btusb
[ 2029.999422] usbcore: registered new interface driver btusb
[ 2030.870472] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=1200
[ 2030.870480] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723a_fw.bin
[ 2042.415078] usb 2-2: reset full-speed USB device number 2 using ohci-pci
[ 2044.098990] Bluetooth: hci0 command 0x2005 tx timeout
[ 2046.114980] Bluetooth: hci0 command 0x200b tx timeout
[ 2048.130932] Bluetooth: hci0 command 0x200c tx timeout
[ 2056.098846] Bluetooth: hci0 command 0x2005 tx timeout
[ 2058.114712] Bluetooth: hci0 command 0x200b tx timeout
[ 2060.130777] Bluetooth: hci0 command 0x200c tx timeout
[ 3735.546801] usbcore: deregistering interface driver btusb
[ 3739.035869] usbcore: registered new interface driver btusb
[ 3739.906078] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=1200
[ 3739.906086] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723a_fw.bin
[ 3762.375264] usb 2-2: reset full-speed USB device number 2 using ohci-pci
[ 3764.063188] Bluetooth: hci0 command 0x2005 tx timeout
[ 3766.075123] Bluetooth: hci0 command 0x200b tx timeout
[ 3768.091140] Bluetooth: hci0 command 0x200c tx timeout
[ 3776.058992] Bluetooth: hci0 command 0x2005 tx timeout
[ 3778.074906] Bluetooth: hci0 command 0x200b tx timeout
[ 3780.090873] Bluetooth: hci0 command 0x200c tx timeout
[ 3788.058723] Bluetooth: hci0 command 0x2005 tx timeout
[ 3790.074733] Bluetooth: hci0 command 0x200b tx timeout
[ 3792.090625] Bluetooth: hci0 command 0x200c tx timeout
[ 4620.252471] usbcore: deregistering interface driver btusb
[ 4646.982860] usbcore: registered new interface driver btusb
[ 4647.856172] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=1200
[ 4647.856181] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723a_fw.bin
[ 4677.096344] usb 2-2: reset full-speed USB device number 2 using ohci-pci
[ 4678.792212] Bluetooth: hci0 command 0x0c1a tx timeout
```
if you need anything ?

Hello,

The driver is installed, I can see the bluetooth device. However running hcitool scan returns no devices found, the same for bluetoothctl scan on.
hciconfig is up and systemctl is started. Do you know how I can make it working with this linux kernel 4.11.6 ?
Thanks for your help,

Jonathan

On RTL8723BE (13d3:3410 ) Mini PCIe (Brix N2807) BT works great with the new branch, but stops connecting to devices if wifi is connected to a hotspot. btcoexist is loaded.

Will give details later on.

Hello,

I use this driver on Kubuntu 16.04 with kernel 4.4. Whenever I connect to a WiFi, I see it twice in the available networks. Once with an ID starting wlp0... behind it and second time with wlx8c...

Why do I see the nets twice? Usually the one starting with wlp0 is more stable but both of them have tendency to stop transmitting data and after a few minutes start working correctly again.

Did I do anything wrong? What could be causing this problem?

Hi, I was just trying to get the bluetooth working with my annoying rtl8723be hardware, but it won't compile because hci_recv_fragment was removed.

e.g.
#16

Of course it's not meant for my hardware (seems like nothing is), but I thought i'd let you know.

I have a problem with establishment A2DP sink Bluetooth connection. I have Allwinner A13 development board and Realtek RTL8723AS-VAU Wifi-bluetooth module with installed Linux kernel 3.4.103, bluez 5.28, PulseAudio 5.0. Sometimes smartphone can't connect with the board, hcidump not show any packet exchange and bluetooth driver does not display the btusb_notify message (rtk_btusb: btusb_notify : hci0 evt 1). Sometimes smartphone is paired with development board and in general everything is all right with the connection on A2DP. But at times after disconnection it is hard to reconnect again. Have a look at the process of communication with the use of hcidump:

HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 2
status 0x00 bdaddr 04:5A:95:E9:ED:1F
ACL data: handle 7 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 25 scid 0x0041
HCI Event: Encrypt Change (0x08) plen 4
status 0x00 handle 7 encrypt 0x01
< ACL data: handle 7 flags 0x00 dlen 16
L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0041 result 3 status 0
Connection refused - security block
HCI Event: Number of Completed Packets (0x13) plen 5
handle 7 packets 1
ACL data: handle 7 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 7 flags 0x00 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
HCI Event: Number of Completed Packets (0x13) plen 5
handle 7 packets 1
HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 7 reason 0x13
Reason: Remote User Terminated Connection
HCI Event: Number of Completed Packets (0x13) plen 5
handle 7 packets 0

So, there is no connection establishment because of Connection refused - security block. Have somebody ever come across such a problem and can recommend me how to solve it? Thank you beforehand for your help.

I am using Ubuntu 15.04. I have tried Mainline kernels 4.0 through 4.2 RC4 and with 4.1 and 4.2 BT is working out-of-the-box but I am getting kernel panics at seemingly random intervals when my BT mouse is turned on.

With kernel 4.0 I compiled wifi (rtlwifi_new-master) and BT (rtl8723au_bt-kernel) drivers and everything worked fine.

Compiling BT drivers on kernel 4.2 did not help, but as I understand, they are already included since this version. Compiling the wifi drivers failed on 4.2.

Any tips on how to debug the problem?

Hello, I am using Fedora 18, I build the module with every new kernel released and I got no luck with any of them.
Module gets loaded, but bluetooth still not working.

[root@yoda ~]# cat /etc/redhat-release
Fedora release 18 (Spherical Cow)
[root@yoda ~]#
[root@yoda ~]# lsmod |grep -i 8723
8723au 832171 0
[root@yoda ~]# uname -r
3.9.4-200.fc18.x86_64
[root@yoda ~]#
[root@yoda rtl8723au_bt]# lsmod |grep -i bt
ebtable_nat 12807 0
ebtable_filter 12827 0
ebtables 30757 2 ebtable_nat,ebtable_filter
rtk_btusb 22936 0
bluetooth 360184 9 bnep,rtk_btusb

I am sorry if this is already known issue, but I couldn't find anywhere info about this.
Please help me to troubleshoot it.

Thank you.

Bluetooth driver loads and I can successfully pair a device. However using Bluetooth comes at the expense of WIFI connectivity.

Performing an hcitool scan while pinging and downloading a large file I received WIFI errors in /var/log messages. Ping displayed slow responses during this time and my download stopped. I also found that while my iPhone was performing device discovery, even if it wasn't paired with my laptop, WIFI would drop.

hcitool scan
/var/log messages:
May 16 12:35:49 tomcat kernel: [ 5210.809934] RTL8723AU: rtw_sctx_wait timeout
May 16 12:35:50 tomcat kernel: [ 5211.810515] RTL8723AU: rtw_sctx_wait timeout
May 16 12:35:51 tomcat kernel: [ 5212.811316] RTL8723AU: rtw_sctx_wait timeout
May 16 12:35:52 tomcat kernel: [ 5213.312163] RTL8723AU: ERROR issue_nulldata, FAIL!, try_cnt =3, wait_ms =500
May 16 12:35:52 tomcat kernel: [ 5213.312363] RTL8723AU: rtw_ack_tx_done ack_tx not set
May 16 12:35:52 tomcat kernel: [ 5213.318658] RTL8723AU: rtw_ack_tx_done ack_tx not set
May 16 12:35:52 tomcat kernel: [ 5213.319317] RTL8723AU: rtw_ack_tx_done ack_tx not set
May 16 12:35:53 tomcat kernel: [ 5215.169193] RTL8723AU: OnAction_back
May 16 12:35:53 tomcat kernel: [ 5215.169232] RTL8723AU: OnAction_back, action =0
May 16 12:35:53 tomcat kernel: [ 5215.169241] RTL8723AU: issue_action_BA, category =3, action =1, status =0
May 16 12:35:53 tomcat kernel: [ 5215.218514] RTL8723AU: rtw_sctx_wait timeout
May 16 12:35:54 tomcat kernel: [ 5216.219251] RTL8723AU: rtw_sctx_wait timeout
May 16 12:35:55 tomcat kernel: [ 5217.219951] RTL8723AU: rtw_sctx_wait timeout
May 16 12:35:56 tomcat kernel: [ 5217.720657] RTL8723AU: ERROR issue_nulldata, FAIL!, try_cnt =3, wait_ms =500
MayMay 16 12:35:49 tomcat kernel: [ 5210.809934] RTL8723AU: rtw_sctx_wait timeout
May 16 12:35:50 tomcat kernel: [ 5211.810515] RTL8723AU: rtw_sctx_wait timeout
May 16 12:35:51 tomcat kernel: [ 5212.811316] RTL8723AU: rtw_sctx_wait timeout
May 16 12:35:52 tomcat kernel: [ 5213.312163] RTL8723AU: ERROR issue_nulldata, FAIL!, try_cnt =3, wait_ms =500
May 16 12:35:52 tomcat kernel: [ 5213.312363] RTL8723AU: rtw_ack_tx_done ack_tx not set
May 16 12:35:52 tomcat kernel: [ 5213.318658] RTL8723AU: rtw_ack_tx_done ack_tx not set
May 16 12:35:52 tomcat kernel: [ 5213.319317] RTL8723AU: rtw_ack_tx_done ack_tx not set
May 16 12:35:53 tomcat kernel: [ 5215.169193] RTL8723AU: OnAction_back
May 16 12:35:53 tomcat kernel: [ 5215.169232] RTL8723AU: OnAction_back, action =0
May 16 12:35:53 tomcat kernel: [ 5215.169241] RTL8723AU: issue_action_BA, category =3, action =1, status =0
May 16 12:35:53 tomcat kernel: [ 5215.218514] RTL8723AU: rtw_sctx_wait timeout
May 16 12:35:54 tomcat kernel: [ 5216.219251] RTL8723AU: rtw_sctx_wait timeout
May 16 12:35:55 tomcat kernel: [ 5217.219951] RTL8723AU: rtw_sctx_wait timeout
May 16 12:35:56 tomcat kernel: [ 5217.720657] RTL8723AU: ERROR issue_nulldata, FAIL!, try_cnt =3, wait_ms =500
May 16 12:35:56 tomcat kernel: [ 5217.721353] RTL8723AU: survey done event(3)
May 16 12:35:56 tomcat kernel: [ 5217.721461] RTL8723AU: rtw_ack_tx_done ack_tx not set
May 16 12:35:56 tomcat kernel: [ 5217.734394] RTL8723AU: rtw_ack_tx_done ack_tx not set
May 16 12:35:56 tomcat kernel: [ 5217.735460] RTL8723AU: rtw_ack_tx_done ack_tx not set
May 16 12:36:34 tomcat kernel: [ 5255.722141] UpdateHalRAMask8192CUsb => mac_id:0, networkType:0x0b, mask:0x000fffff
May 16 12:36:34 tomcat kernel: [ 5255.722141] ==> rssi_level:3, rate_bitmap:0x000ff005
May 16 12:37:04 tomcat avahi-daemon[492]: Registering new address record for fe80::2216:d8ff:febe:2ef on enp0s26u1u4i2..
May 16 12:37:06 tomcat kernel: [ 5287.775484] UpdateHalRAMask8192CUsb => mac_id:0, networkType:0x0b, mask:0x000fffff
May 16 12:37:06 tomcat kernel: [ 5287.775484] ==> rssi_level:2, rate_bitmap:0x000ff000
May 16 12:37:08 tomcat avahi-daemon[492]: Withdrawing address record for fe80::2216:d8ff:febe:2ef on enp0s26u1u4i2. 16 12:35:56 tomcat kernel: [ 5217.721353] RTL8723AU: survey done event(3)
May 16 12:35:56 tomcat kernel: [ 5217.721461] RTL8723AU: rtw_ack_tx_done ack_tx not set
May 16 12:35:56 tomcat kernel: [ 5217.734394] RTL8723AU: rtw_ack_tx_done ack_tx not set
May 16 12:35:56 tomcat kernel: [ 5217.735460] RTL8723AU: rtw_ack_tx_done ack_tx not set
May 16 12:36:34 tomcat kernel: [ 5255.722141] UpdateHalRAMask8192CUsb => mac_id:0, networkType:0x0b, mask:0x000fffff
May 16 12:36:34 tomcat kernel: [ 5255.722141] ==> rssi_level:3, rate_bitmap:0x000ff005
May 16 12:37:04 tomcat avahi-daemon[492]: Registering new address record for fe80::2216:d8ff:febe:2ef on enp0s26u1u4i2..
May 16 12:37:06 tomcat kernel: [ 5287.775484] UpdateHalRAMask8192CUsb => mac_id:0, networkType:0x0b, mask:0x000fffff
May 16 12:37:06 tomcat kernel: [ 5287.775484] ==> rssi_level:2, rate_bitmap:0x000ff000
May 16 12:37:08 tomcat avahi-daemon[492]: Withdrawing address record for fe80::2216:d8ff:febe:2ef on enp0s26u1u4i2.

I just found on the Asus F200MA an atheros Wifi card with an IMC networks bluetooth part integrated.

I've used the "new" branch, but it gets usb transmit error.

Shall we contact "IMC network" ?

This worked well before 3.13.0 now it doesn't work. Would like to see it fixed. I will submit any info you request.

email: imese -at- bellsouth .net

Thanks
Gene

Summary
I'm able to build the kernel branch on a raspberry pi b+ (jessie), install the drivers, view the devices and start an LE scan. However, the LE scan only returns 1 result for the rtl8723bu device, whereas it returns dozens of results for a CSR bluetooth device.

Hardware summary

pi@raspberrypi ~/rtl8723au_bt $ uname -a
Linux raspberrypi 4.1.7+ #817 PREEMPT Sat Sep 19 15:25:36 BST 2015 armv6l GNU/Linux
pi@raspberrypi ~/rtl8723au_bt $ lsusb
Bus 001 Device 008: ID 0bda:b720 Realtek Semiconductor Corp.
Bus 001 Device 005: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Building the drivers

pi@raspberrypi ~/rtl8723au_bt $ date
Mon Nov 16 14:26:09 UTC 2015
pi@raspberrypi ~/rtl8723au_bt $ git pull
Already up-to-date.
pi@raspberrypi ~/rtl8723au_bt $ git status
On branch kernel
Your branch is up-to-date with 'origin/kernel'.
nothing to commit, working directory clean
pi@raspberrypi ~/rtl8723au_bt $
pi@raspberrypi ~/rtl8723au_bt $ make clean
rm -rf *.o *.mod.c *.mod.o *.ko *.symvers *.order *.a
pi@raspberrypi ~/rtl8723au_bt $
pi@raspberrypi ~/rtl8723au_bt $ make
make -C /lib/modules/4.1.7+/build M=/home/pi/rtl8723au_bt modules
make[1]: Entering directory '/home/pi/linux-59e76bb7e2936acd74938bb385f0884e34b91d72'
  CC [M]  /home/pi/rtl8723au_bt/btusb.o
  CC [M]  /home/pi/rtl8723au_bt/btrtl.o
  CC [M]  /home/pi/rtl8723au_bt/btintel.o
  CC [M]  /home/pi/rtl8723au_bt/btbcm.o
  Building modules, stage 2.
  MODPOST 4 modules
  CC      /home/pi/rtl8723au_bt/btbcm.mod.o
  LD [M]  /home/pi/rtl8723au_bt/btbcm.ko
  CC      /home/pi/rtl8723au_bt/btintel.mod.o
  LD [M]  /home/pi/rtl8723au_bt/btintel.ko
  CC      /home/pi/rtl8723au_bt/btrtl.mod.o
  LD [M]  /home/pi/rtl8723au_bt/btrtl.ko
  CC      /home/pi/rtl8723au_bt/btusb.mod.o
  LD [M]  /home/pi/rtl8723au_bt/btusb.ko
make[1]: Leaving directory '/home/pi/linux-59e76bb7e2936acd74938bb385f0884e34b91d72'
pi@raspberrypi ~/rtl8723au_bt $
pi@raspberrypi ~/rtl8723au_bt $ sudo make install
depmod -a /lib/modules/4.1.7+
installed revised btusb
pi@raspberrypi ~/rtl8723au_bt $

Installing drivers

pi@raspberrypi ~/rtl8723au_bt $ sudo modprobe -rv btusb
rmmod btusb
rmmod btintel
rmmod btbcm
pi@raspberrypi ~/rtl8723au_bt $
pi@raspberrypi ~/rtl8723au_bt $ sudo modprobe -v btusb
insmod /lib/modules/4.1.7+/kernel/drivers/bluetooth/btintel.ko
insmod /lib/modules/4.1.7+/kernel/drivers/bluetooth/btbcm.ko
insmod /lib/modules/4.1.7+/kernel/drivers/bluetooth/btusb.ko
pi@raspberrypi ~/rtl8723au_bt $
pi@raspberrypi ~/rtl8723au_bt $ dmesg | tail
[37141.874215] Bluetooth: hci0 urb d6b08600 failed to resubmit (2)
[37145.824820] usbcore: registered new interface driver btusb
[37579.022835] usbcore: deregistering interface driver btusb
[37579.023067] Bluetooth: hci1 urb d6b08600 failed to resubmit (2)
[37579.023164] Bluetooth: hci1 urb d6b08180 failed to resubmit (2)
[37579.023211] Bluetooth: hci1 urb d6b08500 failed to resubmit (2)
[37579.040417] Bluetooth: hci0 urb d6b08980 failed to resubmit (2)
[37579.040488] Bluetooth: hci0 urb d6b08f00 failed to resubmit (2)
[37579.040531] Bluetooth: hci0 urb d6b08e00 failed to resubmit (2)
[37583.504172] usbcore: registered new interface driver btusb
pi@raspberrypi ~/rtl8723au_bt $

Device details via bluez post driver install

pi@raspberrypi ~/rtl8723au_bt $ hciconfig -a
hci1: Type: BR/EDR  Bus: USB
   BD Address: 5C:F3:70:24:3E:BC  ACL MTU: 820:8  SCO MTU: 255:16
   UP RUNNING
   RX bytes:610 acl:0 sco:0 events:36 errors:0
   TX bytes:942 acl:0 sco:0 commands:36 errors:0
   Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
   Link policy: RSWITCH HOLD SNIFF PARK
   Link mode: SLAVE ACCEPT
   Name: 'raspberrypi'
   Class: 0x000000
   Service Classes: Unspecified
   Device Class: Miscellaneous,
   HCI Version: 4.0 (0x6)  Revision: 0xe2f
   LMP Version: 4.0 (0x6)  Subversion: 0x9f73
   Manufacturer: Realtek Semiconductor Corporation (93)

hci0: Type: BR/EDR  Bus: USB
   BD Address: 00:15:83:D1:06:D1  ACL MTU: 310:10  SCO MTU: 64:8
   UP RUNNING
   RX bytes:610 acl:0 sco:0 events:36 errors:0
   TX bytes:942 acl:0 sco:0 commands:36 errors:0
   Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
   Link policy: RSWITCH HOLD SNIFF PARK
   Link mode: SLAVE ACCEPT
   Name: 'raspberrypi #1'
   Class: 0x000000
   Service Classes: Unspecified
   Device Class: Miscellaneous,
   HCI Version: 4.0 (0x6)  Revision: 0x22bb
   LMP Version: 4.0 (0x6)  Subversion: 0x22bb
   Manufacturer: Cambridge Silicon Radio (10)

LEScan attempt for rtl8723bu device returns one result and stops

pi@raspberrypi ~/rtl8723au_bt $ cat /proc/uptime
37662.55 35221.92
pi@raspberrypi ~/rtl8723au_bt $ sudo hcitool -i hci1 lescan
LE Scan ...
E2:72:03:D3:3B:B7 (unknown)
^Cpi@raspberrypi ~/rtl8723au_bt $ cat /proc/uptime
37684.37 35243.46

LEScan attempt for CSR bluetooth device returns results quickly and continues forever

pi@raspberrypi ~/rtl8723au_bt $ cat /proc/uptime
37684.37 35243.46
pi@raspberrypi ~/rtl8723au_bt $
pi@raspberrypi ~/rtl8723au_bt $ sudo hcitool -i hci0 lescan
LE Scan ...
7C:D1:C3:3B:6A:17 (unknown)
E2:72:03:D3:3B:B7 (unknown)
E2:72:03:D3:3B:B7 estimote
7C:D1:C3:3B:6A:17 (unknown)
7C:D1:C3:3B:6A:17 (unknown)
7C:D1:C3:3B:6A:17 (unknown)
7C:D1:C3:3B:6A:17 (unknown)
7C:D1:C3:3B:6A:17 (unknown)
7C:D1:C3:3B:6A:17 (unknown)
7C:D1:C3:3B:6A:17 (unknown)
E9:14:2B:53:67:5B (unknown)
E9:14:2B:53:67:5B estimote
7C:D1:C3:3B:6A:17 (unknown)
7C:D1:C3:3B:6A:17 (unknown)
7C:D1:C3:3B:6A:17 (unknown)
7C:D1:C3:3B:6A:17 (unknown)
^Cpi@raspberrypi ~/rtl8723au_bt $ cat /proc/uptime
37693.06 35251.87
pi@raspberrypi ~/rtl8723au_bt $

I tried all the other branches, but the kernel branch had the best results. I don't see any errors. Not sure what's going on.

I'm using this with my Lenovo Yoga 13 - works fine until I did an update today to 3.13.0-34 - and my bluetooth keyboard/mouse no longer works. I run Ubuntu. Please help! :)

I got the following error during compile (On 3.13 and 3.17 kernel). Related to #16 ?
If i remove the "static" from the hci_recv_fragment (in btusb.c) proc it compile as intended.... Strange as the rtk_btusb.c has the same static proc defined (from Troy-san repo) and i got not this error (I have almost no knowledge with C).

make -C /lib/modules/3.13.0-44-generic/build M=/home/pierre/git/rtl8723au_bt modules
make[1]: Entering directory `/usr/src/linux-headers-3.13.0-44-generic'
CC [M] /home/pierre/git/rtl8723au_bt/btusb.o
/home/pierre/git/rtl8723au_bt/btusb.c:215:12: error: static declaration of ‘hci_recv_fragment’ follows non-static declaration
static int hci_recv_fragment(struct hci_dev *hdev, int type, void *data, int count)
^
In file included from /home/pierre/git/rtl8723au_bt/btusb.h:39:0,
from /home/pierre/git/rtl8723au_bt/btusb.c:34:
include/net/bluetooth/hci_core.h:769:5: note: previous declaration of ‘hci_recv_fragment’ was here
int hci_recv_fragment(struct hci_dev *hdev, int type, void *data, int count);

I'm trying to run some code that makes Bluetooth LE connections but it seems to be having issues on this hardware. It tries to make the connection but fails with a UNKNOWN_CONNECTION_IDENTIFIER. Each time it tries to make the connection I see this in the syslog:

rtk_btusb: btusb_notify : hci0 evt 1
rtk_btusb: btusb_notify : hci0 evt 2

I tried wading through the code, but I couldn't figure out where that evt value was coming from in rtk_btusb.c. It seems to just be indicating a connection attempt and then a disconnect.

Surprisingly, the gatttool seems to make connections fine. This is surprising to me because the other code I'm running is patterned after it. However, my other code is also making network connections at the same time.

Any suggestions on trying to debug this?

Hi, lwfinger

First i appreciate your work for the realtek based wifi modules, it helped us a lot. We have some problem with the bluetooth pairing under Linux. The details are described here: http://wiki.radxa.com/Rock/Wireless#Bluetooth

We can scan other BT devices but never can pair with them. Can you point to us which is the direction to go?

I have updated my kernal and a new install of Linux Mint to once was a intel atom skylake tablet. Everything was okay until i need a mouse and keyboard witch i havr bu the bluetooth does not work. I must tell you I am a noob at this most definitely.

What ive tried doing

• Compled the Drivers
• Wifi works

• bluetooth servive does not start even with hciattach

This is a reltek bluetooth and wifi device

Cant remember the name of it rn since my tablet is wall charging.

I desperately need help and this newest kernal.

I have installed the kernel 4.2.1 on opensuse tumbleweed, and the bluetooth adapter is not found.

linux-g7rn:/home/jordi # rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

linux-g7rn:/home/jordi # lsusb
Bus 002 Device 004: ID 04f2:b322 Chicony Electronics Co., Ltd
Bus 002 Device 003: ID 2047:0855 Texas Instruments Invensense Embedded MotionApp HID Sensor
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 04f3:000a Elan Microelectronics Corp. Touchscreen
Bus 001 Device 004: ID 0bda:1724 Realtek Semiconductor Corp. RTL8723AU 802.11n WLAN Adapter
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have try to install rtl8723au_bt apparently the installation is correct but the adapter is not found.

Jordi

Hai ✋ , today I wanted to update drivers. I downloaded kernel branch, unpacked, cd and typed make.
Make made errors and output:

`https://pad.riseup.net/p/Oai25KpPZuaa'

How to fix it?

I'm running Fedora 23 kernel 4.2.8-300.fc23.x86_64

The kernel already includes the RTL8723AU driver, but lacks the Bluetooth support for my Lenovo Yoga 11s.

Can I install this driver given my current system? Are there any forks/branches aimed at a Fedora (or agnostic) Makefile?

Might be a problem on my end, but just in case, my Makefile ended up with an unterminated quote which prevented uninstall the first time.

rm -f $(DRV_DIR)/rtk_btusb.ko
    depmod -a $(MDL_DIR)
    rm -f $(FW_DIR)/rtk8723a.bin
    echo "uninstall rtk_btusb success! #here

obvs. not a huge problem. Cheers.

In kernel branch, after make,getting "successfully installed" output and reboot:

• Bluetooth doesn't seem to be working
• Other devices are not able to detect it
• My device is also not recognising any other device
• Turning on the discoverablility of bluetooth device hangs the system settings.

I am using Ubuntu 16.04 and have rtl8723be as my wireless network adapter !

I think this should be the same flag. Without CONFIG_BT_HCIBTUSB_RTL the firmware is never loaded for devices with .driver_info = BTUSB_REALTEK