Detecting connect/disconnect using CapabilityApi - Wear OS Software and Hacking General

In developing my wear watch faces I like to have the wearable vibrate when it detects connection of disconnection from the mobile. In the past I've implemented NodeApi.NodeListener and done the vibration in the onPeerConnect or onPeerDisconnect methods.
This has worked well but NodeApi has be deprecated in favor of the CapabilityApi.
Does anyone know of any simple example of how to detect connection using the CapabilityApi? None of the examples I've tried have worked at all. It should be fairly simple since I'm not trying to do downloads or anything, just detecting.
Thanks.

---

dlbarron said:
In developing my wear watch faces I like to have the wearable vibrate when it detects connection of disconnection from the mobile. In the past I've implemented NodeApi.NodeListener and done the vibration in the onPeerConnect or onPeerDisconnect methods.
This has worked well but NodeApi has be deprecated in favor of the CapabilityApi.
Does anyone know of any simple example of how to detect connection using the CapabilityApi? None of the examples I've tried have worked at all. It should be fairly simple since I'm not trying to do downloads or anything, just detecting.
Thanks.
Click to expand...
Click to collapse
Did you checked this http://stackoverflow.com/questions/35136881/cant-detect-node-using-the-capability-api ?

---

Skin1980 said:
Did you checked this http://stackoverflow.com/questions/35136881/cant-detect-node-using-the-capability-api ?
Click to expand...
Click to collapse
Yes, I've seen that one. The code is far from complete, for example, what does that class extend or implement?

---

Here's what I've done.
This is the entry in the manifest for the service.
<service
android:name=".MyService">
<intent-filter>
<action android:name="com.google.android.gms.wearable.DATA_CHANGED" />
<action android:name="com.google.android.gms.wearable.MESSAGE_RECEIVED" />
<action android:name="com.google.android.gms.wearable.CAPABILITY_CHANGED" />
<action android:name="com.google.android.gms.wearable.CHANNEL_EVENT" />
</intent-filter>
</service>
And here is the code that is supposed to run
public class MyService extends WearableListenerService implements GoogleApiClient.ConnectionCallbacks,GoogleApiClient.OnConnectionFailedListener {
private GoogleApiClient mGoogleApiClient;
private static final String TAG="MyService";
public static final long VIBRATE_TIME = 250;
@override
public void onCreate() {
super.onCreate();
Toast.makeText(this,"Starting onCreate",Toast.LENGTH_LONG).show();
Log.i(TAG,"Starting onCreate");
mGoogleApiClient = new GoogleApiClient.Builder(this)
.addApi(Wearable.API)
.addConnectionCallbacks(this)
.addOnConnectionFailedListener(this)
.build();
ConnectionResult connectionResult = mGoogleApiClient.blockingConnect(30, TimeUnit.SECONDS);
if(!connectionResult.isSuccess()) {
Toast.makeText(this,"onCreate",Toast.LENGTH_LONG).show();
Log.i(TAG,"onCreate");
}
}
I've overridden the other methods in WearableListenerService but it doesn't matter, the onCreate isn't even called so there's no way the GoogleApiClient is ever created. Now according to what I've read I shouldn't have to do anything to start the service, it is supposed to be started in response to events, like connecting etc, but nothing.

---

Well, I found the solutions. I created a java class that extends WearableListenerService and in it I override the onPeerConnected and onPeerDisconnected methods. But I also had to add this to the wearable manifest:
<service
android:name=".WearListener">
<intent-filter>
<action android:name="com.google.android.gms.wearable.BIND_LISTENER"/>
</intent-filter>
</service>
This is odd because BIND_LISTENER is deprecated. But it works so that's all I care about.