Maybe I'm being dense here so forgive me. But if Chrome is proving such a battery drain surely just use an alternative browser until Google fix it?
Yes sorry I did try other browsers so it seems browsing per se causes the drain, maybe Lollipop itself is the issue.
The problem is the configuration of the cpu governer. It ramps up to high speeds far too quickly in response to very light loads. It also throttle up to 1.5ghz in response to simple touch inputs. That is the reason you see such huge useage while browsing as you are constantly scrolling and reading, all the time using the touch screen. The governor won't allow the cpu to throttle back after the touch input finishes and it just sits there. Your graph shows it perfectly, even when cpu load drops to about 15-25% the cpu speed stays at a pretty consistent 1.5ghz level the whole time.
People reporting good battery life appear to be mainly using it for watching video where there is little to no input for hours at a time leaving the cpu sitting in its lowest power state while the decoding is handled on another part of the soc.
We are not going to see an improvement without major configuration changes to the base kernel as it controls all of the cpu power scheduling and there has been no changes in any of the ota updates.
plausible comment from xda poster
Last edited:
