Hi Florian, On Thu, Sep 1, 2022 at 11:10 AM Florian Leeber <florian@xxxxxxxxxxx> wrote: > > Am 01.09.2022 um 12:46 schrieb Bastien Nocera: > > On Wed, 2022-08-31 at 13:18 -0700, Luiz Augusto von Dentz wrote: > >> Hi Florian, > >> > >> On Wed, Aug 31, 2022 at 12:44 PM Florian Leeber <florian@xxxxxxxxxxx> > >> wrote: > >> gs as default). > > FWIW, gnome-bluetooth has its own database on top of bluez, which we > > prefer to the code in bluez. I'd be happy getting rid of it. > > > > Loads of devices that need pairing despite their class and Bluetooth > > version, and devices that need special handling like the Navman GPS > > that expects a non-numerical PIN. > > > > The database: > > https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/blob/master/lib/pin-code-database.xml > > The code to parse it: > > https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/blob/master/lib/pin.c > > Oh my, this escalated quickly ;) - tbh implementing this as a fully > fledged config-based feature might be over my head. I am not proficient > with the Bluez code at all, and my main work currently is being the OTA > release manager for Ubuntu Touch. I could only work on this with some > support to get the basics established. > > Thanks for the hint with the database, we did not know about this. Can't you solve the problem in the agent thought? Or does the current logic make the pairing fail right away? > -- Luiz Augusto von Dentz
