When we receive a push notification on Android, we cannot assume that Fennec is running. According to Brad, we're planning to use GCM on Android. Presumably we're going to have some kind of Android background service for receiving the messages from GCM. Once we have the message, we will need to start up Gecko and deliver the information about the push to Gecko so that it can wake up the right service worker. We don't necessarily need a Fennec window at that stage, but the SW may want to open a window, so we need to be able to open one very quickly. Snorp, can you please find the right people on the mobile team for this? Thanks!

I started working on this a while back in bug 834033 and mostly had it working. Should be reasonably easy to get it going again. I'll just take this myself.

Bug 1179015 covers the GCM bridge. Morphing the subject to be more specific, given that we'll be using push notifications for several things that don't involve running Gecko.

Such mechanism is also required while handling persistent notification: while a item in notification center is clicked, there is no guarantee that Fennec is running too.

The proper way to wake up a service worker seems to change a lot.

As long as ServiceWorkerManager works the same, e10s redesign won't affect this.

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.