• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 17 subscribers
  • Views 761 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

WL1837MODCOM8I: Bluetooth stops working when Wifi is enabled

Nicholas Carley
Genius 10255 points
Part Number: WL1837MODCOM8I


We are having some issues in our lab  using the WL1837MODCOM8I, where the bluetooth connection gets dropped. Also this issue we are seeing is only in one lab where we have several devices connecting to couple of access points. 

Both devices are placed right next to each other, so It’s not distance or something in between the two bluetooth devices. It seems like something related to WiFi because when we turned off WiFi, the Bluetooth starts working fine. 

We're really confused at the disabling of WIFI to resolve the issue, have you seen something like this before?\

Thanks,
Nick

WL1837MODCOM8I

  • 0
    TI__Mastermind 27080 points

    When, you say "bluetooth connection" getting dropped. Is it a profile level (HFP, A2DP or SPP) connection that is getting dropped? Can, you take BT FW logs when this is happening?

    http://www.ti.com/lit/ug/swau058d/swau058d.pdf

    Thanks

  • 0 in reply to Hari Nagalla
    TI__Genius 10255 points

    We can not modify our instruments in lab to bring up a separate line for the suggested Bluetooth logger. However I am sending you both mobile logs and instrument syslog where it clearly shows the disconnect is happening at the Bluetooth low level and not related to our application.

    Mobile:

    10-04 09:29:30.763  1620  1911 D BluetoothEventManager: onReceive :: getAction = android.bluetooth.device.action.ACL_DISCONNECTED

    10-04 09:29:30.763  1620  1911 E BluetoothEventManager: ACTION_ACL_DISCONNECTED

      

    Instrument:

    1000000958 CROND[12994]: (root) CMD (/usr/sbin/logrotate /etc/OmniBtlogrotate.conf)

    1000000958 bluetoothd[9894]: ../bluez-5.46/src/adapter.c:dev_disconnected() Device EC:10:7B:43:62:0A disconnected, reason 1 à #define MGMT_DEV_DISCONN_TIMEOUT      0x01

     

    1000000958 bluetoothd[9894]: ../bluez-5.46/src/adapter.c:adapter_remove_connection()

    1000000958 bluetoothd[9894]: ../bluez-5.46/plugins/policy.c:disconnect_cb() reason 1

    1000000958 bluetoothd[9894]: ../bluez-5.46/src/adapter.c:bonding_attempt_complete() hci0 bdaddr EC:10:7B:43:62:0A type 0 status 0xe

    1000000958 bluetoothd[9894]: ../bluez-5.46/src/device.c:device_bonding_complete() bonding (nil) status 0x0e

    1000000958 bluetoothd[9894]: ../bluez-5.46/src/device.c:device_bonding_failed() status 14

    1000000958 bluetoothd[9894]: ../bluez-5.46/src/adapter.c:resume_discovery()

  • 0 in reply to Nicholas Carley
    TI__Genius 10255 points

    Hello,

    Any thoughts on the information above?

    Thanks,
    Nick

  • 0 in reply to Nicholas Carley
    TI__Mastermind 27080 points

    Without FW logs, it is difficult to identify why the connections are failing randomly.

    Is it a Android environment or Linux? Did, you take any BT snoop logs to check if the disconnect is occurring at profile level?

    Thanks

  • 0 in reply to Hari Nagalla
    TI__Mastermind 27080 points

    Did, you get a chance to collect the logs? We, will close the ticket for now.. Please reopen when you have more logs..

    Thanks