>Thanks >yes it works even the latest HEAD with bluetoothctl >https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=2179f571e194c2c4635f3501d448a8a934c2c998 Yes I tested with HEAD and now it is fine. I also tested with my application and 3 different devices and it is working fine. >I was testing with >https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=f585e7ac8da3ba20fc465e3c255d2a88b7390977 >client: Fix using RegisterProfile >and this one didn’t work, so something after that fixed the problem. > On 16 Jun 2017, at 17:54, Boris Passerat de la chapelle <bpasserat@xxxxxxxx> wrote: > >> Strange > >> I compiled bluetoothctl after the patch that should fix it. > >> Did you do the steps similar to my bluetoothctl logs? > > I did not use bluetoothctl as RegisterApplication was not available yet. > In my application I have these steps : > > 0. - RegisterApplication with UUID > 1. - scan device > 2. - pair wanted device > 3. - once services resolved do some actions > 4. - device disconnect > 5. - device power up and here I have automatic reconnection > >> What device did you auto connect to ? > > I connect medical devices as : > http://www.andonline.com/medical/products/details.php?catname=Blood_Pressure&product_num=UA-651BLE > http://www.andonline.com/medical/products/details.php?catname=Scales&product_num=UC-350BLE > and 5 or 6 other devices > > From 5.41 I have to revert this commit on bluez : 89ca735e57417ec296a41d8c31d0d0d5c66ce2a9 > > > >> On 16 Jun 2017, at 09:16, Boris Passerat de la chapelle <bpasserat@xxxxxxxx> wrote: >> >> It is working on my system with a small patch on bluez 5.45. >> I got it working without patch up to bluez 5.41 . >> >> >> >> >> -----Message d'origine----- >> De : Krasi Georgiev [mailto:krasi.root@xxxxxxxxx] Envoyé : jeudi 15 >> juin 2017 22:44 À : Boris Passerat de la chapelle <bpasserat@xxxxxxxx> >> Cc : Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx>; Barry Byford >> <31baz66@xxxxxxxxx>; Bluez mailing list >> <linux-bluetooth@xxxxxxxxxxxxxxx> Objet : Re: How to use GattProfile1 >> >> Can someone else try if the auto connect works, or am I doing it incorrectly ? >> >>> On 4 Jun 2017, at 16:15, Krasi Georgiev <krasi.root@xxxxxxxxx> wrote: >>> >>> just tried with the latest master and I still can’t get it to auto >>> connect >>> >>> >>> Here is what happens so let me know if I am doing in the correct >>> sequence >>> >>> >>> [bluetooth]# devices >>> Device 34:31:11:00:CD:7A Samsung Galaxy S IV Device 04:52:C7:57:85:84 >>> Bose Mini II SoundLink Device FF:FF:50:00:53:B6 iTAG >>> >>> [bluetooth]# power on >>> Changing power on succeeded >>> [CHG] Controller B8:27:EB:D5:54:1C Powered: yes [bluetooth]# connect >>> FF:FF:50:00:53:B6 Attempting to connect to FF:FF:50:00:53:B6 [CHG] >>> Device FF:FF:50:00:53:B6 Connected: yes Connection successful [NEW] >>> Primary Service >>> /org/bluez/hci0/dev_FF_FF_50_00_53_B6/service0006 >>> 0000180f-0000-1000-8000-00805f9b34fb >>> Battery Service >>> [NEW] Characteristic >>> /org/bluez/hci0/dev_FF_FF_50_00_53_B6/service0006/char0007 >>> 00002a19-0000-1000-8000-00805f9b34fb >>> Battery Level >>> [NEW] Primary Service >>> /org/bluez/hci0/dev_FF_FF_50_00_53_B6/service0009 >>> 00001802-0000-1000-8000-00805f9b34fb >>> Immediate Alert >>> [NEW] Characteristic >>> /org/bluez/hci0/dev_FF_FF_50_00_53_B6/service0009/char000a >>> 00002a06-0000-1000-8000-00805f9b34fb >>> Alert Level >>> [NEW] Primary Service >>> /org/bluez/hci0/dev_FF_FF_50_00_53_B6/service000c >>> 0000ffe0-0000-1000-8000-00805f9b34fb >>> Unknown >>> [NEW] Characteristic >>> /org/bluez/hci0/dev_FF_FF_50_00_53_B6/service000c/char000d >>> 0000ffe1-0000-1000-8000-00805f9b34fb >>> Unknown >>> [CHG] Device FF:FF:50:00:53:B6 UUIDs: >>> 00001800-0000-1000-8000-00805f9b34fb >>> [CHG] Device FF:FF:50:00:53:B6 UUIDs: >>> 00001802-0000-1000-8000-00805f9b34fb >>> [CHG] Device FF:FF:50:00:53:B6 UUIDs: >>> 0000180f-0000-1000-8000-00805f9b34fb >>> [CHG] Device FF:FF:50:00:53:B6 UUIDs: >>> 0000ffe0-0000-1000-8000-00805f9b34fb >>> [CHG] Device FF:FF:50:00:53:B6 ServicesResolved: yes [CHG] Device >>> FF:FF:50:00:53:B6 Icon is nil [CHG] Device FF:FF:50:00:53:B6 >>> Appearance is nil >>> >>> [iTAG ]# register-application 0000180f-0000-1000-8000-00805f9b34fb >>> Application registered >>> [CHG] Device FF:FF:50:00:53:B6 ServicesResolved: no [CHG] Device >>> FF:FF:50:00:53:B6 Connected: no >>> >>> >>> Here i power cycled the iTag and waited few minutes but bluetoothctl didn’t reconnect so I did it manually. >>> >>> >>> [bluetooth]# info FF:FF:50:00:53:B6 >>> Device FF:FF:50:00:53:B6 >>> Name: iTAG >>> Alias: iTAG >>> Paired: no >>> Trusted: yes >>> Blocked: no >>> Connected: no >>> LegacyPairing: no >>> UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) >>> UUID: Immediate Alert (00001802-0000-1000-8000-00805f9b34fb) >>> UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb) >>> UUID: Unknown (0000ffe0-0000-1000-8000-00805f9b34fb) >>> [bluetooth]# connect FF:FF:50:00:53:B6 Attempting to connect to >>> FF:FF:50:00:53:B6 [CHG] Device FF:FF:50:00:53:B6 Connected: yes >>> Connection successful [CHG] Device FF:FF:50:00:53:B6 ServicesResolved: >>> yes >>> [iTAG ]# >> > ��.n��������+%������w��{.n�����{��� �^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
