The Browser

The improvements to the Android web browser are some of the most noticeable in Ice Cream Sandwich. Browser performance both in JavaScript rendering and web page scrolling is worlds better than in Gingerbread. We've already explained why scrolling is smoother (full OpenGL ES render path), while the js performance improvements come courtesy of a newer V8 rendering engine in ICS.

The browser in 4.x also includes essentially everything that made the browser in 3.x smooth as well. As opposed to the Android 2.x browser's immediate rendering system - which would redraw the page in its entirety as you zoomed and panned around and seem choppy as a result - Android 3.x/4.x now render tiles into a backing store for webpages. This is the same system that iOS, webOS, and Samsung's custom browsers use, and as a result panning and translating around is now just as smooth as it is in those platforms. To be totally honest, this is probably one of the single largest and most welcome improvements over Android 2.x because of how dramatic the difference is.

 
 
Android 4.0 browser with visual indicator enabled (left), debug settings (right)

In Android 4.0 you can actually go inside the debug settings for the browser (enter about:debug into the address bar, enter, then a new settings pane emerges) and enable or disable OpenGL assisted rendering for the browser. With it off, it feels just like 2.x's choppy stock browser, and with it on, it feels buttery smooth like 3.x. The difference is beyond dramatic. This is actually a feature that was present in Android 3.x as well. 

A look at SunSpider and Browsermark performance tells us all we need to know about how the JavaScript V8 engine performance has changed under ICS:

SunSpider Javascript Benchmark 0.9.1 - Stock Browser

BrowserMark

While companies like Motorola and Samsung backported parts of the Honeycomb browser to their own Gingerbread browsers, the stock Gingerbread browser needed work. ICS modernizes the Android web browser and finally removes the need for third party customizations, at least from a performance standpoint.

Gingerbread vs. Ice Cream Sandwich
  Gingerbread Ice Cream Sandwich
Browser

The ICS browser is still WebKit based and uses a much newer version of WebKit than what you'll find in Android 2.3.6. Compared to the latest Honeycomb browser however there's not all that much difference in version number. The ICS browser does still use an older version of WebKit than Mobile Safari in iOS 5.0.1:

User Agent String Comparison
Device OS WebKit Version UA String
Apple iPhone 4S iOS 5.0.1 534.46 Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3
Samsung Galaxy Nexus Android 4.0.2 534.30

Mozilla/5.0 (Linux; U; Android 4.0.2; en-us; Galaxy Nexus Build/ICL53F) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30

ASUS TF Prime Android 3.2.1 534.13

Mozilla/5.0 (Linux; U; Android 3.2.1; en-us; Transformer Prime TF201 Build HTK75) AppleWebKit/534.13 (KHTML, like Gecko) Version/4.0 Safari/534.13

Google Nexus One Android 2.3.6 533.1 Mozilla/5.0 (Linux; U; Android 2.3.6; en-us; Nexus One Build/GRK39F) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1

HTML5 compatibility is fairly similar to Honeycomb, although a significant improvement compared to Gingerbread. If you haven't had any experience with Honeycomb tablets, the ICS browser will feel like like brand new technology.

The HTML5 Test
Test Apple iPhone 4S Samsung Galaxy Nexus Google Nexus One ASUS Eee Pad Transformer ASUS Eee Pad Transformer Prime
OS iOS 5.0.1 Android 4.0.2 Android 2.3.6 Android 3.2.1 Android 3.2.1
WebKit Version 534.46 534.30 533.1 534.13 534.13
Total Score 305 (and 9 bonus points) 256 (and 3 bonus points) 182 (and 1 bonus point) 222 (and 3 bonus points) 233 (and 3 bonus points)
Parsing rules 11 (2 bonus points) 11 (2 bonus points) 1/11 11 (2 bonus points) 11 (2 bonus points)
Canvas 20 20 20 20 20
Video 21/31 (4 bonus points) 21/31 21/31 21/31 21/31
Audio 20 (3 bonus points) 20 (1 bonus point) 20 (1 bonus point) 20 (1 bonus point) 20 (1 bonus point)
Elements 22/29 23/29 13/29 20/29 20/29
Forms 77/100 57/100 33/100 54/100 54/100
User Interaction 17/36 17/36 0/36

0/36

0/36
History and navigation 5 5 5 0/5 0/5
Microdata 0/15 0/15 0/15 0/15 0/15
Web applications 15/20 15/20 19/20 15/20 15/20
Security 5/10 5/10 5/10 5/10 5/10
Geolocation 15 15 15 15 15
WebGL 9/25 9/25 0/25 0/25 9/25
Communication 32/36 12/36 9/36 10/36 12/36
Files 0/20 10/20 0/20 10/20 10/20
Storage 15/20 15/20 15/20 15/20 15/20
Workers 15 0/15 0/15 0/15 0/15
Local multimedia 0/20 0/20 0/20 0/20 0/20
Notifications 0/10 0/10 0/10 0/10 0/10
Other 6/8 6/8 6/8 6/8 6/8

Performance and compatibility are obvious improvements, however there's much more to the ICS browser. For starters it implements tabbed browsing, a feature that has been available on Honeycomb but not in Gingerbread. Given the small screen size, tabs aren't immediately visible but are instead switched between after hitting the tabs button. The process makes sense and thanks to GPU accelerated drawing, scrolling through tabs is extremely smooth.

 
The normal desktop UA switcher (left), More options under developer settings (right)

Google added quick user agent switching to ask for desktop versions of websites vs. mobile by default through a checkbox under settings. Enabling the option changes the browser's UA string from representing itself as a mobile Safari browser to Chrome 11. There's also a menu inside debug settings to change your user agent (UAString) to look like the desktop, iPhone, iPad, Nexus One with Froyo, or a Xoom with Honeycomb. 

User Agent String Comparison
Device UA String
Default

Mozilla/5.0 (Linux; U; Android 4.0.2; en-us; Galaxy Nexus Build/ICL53F) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30

Desktop

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit 534.24 (KHTML, like Gecko) Chrome/11.0.696.34 Safari/534.24

Prior to ICS, the browser was a serious limitation of the Android platform on smartphones - it was choppy, and something OEMs continually replaced with their own (sometimes worse, sometimes better) browser. Granted you could always download and replace the browser with one of your own choosing, but for the mainstream user the Gingerbread browser was a problem. In ICS the browser is a blessing to use. It's very fast, smooth and compatible. We've had no problems using the Honeycomb browser and the same can be thankfully said about the evolution of it in ICS.

The Keyboard & Facial Recognition Email & Gmail
Comments Locked

185 Comments

