Return-Path: MIME-Version: 1.0 In-Reply-To: <9F3DE92910DE1D4697DD7D6F2FB4FDDC25A15D91@003FCH1MPN5-071.003f.mgd2.msft.net> References: <9F3DE92910DE1D4697DD7D6F2FB4FDDC25A15990@003FCH1MPN5-071.003f.mgd2.msft.net> <20160909104247.GA11006@t440s.lan> <9F3DE92910DE1D4697DD7D6F2FB4FDDC25A15D91@003FCH1MPN5-071.003f.mgd2.msft.net> From: Barry Byford <31baz66@gmail.com> Date: Fri, 9 Sep 2016 16:27:19 +0100 Message-ID: Subject: Re: bluez bluetooth problem To: "Montague, Jay" Cc: Johan Hedberg , "linux-bluetooth@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Jay, On 9 September 2016 at 16:14, Montague, Jay wrote: > > you might want to look into using the profile API instead (see doc/profile-api.txt and test/test-profile). > But I guess ill look into using the API profile instead. You didn't attach any documents so I guess these are available on github or something. To give the full paths... The documentation can be found at: http://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/profile-api.txt The Python example for using that API is at: http://git.kernel.org/cgit/bluetooth/bluez.git/tree/test/test-profile