none
Bluetooth RFCOMM SerialPortService connection in Windows 10 RRS feed

  • Question

  • We successfully use Windows Sockets for Bluetooth for connection to our devices in В Windows XP SP3, Windows 7, 8, Windows 10 version 1703. However, we cannot connect to them in Windows 10  version 1809. Function “connect” from “socket” exits with error 0x0000274c "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond". Windows 10  version 1809 is able to discover our remote device, add to system, but RFCOMM SPP  connection is not set. Possible issue is that remote device based on CSR-BC417 chip does not response on request “4.10 INFORMATION REQUEST (CODE 0x0A). Extended features supported 0х0002” and connection fails. According to Bluetooth specification the device have to response on such request with “INFORMATION RESPONSE (CODE 0x0B)”, however it does not.

    Perhaps, the following is an addition to this issue:  "Bluetooth - Windows 10 revision 1803 - SPP QOS regression"

    Perhaps, the following is a confirmation of such issue: "Bluetooth Serial Port settings for Windows10 PC"

    Is there any solution to fix this issue?

    Tuesday, November 19, 2019 11:10 AM

Answers

  • You're assessment is very likely accurate. Can you reproduce this with Feedback Hub and share the link here so I can promote it? This way we can build a workaround for this device in an upcoming release.

    Tuesday, November 19, 2019 4:51 PM
  • I can confirm your assessment is accurate after reviewing the logs.We are indeed disconnecting because the CSR-BC417 is failing to respond to a required command. We'll investigate our options, as I have your email we'll follow up there until there is closure.

    Windows Logs

    3672 [2]0004.00F0::11/21/2019-05:06:52.303 [bthport][TFLAG_L2CAP][LEVEL_VERBOSE][L2capCon_ReadExtendedFeaturesSupportedCallback]: Exit
    3675 [2]0004.00F0::11/21/2019-05:06:52.303 [bthport][TFLAG_L2CAP][LEVEL_VERBOSE][L2CapInt_DestroyInfoRequestContext]L2CapInt_DestroyInfoRequestContext: L2CapInt_DestroyInfoRequestContext with Context FFFF990B66C4A3E0
    3678 [2]0004.00F0::11/21/2019-05:06:52.303 [bthport][TFLAG_L2CAP][LEVEL_WARNING][L2CapCon_DeleteConnectionEx]L2CapCon_DeleteConnectionEx: Final status is already set to 0xc00000b5(STATUS_IO_TIMEOUT)
    3684 [3]0004.00EC::11/21/2019-05:06:52.303 [rfcomm][][DBG_TDI][TdiDisconnectRequest]+TdiDisconnectRequest Abortive Internal pConn=FFFF990B56572270 STATE_CONN_CREATED
    3695 [2]0004.00F0::11/21/2019-05:06:52.303 [bthport][TFLAG_L2CAP][LEVEL_VERBOSE][L2CapCon_PurgeWrites]L2CapCon_PurgeWrites: <L2CapCon_PurgeWrites FFFF990B627C8B20

    Snoop Logs

    Packet # | Item                                                                                                               | Status                 | Payload | Time           | Application 
    20       | L2CAP Information (Extended Features Supported), Incomplete                                                        | No Response From Slave |         | 2.311 708 000  | L2CAP       
    42       | HCI Disconnect (Connection=0x0046, Reason=Remote User Terminated Connection) › Connection Terminated By Local Host | OK                     |         | 20.318 251 000 | HCI         

    Friday, November 22, 2019 4:14 PM

