Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (3)
to SailfishOS by edp17 - 4 hrs, 30 mins ago -
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 8 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 1 day, 21 hrs ago -
n770 youtube video (0)
to General by nmdv - 5 days, 20 hrs ago - more...
 |
|
2010-02-26
, 21:34
|
|
Posts: 4,708 |
Thanked: 4,649 times |
Joined on Oct 2007
@ Bulgaria
|
#42
|
Originally Posted by ysss
Okay, 2.5x and shake hands?
Not quite
320 * 480 = 153 600
vs
800 * 480 = 384 000
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
| The Following User Says Thank You to Bundyo For This Useful Post: | ||
|
|
2010-02-26
, 22:01
|
|
Posts: 59 |
Thanked: 17 times |
Joined on Dec 2009
@ Ireland
|
#43
|
Originally Posted by captainqtp
Sorry, but I read the whole thread... am I the only one who thinks the Maemo 5 OS *IS* very fluid and has no problem with it? It seems to me that the title of this thread begs the question...
Yep me! i'm more than happy with how slick the UI is. class.
|
|
2010-02-26
, 22:16
|
|
Posts: 174 |
Thanked: 69 times |
Joined on Jun 2009
|
#44
|
just improve the scrolling, thats the only thing thats choppy and visible.
I am sure being 'fluid' should not be an issue, given the 1st iteration of the iphone with an even weaker processor managed it.
I am sure being 'fluid' should not be an issue, given the 1st iteration of the iphone with an even weaker processor managed it.
|
|
2010-02-26
, 22:28
|
|
Posts: 1,179 |
Thanked: 770 times |
Joined on Nov 2009
|
#45
|
Originally Posted by zfarooq
Scrolling is woeful. At least on mine, When scrolling through a long picture folder or music list I almost have to turn away due to how jerky it is. And the switching between desktops should be so much better. Also takes a while to load so many things unlike on the iphone where you tap and it just opens up what you tapped immediately. Someone mentioned that the rotation distracts from the fact that it is loading up but if the N900 had the same feature it would often have to rotate a 100 times just (slight exaggeration ofcourse) just to open up what you have selected, or freeze up for five seconds in the middle of the rotating screen.
just improve the scrolling, thats the only thing thats choppy and visible.
I am sure being 'fluid' should not be an issue, given the 1st iteration of the iphone with an even weaker processor managed it.
 |
|
2010-02-26
, 22:33
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#46
|
iirc, the iphone on loading a app first shows a static image of the app interface, and then overlays the ui elements on top.
btw, it would not surprise me if anything but phone and music playback on the iphone have low priority set. So when a app loads its a case of "drop everything, app loading!".
btw, it would not surprise me if anything but phone and music playback on the iphone have low priority set. So when a app loads its a case of "drop everything, app loading!".
| The Following User Says Thank You to tso For This Useful Post: | ||
 |
|
2010-02-26
, 22:36
|
|
Posts: 1,091 |
Thanked: 323 times |
Joined on Feb 2010
@ ~
|
#47
|
Originally Posted by tso
Me neither. Whereas the N900 is running many processes/daemons/apps at once. Wonder how many processes that runs on a stock iPhone(and the CPU usage).
btw, it would not surprise me if anything but phone and music playback on the iphone have low priority set. So when a app loads its a case of "drop everything, app loading!".
----------------
Now playing: Tool - H.
Last edited by ToJa92; 2010-02-26 at 22:53.
|
|
2010-02-26
, 22:46
|
|
Posts: 20 |
Thanked: 14 times |
Joined on Feb 2010
|
#48
|
Originally Posted by jakiman
I don't think the problem is related to a particular toolkit.
Chip spec wise yes. But 3GS has the SGX535 gpu heavily underclocked as far as I know. To a quarter of its actual frequency. Where as N900's SGX530 is clocked at full speed. So technically N900's GPU is faster than iPhone 3GS.
Fluidity has nothing to do with HW. Maemo 5 is the issue. If Maemo 5 had QT4.6 and if the gui was based on that also, it would be far smoother. Try the QT4.6 demos to see for yourself. I expect Meego to be very fuild.
Clutter can also achieve super smooth animation if it's used correctly.
The issue is just that supporting several toolkit layers introduces overheads.
I remember a topic explaining that Vsync was actually turned off because activating it would imply an even slower frame rate... All that because of the several synchronizations needed between all API layers involved in the graphic rendering.
| The Following User Says Thank You to Spyker For This Useful Post: | ||
 |
