I see same problem with designer mouse when i connect it on 10718.71.0 build

Note: The Microsoft universal kb and the designer mouse work fine on 10718.63.0 build.

Seems to be a regression between 10718.63.0 and 10718.71.0 builds

10718.71.0 is a stable candidate. This looks like a stable blocker. Adding other folks to get their thoughts before we add RBS label.

Actually I am going to proceed with adding RBS label on it now. We can remove it later if its not considered RBS.

btsnoop (2).log is in raw text. Can I get the real snoop log, which I can analyze with wireshark? Just the output of "btmon -w <output>", and don't transfer it to raw text.

Joseph, do you have either of these devices?

Maybe useful info: there is one bluetooth change between the said regression window:
https://crosland.corp.google.com/log/10718.63.0..10718.71.1 (CHROMIUM: Merge eir_uuids into uuids)

We could try whether building without that CL can repro the issue.

Making this a beta blocker as well.

What device is this on? Is this only snappy or others?

We have had bad BT problems for some time, and we are already blocking MTK devices based on a BT issue, if this not across all devices please let me know ASAP, the R68 release is already late. 

Suspect CL reverted on all branches.

Re: C#6: hi, Rahul, I have a Microsoft Universal Foldable Keyboard and will have it with me to MTV. (I am departing today.)

As i check on 10718.71.2 build, I am able to pair , connect and use dell keyboard and designer mouse without any issues

pbathini@ - please check with any other keyboards and mice that you have as well.

I have also connected the Microsoft universal kb on 10718.71.2 build and it works too.

The devices ( Logitech BT mouse , Bose QC35 headphones )  working on last build work on 10718.71.2 build too.

This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone.

All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Marking fixed based on c#15. Lets reopen if the issue still repros.

[Auto-generated comment by a script] We noticed that this issue is targeted for M-68; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-68 label, otherwise remove Merge-TBD label. Thanks.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/bluez/+/7e730a02ca9e04ef673a54cf7cf0b366bf4a64b3

commit 7e730a02ca9e04ef673a54cf7cf0b366bf4a64b3
Author: Qiyu Hu <qiyuh@google.com>
Date: Wed Aug 08 01:09:06 2018

CHROMIUM: Change the semantic of UUIDs property in device

Keep the list of eir_uuids in property "UUID".
Avoid removing eir_uuids after service discovery.

So the semantic of UUIDs property in device changes in the following way:

1. Without this patch, UUIDs contains eir uuids only before service
   discovery. After service discovery, UUIDs contains service UUIDs BlueZ
   discovers.
2. With this patch, UUIDs contains eir uuids only before service
   discovery. After service discovery, UUIDs continas service UUIDs and
   eir_uuids.

BUG= chromium:853037 ,  chromium:841041 ,  chromium:870011 
TEST=Verify that the missing service UUIDs bug is no longer reproducible
     Pair and connect w/ baiscally all peripherals @pbathini can provide

Change-Id: Ifa2fcb4e074d8de10b6ed6902c36d451ebbea359
Reviewed-on: https://chromium-review.googlesource.com/1161543
Commit-Ready: Qiyu Hu <qiyuh@google.com>
Tested-by: Qiyu Hu <qiyuh@google.com>
Reviewed-by: Miao-chen Chou <mcchou@chromium.org>

[modify] https://crrev.com/7e730a02ca9e04ef673a54cf7cf0b366bf4a64b3/src/device.c
[modify] https://crrev.com/7e730a02ca9e04ef673a54cf7cf0b366bf4a64b3/doc/device-api.txt

pbathini@ - please test/verify this on a build with the above fix.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/bluez/+/7950443b86cf0ef89a2473b62206fea68df8fae3

commit 7950443b86cf0ef89a2473b62206fea68df8fae3
Author: Qiyu Hu <qiyuh@google.com>
Date: Mon Sep 10 23:09:19 2018

CHROMIUM: Change the semantic of UUIDs property in device

Keep the list of eir_uuids in property "UUID".
Avoid removing eir_uuids after service discovery.

So the semantic of UUIDs property in device changes in the following way:

1. Without this patch, UUIDs contains eir uuids only before service
   discovery. After service discovery, UUIDs contains service UUIDs BlueZ
   discovers.
2. With this patch, UUIDs contains eir uuids only before service
   discovery. After service discovery, UUIDs continas service UUIDs and
   eir_uuids.

BUG= chromium:853037 ,  chromium:841041 ,  chromium:870011 
TEST=Verify that the missing service UUIDs bug is no longer reproducible
     Pair and connect w/ baiscally all peripherals @pbathini can provide

Change-Id: Ifa2fcb4e074d8de10b6ed6902c36d451ebbea359
Reviewed-on: https://chromium-review.googlesource.com/1161543
Commit-Ready: Qiyu Hu <qiyuh@google.com>
Tested-by: Qiyu Hu <qiyuh@google.com>
Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
(cherry picked from commit 7e730a02ca9e04ef673a54cf7cf0b366bf4a64b3)
Reviewed-on: https://chromium-review.googlesource.com/1216748
Commit-Queue: Qiyu Hu <qiyuh@google.com>
Reviewed-by: Sonny Sasaka <sonnysasaka@chromium.org>

[modify] https://crrev.com/7950443b86cf0ef89a2473b62206fea68df8fae3/src/device.c
[modify] https://crrev.com/7950443b86cf0ef89a2473b62206fea68df8fae3/doc/device-api.txt