LWUITDemo >> WARNING: Jar file is too large to run on actual device.

[andu77]

I noticed this:
WARNING: Jar file is too large to run on actual device.

while running demo project in Nokia SDK 2.0 for Java emulator.
Jar size is: 1.47 MB (1,542,376 bytes)
Did anybody run this project on a real device ?
Is it possible to load only partially LWUIT lib ? It's linked against S40-full-touch.jar of size 810 KB (829,897 bytes)

Regards,
Andu.

[petrib]

The max jar size allowed varies from device to device (ranging from "small" - e.g., 124KB - to "however much RAM happen to be free at the time the user decides to run the app" - e.g., tens of MB -, or anything in between).

For different Nokia models, see what the device specs say (see the "Memory Functions" section for each model): http://www.developer.nokia.com/Devic...pecifications/

I have no idea whether it is possible to just load LWUIT partially (probably not, unless you build it yourself so that you leave out stuff you don't need/use, but that is probably not an easy route, and leads to a maintenance problem).

[bandarap]

Hi andu77,

Maximum jar size in Java ME is 2 MB. LWUIT demo project is huge one and it has man resources.

To decrease the jar size, you need to package your application with obfuscate option. In that case, Demo project jar size decrease to around 900KB (962,093 bytes).

If you create normal hellow LUWIT project with obfuscation option, generated jar file will be around 300 KB.

I also successfully run Demo project in Asha 305 and 311 without obfuscation option.

[petrib]

Maximum jar size in Java ME is 2 MB. LWUIT demo project is huge one and it has man resources.

Perhaps there is a Java ME restriction or recommendation, but at least in the case of Nokia's various devices, the max jar size range varies greately below and above 2MB (especially when comparing older Series 40 models to newer models vs. S60/Symbian based models).

[andu77]

Launching directly the MIDlet(File/Open) I don't see this warning even if code is not obfuscated(by the way, indeed, obfuscation shrinks a lot!). Probably, message is bogus or it's something hard-coded into emulator FileUtils.createFakeJadAndJar class method(?) ... are emulator sources open/are they obfuscated Anyway I use 'Set maximum jar size (bytes)' option and set it to my device max. for testing.