On 2 December 2015 at 09:47, Zheng, Wu wrote:
> From the log, I can’t find that the issue is related with Bluez-5.36.
>
>
With the 5.36 upgrade, bluez segfaults on startup on every qemu image that
we test on the autobuilder. It's probably related to the machines not
having any bluetooth hardware
: Zheng, Wu
Cc: OE-core
Subject: Re: [OE-core] [PATCH] bluez5:upgrade bluez5 to 5.36
On 27 November 2015 at 10:03, Wu Zheng
mailto:wu.zh...@intel.com>> wrote:
Bluez5-5.36 fixes the most part of bug.
The target areas of bug are such as PBAP, AVRCP, HoG and GATT.
It fixes a fairly important bug f
Hi Burton, Ross
Thanks.
Best Regards
Zheng Wu
From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Friday, November 27, 2015 6:03 PM
To: Zheng, Wu
Cc: OE-core
Subject: Re: [OE-core] [PATCH] bluez5:upgrade bluez5 to 5.36
On 27 November 2015 at 10:03, Wu Zheng
mailto:wu.zh...@intel.com
On 27 November 2015 at 10:03, Wu Zheng wrote:
> Bluez5-5.36 fixes the most part of bug.
> The target areas of bug are such as PBAP, AVRCP, HoG and GATT.
> It fixes a fairly important bug for the GATT D-Bus interfaces too.
> At the same time, Bluez will cache more information of remote GATT
> data
Bluez5-5.36 fixes the most part of bug.
The target areas of bug are such as PBAP, AVRCP, HoG and GATT.
It fixes a fairly important bug for the GATT D-Bus interfaces too.
At the same time, Bluez will cache more information of remote GATT
databases and thereby avoid unnecessary rediscovery of remote
