Don't expect miracles here, don't expect solutions to world's problems. It is more likely that I will ask [myself] questions looking for a always elusive answer.
And of course: "All opinions expressed in this blog are the author's own and do not necessarily represent the official view of Nokia". I mean it!
ltomuta | 29 July, 2008 23:00
Just now I've run across a thread in the Forum Nokia's Discussion Boards promising an 1000% improvement of emulator's startup time.
Two things came to my mind seeing this thread: a paradox attributed to Zeno of Elea and ... the S60 3rd Edition SDK, supporting Feature Pack 2.
First, Zeno's paradox, adapted so that it fits the topic:
In order to satisfy the developers, the emulator would have to be fully up and running in about 10s. But, in order to do so, it would have to be in a "half way there" state first, which it cannot do unless it reaches half of that state to begin with. And so on, ... and so on, ad infinitum.
I have seen at least two conclusions of this paradox, pick your choice:
Ok? No more complaints about the emulator please!
Now the serious part:
The S60 3rd Edition SDK FP2 does implement two start modes for the emulator, a partial one, with only a few critical servers started, and the full slow start-up mode with which we are all accustomed by now.
You can switch between the two start-up modes by modifying a setting in emulator's Preferences dialog (through the Tools -> Preferences menu option).
The SDK release v1.1 also adds a graphical indicator to the emulator's window so that the developer knows all the time whether the emulator runs in partial or full startup mode. This is intended as a reminder likely to be useful should you experience some strange application error, which can be a side effect of the chosen startup mode.
For tweaking the emulator of the previous platform releases we are each on our own, but it should be quite safe to try ...
ltomuta | 31/07/2008, 10:54
One old joke about the depreciation of the US Dollar said "No matter how low the dollar is, when you see one bend down and grab it"
I have the same approach to the emulator, and I will always use it, however slow it might be :)
I've been poking my nose in mobile software development since 2000, starting on what was then the ER5 and Ericsson's R380. Since then I've been doing a bit of everything on the S60 Platform, from learning its bits and pieces to helping others find their way trough the maze.
RDF Facets:
qfnZtopicQUqfnTopicZseriesE5f60Q
qfnZtypeQUqfnTypeZBlogContentQ
qfnZtypeQUqfnTypeZBlogE45ntryQ
qfnZtypeQUqfnTypeZCommunityContentQ
qfnZtypeQUqfnTypeZWebpageQ
qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX
Not starting the emulator at all...
mgroeber9110 | 31/07/2008, 10:31
It seems to me that this is a bit the approach that the Carbide.c++ v1.3 release has adopted: the best way to avoid problems with the emulator is to not start it at all, and to use On-Device Debugging instead... :-)