public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [Bluez-devel] Can't connect to Trust Bluetooth mouse..
@ 2008-09-08 20:16 Florian Echtler
  2008-09-08 20:38 ` Bastien Nocera
  0 siblings, 1 reply; 4+ messages in thread
From: Florian Echtler @ 2008-09-08 20:16 UTC (permalink / raw)
  To: bluez-devel

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:

hcidump -V -i hci0
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
    bdaddr 11:11:12:11:1F:06 ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 
> HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 12 bdaddr 11:11:12:11:1F:06 type ACL encrypt 0x00
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
    handle 12
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
    handle 12 policy 0x0f
    Link policy: RSWITCH HOLD SNIFF PARK 
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 12
    Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
> HCI Event: Command Complete (0x0e) plen 6
    Write Link Policy Settings (0x02|0x000d) ncmd 1
    status 0x00 handle 12
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
    bdaddr 11:11:12:11:1F:06 mode 2 clkoffset 0x0000
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 11:11:12:11:1F:06 name 'Trust  Mouse 15351'
< HCI Command: Disconnect (0x01|0x0006) plen 3
    handle 12 reason 0x13
    Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
    Disconnect (0x01|0x0006) status 0x00 ncmd 1
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x16
    Reason: Connection Terminated by Local Host

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?

Many thanks, Yours, Florian
-- 
0666 - Filemode of the Beast


-------------------------------------------------------------------------
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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-devel] Can't connect to Trust Bluetooth mouse..
  2008-09-08 20:16 [Bluez-devel] Can't connect to Trust Bluetooth mouse Florian Echtler
@ 2008-09-08 20:38 ` Bastien Nocera
  2008-09-12  7:14   ` Florian Echtler
  0 siblings, 1 reply; 4+ messages in thread
From: Bastien Nocera @ 2008-09-08 20:38 UTC (permalink / raw)
  To: BlueZ development

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-devel] Can't connect to Trust Bluetooth mouse..
  2008-09-08 20:38 ` Bastien Nocera
@ 2008-09-12  7:14   ` Florian Echtler
  2008-09-12  7:22     ` Florian Echtler
  0 siblings, 1 reply; 4+ messages in thread
From: Florian Echtler @ 2008-09-12  7:14 UTC (permalink / raw)
  To: BlueZ development


[-- Attachment #1.1: Type: text/plain, Size: 1674 bytes --]

> > 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.
> 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.
Thanks for the hint; I've used new batteries and checked the contacts.
Still, no luck. However, it looks like the problem is of a different
sort than I previously thought. IIRC connecting via hcitool isn't really
supposed to work for input devices anyway. When I try to connect via
bluetooth-applet, hcidump shows:

< HCI Command: Inquiry (0x01|0x0001) plen 5
    lap 0x9e8b33 len 8 num 0
> HCI Event: Command Status (0x0f) plen 4
    Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Inquiry Result (0x02) plen 15
    bdaddr 11:11:12:11:1F:06 mode 1 clkoffset 0x1d51 class 0x002580
> HCI Event: Inquiry Complete (0x01) plen 1
    status 0x00

And nothing else anymore, even after I click the connect button. Just an
empty window labeled "connecting to device..", but nothing else happens
(especially no bluetooth communication). In the console,
bluetooth-properties shows:

** (bluetooth-properties:7171): CRITICAL **: dbus_g_proxy_begin_call:
assertion `DBUS_IS_G_PROXY (proxy)' failed

So I'm getting suspicious that this is in fact a DBus problem.. any
ideas?

Many thanks, Yours, Florian

[-- Attachment #1.2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
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=/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-devel] Can't connect to Trust Bluetooth mouse..
  2008-09-12  7:14   ` Florian Echtler
@ 2008-09-12  7:22     ` Florian Echtler
  0 siblings, 0 replies; 4+ messages in thread
From: Florian Echtler @ 2008-09-12  7:22 UTC (permalink / raw)
  To: BlueZ development


[-- Attachment #1.1: Type: text/plain, Size: 732 bytes --]

> And nothing else anymore, even after I click the connect button. Just an
> empty window labeled "connecting to device..", but nothing else happens
> (especially no bluetooth communication). In the console,
> bluetooth-properties shows:
> 
> ** (bluetooth-properties:7171): CRITICAL **: dbus_g_proxy_begin_call:
> assertion `DBUS_IS_G_PROXY (proxy)' failed
> 
> So I'm getting suspicious that this is in fact a DBus problem.. any
> ideas?
P.S. When I try to connect from the command line (using the commands
from http://wiki.bluez.org/wiki/HOWTO/InputDevices), the connection and
the mouse work! So I'm starting to get really confused now, the problem
seems to be in bluetooth-properties itself.. ?

Yours, Florian

[-- Attachment #1.2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
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=/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-09-12  7:22 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-09-08 20:16 [Bluez-devel] Can't connect to Trust Bluetooth mouse Florian Echtler
2008-09-08 20:38 ` Bastien Nocera
2008-09-12  7:14   ` Florian Echtler
2008-09-12  7:22     ` Florian Echtler

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox