Skip to main content

Do I need to implement the Bluetooth profiles for PhoneMe

7 replies [Last post]
feng_tian
Offline
Joined: 2007-09-20
Points: 0

According to the description of PhoneMe MR2, it supports JSR82(bluetooth).
Does PhoneMe also implements the profiles of bluetooth, or it must base on the profiles that you implemented on linux?
I mean if I have a platform, let's say AT91SAM9260(ARM926), and bluetooth was supported in the driver and stack level. Then I port the PhoneMe MR2 to the platform, does every function of bluetooth available then? Do I need to implement the profiles of bluetooth first, and then port PhoneMe to the platform.
Another question, which profile does PhoneMe supports.
Thanks in advance.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
feng_tian
Offline
Joined: 2007-09-20
Points: 0

As for the bluez, I found that all the profiles is for the host, did I miss something.
We also want to implement our device as a client which can function like a headset.
Can I still use bluez?
If not, is there any open source implementation?
Thanks

Regards
Feng

peterp
Offline
Joined: 2005-06-30
Points: 0

Dear feng_tian,

JSR 82 is not developed in open source repository due to the legal restrictions. This is why you don't see jsr82 directory in phoneME Advanced. Sun has legal right to publish JSR 82 sources when the JSR is TCK compliant only. So, the JSR 82 on CDC will be available as part of source bundle as soon as it passes TCK.

Currently, JSR 82 on CDC is under development.

Regards,
Petr

Johannes Eickhold

On Mon, 2007-10-01 at 23:09 -0700, phonemeadvanced@mobileandembedded.org
wrote:

Hi Petr!

> JSR 82 is not developed in open source repository due to the legal
> restrictions. This is why you don't see jsr82 directory in phoneME
> Advanced. Sun has legal right to publish JSR 82 sources when the JSR
> is TCK compliant only.
>
> So, the JSR 82 on CDC will be available as part of source bundle as
> soon as it passes TCK.

This is hard to understand. BlueZ is developed as open source, the Java
VM and its runtime environment is now developed as open source but a
"wrapper" API (JSR-82) around BlueZ conforming to this standard as part
of the runtime environment is NOT developed in the open? Can you please
explain where this does come from?

> Currently, JSR 82 on CDC is under development.

To me it seems that JSR-82 is a very usefull extension needed and wanted
by many. This is obvious as we talk mostly about a Java environment for
mobile devices here where bluetooth is the first connection type one
thinks of. Don't you think the project would benefit from a development
in the open?

Just my 2 cent,
Jonek.

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

Terrence Barr - Evangelist, Java Mobile & Embedded

Hi Johannes,

It's not a question of not wanting to do development
in the open. It's an unfortunate side-effect of the
current JCP rules.

These rules state that an implementation of a JSR spec
can only be made available outside of the corresponding
expert group if that implementation is compliant to the
appropriate TCK.

Unfortunately, if interpreted strictly this means that
you cannot do any code development of a JSR implementation
in the open since at certain points in time that code will
not be TCK compliant but it is available outside the
expert group.

For JSR specification where Sun is the spec lead (or co-
spec lead) this is not an issue because we want to
encourage development in the open and so we permit this
use case. That is why you will find our implementations
of MIDP and many other JSRs in the open source code base.

However, we cannot assume the same is true for other JSR
specs that Sun does not lead. JSR 82 is such a case and
so for now we cannot develop the implementation of it in
the open and can only make it available once it is complete
and has passed the TCK.

JCP has recognized the problems these rules cause for open
source projects seeking to implement JSRs and is working on
updating the rules accordingly to enable open source
development. But this will take time.

-- Terrence

Johannes Eickhold wrote:
> On Mon, 2007-10-01 at 23:09 -0700, phonemeadvanced@mobileandembedded.org
> wrote:
>
> Hi Petr!
>
>> JSR 82 is not developed in open source repository due to the legal
>> restrictions. This is why you don't see jsr82 directory in phoneME
>> Advanced. Sun has legal right to publish JSR 82 sources when the JSR
>> is TCK compliant only.
>>
>> So, the JSR 82 on CDC will be available as part of source bundle as
>> soon as it passes TCK.
>
> This is hard to understand. BlueZ is developed as open source, the Java
> VM and its runtime environment is now developed as open source but a
> "wrapper" API (JSR-82) around BlueZ conforming to this standard as part
> of the runtime environment is NOT developed in the open? Can you please
> explain where this does come from?
>
>> Currently, JSR 82 on CDC is under development.
>
> To me it seems that JSR-82 is a very usefull extension needed and wanted
> by many. This is obvious as we talk mostly about a Java environment for
> mobile devices here where bluetooth is the first connection type one
> thinks of. Don't you think the project would benefit from a development
> in the open?
>
> Just my 2 cent,
> Jonek.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
> For additional commands, e-mail: advanced-help@phoneme.dev.java.net
>
>

--
Terrence Barr
Technical Evangelist, Java Mobile & Embedded Community
Phone: +49 711 720 98185
http://www.mobileandembedded.org, http://www.sun.de, http://www.sun.com

Registered Office:
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten, Germany
Commercial register of the Local Court of Munich: HRB 161028
Managing Directors: Wolfgang Engels, Dr. Roland Boemer
Chairman of the Supervisory Board: Martin Haering

NOTICE: This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended recipient,
please contact the sender by reply email and destroy all copies of the original
message.
[terrence.barr.vcf]
---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

feng_tian
Offline
Joined: 2007-09-20
Points: 0

I found that bluez and jbluez seem to be a good solution if PhoneMe needs all the profiles.
Has anyone has the experience to port the jbluez into PhoneMe? Does it feasible?

akz003
Offline
Joined: 2006-10-13
Points: 0

Dear feng_tian,

phoneME Feature MR2 release issued in May is based on bluez stack - you may get the linux JSR82 bits from the download page, however the stack itself neither part of source bundle nor binary due to legal restrictions.

Regards
Kostya

feng_tian
Offline
Joined: 2007-09-20
Points: 0

Dear akz003,
I downloaded the "phoneme_advanced-mr2-dev-src-b21-04_may_2007", but it doesn't include a jsr82 dir. phoneme feature has jsr82 dir, but we don't want touse phoneme feature, because we need CDC not CLDC.
Where can I find this package?
Thanks.

Regards
Feng