# Push to android/mobile

**URL:** https://forum.syncthing.net/t/push-to-android-mobile/13273
**Category:** Feature
**Created:** [May 15, 2019, 1:24pm UTC](https://forum.syncthing.net/t/push-to-android-mobile/13273 "2019-05-15T13:24:46Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![anon\_syncthing](https://forum.syncthing.net/user_avatar/forum.syncthing.net/anon_syncthing/32/6203_2.png) [@anon\_syncthing](https://forum.syncthing.net/u/anon_syncthing)
#### Post date: [May 15, 2019, 1:24pm UTC](https://forum.syncthing.net/t/push-to-android-mobile/13273/1 "2019-05-15T13:24:46Z")

</div>

I don’t leave syncthing running on my android devices because it is a battery drain. I propose that the desktop versions of syncthing allow remote devices to be designated as “mobile devices.” When changes are seen, a push notification is sent to android that starts the syncthing service, syncs the changed files, and then stops the syncthing service.

---

<div class="post-metadata">

### Author: ![calmh](https://forum.syncthing.net/user_avatar/forum.syncthing.net/calmh/32/15311_2.png) [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [May 15, 2019, 4:27pm UTC](https://forum.syncthing.net/t/push-to-android-mobile/13273/2 "2019-05-15T16:27:48Z")

</div>

The Syncthing protocol is essentially “push notification” style already. I suspect the battery drain comes from Syncthing not properly _sleeping_ for long enough to let the mobile CPU shut down etc, as there are a lot of background things ongoing.

“Real” Android-level push notifications, handled by Android/Google when the app is not even running, is not something that fits into how Syncthing works unfortunately.
