Hi Ken, On Fri, Jan 19, 2018 at 4:09 PM, Ken Mandelberg <km@xxxxxxxxxxxxxxxx> wrote: > The Google Home speakers offer bluetooth connectivity which works with > Android phones and tablets. I don't have IOS devices but I presume they > work too. > > When I try to pair with bluez based bluetooth on Linux on my very first try > it wants a pin. I try one of the generic pins and it fails. Subsequent > pairing attempts fail but never ask for a PIN again. Weird that would mean it is using legacy pairing which is very weird considering most systems should already have 4.0 controllers, anyway we could tell more from the HCI trace if you have it. (you can use either btmon, hcidump to collect that.) > After a long timeout bluetoothctl shows > > Failed to pair: org.bluez.Error.AuthenticationCanceled > > Info shows > > Device E4:F0:42:60:85:DF > Name: Office speaker > Alias: Office speaker > Class: 0x5e0400 > Icon: audio-card > Paired: no > Trusted: no > Blocked: no > Connected: no > LegacyPairing: no > UUID: Audio Sink > (0000110b-0000-1000-8000-00805f9b34fb) At least A2DP should work with the above UUID. > UUID: A/V Remote Control Target > (0000110c-0000-1000-8000-00805f9b34fb) > UUID: A/V Remote Control > (0000110e-0000-1000-8000-00805f9b34fb) > UUID: PnP Information > (00001200-0000-1000-8000-00805f9b34fb) > UUID: Google > (0000fe9f-0000-1000-8000-00805f9b34fb) > > Any way to workaround? > > -- > To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" > in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
