Closed Bug 446418 Opened 14 years ago Closed 4 years ago

[meta] Investigate power management issues


(Firefox for Android Graveyard :: General, defect, P2)



(Not tracked)



(Reporter: dougt, Unassigned)


(Depends on 7 open bugs)


(Keywords: helpwanted, meta, mobile)

It may be a good idea to suspend flash, animations, javascript, periodic network downloads, during idle time to conserve battery life.
Flags: wanted-fennec1.0?
Flags: wanted-fennec1.0? → blocking-fennec1.0+
Priority: -- → P2
Target Milestone: --- → Fennec A4
Depends on: 448544
Depends on: 448545
Depends on: 449033
it isn't clear how best to implement power saving mode in fennec.  any help or
input appreciated.
Keywords: helpwanted
Can we use appShell->SuspendNative/ResumeNative for it? at least it should stop native event loop, javascript/downloads/animations...

I want to do as little as possible.  When system-idle event is given to our application, does the system suspend us -- does it prevent us from running, or makes us run slower/ get less time ?
I don't think that system do anything special, I think it is just notification which handled (or not) by other applications..

Assignee: doug.turner → nobody
We should get rid of permanent UI timer callback see bug 508518
Depends on: 508518
I think we should care not only about "system-idle" state, but also about default state when window is visible, and simple https/https page rendered (no active page internal JS timers).

Also background DOM windows must not do any unnecessary activity, painting, image animations, also some Javascript suspension required, if possible without breaking JS pages.
Depends on: 518788
Depends on: 518802
Depends on: 518804
Depends on: 518805
Depends on: 519173
Depends on: 526715
Depends on: 526718
This is a mass change. Every comment has "assigned-to-new" in it.

I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.
Depends on: 571394
Is there plans on how to resolve fennec use-time issues? Two different approaches are suggested: suspending/throttling on process level(bug 568054) or suspending where needed. Probably both of these are needed, but how is are those going to be implemented? Is there going to be some "idle-state" when all activity of the browser is going to be suspended? Will there be different states for suspending animation, javascript, checkers and so on? On unix side there are notifications like: "system-idle", "system-active", "system-display-on", "system-display-dimmed-or-off". Should these be used for all the mobile platforms also, like Meego, and implement suspending of different parts according to those and maybe some other notifications also? Is this a correct bug to talk about this or is there already a better meta bug or should that be created?
I think that we first need to get a good picture of the OS situation - what the OSes provide in terms of application lifecycle, what is expected from applications in the various states of the lifecycle (active, minimized, closed, background, etc.).

For example, there are good docs for Android about this:

We need something similar for Maemo/MeeGo, and can then start to plan how to tackle this topic.
Depends on: 604527
Depends on: 604804
Depends on: 608440
Keywords: meta, mobile
OS: Mac OS X → All
Hardware: x86 → All
Summary: Investigate power management issues. → [meta] Investigate power management issues
Target Milestone: fennec1.0b2 → ---
Depends on: 672356
Depends on: 673352
Depends on: 679923
Depends on: 407325
Depends on: 506975
See Also: → 978857
Bug 978857 will introduce a module that will make it easier to write tests for these, FYI. As of now only FxOS has the ability to spoof the battery (in marionette)
Closing all opened bug in a graveyard component
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.