Browser Battle: Nexus One / Droid / Iphone - Nexus One General

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

Related

Sense UI too much for Htc Hero?

according to this gizmodo android review, it seem's so...
http://gizmodo.com/5318860/htc-hero-review-ambitious-but-tragically-flawed
"Guts and Miscellany
Powering Hero is 528MHz processor virtually identical to one inside the Dream and Magic, and it has the same 288MB of RAM as the latter. Frankly, it's not enough. At least not with HTC's custom user interface, more than a couple of widgets and an application running. Killing all of the widgets—especially the Twitter one—does help. But moments where the phone does nothing for a second or three after you've tapped, flicked or swiped happens far too often. Which is to say, a lot, especially after it's been on for more than an hour. Fast, totally smooth transition animations are infrequent enough I'm pleasantly surprised when a desktop screen immediately and gracefully slides to the left or right without a hiccup. It's frustrating"
sounds like it doesn't that much better than hero on our g1's, which is sad for such a lovely gui.
tho I all I would really want from rosie/sense/touchflo is people/albums twitter and facebook integration as well as the twitter widget.
to really i'd love to have all the damned widgets, even the stock widget that no one here seem's to want, onyl if they could integrate it w/ google finance for the most real-time pricing available for free.
im running off on tangents tho..so i will stop..
Don't put to much stock in the engadget or gizmodo reviews. It's hard to get a earnest review of anything other than Iphones from either site. Some people in the gizmodo thread state that there is a clas4 card included with the kits, and swapping it out for a class6 makes the sluggishness go away. Apparently hero uses a swap file aswell. It would be interested to see them retest with a class6 card. Head off to some of the other sites and you will find reviews that explicitely say they DID NOT notice the sluggishness.
It's also noted that alot of the widgets only update when the phone wakes, some of that bogging could simply be the edge connections choking truing to update all the widgets, of which im sure they loaded every possible page full.
It would be very interesting to see if the class4 sd card really is the bottleneck. If it is, i would like these guys to eat crow for lunch. Even HTC is puzzled by the fact that some people report no issues, while the highest profile sites report its just abysmal. I'm getting one regardless, when the NA 3g band version is available, even if it was sluggish, one cyanogen and the gang get ahold of it, it's a wrap.
I believe Android itself is part of the bottleneck - the Dalvik VM makes everything unbearably slow. Hopefully HTC will make use of the NDK.
There are several comments from actual Hero users who say that a lot of the sluggish behaviour was gone when they didn't use the Class 4 MicroSD card and used Class 6 instead, which indicates a problem with the IO as Android uses the mem card for its swap file. That means its not the processing time when all these apps are running concurrently afterall. Food for thought..
I've read both the gizmodo and engadget reviews, as mentioned before, both sites do have a bias towards the iPhone, but I found that engadget's review of the hero to be quite objective in their testing. As for the gizmodo review, they seemed ready to hate it as soon as they didn't see an apple logo on it.
I think Hero is just poorly coded. Have you watched the logs on this thing? Providers in Providers, hundreds of BroadcastReceivers, its crazy. To do anything on the device 100 different apps wake up.
mpeezay said:
according to this gizmodo android review, it seem's so...
http://gizmodo.com/5318860/htc-hero-review-ambitious-but-tragically-flawed
"Guts and Miscellany
Powering Hero is 528MHz processor virtually identical to one inside the Dream and Magic, and it has the same 288MB of RAM as the latter. Frankly, it's not enough. At least not with HTC's custom user interface, more than a couple of widgets and an application running. Killing all of the widgets—especially the Twitter one—does help. But moments where the phone does nothing for a second or three after you've tapped, flicked or swiped happens far too often. Which is to say, a lot, especially after it's been on for more than an hour. Fast, totally smooth transition animations are infrequent enough I'm pleasantly surprised when a desktop screen immediately and gracefully slides to the left or right without a hiccup. It's frustrating"
sounds like it doesn't that much better than hero on our g1's, which is sad for such a lovely gui.
tho I all I would really want from rosie/sense/touchflo is people/albums twitter and facebook integration as well as the twitter widget.
to really i'd love to have all the damned widgets, even the stock widget that no one here seem's to want, onyl if they could integrate it w/ google finance for the most real-time pricing available for free.
im running off on tangents tho..so i will stop..
Click to expand...
Click to collapse
My G1 running Hero is NOT slow at all:
http://www.youtube.com/watch?v=KxLZOhUA3R0
I don't know if you guys remember, but the original release of android was also plagued with sluggishness when it first came out. Browser scrolling was choppy, using browser and then going back home would cause a re-load (on a stock system). The hero is not much more different than then Dream in terms of hardware (the qualcomm processor uses the same ARM core, and I believe the only change between it and the Dream's is improvements in the radio), much more like the sapphire. I was too disapointed when I saw videos of the Hero device and saw slowdowns and sluggishness, and like Cyanogen pointed out, HTC basically built Touch-flo on top of running android processes without caring for either disabling or reusing them. The size of HTC's framework is about as big as the original Android system (considering how much of android they've taken off too).
I also have to wonder, though what it is people are perceiving as "speed". If, like Breakthecycle2, you're reffering to speed as just flicking the home screen from side to side without slowdown, then you're just considering the UI aspect of the whole system (and only the home app at that).
A system that runs lean, boots fast, keeps all systems shut until they're required, and is able to start them quickly on demand is really a fast system, and android sucks at that. Android is much like vista, it likes keeping the memory full and all services ready to make up for the shortcomings of running a VM, but the Dream is not a desktop computer, nor does it come equiped with 4 gb or ram where you can get away with doing just so.
I don't believe it's gonna change anymore either, programmers, companies, nobody really cares about optimizing runtimes anymore. We've been spoiled with increased capacities, speeds, etc that we're completely comforatble with wasting resources to use shortcut instead of solving challenges programatically (ie, loading up bitmaps instead of creating and using vectors, just because we have the storage for them and it's easier), and companies will settle with "good enough" or "fast enough" just to make a profit, after all, if it's selling, why spend money on improving it?

Acer A500 disapointment ...

Hello, I just bought an Acer A500, this is my first Android device (I own an iphone 3gs).
But I am very dispointed by its speed. I was hoping it would be as fast and smooth (at least !) as my old iphone 3gs but it's not ... When you scroll a web page it's not smooth, whatever the web browser I tried, even single web page as Google !
The only smooth scrolls are when you use the photo browser or when you scroll through the icons pages. For the rest, even the Android Market app, it's not smooth at all.
So is there any optimisation we can do to let the A500 display everything smoother, or is it just an Android 3.0 problem which may be corrected in a future release ?
Thanks
The coming Android OS 3.1 will be better. The update including the browser stability and smoothness.
.
Sent from my A500 using XDA Premium App
Thanks, I just hope now the 3.1 will come quickly to the A500 and that it will really be smoother ...
My experience with the A500 is very fluid. I find that browsing to be "fast & smooth" as well. So, I'm left scratching my head that your receiving a better browsing experience on a 3GS. Could you upload a video sample on youtube? Some people have reported wifi issues with their device and that could be the culprit to your browsing experience. See if coming in close proximity of your wifi AP improves your browsing experience. If so then search this forum for what others have done to resolve the wifi issue. I am not having an issue so I have not further investigated the wifi issue.
Sent from my Nexus S 4G using Tapatalk
The browsing experience is a pain in the ass... but that is not from ACER it's from honeycomb...
the stock browser is still unstable and buggy and not support HTML5 and CSS3 as promissed...
and some function supported already by Iphone (field url and email for input do not trigger the good keyboard)
no smooth animation on javascript it s choppy and lost a lot a frame...
-- EDITED --
When I say a pain in the ass I mean, only if we want make or build animated javascript website
http://www.thewildernessdowntown.com
this should be SMOOTH...or maybe I expect too much from "high-end" tablet dual-core.
HTML form field url/email
Issue16401 : http://code.google.com/p/android/issues/detail?id=16401
SenchaMobile.
http://dev.sencha.com/deploy/touch/examples/kitchensink
-- animations ... choppy and not smooth at all...
-- Buttons ... rounded are... weirdly rendered but that is not a real issues from the android, but probably from webkit or more from also sencha methods.. but still
flickering on any page change...
you can see this flickering also when you are on form fields
-- FEEDBACK --
I do not mean anything wrong, I said before that Android 3.0 is young and will grow up by time with better and better things to come I love android and I love Acer Tablet, really good products
-- 3.1 --
it's come in this month "confirmed by Acer Thailand" but no final date yet...
So far my disapointment are not same
I just see the UI improvement on Samsung Galaxy 8.6... it's so nice the UI is sweeeeet
the status bar, with the turn on/off many things...
the fast app launcher on the bottom... WoOow sweet...
I hope we will got some flavor of it
IMPORTANT:
I own 2 tablets Acer A500
I own 2 Liquid Metal S120
You should probably return it. Nobody has yet had these issues, so it might be something wrong with your tablet.
@bec07 : who ?
You and the OP.
It is important to note that not all websites are created equal. I have fast and smooth experiences with some sites and horrible one with others. There are too many variables from code quality, embedded media and offsite advertising, amount of content on a given page etc to truly quantify a 'good' or 'bad' browsing experience.
Sometimes it's good, sometimes it's bad. Some of it has to do with the browser, some has to do with the page you're loading.
gammaRascal said:
It is important to note that not all websites are created equal. I have fast and smooth experiences with some sites and horrible one with others. There are too many variables from code quality, embedded media and offsite advertising, amount of content on a given page etc to truly quantify a 'good' or 'bad' browsing experience.
Sometimes it's good, sometimes it's bad. Some of it has to do with the browser, some has to do with the page you're loading.
Click to expand...
Click to collapse
Agree, google.com is fast for me, but this site xda is very slow.
I use Dolphin HD browser... faster and more features.
Basicly all tablets are identical at this point. Some thinner, some thicker but only one manufacturer was smart enough to add the full size USB port.
Since the hardware is identical and it really packs quite a punch those issues should not happen. It would be best they check with their retailer or inconspicuously go to try out another A500.
Bec07 said:
Basicly all tablets are identical at this point. Some thinner, some thicker but only one manufacturer was smart enough to add the full size USB port.
Since the hardware is identical and it really packs quite a punch those issues should not happen. It would be best they check with their retailer or inconspicuously go to try out another A500.
Click to expand...
Click to collapse
I have 2 tablet and both are identical so I should change all tablet... naaaa don't think so.
I do think the 3.1 will remove some flickering glitch, and smooth maybe the javascript animation and css animation stuff. but for sure some website are poorly coded or got a DOM overloaded that eat the memory.
I do compare Sencha Touch website between iPad 1 and Acer A500... sad that run smoother on the old old iPad rather than on the new A500
but read really, I said the honeycomb and android is still young and buggy and will be better day after day because of the active community and the open mind of the code. do not interpret or miss understand.
It's a fact that browsing is not that smooth that should be, but it's already good.
now have to become the BEST.
(someone told me on the galaxy S II the browser was.... too fast for rendering it's tooooo good, but I didn't check about flickering or else)
I would have to agree with the first post, the web browsing experience is not as nice as iOS in regards to smoothness/scrolling, comapred to my iphone4 and former ipad1, but its not that bad either.
looking forward to 3.1.
sencha was developed with iPhone in mind, that's not really a valid comparison.
sollie said:
Agree, google.com is fast for me, but this site xda is very slow.
Click to expand...
Click to collapse
Just change the theme to xda classic and here you go
Today I checked xoom 3.1 videos on youtube, and I'm still disapointed ...
Browsing the web is faster but still not as smooth as it should be.
And not only the web, also the other apps were not 100% fluid.
I don't know if I will wait until the 3.1 comes to the A500 ... I may sell it quick (only owned for 2 days !) and buy an iPad. And believe it or not : yesterday I have been to the hospital because of an epilleptic crisis I did while using the A500, because of the non-smooth scrollings ...
My point of view is that a pad experience seems magic when it's 100% fluid, without this the pad experience seems not far from a laptop experience, which is not what I was searching for.
New android users always feel that. U can easily change ur the launchers such as Launcher Pro which is very smooth and fast in my opinion. There are tweaks around for you to look for and learn while experiencing Android =)
dizzy33 said:
Hello, I just bought an Acer A500, this is my first Android device (I own an iphone 3gs).
But I am very dispointed by its speed. I was hoping it would be as fast and smooth (at least !) as my old iphone 3gs but it's not ... When you scroll a web page it's not smooth, whatever the web browser I tried, even single web page as Google !
The only smooth scrolls are when you use the photo browser or when you scroll through the icons pages. For the rest, even the Android Market app, it's not smooth at all.
So is there any optimisation we can do to let the A500 display everything smoother, or is it just an Android 3.0 problem which may be corrected in a future release ?
Thanks
Click to expand...
Click to collapse
Ipads have had probably What? 50 updates. A500 had one so far. I have the A500 and my wife's has the Ipad. I think I updated my wife Ipad 3 times since Christmas ( hour or longer updates ) Give it some more updates and the A500 will shine. The way both Tablets are now if I had to sell one of them it would be the Ipad. The only thing I like better about my wife's Ipad is, I can plug it directly into our digital camera and get pictures real fast, but you also have to buy the 30.00 adapter to do this and now you have something more to lose and carry around. JM2C
This is the difference with Apple : with Apple it works fine out of the box, of course a few bugs are corrected in firmware updates but these bug do not avoid you to use your pad.
With Android I feel like in the bad days of Windows mobile : you have to wait for the manufacturer promeses before being able to use your pad properly, but most of the time windows mobile devices never worked as expected ... That's the problem of having one operating system for hundred of devices with different hardwares.
I would be very happy to keep my A500 mainly because of the included usb port, but also because of the price and the fact that Android is more "open", if only Acer would have given us a 3.1 release date I would feel better.
Edit : this time it's sure, I will sell it !!! A current bug let me type very slow on the keyboard, this is the last bug I will accept ! Another big problem has been found : the button bar on the bottom of the screen : I often touch it while using the A500 which freezes the screen ....
I guess I will wait for 3 or 4 more years before going back to Android ! For now I'll stay with Apple.
Thanks anyway to all of you !

