From: Damien Bardon <damien@bardon-net.fr>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] My device can't be detected by another one
Date: Mon, 8 Jan 2007 22:36:21 +0100 [thread overview]
Message-ID: <200701082236.21496.damien@bardon-net.fr> (raw)
In-Reply-To: <20070108184535.GJ16663@suse.de>
Thanks a lot it is working I had to do :
# apitest SetMode discoverable
This is not very convenient, it would be better if it was integrated to
kbluetoothd, or configurable with Yast...
Cheers,
Damien
On Monday 08 January 2007 19:45, Stefan Seyfried wrote:
> On Mon, Jan 08, 2007 at 07:35:15PM +0100, Damien Bardon wrote:
> > perfectly detected, and I can see other devices and connect to them. The
> > problem is that other devices (I have tried with two different mobile
> > phones, one nokia and one samsung) can't see my device. Which means that
> > for example, I can send a file from my laptop to my phone, but can't send
> > a file from my phone to my laptop. My linux seems to be configured to be
> > able to be detected, but I have probably missed something and I hope you
> > can tell me what.
>
> Read /usr/share/doc/packages/bluez-utils/README.SUSE
> If there are still problems, ask again.
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-01-08 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 18:35 [Bluez-users] My device can't be detected by another one Damien Bardon
2007-01-08 18:45 ` Stefan Seyfried
2007-01-08 21:36 ` Damien Bardon [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=200701082236.21496.damien@bardon-net.fr \
--to=damien@bardon-net.fr \
--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