Hi Stefan Thanks again for following up with the bluez devs. Given the lack of an alternative to /dev/rfcommX, is it still your intention to patch bluez to "un-deprecate" rfcomm for openSUSE? Best regards Graeme On 4/1/20 11:09 pm, Stefan Seyfried wrote:
Hi Graeme.
Am 23.12.19 um 05:47 schrieb Graeme Blackman:
On 22/12/19 8:10 pm, Stefan Seyfried wrote:
I have inquired upstream about this and asked to un-deprecate rfcomm.
Let's see what comes out of this discussion. If there is no resolution, I can still patch bluez to "un-deprecate" rfcomm for openSUSE :-) Many thanks for your efforts, they are really appreciated. Un-deprecating rfcomm upstream would be such a great result for many frustrated users. I guess that this (upstream bluez un-deprecating rfcomm tool) will not happen: I have been pointed to the doc/profile-api.txt and after investigating I have been able to use it to create both a SPP server and a SPP client, using the examples fromhttps://ukbaz.github.io/howto/AppInventor.html (for the SPP server) andhttps://github.com/tonyespy/bluez5-spp-example (for both SPP server and client). It does not create /dev/rfcommX devices, though.
Best regards,
Stefan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org