Related
Here's a battle between WiFi browser loading speeds between the three phones. Very interesting result. Can anyone explain why the iphone was significantly faster? Nexus One should have been way faster compared to the iphone on same wifi speeds.
check it out:
http://www.youtube.com/watch?v=aMGkhBIqOMg
are we sure the android browser is loading everything in the same order? (it could have been loading the images further down the page first), also, it seems like the apple had cached the page, I have no sound here, but did they say that all 3 phones had been fuly reset or had their cache's cleared?
Yeah, that site was iPhone optimized! That's why there was such a huge difference in load times... what a scam! Notice you even see the "Engadget for the iPhone" banner pop up on the iPhone's screen...
Also notice the guys' ENTIRE post was so SLANTED!!!!!!!!!! He's a complete Apple fan boy. He wanted the Driods to lose. Just ticks me off becuase people will buy that when there is NO way AT&T has a better network and the Iphone is a slower machine.
I so wish this phone was unlocked for AT&T too! gah... my wifes stupid plan and her free minutes!!! I'm switching anyway but it would have been nice to truly have the open system.
No doubt the iphone had the page cached. I've just tried loading engadget on my iPhone 3GS, clearing the cache first and it took twice as long as what video showed on the iphone. I on Wifi with a 6.5mb connection too.
Engadget is totally biased toward Apple big time, nothing can ever live up to them if it hasnt got a apple logo on it.
This begs the question how did a bias reviewer like that get the exclusive review ?
But in head to head non cached race they will be almost the same, but even if the iphone wins (as some browsers generally handle different coded sites better) its doesn't matter as hay nexus one has confirmed Flash ..... my 3gs is looking older and older with every nexus one news story lol
Stop being fanboyish and look at facts. The new browser is nice, but Google screwed it up by moving the drawing engine to the skiagl library. It's now running on the same circumstances as the Chrome browser.
Engadget is a pretty punishing site, and, unlike the iPhone's safari, Android's browser won't release a page until most content is loaded (with the iPhone you can start viewing content even as it's loading).
Here's an interesting thing: If you have a Dream, load up Cupcake on it. No, seriously, load Cupcake on it, the do a browser test of Cupcake browser vs Eclair browser.
The new browser is pretty, but it's pretty much crap.
-edit-
I check engadget almost daily, and I had noticed that since I started using the 2.0 browser loading was slower. Oddly enough, most other websites are pretty quick too. The iPhone browser is supperior, and nobody's questioning that. I switched to Opera Mini on my device mostly because of the slow speed of the stock browser.
-edit2-
Honestly, run the test yourselves. Any eclair browser (either using a droid, or a nexus one, or a dream with either and aosp eclair build or cm's newest donut release with the 2.0 browser backported) will load the page at about the same rate (slower on my g1 over wifi which, according to speedtest.net, is running at 14.28 Mbps down, plenty fast).
Actually, I'll make a video of two android emulator devices, one with 2.0.1, and another with 1.5 and I'll load engadget on both.
plus the smoothness of the scroll. The iphone scrolls at snail speed, moving down screen length, of course its going to look smooth. Android scroll speed is 5 times faster, obviously it's going to look less smooth because of the refresh rate.
I don't see them commenting about that
Ok, here we go.
Android 1.1 browser (unchanged up to donut except for a few ui changes, but rendering engine is the same) vs Android 2.0.1 browser (with libskiagl drawing engine).
http://www.youtube.com/watch?v=EjsWWjh79oM
Interesting stuff, Jubeh!
Yes, Engadget is quite a bit slanted in apples favor. That entire review which contained that video was slanted. They failed to mention call quality in that review... did not even bring up the noise cancelling mike. Used sarcastic remarks all over the place. In this video he was like ohhh.. "If I were an owner of this phone I would be in tears"
I bet when I run this test myself the nexus one will probably win out most times but it all depends on the site. Gizmodo stated that the Nexus outperformed both the 3gs and droid most times in multiple test. Unlike Engadget.. they saw the result they wanted on their first try and didn't try it elsewhere.
i love my iphone
......now ducks under a table
I love my iPhone too but some ppl who have them think they are flawless which is untrue there are may downsides to the iphone which this particular review glossed over when comparing the too, things like :-
- WiFi 'n' Connectivity
- Removable battery (when the iphones battery dies like they do its a mess to replace the battery not to mention it voids the warrantee)
- Apples Grip on AppStore
- How apple restricts JB/Rooting is immense ( reducing your control over iphones)
- Battery Nexus Has a bigger battery and better life
Im not saying the nexus is perfect either :-
- Browser does seem slower on nexus (time will tell) Acid3 test them :-|
- UI of the nexus still looks kinda dated
- Some reported lag on home screens
So I understand that there are areas where the N1 falls behind the iPhone but on other, some more practical areas the iPhone falls behind.
Also did they say there device was On 2.1 ?? it could have been on 2.0.1 and i dint see any 2.1 specific features
how is 1.1 better than 2.0.1, how is that even possible?
Why would they let it come to that?
They better fix that!!!!
Anyone know if flash 10 works on the Nexus??
liamhere said:
......now ducks under a table
Click to expand...
Click to collapse
Whats wrong with liking your own phone?
Now if you were to say that the iPhone was better than the Nexus One in a Nexus One forum, with android fans, then you might need to hide under a table. BUT EVEN THAT WONT SAVE YOU!!!!
lolz
Err, is *2.1* slower?
trinode said:
Err, is *2.1* slower?
Click to expand...
Click to collapse
unknown, no one else seems to be wanting to do some browser videos.
http://forum.xda-developers.com/showthread.php?t=612843
Just got my nexus 1 and tried the engadget browser test. On my n1, it loaded the site just as fast as the iphone 3gs. And, after the page was cached, the n1 loaded the site faster than the 3gs.
And scrolling is very smooth, significantly better than the mt3g.
Here is a video from REAL Nexus One users comparing the browser speeds.
The N1 is just as fast if not faster than the iPhone.
Don't know why Engadget would make it seem Android is dyingly slow!!
http://www.youtube.com/watch?v=YdqXSY0UOHU
tethering or Wi-Fi Router than using the browsers on my T9193? This does not make sense when the data has to go through the same bottle neck.
because your laptop or whatever has faster processor and a ****load of RAM?
I'm not sure that's all there is to it. CPU/ram will have less of an effect on browsing when you're only opening a few tabs -- assuming there is sufficient RAM in the first place, and that you're not reading a site like slashdot with horrid JS.
It might just be an imagined effect though? I've noted that tethered internet seemed faster too but I've never ran any formal tests.
mazzarin said:
I'm not sure that's all there is to it. CPU/ram will have less of an effect on browsing when you're only opening a few tabs -- assuming there is sufficient RAM in the first place, and that you're not reading a site like slashdot with horrid js. It might just be an imagined effect though? I've thought tethered internet was faster too but I've never ran any formal tests.
Click to expand...
Click to collapse
Data don't just sit there. They need to be processed and rendered. A puny smartphone with a SoC isn't nearly as robust as say a dedicated motherboard with northbridge, southbridge, and different individual chips to handle their respective tasks. Sure, big CPU and RAM doesn't tell a whole story, but it certainly tell you enough for you to understand.
If you go to http://www.youtube.com/html5 and press the opt in link at the bottom on your phone you should then be able to view a variety of videos on youtube, html5 videos run much better than resource hogging Flash..
try this video to see if it works http://www.youtube.com/watch?v=siOHh0uzcuY
You are wrong, flash actually outperforms HTML5 and consumes less battery power
http://www.blackcj.com/blog/2010/09/17/flash-outperforms-html5-on-mobile-devices/
woopdy doo you can show one benchmark using one phone in a comparison, there are hundreds of html5 vs flash comparisons online and all show different results on different platforms and hardware, and on mobile devices this is down to devices having hardware accelerartion, without this HTML5 really does wipe the floor with it, play a flash video on an atom n270 then play a HTML5 video and see what the difference is on cpu usage..
anarchyuk said:
woopdy doo you can show one benchmark using one phone in a comparison, there are hundreds of html5 vs flash comparisons online and all show different results on different platforms and hardware, and on mobile devices this is down to devices having hardware accelerartion, without this HTML5 really does wipe the floor with it, play a flash video on an atom n270 then play a HTML5 video and see what the difference is on cpu usage..
Click to expand...
Click to collapse
why have you suddenly gone off in a tangent and comparing flash on a computer. Thought you were talking about the SGS here....?
psp888 said:
why have you suddenly gone off in a tangent and comparing flash on a computer. Thought you were talking about phones....?
Click to expand...
Click to collapse
Yeah and it applys to all devices, if you fine tune a product i.e the flagg ship 2.2 froyo device to play a video and optimize it then it will out perform. This does not mean on all devices with varying cpu's that this will be the case, the evidence shows that flash is not an all round good video codec/compression method due to it being bloated and certain variations, hence why apple are concentrating on HTML 5, I think we should let people decide the performance difference..
anarchyuk said:
Yeah and it applys to all devices, if you fine tune a product i.e the flagg ship 2.2 froyo device to play a video and optimize it then it will out perform. This does not mean on all devices with varying cpu's that this will be the case, the evidence shows that flash is not an all round good video codec/compression method due to it being bloated and certain variations, hence why apple are concentrating on HTML 5, I think we should let people decide the performance difference..
Click to expand...
Click to collapse
you're drinking too much apple cool aid
flash performs actually very very well lately (computers & phones alike)
html5 support would be nice for compatibility, but so far, html5 browsers actually use more power to play videos because they're not as optimized as flash is yet.
Truth is sometimes shocking
anarchyuk said:
Yeah and it applys to all devices, if you fine tune a product i.e the flagg ship 2.2 froyo device to play a video and optimize it then it will out perform. This does not mean on all devices with varying cpu's that this will be the case, the evidence shows that flash is not an all round good video codec/compression method due to it being bloated and certain variations, hence why apple are concentrating on HTML 5, I think we should let people decide the performance difference..
Click to expand...
Click to collapse
Bloated? Really? I love how people throw that term around. That works on digg perhaps, where people accept bloat as a valid answer, but the term has no distinct meaning. What do you mean? Because programs can have plenty of functionality and still perform as fast as one without.
There really is no reason why flash couldn't run as fast as normal HTML5, especially since neither run fully compiled code. And if you basically read the stream and dump it on the GPU for processing, in both cases, it's mostly done the same way probably.
I know all Atrix users are having problems with slower data connections than using, say the iPhone 4. So I went ahead and did a quick video of, iPhone 4 and Verizon LG Vortex to show the speed difference. Clearly you can see that the Atrix is very slow in uploading, but overall was pretty close in download speeds with the iPhone 4. I have been averaging around 2.2 Mps down and .31 upload. Overall when using the Atrix phone to look up anything in the Market place or web browsing, and or using a app that requires data, it feels much faster overall. Could be that the Dual-Core is helping in this. My next video will be, comparing on the phone browsing and using data apps to compare.
Here is the link to the video: http://www.youtube.com/watch?v=yA72kfo856w
Ya shouldn't run both ATT phones at the same time.
zephxiii said:
Ya shouldn't run both ATT phones at the same time.
Click to expand...
Click to collapse
Why its a fair real work comparison that way. No one is going to be the only one running a connection at any give time.
Sent from my Delorean using a flux capacitor!
compumasta said:
Why its a fair real work comparison that way. No one is going to be the only one running a connection at any give time.
Sent from my Delorean using a flux capacitor!
Click to expand...
Click to collapse
If you are interested in testing the device's ultimate speed, you shouldn't be running the test at the same time right next to each other period. That causes channel interference (if on same carrier) which degrades performance, not to mention you are cutting available air interface resources in half in on the same channel/sector. That is not going to tell you jack **** about how the device performs (as far as above average potential) in comparison to another device on the same network...it only really shows how each device handles data in a crappy signal situation....interestingly ATT was better than VZW.
It has been demonstrated that the Atrix lacks HSUPA and will generally not perform as well as iPhone4 (or other HSUPA enabled device) until this problem is resolved.
zephxiii said:
If you are interested in testing the device's ultimate speed, you shouldn't be running the test at the same time right next to each other period. That causes channel interference (if on same carrier) which degrades performance, not to mention you are cutting available air interface resources in half in on the same channel/sector. That is not going to tell you jack **** about how the device performs (as far as above average potential) in comparison to another device on the same network...it only really shows how each device handles data in a crappy signal situation....interestingly ATT was better than VZW.
It has been demonstrated that the Atrix lacks HSUPA and will generally not perform as well as iPhone4 (or other HSUPA enabled device) until this problem is resolved.
Click to expand...
Click to collapse
I think you misunderstood what he's saying. In the real world, you could be standing next to someone else using an AT&T phone, so that interference isn't unexpected. How the device handles that kind of interference is absolutely relevant information.
Ririal said:
I think you misunderstood what he's saying. In the real world, you could be standing next to someone else using an AT&T phone, so that interference isn't unexpected. How the device handles that kind of interference is absolutely relevant information.
Click to expand...
Click to collapse
In the real world, he probably isn't running a speedtest right when you are.
It's still pointless as if you are trying to compare device speeds on the network, you need to give them ideal conditions....otherwise you aren't comparing the devices really. This is obvious because it isn't showing the Atrix's crippled network interface.
zephxiii said:
In the real world, he probably isn't running a speedtest right when you are.
It's still pointless as if you are trying to compare device speeds on the network, you need to give them ideal conditions....otherwise you aren't comparing the devices really. This is obvious because it isn't showing the Atrix's crippled network interface.
Click to expand...
Click to collapse
I'm not even sure I understand what you're arguing. Someone next to you is not using a data connection if they're not running a speedtest? Because that's what it sounds like you're saying. The speed of the phone next to you is irrelevant. A phone pulling down 1000Mbps as opposed to 100Mbps won't magically decrease the surrounding signal. In modern devices, channel interference like that isn't really a problem anyway.
Ririal said:
I'm not even sure I understand what you're arguing. Someone next to you is not using a data connection if they're not running a speedtest? Because that's what it sounds like you're saying. The speed of the phone next to you is irrelevant. A phone pulling down 1000Mbps as opposed to 100Mbps won't magically decrease the surrounding signal. In modern devices, channel interference like that isn't really a problem anyway.
Click to expand...
Click to collapse
Based on that statement, it looks like you really don't understand how WCDMA (or CDMA based) networks work. Channel noise, noise floor, neighboring interference etc. plays a huge part in network performance. So yes, even though signal receive strength may be very good, performance can suffer from channel noise...and I see it all the time in cell overlap areas (I live in one even).
And when you have two devices like that operating right next to each other using the same ARFCN, especially if one is in the upload portion of the test, it's going to create additional noise that the other device is going to have to fight through....then throw on top that both devices are fighting for whatever is left of free resources on the site..which is basically cutting whatever is left in half....if they are on the same sector/channel.
zephxiii said:
Based on that statement, it looks like you really don't understand how WCDMA (or CDMA based) networks work. Channel noise, noise floor, neighboring interference etc. plays a huge part in network performance. So yes, even though signal receive strength may be very good, performance can suffer from channel noise...and I see it all the time in cell overlap areas (I live in one even).
And when you have two devices like that operating right next to each other using the same ARFCN, especially if one is in the upload portion of the test, it's going to create additional noise that the other device is going to have to fight through....then throw on top that both devices are fighting for whatever is left of free resources on the site..which is basically cutting whatever is left in half....if they are on the same sector/channel.
Click to expand...
Click to collapse
I understand the theory, I've just never seen it affect a device in practice to any noticeable degree. I might get 3.15 down with no other devices nearby, and 3.14 down with several others running at once (GSM and CDMA devices).
Living in an area with several carriers fighting for the airways can impact performance, but again, I've never seen a big enough difference to care. Maybe you've just been in areas with outdated hardware or poor filtering. This is all from personal experience, however, and I live in Chicagoland where there is no shortage of service from any carrier.
I know some have said that having all 3 devices and running the test can affect the performances when running data. I was hoping to try to run a test that could show what would happen if you were out and happen to be close to other smartphones that might be accessing data.
I will post another video showing how the data performance is, by running the speed test one at a time. I did try that today, and I can say that whether I had all three running at the same time or run speed test one at a time, the speeds didn't not change much; maybe only .04 difference. So having all three running the speed test would only affect around .04 to .06 difference in download speed.
I will also do a test to compare the speed to open browser and going to websites.
Also when I was doing the speed test today with my Atrix, I was using it as a mobile hot spot to provide internet to my Samsung Galaxy Tab, and the download speeds on the Atrix was very good. I got around 3.0 Mbps down and .29 Mbps upload; which is very slow compared to my iPhone 4. Hopefully soon this will be fixed.
So in real world situations if others around me are using their phones/data I shouldn't judge how my phone performs based on that? Individual testing is fantastic, but I'm rarely the only person in the room with an AT&T smartphone so it's not practical. Everyday use throughout the day (speedtest app or not) is the only real way to judge data performance in my book.
Besides, the speedtest app can go from 1.2 to 3.4 to .08mbps in 3 consecutive tests. It's all over the place.
For browsing the Atrix should open pages quicker because the processor will help out along with the network speeds.
A former intern for Google's Android team has provided explanations for why Android experiences more touch interface lag than competing mobile operating systems from Apple, Microsoft and Research in Motion.
Undergraduate software engineering student Andrew Munn posted his observations on Google+, as noted by Cult of Mac. He did disclaim, however, that he will be starting an internship with Microsoft's Windows Phone team in January, adding that any opinions from the report were his alone.
According to Munn, Android has a difficult time dealing with the touch interface because it handles rendering "on the main thread with normal priority," as opposed to iOS, which treats UI rendering with real-time priority. He cites examples of website loading and the Movies app on Android where the operating system will continue to load while registering touch input.
Munn identified several other factors that contribute to UI lag on Android. For instance, the photo gallery app in either Android 3.0 Honeycomb or 4.0 Ice Cream Sandwich is capped at 30 frames per second in order to prevent a noticeable "hiccup" at 60 FPS.
"Capping the frame rate at 30 fixes the hiccup problem at the expense of buttery smooth animations at all times," he said.
The author also pointed to hardware issues for Android. According to him, Nvidia's Tegra 2 chip limits Android because of its low memory bandwidth and lack of NEON instruction set support. Tablets based on Honeycomb would be "better off with a different GPU," such as the Samsung Hummingbird or Apple A4.
Munn noted that Android "has a ways to go" before achieving more efficient UI compositing, especially when compared against Apple's iOS.
"On iOS, each UI view is rendered separately and stored in memory, so many animations only require the GPU to recomposite UI views," he said. "GPUs are extremely good at this. Unfortunately, on Android, the UI hierarchy is flattened before rendering, so animations require every animating section of the screen to be redrawn."
Another reason for the lag is the limitations of Android's Dalvik virtual machine, which is "not as mature" as a desktop-class Java VM, Munn said. However, the issue with Dalvik will be offset by hardware acceleration from Ice Cream Sandwich on and improvements to Dalvik.
But, in spite of the improvements, Munn believes the Android user interface "will never be completely smooth because of the design constraints" that limit UI rendering to the main thread of an app with normal priority.
"Even with a Galaxy Nexus, or the quad-core EeePad Transformer Prime, there is no way to guarantee a smooth frame rate if these two design constraints remain true," he said. "It’s telling that it takes the power of a Galaxy Nexus to approach the smoothness of a three year old iPhone."
According to Munn, the reason behind the design change is that the original Android prototype didn't have a touchscreen, as it was meant to be a BlackBerry competitor. As such, Android's architecture is meant to support a keyboard and trackball. Munn further claimed that after the original iPhone arrived in 2007, Google rushed to complete Android, but "it was too late to rewrite the UI framework."
He cited Windows Mobile 6.5, BlackBerry OS and Symbian as examples of other older operating systems that suffered similar problems with touch performance. Microsoft, RIM and Nokia have all abandoned those OSes in order to start from scratch. "Android is the only mobile OS left that existed pre-iPhone," the report noted.
Android Software Engineer Romain Guy admitted as much when he said that choices made years ago had contributed to work the team has to do now.
"Having the UI thread handle animations is the biggest problem," he said. "We are working on other solutions to try to improve this (schedule drawing on vsync instead of block on vsync after drawing, possible use a separate rendering thread, etc.) An easy solution would of course to create a new UI toolkit but there are many downsides to this also.”
According to the report, those downsides include the fact that apps would have to be rewritten to support the new framework, Android would need legacy support for old apps and work on other Android features would be held up while the new framework was being built.
"However, I believe the rewrite must happen, despite the downsides. As an aspiring product manager, I find Android’s lagginess absolutely unacceptable. It should be priority #1 for the Android team," Munn said.
UI Lag has long been an area for which reviewers have criticized Android. One recent usability study by Jakob Nielsen on Amazon's Android-based Kindle Fire found erratic scrolling and "huge lag in response after pressing command-buttons." Nielsen suspected that "sloppy programming" was causing the issue.
The New York Times' David Pogue also took issue with the Kindle Fire. "Animations are sluggish and jerky -- even the page turns that you'd think would be the pride of the Kindle team," he said in his review. "Taps sometimes don't register. There are no progress or 'wait' indicators, so you frequently don't know if the machine has even registered your touch commands. The momentum of the animations hasn't been calculated right, so the whole thing feels ornery."
Munn himself viewed the issue as damaging to Android's image. He also saw it as a violation of Google's guiding principles, which have generally led to faster, optimized products. Finally, he mentioned that UI lag breaks the direct 1-to-1 relationship that touch screens offer.
"The device no longer feels natural. It loses the magic. The user is pulled out of their interaction and must implicitly acknowledge they are using an imperfect computer simulation. I often get “lost” in an iPad, but I cringe when a Xoom stutters between home screens," he said.
To conclude, the report ended on a more upbeat note, with Munn voicing his belief that the Android rendering framework is in the hands of a capable team. "I know they will have it eventually," he said.
___________________________________________________________________
I`m sorry o hear this .. so is there any chances that google make android on same structure as ios?
I know IOS is for only Apple devices, and because of that is feeling so smoth .. but how windows (computer windows) can be smoth for all computer configurations? and Android can`t, even quad core can`t stable android ....
This article makes me think. Let`s hope that there will be future improvement on how Google will write it`s UI code. I mean, it`s sad to have an SGS2 or an quad-core powered phone/tablet and a OS to hold back it`s power.
And more or less in reply to this came a post by Dianne Hackborn, who is part of the Android development team, explaining why most of this was either irrelevant or wrong.
https://plus.google.com/105051985738280261832/posts/XAZ4CeVP6DC
Still, plenty of questions of course.
I heard that android was made for phones with buttons and because of this we have all problems ...
No way this is true.
Nope, the system is power smooth and no lag whatsoever. Nada.
The truth is IQ restricted to a few in Android. Be happy with what you got. All the user posted issues are IDIOT related, as a senior member reminded me.
/sarcasm off
Dalvik VM limitations were known and were a set back from the beginning (just like fat32). Nevertheless, they ''fixed it'' somehow, this is why Oracle is giving hard time to Google.
I can't say WP7/BBoS is smoother/better when compared to SGS2 GB...but both OS's are smoother when compared to appropriate hardware.
Student i see well that's not somebody that knows what they are talking about is it .
jje
This is false because thread priority can be assigned by the OS or even the software (in certain cases). The reason why the web browser in the iPhone is more responsive than in Android is as follows.
On the iPhone, the web browser is rendered with a tiling method, What this means is that the only things drawn in high quality are the "tile" that you see (everything on screen) as well as the immediately touching tiles. Ever notice that when you pan/scroll on iOS, it seems to only leap one page, similar to Page Down on your PC? This gives the browser time to dump tiles that are no longer adjacent while rendering the newly adjacent tiles in higher quality.
On Android, the entire page is rendered in the same quality. This is more work, so scrolling/panning/zooming fluidity suffers. This allows for a consistent but not as smooth approach. It also means that you can flick-scroll indefinitely.
On the SGS2, Samsung tried to implement the tiling approach but left in the Android scrolling limitations. This means that you can sometimes scroll faster than the page can keep up, causing a checkerboard affect (this is what Apple is hiding with their method).
On the ICS browser, Google also adopted the tiling method (finally), and managed to disguise the checkerboard affect by covering it with the webpage's default background color. The "checkerboard" is still there, but you never see or notice it. Anyway, I did a writeup with videos to illustrate this. Unfortunately, most idiots are taking the videos as fanboy fodder. They seem to think that the point was to show off how much better phone X is than phone Y, rather than to show the differences in approaches. The RAZR/Rezound will have these enhancements with their 4.x update.
http://www.anythingbutipod.com/forum/showthread.php?t=67100
Yep, pretty much accurate info here but this is only regarding browser smoothness. Responsiveness is another issue android seems to have. When you scroll in iOS the contents are almost always directly below your finger, not "lagging" behind your swipes trying to catch up as you normally see in Android. I'm no expert so I have no idea what the cause of this is.
jaykresge said:
This is false because thread priority can be
assigned by the OS or even the software (in certain cases). The reason why the web browser in the iPhone is more responsive than in Android is as follows.
On the iPhone, the web browser is rendered with a tiling method, What this means is that the only things drawn in high quality are the "tile" that you see (everything on screen) as well as the immediately touching tiles. Ever notice that when you pan/scroll on iOS, it seems to only leap one page, similar to Page Down on your PC? This gives the browser time to dump tiles that are no longer adjacent while rendering the newly adjacent tiles in higher quality.
On Android, the entire page is rendered in the same quality. This is more work, so scrolling/panning/zooming fluidity suffers. This allows for a consistent but not as smooth approach. It also means that you can flick-scroll indefinitely.
On the SGS2, Samsung tried to implement the tiling approach but left in the Android scrolling limitations. This means that you can sometimes scroll faster than the page can keep up, causing a checkerboard affect (this is what Apple is hiding with their method).
On the ICS browser, Google also adopted the tiling method (finally), and managed to disguise the checkerboard affect by covering it with the webpage's default background color. The "checkerboard" is still there, but you never see or notice it. Anyway, I did a writeup with videos to illustrate this. Unfortunately, most idiots are taking the videos as fanboy fodder. They seem to think that the point was to show off how much better phone X is than phone Y, rather than to show the differences in approaches. The RAZR/Rezound will have these enhancements with their 4.x update.
http://www.anythingbutipod.com/forum/showthread.php?t=67100
Click to expand...
Click to collapse
dinan said:
Yep, pretty much accurate info here but this is only regarding browser smoothness. Responsiveness is another issue android seems to have. When you scroll in iOS the contents are almost always directly below your finger, not "lagging" behind your swipes trying to catch up as you normally see in Android. I'm no expert so I have no idea what the cause of this is.
Click to expand...
Click to collapse
Depends on the device. This was absolutely true of my HTC Incredible on Android 2.1. With 2.2/2.3 and bloatware removed, the UI outside of the browser is more responsive than my wife's old iPhone 4, but a hair behind her new 4s (The 4 slowed down with iOS 5 due to the new notification shade). This goes back to a previous post I made in another thread where the iPhone's entire UI is GPU accelerated due to not having high requirements. Android's UI is more complex which causes OEMs to decide which elements are accelerated and which are not. In most newer phones the notification shade is always accelerated, the wallpaper is not, but the homescreens are to varying degrees. There is a fill-rate budget and the OEM has to decide what is accelerated and what isn't within this budget.
A prime example is the Nexus S vs. the Galaxy Nexus. While both use the SGX540 GPU, the Galaxy Nexus version is clocked higher and has MUCH higher performance. As such, the entire Galaxy Nexus UI is accelerated. However, for the Nexus S ICS build, only certain parts of the UI are accelerated. Google has gone on record as saying that this is due to hardware limitations.
I'd be willing to bet that this is why the Nexus One isn't getting ICS. The Adreno 200 GPU was subpar even when it came out. With the new overlays in ICS, the UI in the N1 would become laggier rather than smoother, as with previous releases. Google may have felt that the user experience of GB on the N1 is superior to that of ICS due to the new features. Even budget phones today using scaled down Snapdragon S2s or the older OMAP4 have a better GPU than what the N1 had.
sounds like a disgruntled employee speaking half truths.
Guess this guy never tried an sgs2. No lag whatsoever!
Sent from my GT-I9100 using XDA App
Pretty much spot on. You cnt disagree that ios is muuuuuch smoother than android and that it does lag at times. Student nailed it in my opinion. Well written. Ive always said it has a long way to go and quad core wont b much differnt to dual core phones. When i used a iphone 4s for a while.... it blew me away how slick it was. Future versions will hopefully only get better. But iphone cnt match android open source fun lol. .
Sent from my GT-I9100 using xda premium
Fizzerr said:
Guess this guy never tried an sgs2. No lag whatsoever!
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Since when u have your s2? Cuz on my s2.. I get lag.. and you know when? UI. When unlocking.. when i close an app it takes some time to get to UI...and so on. And I am on stock firmware.
Cristitamas said:
Since when u have your s2? Cuz on my s2.. I get lag.. and you know when? UI. When unlocking.. when i close an app it takes some time to get to UI...and so on. And I am on stock firmware.
Click to expand...
Click to collapse
No lag whatsoever on my GSII. And on my iPhone 4S there is also no lag. Both aee extremely fluid in my opinion. Galaxy Nexus, GSII, and the 4S are the fastest phones on the market right now.
Sent from my GT-I9100 using xda premium
Fizzerr said:
Guess this guy never tried an sgs2. No lag whatsoever!
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
In fact, when scroll in tapatalk lags, when im moving in desktop and receive a message of whats app or miyowa messenger lags too.
iNeri said:
In fact, when scroll in tapatalk lags, when im moving in desktop and receive a message of whats app or miyowa messenger lags too.
Click to expand...
Click to collapse
It lags...period lol
Sent from my GT-I9100 using xda premium
androidkid311 said:
It lags...period lol
Click to expand...
Click to collapse
Correct. So far any Android device lags. Any phone, any tablet, all of them. Sure, we are lucky to have one of the more lag-less devices but anybody who says the SGS2 doesn't lag at all either:
a) is ignorant
b) is very easy to please
c) is blinded by Android fanboyism
d) hasn't seen a true lag free device yet.
The SGS2 lags. Sometimes a little, sometimes like crazy, so be it. Don't claim otherwise.
Yes, my old xperia x10 lagged all the time. But my custom-ROM-running sgs2 doesn't lag. Yes, I've had an iPhone 4 for 8 months so I can compare them.
IMHO, lag is mostly placebo and expecting too much these days. Ugly code can cause the UI to stutter on every platform, including iOS.
# Galaxy S II w/ tapatalk
Pfeffernuss said:
The SGS2 lags. Sometimes a little, sometimes like crazy, so be it. Don't claim otherwise.
Click to expand...
Click to collapse
LOL. You must have a heap of bloatware on that thing. Either that or you've flashed a dodgy ROM. I get no lag at all. I think you are getting lag confused with app loading time. If you fire up Asphalt 6 and it takes 10 seconds to load that's not lag. Have a play with a Galaxy S on one of the earlier ROM's. Then you will see lag.
Sent from my GT-I9100 using XDA App
Fizzerr said:
LOL. You must have a heap of bloatware on that thing.
Click to expand...
Click to collapse
No bloatware whatsoever.
Either that or you've flashed a dodgy ROM.
Click to expand...
Click to collapse
Tried many many Roms, many many kernels, many many Launchers, etc. All the same thing. The phone will once in a while lag and/or show micro-stutters.
I get no lag at all.
Click to expand...
Click to collapse
None at all, really. A statement like that makes all the other things you say worthless. Every Android device will once in a while lag and/or expose micro-stutters.
I think you are getting lag confused with app loading time. If you fire up Asphalt 6 and it takes 10 seconds to load that's not lag.
Click to expand...
Click to collapse
I know what lag is, thank you.
It's exactly the same as when people say "my screen is perfect. I have no yellow/darker left side on my panel". When you check it yourself of course the panel isn't even. Usual reply? "Well, I don't see it so it doesn't bother me". That's not the point, it's there. The fact that the phone is 100% smooth for you is nice, only it is not.
Your SGS2 also will have occasional lag/micro stutters. In all apps/all the time? No. In most apps/usually? No. In some apps/occasionally? Yes.
Is it still an amazing phone? For sure. Probably the best/smoothest Android so far? Guess so. Does it sometimes lag and/or stutter? Absolutely.