Distinguishing device in midp 2.0

Hi guys,
Is there any way I can distinguish devices from their requst made to server. For example phone number, imei number or any anything else.
in midp 1.0 it was secuirty violation i gues which prevented it implementing the imei number is it possible now to retrieve it. If yes how?
Thank you

uaprof !
you can analyze it: if the device is MIDP 2.0, the server will send to the mobile the MIDP2.0 version,
otherwise, the server will send to the user the MIDP1.0 version...

Similar Messages

MIDP/CLDC Device Compatibility...

Hello everyone,
I am performing some research on the compatibility of MIDP/CLDC and current devices. It is a well known fact that some applications (MIDlets) will operate fine on some devices, while other devices require 'tweaking'.
Mikko Konito (writting for IBM) says "manufacturers often deviate from the [MIDP] profile" (link: http://www.ibm.com/developerworks/wireless/library/wi-design.html) which explains why these tweaks are necessary.
I would like to hear your views on what else could cause such "incopatibilities" with mobile devices and MIDP.
Many thanks,
P.M

Hi,
I worked about 5 years in J2ME development and porting. From the beginning of J2ME (MIDP-1.0 and beginning of MIDP-2.0) porting was a great business - every manufacturer and almost every handset type was different in many aspects.
Now the situation is a little bit better and also handset manufacturers are more responsible for their work.
But still - you must care:
- different display sizes
- different media capability (sound formats)
- diferent sets of API implementations
- ...and different BUGS in the MIDP implementation!
While the basic MIDP was implemented poorly at the beginning, now it seems that the MIDP itslef is implemented well on most of the new handsets, however the situation repeats with various new and non standard APIs (PIM, M3G...).
Simply - it's always good to test particular application on particular handset to be sure...
Rada

Creation of a database engine for mobile devices using j2me

am trying to develop a database engine for mobile devices.. it is to develop a miniature version of the DBMS that
can be deployed on a mobile phone..I have to develop my own code for performing tasks such a s creating a table,
inserting values into it, selecting from it etc..
I limited my self to develop the software so that it can perform 3 functionalities of create, insert,select..
I should be taking the details such as table name and its parameters from the user and then should be able to
create a suitable data structure for it(i tried to develop a class)...
Usage of RMS package helps me partially in this.. I did that and ll be doing that..
I got stuck while developing the code for creation of a table.. I am facing problems in creating a dynamic data
structure for a table and also to use such data structure else where in my project..
I need help in developing an algorithm for this..
I would be very grateful to u all if u help me out in developing the code for this project..

I'm sorry for the amount of time it took me to get back. Derby is an open source database written entirely in Java. I do not know if it can support resource constrained devices like MIDP compliant, but may work okay with CLDC.
But outside of Derby being a solution, let me give you a few ideas off the top of my head.
Set up a database server in a separate thread. This server will really be your controller for RMS access.
Since RMS is just a big sequential 'pipe' you will have to think of data as 'frames' - (starttable) (tableID) (tablename) (data) (tablename) (data).....(endtable).
When you need to write additional data, just append it to the end of the RMS object.
When you need to retrieve data, thing are more complex.
1. Read in all data, looking for your particular tableID. This may be made much easier using RMS filters - (I'm not sure, I've never used them)
2. Once start of table of interest is found, stick the data elements in either a java vector or array until you reach the table end identifier. I think vector will be a better choice - trust me. (I think its available in J2ME...)
3. Package this into a do while loop until the element you are searching for is read. If you need to do some sorts on the data or something else that requires the all the data to be present then you need all the data for that particular table. One thing will always be clear. The first data you grab will always be some start table identifier and the last data you grab will be an end table identifier. We just don't know which table because of how we put stuff in the RMS resource.
This provides you a few positives as well as negatives:
Positive:
1. Fast data writes, no need to search for a particular table before accessing it, nor do you need to search for an index in that table.
2. When looking for data, data may* be found without searching through the entire table. This is accomplished with RMS filters or logic test within the RMS read loop.
Negative:
1. Slow when all data of a table is needed (i.e. compute sums or averages of entries). The entire RMS database must be read to ensure all the entries are searched. An example of how this is a problem is as follows: You have 5000 entries in you RMS database resource and you are looking to compute the average of a value in some table. When you first wrote the data to the table, it was done sequentially and no other data for that table exist. But we can't tell if that's the case, so we have to read through all 5000 entries to make sure we looked for every piece of data.
Beacuse of this issue, this database structure, performance may be fine for 50K - 100K entries (depending on table element size), if the reading requirements don't force full data reads. Otherwise, 25K may be an upper limit.
I hope this helps.
Edited by: estarkey on Mar 17, 2009 9:15 PM
Edited by: estarkey on Mar 17, 2009 10:01 PM

Print in MIDP ...

How to print some text to a printer connectting with the PALM ?
tks.

[jun_w],
If you are referring to printing from a Palm OS device using MIDP, I am afraid you are out of luck as the MIDP specification does not make provision for any print APIs in MIDP, at least for the current MIDP 1.0 specifications.
HTH.
Allen Lai
Developer Technical Support
SUN Microsystems
http://www.sun.com/developers/support/

Midp 2.0 support

Does only the newest devices support midp 2.0? Or can I run some midp 2.0 code on any device, like motorola i85s?
The nokia 7650 does support midp 2.0?
Thnks
Ricardo

There are no devices out on the market that support MIDP 2.0. They say the first devices will come out in the summer of 2003. So, currently there are no phones that support it (not even the 7650).

How to get around this error

I want to use extenal classes in j2me, but it always get errors.
ERROR: floating-point arguments should not appear
Error preverifying class java.lang.String
com.sun.kvem.ktools.ExecutionException: Preverifier returned 1
Build failed
finally I write a class myself,pack it, and put it in the lib directory. The same error came out. Who can tell my why? thanks!

Guess what's the reason! Hint: "ERROR: floating-point arguments should not appear". Only integers can be used. These seem to be used in some of the external classes you're trying to use. Why is this all? Because not all devices supporting MIDP/CLDC have floating point operation unit.

Can't figure out why I can't enter letters into TextField from emulator

I have a Midlet comprised of a single form containing one TextField. When I run the Midlet using the standard emulator and hit keys on the number pad, I am limited to entering numbers only and cannot enter letters to form words. I.e. numerous presses of the same key only yields another number.
The TextField's input mode is UCB_BASIC_LATIN and the input constraints is set to ANY.
Platform Type = CLDC/MIDP
Emulator Platform = Java(TM) Platform Micro Edition SDK 3.0
Device = DefaultCldcMsaPhone2
Device Configuration = CLDC-1.1
Device Profile = MIDP-2.0
Mel

Facepalm
Menu > Qwerty > { Qwerty, 123, abc, Predict, Symbols, Virtual }.
Mel

IME API and IME Text Input Enhancement

Hi All,
I am presently using Adobe Air 1.5 Framework and i want to update the Air 2 Beta version. Help me in setting the same.
As in my application, it uses TLF which doesn't supprot IME. But as i came to know the features from AIR 2 Beta it provides.
Can you help me for the same in implementing the feature "IME API and IME Text Input Enhancement" with some samples or examples.
Thanks in advacne.
Krishna

I do not know what VM is ported on ur Pocket PC? It depends on the MIDP RI [Reference Imlementation] ported specific for each device. for e.g.:- for few pointer/touch screen devices the MIDP RI ported handles both the keypad and the pointer mappings automatically.
Kindly check out the below link where-in you have list of JVM's that you could port on your pocket PC.
http://www.comp.lancs.ac.uk/~fittond/ppcjava.html
Most of the palm or pocket PC's would be ported with CDC/Foundation Profile where you will have JNI support that may help you to develop your own application specific API's using the existing device native libraries provided by the vendor.
IBM's J9 VM for example supports JNI.
~Mohan

Interface StreamConnexion not find

Hi all,
In order to communicate with a bluetooth device, I've installed on my PC (OS : Ubuntu 8.04) the WTK 2.5.
I would like to create a SPP Server. I find a lot of example on the web which use the StreamConnection interface of the mdi api.
But I can't find anywhere this interface!
I use Eclipse and I add several jar in my project : midpapi10.jar, mdipapi20.jar and mdipapi21.jar (from WTK2.5.2/lib).
And in my code : import javax.microedition.io.*;
But without result!
I downloaded the WTK here : http://java.sun.com/products/sjwtoolkit/download.html?feed=JSC
I use the Bluez software to use Bluetooth connection.
Thanks in advance.

My question is : Which jar file have I to add in my project to use StreamConnection?
I read in the sun website :
The Sun Java Wireless Toolkit (formerly known as Java 2 Platform, Micro Edition (J2ME) Wireless Toolkit) is a state-of-the-art toolbox for developing wireless applications that are based on J2ME's Connected Limited Device Configuration (CLDC) and Mobile Information Device Profile (MIDP), and designed to run on cell phones, mainstream personal digital assistants, and other small mobile devices. The toolkit includes the emulation environments, performance optimization and tuning features, documentation, and examples that developers need to bring efficient and successful wireless applications to market quickly. That's why I try to use the WTK's libraries to communicate with my device (it's a small captor which use virtual bluetooth serial port to send its data). So if I understand what you said I cannot do that with the wireless toolkit libraries?
(First, I try to use directly RXTX library but I wasn't able to open the /dev/rfcomm0 port. My code return that the port doesn't exist!)

