I've been working on creating my own System Service for a custom Android build. Everything has progressed as planned and I've just built an SDK that exposes the service interface.
However, I've also been working on an SDK Add-on that includes some libraries that aren't intended to be included in the Android SDK. Optimally, I would like to include the service as part of my SDK Add-on, but for it to still be exposed as a system service rather than a user service. My question: *is there a pathway for adding a system service in an SDK add-on, without making modifications to the platform SDK*? I've looked at Markana's Remixing Android and concluded that the service can be included, however this appraoch appears to register the service by calling ServiceManager.addService in the onCreate method of an app that declares "android:persistent=true" in itss manifest. To my eyes, this seems like a hack to register the service with the system WITHOUT having to modify the platform (i.e. add service in SystemService.java). I'm not against doing this but would prefer to use a more appropriate method if one is available. -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
