Re: Connection Rejected due to Unacceptable BD_ADDR in Chromebook smart lock feature

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Ethan,

On Thu, Feb 12, 2015, Ethan wrote:
> I met a connection rejected issue in kernel 3.10/3.14 (the kernel version
> that be used in Chrome) in Chromebook smart lock feature. From btmon, the
> connect request was initial from phone, but chrome host reject it due to "
> Unacceptable BD_ADDR". I need to start
> connection manually from Chrome (and then it's working).The full btmon log
> as below, thank.

The only way this should be possible on a clean 3.10 or 3.14 kernel
(i.e. no backported Bluetooth patches) is if you have explicitly
blacklisted the device in question. Is this a clean kernel or do you
perhaps have (incorrectly) backported patches which break the behavior?

Johan
--
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




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux