android - Can a Wear app use a MediaBrowser to call a MediaBrowserService in an app on the device? -

we added mediabrowserservice our app allows android auto discover , play audio content via our app on device. works expected.

by default, wear picks , displays our "now playing" notification, provides basic play/pause funtionality, , provides "browse" action communicating our mediabrowserservice.

i'm working on adding actual wear sub-app our main app , i'd call our own mediabrowserservice wear os does.

however, when call mediabrowser.connect(), connectioncallback onconnectionfailed fires. connection never succeeds. debugging on primary app, never see call come in our mediabrowserservice.

here's related code. possible use mediabrowser in way replicate functionality wear capable of? unfortunately, connectioncallback provides no information whatsoever explain why connection attempt failed.

mediabrowser.connectioncallback callback = new mediabrowser.connectioncallback() {             @override             public void onconnected()             {                 super.onconnected();             }              @override             public void onconnectionfailed()             {                 super.onconnectionfailed();             }         };   mediabrowser mediabrowser = new mediabrowser(this, new componentname("main.app.package.name", "full.package.name.of.our.mediabrowserservice"), callback, null); mediabrowser.connect(); 

update

when play audio in our app , audio notification appears on watch, can see our mediabrowserservice start , package calling "ongetroot"

com.google.android.wearable.app

i assuming wear os seems package name android wear app on device. somehow requesting , relaying data watch , perhaps mediabrowser doesn't work actual wear app on watch?

i see plenty of examples using googleapiclient communicate data between watch , phone. hoping reuse our mediabrowserservice since wear uses default. seems not option , must use googleapiclient , wearablelistenerservice if want have wear app request data handheld app.

for answer question "no". presumably 1 can use mediabrowser , mediabrowserservice within same wear app (or possibly between 2 wear apps) can't use mediabrowser on wear device find , connect mediabrowserservice on connected phone/tablet. android wear app on phone/tablet use mediabrowser talk mediabrowserservices on phone/tablet; however, data passed notification on wear device via normal wear data layer.