Wednesday, February 27, 2013

Chrome for Android Update

The Chrome team is excited to announce the promotion of Chrome 25 to the Stable Channel for Android. Chrome 25.0.1364.123 is currently rolling out to Google Play over the next few hours. This update contains a huge number of changes over the previous release, including:
  • Improved scrolling performance
  • Increased responsiveness to pinch-zooming on pages
  • Faster interactive pages thanks to the latest version of the V8 javascript engine
  • Audio now continues to play while Chrome is in the background
  • Expanded support for HTML5 features
  • Support for pausing audio in Chrome when phone is in use (note: this requires an additional permission)
This update also picks up other important stability and performance fixes since the last release, along with some minor UI adjustments. Known issues are available on the Chrome support site.

Interested in other release channels of Chrome for Android? A Beta channel is now available and can be run side by side with Stable. If you find a new issue, please let us know by filing a bug. More information on Chrome for Android is available on the Chrome site.

Jason Kersey
Google Chrome


Blogger Andrew Rabon said...

Finally. Thank you based Google.

10:42 AM, February 27, 2013  
Blogger Aaron Sentell said...

This was so long overdue. Glad to have it. I will be running the stable channel now. I'd appreciate it, if we could completely replace the Stable channel with the Beta channel (like we can on our computers). Then, I would go back to Beta.

10:51 AM, February 27, 2013  
Blogger Migman said...

Update Omahaproxy plz.

11:00 AM, February 27, 2013  
Blogger Unknown said...

Text autosizing does break the layout on all pages that care about it. This is a major drawback against the previous "stable" version. Chrome has now become generally unusable for mobile webdesign.

11:50 AM, February 27, 2013  
Blogger Hamza Gölyeri said...

