[codenameone-discussions] Re: Display.getInstance().execute on android causes OS to suspend my app

2020-02-13 Thread Shai Almog
No. It's core to their architecture. It's about battery life and control. Notice your app still has CPU access if it needs it. This isn't about that. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group

[codenameone-discussions] Re: Display.getInstance().execute on android causes OS to suspend my app

2020-02-12 Thread Mark Bolduc
On Wednesday, February 12, 2020 at 7:55:46 AM UTC-5, Mark Bolduc wrote: > > Fair enough. > > thanks. > > Do you think this behaviour will go away when these devices have more > processing power? > > Regards. > > On Tuesday, February 11, 2020 at 9:10:26 PM UTC-5, Shai Almog wrote: >> >> iOS

[codenameone-discussions] Re: Display.getInstance().execute on android causes OS to suspend my app

2020-02-12 Thread Mark Bolduc
Fair enough. thanks. Do you think this behaviour will go away when these devices have more processing power? Regards. On Tuesday, February 11, 2020 at 9:10:26 PM UTC-5, Shai Almog wrote: > > iOS would do that for some processes. Android is more consistent in that > sense. You should code

[codenameone-discussions] Re: Display.getInstance().execute on android causes OS to suspend my app

2020-02-11 Thread Shai Almog
iOS would do that for some processes. Android is more consistent in that sense. You should code defensively regardless. FYI Android does that when you just rotate the device... We hide a lot of these nuances from the developers but there are some things that aren't abstractable. -- You

[codenameone-discussions] Re: Display.getInstance().execute on android causes OS to suspend my app

2020-02-11 Thread Mark Bolduc
Note that this is only on Android, IOS does not suspend my app when my app spawns another process like reading a PDF document. Regards. On Sunday, February 9, 2020 at 8:52:22 PM UTC-5, Shai Almog wrote: > > No. When you exit the app the process is always suspended that's how > mobile

[codenameone-discussions] Re: Display.getInstance().execute on android causes OS to suspend my app

2020-02-09 Thread Shai Almog
No. When you exit the app the process is always suspended that's how mobile programming works. Notice the PDF reader logic works perfectly you just receive a suspend/resume for the current activity. -- You received this message because you are subscribed to the Google Groups "CodenameOne

[codenameone-discussions] Re: Display.getInstance().execute on android causes OS to suspend my app

2020-02-09 Thread Mark Bolduc
So , 1 year later, In Android 9 Can An App run an external process / app without the OS sending a suspend to my app? Is there a codenameone PDF reader library? Regards On Sunday, February 17, 2019 at 8:12:23 AM UTC-5, Mark Bolduc wrote: > > Thanks. > > On Saturday, February 16, 2019 at

[codenameone-discussions] Re: Display.getInstance().execute on android causes OS to suspend my app

2019-02-17 Thread shop . service . assistant
Thanks. On Saturday, February 16, 2019 at 11:26:50 AM UTC-5, shop.servic...@gmail.com wrote: > > If you are experiencing an issue please mention the full platform your > issue applies to: > IDE: NetBeans/Eclipse/IDEA NetBeans 8.2 > Desktop OS Windows 10 Pro > Simulator Latest > Device Android 7

[codenameone-discussions] Re: Display.getInstance().execute on android causes OS to suspend my app

2019-02-16 Thread Shai Almog
This is a core difference between the OS's. In some cases we hide those differences but in lifecycle it's really hard/undesireable to do so. Android is very aggressive about activity lifecycle. It suspends instantly, even does that on device rotation by default (we hide that behavior).