![]() |
2009-12-10
, 15:58
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#22
|
![]() |
2009-12-10
, 16:12
|
Posts: 127 |
Thanked: 50 times |
Joined on Sep 2009
@ Denmark
|
#23
|
![]() |
2009-12-10
, 16:13
|
|
Posts: 2,121 |
Thanked: 1,540 times |
Joined on Mar 2008
@ Oxford, UK
|
#24
|
![]() |
2009-12-10
, 16:23
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#25
|
![]() |
2009-12-10
, 17:19
|
Posts: 114 |
Thanked: 113 times |
Joined on Nov 2009
|
#26
|
![]() |
2009-12-10
, 18:09
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#27
|
I can also confirm this behavior. I am having a little trouble believing that some devices have this problem and some don't...in a fresh out of box, same firmware state. I think some people are coming from faster devices and noticing it more than other people.
Either way, hope it gets fixed because it's really annoying.
![]() |
2009-12-10
, 18:17
|
Posts: 114 |
Thanked: 113 times |
Joined on Nov 2009
|
#28
|
How can you fail to notice the CPU getting pegged for 15 seconds in the load monitor? Face it, it's just not happening for some people - the CPU load drops straight off as soon as the page is loaded for me.
![]() |
2009-12-10
, 18:17
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#29
|
I can also confirm this behavior. I am having a little trouble believing that some devices have this problem and some don't...in a fresh out of box, same firmware state. I think some people are coming from faster devices and noticing it more than other people.
The Following User Says Thank You to Texrat For This Useful Post: | ||
![]() |
2009-12-10
, 18:27
|
Posts: 114 |
Thanked: 113 times |
Joined on Nov 2009
|
#30
|
It isn't that simple. As has been demonstrated, even videos are indicating different results.
There are far too many variables in this scenario to peg the problem to something black or white at this point. Posting usage variables, firmware versions, etc will go a long way toward determining why some people report this issue and some like myself do not. Whether you choose to believe that is the case or not, it is. And there are many among the 300 Amsterdam device recipients who can confirm.
Some report this issue... some report the opposite. So obviously (at least with some version of firmware) the browser can indeed perform decently. So there's an undiscovered gremlin here...
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net