Text on web pages become very fuzzy/blurry with this update. Sites that I was able to read without zooming in on my Nexus 7 become totally unreadable (ex. Chrome become unusable for me on my Nexus 7.

12:16 PM, February 27, 2013  
Blogger Sterling said...

Can't wait to try the audio cont. to playing while Chrome is in the background.

I hope you bring that to the beta channel soon!

12:23 PM, February 27, 2013  
Blogger Ronald said...

Is webRTC coming to the Chrome Beta for Android?

1:52 PM, February 27, 2013  
Blogger Josephine Benson said...

Why is it very difficult to be part of amazon publisher member.

3:24 PM, February 27, 2013  
Blogger Josephine Benson said...

With every step I've taken, am very glad to be a full member of

3:39 PM, February 27, 2013  
Blogger Ryan Walsh said...

Chrome 25 seemed to break the -webkit-animation: wiggle 0.2s ease-in-out alternate; featured on the logos of and Was that intentional? Do we need to change our code in a certain way to make the animation work again?

5:05 PM, February 27, 2013  
Blogger Paul C said...

Y is it that when I press the "home button" the audio(youtube through chrome) stops playing , what am I doing wrong?

5:05 PM, February 27, 2013  
Blogger Jason Jan Ngo said...

Thanks Hamza Gölyeri for your comment. Guess I should hold off on upgrading Chrome on my Nexus 7. I noticed the fuzzy text on the Chrome Beta. I thought it was just me.

9:48 PM, February 27, 2013  
Anonymous Anonymous said...

This comment has been removed by a blog administrator.

4:36 AM, February 28, 2013  
Anonymous Anonymous said...

Text on web pages become very fuzzy/blurry with this update. Sites that I was able to read without zooming in on my Samsung Galaxy Tab 2 7.0 become totally unreadable (ex. Chrome become unusable for me on my Samsung Galaxy Tab 2 7.0.

4:39 AM, February 28, 2013  
Blogger Julian Philpot said...

Can you explain why this new release needs access to the phone number of a remote caller? I can understand that it needs to know the phone state in order to turn off audio - but why does it need to know the number? Is this necessary?

5:03 AM, February 28, 2013  
Blogger Jo said...

Congratulations on this release! Looking forward to seeing Chrome for Android move along at the same rate as Chrome for Desktop!

7:18 AM, February 28, 2013  
Blogger SyP said...

Is it available for Android on Intel x86 phones too? I'm trying to update the wiki article , but I don't know how to distinguish between the Intel and ARM versions. Thanks!

7:32 AM, February 28, 2013  
Blogger Oskar Wróbel said...

Text become very blurry after this update. Also scrolling become more laggy and browser feels generally less responsive. (7 inch tablet RK3066 based; 1280x800 IPS display)

8:32 AM, February 28, 2013  
Blogger HyperCasinos said...

Text on a lot of pages has become too blurry to read since this update. No more Chrome for me (Nexus 7)

9:04 AM, February 28, 2013  
Blogger Grayson Carr said...

Font rendering is horrible now! Blurry as hell on my Nexus 4. Chrome for Android devs... Please get someone with half decent eyesight to help you. It's embarrassing for a core Google product to have an issue this serious.

9:45 AM, February 28, 2013  
Blogger Simon said...

This release is surprisingly bad. :( Font rendering is blurry and it's even more laggy!

12:40 PM, February 28, 2013  
Blogger andy said...

Blurry font rendering, certain sizes of fonts unreadable, when pinch resizing page for zoom in, certain elements on page do not get resized and stay static on display area.

Those elements are 'above' ther rest of the zoomed in elements, covering their view on screen.

Idk how this was released to stable. The devs must feel ashamed. But i trust that they will fix it sooner or later. N my wishes that things go smoothly for them => Nexus 7 4.2.2 here.

1:05 PM, February 28, 2013  
Anonymous Anonymous said...

Who's in charge of the chrome browser for android? It's so slow and laggy. Why can't it run smoothly and buttery with high spec phones? CONCENTRATE ON TOUCH RESPOND AND SCROLLING AND PINCH ZOOM. Do you test your browser before release? Oh and even worse, blurry fonts.

1:09 PM, February 28, 2013  
Blogger Davy Mo said...

The text is all blurred. I'm having to use another browser.

1:17 PM, February 28, 2013  
Blogger Pablo Santa Ana said...

I feel that the people working on Chrome for Android try their best to keep the address bar always visible, a "feature" that steals precious pixels on my Galaxy S3 screen. Until this "feature" is removed, I will keep using Android's nameless browser.

3:55 PM, February 28, 2013  
Blogger Pablo Santa Ana said...

As you scroll down the address bar should scroll up and out of view. This should be basic and intuitive. But no, I'm stuck with it, no matter what. At least give us a choice in the matter!

4:06 PM, February 28, 2013  
Blogger Ryan Hilby said...

To those who want to go back to the last update, follow these steps:
1. Go to settings and go under apps
2. Find Chrome and click on it
3. Then click on "uninstall all updates"

This made Chrome go back to the last update (at least for me) which solved the blurry text issue.
I hope this helps!!

5:50 PM, February 28, 2013  
Blogger Karthik S said...

Awesome update will try the features

12:00 AM, March 01, 2013  
Blogger dogsop said...

This Android release is seriously broken. On both my Nexus 7 and my phone I get nothing but blank pages for all sites.

1:25 PM, March 01, 2013  
Blogger Istimsak Abdulbasir said...

Exactly how is the ability to play audio while chrome is running in the background work?

8:32 PM, March 01, 2013  
Blogger Hosein Mansouri said...

Unfortunately Chrome 25 doesn't work on my Galaxy Tab Plus (Android 4)
With this error:
Critical functionality required to run Chrome is missing; either your Chrome installation is incomplete, or not compatible with this version of ...

9:16 PM, March 01, 2013  
Blogger Unknown said...

SyP: Chrome 25 is available for x86, but that doesn't mean it runs!

I realize Android x86 doesn't have many users, but it still is an officially supported platform (as announced on this blog).

Sadly it doesn't seem like this release was even tested on x86.

9:27 PM, March 01, 2013  
Blogger Positive ability said...

This comment has been removed by a blog administrator.

2:21 AM, March 03, 2013  
Blogger OnOff said...

It's a step back on my Nexus 7. Please fix the font.

6:04 AM, March 03, 2013  
Blogger Ganesh Hegde said...

This release breaks compatibility with x86 and Chrome force closes. It does not even open let alone work. Please fix this

11:21 AM, March 04, 2013  
Anonymous Anonymous said...

This comment has been removed by a blog administrator.

4:47 AM, March 06, 2013  
Blogger Ewejoko Balogun said...

This comment has been removed by a blog administrator.

11:19 AM, March 06, 2013  
Blogger Ewejoko Balogun said...

This comment has been removed by a blog administrator.

11:58 AM, March 06, 2013  
Anonymous Anonymous said...

This comment has been removed by a blog administrator.

12:46 PM, March 06, 2013  
Blogger Vašek Stodůlka said...

This release is so slooooow, in contrast to previous version. Even 18 was not somehow magically fast, but it was usable, now I am waiting 30 seconds to load page (on fast WiFi), which Opera Beta loads in 2 secs. I didn't have Opera installed before this update, I just downloaded it to compare responses and I must say, this WebKit Opera Beta looks more or less like Chrome, feels like a Chrome (not like Opera Mobile, which is weird), but is definitely faster!

Dear Chrome developers, please revert Chrome to previous version on Google play, download Opera Beta, try to compare rendering times with it (it uses the same WebKit core) and release next version of Chrome when you achive rendering at least 2 times Opera or better, thanks. Your "potato chrome" youtube videos looks like a bad joke now.

Yes, and the fonts are blurry. :-)

12:56 AM, March 08, 2013  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home