Assigned
Status Update
No update yet.
Comments
ss...@google.com
mi...@gmail.com
I've got a BLE peripheral that is capable of being connected as slave to multiple centrals and just tried what would happen if you use autoConnect parameter set to true and also have a pending connection to another device. What I expected happens:
On a Nexus 5 (that has a Broadcom Bluetooth 4.1 chip), running the latest Marshmallow update, as soon as the BLE peripheral starts an advertisement after it has connected, the previous link is dropped by the Broadcom chip. Since this goes on and on, it gets stuck in a "connect-disconnect loop". I've attached a new snoop log for this. See from packet 1865 and forward.
On an LG G3 phone (that has a Qualcomm Bluetooth 4.1 chip), running the latest Marshmallow update, as soon as the BLE peripheral starts an advertisement after it has connected, the bluetooth chip now initiates the second connection to this device, notifying the host about this, which as written above gets confused and gets stuck in a state where it will make no further connections until Bluetooth is restarted. I've attached a new snoop log for this as well. See from packet 593 and forward.
On a Nexus 5X phone (that has a Qualcomm Bluetooth 4.2 chip), no bug will be triggered and there are no problems. The reason is that since the Bluetooth 4.2 standard, some new sentences have been added: "There shall be only one connection between two LE device addresses. An initiator shall not send a connection request to an advertiser it is already connected to. If an advertiser receives a connection request from an initiator it is already connected to, it shall ignore that request." The bluetooth chip honours this and will therefore not establish a new connection, even though the peripheral advertises and its address is in the white list.
So, I really think the best fix would be to make sure that when there is a pending connection, the white list should not contain addresses to devices that already have an established connection. As newer BLE peripherals that support multiple centrals will eventually be more common on the market, I think it's good to fix this issue as soon as possible before people are stuck with non-upgradable old Marshmallow phones.
On a Nexus 5 (that has a Broadcom Bluetooth 4.1 chip), running the latest Marshmallow update, as soon as the BLE peripheral starts an advertisement after it has connected, the previous link is dropped by the Broadcom chip. Since this goes on and on, it gets stuck in a "connect-disconnect loop". I've attached a new snoop log for this. See from packet 1865 and forward.
On an LG G3 phone (that has a Qualcomm Bluetooth 4.1 chip), running the latest Marshmallow update, as soon as the BLE peripheral starts an advertisement after it has connected, the bluetooth chip now initiates the second connection to this device, notifying the host about this, which as written above gets confused and gets stuck in a state where it will make no further connections until Bluetooth is restarted. I've attached a new snoop log for this as well. See from packet 593 and forward.
On a Nexus 5X phone (that has a Qualcomm Bluetooth 4.2 chip), no bug will be triggered and there are no problems. The reason is that since the Bluetooth 4.2 standard, some new sentences have been added: "There shall be only one connection between two LE device addresses. An initiator shall not send a connection request to an advertiser it is already connected to. If an advertiser receives a connection request from an initiator it is already connected to, it shall ignore that request." The bluetooth chip honours this and will therefore not establish a new connection, even though the peripheral advertises and its address is in the white list.
So, I really think the best fix would be to make sure that when there is a pending connection, the white list should not contain addresses to devices that already have an established connection. As newer BLE peripherals that support multiple centrals will eventually be more common on the market, I think it's good to fix this issue as soon as possible before people are stuck with non-upgradable old Marshmallow phones.
Description
However, when I tried to use my phone, connected using USB to my computer, the build fails with the above error.
When I turned off Instant Run, the build works fine for the device too.