|
2010-02-26
, 23:00
|
|
Posts: 861 |
Thanked: 734 times |
Joined on Jan 2008
@ Nomadic
|
#49
|
Clarifications to this thread's semantics are needed:
The OP starts with the term "fluid," which indicates not UI speed in transition but UI smoothness in transition.
Wouldn't it mean that using any raw numbers outside those which determine visual viscosity are pretty much missing the point of the post? That is, looking at the speed of the GPU, number of pixels, etc. are all pieces to be understood, but not where the answer for the post's question is to be found.
The answer would have to lie in something that measures (?) this statement:
The iPhone user interface utilizes screen transitions between input/reading screens at X rate because it was determined that X rate was the longest amount of time that could be allowed for applications to unload themselves from the main viewport and use of primary system resources. These numbers were seen to have given the best responses from users during testing which looked at transitions, gradients, and other elements which, when added together, conveyed a positive viscosity metric.
In light of this, the Maemo 5 user interface uses screen transitions at Y rate because it was determined that this rate is more suitable for system performance relating to the user intent of a heightened multi-tasking experience. This time (Y) is suffient to display ABC transitions similar to the iPhone, but because X does not equal Y, the rate of fluidity (visual viscosity) for Maemo will give this alternate user experience that emphasizes multitasking, but the cost is the difference of Y-X in smoothness to the end-user.
Am I wrong for looking at what the OP asked? Or, do we have the numbers according to this statement to investigate and answer this question as close to correctly as possible?
Last edited by ARJWright; 2010-02-26 at 23:10. Reason: clarifiation to the first part of the statement; grammar
The OP starts with the term "fluid," which indicates not UI speed in transition but UI smoothness in transition.
Wouldn't it mean that using any raw numbers outside those which determine visual viscosity are pretty much missing the point of the post? That is, looking at the speed of the GPU, number of pixels, etc. are all pieces to be understood, but not where the answer for the post's question is to be found.
The answer would have to lie in something that measures (?) this statement:
The iPhone user interface utilizes screen transitions between input/reading screens at X rate because it was determined that X rate was the longest amount of time that could be allowed for applications to unload themselves from the main viewport and use of primary system resources. These numbers were seen to have given the best responses from users during testing which looked at transitions, gradients, and other elements which, when added together, conveyed a positive viscosity metric.
In light of this, the Maemo 5 user interface uses screen transitions at Y rate because it was determined that this rate is more suitable for system performance relating to the user intent of a heightened multi-tasking experience. This time (Y) is suffient to display ABC transitions similar to the iPhone, but because X does not equal Y, the rate of fluidity (visual viscosity) for Maemo will give this alternate user experience that emphasizes multitasking, but the cost is the difference of Y-X in smoothness to the end-user.
Am I wrong for looking at what the OP asked? Or, do we have the numbers according to this statement to investigate and answer this question as close to correctly as possible?
Last edited by ARJWright; 2010-02-26 at 23:10. Reason: clarifiation to the first part of the statement; grammar
| The Following 4 Users Say Thank You to ARJWright For This Useful Post: | ||
|
|
2010-02-26
, 23:03
|
|
Posts: 1,746 |
Thanked: 2,100 times |
Joined on Sep 2009
|
#50
|
Originally Posted by tso
The N900 does this as well. You can tell in the subtle change in appearance a couple seconds after the application finishes loading and things smooth out.
iirc, the iphone on loading a app first shows a static image of the app interface, and then overlays the ui elements on top.
It's easily spotted in the Application Manager, whose appearance changes noticeably, from a visibly banded gradient and rough icons to smooth. Sometimes the transition between static image and actual UI isn't clean and you see the initial redraw upon load completion.
| The Following User Says Thank You to wmarone For This Useful Post: | ||
But other than Ovi Maps I think the Maemo UI is quite fast, and very pretty. So they put all their effort in fluid scrolling What's the big mystery again?
I am a Mac user and love OSX. But I do not want an iPhone at all..I think the lower resolution is awful. I am still stunned by the crisp text on the N900.