Do you mean 1)the MIDlet goes to actual Paused state in the sense of the MIDP midlet lifecycle, or 2) it just looks like doing nothing, ie "paused".
1) It can't be or it shouldn't be unless the constructor of the object you're creating calls MIDlet.notifyPaused() somehow. What kind of object are you creating?
2) Maybe you are blocking the
thread inside the constructor, so it looks "paused".
Regards
[ April 18, 2007: Message edited by: Eduardo Marques ]