From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A2DP over DBUS
Date: Sat, 13 Sep 2008 13:12:15 -0600 [thread overview]
Message-ID: <d89ddf300809131212h2e1fbfb6k4d4d50763b2a0299@mail.gmail.com> (raw)
In-Reply-To: <f21e7dc80809131154s7d0b7e99t23201743f65e1f50@mail.gmail.com>
Choi
> That's interesting. What about platforms like Android that are only
> Java (If I am not wrong) ? Can they connect directly to those sockets
> from Java applications ?
Check the android API docs. I'd heard the API for bluetooth was
incomplete in the latest android but I haven't read up.
The sun embedded java APIs specify a way to run L2CAP (at least) using
java. Can't remember about SCO. Android breaks with the sun API (for
good reason).
The right way to do it in android would be integrating the bt audio
services with their multimedia hooks, so you wouldn't deal with the
underlying implementation.
--
Brad
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-09-13 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 17:26 [Bluez-devel] A2DP over DBUS Choi Sonim
2008-09-13 18:27 ` Marcel Holtmann
2008-09-13 18:32 ` Choi Sonim
2008-09-13 18:47 ` Marcel Holtmann
2008-09-13 18:54 ` Choi Sonim
2008-09-13 19:12 ` Brad Midgley [this message]
2008-09-13 19:54 ` Marcel Holtmann
2008-09-16 16:56 ` Nick Pelly
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=d89ddf300809131212h2e1fbfb6k4d4d50763b2a0299@mail.gmail.com \
--to=bmidgley@gmail.com \
--cc=bluez-devel@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