898969 - New apps are regularly running when I unlock the device

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia, defect)

Description

[Matthew N. [:MattN]]

I don't have steps to reproduce but many times this week when I unlocked the device using my pin, an unexpected app was in the foreground (often one that I know wasn't running since the last restart).

Today I had cost control in the foreground but I hadn't used that app yet today. I would guess touch events are still going to the homescreen in some cases when they shouldn't e.g. from the lock screen or when the display turns off.

Unagi/1.1.0/beta
Build: 20130719070225

Comment 2

[Jason Smith [:jsmith]]

See the dupe for STR. Looks like a regression with two confirmed reproductions.

Comment 3

[bhavana bajaj [:bajaj]]

This may impact battery life if apps keep running in background and this is a confirmed regression, leo+

Comment 4

[bhavana bajaj [:bajaj]]

needsinfo on Lucas and Dylan to help pass this on to right team for investigation.

Comment 5

[bhavana bajaj [:bajaj]]

Gregor, can you please help find someone who can take a look at this ? Dylan suggested i could reach out to you for help

Comment 6

[Gregor Wagner [:gwagner]]

Is it always the same app or do you see random apps after unlocking?

Comment 7

[Matthew N. [:MattN]]

I had it with cost control and calendar. There are STR in the dupe but I haven't verified it.

Comment 8

[Gregor Wagner [:gwagner]]

(In reply to Matthew N. [:MattN] from comment #7)
> I had it with cost control and calendar. There are STR in the dupe but I
> haven't verified it.

I think they are known and we decided to accept this.
Calendar does synchronization in the background and opens the app.
James, is this expected behavior?
Cost control might be similar. I don't know who owns const control.

Comment 9

[James Lal [:lightsofapollo]]

Yes that sounds about right- However when we implemented this functionality there was no way for an app to close itself (early 1.0.0 era). We can optimize this by launching the app only when needed then closing itself if notifications are not clicked.

Comment 10

[Jason Smith [:jsmith]]

(In reply to James Lal [:lightsofapollo] from comment #9)
> Yes that sounds about right- However when we implemented this functionality
> there was no way for an app to close itself (early 1.0.0 era). We can
> optimize this by launching the app only when needed then closing itself if
> notifications are not clicked.

Okay. Then I was mistaken with the nomination here - this isn't a new 1.01 regression. It's probably a performance issue, however.

Comment 11

[Mason Chang [Inactive] [:mchang]]

From comment 8 and 9, looks like this is expected behavior. Please reopen if this becomes an issue.