All replies

  • You're assessment is very likely accurate. Can you reproduce this with Feedback Hub and share the link here so I can promote it? This way we can build a workaround for this device in an upcoming release.

    Tuesday, November 19, 2019 4:51 PM
  • Thanks. I reproduced this in the Feedback Hub under the Bluetooth Serial Port Service connection heading and attached the corresponding  log (Event Viewer *.evtx) files.
    Wednesday, November 20, 2019 7:56 AM
  • Link https://aka.ms/AA6lnzt
    Wednesday, November 20, 2019 8:09 AM
  • Hi Alexey,

    I can confirm I got the feedback item you submitted. I also promoted it to a product issue, however evtx files don't contain the needed information (ever), and the Feedback Hub item does not contain repro logs (needed).

    Can you please collect the same traces manually using the instructions below and I'll attach them to the feedback item myself?

    https://github.com/Microsoft/busiotools/tree/master/bluetooth/tracing

    We need the information in the trace to identify the problematic device, to confirm your hypothesis and provide a workaround in the upcoming versions of Windows. With out this information we'll not be able to address this.

    Thanks,

    Fg

    Wednesday, November 20, 2019 3:37 PM
  • Thursday, November 21, 2019 8:46 AM
  • <I'll attach them to the feedback item myself?> Where can I send the file?

    I attached "BthTracingErr0x0274c.etl" file to the Feedback Hub created according to your instructions.

    Thursday, November 21, 2019 1:35 PM
  • Hi Alexey,

    I can't seem to find the attachment.

    My tooling says there were no more uploads or attachments (NumUserFileSent=0). I see only two ETL files from the original the submission (setup.etl, setup_inject.etl).  Is it possible provide a link here?

    Thanks,

    Fg

    Thursday, November 21, 2019 10:46 PM
  • I sent the packed file again.
    Perhaps the parcel is blocked by our firewall.
    I asked for help in SOLV.
    Friday, November 22, 2019 12:15 PM
  • I sent logs to you from personal mail

    Friday, November 22, 2019 1:25 PM
  • I can confirm your assessment is accurate after reviewing the logs.We are indeed disconnecting because the CSR-BC417 is failing to respond to a required command. We'll investigate our options, as I have your email we'll follow up there until there is closure.

    Windows Logs

    3672 [2]0004.00F0::11/21/2019-05:06:52.303 [bthport][TFLAG_L2CAP][LEVEL_VERBOSE][L2capCon_ReadExtendedFeaturesSupportedCallback]: Exit
    3675 [2]0004.00F0::11/21/2019-05:06:52.303 [bthport][TFLAG_L2CAP][LEVEL_VERBOSE][L2CapInt_DestroyInfoRequestContext]L2CapInt_DestroyInfoRequestContext: L2CapInt_DestroyInfoRequestContext with Context FFFF990B66C4A3E0
    3678 [2]0004.00F0::11/21/2019-05:06:52.303 [bthport][TFLAG_L2CAP][LEVEL_WARNING][L2CapCon_DeleteConnectionEx]L2CapCon_DeleteConnectionEx: Final status is already set to 0xc00000b5(STATUS_IO_TIMEOUT)
    3684 [3]0004.00EC::11/21/2019-05:06:52.303 [rfcomm][][DBG_TDI][TdiDisconnectRequest]+TdiDisconnectRequest Abortive Internal pConn=FFFF990B56572270 STATE_CONN_CREATED
    3695 [2]0004.00F0::11/21/2019-05:06:52.303 [bthport][TFLAG_L2CAP][LEVEL_VERBOSE][L2CapCon_PurgeWrites]L2CapCon_PurgeWrites: <L2CapCon_PurgeWrites FFFF990B627C8B20

    Snoop Logs

    Packet # | Item                                                                                                               | Status                 | Payload | Time           | Application 
    20       | L2CAP Information (Extended Features Supported), Incomplete                                                        | No Response From Slave |         | 2.311 708 000  | L2CAP       
    42       | HCI Disconnect (Connection=0x0046, Reason=Remote User Terminated Connection) › Connection Terminated By Local Host | OK                     |         | 20.318 251 000 | HCI         

    Friday, November 22, 2019 4:14 PM
  • Thanks. Hopefully a workaround will ever be.
    Monday, November 25, 2019 6:35 AM