N73 Class format error 40

[nagkumar]

We are observing class format error 40 when a perticular class is being loaded by our j2me application. This class a very simple form which is supposed to show a form with rms data.

The jad/jar works fine on other phones such as nokia 6600, v3x etc..

Are there any clues what could be the issue w.r.t to N73 and this error message.

Regards,
Raja Nagendra Kumar,
C.T.O
www.tejasoft.com
Competant and Reliable Offshore Development Partners

[syazwan_m]

I'm also having problem with N73. My MIDlet works fine for N70, but does not start on N73. I'm still waiting for someone to shed some light unto this matter.
I think its about Symbian OS new version or something.

[jimgilmour1]

hi
I think you are suffering similar problems to mine with the N73. The device needs an firmware upgrade

The N73 may need a firmware update to view Live TV, continuous video streaming using an on mobile phone application.

Java ™ Platform, Micro Edition versions by all suppliers appear affected.

The symptoms are the video starts in a windows then a second later stops with an Media Event error.

see article in Forum Wiki
http://wiki.forum.nokia.com/index.ph...ideo_streaming.

Good Luck
Jim,

[nagkumar]

Our further investigation on this is giving the following clue..

We don't see the class format error if the code is not obfuscated. Only in obfuscated code we see such thing.

Ya, this seems to be happening only on N73 phone and not on 6600 or other motorola phones. I think there is some issue kvm class loading and perticular combination of symbols etc. Need to try the firware upgrade and see if this fixed.

Regards,
Raja Nagendra Kumar,
C.T.O
www.tejasoft.com

[pjreez]

I'm observing the same problem on a E65 phone. ClassFormatError 40 is thrown when a particular class is being instantiated. The problem disappears when the code is not obfuscated.
@nagkumar: Could you tell me if updating the firmware solved the problem for you? Thanks

[grahamhughes]

What obfuscator are you using?

Some Series 60 devices do seem to have occasional problems with obfuscated code. Try disabling any optimization options your obfuscator has. If you're using Proguard 4, make sure you have the latest (non-Beta!) version. Always avoid using Beta versions of development tools. If you are using the latest, try using Proguard 3 instead.

Graham.