If you're running the Chrome Beta on your Android device, prepare for an update. Chrome v32 is rolling out to the Play Store, and it includes a few improvements and fixes. Being a beta, there are also some known issues to be aware of.

2013-11-21 15.29.23

Here's the good stuff from Chrome 32 for Android:

  • Application shortcuts: Ability to add shortcuts to home screen is back
  • Vibration API: An API that allows web apps to make devices vibrate
  • 285066: Reenabled canvas anti-aliasing

And the not so good:

  • 319983: Lots of background color when scrolling up and down on pages
  • 320094: [M32/M33] Double tap drag zoom gets stuck sometimes
  • Some known crashes

If you want to try the Chrome Beta, use the link below as it won't show up in searches. There are usually a few bugs like the ones listed above, but you get new features before the stable channel.

[Chrome Blog]

Ryan Whitwam
Ryan is a tech/science writer, skeptic, lover of all things electronic, and Android fan. In his spare time he reads golden-age sci-fi and sleeps, but rarely at the same time. His wife tolerates him as few would.

He's the author of a sci-fi novel called The Crooked City, which is available on Amazon and Google Play.

  • schloppyloppy

    Is anybody else on Kitkat getting Chrome to lock up whenever you try to type something in the Omnibar?

    • Ryan

      Nope, not over here.

  • George Bakos

    There is an issue with the nexus 4 running GEL and KitKat. When you make a shortcut it redirects you to the Google Now home screen and the shortcut is created in the stock launcher. In order to see the shortcut in GEL you have to select another launcher, swipe the GEL launcher from the recents tab and reselect the GEL launcher.

  • captainkirk

    Nice to see that they brought back Ability to add shortcuts to home screen

    • ddpacino

      I disable this. Clogs up my menu over there.

  • mateor

    Interesting experiment in Chrome 32 that checks to see if old infrastructure that supports the web breaks TLS 1.2 ( successor to ssl). If the TLS 1.2 protocol is maintained, then we may see some progress towards some more secure cipher suites using ChaCha20-Poly1305 and AES-GCM.

    The more security conscious companies are already moving to those ciphers but the rest of the web doesn't always follow suit. RC4 is pretty old at this point and has a couple of known deficiencies (even if they are hard to actually carry out).

  • Luis

    That would be great if Google fixed the lag and stutter while scrolling. That is a random bug on my former Galaxy Note II AND the NEXUS 7 2013.

    • ddpacino

      Scrolling seem perfectly fine on my Nexus 4, on latest kit kat

      • Luis

        Yep... It seems.. But when you read a lot of content and you constantly scroll down and up to fit the screen, mainly small movements, the issue shows up randomly. It's like it stutters for less then a second. That behavior does not happen on the iPhone. Only on Android and Chrome. The scrolling behaves like it wanted to be in that position and you have to insist in the same action to make it work. Google doesn't like to fix random bugs related to usability. This is usually a second thought for them, which is sad, because people do see that. They just are not good at explaining the issue and so just call Android "laggy" in general.

  • Oliver Baker

    Urghh they took away the new tab button AGAIN! Whyyyy. :'( I'm running KitKat on a Nexus5 btw.

    • ddpacino

      The New Tab button? I havent seen that for a few updates. It seems off without it, and thought it was something I could enable in flags -- Nope!

      • Oliver Baker

        It was on the previous update for me.. I was so happy that it was back, but now it's gone again. Yeah it should really be in the flags (kind of like the new new tab page is)

  • joshtownsend

    No new tab button sucks

    • Matthew Fry

      Eh. I'm not that worried about it with the pull on address bar thingy.

  • Sandesh

    How do some peole have the new tab button on the stable version of chrome? I only had it when 31 was still in beta, but not after it became stable, and couldn't find it in the settings.