samsung galaxy 10.1 major disappointment

I have owned the samsung galaxy 10.1 for approx 2 weeks. I sold my IPAD 2 to purchase as I have always been a fan of android phones. So far, I find the galaxy to be very unpolished. For example, the screens lag when navigating and apps force close to much. When I scroll up and down on the UI, its not smooth as butter like the IPAD. When I change the screen orientation, its very choppy. The IPAD runs circles around this device. I wish it wasnt the case as I wanted to like it. Even the on screen keyboard is hard to type on. Try copying and pasting a sentence. The arrows you use to drag across the words never line up with what is being clicked. I am not sure how anybody finds this device to be a pleasant experience unless you are in denial and I am not talking about the river. Maybe Ice Cream will fix some of the issues. For now, the tablet serves as a perfect example of what happens when technology is rushed to the market without consideration of quality.
I feel better now.
Lance
Take the time to tweak your device with everything available on these forums, it becomes an entirely different device.
Sent from my Samsung Fascinate
lancer123 said:
I have owned the samsung galaxy 10.1 for approx 2 weeks. I sold my IPAD 2 to purchase as I have always been a fan of android phones. So far, I find the galaxy to be very unpolished. For example, the screens lag when navigating and apps force close to much. When I scroll up and down on the UI, its not smooth as butter like the IPAD. When I change the screen orientation, its very choppy. The IPAD runs circles around this device. I wish it wasnt the case as I wanted to like it. Even the on screen keyboard is hard to type on. Try copying and pasting a sentence. The arrows you use to drag across the words never line up with what is being clicked. I am not sure how anybody finds this device to be a pleasant experience unless you are in denial and I am not talking about the river. Maybe Ice Cream will fix some of the issues. For now, the tablet serves as a perfect example of what happens when technology is rushed to the market without consideration of quality.
I feel better now.
Lance
Click to expand...
Click to collapse
Not sure if you are trolling here, but eh, I'm bored so I'll bite.
Those of us who find the Tab to be a pleasant experience must be in denial huh? Don't you think that's a pretty presumptuous and arrogant statement? How do you know what my experience with it has been? Or anyone else's for that matter?
I would usually sit here and try to help you solve your lagginess issue, maybe seeing if you have some sort of rouge process going on or if you are even on the latest firmware. Maybe point you to some of the great custom ROMs the developers here have given us. But, nope. You speak for everyone and everyone must be having the same ****ty experience as you, and if we say we don't we must be lying.
I will tell you though that my experience has been fantastic. The only time I get lag on the homescreen is when I have a live wallpaper up. I've never had any browser lag or lag anywhere else. I have a ton of widgets on my screens too. No lag. Of course though I'm totally lying, but you knew that already right?
I'm finished being sarcastic. Honestly if you aren't happy with the device, go sell it and get an Ipad again. Nobody is stopping you. The Tab is a fantastic product and I would go so far as to say it is the best tablet on the market as of this very moment. But it is not for everybody, especially for people who have no idea what they are doing.
Posting threads like this serves no purpose other than being a troll and drawing the ire of members like myself.
lancer123 said:
I have owned the samsung galaxy 10.1 for approx 2 weeks. I sold my IPAD 2 to purchase as I have always been a fan of android phones. So far, I find the galaxy to be very unpolished. For example, the screens lag when navigating and apps force close to much. When I scroll up and down on the UI, its not smooth as butter like the IPAD. When I change the screen orientation, its very choppy. The IPAD runs circles around this device. I wish it wasnt the case as I wanted to like it. Even the on screen keyboard is hard to type on. Try copying and pasting a sentence. The arrows you use to drag across the words never line up with what is being clicked. I am not sure how anybody finds this device to be a pleasant experience unless you are in denial and I am not talking about the river. Maybe Ice Cream will fix some of the issues. For now, the tablet serves as a perfect example of what happens when technology is rushed to the market without consideration of quality.
I feel better now.
Lance
Click to expand...
Click to collapse
I bought mine a couple weeks back too, and my experiences are similar to yours. I still can't understand how a dual core device can be this laggy! I'm hoping its all due to the Samsung bloatware, so I'm going to load up a custom ROM over the weekend and see how that goes... you should try it too
I really like the additional screen space coming from a 4.2" Xperia Arc, and Honeycomb is a lot zippier now than it was back in April when I had the Xoom for a couple of weeks. I still believe its a better tablet than the iPad2 though. That thing seems so zippy because all it is is a magnified iPhone. There's almost nothing running in the background which gives it the appearance of being a lot quicker and better battery life. Load it up with widgets and lets compare them then.
My biggest problem though, is the lack of a good pdf app. I've tried tons of them and they are all really slow to load, very jerky pinch to zoom, and slow scrolling. Hope this improves with ICS
And to the poster above this, I don't get why you even bothered posting if you're going to be so incredibly unhelpful
lancer123 said:
I have owned the samsung galaxy 10.1 for approx 2 weeks... I am not sure how anybody finds this device to be a pleasant experience...
I feel better now.
Lance
Click to expand...
Click to collapse
Lance,
I have watched my brother in law's ipad closely, and you are right. It is faster and more responsive (once tweaked) than my SGT was out of the box. However, the others are right too.
I have rooted and tweaked my SGT and it now makes my ios friends raise their eyebrows. You happily partied all over your ipad, making many changes suggested on user sites like this one. Now you need to do the same with your SGT. If you are unable or unwilling to do that, you are not an idiot or a molester of small animals, you are just one of those people that the ipad was designed for. So get another one, and enjoy it.
I prefer my Android gadgets, because they are more flexible. I am not locked into iTunes, and I have access to my 650GB music library that is not as compressed as AAC. I have a FREE SDK that works rather well, when i want to write my own apps. There are a few paid apps that I depend upon for day to day stuff, just like I would for iOs devices. For me, and many of the others in this form, that is what they want.
Sent from a distant planet with the aid of my towel.
lancer123 said:
I have owned the samsung galaxy 10.1 for approx 2 weeks. I sold my IPAD 2 to purchase as I have always been a fan of android phones. So far, I find the galaxy to be very unpolished. For example, the screens lag when navigating and apps force close to much. When I scroll up and down on the UI, its not smooth as butter like the IPAD. When I change the screen orientation, its very choppy. The IPAD runs circles around this device. I wish it wasnt the case as I wanted to like it. Even the on screen keyboard is hard to type on. Try copying and pasting a sentence. The arrows you use to drag across the words never line up with what is being clicked. I am not sure how anybody finds this device to be a pleasant experience unless you are in denial and I am not talking about the river. Maybe Ice Cream will fix some of the issues. For now, the tablet serves as a perfect example of what happens when technology is rushed to the market without consideration of quality.
I feel better now.
Lance
Click to expand...
Click to collapse
I understand how you feel, and I felt the same way when I first handled the SGT 8.9 the UI lag was horrendous .. I felt the product manager of the device should be sacked (or worse done to him) for ever allowing such a device out the door in such state. To make matters worse for me, there was an ipad close by and the UI flow was like watching man utd beat arsenal 8-2 .. I promptly returned the device.
However my opinion has since change since coming here lots of people have filled me in with some tweaks and work around which resolves most of the laggy issue. (You can check out the SGT 8.9 Q & A section its a sticky under this section for people experience with the device)
First of if you can't be bothered to root your device, try the ADW launcher ex, everyone who tried that said its greatly improves the performance and eliminates the lag issue.
You can also if you are feeling adventurous root the device. And install some of the numerous roms around.
just try and take advantage of the open nature and make it yours. Soon ipad owners would be looking at your tab and feeling the envy.
Just my 2 cents
Sent from my GT-I9100 using XDA App
Please go get your ipad back dude. I have none of the issues you speak of. This thread is a total waste. I don't even believe you own a tab.
By saying "you like Android phones" I'm assuming you mean in comparison to the iPhone. Most of the same issues you’re experiencing in an Android vs. iPad tablet comparison apply to a phone comparison also so your statement's kind of confusing.
iOS is so "buttery smooth" because it's locked down like a prison with Apple exerting Orwellian control over the entire eco-system. I bought my G-Tab and paid more than an equivalent iPad because, for what I do, the collection of individual apps works better than the homogenous equivalents on the iPad. And I did that knowing the iPad had a better display and that the UI and navigation were smoother and more mature.
This forum is fascinating because of the disparity in experiences everyone has. I've had two G-Tab's (Wi-Fi and 3G) and never had a force close on either and I have over 50 apps installed. There's occasional stutter and lagginess but I'd say it appears (for me) less than 5% of the time. One huge difference between iOS and Android is that Android, with its limitless ability to be tweaked, can get hosed by people using badly written apps and the use of memory managers, task killers, battery monitors and the like. Every XDA forum I participate in has people *****ing about some function being hosed and then go on to elaborate about all the crap they've done to their device and ****ty low-rent apps they're using. And they don’t understand why their phone’s getting crappy battery life and has tons of issues no one else seems to be experiencing. I guess freedom comes at a price and it can be abused.
I've had a G-Tab in one form or another since August and have been really satisfied with it. I took my new 3G version on a trip over the weekend and it performed flawlessly and got fantastic battery life with 3G active continuously and download speeds of 8MB in TX (vs. less than 1MB for an iPad). I sat across from someone using an iPad on the flight home last night. The local video he was playing was gorgeous. Compared to mine, his WSJ app looked like crap as did Solitaire and a bunch of other stuff I saw him use. Meanwhile, I was streaming Hulu, HBOGO, and TV shows from my home server using the planes Wi-Fi. I can also play music I have stored on my home server, the Amazon cloud, or from the 2K songs I store locally using my $9.99 Rhapsody monthly subscription. All while reading magazines and newspapers using Next Issue and Press Reader. I’d gladly trade options and versatility for “buttery smooth” any day. iOS is great for a subset of device owners because of its constraints and consistency. But those restrictions are why I chose Android. Android can become smoother through s/w and h/w evolution but iOS will never become more open. Hopefully OP bought his G-Tab somewhere with a liberal return policy so he can return it.
BarryH_GEG said:
By saying "you like Android phones" I'm assuming you mean in comparison to the iPhone. Most of the same issues you’re experiencing in an Android vs. iPad tablet comparison apply to a phone comparison also so your statement's kind of confusing.
iOS is so "buttery smooth" because it's locked down like a prison with Apple exerting Orwellian control over the entire eco-system. I bought my G-Tab and paid more than an equivalent iPad because, for what I do, the collection of individual apps works better than the homogenous equivalents on the iPad. And I did that knowing the iPad had a better display and that the UI and navigation were smoother and more mature.
This forum is fascinating because of the disparity in experiences everyone has. I've had two G-Tab's (Wi-Fi and 3G) and never had a force close on either and I have over 50 apps installed. There's occasional stutter and lagginess but I'd say it appears (for me) less than 5% of the time. One huge difference between iOS and Android is that Android, with its limitless ability to be tweaked, can get hosed by people using badly written apps and the use of memory managers, task killers, battery monitors and the like. Every XDA forum I participate in has people *****ing about some function being hosed and then go on to elaborate about all the crap they've done to their device and ****ty low-rent apps they're using. And they don’t understand why their phone’s getting crappy battery life and has tons of issues no one else seems to be experiencing. I guess freedom comes at a price and it can be abused.
I've had a G-Tab in one form or another since August and have been really satisfied with it. I took my new 3G version on a trip over the weekend and it performed flawlessly and got fantastic battery life with 3G active continuously and download speeds of 8MB in TX (vs. less than 1MB for an iPad). I sat across from someone using an iPad on the flight home last night. The local video he was playing was gorgeous. Compared to mine, his WSJ app looked like crap as did Solitaire and a bunch of other stuff I saw him use. Meanwhile, I was streaming Hulu, HBOGO, and TV shows from my home server using the planes Wi-Fi. I can also play music I have stored on my home server, the Amazon cloud, or from the 2K songs I store locally using my $9.99 Rhapsody monthly subscription. All while reading magazines and newspapers using Next Issue and Press Reader. I’d gladly trade options and versatility for “buttery smooth” any day. iOS is great for a subset of device owners because of its constraints and consistency. But those restrictions are why I chose Android. Android can become smoother through s/w and h/w evolution but iOS will never become more open. Hopefully OP bought his G-Tab somewhere with a liberal return policy so he can return it.
Click to expand...
Click to collapse
The stuff you speak of is why I have ran Linux exclusively on my PC for close to 5 years now. Yet I think the OP has a point and was just letting out steam. I too was extremely disappointed when I handled the galaxy tab (in my case it was the 8.9) right from boot the experience was horrendous and the UI lagged SOO much it was embarrassing. This first impression was a real turn off for me and I can understand the feeling of someone who gets a device with such awesome hardware only be bugged down with software. Sure you can always improve with tweaks and mods but if android is ever gonna replicate its success on mobile on tablets. Then the out of the box experience most be killer. Having and awesome out of the box experience and ability to further tweak should not be mutually exclusive. The experience I got on my galaxy s2 even with default rom was exquisite. Just breath taking. Even without Modding or installing a custom rom. That's what I expected from honeycomb. Hopefully most of this out of the box issues would be fixed with honeycomb 3.2 and ICS.
Sent from my GT-I9100 using XDA App
I must agree with OP. Its a f****g ambaresment how a product can be released in the state it was when it was in the box. Now after tweaking and rooting and flashing and using it for a couple of months its useable. But it still lags, not all the time , but try installing something form market and then go to homescreen, right then its laggy as hell.
But we all know this by now, so i agree with the rest of you that we have no need for this thread. And if OP just read a little before buying he would have found this info about the tab. Anyways welcome hope you get your tab sorted.
nickwarn said:
I must agree with OP. Its a f****g ambaresment how a product can be released in the state it was when it was in the box. Now after tweaking and rooting and flashing and using it for a couple of months its useable. But it still lags, not all the time , but try installing something form market and then go to homescreen, right then its laggy as hell.
But we all know this by now, so i agree with the rest of you that we have no need for this thread. And if OP just read a little before buying he would have found this info about the tab. Anyways welcome hope you get your tab sorted.
Click to expand...
Click to collapse
Same experience here.... I've even rooted my tab and it did improve but not as much as I would of liked, this was a month ago though, so i don't know if anything better has comed out. I've thought about getting an iPad but..... I just can't if it can't play flash.... How the hell could you own a tablet and not watch a simple flash video. So if anyone can give me advice on how to make my 10.1 as smooth as some of you have said, then please do tell me how. I love my Gtab but the lag does really bother me enough to have had to remove all my widgets....
Sent from my Nexus S 4G using XDA App
shoo troll.
Klk450 said:
Same experience here.... I've even rooted my tab and it did improve but not as much as I would of liked, this was a month ago though, so i don't know if anything better has comed out. I've thought about getting an iPad but..... I just can't if it can't play flash.... How the hell could you own a tablet and not watch a simple flash video. So if anyone can give me advice on how to make my 10.1 as smooth as some of you have said, then please do tell me how. I love my Gtab but the lag does really bother me enough to have had to remove all my widgets....
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Root your tab is only the first step. You need to flash custom rom after you root your tab, then only you can feel the difference.
I just got my tab last week, wifi only version. I can say I'm really satisfied with the performance and I love my tab. The basic steps are:
1. root your tab
2. flash custom rom
That's all you need to do to feel the difference. You can ignore some of the gimmicks, for instance supercharger, overclock kernel and etc that have been mentioned if you have no freaking idea what they are about at the moment. You will pick them up along the way just like I did.
The one tip that everyone here would tell you - READ THE FORUM!
For instance, the first sticky post in the Galaxy Tab 10.1 Android Development is a good read and good resource to get you started. Here's the link if you have no idea where it is (Seriously?): http://forum.xda-developers.com/showthread.php?t=1171089
lancer123 said:
I have owned the samsung galaxy 10.1 for approx 2 weeks. I sold my IPAD 2 to purchase as I have always been a fan of android phones. So far, I find the galaxy to be very unpolished. For example, the screens lag when navigating and apps force close to much. When I scroll up and down on the UI, its not smooth as butter like the IPAD. When I change the screen orientation, its very choppy. The IPAD runs circles around this device. I wish it wasnt the case as I wanted to like it. Even the on screen keyboard is hard to type on. Try copying and pasting a sentence. The arrows you use to drag across the words never line up with what is being clicked. I am not sure how anybody finds this device to be a pleasant experience unless you are in denial and I am not talking about the river. Maybe Ice Cream will fix some of the issues. For now, the tablet serves as a perfect example of what happens when technology is rushed to the market without consideration of quality.
I feel better now.
Lance
Click to expand...
Click to collapse
I agree with you on most counts, except that I don't have any issues with the onscreen keyboard and don't get force closes. There are some things you can do to improve the user experience (alternate launchers, overclocking etc), however it still won't feel like the iPad.
That being said, there are things you can do with the tablet out of the box which you can't do with an iPad:
- Adobe Flash support
- Emulation apps availability (SNES, DOS, Scumm)
- File / Directory browsing
- UI customization
- Non-market / store applications installation
While I would love the overall UI performance to be on par with the iPad, given a choice between the two I would rather have the above functionality instead. There is also the possibility of Android's UI performance improving in the future with all this functionality retained. In case of Apple, apart from limited UI customization perhaps, the other stuff is just not going to be available ever.
PS: And all that's just out of the box, if you root your device there's some far more interesting stuff you can do with the tablet!
---------- Post added at 01:01 PM ---------- Previous post was at 12:57 PM ----------
pngface said:
My biggest problem though, is the lack of a good pdf app. I've tried tons of them and they are all really slow to load, very jerky pinch to zoom, and slow scrolling. Hope this improves with ICS
Click to expand...
Click to collapse
You have probably tried it already, but EZ PDF is pretty good. I am comparing it to GoodReader on the iPad and I don't have any issues with loading / scrolling / flipping / resizing.
Of course, this maybe dependent on the size and content of the PDFs you are using, so YMMV -- I mostly read book-sized documents, mostly text, and it works fine for me.
I recently bought a GalaxyTab and I have to confirm, it is quite laggy - In comparison to an iPad.
There are several things which can drastically improve the situation:
Use ADW Launcher EX
Custom ROM, Like Task650/Phantom Extreme Stock
Overclock (although, this didn't change a lot)
I found that the first two points are the most important. ADW Launcher makes the whole Homescreen and Applauncher absolutely smooth, just like on an iPad. And no, the stock launcher isn't.
It's great how many possibilites we have with Android, but be honest - I'd rather have ICS without any new features, but just great performance increases. Thats why I switched to Windows Phone in the first place - I don't want apple, but I want smooth scrolling, smooth transitions. And now, just because Android has much more possibilites doesn't mean it has the right to be slow and choppy. Take a look at the Windows 8 Developer Preview. My god, this isn't even an ALPHA and boy it's SO SMOOTH, I cried almost when I saw that.
The only reason I bought my Galaxy Tab is, that Microsoft still needs about a year until their first tablets are out - And I hate waiting
So please Google, get your Team together and tell them to START OPTIMIZING.
PS:
ezPDF is quite good - But the UI is horrible, and I miss the feature to insert Pages into a PDF. Mandano seems a lot more polished and faster, but misses a lot of annotation features.
I agree with the original poster. My tab is rooted, custom rom, adw, etc. My wife's ipad is a far smoother experience than this tablet. Would I switch back to the ipad prison? Not in a million years. My tablet does so much more than the ipad. If an example is needed, how about my choice of swype or thumb keyboard.
root your tab and wait for an ICS port... ICS is said to have hardware acceleration. That is the only thing Honeycomb lacks and that is why its not as smooth as the iPad...
OR
Flash a custom ROM such as Overcome 1.2.1 (didnt like 1.2.2 or 1.2.3) or w/e other one suits you and then come back edit the OP with the overall news... don't judge this book by its cover and remember its NOT iOS
A newbie when rooting is involved but i was wondering if you could give me an idea of what tweaks you have made? i'm considering rooting my device but unsure of what i could do to make it better.
Cpt Streamline said:
A newbie when rooting is involved but i was wondering if you could give me an idea of what tweaks you have made? i'm considering rooting my device but unsure of what i could do to make it better.
Click to expand...
Click to collapse
Flashing a custom ROM is the big one, will make a huge difference. I am using Task650 & Phantom's "In Paris V4". I also installed pershoot's kernel and overclocked.
The experience
I love my Galaxy Tab in comparison to my previously owned iPad but the reason is simply because I like playing with roms and hacking to get the most of my device. On my iPad, I felt too restricted and forced to use software I didn't like. Yes, some of the apps are better on the iPad and yes, the interface is a bit smoother but it's nowhere near as attractive and it's far too limiting.
A friend of mine equated the iPad experience with being put in a padded room where he can't hurt himself and everything if fluffy and safe feeling. It made me laugh but somewhat sums up the experience. Personally, I'd rather not be spoon fed the experience but would rather create my own and make it about me.
My hope is that ICS will be a significant jump. realistically, Android tablet manufacturers should be trolling these forums for employees who can tweak up their software.. Why they don't do this, one will never know.
Either way, I don't think attacks on the Op are warranted. These forums are here for people to both vent and discuss like the adults we are.

Former Google intern explains why UI lag occurs more often in Android than iOS

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.

Browser stutter

Perfectly smooth scrolling web pages are something that I've become accustomed to with the Ipad's I've had while waiting for a decent Android tablet. I thought the Nexus 10 would finally offer the smoothness of the Ipad with 4.2 and the awesome Exynos processor. Sadly, I can't find a browser that is nearly as smooth as Safari on the Ipad. I tried every browser I could find in the Market and even rooted and installed the AOSP browser. The AOSP browser is the best, but on image heavy sites, it still stutters.
Am I the only one that is bothered by this?
Why can the Nexus 10 run graphic heavy games at 30-40 fps but can't render a damn webpage with static graphics smoothly?
Also, I've found quite a few apps don't have smooth scrolling, but I suspect poor coding is causing the issue on them, even though knowing the cause doesn't help that that they are still inferior to their Ipad counterparts.
I don't want to go back to an Ipad! Will custom ROMs, kernels and OCing smooth it out?
The reason certain browsers including Chrome "stutter" is because of how it's coded. I've been using boat browser and I have no stutter issues or smoothness problems. Which other browsers have you tried other than aosp browser?
Sent from my Nexus 10 using xda app-developers app
I don't think browsers are optimized for the Nexus 10 or Android 4.2 just yet, hell, I don't think 4.2 or the Nexus 10 drivers are fully optimized at this time, but what I'm seeing of Dolphin and Boat Browser in the following video is pretty darn good, skip to 10 and 20 minutes.
Performance issues on this tablet are very likely software optimization issues and will be fixed eventually. Don't believe all the bad press that makes up stuff as they go along by saying the Exynos chip can't handle the resolution. That's garbage, and shows a pretty big misunderstanding of the processor/GPU. What amazes me is that even major tech sites with people who should know what they are talking about are saying it, and it drives me nuts.
The tablet has been out for less than a week. Developers need time to catch up, including Google with Chrome. If you look at the history of Nexus devices, they have always shipped with software issues, including very blatant issues that should have been fixed before release. The beauty of owning a Nexus however is that bug fixes come right from Google...no waiting on an OEM to deliver them.
A lot of the same issues were leveled against the Nexus 7, and after a couple of OTAs things have been greatly improved, and now everyone loves that tablet. Give it time. Things will get better.
MMcCraryNJ said:
Performance issues on this tablet are very likely software optimization issues and will be fixed eventually. Don't believe all the bad press that makes up stuff as they go along by saying the Exynos chip can't handle the resolution. That's garbage, and shows a pretty big misunderstanding of the processor/GPU. What amazes me is that even major tech sites with people who should know what they are talking about are saying it, and it drives me nuts.
Click to expand...
Click to collapse
Google is partially to blame, they handed out a pre-release stuttery models to reviewers after all. Things are better since the 13th update, but Chome is still doing the Nexus 10 a great disservice. Let's see how sites such as GSM and PhoneArena who patiently waited for the final model judge it, I think it's safe to say first impressions mean a lot, and they are testing units with fresh SW, multi-user accounts and performance improvements out of the box. Of course, as you said, there's plenty of performance still to come, and I can't wait to get mine!
johno86 said:
The reason certain browsers including Chrome "stutter" is because of how it's coded. I've been using boat browser and I have no stutter issues or smoothness problems. Which other browsers have you tried other than aosp browser?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the rationale responses so far. Google is really shooting themselves in the foot with the lack of polish on Chrome, Android, etc. They are doing well overall, but just think of how good they could be doing with a few improvments to user experience here and there! Hire the programmers to make it happen Google!
I tried the Boat Browser and it was decent but not buttery smooth like Safari on the Ipad. I'll reinstall it and post a youtube video of the stutter tonight when I get home.
Boat Browser is the best. Safari might be a bit smoother but that is because you can't scroll as fast as Boat and Dolphin. Scroll it at the same speed for both if your hands is steady enough to slow scroll boat and you will see it is the same ****.
Don't let the i-tricks fool you by hiding stutter with animation and masking page load speeds with both a load bar and a background image loading spin wheel.
Also, after using some of the features on Boat, such as the screen shot and auto scroll top of the page or bottom of the page touch icon, you will never use another browser.
Have you tried Dolphin with Dolphin Jetpack addon? Just make sure you turn on jetpack in Dolphin setting. It's off by default.
Sent from my Transformer Prime TF201 using Tapatalk 2
Chrome sucks. End of story. But it's not like the iPad is perfect either. I just browsed on my sisters iPad 4. It was quite a nice experience, I can't deny that, but there was some tiny lag on sites like Engadget and Android police
Sent from my HTC One S using xda app-developers app
slide83 said:
Thanks for the rationale responses so far. Google is really shooting themselves in the foot with the lack of polish on Chrome, Android, etc. They are doing well overall, but just think of how good they could be doing with a few improvments to user experience here and there! Hire the programmers to make it happen Google!
I tried the Boat Browser and it was decent but not buttery smooth like Safari on the Ipad. I'll reinstall it and post a youtube video of the stutter tonight when I get home.
Click to expand...
Click to collapse
I don't think you'll see Android be as smooth as iOS anytime soon. They are fundamentally different architectures and I think Google will likely stick with what they have in Android and wait for the hardware to catch up. Hardware was finally catching up starting with this generation but the large jump in resolution presents a *slight* setback in performance.
9 times out of 10 Jellybean is smooth enough for me. It is much better than it was in the past.
As for Chrome:
Like I've stated before, most of the development effort going into Chrome for Android for the last 6 months has been to upstream and open the source code rather than on performance and bugs. This is why Android is still on Chrome 18 while other platforms are on 24. There are several bug fixes that we'll get once they release Chrome 24 or 25 for Android, including a bug that makes Chrome laggy to scroll busy webpages.
Once Chrome is fully upstreamed, which looks like it might be for Chrome 25, it will then also be fully open source. This means we have make our own builds and do it as frequently as we want. Additionally, it is likely that we will see a much faster pace of development for Chrome as well.
slide83 said:
Thanks for the rationale responses so far. Google is really shooting themselves in the foot with the lack of polish on Chrome, Android, etc. They are doing well overall, but just think of how good they could be doing with a few improvments to user experience here and there! Hire the programmers to make it happen Google!
I tried the Boat Browser and it was decent but not buttery smooth like Safari on the Ipad. I'll reinstall it and post a youtube video of the stutter tonight when I get home.
Click to expand...
Click to collapse
As others have said, software optimization is key. The biggest issue is that they are dealing with a new SoC, so there is more involved than just CPU and GPU coding. Almost all Android hardware has been Tegra so far, so that code is certainly mature at this point. Comparisons at this stage can be unreasonable in some cases. While the Exynos 4 series has been in use in the Note 10.1, but the 5250 has a new core -- the A15, which no one has experience with AFAIK -- new GPU, new memory architecture... Also, it's possible that Samsung wrote the drivers for the Note 10.1 while Google is taking responsibility for the N10.
So, my point is twofold:
Firmware development for this platform is at an early stage of maturity.
Optimization will be complex and won't be as easy as writing a few simple patches.
I think it will take some time for this new platform to reach its potential. The early adopters, as always, will have to be patient. I hope that gives you some reassurance that your N10 will still meet or exceed your expectations... in time.
slide83 said:
Perfectly smooth scrolling web pages are something that I've become accustomed to with the Ipad's I've had while waiting for a decent Android tablet. I thought the Nexus 10 would finally offer the smoothness of the Ipad with 4.2 and the awesome Exynos processor. Sadly, I can't find a browser that is nearly as smooth as Safari on the Ipad. I tried every browser I could find in the Market and even rooted and installed the AOSP browser. The AOSP browser is the best, but on image heavy sites, it still stutters.
Am I the only one that is bothered by this?
Why can the Nexus 10 run graphic heavy games at 30-40 fps but can't render a damn webpage with static graphics smoothly?
Also, I've found quite a few apps don't have smooth scrolling, but I suspect poor coding is causing the issue on them, even though knowing the cause doesn't help that that they are still inferior to their Ipad counterparts.
I don't want to go back to an Ipad! Will custom ROMs, kernels and OCing smooth it out?
Click to expand...
Click to collapse
I have been an Android user for two years and in my honest opinion this is as good as it gets with it. There is something historically wrong with the core of Android where a game like Modern Combat 3 can look as smooth as silk, but browsing just feels like its being pushed to its limit.
A friend of mine this week bought himself a 32GB Nexus 7. I rushed round to have a play and was disappointed when trying out Chrome and Opera Mobile with these XDA forums. The Nexus 7 sported a quad-core processor and still browsing at times felt awkward and reluctant. It looked like the framerate wasn't right or the resolution was too much to handle. And that's with the latest update to Jelly Bean.
I did raise a similar issue with my Galaxy Tab 2 7" here and before anyone beheads me I had already flashed it with CM9 final. As I stated NOVA 3 was slick as oil, but browsing with Stock Browser, Opera Mobile and Chrome was making my eyes jump like mad. It looked like Chrome was trying to get around it by only rendering half the screen and then a split second later displaying the rest.
My niece's iPad 2 really impressed me when browsing on the XDA forums. The same pages I browsed on the Nexus 7 were scrolling as good as on a PC. Any comment that Android browsers scroll faster and therefore make the iPad look smoother is full of it. It was fast and it was smooth.
This will be last journey with Android. But that doesn't mean I'm gonna turn into an Apple user and get mugged off by paying ridiculous prices for a piece of their overinflated kit. My current smartphone and tablet will be with me for the next few years to come as the wow factor with all these mobile devices is disappearing, I'm afraid.
Easiest fix is ocean browser. Till they work out the kinks of chrome mobile/tablet version.
Also anyone saying safari on the ipads don't stutter are wrong they certainly do, perhaps not as often as chrome but it does happen. We use the gen 3's at work.
However to say there wasn't any conceivable improvement from Donut to JB I do find strange as I certainly did.
slide83 said:
Perfectly smooth scrolling web pages are something that I've become accustomed to with the Ipad's I've had while waiting for a decent Android tablet. I thought the Nexus 10 would finally offer the smoothness of the Ipad with 4.2 and the awesome Exynos processor. Sadly, I can't find a browser that is nearly as smooth as Safari on the Ipad. I tried every browser I could find in the Market and even rooted and installed the AOSP browser. The AOSP browser is the best, but on image heavy sites, it still stutters.
Am I the only one that is bothered by this?
Why can the Nexus 10 run graphic heavy games at 30-40 fps but can't render a damn webpage with static graphics smoothly?
Also, I've found quite a few apps don't have smooth scrolling, but I suspect poor coding is causing the issue on them, even though knowing the cause doesn't help that that they are still inferior to their Ipad counterparts.
I don't want to go back to an Ipad! Will custom ROMs, kernels and OCing smooth it out?
Click to expand...
Click to collapse
totally agree. for something that has great specs, its dissapointing to see it stutter when loading webpages. my ipad had lower specs compared to this and it was smoother by a mile than the nexus. i think thats the trade off for buying sometor buying something about to Mike about you can talk to my phone but they hired mejust too ****ing hi Billy.
okay the last part was typed using the voice and it sucks too.lol
Chrome currently really has its problems, but keep in mind that as dalingrin said, the mobile chrome version is 18 while the desktop version sits at 23. So there has been a lot of effort put into porting everything from desktop to android rather than bugfixing and polishing. The android version will catch up early next year: http://www.androidpolice.com/2012/1...s-including-android-starting-early-next-year/
In the meantime I recommend using the android stock browser. Its extremly fast and fluid and even supports flash.

Categories

Resources