This message is to describe what I have learned in respect to the problem I was having. Just FYI. I have found a solution. It seems, that after calling startService(), the Android OS calls onCreate() asynchronously. So, when I tried to use the results of the onCreate() immediately in the next line of code following the call to startService(), the onCreate() was not done yet. onCreate() is run short after (less than 100ms), but immediately after the call to startService(). droidguy
On Wed, Jan 20, 2010 at 9:15 AM, Stan Berka <[email protected]> wrote: > I continue working on issue 74. I hit some issue with starting the service. > > If anyone has a hint, here's the issue: > In OpenSatNav's onCreate, I'm instatiating TripStatsController, which, in > its constructor, starts the TripStatsService and in the next line calls a > method on the TripStatsService. For this method to run, the > TripStatsService's onCreate must first complete. But: > (core:) > it seems that the TripStatsService's onCreate is not executed by Android OS > immediately after starting the service. > > Has anyone run into antyhing similar? I'm afraid the issue description is a > bit unclear. > droidguy > > >
_______________________________________________ Osn-dev mailing list [email protected] https://lists.kentgeek.org/mailman/listinfo/osn-dev
