Alexander Traud

Greenhorn
+ Follow
since Jul 07, 2004
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
In last 30 days
0
Forums and Threads

Recent posts by Alexander Traud

Although it is CDC here, but if you do CLDC and really, really need the Collection package: Sun InfoBus.
This gives the Collection API. Never tried in J2ME but it should work if you have enough heap.
[ November 27, 2004: Message edited by: Alexander Traud ]
19 years ago
Forum Nokia > Resources > Documents > Bluetooth
19 years ago
Sure, why not. Just implement the clases yourself or find 100% JSR-82 OBEX Java classes.
19 years ago
Do want a data connection or a voice connection? The latter needs a ; at the end. You manage to issue AT commands from a MIDlet? To what AT command interface do you talk?
19 years ago
Unfortunately not.

Mac OS 8 and Mac OS 9 are out because a byte code preverifier is missing. At least I have not found a Java JDK 1.1.8 compatible one yet.

For Mac OS X it is a bit better:
MIDP 1.0
MIDP 2.0

Another way are Java compatible emulators. See the articles above for further references. Even UNIX x86 is problematic for J2ME development. Nokia does a lot here or you install Windows API emulators.
19 years ago
The Nokia 6230 is the only JSR-82 enabled Nokia Series 40 mobile phone. I do not understand you.

You made sure the master/slave configuration is correct in your setup? If you have a server/client configuration within your Java application, you should do a master/slave switch on the Bluetooth link, too. Your server must be the Bluetooth master otherwise you create Bluetooth piconets which are not supported by most Bluetooth chips.

You made sure to use L2CAP layer instead of the Serial Port Profile. I am not sure on that definitely, but I have read it supports only 1:1 communications.
[ September 24, 2004: Message edited by: Alexander Traud ]
19 years ago
Which one does have JSR-82 with the optional OBEX support? Nokia 6260, 6600, 6620, 6630 and 7610 do not. The Nokia 6230 a Series 40 device does not have it, too. The Sony Ericsson P900 does not have it. Not sure for the Siemens and Sendo implementations.
20 years ago
No mobile phone ships with that. Anyway it is quite easy to add it.
20 years ago
No, only these phones support JSR-82:
- Nokia 6230
- Nokia 6600
- Nokia 6620
- Nokia 7610
- Siemens SX1 (since firmware 10 or 11)
- Siemens S65
- Sony Ericsson P900 (since firmware R1B or somthing like that)

and the Sendo X shall have it. JSR-82 is "quite" new and the mobile phone manufactures needed time to implement it. A good start is Benhui but personally I recommend to read the JSR-82 specification which gives anything you will need - even code examples.
20 years ago
I recommend to buy a book about Java 2 Micro Edition (J2ME) and CLDC/MIDP. Over the air is done via WAP/HTTP connection. With the Nokia Content Copier you can load your MIDlet via cable, infrared and Bluetooth to your phone. The Nokia SDK even contains this application - it was installed while it installed the emulator...

Nokia Forum has a lot and extremly good documentation about J2ME, too.

Your other question is too "generic". It could be nearly everything. You read the outstanding EclipseME documentation? You have the latest version(s)?
20 years ago
Either over the air or the Nokia Content Copier (came on the Nokia 6230 CD-ROM). The Nokia SDK allows it to.
20 years ago
Javac is javac. The classes won't get better in an IDE nor do they get worse. It depends on the javac options. Compiling was no problem yet.

How to do it manually? You know the command prompt and "jar" and "preverify"? These command line utilities are your way. Look at their parameters and you will find it. "preverify" does not need an option, just the file and your classpath. "jar" needs several options. Just look for a reference on the net or look into their help pages. I can't give a "general" rule here - it is just passing the right paramters to these apps.
20 years ago
I had a similar problem in my XHTML page and it turned out to be a bug on my side. I would say that file is not well formed. Every literal "&" must be escaped with "& a m p ;" even within attribute values. The W3C validator will not like your page either.

If you want to use a literal ampersand in your document you must encode it as "& a m p ;" (even inside URLs!).


[ July 11, 2004: Message edited by: Alexander Traud ]
20 years ago
EclipseME makes not very good JAR files. The classes are not preferified sometimes (have not figured out why yet), it is not compiled with Java 1.1 compatible byte code (can be fixed via the project settings or better via the preferences of Eclipse) and the JAR is filled with unnecessary files (I see no possible solution for this). I read the full documentation - perhaps I am too stupid. Anyway the JAD and the MANIFEST file need fine tuning, so I have to repackage it anyway.

EclipseME is great for the developing and debugging phase but when it comes to the final release, you'll have to go over it manually.

But I think my next (very) big J2ME project will be made within a text editor and the command line utilities. Eclipse is too slow here and sometimes the behaviour is obscure.
[ July 11, 2004: Message edited by: Alexander Traud ]
20 years ago
Put the JSR-82 stub files you have into the class path and compile. You should be able to run it then on your Nokia mobile phone. But please remember - currently only these two Nokia mobile phones Nokia 6600 and Nokia 6230 support JSR-82 and do not include these stubs into the JAR. There are not muc more which do at the moment (Siemens SX1, Sony Ericsson P900 both with latest firmware) but there are coming a lot more this year.

You do not need any Bluetooth implementation within these stubs. But then you have to do all your testing on a real device. If you want to test your Bluetooth application, I recommend either the WTK 2.2 or a J2ME emulator from Nokia. Personally I work with the Nokia 6230/6600/9500 Concept SDKs under Linux and EclipseME successfully.

The Windows version from Nokia allow even more features.

In my small experince EclipseME is great for the start but it makes not very good real MIDP apps in the output. In my case I had to enable Java 1.1 compatible class generation, manually redoing the preverifying and package the JAR correctly. Even the outputed MANIFEST.MF is wrong according to MIDP 1.0 specification. Anyway I use it. :roll:
[ July 10, 2004: Message edited by: Alexander Traud ]
20 years ago