From: Stefan Seyfried <seife@suse.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Mouse reconnect problems since version 3.12
Date: Fri, 6 Jul 2007 11:10:29 +0200 [thread overview]
Message-ID: <20070706091029.GA934@suse.de> (raw)
In-Reply-To: <1183701453.6351.107.camel@aeonflux.holtmann.net>
Hi,
On Fri, Jul 06, 2007 at 07:57:33AM +0200, Marcel Holtmann wrote:
> Hi Stefan,
> > > I need to see the hcidump output. Otherwise I can't tell anything.
> > =
> > HCI sniffer - Bluetooth packet analyzer ver 1.35
> > device: hci0 snap_len: 1028 filter: 0xffffffff
> > > ACL data: handle 6 flags 0x02 dlen 13
> > L2CAP(d): cid 0x0041 len 9 [psm 0]
> > 0000: a1 02 01 00 00 00 00 00 00 .........
> > > HCI Event: Mode Change (0x14) plen 6
> > status 0x00 handle 6 mode 0x00 interval 126
> > Mode: Active
> > > HCI Event: Mode Change (0x14) plen 6
> > status 0x00 handle 6 mode 0x02 interval 20
> > Mode: Sniff
> > =
> > up to here this was a left button press, from here on i was moving the
> > mouse around.
> =
> are you sure that the authorization agent is working. Maybe you wanna
> use adapter.SetTrusted() to make it fully trusted.
I think i already have done this (via kbluetooth). If i have no auth-agent
running, unplug and replug the dongle, then the mouse works again
immediately (after the short reconnection delay).
This is what is in my /var/lib/bluetooth:
root@strolchi:/var/lib/bluetooth# ls 00\:00\:00\:00\:00\:00/
trusts
root@strolchi:/var/lib/bluetooth# cat 00\:00\:00\:00\:00\:00/trusts
00:07:61:3F:1B:6D input
root@strolchi:/var/lib/bluetooth# ls -l 00\:50\:F2\:EA\:6B\:EF/
total 92
-rw-r--r-- 1 root root 3564 26. Jun 14:06 classes
-rw-r--r-- 1 root root 68 28. Jun 10:35 config
-rw-r--r-- 1 root root 525 4. Jul 14:08 features
-rw-r--r-- 1 root root 652 2. Jul 22:42 hidd
-rw-r--r-- 1 root root 865 2. Jul 22:42 input
-rw-r--r-- 1 root root 5502 4. Jul 18:57 lastseen
-rw-r--r-- 1 root root 798 6. Jul 10:58 lastused
-rw------- 1 root root 110 13. Feb 11:26 linkkeys
-rw-r--r-- 1 root root 388 4. Jul 14:08 manufacturers
-rw-r--r-- 1 root root 959 5. Jul 18:40 names
-rw-r--r-- 1 root root 13162 4. Jul 14:28 sdp
Thanks,
Stefan
-- =
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG N=FCrnberg)
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-07-06 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 14:11 [Bluez-devel] Mouse reconnect problems since version 3.12 Stefan Seyfried
2007-07-05 8:05 ` Marcel Holtmann
2007-07-05 15:55 ` Stefan Seyfried
2007-07-06 5:57 ` Marcel Holtmann
2007-07-06 9:10 ` Stefan Seyfried [this message]
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=20070706091029.GA934@suse.de \
--to=seife@suse.de \
--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