Software

Before we go much further, I think it’s important to go over all of the software running on the international version of the SGS2 we’ve been loaned. I’ve made explicit mention of the fact that we were loaned this device because as a result it makes testing things with custom and leaked ROMs somewhat interesting. For the most part, carriers and OEMs don’t care as long as everything makes it back to them in exactly the same state they were shipped out, but it’s always a grey area. For that reason, I’ve been testing and using the device exclusively with the latest ROM for the phone as shown in Samsung Kies. As of this writing, that’s still Android 2.3.3 and firmware XWKF3. I realize there’s a leaked ROM which is 2.3.4, however we’ve opted to just go with official at this point.

The original SGS1 started Samsung’s trend of adding UI skins to high-end devices, and drew a firestorm of criticism from critics all over. Thankfully it seems as though Samsung has heard those complaints and has lightened things up considerably this go-around with TouchWiz 4.0 which runs on the SGS2. Where TouchWiz 3.0 (from SGS1) looked like a strange attempt at making Android 2.1 and 2.2 look like iOS, TouchWiz 4.0 is a much cleaner, less claustrophobic, and considerably less garish experience.

 

Starting with the lock screen, TouchWiz 4.0 continues the tradition of changing things here. Unlocking is achieved by moving the large graphic and clock off the screen, unless of course you’ve defined a custom lock pattern or PIN. Alerts such as new SMSes can be handled by sliding the notification ribbon across the screen. Of course this background is customizable and discrete from the main background as well. There’s really not much to say about this beyond that I’m still surprised TouchWiz didn’t take a nod from HTC’s Sense 3.0 and add shortcut functionality into this menu.

 

The main application launcher and home screens are what make or break a skin, and here I think there’s more positive than negative with TouchWiz 4.0. To start, home screen one is the far left, not the center. Switching between these is accomplished either by swiping back and forth or dragging on the dots at the bottom. This animation is extremely fluid - I get the impression that the entire TouchWiz 4.0 experience does leverage the GPU for composition and as a result feels very speedy.

 

There’s a contextual menu as well where new widgets, shortcuts, and folders can be added. In fact, most of the home screen customization takes a similar - screen on top, menu on bottom - approach, which makes a lot more sense than stock Android’s popup bubble schema. Tapping widgets gives you a long list of available widgets which tilt as you scroll through them. Just like other UI skins, there’s an assortment of skin-specific widgets that support resizing.

For the most part, I find that TouchWiz 4.0 moves away from the social-hub augmented with weird widgets motif set by the last generation of UI skins. That’s definitely a good thing, because most of the time that last generation failed to really deliver social experiences that came close to true first-party experiences.

TouchWiz 4.0 does still keep the bottom row of applications which is another throwback to iOS, and like other skins puts the application launcher shortcut in the far right.

 

By default the applications launcher presents icons in a 4x4 paginated layout, though you can toggle a list view as well and just scroll up and down. Menu edit brings you to a view just like the home screen customization page, where you can move icons around and also change the bottom row of shortcuts. There’s also folder support for organization. One major plus is that icons no longer have the chicklet-like background colors that made everything square and applications difficult to identify quickly. Thankfully, that’s gone, and the result feels far less tacky than the previous iteration.

Just like the home screen, you can change between pages of applications by tapping on the page number dot, or scroll back and forth quickly by sliding along the bar. This results in the same animated sliding view that the homescreen shows. I guess that’s one positive thing this go-around with TouchWiz, if anything you can’t criticize it for being inconsistent. For the most part honestly the launcher and homescreen TouchWiz components are pretty tolerable.

Just like in the past, the notifications shade drop down includes toggles for WiFi, Bluetooth, GPS, Sound, and Auto Rotate. It all works just like you’d expect it to. One small thing here is that if you’re in manual brightness mode, press and holding on the notifications bar and dragging left or right will change brightness along the scale. It’s a quick way to get analog control over brightness if you’re in manual setting mode.

Physical Impressions and Comparison Table Keyboards, Messaging, and a Smooth Browser
Comments Locked

132 Comments

View All Comments

  • Mugur - Tuesday, September 13, 2011 - link

    Well, for most Android devices I've tried (I currently own 3), if you just leave them doing nothing overnight (even with wifi on on some of them, but no 3G/HSDPA, no GPS etc.) the battery drain is like 2-3%. Of course, if some app or push email or an updating widget wakes them, the drain could reach 20-25%.

    You just have to play a bit with the phone and find out what is mostly consuming your battery, even get one of the "green" apps on the Market. Through experimentation, I'm sure most people (excluding the really heavy users) will get 50% more time of the battery.
  • wuyuanyi - Monday, September 12, 2011 - link

    It must be the final answer for my pending problem.my GS II has this problem and I has been very annoyed.the CPU current produce a EMI on the output circuit ,for the BT earphone DOESN'T play such hiss and noisy.apprecite it to solve my problem rather than suspect whether it is my own case. but the next question is how to solve it ? can we manual fix the shield or , generate a noisy that is against the noisy --with reverse wave?
    hehe

    sorry for my poor ENGLISH
  • awesomedeleted - Monday, September 12, 2011 - link

    This is a fresh copy of my current phone...Samsung Infuse 4G...which came out in May. I hate the newer Galaxy S round home button thingy too. What's so special, the name?
  • awesomedeleted - Monday, September 12, 2011 - link

    Although I now notice a few small differences in hardware, such as 1.2Ghz Dual-core A9 vs. my Infuse's 1.2Ghz Single-core A8, and the 1GB RAM.
  • supercurio - Monday, September 12, 2011 - link

    Infuse 4G is a Galaxy S "repackaged" with a Galaxy S II look, screen and probably camera sensor for AT&T.
  • bmgoodman - Monday, September 12, 2011 - link

    So I understand that the audio quality of this phone is a step down from the original galaxy. My question is how big a step down? For a non-"audiophile" who just wants to connect the headphone jack into the AUX port on his OEM car stereo to listen to his variable bit rate MP3 (~128 bps IIRC) music collection, is this something that's likely to disappoint? Is it a notable shortcoming for a more typical music fan?
  • supercurio - Monday, September 12, 2011 - link

    No doubt cars are in general a noisy environment.
    Furthermore its very rare to find cars benefiting from good speakers and implementation, resulting in far from linear frequency response, left/right imbalance, resonance in other materials etc :P

    Trained ears or sensible people are capable of detecting subtle difference in sound like nobody can imagine ^^ but I don't think it will Galaxy S II DAC issues described will make a noticeable difference when listening to music while driving a car for most people.

    Note: I have no idea how was the original Samsung Galaxy phone on this regard, but its a regression over Galaxy S.

    Headphones.. that's something else because even cheap ones (price doesn't matter) can provide some low distortion levels and let your perceive fine details.
  • Deusfaux - Monday, September 12, 2011 - link

    It is there and does work, speaking from experience with a Nexus S.
  • Deusfaux - Monday, September 12, 2011 - link

    An HTC I used did it best though, with integrating the feature right into the browser settings. No special URL strings needed to access functionality.
  • aNYthing24 - Monday, September 12, 2011 - link

    But isn't there a version of the Tegra 2 that is clocked at 1.2 GHz? It's going to be at that clock speed in the Fusion Grid table.t

Log in

Don't have an account? Sign up now