Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Android Chrome The Internet

Chrome 52 for Android Arrives With Smoother Video Playback, Faster Load Times, and Better Battery Life (venturebeat.com) 28

An anonymous reader shares a VentureBeat report: Following the release of Chrome 52 for desktop two weeks ago, Google last week also launched Chrome 52 for Android. For whatever reason, the company didn't share what's new until today. You can download the new version from Google Play. Chrome 52 for Android makes video playback feel smoother, load faster, and consume less battery. More specifically, video playback has been improved for speed and power efficiency, meaning you should expect smoother playback and faster load times (so videos will start playing sooner, instead of pausing briefly before starting). Your Android device's battery should also last longer if you consume a lot of videos online. Last but not least, video in Chrome for Android also now works with Data Saver Mode. This means a lightweight version of the video will be downloaded and played if you have Data Saver Mode on, saving you as much as 50 percent in data downloads, by Google's estimation.
This discussion has been archived. No new comments can be posted.

Chrome 52 for Android Arrives With Smoother Video Playback, Faster Load Times, and Better Battery Life

Comments Filter:
  • Great to know about new stuff they are bringing, but what about hangout hogging memory and CPU like crazy? (During summer, in many countries, the hangout has caused thermal shutdown of my laptop.)
  • because 52 [slashdot.org] > 48 [slashdot.org]!
  • Google last week also launched Chrome 52 for Android. For whatever reason, the company didn't share what's new until today.

    I wouldn't install an update if I had no way to see what's changed. I suppose people didn't have a choice in the matter though, if it was Chrome on Android.

  • With 50 and 51, one could preview the new media by turning on a chrome://flags setting. That setting is now default 'on' instead of off with 52. With html5 audio tag, it fixes a lot of streaming issues with constant bit-rate files (duration wouldn't update, and you'd not get an 'end' event when the song finished, things that worked fine for variable bitrate files), issues that were also in the webview as well. So those web apps that need html5 audio tag will work much better, and phonegap/cordova apps will

If all the world's economists were laid end to end, we wouldn't reach a conclusion. -- William Baumol

Working...