The Keyboard

The stock Gingerbread keyboard was a significant step forward, but the ICS keyboard is really good. I don't know that there's much that's truly groundbreaking about the ICS keyboard, but it's at the point where short of Swype for those users who care about it, I would be very disappointed to see any third party keyboard replacements from HTC, Motorola or Samsung.

The basic layout hasn't changed from Gingerbread, although there are a few subtle differences. You get the same standard four row keyboard with two alternate modes (numerics and symbols). Where the Gingerbread/ICS keyboards differed from the standard iOS or Windows Phone keyboard is there's a fifth row of punctuation keys by default above the rest of the keyboard. This fifth (or first, depending on how you look at it) row actively changes into a list of predicted words. The word in the center is what the autocorrect engine believes you're typing, while the words on the left/right are alternates. While Gingerbread allowed you to scroll horizontally on this row, the items are fixed in ICS. As a consolation, you can bring up additional autocorrect suggestions by tapping and holding on a word in the prediction row. Accented characters are available by pressing and holding on keys that can be accented. Popup menus also exist for punctuation and the smiley key.

Keypresses are still accompanied by a magnified duplicate of the key itself. Unlike in Gingerbread where the magnified key hovered unconnected, the ICS keyboard connects the magnified key to the key itself. In my opinion this makes the keyboard look less chaotic when you're typing very quickly. Rather than giving the impression of random letters flying around everywhere, the animation serves its intended purpose better: letting you know what you just hit.

 

There's also a hidden Android Keyboard debug settings pane with some different themes that can be selected. 

Gingerbread vs. Ice Cream Sandwich - Keyboard & Autocorrect
  Gingerbread Ice Cream Sandwich
Keyboard

Quick Punctuation

Autocorrect
Autocorrect

Facial Recognition

Android has historically offered multiple options to secure your phone or tablet. Ice Cream Sandwich continues the trend. You can choose a basic PIN with a minimum of four numbers and a maximum of 17. There's an alphanumeric password option, simple slide to unlock and no security at all. ICS adds a new option to the list: Face Unlock.

The feature is exactly what it sounds like. ICS can store a photo of your face and use it as authentication for unlocking your device. While you only need a single picture to start, Google recommends taking multiple photos in different lighting conditions, with/without glasses and with a clean vs. unshaven face if applicable. As a backup you have to provide ICS with a PIN in case it can't recognize your face (either due to lighting conditions or because of a recent tumble down some stairs).

Google warns that someone who looks like you would be able to unlock your device, making Face Unlock less secure than a long PIN, pattern or password. Admittedly a thief would have to either be really lucky or know what you look like to fool the technology, but it is a valid point.

The feature actually works surprisingly well in practice. With Face Unlock enabled the lock screen has a front facing camera live view window that you're supposed to use to center your face. With the exception of really bright (with the light shining into the camera) or really dim scenarios, Face Unlock worked for me almost every time. When it works perfectly using your face to unlock the phone is extremely quick. In the right conditions I've seen ICS unlock itself a split second after I even saw my face on the screen. On average though the process is slower than typing in a PIN or using any of the other unlock methods. Furthermore, if you use your phone a lot at night (especially in cars) you have to hit the power/lock button then tap the lock icon to circumvent Face Unlock and go directly to your PIN/password/pattern. Finally, don't try to use Face Unlock to unlock your phone while driving - that's a recipe for bad, or worse, death.

The UI: Holo Evolved The Browser
Comments Locked

185 Comments

View All Comments

  • gamoniac - Wednesday, January 18, 2012 - link

    The article is co-authored, yet I keep seeing the use of "I" as the pronoun in sentences throughout. As a daily AT reader, I find it a bit awkard when trying to put a face to the article. I like the writing style; it just bugs me when I can't figure out whether it is Anand or Brian who is making the statement that I am reading. Perhaps the use of "we" makes more sense?

    Thanks. Great work as usual.
  • Omid.M - Wednesday, January 18, 2012 - link

    As an editor, I agree with this comment.

    It's not a huge deal, but it's nice to see:

    AL: I think that...

    BK: I disagree with Anand, but...

    Just don't do it everywhere because it'll seem like an interview.

    Anand,

    The videos have been the best new thing AT has done in a long time. Thanks! Good to put faces to names, even better to add voices. Next, comment system ;)

    @moids

    -Omid
  • bjacobson - Wednesday, January 18, 2012 - link

    Perhaps writers at Anand should be required to speak in terms of The Collective.
  • Brian Klug - Thursday, January 19, 2012 - link

    This is definitely something we've struggled with in the past and admittedly continue to struggle with. Most of ICS is Anand (though we collaborated and always wind up agreeing about most things), then the hardware and onwards is myself.

    Think of us as a hivemind (or collective) and the problem goes away :P

    -Brian
  • Zoomer - Thursday, January 19, 2012 - link

    Or write in 3rd person like a technical paper. Though that can be boring to read.
  • just4U - Friday, January 20, 2012 - link

    "Think of us as a hivemind (or collective) and the problem goes away :P
    -Brian"

    ------

    It does NOT!! Ok, which bonehead asimilated Brian & Anand? There goes the neighborhood (...grin)
  • thebitdnd - Wednesday, January 18, 2012 - link

    I've had my GNex since the day after launch. It surpasses any experience I've had with a smartphone (including HTC Incredible, iPhone 3GS, and a HTC EVO) as a web browser and mobile computer device, but the single complaint I have is with using it as a...(wait for it) PHONE.

    I've had over a dozen calls now where I'll be conversing away and all of the sudden my microphone cuts out and the other person can't hear a word I'm saying. The call is still connected and I can hear them just fine, but I have to hang up each time and call them back.

    Google directed me to Verizon, Verizon says it's a Samsung/Google problem, but I've been assured it's a software problem and there will be a fix in 'an upcoming update'.

    As much as I like the hardware and software, not making reliable calls is a real kick in the junk for a smartphone.
  • jalexoid - Wednesday, January 18, 2012 - link

    Well, what did you want with CDMA or LTE? No bugs?
  • mhaager2 - Wednesday, January 18, 2012 - link

    Great review as always Anand. My only criticism is that it felt like it took you a very long time to get this review out compared to how quickly the iphone 4S review came out. I think your comments about the hardware are correct; its certainly not leaps and bounds ahead of other phones. Being my first phone since the iphone 3G I do wish it was more bleeding edge to future proof it a bit. However it actually works very well, both as a content consumption device, as well as (gasp) as a phone, and I just love, love, love that fact that its penta band. Now when I visit the US I no longer have to endure the legal extortion that used to be the norm with carrier locked devices. That feature alone makes this phone better than any other out there,, old GPU and all.

    Has anyone overclocked this to its 1.5 ghz spec? I wonder if there is any appreciable differerence and what the battery life trade off is.
  • tipoo - Wednesday, January 18, 2012 - link

    I can only speak from my experience with my Nexus S, but the max CPU speed has little battery life impact compared to the impact the CPU governor does. 1.3GHz with the Lazy governor (available in Trinity Kernel) lasts longer than the stock 1GHz on OnDemand.

Log in

Don't have an account? Sign up now