El 23/05/14 15:31, "Pipo Koenig" escribió:
>I cannot see how the mozAlarms approach could work.
>When I add the alarm from within the app that gets eventually killed,
>then the message handler for the alarm gets killed as well and will never
>be called, right?
When you are adding an alarm (ima
> Could you potentially use mozAlarms to wake your app up in case it gets
> closed? This is what we do for calendar to synchronize events with the server.
>
Thanks guys,
I cannot see how the mozAlarms approach could work.
When I add the alarm from within the app that gets eventually killed, the
-...@lists.mozilla.org
Sent: Thursday, May 22, 2014 2:24:48 PM
Subject: [b2g] Prevent app from being killed
Hi there,
I'm quite new to Firefox OS. At the moment I'm struggling with implementing
some kind of a "service" that listens for geolocation updates in the background.
On 22/05/2014 20:02, Pipo Koenig wrote:
Thanks, but sorry, I don't get it yet. So the app has to listen to a system
message? Which one should that be?
That's something I have to figure out myself :)
And is there a lifecycle event that notifies the app that it is about to be
discarded? I'm n
> requesting a wake-lock alone is not enough to keep your app alive, you
>
> also need to be waiting for some kind of system message and I'm not sure
>
> if the geolocation service counts towards that.
Thanks, but sorry, I don't get it yet. So the app has to listen to a system
message? Which
On 22/05/2014 13:24, porschekoe...@googlemail.com wrote:
I'm quite new to Firefox OS. At the moment I'm struggling with implementing some kind of
a "service" that listens for geolocation updates in the background.
If there are lots of other apps running at the same time mine seems to be
killed
Hi there,
I'm quite new to Firefox OS. At the moment I'm struggling with implementing
some kind of a "service" that listens for geolocation updates in the background.
If there are lots of other apps running at the same time mine seems to be
killed by the system. When I debug with App Manager it
