Re: Two connect failed...

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

 



Thank you Marcel!

On Fri, Jan 29, 2016 at 12:07 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote:
> Hi Francois,
>
>> Reducing APP_ADV_INTERVAL to 400 (instead of 1600) makes the "LE
>> Create Connection" work every single time now.
>>
>> Hopefully with bluetooth-next update in Chrome OS
>> (https://code.google.com/p/chromium/issues/detail?id=576577#c20) and
>> especially https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=2f99536a5b34d5b0f54723067d68f6cef3f0fdc6,
>> we won't have to set a smaller Advertising Interval as it reduces
>> battery's life.
>>
>> Do you maybe have another recommendation while it reaches Stable channel?
>
> I highly doubt there is anything else that can be done. I would cherry pick that single patch and backport it into the Chrome OS kernel.
>
> Regards
>
> Marcel
>
--
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