Linked by Thom Holwerda on Wed 7th Nov 2012 17:06 UTC
Google Back when I reviewed the Nexus 7, I mentioned that I was disappointed with Chrome for Android. It often felt slow, would hang, and typing in the address bar and input fields on webpages would lag. Scrolling wasn't always optimal, and sometimes, it would simply freeze up altogether. We're several months down the line now - has the situation improved for me?
Thread beginning with comment 541374
To read all comments associated with this story, please click here.
Firefox?
by _xmv on Thu 8th Nov 2012 06:15 UTC
_xmv
Member since:
2008-12-09

The only equivalent to Chrome on Android is Firefox.
Opera is a special mobile version. Most others are using the Android "builtin" webkit. Probably why you did switch to Firefox in fact. Like I did.

Only Chrome and Firefox deliver an "exactly same engine as desktop".

Except Firefox works, and is very fast, while Chrome is slow and annoying (even thus it has nice animations).

So yeah, ironically, the opposite as on the the desktop.

Solution to Chrome's issues? Just use Firefox. On top of that, you get to use something's that's actually supporting the free web.

Oh and, Firefox Sync happen to be working a lot better than I expected.

The only thing I'm missing is proper "full screen browsing". The UI doesn't annoy me, it's different, but not bad. Not exceptional either, it's just fine. And hey, there's full noscript and full adblock support.

Edited 2012-11-08 06:22 UTC

Reply Score: 2

RE: Firefox?
by Morgan on Thu 8th Nov 2012 07:40 in reply to "Firefox?"
Morgan Member since:
2005-06-29

On my Transformer, I got in the habit of using the built in browser for most sites, Chrome for certain sites that rendered better in it, and Firefox specifically for cherokeeforum.com as it automatically resizes forum images correctly. The other two had issues with that, though Chrome worked on a few other forum sites. The built in browser was terrible at most forums I frequent.

When I was testing a Nexus S with ICS and then JB, it was even worse. Chrome was terribly slow, and while Firefox wasn't any faster than the built in browser it did render sites better most of the time.

If I decide to get a Galaxy Note 2 next year to replace my WP7 phone, I'll be curious to see the state of Chrome by then. Everything I've read about the Note 2 indicates that I may not even need an add-on browser unless I want bookmark sync, and in that case I'd stick with Firefox.

Reply Parent Score: 2

RE[2]: Firefox?
by REM2000 on Thu 8th Nov 2012 13:36 in reply to "RE: Firefox?"
REM2000 Member since:
2006-07-25

I have a Galaxy Note 2 on O2 in the UK on version 4.1.1.

So far ive found the chrome experience really good. I was an iPhone user so came from Mobile Safari. So far ive found chrome to be a lot more responsive, i like the tab handling and it's really easy to navigate.

Im not sure on what the performance hits are experienced by others. I don't know if the note2 having a quad core and 2GB RAM helps it.

Web sites tend to scroll quite quickly even on photo heavy sites, even silly animated gifs seem to work. I haven't installed flash so im not sure on the performance of that.

I also own a Galaxy Note 10.1 which is running ICS and chrome is very fast on that also.

I will say though when i got the note2 at the end of october odd, the version of chrome then was slow and not very good, im sorry but i couldnt find the version of chrome im using at the moment on my note2.

Reply Parent Score: 2

RE: Firefox?
by zima on Fri 9th Nov 2012 20:47 in reply to "Firefox?"
zima Member since:
2005-07-06

The only equivalent to Chrome on Android is Firefox.
Opera is a special mobile version. Most others are using the Android "builtin" webkit. Probably why you did switch to Firefox in fact. Like I did.
Only Chrome and Firefox deliver an "exactly same engine as desktop".

Though there are two mobile Operas. Opera Mini (which is essentially just a remote viewer, browser engine sitting on the servers of Opera, data pipe between them highly compressed) and Opera... Mobile (a full browser; though it also can utilise compressed connection - but here the rendering is still local)

Both using essentially the same engine as desktop browser (maybe it just lags a bit, usually, IIRC; anyway, not sure I want exactly the same engine in very different, mobile vs desktop, circumstances)

Reply Parent Score: 2