From: detlef.grittner@t-online.de (Detlef Grittner)
To: Simone Gotti <simone.gotti@email.it>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Pocket PC 2003 and Linux
Date: Wed, 25 Aug 2004 18:30:43 +0200 [thread overview]
Message-ID: <412CBEB3.6090606@t-online.de> (raw)
In-Reply-To: <200408251612.44110.simone.gotti@email.it>
Simone Gotti wrote:
>So the Obex Push service is right registered but the Pocket PC can't find it?
>you said that it can find only the kbtserialchat, can you confirm this?
>I can only think that probably there are registered more than one obexservice.
>Can you post the full output of "sdptool browse local"?
>
>P.S. I don't know if this is the right place to talk about kdebluetooth.
>Probably we should move our thread to the kdebluetooth mailing list (avoiding
>any crossposting).
>
>Bye!
>
>
It's not only kdebluetooth that isn't working, but opd as well.
And yes, kserialchat is detected by the Pocket PC.
Here is the output, which looks alright:
Browsing FF:FF:FF:00:00:00 ...
Service Name: SDP Server
Service Description: Bluetooth service discovery server
Service Provider: BlueZ
Service RecHandle: 0x0
Service Class ID List:
"SDP Server" (0x1000)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 1
Version: 0x0001
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Service Name: Public Browse Group Root
Service Description: Root of public browse hierarchy
Service Provider: BlueZ
Service RecHandle: 0x804d008
Service Class ID List:
"Browse Group Descriptor" (0x1001)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Service Name: Obex Push Server
Service Description: KDE OBEX Object Push Service
Service RecHandle: 0x8050770
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
"OBEX" (0x0008)
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100
Service Name: KBtHandsfree
Service Description: KDE Bluetooth Phone Client
Service RecHandle: 0x8050b58
Service Class ID List:
"" (0x111e)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Profile Descriptor List:
"" (0x111e)
Version: 0x0101
Service Name: KBtSerialChat
Service Description: KDE Bluetooth Serial Chat Service
Service RecHandle: 0x8050eb0
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 5
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-08-25 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 8:57 [Bluez-users] Pocket PC 2003 and Linux Detlef Grittner
2004-08-25 12:02 ` Simone Gotti
2004-08-25 13:25 ` Detlef Grittner
2004-08-25 16:12 ` Simone Gotti
2004-08-25 16:30 ` Detlef Grittner [this message]
[not found] ` <200408251846.26673.simone.gotti@email.it>
[not found] ` <412CC793.1000208@t-online.de>
2004-08-25 20:02 ` Simone Gotti
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=412CBEB3.6090606@t-online.de \
--to=detlef.grittner@t-online.de \
--cc=bluez-users@lists.sourceforge.net \
--cc=simone.gotti@email.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.