Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
[Meta] Enable Battery Saver settings #240
Goal: Provide an app that saves storage on the device and is battery efficient (GV)
@st3fan this is the list I have of things we have discussed that could potentially create battery savings:
There was also some discussion around things we might not being optimizing on the platform side because we haven't been thinking about them primarily from an energy saving perspective. This included some discussion around maybe more aggressively caching things to avoid using the radio.
I guess I misunderstood the feature based on older discussions. We'd mentioned removing native apps and replacing them with PWAs or web apps. Also, we seemed to indicate we'd somehow measure the benefit of various steps, which is tremendously hard on Android.
The list you mention doesn't seem too difficult, but there's the overhead of keeping extra code branches across the app. We could probably handle this type of configuration with the component architecture we have planned-- the same way we're handling layout A/B experiments.
This was referenced
Jan 25, 2019
Some suggestions on power saving
I think animating, scrolling and flinging use quite a lot of CPU power (GPU in the case of WebRender). You could reduce layout.frame-rate to 30 fps. (I think Firefox Desktop is talking about doing this on low power machines but to speed things up not save battery???).
IIRC my previous Sony Xperia phone had "Stamina" mode which I think downclocked the GPU and limited the frame rate, on Android native animations at least. It got quite janky.
A guess but...
Most phone CPUs have some kind of big.LITTLE architecture. The big cores will likely use more energy for a given task than the LITTLE cores, but will do the task faster. Is it possible to force a phone to use only its LITTLE cores for page load, JS etc? Even with no big.LITTLE, energy consumption should drop somewhat with a bit of downclocking, so e.g. a CPU limited to say 1500 MHz might use a bunch less energy than clocked right up to 2000 MHz.
For example, you might see 30% longer page loads by doing this, but get but 20% power saving. Or something. No idea if it's practical.
My Galaxy S7 has a power saving mode which allegedly reduces the CPU speed.
Doubt it's possible but again GPU workload could be reduced by forcing the phone to use a lower resolution. I doubt you can do this app by app, it's probably a system wide setting. Again my Galaxy S7 has a power saving mode which reduces screen resolution to HD.
No idea if it's any help!
We decided on March 15 that we will take individual features out of the batter context, add them individually and in the future, in "past MVP" versions, we might bundle it all back together, once we have all instrumentation in place and data gathered to make a claim how these individual features can and will save battery.