Why google wearable service needs intent-filter?
The best way to seehow to implement a WearableListenerService on Android Wear is to look at one ofthe existing samples provided by the SDK. If you look at the DataLayer sampleincluded at $SDK/samples/android-20/wearable/DataLayer it has a full implementationof what you are wanting to do.
If you look in theAndroidManifest.xml for the wearable side, you can see it has the following:
<meta-data android:name="com.google.android.gms.version" android:value="@integer/google_play_services_version" />
<service android:name=".DataLayerListenerService"> <intent-filter> <action android:name="com.google.android.gms.wearable.BIND_LISTENER"/> </intent-filter> </service>
For your securityconcerns ... When we declare a service in manifest and add a filter to it, itautomatically becomes an exported service. So in general, other apps can bindto that service. In case of WearableListenerService, there is a security checkthat happens in the framework to make sure that the agent binding to that isGoogle Play Services so no one else can really bind to that service, unless theapp developer exposes other intent filters in which case the intention is forothers to access it.
So if you implementyour code in the same way as the Wear SDK samples, your app should be secureand you do not need to worry about any extra permissions, etc.
Andriod wearable phone's app service willautomatically be started if phone sendData to phone
1 inherit fromWearableListenerService
Although the phone'sservice doesn't start, but app procedure is open, google will automaticallystart the service if watch sendData to phone