The part of your app that uses activities, that needs this initialization part, must access the resources/caches/etc that are created during this initialization. Why can't you initialize these resource/caches/etc. when they are accessed for the first time (the lazy-loading stuff)? If you can't do the lazy-loading on first access, why is that? Maybe we can find a solution for that issue and you don't need to try to get at the process-id.
Using some form of lazy loading, the IntentService, which will never access these resources/caches/etc, will therefore not cause the initialization of these resources/caches. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
