- May 16, 2013
- 1,777
- 0
- 0
I have been setting the Chrome Data Saver toggle to On by defualt ever since it appeared in the browser. Whenever I re-install a new flavor of Chrome, I make sure that's on. The percentages I see displayed as data saved has made me think it's worthwhile.
Recently I turned Data Saver off. It dawned on me that this is the sort of setting that could be draining battery more than it otherwise would. Because Chrome of any flavor is usually a pretty big battery consumer, I figured testing it out would be worth the time.
I haven't documented the drain percentages in any fixed form, but have been noticing anecdotally. It seems there is a slight decrease in the amount (or percentage to be more accurate) of Chrome usage in my battery stats. Where 3-4% seemed to be most common, which usually put it atop the apps list, just after Screen, Android System and Kernel (Android OS), I've been seeing it top out at around 2% since turning off Data Saver.
Has anyone else ever tried this comparison or seen other info on it? I'd think especially if you're on WiFi a good deal of the time, it may be worth trying for yourself.
FYI, I'm currently using the latest version of Chrome Dev.
Recently I turned Data Saver off. It dawned on me that this is the sort of setting that could be draining battery more than it otherwise would. Because Chrome of any flavor is usually a pretty big battery consumer, I figured testing it out would be worth the time.
I haven't documented the drain percentages in any fixed form, but have been noticing anecdotally. It seems there is a slight decrease in the amount (or percentage to be more accurate) of Chrome usage in my battery stats. Where 3-4% seemed to be most common, which usually put it atop the apps list, just after Screen, Android System and Kernel (Android OS), I've been seeing it top out at around 2% since turning off Data Saver.
Has anyone else ever tried this comparison or seen other info on it? I'd think especially if you're on WiFi a good deal of the time, it may be worth trying for yourself.
FYI, I'm currently using the latest version of Chrome Dev.