ubuntu-phone team mailing list archive

[Rodney Dawes <rodney.dawes@xxxxxxxxxxxxx>]

On Wed, 2014-06-25 at 17:10 -0300, Sergio Schvezov wrote:
> On miércoles 25 de junio de 2014 16h'29:10 ART, Rodney Dawes wrote:
> > On Wed, 2014-06-25 at 14:44 -0400, Marc Deslauriers wrote:
> >> On 14-06-25 02:11 PM, Rodney Dawes wrote: ...
> >
> > No. It means the app is running, whether it is in the foreground or
> > background. It doesn't need to be the current foreground app. Running
> > apps, the automotive data logging app I linked, etc… continue running
> > even in the background, to be able to monitor location, log performance
> > data from BT/ANT+ devices, and perform actions based on location or the
> > data stream from a connected device.
> 
> Please take the time to read the full length of the document I linked to.

The Apple doc? It clearly indicates to me that long-running background
processes remain running.

I think maybe there is some confusion in this thread about what
"running" means. A sleeping/stopped process is still running and has a
PID. A killed process is not running. Apps which do not register
themselves as long-running background processes will certainly be
stopped indefinitely, or killed on iOS.

However, it is not clear to me if iOS is actually stopping processes, or
if they are just sleeping and waiting for the main loop to send an
event, when they are registered for long-running background processing.
It is clear that it does wake the process and call a callback in that
process, depending on the task it is registered for, though.