public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Simone Gotti <simone.gotti@email.it>
To: bluez-users@lists.sourceforge.net
Cc: Detlef Grittner <detlef.grittner@t-online.de>
Subject: Re: [Bluez-users] Pocket PC 2003 and Linux
Date: Wed, 25 Aug 2004 12:02:47 +0000	[thread overview]
Message-ID: <200408251202.48482.simone.gotti@email.it> (raw)
In-Reply-To: <412C5482.3010909@t-online.de>

On Wednesday 25 August 2004 08:57, Detlef Grittner wrote:
> I have a working connection between a Linux box with SuSE 9.1 (Sitecom
> Bluetooth dongle) and a Pocket PC 2003 HP 5550.
> Ping and so on is no problem.
>
> But I found no way to transfer files from the Pocket PC to the Linux box.
> The other way round works: I can send any file from my Linux box to the
> Pocket PC via OBEX push.
> I have tried to start the obex demon with:
> opd --mode OBEX --channel 10 --daemonize --path /tmp --sdp
> Although the Pocket PC finds the Linux box, it says there are no known
> services on it.
> I have tried kbluetoothd as well and now the Pocket PC claims there is a
> kbtserialchat service on my Linux box. But I have no idea what I can do
> with it on my Pocket PC.
> I was able to establish a PAN network. But again, although the Pocket PC
> claims it is working, I have no idea how to use it.
>
> What I want to do is a obex push from the Pocket PC to the Linux box.
> Any ideas what am I missing?

I can answer you for the kde-bluetooth's kbluetoothd

To look if it has registered the OBEX PUSH sdp entry you can use the graphical 
interface (right click on the kbluetoothd tray icon -> configuration details 
-> configure services and look if the kbtobexsrv is registered and active.

You can do the same thing typing in a shell:
 sdptool browse FF:FF:FF:00:00:00

If the Obex Push is registered you'll get something like this:

Service Name: Obex Push Server
Service Description: KDE OBEX Object Push Service
Service RecHandle: 0x804f9a8
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


Bye!
-- 
Simone Gotti
<simone.gotti@email.it>
http://kde-bluetooth.sf.net


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

  reply	other threads:[~2004-08-25 12:02 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 [this message]
2004-08-25 13:25   ` Detlef Grittner
2004-08-25 16:12     ` Simone Gotti
2004-08-25 16:30       ` Detlef Grittner
     [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=200408251202.48482.simone.gotti@email.it \
    --to=simone.gotti@email.it \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=detlef.grittner@t-online.de \
    /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