Hi all! I have an app that during it's initialization it posts custom events for itself, and initialization finishes when no more events are received.
During the initialization the EvtGetEvent read events with no delay and on the first idle event starts to wait forever, as a classic app. All this works ok, except on *some* of the Tungsten|T5 and Treo 650 devices (say 30% of all I know of). The usual initialization is about 1 second (I have a T5 myself), but some users report times like 10 to 40 seconds. What can delay the event loop on these devices during the initialization phase? There is some moderate memory allocation and reading or resources, but nothing extraordinary. Still the majority of users report perfect initialization. I've researched a potential conflict with the apps installed on the problem devices for over a month with no success. Any idea will be more then welcome! Thanks and all the best, Ilia. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
