Received-SPF: softfail (google.com: domain of transitioning linux-bluetooth-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Message-ID: <db5b5136-25c9-c334-e5bd-725bcbcc89a2@mindspring.com>
Date:   Tue, 17 May 2022 17:24:36 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.8.0
Subject: Re: Battery1 vs. GATT reporting
Content-Language: en-US
From:   Ed Beroset <beroset@mindspring.com>
To:     Sonny Sasaka <sonnysasaka@chromium.org>
Cc:     BlueZ <linux-bluetooth@vger.kernel.org>
References: <f46af838-8b28-79e6-5298-4458b44664ca@mindspring.com>
 <CAO271m=RNShfq+zRQjX=yK8NkUDwknr0mekJsCg_Rny3s0gUgA@mail.gmail.com>
 <72122fe6-8c8b-d26e-9c1d-75462052b503@mindspring.com>
 <CAO271m=-nxu238MKCtM-Kc1T88UOO4V2qyon0zF3ifVcThBsPA@mail.gmail.com>
 <307e7ee7-b973-4d15-03fd-31cc6087163b@mindspring.com>
 <5a1c1826-92a9-f949-9f40-473416ab82b9@mindspring.com>
In-Reply-To: <5a1c1826-92a9-f949-9f40-473416ab82b9@mindspring.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk

On 3/2/22 10:33, Ed Beroset wrote:
> On 3/1/22 11:01, Ed Beroset wrote:
>> On 3/1/22 10:43, Sonny Sasaka wrote:
>>> Hi Ed,
>>>
>>> What I do is call `gatt.select-attribute` on the characteristic called
>>> "Battery Level", but it is not shown in your case. So maybe this is
>>> the bug that you are encountering. What is the exact version of your
>>> BlueZ (commit sha if possible)? Could you also try tip of tree to see
>>> if this is already fixed?
>>
>> Hi Sonny,
>>
>> I'm sorry, I should have noted that this is with the tip of tree, 
>> commit bf09e1f048.  Thanks for your help with this!
> 
> I am trying this from a different computer today and I find that now the 
> Battery Service and Battery Level characteristic are showing up, even on 
> the same devices I was reading the other day.  Not sure what's going on, 
> but I am investigating further.  At the moment, it seems more likely 
> that the problem is either with my devices or with my software.  I just 
> wanted to report back to avoid having you all waste your time.  When I 
> figure this out, I'll send another update.  Thanks for the help so far.

OK, it's been a while, but the problem was eventually tracked not to 
BlueZ but a Qt component I was using.  Essentially, changes in BlueZ 
were being tracked by changes in Qt, but there was a problem with the Qt 
implementation starting with BlueZ version 5.55.  No change required in 
BlueZ, and already fixed in Qt, but I thought I'd circle back around and 
let you all know the resolution.

https://bugreports.qt.io/browse/QTBUG-70222

Ed