You can use it to compare phones, but you can't use it to compare hardware. From the benchmarks above I can say that the iPhone 5 is twice as fast as the US Galaxy SIII, but I can't say that the A6 is twice as fast as the Snapdragon S4.
-
Hey Guest. Check out your NeoGAF Wrapped 2025 results here!
Android, iOS, WP8 phone debate thread
- Thread starter Scuba Steve
- Start date
- Status
NotTarts said:
Okay, but in the end we're comparing phones and their performance. Who cares about which is synthetically better with floating point calculations or whatnot? It's just as bad as comparing mhz/ghz and counting cores.
http://www.ukmobilereview.com/editorial/apple-maps-vs-nokia-maps-iphone-5-vs-lumia-900-showdown/
nokia maps are way ahead of the apple ones
nokia maps are way ahead of the apple ones
Baron Doggystyle von Woof
Member
Oh man. How can you release such a shitty maps app? I mean just use google maps for a few more years after yours is perfect.
Psychotext
Member
Nokia maps win by default because you can route without a connection. I've used that so many times recently.
I had no idea the others couldn't do it. Makes them pretty much useless in many areas near me.
I had no idea the others couldn't do it. Makes them pretty much useless in many areas near me.
Alright, so I finally had the chance to spend a good 20 minutes with an S3 running Jelly Bean.
You guys win, the interface is much smoother. No doubt about it. The general UI navigation does indeed deliver a smooth 60 fps refresh rate and the general feeling of using the device is much snappier than with ICS. It seems like an excellent phone, no doubt about it, and with Jelly Bean the experience is excellent.
I do have a question, however, regarding the way the default Android web browser handles page rendering.
So I was testing speed on my iPhone 5 vs the S3 opening web pages. Let's say I open the desktop version of Engadget on both phones. Neither one exhibits checker board patterns when scrolling quickly, which is awesome, and the Android zooming performance has been cleaned up a lot (still not as smooth as iPhone, but damn close).
The thing that struck with with nearly every page, however, was how SMALL the text is on Android when viewing desktop sites. This was an issue with older Android phones and I see this is still happening here. Is there a way to solve this? I messed around in the configuration options with different text and zoom options all of which had an effect on the text size but none of it brought it to the iPhone levels.
The reason this is an issue is simply that, on iPhone, you can zoom all the way out of a desktop web site and the text, while small, is just large enough to comfortably and clearly read. On the S3, however, text was a bit smaller and almost impossible to comfortably read at full page view. The Pentile display made it worse, I thought.
So as I was wrong about JB, I'm wondering if anyone can clarify this issue for me. Is there a way to make it so standard webpages display text at a larger (but still small) size that is easy enough to read?
I don't have an Android screen to show this, but the text on this page seemed almost 50% smaller compared to this and was difficult to read despite the larger screen. The font was just smaller.
You guys win, the interface is much smoother. No doubt about it. The general UI navigation does indeed deliver a smooth 60 fps refresh rate and the general feeling of using the device is much snappier than with ICS. It seems like an excellent phone, no doubt about it, and with Jelly Bean the experience is excellent.
I do have a question, however, regarding the way the default Android web browser handles page rendering.
So I was testing speed on my iPhone 5 vs the S3 opening web pages. Let's say I open the desktop version of Engadget on both phones. Neither one exhibits checker board patterns when scrolling quickly, which is awesome, and the Android zooming performance has been cleaned up a lot (still not as smooth as iPhone, but damn close).
The thing that struck with with nearly every page, however, was how SMALL the text is on Android when viewing desktop sites. This was an issue with older Android phones and I see this is still happening here. Is there a way to solve this? I messed around in the configuration options with different text and zoom options all of which had an effect on the text size but none of it brought it to the iPhone levels.
The reason this is an issue is simply that, on iPhone, you can zoom all the way out of a desktop web site and the text, while small, is just large enough to comfortably and clearly read. On the S3, however, text was a bit smaller and almost impossible to comfortably read at full page view. The Pentile display made it worse, I thought.
So as I was wrong about JB, I'm wondering if anyone can clarify this issue for me. Is there a way to make it so standard webpages display text at a larger (but still small) size that is easy enough to read?
I don't have an Android screen to show this, but the text on this page seemed almost 50% smaller compared to this and was difficult to read despite the larger screen. The font was just smaller.
Alright, so I finally had the chance to spend a good 20 minutes with an S3 running Jelly Bean.
You guys win, the interface is much smoother. No doubt about it. The general UI navigation does indeed deliver a smooth 60 fps refresh rate and the general feeling of using the device is much snappier than with ICS. It seems like an excellent phone, no doubt about it, and with Jelly Bean the experience is excellent.
I do have a question, however, regarding the way the default Android web browser handles page rendering.
So I was testing speed on my iPhone 5 vs the S3 opening web pages. Let's say I open the desktop version of Engadget on both phones. Neither one exhibits checker board patterns when scrolling quickly, which is awesome, and the Android zooming performance has been cleaned up a lot (still not as smooth as iPhone, but damn close).
The thing that struck with with nearly every page, however, was how SMALL the text is on Android when viewing desktop sites. This was an issue with older Android phones and I see this is still happening here. Is there a way to solve this? I messed around in the configuration options with different text and zoom options all of which had an effect on the text size but none of it brought it to the iPhone levels.
The reason this is an issue is simply that, on iPhone, you can zoom all the way out of a desktop web site and the text, while small, is just large enough to comfortably and clearly read. On the S3, however, text was a bit smaller and almost impossible to comfortably read at full page view. The Pentile display made it worse, I thought.
So as I was wrong about JB, I'm wondering if anyone can clarify this issue for me. Is there a way to make it so standard webpages display text at a larger (but still small) size that is easy enough to read?
I don't have an Android screen to show this, but the text on this page seemed almost 50% smaller compared to this and was difficult to read despite the larger screen. The font was just smaller.
Well I don't have an S3 on hand to test it, but if you're using the chrome browser, you can go to accessibility and increase the font size. I'm not sure if the S3 default browser has that, but I'm sure someone else can check.
I tried that, and all it did was result in a smaller column of text with a similarly small font. Very strange.
I should note that the browser was indeed Chrome. Chrome on iOS actually works like Safari iOS in that regard, strangely enough. This made it clear to me that the two are very different browsers (at least in how they handle page displays). Chrome on the PC, of course, functions differently as well as you'd expect.
That's weird, I just tested it on engadget and it did scale up the font. Tried it on both the desktop and mobile version of the site.
Now that's a bizarre shot. Are you zoomed in? That doesn't look like the desktop site. When I upped the font size, though, I did end up with more of a text column as you see there but when zoomed out to see the entire site it was still too small.
What I was trying to do was display the entire page, as you see in my pics, with text that is readable. You can easily read the entire blurb on iOS without zooming in and the page looks like it should.
Could you snap a picture of The New York Times in landscape? That's another interesting one. There is so much text that that, in portrait, it's difficult to read on any device but in landscape it's very clear. I didn't test it on Android and I'm curious to see what it looks like.
Well I didn't realize you wanted the whole site, I just double tapped to zoom to the paragraph. Here's one without it zoomed:
Hmm, that's much better. I was getting columns but the font was still small.
Which settings did you change?
I knew there had to be a good way to improve it.
It's odd that it still shows less text overall, though. Is there a setting that's smaller than what you have there but still larger than the default?
Here's the NYT site, you're right it seems text scaling doesn't work on this site for some reason, but it seems to look close enough in size to your screenshot. It also helps that the screen is bigger, but I'm not sure why scaling wouldn't work here. It's worth noting that the chrome bar does take up an uncomfortable amount of the screen in landscape mode.
I just moved the accessibility text scaling slider up for that engadget one. I set it to 130%, but you can obviously set it lower to suit your needs.
Ah ha, that's what it was. The accessibility setting.
Am I really the first to share this bit of hilarity?
http://www.theverge.com/2012/9/25/3403928/samsung-touchwiz-reset-vulnerability
http://www.theverge.com/2012/9/25/3403928/samsung-touchwiz-reset-vulnerability
Alright, so I finally had the chance to spend a good 20 minutes with an S3 running Jelly Bean.
You guys win, the interface is much smoother. No doubt about it. The general UI navigation does indeed deliver a smooth 60 fps refresh rate and the general feeling of using the device is much snappier than with ICS. It seems like an excellent phone, no doubt about it, and with Jelly Bean the experience is excellent.
I do have a question, however, regarding the way the default Android web browser handles page rendering.
So I was testing speed on my iPhone 5 vs the S3 opening web pages. Let's say I open the desktop version of Engadget on both phones. Neither one exhibits checker board patterns when scrolling quickly, which is awesome, and the Android zooming performance has been cleaned up a lot (still not as smooth as iPhone, but damn close).
The thing that struck with with nearly every page, however, was how SMALL the text is on Android when viewing desktop sites. This was an issue with older Android phones and I see this is still happening here. Is there a way to solve this? I messed around in the configuration options with different text and zoom options all of which had an effect on the text size but none of it brought it to the iPhone levels.
The reason this is an issue is simply that, on iPhone, you can zoom all the way out of a desktop web site and the text, while small, is just large enough to comfortably and clearly read. On the S3, however, text was a bit smaller and almost impossible to comfortably read at full page view. The Pentile display made it worse, I thought.
So as I was wrong about JB, I'm wondering if anyone can clarify this issue for me. Is there a way to make it so standard webpages display text at a larger (but still small) size that is easy enough to read?
I don't have an Android screen to show this, but the text on this page seemed almost 50% smaller compared to this and was difficult to read despite the larger screen. The font was just smaller.
Set the browser to fit text to page, then just double tap to zoom. You can also alter the default double tap zoom if you like.
Don't forget to enable the pie controls in developer options.
Lawl, people getting Samsung'd errywhere
EightBitNate
Member
Dial codes are perfectly fine, most phones have them. They're extremely useful in-fact, it's HTML links that would do the same that are the problem.
Yea the code is not the issue. Most people would never have known this. Apparently samsung were advised prior to this being let out, hopefully they are working on a fix.
HTML.
Lol.. Figures..
LyleLanley
Banned
That was pretty ballsy of you.
The Faceless Master
Member
apparently it works on Verizon GS3
http://www.androidcentral.com/major...hones-could-trigger-factory-reset-web-browser
International and AT&T are patched, others unknown
http://www.androidcentral.com/major...hones-could-trigger-factory-reset-web-browser
International and AT&T are patched, others unknown
Comforting...
(from article above (http://www.androidpolice.com/2012/0...ng-exploit-it-was-already-fixed-in-an-update/))
(from article above (http://www.androidpolice.com/2012/0...ng-exploit-it-was-already-fixed-in-an-update/))
LOL that's hilarious.
Funky Papa
FUNK-Y-PPA-4
I surmise nobody gives a shit about the BlackBerry event that's taking place ATM.
Eh.
Eh.
The Faceless Master
Member
their conference got Samsung'd!
Funky Papa
FUNK-Y-PPA-4
Yep.
Nokia lawsuit coming? ;-)You mean this one ?
Just caught up on the BB10 conference. It looks kind of cool but I'm not sure how the "always multitasking" will affect battery life and performance. I'm upgrading this upcoming summer so I'm trying to decide between BB10, WP8 and iOS. Honestly BB10 seems like my sort of phone. I've been using BB's for the longest time and only recently upgraded to WP7. I guess I'll wait for reviews.
That's not even the actual phone. Just a developer device.
Your sarcasm meter broke. :-(
The Faceless Master
Member
I've been reading Crackberry..... 'nuff said.
Damon Bennet
Member
note 2 is cooler
mescalineeyes
Banned
You mean the update that fixed this weeks ago?
- Status