From: "Robert Moskowitz" <rgm@htt-consult.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Current information on bluetooth mouse support
Date: Fri, 20 Oct 2006 13:41:54 -0400 [thread overview]
Message-ID: <45390A62.4050805@htt-consult.com> (raw)
I am trying to find information on bluetooth utilities. Everything I
have found so far is either at least a year old, and does not map to
files on my system.
Anyway, I have an HP NC4010.
I am using a Cables Unlimited dongle:
/usr/sbin/hciconfig -a
hci0: Type: USB
BD Address: 00:0D:18:01:20:B9 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:491300 acl:31961 sco:0 events:5005 errors:0
TX bytes:5297 acl:136 sco:0 commands:205 errors:0
Features: 0xff 0xff 0x8f 0xf8 0x18 0x18 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'nc4010.htt-consult.com-0'
Class: 0x120104
Service Classes: Networking, Object Transfer
Device Class: Computer, Desktop workstation
HCI Ver: 1.2 (0x2) HCI Rev: 0x512 LMP Ver: 1.2 (0x2) LMP Subver:
0x512
Manufacturer: Cambridge Silicon Radio (10)
So far I have been working with my IOgear mouse.
After much effort, I have gotten it connected and authenticated. Now if
I turn it on and press its connect button I can then do a:
hidd --search
Searching ...
Connecting to device 00:0A:94:C0:C3:19
and
hcitool info 00:0A:94:C0:C3:19
Requesting information ...
BD Address: 00:0A:94:C0:C3:19
Device Name: Bluetooth Mouse
LMP Version: 1.1 (0x1) LMP Subversion: 0x356
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2
packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
<power control> <transparent SCO>
But I loose connection with this mouse if it goes idle long enough, and
so far I have had to power it off and reconnect.
I have read messages like:
http://article.gmane.org/gmane.linux.bluez.user/6609/match=automatically+accepting+pairing+mouse
But I don't have a /etc/default/bluez-utils file to add:
HIDD_ENABLED=1
HIDD_OPTIONS="--server"
Nor can I figure out what file this now goes into.
Also how do I get the Gnome bluetooth tools working on my Centos desktop?
I still have my headphone, stereo headset, and TREO 650 to connect....
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2006-10-20 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 17:41 Robert Moskowitz [this message]
2006-10-20 18:30 ` [Bluez-users] Current information on bluetooth mouse support Andrey Jivsov
2006-10-20 20:19 ` Robert Moskowitz
2006-10-21 19:07 ` Andrey Jivsov
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=45390A62.4050805@htt-consult.com \
--to=rgm@htt-consult.com \
--cc=bluez-users@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