View All Comments

  • sjankis630 - Wednesday, January 25, 2012 - link

    I can comment that my Galaxy Nexus' black is as black as midnight to a blind man.
    The only time I see some grey type tones is when the website is colored that way.
  • walkman - Sunday, January 22, 2012 - link

    That was a shocking detailed and informative review -- It's the sort of article that makes Anandtech my first choice for tech reviews.

    - The article mentioned new processors just around the corner. Was this referring to any processors other than Krait? I haven't heard any news about Krait since November PR -- Are we looking at April or June? And do we think anyone besides HTC will use Krait?
  • Omid.M - Sunday, January 22, 2012 - link

    Processors around the corner:

    Krait
    Tegra3
    OMAP5
    Exynos 5250

    It's going to be a bloodbath for the next 12-18 months.

    If iPhone 5 uses the MDM9160 (?) modem with LTE, I'm jumping on that. Tired of tweaking battery life on my Thunderbolt. Not sure I want to do the same with a Galaxy Nexus LTE.

    And what's this I'm reading about connection issues / dropped calls on the VZW Nexus? Ridiculous.
  • Rictorhell - Monday, January 23, 2012 - link

    I am a big fan of this site and I read the reviews and articles all of the time and I find them very informative and useful, but, I have a request.

    When a review is written, particularly about a certain smartphone or tablet, it is mentioned whether the device has an SD card slot and you always tend to differentiate between whether it is a “full-sized” SD slot or a “micro”SD slot. That is useful to know, but there are several actual types of SD cards available, each with a different maximum storage capacity, and you don't specify in your reviews which types of SD cards are actually supported by the device being reviewed and I think that is a bit of an oversight.

    To the best of my knowledge, standard SD cards only have a maximum capacity of up to 2gb, while SDHC cards can go up to as high as 32gb, and SDXC cards, while only available right now in sizes up to 128gb, are supposed to theoretically be able to be manufactured in sizes up to 2tb.

    There is a huge difference in size between 2gb, 32gb, and 128gb. Given that smartphones and tablets have substantial built in limits as far as storage capacity, I think it would be very helpful to know which type of SD card is supported by which device, if that is possible.

    If I read two reviews about two different Android tablets and both reviews mention that both cards have a full-size SD card slot, as a user with a lot of media files, I'm going to be interested to know if one of those tablets can support SDXC cards while the other one cannot.

    I consider that to be a major feature, to me, just as important as battery life. If you do reviews of tablets and smartphones, or even ultrabooks, and neglect to specify how much storage potential these devices have or do not have, you are making it very easy for the hardware manufacturers to simply put in second rate storage and format support, knowing that it will not be covered in reviews by sites like Anandech. Not only is this going to stunt the evolution of these devices but it's also going to mean less options for consumers.

    Anyway, thank you for your time.
  • peevee - Tuesday, January 24, 2012 - link

    Anand, please include OS version number (and carrier when applies) in the charts for performance and battery life tests. They make huge difference, as browser speeds improve, they consume less CPU time and less energy when browsing.
    For example, the discrepancy between iPhone 4 and iPhone 4S looks outsized and probably is the result of testing iPhone 4 with iOS much older than the current version, probably not even 4.3, and 4S with iOS 5.
  • skinien - Tuesday, January 24, 2012 - link

    What a review!!! I'm not in the market for a new hone right now, but when the time comes, I'll be looking here for a review on prospective phones. GREAT WRITE UP!
  • sonicmerlin - Thursday, January 26, 2012 - link

    I'm sorry, but you're ignoring the fact that ICS STILL lags. If you load up a heavy site like theverge, try scrolling around while the site is loading. Your entire page stutters and freezes until everything is done loading. ICS also lags more as you load more apps onto your phone, just like all previous versions of Android. Also notice how all UI elements are flattened when pages are rendered. Try zooming in or out. The new page info appears all at once, rather than pop up individually as in iOS and WP7. This can result in lag on heavy sites.

    For whatever reason tech "nerds" don't seem to notice the very obvious fluidity issues. Yes once you've loaded up a site it's easy to pan around, but people don't sit there patiently waiting for websites to load. Nor do they appreciate the frequent microstutters due to garbage collection issues, or the massive standby battery drain issues that tons of Android phones experience. And even the basic phone UI itself still lags behind your finger, demonstrating an irritating rubberband affect.

    It's stupid. Android will never stop lagging until Google rewrites the OS to give the UI thread priority, instead of putting it at the same level as app priority.
  • rupert3k - Friday, January 27, 2012 - link

    Learned loads from reading this, really impressed with how far Android has come.
    The stuttering when scrolling, zooming or browsing always annoyed me, stoked to learn ICS is fully accelerated.

    One wonders if we'll see any Motorola Nexus style devices once Google settles into their new ownership. Be nice to see a Motorola this nice!

    Hope we see high dot pitch Android devices to combat Retina, not happy with AMOLED at present it seems a bit yellowy & over saturated to me, surely LG or Samsung can also spec Retina style IPS or at least offer the choice between AMOLED & IPS 330dpi.

    Bring on the Quad high DPI Android & iOS tablets!!
  • bruce3777a - Sunday, January 29, 2012 - link

    Hi,

    Please bear with me:)

    If a phone was upgraded from Gingerbread to ICS and It appears to be able to still work with the apps from many banks

    It seems like these apps were not compatable with tablets running honeycomb so it was necessary to just use the browser.

    If a tablet is upgraded from Honeycomb to ICS, or if a new tablet is purchased that has ICS would/should that automatically make it compatable, or is there still something that the banks would need to do to make it universal to both phones and tablets that use ICS. Thanks in advance for any insight.
  • Lucian Armasu - Monday, January 30, 2012 - link

    I think I figured it out. I just saw this:

    http://score.nena.se/nenamark/view?version=2&d...

    And I remembered it's not the only time I see 1196x720 pixels being rendered in a benchmark. Anand, if you're reading this, could it be because the buttons are NOT rendered by the GPU, and instead are rendered by those Cortex-M3 2D cores? They would have to render much fewer pixels, but they are also much slower than the GPU, and also pretty old tech I think.

Log in

Don't have an account? Sign up now