From: "Bearcat M. Sandor" <Bearcat@feline-soul.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Connecting a Logitech Mobile Traveler...progress
Date: Sat, 29 Jul 2006 15:20:25 -0600 [thread overview]
Message-ID: <200607291520.25745.Bearcat@feline-soul.com> (raw)
In-Reply-To: <200607290035.01939.Bearcat@feline-soul.com>
Well, i'm still trying to get my keyboard working.
However, i am making progress on the headset.
When i turn the headset on and hold down the powerbutton i get the flashing
red/blue light as the manual says.
As i stated below i changed the passkey in /etc/bluetooth/hcid.conf to "0000".
The manual for the headset says "The PIN/passkey is: 0000"
When i do a hidd --connect 00:0D:44:4F:37:72 or a hcitool cc 00:0D:44:4F:37:72
i see the following in hcidump now:
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: PIN Code Request (0x16) plen 6
< HCI Command: PIN Code Request Negative Reply (0x01|0x000e) plen 6
> HCI Event: Command Complete (0x0e) plen 10
> HCI Event: Connect Complete (0x03) plen 11
At the console the message "Can't get device information: Permission denied"
and kdebluetoth reports "Pairing not allowed"
That's progress, i think. I STILL am never asked for a passcode. I can
run /usr/lib/kdebluetooth/kdebluetooth manually, so i know the dialog is
operational, it just never comes up. I made a script that contains
echo "PIN:0000"
and i have tried supplying that as my pass_helper, but that is never utilized
either.
I've tried commenting out the line: #passkey "0000";
but that does not force a pin_helper to appear or be run. I have tried
entering 0000 on the keyboard but that doesn't do anything either. Do i need
to adjust something in my rfcomm.conf file? (seen here
http://www.feline-soul.com/files/bluetooth/rfcomm.conf )?
My hcid.conf file can be viewed here:
http://www.feline-soul.com/files/bluetooth/hcid.conf
Ideas?
Bearcat
On Saturday 29 July 2006 00:35 in an email titled "Re: [Bluez-users] can't
connect EPOX Keyboard BT-KB01B" Bearcat M. Sandor wrote:
>An update I just recieved my logitech headset and i'm making some headway.
>It's actually giving my some clues about the keyboard
>
>I did the following:
>
>1. in the hcid.conf file i changed the passkey to "0000"
>2. Reloaded bluez.
>3. hiconfig up and down
>4. hold power button on headset
>5. hcitool scan
>I see 00:0D:44:4F:37:72 Logitech HS03 V04
>then a hidd --connect 00:0D:44:4F:37:72 or a hcitool cc 00:0D:44:4F:37:72
>starts the connection.
>
>In hcidump i see:
>
>< HCI Command: Create Connection (0x01|0x0005) plen 13
>
>> HCI Event: Command Status (0x0f) plen 4
>> HCI Event: PIN Code Request (0x16) plen 6
>> HCI Event: Connect Complete (0x03) plen 11
>
>I am never prompted for a pin code. I even made a script which contains:
> echo "PIN:0000"
>but no pin is ever entered.
>
>Thus kdebluetooth sees the headset but it is never connected.
>
>The keyboard on the other hand is never seen at all. A hcitool scan does not
>show it, nor does it ever appear in kdebluetooth. However, the mouse is
>never seen in a scan either, yet it works perfectly and is seen in
>kdebluetooth.
>
>I'm very confused.
>
>Bearcat
>
>
>On Friday 28 July 2006 12:38 in an email titled "Re: [Bluez-users] can't
>
>connect EPOX Keyboard BT-KB01B" Bearcat M. Sandor wrote:
>>Sorry about that. I meant to say files/bluetooth on all those.
>>
>>They are here: http://www.feline-soul.com/files/bluetooth/
>>
>>Here the are inline:
>>http://www.feline-soul.net/files/bluetooth/hcid.conf:
>>#
>># HCI daemon configuration file.
>>#
>>
>># HCId options
>>options {
>> # Automatically initialize new devices
>> autoinit yes;
>>
>> # Security Manager mode
>> # none - Security manager disabled
>> # auto - Use local PIN for incoming connections
>> # user - Always ask user for a PIN
>> #
>> security user;
>>
>> # Pairing mode
>> # none - Pairing disabled
>> # multi - Allow pairing with already paired devices
>> # once - Pair once and deny successive attempts
>> pairing multi;
>>
>> # Default PIN code for incoming connections
>> passkey "BlueZ";
>>
>> # PIN helper
>> #pin_helper /usr/bin/bluepin;
>> #pin_helper /etc/bluetooth/cbpinscript;
>> pin_helper /usr/lib/kdebluetooth/kbluepin;
>>}
>>
>># Default settings for HCI devices
>>device {
>> # Local device name
>> # %d - device id
>> # %h - host name
>> name "BlueZ (%d)";
>>
>> # Local device class
>> class 0x100000;
>>
>> # Default packet type
>> #pkt_type DH1,DM1,HV1;
>>
>> # Inquiry and Page scan
>> iscan enable; pscan enable;
>>
>> # Default link mode
>> # none - no specific policy
>> # accept - always accept incoming connections
>> # master - become master on incoming connections,
>> # deny role switch on outgoing connections
>> lm accept;
>>
>> # Default link policy
>> # none - no specific policy
>> # rswitch - allow role switch
>> # hold - allow hold mode
>> # sniff - allow sniff mode
>> # park - allow park mode
>> lp rswitch,hold,sniff,park;
>>}
>>-------------------------------------------------------------------
>>http://www.feline-soul.net/files/bluetooth/hcidev_-a_output:
>>hci0: Type: USB
>> BD Address: 00:07:61:1C:9F:D3 ACL MTU: 192:8 SCO MTU: 64:8
>> UP RUNNING PSCAN ISCAN
>> RX bytes:8886937 acl:584808 sco:0 events:79865 errors:0
>> TX bytes:392377 acl:192 sco:0 commands:77281 errors:0
>> Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>> Link policy: RSWITCH HOLD SNIFF PARK
>> Link mode: SLAVE ACCEPT
>> Name: 'BlueZ (0)'
>> Class: 0x000000
>> Service Classes: Unspecified
>> Device Class: Miscellaneous,
>> HCI Ver: 1.1 (0x1) HCI Rev: 0x34e LMP Ver: 1.1 (0x1) LMP Subver: 0x34e
>>Manufacturer: Cambridge Silicon Radio (10)
>>--------------------------------------------------------------------
>>http://www.feline-soul.net/files/bluetooth/hcidump:
>>HCI sniffer - Bluetooth packet analyzer ver 1.31
>>device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
>>
>>> HCI Event: Mode Change (0x14) plen 6
>>
>> status 0x00 handle 41 mode 0x00 interval 0
>> Mode: Active
>>
>>> HCI Event: Mode Change (0x14) plen 6
>>
>> status 0x00 handle 41 mode 0x02 interval 126
>> Mode: Sniff
>>-----------------------------------------------------------------
>>http://www.feline-soul.net/files/bluetooth/hcidump_hcitool_connect HCI
>>sniffer - Bluetooth packet analyzer ver 1.31
>>device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Create Connection (0x01|0x0005) plen 13
>> bdaddr 00:07:61:1B:50:9B 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 0x0c ncmd 1
>> Error: Command Disallowed
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>
>>> HCI Event: Connect Complete (0x03) plen 11
>>
>> status 0x04 handle 0 bdaddr 00:07:61:1B:50:9B type ACL encrypt 0x00
>>Error: Page Timeout
>>--------------------------------------------------------------------
>>http://www.feline-soul.net/files/bluetooth/hcidump_hidd_connect
>>HCI sniffer - Bluetooth packet analyzer ver 1.31
>>device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
>>
>>> HCI Event: Mode Change (0x14) plen 6
>>
>> status 0x00 handle 41 mode 0x00 interval 0
>> Mode: Active
>>
>>> HCI Event: Mode Change (0x14) plen 6
>>
>> status 0x00 handle 41 mode 0x02 interval 126
>> Mode: Sniff
>>< HCI Command: Create Connection (0x01|0x0005) plen 13
>> bdaddr 00:07:61:1B:50:9B 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 0x04 handle 0 bdaddr 00:07:61:1B:50:9B type ACL encrypt 0x00
>>Error: Page Timeout
>>< HCI Command: Create Connection (0x01|0x0005) plen 13
>> bdaddr 00:07:61:1B:50:9B 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 0x04 handle 0 bdaddr 00:07:61:1B:50:9B type ACL encrypt 0x00
>>Error: Page Timeout
>>-----------------------------------------------------------
>>http://www.feline-soul.net/files/bluetooth/rfcomm.conf
>>#
>># RFCOMM configuration file.
>>#
>>
>>rfcomm0 {
>> # Automatically bind the device at startup
>> bind no;
>>
>> # Bluetooth address of the device
>> device 11:22:33:44:55:66;
>>
>> # RFCOMM channel for the connection
>> channel 1;
>>
>> # Description of the connection
>> comment "Example Bluetooth device";
>>---------------------------------------------
>>
>>That's it. The commands i used to get these sets of output are in the
>>previous email.
>>
>>Thanks all,
>>
>>Bearcat
>>
>>> Hi Bearcat,
>>>
>>> On 7/28/06, Bearcat M. Sandor <Bearcat@feline-soul.com> wrote:
>>>> Thank you again for the help so far. I have placed a bunch of output
>>
>>files on
>>
>>>> my server for your viewing pleasure, instead of giving you large
>>
>>outputs
>>
>>>> in
>>>> an email body.
>>>
>>> Sorry, but I couldn't see any of those files (all links end up with "404
>>
>>Not found" error). Can you send those files inline so we can see what's
>>happening, please?
>>
>>> Regards,
>>>
>>> -- Ulisses
--
Bearcat M. Sandor
Bearcat@feline-soul.com
ICQ: 6628727
MSN: bearcatsandor@hotmail.com
Yahoo: bearcatsandor
AIM: bearcatmsandor
Jabber: bearcatsandor@jabber.org
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-07-29 21:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 7:46 [Bluez-users] can't connect EPOX Keyboard BT-KB01B Wolfram Reda
2006-07-27 17:30 ` Bearcat M. Sandor
2006-07-27 17:43 ` Nils Faerber
2006-07-27 18:50 ` Wolfram Reda
2006-07-27 20:16 ` Bearcat M. Sandor
2006-07-28 1:22 ` Marcel Holtmann
2006-07-28 3:26 ` Bearcat M. Sandor
2006-07-28 7:21 ` Marcel Holtmann
2006-07-28 9:39 ` Nils Faerber
2006-07-28 9:46 ` Marcel Holtmann
2006-07-28 16:48 ` Bearcat M. Sandor
2006-07-28 18:21 ` Ulisses Furquim
2006-07-28 18:38 ` Bearcat M. Sandor
2006-07-29 6:35 ` Bearcat M. Sandor
2006-07-29 21:20 ` Bearcat M. Sandor [this message]
2006-07-28 0:18 ` [Bluez-users] Mouse works now, but can't connect Logitech Cordless Elite keyboard Bearcat M. Sandor
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=200607291520.25745.Bearcat@feline-soul.com \
--to=bearcat@feline-soul.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;
as well as URLs for NNTP newsgroup(s).