Return-Path: Message-ID: <47AD98EF.2030706@aircable.net> Date: Sat, 09 Feb 2008 10:13:35 -0200 From: Manuel Naranjo MIME-Version: 1.0 To: BlueZ users References: <200802090347.m193lOJq023253@alumnus.caltech.edu> In-Reply-To: Subject: Re: [Bluez-users] failed PIN Code Request Reply-To: BlueZ users List-Id: BlueZ users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-users-bounces@lists.sourceforge.net Errors-To: bluez-users-bounces@lists.sourceforge.net > the other side, computer to device. I believe that's 'hcitool cc
' > then 'hcitool auth
' but my headset doesn't seem to like to operate > this way and wants to disconnect quickly due to not being used for sound. > If I'm not wrong it's not your headset the one that closes the connection, but rather the kernel. Solution: ADDR= hcitootl cc $ADDR; hcitool auth $ADDR Still not the preferred way but it works. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users