Re: [codenameone-discussions] SCREEN/APP FREEZING

Hi, I think my problem was to create all my form in advance, not in the EDT plus to do expensive task on this... On Wednesday, October 26, 2016 at 3:44:14 AM UTC+2, Shai Almog wrote: > > Do you have more than one call to invokeAndBlock in a row? > The method has an overhead and a nesting limit

Re: [codenameone-discussions] SCREEN/APP FREEZING

Im experiencing something similar on the simulator, not even on a real device, An exception occurred during transition paint this might be valid in case of a resize in the middle of a transition java.lang.StackOverflowError at

Re: [codenameone-discussions] SCREEN/APP FREEZING

Hi, What do you mean by sleeping off the EDT ? On Saturday, October 22, 2016 at 4:48:11 AM UTC+2, Shai Almog wrote: > > If you have intensive work you need to sleep off the EDT between work > batches. Even multi-core CPU's are pretty damn weak on mobile. > -- You received this message because

Re: [codenameone-discussions] SCREEN/APP FREEZING

If you have intensive work you need to sleep off the EDT between work batches. Even multi-core CPU's are pretty damn weak on mobile. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving

Re: [codenameone-discussions] SCREEN/APP FREEZING

While that could be a performance problem the UI should still appear eventually. I don't see the stack you screenshotted earlier which is why I asked for the logs here... -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To

Re: [codenameone-discussions] SCREEN/APP FREEZING

>From the Log(Attached) I can see the 'Choreographer : Skipped 36 Frames! The Application maybe doing too much work in its main tread' that happens whenever i touch on the freezed screen. On Friday, August 26, 2016 at 7:44:49 AM UTC+3, Shai Almog wrote: > > That's a screenshot, not the text log

Re: [codenameone-discussions] SCREEN/APP FREEZING

Attached is my DDMS Log. How can you help? On Wednesday, August 24, 2016 at 7:13:16 AM UTC+3, Shai Almog wrote: > > If you can isolate a standalone test case and file an issue then we can > look at it. I'm assuming that isolating a test case would be harder. > -- You received this message

Re: [codenameone-discussions] SCREEN/APP FREEZING

If you can isolate a standalone test case and file an issue then we can look at it. I'm assuming that isolating a test case would be harder. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop

Re: [codenameone-discussions] SCREEN/APP FREEZING

Trying to set up it up on Netbeans but not yet successful. On Friday, August 19, 2016 at 9:03:45 AM UTC+3, Shai Almog wrote: > > Font classes shouldn't be a problem, do you see any output in the DDMS > console? > -- You received this message because you are subscribed to the Google Groups

Re: [codenameone-discussions] SCREEN/APP FREEZING

This sounds like the EDT thread is stalled waiting for a synchronization monitor. You have some hope if you can produce this behavior in the simulator, where you can see what threads are doing. -- You received this message because you are subscribed to the Google Groups "CodenameOne

Re: [codenameone-discussions] SCREEN/APP FREEZING

I suggest connecting the device with a cable and looking at the DDMS output to see if there is any exception or suspicious printout when you reproduce this issue. We'll also need to understand what's in that page. -- You received this message because you are subscribed to the Google Groups

Re: [codenameone-discussions] SCREEN/APP FREEZING

Not at all. On Wednesday, August 17, 2016 at 6:13:07 PM UTC+3, Steve Hannah wrote: > > Are you using any GeneralPaths or drawShape()? > > On Wed, Aug 17, 2016 at 4:28 AM, Jojiez > wrote: > >> Hi, >> >> There this Android App I've developed that is having freezing issues

Re: [codenameone-discussions] SCREEN/APP FREEZING

Are you using any GeneralPaths or drawShape()? On Wed, Aug 17, 2016 at 4:28 AM, Jojiez wrote: > Hi, > > There this Android App I've developed that is having freezing issues when > installed on Android 5.0 Lollipop. The freezing takes places during form > transition(see

[codenameone-discussions] SCREEN/APP FREEZING

Hi, There this Android App I've developed that is having freezing issues when installed on Android 5.0 Lollipop. The freezing takes places during form transition(see attached) , components touch response.. But it works very fine on Android 6.0 Marshmallow. What could be the problem? If you