Algorithm for create serial connection without rfcomm
A message that is not in the archive (sent off-list or not yet received): 000301d347db$df1dd300$9d597900$@com
A message that is not in the archive (sent off-list or not yet received): 6B2D6FC09217DA4280D35175FA16A620688418CA@msceml521-mbx.china.huawei.com
A message that is not in the archive (sent off-list or not yet received): 457BA4F48509464E9000537839AF501857261694@msceml521-mbx.china.huawei.com
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 457BA4F48509464E9000537839AF501857261990@msceml521-mbx.china.huawei.com
A message that is not in the archive (sent off-list or not yet received): 7CC793D56C5DD04ABFAFBF59EB0D4A3650F1DDAB@msceml522-mbx.china.huawei.com
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 7CC793D56C5DD04ABFAFBF59EB0D4A3650F1E01D@msceml522-mbx.china.huawei.com
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 7CC793D56C5DD04ABFAFBF59EB0D4A3650F1E6D0@msceml522-mbx.china.huawei.com
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 7CC793D56C5DD04ABFAFBF59EB0D4A3650F23FDB@msceml522-mbx.china.huawei.com
A message that is not in the archive (sent off-list or not yet received): 480C9E29A742984996B50276401889F36B33E940@msceml521-mbx.china.huawei.com
Hi all,
The rfcomm command is deprecated, what is the use of the algorithm to create serial connections?
Whether it is possible to create /dev/rfcomm not using rfcomm command through Dbus or another utility from Bluez5?
In many forums, people also ask this question, and everything is decided by adding rfcomm command.
--------------
Best regards,
Aleksandr Proklov
A message that is not in the archive (sent off-list or not yet received): CAAu3APYXpqO77M0AhAVD-EnOapXAOXsAD4e26x5ULTVCxfSreg@mail.gmail.com
Thank you Barry Byford,
Your example is more understandable for me, but I do not know python. If I understand correctly, the algorithm is as follows:
1. Connect to device (pair, connect)
2. "Release" profile
3. "RegisterProfile" with parameters. profile_path - path for new profile on Dbus?
After RegisterProfile device port /dev/rfcomm created automatic or need more operation?
4. For disconnect make RequestDisconnection
26.04.2018 21:39, Barry Byford пишет:
Quoted 39 lines
Hello Aleksandr ,
I believe that the following example in the tree is intended to serve the purpose.
https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/test/test-profileI couldn't workout the correct command line switches to get this working so I did my own experiment and came up with the follow gist for Serial Port Profile:
https://gist.github.com/ukBaz/217875c83c2535d22a16ba38fc8f2a91I hope that helps.
Regards,
BarryQuoted 19 lines · Проклов Александр Валерьевич
Hi all,
The rfcomm command is deprecated, what is the use of the algorithm to create serial connections?
Whether it is possible to create
/dev/rfcommnot using rfcomm command through Dbus or another utility from Bluez5?In many forums, people also ask this question, and everything is decided by adding rfcomm command.
--------------
Best regards,
Aleksandr Proklov
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
No, nothing is clear yet.
I use bash script for manage bluetooth, dbus-send command help me use DBus.
All programm need serial device ex: /dev/ttyS0 or for bluetooth /dev/rfcomm0 created.
I can not understand whether a device will be created, or it should be created by myself. And how to create a device with a given name ex: /dev/rfcomm0
After run ./spp-profile script will the device file be created in /dev directory?
May be 'bluetoothctl devices' not right?
In reply to a message not in the archiveHi all,
The 'devices' command 'List available devices' should show all founded devices after 'scan on' (all visible paired and unpaired devices?).
Now (git version bluetoothctl) 'devices' command show visible devices and all paired devices even if the device is turned off (not available).
May be exclude the display of paired devices that are turned off (not available)?
--------------
Best regards,
Aleksandr Proklov
Re: May be 'bluetoothctl devices' not right?
Maybe you know the standart method to check availability of the device ?
Now i use l2ping command for this.
01.08.2019 13:35, Проклов Александр Валерьевич пишет:
Quoted 14 lines
Hi all,
The 'devices' command 'List available devices' should show all founded devices after 'scan on' (all visible paired and unpaired devices?).
Now (git version bluetoothctl) 'devices' command show visible devices and all paired devices even if the device is turned off (not available).
May be exclude the display of paired devices that are turned off (not available)?
--------------
Best regards,
Aleksandr Proklov