Related
Guys,
Never ever wanted to even bother about iPhone due to the fact that WinMo devices have almost endless custom apps available and tweaks etc.
That said...I played/fiddled with a mates iPod touch today and the speed at which animation took place and the scrolling of files was immensely smooth.
Anyone recommend any tweaks to help make the Touch HD run this smooth?
Wiggz said:
Guys,
Never ever wanted to even bother about iPhone due to the fact that WinMo devices have almost endless custom apps available and tweaks etc.
That said...I played/fiddled with a mates iPod touch today and the speed at which animation took place and the scrolling of files was immensely smooth.
Anyone recommend any tweaks to help make the Touch HD run this smooth?
Click to expand...
Click to collapse
Buy an iphone 3GS!
Come on...seriously. Can the HD not perform to that level then?
You could try flashing a new ROM??
There's a huge difference between "smoothness" and "speed"!
While the iPhone's UI is VERY smooth, it's actually slower than the Touch HD (for the iPhone 3G, the 3GS is now a bit faster due to the Cortex A8 processor architecture).
The level of smoothness depends on the software. While Windows Mobile was designed for slow hardware and therefore is pretty fast on newer devices, it was not designed for finger use and therefore doesn't feature that smooth kinetic scrolling and nice animations.
Sorry, but you can't have an interface that's as "nice looking" as the iPhone's for now, though I think TouchFlo is already pretty good and leaves little to be desired.
Also, try out Miri's or Dutty's WM6.5 ROM and you'll at least get that smooth kinetic scrolling and bigger, nicer looking list items.
The iPhone's interface may look nice and smooth, but it's actually less practical for "professional" use because you don't have multitasking, you only get a bunch of icons, you've got to go back to the homescreen every time you want to switch between applications and there's no good solution for notifications (like the top bar on WM).
I agree - I'm not disputing that Touch HD is a better unit for professionals...and indeed myself...I'm just trying to get the smoothness to rival it.
Have you tried WM6.5? Microsoft has added kinetic scrolling to it.
No, I'm trying to stay with stock ROM
Then you must replace the default WM applications with "smoother" ones. I've made a package with finger friendly applications a while ago:
http://forum.xda-developers.com/showthread.php?t=473116&highlight=finger+friendly
You can use applications like ThumbCal, Kinoma Play, iContact etc. and make them the default ones via the registry.
The package is a bit outdated and I don't use it anymore because with WM6.5 and the newest TouchFlo it's not necessary.
Wiggz,
I spend the last hour doing my homework and I've found some useful tweaks that speeds up the interface a little bit.
First and foremost, read through this thread.
Having said that, I suggest you use some form of registry explorer and look for the following things.
FontCache / Glyphcache - Located at
HKLM\SYSTEM\GDI\GLYPHCACHE\
The limit should be 8192, if not, record that number and keep it somewhere so that if it doesn't turn out to be stable for you, you can revert it. Change this limit to 65536.
File System Cache - Located at
HKLM\System\StorageManager\FATFS\CacheSize
The limit should be 0 by default. Change this value to 8192. Also, in the same section, you'll see something called EnableCache. The value of that should be 1, if it's 0, change it to 1 to enable file system cache.
File System Filter Cache - Located at
HKLM\System\StorageManager\Filters\fsreplxfilt\ReplStoreCacheSize
The limit should be 0 by default as well. Change this value to 131072.
After doing these settings, do a soft reset and see what happens? Noticeable differences should be seen in Opera. If you find that you get instability as a result of these cache differences, simply reduce the numbers by dividing them by 2 (e.g., 65536 > 32768).
I hope this helps you get that iPhone fluidity that you're looking for.
Cheers.
Credits goes to this thread by vincent1 and this thread by hyphen.
if you like iphone interface ... buy an iphone for dummies ....
HD is better faster and superior ....
if you want more speed and iphone interface install Vito winterface or better mobile shell 3 the iphone UI killer
You can also buy a Samsung Omnia 2: http://wmpoweruser.com/?p=5734
Looks pretty smooth, hm?
You can also buy a Samsung Omnia 2: http://wmpoweruser.com/?p=5734
Looks pretty smooth, hm?
The iPhone is indeed smoother and more fluid. There is no tweak, custom Rom or other today plugin that can give you the same experience and still deliver the ease, clean looks and functionality in one package. Believe me, I've tried them all and thus got an iPhone
In theory the HD might be faster, but in practice it isn't. WinMo is fundamentaly flawed in many ways. Graphicly 6.5 is a joke, that's why every manufacturer (samsung, HTC...) are trying so hard to cover it up. And let's not forget iPhone's 3D capabilities!
The HD had potential, but HTC and microsoft failed (again) IMO.
The amount of apps shouldn't be the reason to buy the HD. Many apps don't support WVGA and the iPhone's appstore has thousands of programs and is growing fast. Some free, some not. It's nice to see a lot of iPhone apps are far more 'creative' and utilize multitouch.
While the iPhone interface seems smoother at first glance, it is actually slower because there's no multitasking and you have to close the application you're in and go back to the home screen in order to launch another application. This slows down the workflow dramatically.
When I got the iPhone 3G, at first I also was stunned by how smooth the UI was, but after some weeks of using it, I realized that the UI was actually pretty ineffective because you can only have that bunch of icons, no information on the homescreen, no multitasking and there's no good solution for notifications.
While the WM interface looks a bit "old", it's actually more effective/productive in my opinion.
You should really try out Miri's or Dutty's latest WM6.5 ROMs, the new Manila is a lot better and the kinetic scrolling makes for a huge difference imo.
I agree that with the shipped ROM or with a badly configured ROM the Touch HD seems a little "stucky" and not that smooth or fast as an iPhone (and especially the 3GS). But have you tried some good cooked ROMs? Especially the new WM 6.5 releases are VERY fast and smooth.
Almost all my collegues own an iPhone (3G). In the beginning they laughed at me (they're all Apple addicts, I am the only PC user). But with every new ROM I flashed I astonished them more and more. Now two of them even sold their iPhones
maati,
You kept saying that iPhone 3G is slower and 3GS is only slightly faster. I find this not to be the case at all. My cousins has both 3G and 3GS and we sat down few days ago and did a side by side comparison surfing some websites. We're on the same network. Both 3G and 3GS beats my HD by miles in speed. 3G still beats mine but by not much but for 3GS the difference is very noticeable.
I'm still using stock ROM, but I'm not sure if ROM makes any difference to Opera mobile's speed.
The thing is, iPhone is fast out of the box, no tweaking is needed. Whereas I'm struggling still with the randomly non-reponding screen. I still find myself having to press very hard to activate actions on my HD. Sometimes nothing happens after 5 or 6 presses, then suddenly a rapid strings of reactions comes, and it overshot what I actually wanted to do. I had the same problem with my HTC advantage with its cook ROMs. Everytime I flash a new ROM, the desktop UI is fast (though it seldom have any influence on the underlying applications) for a while but it usually quickly deteriorate once more tweaking and softwares are loaded.
Not only that, when she showed me her applications and walk though with me some of the 65,000 applications in the apple store, I was just dumbfounded. I had always ridiculed her for not using what I had always believe to be the most superior phone, which to me was window mobile phones.
So to tell the truth, I'm lately extremely tempted to jump ship myself.
I was not talking about surfing the internet. This depends on where you are and which network you are on (e.g. where I live, the Touch HD is faster than the 3G, especially on fast HSDPA networks).
I was talking about stuff like opening applications, everyday tasks. The HD does them faster than the 3G, especially when you leave the applications running in the background. And even with lots of applications running in the background, the HD's battery life is significantly better.
Maybe it's because I know how to use it (e.g. don't press more than once on a button just because it doesn't react immediately) but I've got no problem with the responsiveness of the HD. I even think it's a bit better than on the iPhone where some applications are also pretty slugish (though the resistive screen needs more force). And my iPhone crashed at least as often as my Touch HD (I think about once in 2-3 weeks with no soft reset).
(btw. I'm talking only about the iPhone 3G which I used together with the Touch HD for some weeks. I only tried the 3GS once.)
IMO...
speed = yes
smoothness and fluidy = no
(there is a difference but WinMo is just not designed to be smooth overall like the iPhone)
Wiggz said:
Guys,
Never ever wanted to even bother about iPhone due to the fact that WinMo devices have almost endless custom apps available and tweaks etc.
That said...I played/fiddled with a mates iPod touch today and the speed at which animation took place and the scrolling of files was immensely smooth.
Anyone recommend any tweaks to help make the Touch HD run this smooth?
Click to expand...
Click to collapse
hi Wiggz,
if u want a UI which has speed on WM6.1 then i recommend Point UI. it is finger friendly and the kinetic scrolling speed is great. with customizing it; there are a large no. of applets which r all free from the community page on their website
try it out...ive been using it for a while now and ill never go back to touch flo 3D. If u buy PointUI pro or find a cracked one somewhere then this increases the detachment from WM UI as u have a full contact card and no longer need 2 use Wm's ugly one. if u choose to download either version a great Applet mod is the Messaging Mod which lets u read ur SMS with out going to the WM app.
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.
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.
I stopped by the TMO store near work today and checked out the sensation. I spent a good 10minutes with it (no one else was at the store)
Despite being thicker, it felt thinner in hand. I actually do like the overall design and feel better than the boxy feeling of Galaxy S II. That being said, if i hear another HTC fanboi whine about the Galaxy S II being too plasticy(lol), I will snap the plastic pieces from the back cover of the sensation and shove them in their mouth. Outside of the little center piece, construction material is very similar
Now to the device performance. It was sad to see the device run so slowly with the sense overlay. Maybe i spent too much time with the GS II but it's very noticeable. I even asked the store rep when the device was rebooted and she said earlier today I don't think i rebooted my GSII since the reflash to KE2 from KE7. When i handed her my phone to the rep while i played with the sensation, she said the samething about the quickness of the device.
I enjoyed the sense in the old days of winmo but now it just seems overly complicated. On my captivate, i ran the stock android launcher over TW3 and TW4 was pretty refreshing until i ran into a few limitations and swapped it out with LP.
There are many more things needing comparison but that would happen soon when i recommend the sensation for my co-worker who's using TMO.
Edit: Screen was pretty decent. It wasn't as bad as some of the review said it was but it wasn't great either. Also the web browser and TMO service ran pretty smoothly but it did choke slightly during the scroll while browsing engadget
I played with it myself. The look and feel gives an impression of higher quality than the plasticy sgs2. Yes, I did have to say it because its true. Saying otherwise would be a lie. It should be pretty obvious where I spent my money and I did so because I believed this was a better device all in. That is how I spend my money, I don't give a rats ass who makes my phone I just want the best possible device money can buy. That doesn't mean I don't call a spade a spade though and the sensation gives off the impression of better build quality. Speaking the truth does not make someone a fanboy and I have yet to see the perfect device.
I also found that it felt less fluid in the gui. There was another guy there who was scoping the phone too and we both compared it to mine. Both of us felt that it was smoother pretty much everywhere but particularly in the browser where the difference is not small.
We both felt the screens were a push overall but this related partly to size. The screens gave about the same impression of available real estate but the thinner width of the sensation allowed by the screen gave it a better feel in hand. IMO this may be the way to go in size and shape down the road.
On sense we disagreed, he loves it and loved it on the sensation. I find it overbearing and the latest iteration on the sensation did nothing to change that.
You miss a lot fiddling around with a phone for 5 minutes in a store but I felt like I had made a good choice with sgs2 over this one which had also been on my short list. An interesting point. That fellow that was scoping the sensation with me, I believe he had been sold on it before he got there. Having played with mine and the demo though he did not buy. He did inquire about where one buys an sgs2 though and left empty handed with a thoughtful look on his face. lol
ph00ny said:
Now to the device performance. It was sad to see the device run so slowly with the sense overlay.
Click to expand...
Click to collapse
Sense doesn't slowdown a device, what you call sense is rosie and it's just a launcher, sense actually is a whole user experience with improved email, message, gallery, keyboard, widgets, locations, likes, etc etc etc but this doesn't slow the device down if certainly if you do not use them. I do know that especially in the app drawer sense can feel less fluid but this actually is a feature, since sense 2.1, and after a while you become used to used and come to appreciate it because it allows you to scroll many rows at a time but still have an overview. Switching home screens and using the carousel was superfluid on the device I tested as was starting up apps.
I also played with it for a view moments in a store unfortunately their was no free wifi, so I couldnt really test the browsing but I did notice I could zoom out much more on the sensation whilst the text remained legible
godutch said:
Sense doesn't slowdown a device, what you call sense is rosie and it's just a launcher, sense actually is a whole user experience with improved email, message, gallery, keyboard, widgets, locations, likes, etc etc etc but this doesn't slow the device down if certainly if you do not use them. I do know that especially in the app drawer sense can feel less fluid but this actually is a feature, since sense 2.1, and after a while you become used to used and come to appreciate it because it allows you to scroll many rows at a time but still have an overview. Switching home screens and using the carousel was superfluid on the device I tested as was starting up apps.
I also played with it for a view moments in a store unfortunately their was no free wifi, so I couldnt really test the browsing but I did notice I could zoom out much more on the sensation whilst the text remained legible
Click to expand...
Click to collapse
Maybe the one that i was playing with needed a reboot? It was pretty sluggish in everything. Scrolling through the app drawer, scrolling between home screens, etc.
Like I said the slow scrolling through apps in the app drawer is a feature, it scrolls one entire screen and then stops, so you can look at the icons and decide to scroll further, in previous sense versions the scrolling through the app drawer was very fast but it was also easy to scroll way past the app you wanted, I prefer it this was, though it appears at first less smooth
giving the carousel a spin was super smooth on the sensation I tested but rosie has always been supersmooth for my too on my desire (and I say this as someone who has reported dozens of bugreports for unsmooth scrolling and various other animations to eg. opera, xorg, various graphic drivers, qt, kwin, and kernels in several linux distros!)
godutch said:
Like I said the slow scrolling through apps in the app drawer is a feature, it scrolls one entire screen and then stops, so you can look at the icons and decide to scroll further, in previous sense versions the scrolling through the app drawer was very fast but it was also easy to scroll way past the app you wanted, I prefer it this was, though it appears at first less smooth
giving the carousel a spin was super smooth on the sensation I tested but rosie has always been supersmooth for my too on my desire (and I say this as someone who has reported dozens of bugreports for unsmooth scrolling and various other animations to eg. opera, xorg, various graphic drivers, qt, kwin, and kernels in several linux distros!)
Click to expand...
Click to collapse
There is a difference between slow scrolling and rough scrolling. That's what i was experiencing throughout the interface. Like i said before, maybe it needs a reboot or maybe i've gotten used to the SGS II.
Overall the Atrix is pretty good, especially recently with overclocking and Cyanogenmod.
CPU and 3D graphics are superb, the phone is generally snappy and loads web pages very quickly over a fast wi-fi network.
However, what was Nvidia thinking when it comes to 2D graphics. Text and image scrolling is 'horrible'. I know, its not THAT bad, but it is seriously annoying when you have a device this powerful and the whole operating system and browser scrolling looks like it is taking place at like 10-20 FPS.
When comparing my year old Samsung Fascinate, to the Atrix, it is a no contest. Scrolling is WAY smoother on the Fascinate.
It just seems like a phone as powerful as the Atrix would be able to pump out 60 FPS scrolling thoughout the OS and the browser.
I am really looking forward to the possibility of an OMAP 4470 (PowerVR SGX544) powered phone!!!!!!!!! Or maybe Nvidia will get it right with Kal El.
Does anyone else share my frustration, or is this just me nitpicking?
Pretty sure it's because hardware acceleration isn't enabled on web browsing.
But I use dolphin hd. It's smooth as butter.
My 2d seems to be fine.
plvaulter06 said:
Overall the Atrix is pretty good, especially recently with overclocking and Cyanogenmod.
CPU and 3D graphics are superb, the phone is generally snappy and loads web pages very quickly over a fast wi-fi network.
However, what was Nvidia thinking when it comes to 2D graphics. Text and image scrolling is 'horrible'. I know, its not THAT bad, but it is seriously annoying when you have a device this powerful and the whole operating system and browser scrolling looks like it is taking place at like 10-20 FPS.
When comparing my year old Samsung Fascinate, to the Atrix, it is a no contest. Scrolling is WAY smoother on the Fascinate.
It just seems like a phone as powerful as the Atrix would be able to pump out 60 FPS scrolling thoughout the OS and the browser.
I am really looking forward to the possibility of an OMAP 4470 (PowerVR SGX544) powered phone!!!!!!!!! Or maybe Nvidia will get it right with Kal El.
Does anyone else share my frustration, or is this just me nitpicking?
Click to expand...
Click to collapse
Penis
10chode
Like you said it is not right for atrix not to have fluid scrolling unlike older phones but still we know what it is capable of despite the lack of fluid scrolling. Dolphin HD is better than stock browser for fluidity, give it a try !
Semseddin said:
Like you said it is not right for atrix not to have fluid scrolling unlike older phones but still we know what it is capable of despite the lack of fluid scrolling. Dolphin HD is better than stock browser for fluidity, give it a try !
Click to expand...
Click to collapse
And Opera is even faster. Its GPU accelerated (at least partially) and runs rings around stock and dolphin on an atrix.
All sammy phones the stock browser for example has HW acceleration, same as Apple. On my galaxy Tab, the stock browser is ipad smooth/fast.