From: Thomas Kear <thomas.kear@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Profiles on Bluez
Date: Fri, 12 Jan 2007 09:55:21 +1300 [thread overview]
Message-ID: <200701120955.24082.thomas.kear@gmail.com> (raw)
In-Reply-To: <4f436aae0701110833m5aa4155bxbbc61920f5421f3c@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2078 bytes --]
SCO (handsfree), A2DP and AVRCP are supported by the bluetooth-alsa driver
http://bluetooth-alsa.sourceforge.net
BPP, depending on which way you want to use it, is a bit of an issue at the
moment. I haven't yet found a server that lets my PC accept print requests
from mobile devices and print them through CUPS. However working the other
way, CUPS has a bluetooth backend that supports adding queues for bluetooth
printers (I believe using HCRP).
OPP and FTP are handled just fine by KDE's 'kdebluetooth' package, if you have
it installed, bluetooth:/ in a konqueror view should give you a device
listing, double clicking a device icon should display supported profiles, FTP
is called "OBEX File Transfer". In OPP's case, sending a file from a device
to the PC should automatically open a dialogue to facilitate recieving it.
Sending files is as easy as right clicking them in a konqueror view and
selecting "Actions> Send with Bluetooth...". Gnome's bluetooth utilities
should have similar funtionality, I cannot comment further as I've never used
them.
--Thomas
On Friday 12 January 2007 5:33 am, Choi Sonim wrote:
> Hello ppl!
>
> What Bluetooth profile do BlueZ support ?
> I found some OBEX utilities (which both gnome and kde provides),
> and the builtin BNEP support. but that;s it. no hands-free, bpp,
> opp,a2dp,ftp, nothing ?
>
> I know it is high-level and everything can be written on top of bluez
> but i wonder what is already supported ?
>
> Thank You ppl,
> Choi.
>
> -------------------------------------------------------------------------
> 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
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-01-11 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 16:33 [Bluez-users] Profiles on Bluez Choi Sonim
2007-01-11 20:55 ` Thomas Kear [this message]
2007-01-12 16:59 ` Choi Sonim
2007-01-12 20:25 ` Thomas Kear
2007-01-12 23:21 ` Michael Mauch
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=200701120955.24082.thomas.kear@gmail.com \
--to=thomas.kear@gmail.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