Help in Push Registry On S40

i have a problem in push registry on s40
it throw the exception
ClassNotFoundException : Midlet Not Found
i try the Same Code In S60 it run Well
The Code::::
private void Test() {
try {
System.out.println
("Befffforrrrrrrrrrrrr");
long x= DF.getDate().getTime();
prevalarm = PushRegistry.registerAlarm(this.getClass().getName(),x);
System.out.println
("Afterrrrrrrrrrrrrrrrrrrrrrrrr");
catch (ConnectionNotFoundException ex) {
System.out.println("Erorororo 1 :"+ex.getMessage().toString());
catch (ClassNotFoundException ex) {
System.out.println("Erorororo 2 :"+ex.getMessage().toString());
/**************************/The Jad file
MIDlet-Name: DemoForFun
MIDlet-Version: 1.8
MIDlet-Vendor: DemoForFun
MicroEdition-Profile: MIDP-2.0
MicroEdition-Configuration: CLDC-1.1
MIDlet-Jar-URL: DemoForFun.jar
MIDlet-Jar-Size: 2096
MIDlet-Permissions: javax.microedition.io.PushRegistry
MIDlet-1: DemoForFun, , DemoForFun

S40 Is MIDP 2.0
The Series 40 Platform 1st Edition supports Java� 2 Platform, Micro Edition (J2ME�) APIs, including Mobile Information Device Profile (MIDP) 1.0, Connected Limited Device Configuration (CLDC) 1.0, and Nokia's user interface APIs
The Series 40 Platform 2nd Edition added J2ME MIDP 2.0 with Java Specification Requests (JSRs), implementation of Wireless Messaging API (JSR 120), Mobile Media API (JSR 135), and Java APIs for Bluetooth (JSR 82).
Series 40 Platform 3rd Edition extends J2ME support, implements CLDC 1.1 and MIDP 2.0, and expands on the provision of messaging, mobile media, and Bluetooth technology APIs with support for FileConnection and personal information manager (PIM) (JSR 75), as well as Mobile 3D Graphics (JSR 184).

NetBeans Midlet signing not working for Sony Ericsson M600i

Hi,
I'm developing an midlet that uses FileConnection class extensively. I intend to deploy the midlet on Sony Ericsson M600i. I want to make my Midlet a trusted one so that the annoying warning popups stop each time access the device filesystem.
I created a keystore in netbeans and created a certificate using keytool using that keystore. Then I installed the certificate on the device. When I tried to depoly the midlet it says 'security check failed. cant install'.
the device has MIDP 2.0 and CLDC 1.1
pls explain how to make my Midlet trusted.
thank you in advance

pls explain how to make my Midlet trusted.You have to purchase a certificate (Verisign, Thawte...). NetBeans and WTK self-generated certificates are only for testing on the emulator and are not recognized by any handset (the root certificate is not available in the certificate store). And then, whether your purchased certificate is recognized by a specific device is both manufacturer/model and carrier dependent.
For self-signing MIDlets for Nokia Series 60 handsets, see SD's topic [n]Free Self Signing Midlet for Series 60 3'rd Edition at
{color:#0000ff}http://forum.java.sun.com/thread.jspa?threadID=5212743{color}
Haven't come across anything similar for SE phones though.
cheers, Darryl

J2ME "instead of" J2SE?

At our company we are thinking about a system that involves slimmed down PCs mounted in trucks. (There will also be an fleet management center at the companies head office.)
Approx PC spec; 200 - 300 MHz CPU, no harddisk but flash RAM maybe 512 MB, 10 inch TFT color screen. Keyboard and probably a CD/DVD reader. OS; Win CE, WinXP Embedded or Linux.
A map/navigation application would run on these. Another application will handle forms (an AWT-GUI will probably do).
We hope to find a commercial map app to install.
I would like to develop the other app in Java but the PC bulider didn't like the idea of runnig J2SE on that limited platform.
How about developing in J2ME? Pros and cons?
Can I just download J2ME from Sun, develop and run as I'm used to with J2SE? If we are running the JRE on Windows. Do we have to implement or port J2ME ourselfs.
I have developed in J2SE (Swing, Java 2D) and a little in J2EE (JDBC, EJB, Applets).

The original question is very interesting: should a mobile app move from J2SE to J2ME?
The answer is not simple at this time because the specs are evolving fast.
GUI features and h/w and OS portability is definitively a current factor but may not be important for many applications. A corporate application can usually select a set of hardware, OS and Java runtimes to support so all you have to do is make sure that your platform satisfies your business requirements and not the business requirements of the rest of the world.
Mobile GUI in J2ME is being improved by some new specs in progress and to be implemented probably in runtimes shipped in 2005.
TCP/IP features are now fully supported by MIDP2 (the socket and server socket are optional in the spec bu the all MIDP2 runtimes being shipped today support them).
Floating-point arithmetic is now supported by the underlying spec., CLDC 1.1; it was not supported by CLDC 1.0.
New specs have been proposed recently and are being supported by new J2ME runtimes: for example Wireless Messaging API (JSR-120, WMA) and Mobile Media API (JSR-135, MMA).
The set of mobile Java specs including MIDP are being regrouped by the JTWI spec: Java Technology for Wireless Industry (JSR-185).
The way to go in today's fast changing mobile technologies is CLDC and the specs supported by it:
-      Connected Limited Device Configuration (CLDC)
-      Mobile Information Device Profile (MIDP)
-      Java Device Test Suite
-      Information Module Profile (JSR-195)
-      Java Technology for Wireless Industry (JSR-185) <<<<<<<<<<<<<<<<<<<<<<<<
-      Wireless Messaging API (JSR-120)
-      Mobile Media API (JSR-135)
-      Location API for J2ME (JSR-179)
-      SIP API for J2ME (JSR-180)
-      Security and Trust Services API for J2ME (JSR-177)
-      Mobile 3D Graphics (JSR-184)
-      J2ME Web Services (JSR-172)
-      Bluetooth API (JSR-82, Motorola, Java Partner Site)
It looks like very soon if not already now, J2ME will have more features than J2SE for most interconnected mobile applications. For example, today, a MIDP2 device can install a new J2ME application over-the-air (OTA), something that cannot be done easily by J2SE, I believe. All the user has to do to install OTA is to browse to the web page with her mobile device that contains an html anchor () to the jad file referencing the application (a MIDlet) and the rest is automatic and the programmer has nothing to write to get this feature.
serge

Java Application not rocognized 3110c

I downloaded a dictionary from the internet with jar extension.
upon trying to run it, message appeared saying " Application not recognized"
could you please elaborate the different types of java platforms and which one is supported o my phone Nokia 3110c, and how to identify the supported one ...
Thanks in Advance

http://www.forum.nokia.com/devices/3110_classic
MIDP 2.0
CLDC 1.1
JSR 135 Mobile Media API
JSR 172 Web Services API
JSR 177 Security and Trust Services API
JSR 184 Mobile 3D Graphics API
JSR 185 JTWI
JSR 205 Wireless Messaging API
JSR 226 Scalable 2D Vector Graphics API
JSR 75 FileConnection and PIM API
JSR 82 Bluetooth API
Nokia UI API

Problem with calling a midlet within another midlet

hello friends,
can a create an instance of a midlet within another midlet.i tried to call , but i have got a Security exception. plz comment on this ..
regards..

"For security reasons, it is assumed that MIDlets within a MIDletSuite are packaged
together for a reason and should be able to interoperate. What's implied here is that the
MIDlets share a name space; in other words, each MIDlet in the MidletSuite can "see" one
another. Because they can see one another, they can launch one another (Class.forName
metaphor).
In contrast, one MIDletSuite cannot launch another MIDletSuite. That's because they do not
share name spaces. Since the CLDC+MIDP does not have a security manager (too big and
complex for small devices), the MIDP expert group felt it more prudent to limit the interaction
of downloaded applications to those that are packaged together by the provider."extract from Sun
see http://developers.sun.com/mobility/midp/articles/pushreg/ for infos to launch MIDlets...

Two free copies of Mobile Media API (MMAPI) book available

Hello everybody,
My book on Mobile Media API has now been released by Apress. This book is called Pro Java ME MMAPI and you can buy it of Amazon (http://www.amazon.com/gp/product/1590596390/ref=sr_11_1/103-6578893-2197420?%5Fencoding=UTF8) or Apress's book website (http://www.apress.com/book/bookDisplay.html?bID=10101). The Apress website also contains a sample chapter on MMAPI lifecyle and events.
I have two copies of the book to giveaway to anyone who promises to write a review on Amazon. Please email me if interested at [email protected]
This is what the book covers from the publicity release:
"Pro Java ME MMAPI book explores this API in detail. This book explains the architecture of this API, explores how this architecture sits with the Mobile Independent Device Profile (MIDP) and shows you how to make the best use of the multimedia capabilities of a Java enabled phone.
This book has detailed examples that cover the basic stuff, like simple audio playback and tone generation to more advanced issues, like synchronized media playback, video, audio and image capture and streaming live radio. The book uses a real world mobile phone to demonstrate these examples, besides the Java Wireless Toolkit emulators and Motorola and BenQ emulators.
This is the first book by a major publisher that covers this topic in detail. It provides an all-in-one reference to create multimedia applications for Java enabled phones using the MMAPI."
I hope you find the book useful. :)
Regards,
Vikram Goyal
[email protected]
Author of Pro Mobile Media API (MMAPI) by Apress
http://www.mmapibook.com

hi ..
did you have an answer to the first post ? if u did plz share me
atspal@hotmailcom
Kind Regards
Ali

Distinguishing device in midp 2.0

Similar Messages

Maybe you are looking for