Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <01070184822b48a4-e211e97b-6c3b-4cd2-8f39-38ed6bb6608b-000000@eu-central-1.amazonses.com>
Date:   Wed, 16 Nov 2022 20:39:45 +0000
MIME-Version: 1.0
Subject: Re: Bluez <> Pebble smartwatch
Content-Language: de-DE
To:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc:     linux-bluetooth@vger.kernel.org
References: <010701848111d140-5dd1752f-c89a-47a1-9472-2e5a5a8a740a-000000@eu-central-1.amazonses.com>
 <CABBYNZJaS8fTuXBm7hEvA_3jYqCpcjBdHbR6f2Zz-zBZF4TEvw@mail.gmail.com>
From:   Florian Leeber <florian@ubports.com>
In-Reply-To: <CABBYNZJaS8fTuXBm7hEvA_3jYqCpcjBdHbR6f2Zz-zBZF4TEvw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Feedback-ID: 1.eu-central-1.U71sxic/3tmi0U3T+Ze2hDyqoN46zyPgdCO+zEPT6YQ=:AmazonSES
Precedence: bulk

Hey, will a btmon trace be enough? Or also Bluez daemon log?

Am 16.11.2022 um 21:36 schrieb Luiz Augusto von Dentz:
> Hi Florian,
>
> On Wed, Nov 16, 2022 at 7:38 AM Florian Leeber <florian@ubports.com> wrote:
>> Hello All,
>>
>> does anyone have any experience pairing a Pebble smartwatch with Bluez?
>> It was working kinda well in an Bluez 5.41, but now with 5.53 to which
>> we are upgrading in Ubuntu Touch the pairing process is unsucessful. As
>> I do not own the device debugging is difficult, but some users try now
>> to get a btmon trace.
> Getting the traces is essential to discover why it is failing, we also
> need the information of the kernel version as well.
>