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
POST A COMMENT

187 Comments

View All Comments

  • zorxd - Thursday, January 19, 2012 - link

    And what exactly is more efficient? Reply
  • c4v3man - Thursday, January 19, 2012 - link

    Their implimention of pseudo-multitasking as opposed to the much more flexible multitasking in Android. Reply
  • erple2 - Friday, January 20, 2012 - link

    Bingo!

    Since the iOS can't do "true" multitasking, primarily as a design decision on Apple's part to greatly improve battery life (seen the battery life numbers on WebOS? They're pretty terrible), the requirements for memory are generally quite a bit lower than for Android.

    You could argue all day as to which one is better, and still not come up with a clear winner. This is strictly due to the phone form factor. Given the limitations on usable screen size (can't display 2 apps at once reliably), and that you have to rely on battery life, the argument of which is "better" is more difficult to make. These all disappear when power is no longer a serious concern (desktop), nor physical screen display (notebook through desktop).
    Reply
  • zorxd - Friday, January 20, 2012 - link

    yeah and DOS is better because it works fine with only 1MB RAM. Reply
  • OCedHrt - Friday, January 20, 2012 - link

    Which is fine due to fast app switching. Reply
  • geekfool - Sunday, March 04, 2012 - link

    Not quite sure how memory management is that different as they both have very similar multitasking management: Active task gets priority, background tasks stay in memory (to be faster to come back, for example a messenger), and tasks no longer in the foreground (that are typically) are put in "stasis" and blown away if the system requires more RAM.

    Memory management can only do so much before you need more. A large game with 768MB of textures will requiring more loading and swapping if it has 512MB RAM compared to one with 1GB. Do remember that not all of it is available for use; the OS will usually take a large chunk.

    Android users might require more RAM simply because it's doing more. For example, the homescreen can be as complicated as TSF Shell or SPB and / or a live wallpaper -- both of which needs to be kept in memory so that pressing Home is extremely responsive and not "loading, please wait...".
    Reply
  • geekfool - Sunday, March 04, 2012 - link

    TSF Shell:
    http://www.youtube.com/watch?v=SYzYQ6YtepU

    All those fancy widgets, animations, rotations, will require much more RAM than a simple grid of 20 icons.
    Reply
  • trob6969 - Wednesday, January 18, 2012 - link

    You didn't have to sacrifice GPU performqnce for a 4.3 inch 720p HD display. You could have done what i did and got an htc rezound. I downloaded Dead space, which is probably one of the most GPU demanding games for a phone, and gameplay is FLAWLESS on it! ZERO choppiness throughout the game. My rezound plays this game just as smoothly as my playstation 3. That says a lot about a phone's performance. Reply
  • metafor - Wednesday, January 18, 2012 - link

    Note that with the increased clockspeed to the SGX540, the OMAP4460 matches the GPU performance of a Snapdragon S3 (used in the Rezound).

    Both chips perform similarly with the CPU clock at 1.2GHz (compare Sensation 4G to GN, for example).
    Reply
  • dwang - Wednesday, January 18, 2012 - link

    Deadspace runs perfectly fine on the galaxy nexus. No choppiness or slowdown. Reply

Log in

Don't have an account? Sign up now