I'm working on what Android calls software-based sensors. Logically, I cannot put my algorithms directly in the Android's MotionManager. These algorithms can be used for different applications. Some specific parameters can be set by any application and affect the behavior of all others. The output from algorithms is something like a float[4] at 100Hz.
I'm looking for a good design pattern but I'm not sure if this is possible with Android because:
I cannot directly add my code to Android's MotionManager (obviously)
A basic library imported in all apps is not designed for this purpose.
"Bind" side of Bind Services is interesting, but, I think they are not designed to work with multiple applications. Moreover, the code for binding is not easier than: [
registerListener (SensorEventListener listener, Sensor sensor, int samplingPeriodUs)](https://developer.android.com/reference/android/hardware/SensorManager.html#registerListener(android.hardware.SensorEventListener, android.hardware.Sensor, int)) for the developer.AIDL can handle the "multiple app" side of the service but I don't feel like it is the way to do it for the same reason than the bind service (passing references).
Did you take a look at http://processors.wiki.ti.com/index.php/Android-Adding_SystemService ?
Writing a small a library to hide the stubs and to handle exceptions might allow you to share the service across applications with a simple API.