From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Can't connect to Trust Bluetooth mouse..
Date: Mon, 08 Sep 2008 21:38:48 +0100 [thread overview]
Message-ID: <1220906328.24928.9.camel@cookie.hadess.net> (raw)
In-Reply-To: <1220904984.8005.8.camel@pancake.floe.gotdns.org>
On Mon, 2008-09-08 at 22:16 +0200, Florian Echtler wrote:
> Hello everyone,
>
> I just bought a Trust Bluetooth Mouse 15351. However, I can't connect to
> it via bluez-gnome, nor via hcitool. Here's what hcidump shows when I
> try:
<snip>
> Unfortunately, I have to admit I can't really make sense out of this,
> except that it seems that the mouse terminates the connection after the
> "Remote Name Request" command.. I have bluez 3.36 installed.
>
> Could anybody give me a hint?
In my experience with a similarly cheap Trust mouse, my advice is:
change the batteries to known working ones, check that they make contact
properly.
I'm lucky the one I bought was just a test mouse, not something I'd
really use...
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-09-08 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 20:16 [Bluez-devel] Can't connect to Trust Bluetooth mouse Florian Echtler
2008-09-08 20:38 ` Bastien Nocera [this message]
2008-09-12 7:14 ` Florian Echtler
2008-09-12 7:22 ` Florian Echtler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1220906328.24928.9.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox