Display.getInstance().execute on android causes OS to suspend my app

[shop.servic...@gmail.com]

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 & 8.1

My app uses Display.getInstance().execute(file system path to PDF doc)

On Android, my app receives a suspend signal from the OS until I close the PDF reader app.

Once the PDF reader app is closed, my app receives a start()

This does not occur on IOS,

Curious, Is there a method that my app can envoke another process and not suspend my app?

Thoughts?

[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). However, we don't know if you might press the home button from the PDF viewer so we can't "fake it" as we won't get another stop() event.

[shop.servic...@gmail.com]

Thanks.

[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

[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.

[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.

[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.

[Mark Bolduc]

Fair enough.

thanks.

Do you think this behaviour will go away when these devices have more processing power?

Regards.

[Mark Bolduc]

[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.