Friday, February 24, 2012

Chrome for Android Beta Update

Chrome for Android Beta has been updated to 0.16.4215.215, picking up changes that have gone in through Chrome 16.0.912.77.  Beyond the Chrome changes, this update contains:
  • Android Beam support - now beam URLs from Chrome to other devices with NFC.
  • Support for additional countries
  • Compatibility checks to ensure system prerequisites for Chrome are met
  • Essential bug fixes
Known issues
  • 112923 : No way to toggle between mobile/desktop UA
  • 113140 : Youtube Links Do Not Prompt For Which Application to Use
  • 113132 : Chrome for Android beta doesn't support configured proxy in wi-fi settings
  • Other notable issues listed here
If you find a new issue, please let us know by filing a bug.

Srikanth Rajagopalan
Google Chrome

33 comments:

Alexander Kuzmin said...

Nice update! It available in Russia now! But some pages looks wrong, for example, left black menu crops in this review on my Prime dfter scroling the page: http://www.theverge.com/2011/12/1/2601558/asus-eee-pad-transformer-prime-review

Brendan said...

This update breaks compatibility with a lot of custom 4.0 roms.

Brian Graham said...

Like what Brendan said:

I'm not sure if this is a Chrome issue or a CM issue, but Chrome does not see my CM9 install as ICS, even though it's Android 4.0.3.

TheAlp said...

Has the bug that caused market links to be opened in the browser been fixed?

Aaron said...

You forgot "Drop support for non-Nexus devices running ICS."

Kind of important, that one.

Brian Haslip said...

It already didn't work on Gingerbread devices. I don't know why you guys would go out of your way to break compatibility with CM9 and other custom ROMs.

Really love Chrome on Android, but if running CM9 means I can't use it, then I'll just go back to Dolphin.

Alexis Cirmi said...

Same here, broken on Defy CM9 :(

AD said...

"Compatibility checks to ensure system prerequisites for Chrome are met". Thank you, that is a very important feature, I missed it in the previous beta, now I miss Chrome because I won't install on CM9. How you will continue to be focused on the most important features like this one because we know that resources are limited (sarcasm)

TheAlp said...

Chrome runs fine on the custom rom I'm running (AOKP M3) and I heard someone with a leaked rom on a sensation had it working fine too.

Matt said...

I'm back to the stock browser because Chrome no longer supports all Android 4.0+ devices

Major letdown

Macs said...

I like it but it's not smooth at all on my Galaxy Nexus. Typing a search on omnibar is really sluggish for example. It needs more work guys

Kyojin said...

Hi!

For you guys who are complaining about Google dropping custom ROMs support, that's not true.

I have a Samsung Galaxy S running CM9/Android 4.0.3, and also faced the "error" message when running the new version of Chrome. But when I looked a little bit deeper into the problem, I discovered that it is a ROM issue, not really Google's or Chrome's fault.

The problem was that the ROM had "Gingerbread" as a build ID + fingerprint, that's why Chrome wouldn't let me use it. Now I changed it to IML47K and everything is running fine, i.e. Chrome running on a CM9 custom ROM.

So if you have this issue, don't blame Google, instead, wait for a "fix" from your ROM developers.

DR said...

lets see..who is running ics and not impacted by the cm9 compatibility issuesm 3 nexus users!! ha

jrr said...

Was gingerbread being let in before? Honeycomb? (Does the new behavior help more than it hurts?)

I'm now wishing market offered access to old versions.

Beano311 said...

The issue is with the new version not working on CM9 based roms is because CM9 uses a gingerbread fingerprint. It's not google's fault, it's CyanogenMod's...

Russ said...

It is Google's fault, there was no need to implement this.

c0z said...

Any chance for support on devices running versions of Android older than ICS?

Jarosław Pietras said...

lol stil not for 2.3

Andy said...

Yes guys. If you're on a custom ROM just change your build.prop. I'm on the CM9 alpha for Captivate by Teamhacksung, and I changed the ro.build.id from GINGERBREAD to IML47K and Chrome works just fine.

If you're not comfortable messing with your build.prop, wait for your ROM dev.

Jason said...

Thank you Andy. That worked perfectly.

Andy said...

Glad it worked. Credit should actually go to Kyojin, who mentioned it first. I just wanted to clarify exactly where to edit it for people.

Fatih Yılmaz said...

why do you ignore the number of Android user in Turkey ? I mean we are the 72 million people and at least 2 million people use Android and we dont even use Google Chrome , that's really sad , you know , being ignored is really sad.

Jay said...

Love Chrome on Android! Works great on my nexus and on my gtab I just had to modify build.prop as suggested. Thanks!

Patrick Archibald said...

Latest update prevents it from running on CM9.

Andy said...

Patrick, read a few posts above. It's easy to fix.

apatkinson said...

One feature it is missing is saving a link. When you visit a page with a link to an mp3 file, and you would like to save it to the device you cannot. this feature is enabled in the stock ICS browser with long press on the link.

Paul said...
This comment has been removed by the author.
jwmaag said...
This comment has been removed by the author.
Dark said...

This update makes the application stop to work in Xperia Arc S with ICS build (Kernel 2.6.32.9 and Android 4.0.3)

deepakw3c said...

Intersting and beautiful blog lovely presentation thanks for sharing your views

Avast Antivirus Support
Avast support
Panda Antivirus Support
panda tech support

ocs123 said...

You may also interested in gucci bags from another gucci outlet shop.

pk_android said...

Hi,
Where can I get source for this update of 0.16.4215.215 so that I can build on NDK

Carlos Silva said...

Still not Portugal in the list... oh well, looking for a download location :/