Live data from Hacker News

Introducing Chrome for Android

googleblog.blogspot.com

151–160 of 240 posts

Re: Introducing Chrome for Android

#151
post #132

It appears to be significantly faster on JS front than stock Browser. Sunspider results: Stock - 3852.2ms Chrome - 3131.8ms (tested on HP Touchpad with CM9 A.06) edit: I was curious and redid it after rebooting: Stock - 2816.1ms Chrome - 2928.1ms (!) So it turns out it's faster on systems under load, but actually slightly slower on freshly booted one. Weird. In case anyone is interested in full benchmarks: Stock: htt…

Html5test.com scores? I've got a new android phone but it won't run chrome.

Re: Introducing Chrome for Android

#152
post #67
post #44

Earlier quoted context omitted.

Root and install a 4.0 rom!

I ran 4.0 via Cyanogenmod 9 on my Nexus S 4G for weeks, and unfortunately the bugs and constant app crashes got so bad that, as much as it pained me to do so, I went back to 2.3 yesterday. I love Android 4.0, but there doesn't seem to be a good, stable implementation of it yet. Example issues: * Random reboots * Choppy playback in the Music app (Amazon MP3 worked fine) * Random app crashes, particularly games (possib…

I've had ICS on my Nexus S for a few months now and I've not seen issues like that. I'm just using the standard Google image (AFAIK, my brother did the upgrade for me - Android 4.0.3, kernel 3.0.8-gb55e9ac). I do see a lot of battery drain when I'm using the GPS, and I don't play games, but no crashes.

Re: Introducing Chrome for Android

#153
post #132

It appears to be significantly faster on JS front than stock Browser. Sunspider results: Stock - 3852.2ms Chrome - 3131.8ms (tested on HP Touchpad with CM9 A.06) edit: I was curious and redid it after rebooting: Stock - 2816.1ms Chrome - 2928.1ms (!) So it turns out it's faster on systems under load, but actually slightly slower on freshly booted one. Weird. In case anyone is interested in full benchmarks: Stock: htt…

Html5test.com scores? I've got a new android phone but it won't run chrome.

256+3 bonus on stock, 343+10 bonus on Chrome.

I don't know how to paste which tests pass and which fail, is there any?

Re: Introducing Chrome for Android

#154
post #132

It appears to be significantly faster on JS front than stock Browser. Sunspider results: Stock - 3852.2ms Chrome - 3131.8ms (tested on HP Touchpad with CM9 A.06) edit: I was curious and redid it after rebooting: Stock - 2816.1ms Chrome - 2928.1ms (!) So it turns out it's faster on systems under load, but actually slightly slower on freshly booted one. Weird. In case anyone is interested in full benchmarks: Stock: htt…

On my Xoom with stock ICS 4.0.3, Chrome is on the whole dead even with the stock browser:

    Chrome - 2276.2ms +/- 1.0%
    Stock - 2288.9ms +/- 2.0%
Here's a screenshot of the detailed breakdown: http://i.imgur.com/WA37A.png . The "FROM" column is Chrome, the "TO" column is stock. Some tests Chrome wins, some stock.

Re: Introducing Chrome for Android

#155
post #150

My initial perception is that all the Chrome features are great, primarily the data syncing with my desktop browsers. But the rendering is flawed; it doesn't render like the standard Android browser, doesn't render like desktop Chrome, and doesn't seem to even render consistent to itself. For example, a few screenshots comparing the standard Browser view of this comment page and the way Chrome beta views it: Browser:…

It's apparently a feature: "An issue that often pops up for mobile browsers is that text on the website may be too small to read properly. Where the Android Browser employs a text reflow algorithm to clarify the situation, Chrome for Android features a technique which we’ve called Font Boosting. It uses an algorithm to increase font sizes when necessary, aiming to make the text readable regardless of the zoom level."…

Wow - I honestly can't decide if thats a horrible idea or not. But I can guarantee there's a ton of UX/UI folks who are going to get pissed that that.

Re: Introducing Chrome for Android

#156
post #150

My initial perception is that all the Chrome features are great, primarily the data syncing with my desktop browsers. But the rendering is flawed; it doesn't render like the standard Android browser, doesn't render like desktop Chrome, and doesn't seem to even render consistent to itself. For example, a few screenshots comparing the standard Browser view of this comment page and the way Chrome beta views it: Browser:…

It's apparently a feature: "An issue that often pops up for mobile browsers is that text on the website may be too small to read properly. Where the Android Browser employs a text reflow algorithm to clarify the situation, Chrome for Android features a technique which we’ve called Font Boosting. It uses an algorithm to increase font sizes when necessary, aiming to make the text readable regardless of the zoom level."…

Then their algorithm isn't consistent, as shown by screenshot. Some comments on HN are "boosted", while others remain tiny. This also makes it impossible to reliably hit any of the other page controls, like voting, without having to manually zoom way in and then back out.

Re: Introducing Chrome for Android

#157

Earlier quoted context omitted.

Apple seems to be able to innovate iOS while providing robust and timely updates for older devices.

Oh yeah? Let me know when I can get Siri on an iPhone 4 without resorting to some sketchy hacks.

This false equivalence is tiresome.

The inability to run a handful of hardware dependent features on iOS is not even in the same ballpark as the complete lack of timely updates for over 95% of Android users.

Re: Introducing Chrome for Android

#160
post #132

It appears to be significantly faster on JS front than stock Browser. Sunspider results: Stock - 3852.2ms Chrome - 3131.8ms (tested on HP Touchpad with CM9 A.06) edit: I was curious and redid it after rebooting: Stock - 2816.1ms Chrome - 2928.1ms (!) So it turns out it's faster on systems under load, but actually slightly slower on freshly booted one. Weird. In case anyone is interested in full benchmarks: Stock: htt…

On my Xoom with stock ICS 4.0.3, Chrome is on the whole dead even with the stock browser: Chrome - 2276.2ms +/- 1.0% Stock - 2288.9ms +/- 2.0% Here's a screenshot of the detailed breakdown: http://i.imgur.com/WA37A.png . The "FROM" column is Chrome, the "TO" column is stock. Some tests Chrome wins, some stock.

Anandtech did a Sunspider comparison with Chrome slightly trailing stock and both somewhat behind Firefox 10. Not really gamebreaking differences though.

http://images.anandtech.com/graphs/graph5517/43983.png

I use Firefox Home on iOS for the sync even though the JS is gimped in non-Safari webkit views. Sync is that killer.

Post reply on HN