I haven't seen any posts commenting on this issue too directly. I played with the Xoom in the Verizon store and noticed that although the UI animations were pretty smooth (with the exception of the app list fly-in, the rotation, and the page-turning in the reader, which all had a little frame stutter), the touch responsiveness in general still just wasn't quite up to par with the Ipad. When scrolling through homescreens there's a small but noticeable delay before the screen actually starts to scroll, whereas with the Ipad the scrolling seems to begin instantly. The Xoom is similar in feel to the Galaxy S phones, which were smooth but not quite as responsive as IOS, whose instantaneous responsiveness just inspires more confidence when you're navigating the device.
Ultimately it's a small difference but one that makes a big difference in the perception of the device's responsiveness. Is this a hardware or software issue? If Honeycomb finally has hardware acceleration, why are IOS and WP7 still ahead in this department? Is it because Android's more complex homescreens require more power to scroll? Is this due to something inherent in Android and Java? Is it possible that a future Honeycomb update might fix this completely? If someone with some expertise in the subject can comment on this, I'd really appreciate it. I fully expected Honeycomb to kill any complaints people could have about UI responsiveness, but it just doesn't seem to have happened yet, and I haven't seen any thorough explanation for it. Thanks a lot.
I just pulled out my Xoom and tested each of the things you talked about.
Auto rotation is slower than my phone.
Everything else is instant... though I have not used the reader. I have noticed stutter in the Kindle app.
But in the main UI, scrolling home screens and app list fly in is instant.
I have head of the auto rotate complaint and Kindle page turning complaint in other comments in this board and others... but the main UI? Nope.
I do not know what was the situation with the Xoom in the Verizon store, but in my personal usage the problem you describe does not exist... I think if it did on a wide basis, you would hear about it.
Describing something as a Hardware vs. Software issue in this case is non-productive. In every instance you can start with the hardware and say if it had more "oomph", you can often make a problem go away. Most issues like this can be dealt with in Software. The only time the whole thing is problematic is if the hardware is so underpowered in relation to what the software is trying to do. My guess is these things that are definitely happening (rotate, slow page turn) can be fixed in software, especially on this hardware.
My experience on the Android platforms is future updates fix first release issues.
My experience is also that extending future OS versions to hardware that cannot support them can be problematic, but Apple has experienced the same issue.
I have to agree that this is not as quick as I thought it would be.
I am blaming it on an app maybe, so I am removing everything back to stock.
The app list fly in is the worst. Looks better on my evo.
hctarks said:
I haven't seen any posts commenting on this issue too directly. I played with the Xoom in the Verizon store and noticed that although the UI animations were pretty smooth (with the exception of the app list fly-in, the rotation, and the page-turning in the reader, which all had a little frame stutter), the touch responsiveness in general still just wasn't quite up to par with the Ipad. When scrolling through homescreens there's a small but noticeable delay before the screen actually starts to scroll, whereas with the Ipad the scrolling seems to begin instantly. The Xoom is similar in feel to the Galaxy S phones, which were smooth but not quite as responsive as IOS, whose instantaneous responsiveness just inspires more confidence when you're navigating the device.
Ultimately it's a small difference but one that makes a big difference in the perception of the device's responsiveness. Is this a hardware or software issue? If Honeycomb finally has hardware acceleration, why are IOS and WP7 still ahead in this department? Is it because Android's more complex homescreens require more power to scroll? Is this due to something inherent in Android and Java? Is it possible that a future Honeycomb update might fix this completely? If someone with some expertise in the subject can comment on this, I'd really appreciate it. I fully expected Honeycomb to kill any complaints people could have about UI responsiveness, but it just doesn't seem to have happened yet, and I haven't seen any thorough explanation for it. Thanks a lot.
Click to expand...
Click to collapse
I'm not finding the same issues you are. The orientation delay is 100% intentional. I wish there were built in options that let you mess with the delay, but that will happen soon enough. I don't mind or notice this intentional lag in daily use.
I'm not finding any other lack of smoothness. I've played with iOS on many different devices, and I find my Xoom to be just as smooth. The iOS devices were smoother than my Droid X (always have been smoother than my phones), but I like what powerful hardware mixed with Honeycomb has shown me.
I'd certainly love to be wrong about this. Maybe it was the display unit that was faulty. But even though the homescreen scrolling was perfectly "smooth," it was more the delay in response that bothered me. When I set my finger down and swiped from one screen to another, there was always a very short, split-second delay before the screen started moving, which felt as if my finger was "slipping" for a few millimeters before gripping the homescreen. This probably isn't even something that I would have noticed if I hadn't been comparing it side-by-side with the display-unit Ipad, which, in comparison, seemed to start scrolling without even the tiniest delay, which ultimately gave the Ipad app list a more authentic sense of tactility.
It looks like Bielinsk is having a similar experience, so we know this isn't a completely isolated phenomenon. Maybe both Bielinsk's and my experience had to do with the specific units and installed apps, but even the possibility that installing a certain app can degrade the whole UI experience on Honeycomb seems to be a problem that IOS is less prone to. I've also read reviews, such as the one on Anandtech, that note that smoothness in Honeycomb is improved but not quite at IOS-level. Again, I hope I'm wrong. Everything else about Honeycomb seems fantastic, but the not-as-responsive-as-IOS issue just seems like something that Android can't fully shake.
Bielinsk said:
I have to agree that this is not as quick as I thought it would be.
I am blaming it on an app maybe, so I am removing everything back to stock.
The app list fly in is the worst. Looks better on my evo.
Click to expand...
Click to collapse
Please update us on whether wiping fixes the problem for you.
I uninstalled all the apps that are not Tablet apps and have the same issue.
Removed all widgets, except the clock.
I don't see any delay or pause changing home screens, but the app fly down list just really looks like ****. I put on spare parts and turned the animations to fast to see if that would help and it didn't see to do anything.
Actually the app fly-in frame-stutter was something that I first thought I noticed when Google demoed the tablet at their Honeycomb event. And then it seemed confirmed when I tried it myself at the store.
Yea, I noticed that when I played with one at Costco. I couldn't really tell if it was designed to look like that or not. I remember everyone raving during the Xoom's debut at CES about how smooth it was and using the app fly in as an example of said smoothness. Weird.
I think the lag and less responsive than expected phenomenon is absolutely real and undebateable even if some have not experienced it. We've seen it many times in online reviews and I have personally experienced it on demo units in store.
What it comes down to is development. Combinaton of hardware and software.
Although the experience is optimized on Android, it is prioritized on Apple.
That is the key idea you need to understand and unless the hardware and software BOTH prioritize it, Apple will always win here since they control both hardware AND software.
DatterBoy said:
That is the key idea you need to understand and unless the hardware and software BOTH prioritize it, Apple will always win here since they control both hardware AND software.
Click to expand...
Click to collapse
Well, but then you look at the fluidness of WP7 devices for which the hardware is made by companies that aren't Microsoft, and this argument doesn't really seem like the whole story.
I love my xoom, so this is not a complaint, but the device is not as smooth as I expected it to be. I have an og droid running one of the cm7 builds and overclocked to 1.2ghz. It is a much smooter device than my xoom in many situations.
I do not experience lag on my home screens or when using widgets, but the app fly in is crap and the browser scrolling is laggy. It was this way when I purchased it so I do not attribute it to any apps in particular. I just think honeycomb is in need of some coding polish.
Really makes me wonder if the dual core is being used for anything aside from keeping the CPU in a lower state of energy consumption for battery life. I wish there was some sort of widget that could show CPU usage so that I can see what is making use of the hardware and what is not.
Sent from my Xoom using XDA App
This is depressing. I really don't understand how it's possible that a hardware-accelerated version of Android on a dual-core device can be, in certain UI animations, consistently laggier than non-hardware-accelerated versions of Android on certain single-core phones.
Edit: For example, the app drawer fly-in on a Samsung Vibrant with a custom ROM or just Launcherpro is extremely smooth--seems like twice the framerate of the same animation on any other Android phone I've seen.
I have 100% the same thoughts/experience, I bought this on day 1, and when I had it up with zero apps it was throwing me similar lag to what has been described so far - the experience just isn't smooth or polished.
The f'd up thing? We basically have to rely on groups like CM (who I love!!!) to make our exerperiences closer to what we expect, I think we can all agree that once/if (PLEASE!) the CM crew starts building custom ROM's for us it'll be optimized and if it still runs like this, that's proof (in my eyes) that something is seriously wrong with this platform.
Fingers crossed we see some kind of update soon... Either official or non.
hctarks said:
... But even though the homescreen scrolling was perfectly "smooth," it was more the delay in response that bothered me. When I set my finger down and swiped from one screen to another, there was always a very short, split-second delay before the screen started moving, which felt as if my finger was "slipping" for a few millimeters before gripping the homescreen. ...
Click to expand...
Click to collapse
I think this is actually by design. This prevents screen movements when one touches the screen for whatever reason and moves slightly, but does not intend to slide the screen, preventing screen jitter. In testing, the slide amount is something less than a centimeter.
I'm trying to decide if I would turn it off or leave it on if it could be toggled.
I'm interested if alternate desktop app's would do this.
So, it is like the orientation delay that is apparently by design. I wish my phone had that, if flips a little to easily (vibrant).
I think IOS demonstrates pretty adequately that such a touch-response delay is not necessary. Same goes with, I think, orientation-switch delay. Re: the latter, when it's a problem on a device it seems like it's usually due to the threshold for the switch being set too low--not the responsiveness of the switch, which I think should happen immediately when the device is tilted a certain amount.
Related
I'm almost positive there was a previous thread about this issue, but I can't seem to find it. In any case, I've noticed that the touch sensor lags behind my finger considerably. I recorded a video with two tests consisting of a. A quick demo with the multitouch visualizer app, and b. A half-assed game of table tennis.
http://www.youtube.com/watch?v=5j7cYb7EtUM
This issue has also been noted by Android Central in one of their tests of the Evo's multi touch capabilities.
http://www.youtube.com/watch?v=ieuB0VvkmwA
As you can see, the video clearly demonstrates a problem with either the hardware or software. The HTC Incredible uses the exact same touch sensor, yet exhibits none of these issues. As a result, I'm kind of doubtful it's an issue with the hardware. I'm sorry, but for such a high-end smartphone, I would expect better from HTC. Here's to hoping they address this problem in a future software update.
yeah.. im kinda disappointed in EVO..
personally, it not that big of a deal. So it's another obstacle while playing air hockey, just something to make the game more exighting. If you really are disappointed in a beast of a phone as this for having some touch sensor lag.... go dig a hole and bury yourself in it.
Rennat said:
personally, it not that big of a deal. So it's another obstacle while playing air hockey, just something to make the game more exighting. If you really are disappointed in a beast of a phone as this for having some touch sensor lag.... go dig a hole and bury yourself in it.
Click to expand...
Click to collapse
That really is not a good excuse for this issue. I don't want air hockey to be more exciting or challenging. I want the paddle to track my finger as accurately as every other high-end smartphone on the market. I have every right to be disappointed, because this isn't 'some' touch sensor lag. In fact, it's quite severe. I paid good money for a good smartphone, and I, along with the rest of the Evo owners, deserve better than this. We shouldn't have to settle for 'not that big of a deal'.
The lag is not on pressing buttons I think, I think it's when you drag stuff.
I mean I tried on my Droid and it feels slow to respond on the emulators with touch controls, but the Evo is slow as well. Also when clicking stuff it feels instant.
jigglywiggly said:
The lag is not on pressing buttons I think, I think it's when you drag stuff.
I mean I tried on my Droid and it feels slow to respond on the emulators with touch controls, but the Evo is slow as well. Also when clicking stuff it feels instant.
Click to expand...
Click to collapse
Well no, there's no lag on pressing buttons. The touch sensor can easily handle a single tap, since it isn't necessarily tracking anything. When it comes to playing something like table tennis though, the problem becomes painfully obvious.
Mecha2142 said:
That really is not a good excuse for this issue. I don't want air hockey to be more exciting or challenging. I want the paddle to track my finger as accurately as every other high-end smartphone on the market. I have every right to be disappointed, because this isn't 'some' touch sensor lag. In fact, it's quite severe. I paid good money for a good smartphone, and I, along with the rest of the Evo owners, deserve better than this. We shouldn't have to settle for 'not that big of a deal'.
Click to expand...
Click to collapse
You're missing my point. I meant to say that is a little bug in the screen tracking going to influence your desission on whether you are cool with he phone or not? Ever phone will always have minor bugs that you just have to live with. Now tell me, can you name any of your last phone's 'little bugs'? I had a Palm Pre, and I loved it. I will say the build quality was crap and I had to return it 3 times but I still enjoyed the phone. The Evo by the looks of things doesn't have any problems with hardware but the memory card issue that got resolved within a few hours of release.
Rennat said:
I meant to say that is a little bug in the screen tracking going to influence your desission on whether you are cool with he phone or not? Ever phone will always have minor bugs that you just have to live with. Now tell me, can you name any of your last phone's 'little bugs'? I had a Palm Pre, and I loved it. I will say the build quality was crap and I had to return it 3 times but I still enjoyed the phone.
Click to expand...
Click to collapse
Yes, this little 'bug' is going to influence my decision because it shows utter negligence on behalf of HTC regarding their flagship device. A minor bug is the notification light going off every once in a while. A minor bug is not the main input method lagging behind by at least a second. This is a bug I'd rather not have to live with if HTC can fix it. What if all smartphones had this 'little bug'? I'm pretty sure nobody would just accept living with it.
When a G1 outperforms an Evo in terms of touch input tracking, there is a serious problem.
Agreed. I'd like to get this resolved. It isn't a deal breaker to me, but it is shocking that a device like this would have a significant issue with the touch sensor. I have a feeling that tracking can just be updated with a future software update, but if/when this occurs is anyone's guess.
This is definitely a software issue. From Chipworks:
Touch Screen controller
The Atmel device provides for up to 224 nodes (hence being called MXT224?) and a patented charge transfer technology that allows it to be used even in netbook screens (>10”). It features an SNR of 80:1, and an extremely fast refresh rate. All in all, the nearest competing off-the-shelf touch screen at the time of introduction has only half as many nodes, a screen refresh rate of only 83Hz (66% slower) and an SNR of only 25:1 (66% less). Another thing, it can recognize (first in the industry) not only touch but also stylus, fingernails and gloved hands. Because of the high SNR rate, the device consumes a smaller amount of power and a decreased response time (due to it not being required to make use of extra filtering circuitry).
Click to expand...
Click to collapse
zeuzinn said:
This is definitely a software issue. From Chipworks:
Click to expand...
Click to collapse
Right. Now that you mention it, this might have some correlation with the 30 frames per second cap on the Evo. I mean, most other phones run at 60fps, and they have no problem tracking touch input. What's possibly going on is that because the phone is limited to 30fps, the screen can't refresh nearly as fast as it has to in order to track the input...
Mecha2142 said:
Right. Now that you mention it, this might have some correlation with the 30 frames per second cap on the Evo. I mean, most other phones run at 60fps, and they have no problem tracking touch input. What's possibly going on is that because the phone is limited to 30fps, the screen can't refresh nearly as fast as it has to in order to track the input...
Click to expand...
Click to collapse
I was just thinking the same thing. Perhaps fixing the frame cap will resolve both issues.
Mecha2142 said:
Yes, this little 'bug' is going to influence my decision because it shows utter negligence on behalf of HTC regarding their flagship device. A minor bug is the notification light going off every once in a while. A minor bug is not the main input method lagging behind by at least a second. This is a bug I'd rather not have to live with if HTC can fix it. What if all smartphones had this 'little bug'? I'm pretty sure nobody would just accept living with it.
When a G1 outperforms an Evo in terms of touch input tracking, there is a serious problem.
Click to expand...
Click to collapse
As I said before.....
Rennat said:
You're missing my point. I meant to say that is a little bug in the screen tracking going to influence your desission on whether you are cool with he phone or not? Ever phone will always have minor bugs that you just have to live with. Now tell me, can you name any of your last phone's 'little bugs'? I had a Palm Pre, and I loved it. I will say the build quality was crap and I had to return it 3 times but I still enjoyed the phone. The Evo by the looks of things doesn't have any problems with hardware but the memory card issue that got resolved within a few hours of release.
Click to expand...
Click to collapse
and no I don't care if the screen lag is hardware issue or software. If your going to yell and grip about this then go away. We really don't need ranters link you in the forum. The xda forum is to help others and create new ways of doing things and having more features.
At this point, I really don't care what you think. As you can tell from the other posts in this thread, and in fact the entire Evo forum, people do care about things like touch input lag, frame limit caps, and bad wi-fi reception.
Have you seen the thread on the Evo's graphical cap? Most people there seem pretty pissed off about the issue and want something done. Should they go away because they're 'ranters'? No, they're right because the only way to get things fixed is to point the problems out in the first place.
Mecha2142 said:
Yes, this little 'bug' is going to influence my decision because it shows utter negligence on behalf of HTC regarding their flagship device. A minor bug is the notification light going off every once in a while. A minor bug is not the main input method lagging behind by at least a second. This is a bug I'd rather not have to live with if HTC can fix it. What if all smartphones had this 'little bug'? I'm pretty sure nobody would just accept living with it.
When a G1 outperforms an Evo in terms of touch input tracking, there is a serious problem.
Click to expand...
Click to collapse
This is not a bug. As of now, the android base will have a minor delay, especially when it comes to user interface because that is just the way java is. Which is why you will not notice it in dalvik prepped apps.
That being said I don't notice it at all after switching to the evo. I did notice it on my hero. There was always a solid delay between my finger and anything it does. On the evo I would say it is almost gone for me. But everyone always compares it to the iphone which is not java but I remember reading about the comparable delays between the two platforms and its there on the iphone <= 3gs but its just not as noticeable.
To each his own but I see way more advantages in waiting for Froyo/JIT on this platform, at least until apple opens up a bit, which will never happen.
EDIT: By the way, RUU the device because I can tell you right now of the two evo's I have played with neither had an input lag anywhere NEAR a second. If that is in fact true I believe the device or install has got something wrong with it. Or it could be a runaway app that has been installed.
flexgrip said:
This is not a bug. As of now, the android base will have a minor delay, especially when it comes to user interface because that is just the way java is. Which is why you will not notice it in dalvik prepped apps.
That being said I don't notice it at all after switching to the evo. I did notice it on my hero. There was always a solid delay between my finger and anything it does. On the evo I would say it is almost gone for me. But everyone always compares it to the iphone which is not java but I remember reading about the comparable delays between the two platforms and its there on the iphone <= 3gs but its just not as noticeable.
To each his own but I see way more advantages in waiting for Froyo/JIT on this platform, at least until apple opens up a bit, which will never happen.
EDIT: By the way, RUU the device because I can tell you right now of the two evo's I have played with neither had an input lag anywhere NEAR a second. If that is in fact true I believe the device or install has got something wrong with it. Or it could be a runaway app that has been installed.
Click to expand...
Click to collapse
Haha this guy doesn't know what he's talking about. Are you saying that my Motorola Droid, which DOESN'T have the input lag, is because it's not running java vm on Android? hahahaha Java VM has nothing to do with the lag on Evo's input.
Not really sure where I said that the moto droid is not based on java or anything of the sort. Pretty much ever developer knows that java ui performance is mostly crap.
For example eclipse and OOO. Perfect examples. They have purely unacceptable lag in their UI.
Nearly ALL user interfaces based on java have a laggy UI. As a developer I made a conscious choice to not use java based ui and go with gtk/clutter. I have played with several motorola droids and they all have a solid delay that in most circumstances does not exist on the iphone. It is a pretty common reason for folks to not use java to build their apps. Take a good look at the sandbox dalvik apps. Even under the android emulator they are much more responsive.
I DO NOT see the moto droid having less delay than my evo. I think you are mistaking frame rate for input lag. As icons are moving, they look "jittery" or skip around. That is a long shot from saying there is a 1 second delay between your finger and movement on the screen. I had an app crash the other day while downloading files to the SD card and the whole system slowed down and had this massive input delay. So all I was really saying was try and see if there is maybe something you have installed that has made this happen because everything seems pretty "instant" to me, coming from the hero. Obviously it could be that my opinion is relative to my hero. But I notice that the evo is a bit snappier than the incredible. And that is backed up by a few reviews.
flexgrip said:
Not really sure where I said that the moto droid is not based on java or anything of the sort. Pretty much ever developer knows that java ui performance is mostly crap.
For example eclipse and OOO. Perfect examples. They have purely unacceptable lag in their UI.
Nearly ALL user interfaces based on java have a laggy UI. As a developer I made a conscious choice to not use java based ui and go with gtk/clutter. I have played with several motorola droids and they all have a solid delay that in most circumstances does not exist on the iphone. It is a pretty common reason for folks to not use java to build their apps. Take a good look at the sandbox dalvik apps. Even under the android emulator they are much more responsive.
I DO NOT see the moto droid having less delay than my evo. I think you are mistaking frame rate for input lag. As icons are moving, they look "jittery" or skip around. That is a long shot from saying there is a 1 second delay between your finger and movement on the screen. I had an app crash the other day while downloading files to the SD card and the whole system slowed down and had this massive input delay. So all I was really saying was try and see if there is maybe something you have installed that has made this happen because everything seems pretty "instant" to me, coming from the hero. Obviously it could be that my opinion is relative to my hero. But I notice that the evo is a bit snappier than the incredible. And that is backed up by a few reviews.
Click to expand...
Click to collapse
Move your finger faster on the screen. Your finger will be going one direction while the interface is still going another direction. The delay is greater than the difference between 30 and 60FPS.
flexgrip said:
Not really sure where I said that the moto droid is not based on java or anything of the sort. Pretty much ever developer knows that java ui performance is mostly crap.
For example eclipse and OOO. Perfect examples. They have purely unacceptable lag in their UI.
Nearly ALL user interfaces based on java have a laggy UI. As a developer I made a conscious choice to not use java based ui and go with gtk/clutter. I have played with several motorola droids and they all have a solid delay that in most circumstances does not exist on the iphone. It is a pretty common reason for folks to not use java to build their apps. Take a good look at the sandbox dalvik apps. Even under the android emulator they are much more responsive.
I DO NOT see the moto droid having less delay than my evo. I think you are mistaking frame rate for input lag. As icons are moving, they look "jittery" or skip around. That is a long shot from saying there is a 1 second delay between your finger and movement on the screen. I had an app crash the other day while downloading files to the SD card and the whole system slowed down and had this massive input delay. So all I was really saying was try and see if there is maybe something you have installed that has made this happen because everything seems pretty "instant" to me, coming from the hero. Obviously it could be that my opinion is relative to my hero. But I notice that the evo is a bit snappier than the incredible. And that is backed up by a few reviews.
Click to expand...
Click to collapse
You drunk?
I have the Droid and the HTC EVO 4g.
Get the a touch input application
Scroll around with the Droid, instant.
Evo 4g super delay
This issue has nothing to do with Dalvik, or Java.
jigglywiggly said:
You drunk?
I have the Droid and the HTC EVO 4g.
Get the a touch input application
Scroll around with the Droid, instant.
Evo 4g super delay
This issue has nothing to do with Dalvik, or Java.
Click to expand...
Click to collapse
+1 its there and verified
One thing I have wondered is why Android is so much further behind in terms of the snappiness and speed of scrolling compared to the iPhone.
Yes, the jerkiness and much of the lag has been completely removed with updates to 2.2 and the newer high-speed processors. However, the difference is extremely apparent even with comparing my 2.2 cyanogen Nexus One to an iPod Touch 2G I happened to pick up today.
The iPod touch's scrolling actually follows your finger, if you rapidly scroll up and down (or left and right), the UI does not lag behind the position of your finger. But on my Nexus One (and even on my friend's Evo with the FPS update), scrolling rarely keeps up with your finger. I even was able to have the page oscillate to the wrong position of my finger by quickly scrolling back and forth.
To me, this is single-handedly one of the most important problems with the Android operating system. Speed is not just the processor, it's how the UI interacts with the user.
My question is - What can we do about it?
It's almost certainly a software issue, unless android phones are using sub-par touch screens, which seems hard to imagine. Is there any way to optimize the sending of touch information to apps?
Just figured I'd throw it out here, as I've yet to find any other posts with similar concerns.
It's because iOS is totally built to support the gpu AKA hardware acceleration. Android OS mainly runs on software, instead of full hardware acceleration. Which is why IOS is much more fluid. But Gingerbread 2.3 is said to have true hardware acceleration, and it's coming soon
Sent from my Vanilla Tazz using XDA App
My sentiments exactly. "Speed is not just the processor, it's how the UI interacts with the user."
Its a combination of poor touch sensor, having multitasking and not enough hardware acceleration.
The nexus/desire can barely multitouch so super smooth scrolling may be too much to ask.
Try scrolling in the new youtube app from google on one of the latest phones (sgs,g2,dhd) its super smooth. Everything will be like that come gingerbread
Sent from my GT-I9000 using XDA App
With an exception in the program list, my HTC Tattoo handles scrolling very well! I am running a Froyo ROM on it that is definitely whats making it fast, and I really look forward for gingerbreads new UI and that it doesn't require too much of the phone as froyo runs great on my tattoo.
It's definitely possible that it's the touchscreen. One thing I did notice however that must be almost certainly part of the software is that there's a "buffer range" when the finger first presses down that the finger must move out of before the scrolling action is started.
Presumably this is to keep from confusing wild presses with scrolls, but on the iPhone that buffer range is far smaller than on the Android platform.
Due to this buffer, the scrolling action only really starts a few hundred milliseconds after I actually touch the screen.
I may find a Verizon store and check out some of the newer phones, I'm curious if they'll work better, than my Nexus One.
Dunno but there are some app's where scroling is smooth whereas it isnt with others, so I dont thinks it's all up to the touchscreen of my desire, for example the launcher pro app drawer is extremely smooth compared to the htc one and so on
I checked out a Verizon store, and I still have to say that there's definitely something off about the smoothness. Anyone who disagrees hasn't tried an Android phone side-by-side to an iPhone.
It also doesn't seem to be something that GPU acceleration could fix:
Romain Guy said:
A one year old NexusOne (and other devices before) is perfectly capable of scrolling a list at close to 60fps (limited by the display’s refresh rate.)
Click to expand...
Click to collapse
So the problem is really either the screen refresh rate, or the slight hiccup when starting the scroll. Other than that, I really can't determine the differing factor, especially since I'm comparing Android to a iPod Touch 2g; nothing that would have significant processing power.
Kleptine said:
I checked out a Verizon store, and I still have to say that there's definitely something off about the smoothness. Anyone who disagrees hasn't tried an Android phone side-by-side to an iPhone.
It also doesn't seem to be something that GPU acceleration could fix:
So the problem is really either the screen refresh rate, or the slight hiccup when starting the scroll. Other than that, I really can't determine the differing factor, especially since I'm comparing Android to a iPod Touch 2g; nothing that would have significant processing power.
Click to expand...
Click to collapse
just use a different launcher. Launcher pro and zeam are incredibly smooth
bobdude5 said:
just use a different launcher. Launcher pro and zeam are incredibly smooth
Click to expand...
Click to collapse
I'm not even using the Launcher. Specifically I've been testing on Astro File Manager (which seems to be the smoothest android application with a long list to use) and the new Youtube app which supposedly has a few optimizations of some sort.
Doesn't the android OS lack gpu acceleration?? Thus Apple devices are smoother
Sent from my Incredible using XDA App
That's true, but look at the comments on this page from Romain Guy himself:
http://www.curious-creature.org/201...-and-tips-tricks/comment-page-1/#comment-4928
According to him, GPU acceleration isn't much of the problem.
http://www.engadget.com/2011/04/18/asus-eee-pad-transformer-uk-edition-review/
I'm surprised that they called out quite a few bugs in the software (and the unresponsiveness of the UI). I hope next few OTAs would fix the issues. But being Engadget, I think they have a slight bias.
I truely think there is no such thing as bug-free product. There will be bugs just as long as they aren't damaging to the point they can't be fix...ever. Lengthy review. Hopefully a review like this will not force Asus to delay release.
Its funny reading the comments at Engadget, a lot of negative feedback, towards the transformer and the review
I think the review was good, but it seemed he was nitpicking the littlest things
Particularly the lag issue with the web browser, which i didn't really notice in other review videos
And i am disappointed he didnt take the price into account for the score
I'm not sure about that review - A few things he is correct about and I'd like to see (like a notification light system) but other issues are clearly software related and sped will improve dramatically over the next month or so (I don't actually find it slow).
I have the Asus, the iPad 1 and the NI ADAM, and it is the ASUS I go to. For outdoor viewing I'd use the ADAM but all the other tablets are too reflective unless a matte screen protector is installed, so I don't know why he makes a fuss about it on the Asus.
Just read the review. Agree with most of what they say about it. The camera app isnt good, I get bad fps in videos too. Yes, it's a reflective screen, but then all tablets i've seen are the same. I disagree on the UI responsiveness though. Feels better than the ipad, and i've not had a problem launching apps or clicking on things. I can't comment on the keyboard dock obviously. Yeah it's not a perfect device but then there won't ever be one. There's meant to be a fota update out tomorrow so we'll see what it fixes.
8/10 from me for just the tablet part. Possible 9/10 if the keyboard dock is as they say.
Most if not all of the concerns in that review were regarding software issues.
The UI doesn't lag consistently, for example, the music and gallery apps are both silky smooth and responsive, but the browser struggles quite a bit and the home screen can't keep up if you add too many widgets.
The Asus on screen keyboard does also add a stupid amount of lag, and the camera software is embarrassingly bad.
The good news however is that most, if not all of this stuff should be fixed with a few updates.
flipao said:
Most if not all of the concerns in that review were regarding software issues.
The UI doesn't lag consistently, for example, the music and gallery apps are both silky smooth and responsive, but the browser struggles quite a bit and the home screen can't keep up if you add too many widgets.
The Asus on screen keyboard does also add a stupid amount of lag, and the camera software is embarrassingly bad.
The good news however is that most, if not all of this stuff should be fixed with a few updates.
Click to expand...
Click to collapse
Well then looks like I'll be waiting for a few updates before buying then . Keyboard and browser lag on a tablet is unacceptable imo
I did notice that the guy obviously doesn't know that much about Android. For example, the reason that you can't kill apps from the multitasking menu is that you don't need to - Android manages this itself.
Also, it seems like he was reviewing a pre-release model. Things like his comment on the lack of scrollpad multitouch were directly contradicting reports from those who have actually bought the device.
Sent from my HTC Desire using XDA Premium App
killermojo said:
Well then looks like I'll be waiting for a few updates before buying then . Keyboard and browser lag on a tablet is unacceptable imo
Click to expand...
Click to collapse
If I remember informations from users of Transformer that I read both issues are easy to avoid right now. Keyboard: use different one. Browser: use different one. Done.
It also bugs me in general when people refer to it as a "multitasking menu." It's not--it's a recent apps menu. It'll show an app in the list even if it's no longer actually running, and it's not meant to be a complete list of all running apps.
I clarified my position on engadget reviews two times in the comments below the review. Just look for my name
I can't stand their way of nagging on little things on the one device (as long as it runs Android) and turn a blind eye on it on other devices (as long as they run iOS). I'm not especially an Apple-hater, it's more the general way Engadget reviews without hard facts, their reviews are more a personal opinion instead of a professional review. I would be ok with that when they wouldn't give a rating that will influence potential customers.
wynand32 said:
It also bugs me in general when people refer to it as a "multitasking menu." It's not--it's a recent apps menu.
Click to expand...
Click to collapse
Sorry! Couldn't think what else to call it!
Sent from my HTC Desire using XDA Premium App
I don't know if i can call that Engadget "Review" a Review? So many things left out from it, Things i would of loved to see them show in the Review were.
1.Google Maps (GPS)
2.Polaris office
3.Flash in different websites other than that flash whore Engadget.
4.Asus own apps (DNLA etc)
5.The Keyboard SD slot shown working at the same time with the Micro?
I really hate that they always want to compare it to the Ipad 2 when clearly the apple device lacks gps, flash, and other things but gets praised by the media. the problem i find with that is that is that other websites do the same.
I for one dont care if the camera is buggy because its fixable with an update,i Rather have a working SD slot than a perfect camera its not like im gonna be taking pictures and videos with the tablet. Also when are people going to care that much about pinch to zoom being as "fast" as the ipad? for me as long as it works thats it i hardly use it, i always double tap to zoom in.
Im no expert but i expect the Iphone 4/ Ipad 2 to have fast scrolling left and right i mean it doesnt need to use any real horsepower to draw on screen to those cutesy little blocks on their homescreen called apps when in Honeycomb3.0 you have lots of things happening everything from widgets, notifications, the transitions 3D esque i mean those little things should not really affect the user experience i for one can't wait for this tablet in the us.
It's Engadget, what did you expect?
They have a CLEAR bias towards Apple products. I love how they mention (amongst other things) "the proprietary connector" as being bad. And Apple uses a standard micro USB port on their devices? Right...and they don't say anything when they review these products.
Of the issues they found:
camera lag - yep it's there.
reflective screen - yes, but not as bad as they claim (I use it outside and don't have issues unless I aim the screen to deliberately reflect the sun).
browser lag - not for me. If I scroll as fast as I can on engadget I can get it to stutter a tiny bit, but not as bad as in their video.
Browser zoom issues - no issues for me on most websites - engadget is the buggiest one but that site is so poorly written it can lock my firefox up if left open for a while. As for the incorrect rendering of pages I've not seen it on any site...
Laggy keyboard - yeah the asus one is a little laggy. Switching to the honeycomb stock one instantly fixes that problem though.
Input lag - I laughed at this - it is not lag, but an elasticity effect on moving icons and the unlock button. Basically a deliberate UI effect
Unresponsive touches - I don't get this. Maybe they're holding it wrong
The review failed to look at the quality of the speakers in the transformer, probably as they're pretty good srs surround speakers and the ipad only has a mono speaker which isn't very good, so I won't expect them to cover the speaker quality until the ipad gets better speakers. They also didn't review video chat (again, because a 1.2MP camera would destroy the ipad 2's vga), nor did they look at productivity apps like polaris.
anyone here with the keyboard dock can confirm the problems with the usb and sd slot not working and need to be reboot. also their problem with the tablet not sensing its disconnected with the dock and not allowing the tablet keyboard to load?
also anyone know how much memory can the keyboard dock hold? can you plug in two usb sticks and a sd card at the same time?
I'm glad they mentioned the things they did, hopefully Google/Asus will take note and get them sorted.
Has anyone got the keyboard dock yet, appart from journos? Don't think I've heard of any...
I also like how he states that the touchpad doesn't have multi-touch....when it does.
Horrible review.
Nickedynick said:
I did notice that the guy obviously doesn't know that much about Android. For example, the reason that you can't kill apps from the multitasking menu is that you don't need to - Android manages this itself.
Click to expand...
Click to collapse
I know they say that, but I don't buy it on the phones - I find I do need to kill apps.
And the reason for some stutter and lag is exactly because the system tries to do something fails and then gets rid of an app in memory and tries again.
review from homeland of transformer, also done by engadget, chinese engagdet
they have a lot more information on the asus and acer tablets
http://translate.google.com/transla...ansformer-detail/&sl=zh-CN&tl=en&hl=&ie=UTF-8
Q & A about the tablet
http://translate.google.com/transla...gadget.com/2011/04/09/25-asus-transformer-qa/
Ok guys, here it is. My first-impressions with the 32GB Asus Transformer after about 24 hours of use. I would like to mention that the opinions below are formulated by someone who owns and uses the first generation iPad (I hate most things Apple) since it was released as well as a Nook Color for about two months.
PROS:
1. Browser (especially bookmark sync with Chrome): After using this for about 5 minutes I knew I was never going to be able to do without this feature. As someone who has their bookmarks extremely well organized in folders and such, syncing is a must. I didn't even bother migrating my bookmarks to my iPad as I knew it would take days to do, so I just learned to do without. However, this feature alone, makes this tablet more like a laptop/desktop replacement than the iPad could ever be. The speed is also very nice. However, I must say that the scrolling and pinching doesn't compare to that of the iPad.
2. Ability to change keyboard (SwiftKey): I must say that the Asus keyboard is pretty horrible. I don't know if it's the slight delay depending on the software that's running, the spacing, aesthetics of the keys, or simply the fact that you have to go to a submenu to access keys such as the "?" or "!" (c'mon, those are pretty commonly used keys). But after using SwiftKey BETA, I must say that the difference has been night and day. I hate having to rest these tablets somewhere or rely on using one hand to access all the keys when in horizontal mode. Fortunately, with SwiftKey, I don't have to worry about that and can keep my hands where they should be, on the bezel. Now if only the TF could automatically change keyboards when docked. SwiftKey can get kind of annoying when using the keyboard to type with its corrections. I think Tasker can handle this though, I'll let you know.
3. Dock: Wow! I was really skeptical as to how practical and efficient the dock would be. To my surprise, I was really impressed with how much it makes the Tranformer feel like a netbook (albeit a bit heavier than most netbooks). Not just a netbook, but an Apple netbook at that. I'm an avid Microsoft/Google fan, but one really must recognize and admire how fluid navigating on an Apple laptop is. The swiping of the finger on the trackpad to scroll up/down, left/right, makes it feel really Apple-esque. Props to Asus! By the way, haven't had any disconnecting dock issues so far. Keeping my fingers crossed!
4. Screen resolution: This thing sure is crisp. Aside from the negative issues I have with the screen (light bleeds; see below), I must admit that in the color/sharpness department, this thing is as crisp as my iPad and Nook Color are. I still would probably give the edge to the Nook Color, but I think it's a small screen/pixel density situation then.
CONS:
QUALITY CONTROL ISSUES:
1. Light Bleed: I posted my issues with it here. As I mentioned on that thread, it isn't too noticeable (only on full brightness or in a really dark setting). But the fact of the matter is that the screen is what you're staring at 100% of the time with such a device; and just knowing that you do have light bleeds keeps you subconsciously hunting for them. Really is a shame that this is an issue. I'm leaning towards getting it exchanged as soon as I feel that newer ones have these issues addressed (not holding my breath). Until then, I guess I'll have to get used to it. The question is, will I?
2. Very small creakiness on left/right edges (pushing inwards): Not much of a problem, but it is worth mentioning. Not that it is very noticeable; it's just that such creaking makes the overall quality and feel of the product seem a bit on the cheap side. I guess I was spoiled by my iPad, but I really don't worry about that thing falling down. This thing seems a bit more sensitive for me. Perhaps I'll get used to it with time?!
OTHER HARDWARE ISSUES:
1. Weight: I don't know of it's just my mind playing tricks on me or what, but the TF seems much heavier than my iPad (first gen). Perhaps it is the difference in dimensions which might require some time getting used to. I don't know what it is, but I definetely can't hold this thing comfortably nearly as long as I can the iPad.
2. Video Playback (including HQ YouTube): People are claiming that this is a limitation of the Tegra 2 processor. If that's the case, than why in the hell would they even bother with it? I mean, I don't expect this thing to run and yield the same quality that my 42" Panasonic VIERA plasma TV does, but this is a tablet. At least 1/3 of everything people do with tablet is watch movies. Especially YouTube movies. This thing should handle it as fine as the first generation iPad does (you know, the one that came out over a year ago). C'mon now! Anyways, my HQ YouTube videos sporadically jerks around and HD videos, well, you've probably seen tons of complaints about it. Tsk, tsk!
3. Smoothness/Speed: I must say that I was somewhat let down with the performance right out-of-the-box. Once again, it must be spoiled by the iPad here. I just feel that either Honeycomb is trying to pack too many animations, graphics, etc. or the processor is just lacking. Whatever the case, I am hoping that someone roots this thing fast and removes some of the resource hogs out of here (apparently there are a lot of unnecessary programs running on the background). Don't get me wrong, this thing isn't dragging ass or anything. It just isn't as speedy as I expected it to be out-of-the-box. I guess I'm more concerned about when I have my 100+ apps installed on this thing. If it's like this now, how will it be then? My EVO 4G seems a lot more fluid when navigating than this thing does, especially when it has a fresh install on it.
4. Smudgeness: I've seen some people complain about this here and there but I thought they just weren't used to using anything touchscreen and were probably exagerating. I was wrong. This thing really does attract a lot more smudging than the iPad, Nook Color, or my Evo. Not that big a deal, but a minor nuissance indeed.
SOFTWARE ISSUES:
1. App Availability/Reliability: So far I haven't come across many apps that don't work well with Honeycomb, but the ones that I do have issues with really bother me. Words with Friends need to step their game up and fix some of the performance and density issues the game is plagued with. Also, out of the apps that are available for Honeycomb and the iPad, the iPad version not only runs so much smoother, but usually contain a lot more features as well. Take Taptu for example. It looks and feels completely different and a lot more robust on the iPad. What a shame! (BTW, I know this is not a TF issue, but a HC issue. Relax!)
2. Auto-brightness: I mentioned this before in this thread. It really does seem that the auto-brightness is a bit too dim. Maybe it is just a dimmer screen than the iPad or Nook Color. But even still, it could use auto-brightness to compensate for that when not in max-brightness mode. Right?
3. Camera: I wasn't expecting wonders from the camera, but I was expecting a lot better movement experience when video recording. I hope that this is something that can be addressed with a software update (maybe tweaking the processing of the captured image/video). On a good note, the front-facing camera worked pretty decently.
I understand that getting a "perfect" device is, in most cases, unrealistic. But, as much as I despise almost everything Apple, I haven't had any cosmetic issues with any of the iPads/iPods I've owned or used. So I know it is possible to be a lot better.
I know, well, hope, that the future is much brighter for the Transformer. Asus seem to be very involved in improving our experience, which is a good sign. Let's just hope they can tackle the camera and video performance as soon as possible.
I know it seems that I have a lot more complaints than praises here. Don't get me wrong, there are issues. But the positive far outweighs them. At least enough for me to keep it. I highly recommend it to anyone wanting a tablet that will encompass a bit more than just surfing the net and watching YouTube videos. This thing really can replace your netbook.
SCORE: 7/10 (9/10 if they fix the software issues)
Reserved for updates, answers to questions, etc.
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.