Running the MediaLibraryService of the demo app in a different process

[XuQK]

I modified demo-session PlaybackService's process as android:process=":audioPlayer", it completely inoperable.

[marcbaechinger]

I'm not sure what you exactly referring to because you decided to not send a stack trace or similar. From what you report, I'd expect that you have received some stack traces saying you are accessing the controller on the wrong thread. I'm guessing though.

Basically, the service is running in the same process as the UI because this is how the demo app has been designed. I think running the service in the same process is the recommended way for most apps. If the service is run in another process, then an app developer needs (we both are just experiencing that :)), a bit of more knowledge of what is going on exactly.

If you want this to work, then you need to apply some further changes in the demo app.

You can do this by replacing MoreExecutor.directExecturor() calls with ContextCompat.getMainExecutor(this) when calling a method of the MediaBrowser that returns a ListenableFuture. I count three such calls in the session demo. This should make the demo app work with a service in another process as well. I think it would make sense to change this on our end (without getting into the discussion of whether MoreExecutor.directExecturor() is preferable over ContextCompat.getMainExecutor(this) in some cases).

If this is not the reason for the inoperable state I'm happy to expect a bit more details describing the malfunctioning.

[marcbaechinger]

With the change above this should now work. I'm closing. Please re-open if you experience further issues. Thanks for reporting!