What % of latest phones from leading vendors like Nokia, Mot, Samsung, etc has JSR 82(bluetooth) stack built in to it?
If i develop an app based on JSR 82, can i cover most of the latest devices?
With MSA 248 (now being deployed in large numbers) JSR 82 is mandatory. However, since part of the Bluetooth APIs are protected you may need permissions to access some of the Bluetooth functionality. This is no different than other protected Java ME APIs.
Due to the potentially different security policies that OEMs and operators may have this results in the less-than-ideal situation that you may have to sign your MIDlet differently for different OEM/carrier permutations.
This is fundamentally not a Java ME problem but a problem of different vendor policies. Java ME is suffering it particularly badly because it is such a widely deployed platform. I think on Android the jury is still out on these things as many aspects of Android are still undefined AFAIK - for example, they explicitly allow proprietary extensions and alterations to the stack. And Android faces the exact same vendor agendas that Java ME has been facing for years.
Thanks for the responses again.
"since part of the Bluetooth APIs are protected you may need permissions to access some of the Bluetooth functionality"
 What part of Bluetooth API's are protected?
 What Bluetooth functionality needs permissions?
Please see our wiki. Lots of info on Bluetooth here:
> Thanks for the responses again.
> "since part of the Bluetooth APIs are protected you may need permissions to access some of the Bluetooth functionality"
>  What part of Bluetooth API's are protected?
>  What Bluetooth functionality needs permissions?
> [Message sent by forum member 'kumarudaya' (kumarudaya)]
> To unsubscribe, e-mail: email@example.com
> For additional commands, e-mail: firstname.lastname@example.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Here is a link that might help you find devices that support jsr 82.
However beware the operators in the US (maybe UK/Asia as well) may restrict access to the bluetooth stack from Java, or may limit the type of support that is allowed. (ie. some operators don't allow data communication to a bluetooth device, and only support audio, or they may not support access to the bluetooth device when a HTTP connection is being made).
Thanks for your response.
Interesting to hear about operators blocking JSR 82 for data! i can understand the reasons behind it and if the device manufactures supports it, then what is the use of JSR 82?
Exactly, what's the use if the operators can randomly pick jsr to turn off of a device.
I think that is why Android said that they had to take it all and only restrict when the user says to. I thought that was how J2ME was going to be, if the device supports it then the user could allow or disallow, but that would have been too useful. ;)
But it's not just JSR82 it's all of them, 75, 135, 120, the list goes on. If the operators don't understand the technology or want it all for themselves they turn off support for the common developer or hobbyist. What is really bad is some operators will allow phone (x) to have full support, while phone (y) doesn't. I pay a lot for unlimited data service, and the right to use my phone as a modem (within reason), but I can't get my bluetooth to support DUN (Dial Up Networking), while my wife pays 1/2 for her dataplan (same operator) and I can get it to work on her phone. Grrrr.... 8-(
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.