Skip to content

Commit

Permalink
leave service running when pebble app is closed. the user might want …
Browse files Browse the repository at this point in the history 
…to go right back to it.
  • Loading branch information
@squilter
squilter committed Mar 14, 2015
1 parent 3730598 commit f31f522
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Android/src/main/java/org/droidplanner/pebble/PebbleCommunicatorService.java
View file
Original file line number Diff line number Diff line change
Expand Up @@ -353,7 +353,7 @@ public void receiveData(Context context, int transactionId, PebbleDictionary dat
break;

case KEY_REQUEST_DISCONNECT:
stopSelf();
//Don't do anything. Running stopSelf() would cause issues if the user changed apps and then changed back

This comment has been minimized.

Sign in to view

Copy link
@phmagic

phmagic Mar 16, 2015

How would the user kill this service then?
break;

case KEY_REQUEST_MODE_FOLLOW:
Expand Down

1 comment on commit f31f522

@squilter
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@phmagic The service is killed when Tower disconnects.

Previously, you could also kill the service by exiting the watchapp on the pebble, but that wasn't a good idea. The user might want to switch to a stopwatch app, start a timer, and switch back.

Please sign in to comment.