In my blog post, I noted that
Despite being almost constantly connected (in order to send notifications to the watch), the Zepp app doesn't seem to sync data very frequently. In fact, as far as I can make out, it often doesn't sync data at all until the app is next opened (I haven't yet tried leaving it for days though).
I've now tried leaving it for a few days - the result is that I ended up with gaps in my data. The app doesn't sync at all unless it's opened.
Whilst this isn't a problem with this sync script per se, it does affect it, so I'm raising this to look at options
Activity
19-Aug-23 11:43
assigned to @btasker
19-Aug-23 11:49
I had been hoping that there might be an intent that we could trigger to have the app sync, however no such luck:
adb shell jflte:/ # dumpsys activity broadcasts | grep Intent | sort | uniq com.google.android.play.core.splitinstall.receiver.SplitInstallUpdateIntentService: Action: "com.google.android.play.core.splitinstall.receiver.SplitInstallUpdateIntentService" Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) } Intent { act=android.intent.action.TIME_TICK flg=0x50200010 } Intent { act=android.os.action.POWER_SAVE_TEMP_WHITELIST_CHANGED flg=0x40000010 } Intent { act=com.android.providers.calendar.intent.CalendarProvider2 flg=0x14 (has extras) } Intent { act=com.android.server.action.NETWORK_STATS_POLL flg=0x14 (has extras) } Intent { act=com.android.server.action.NETWORK_STATS_UPDATED flg=0x40000010 } Intent { act=com.google.android.gms.gcm.ACTION_CHECK_QUEUE flg=0x14 (has extras) } Intent { act=com.google.android.gms.gcm.HEARTBEAT_ALARM flg=0x10 } Intent: act=android.hardware.usb.action.USB_STATE flg=0x31000010 Intent: act=android.intent.action.ACTION_DEFAULT_DATA_SUBSCRIPTION_CHANGED flg=0x21000010 Intent: act=android.intent.action.ACTION_DEFAULT_VOICE_SUBSCRIPTION_CHANGED flg=0x21000010 Intent: act=android.intent.action.BATTERY_CHANGED flg=0x60000010 Intent: act=android.intent.action.HDMI_PLUGGED flg=0x44000010 Intent: act=android.intent.action.SIG_STR flg=0x10 Intent: act=android.intent.action.SIM_STATE_CHANGED flg=0x5000010 Intent: act=android.media.ACTION_SCO_AUDIO_STATE_UPDATED flg=0x10000010 Intent: act=android.media.INTERNAL_RINGER_MODE_CHANGED_ACTION flg=0x34000010 Intent: act=android.media.MASTER_MUTE_CHANGED_ACTION flg=0x34000010 Intent: act=android.media.RINGER_MODE_CHANGED flg=0x34000010 Intent: act=android.media.SCO_AUDIO_STATE_CHANGED flg=0x10000010 Intent: act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4200010 Intent: act=android.net.conn.INET_CONDITION_ACTION flg=0x4000010 Intent: act=android.net.conn.TETHER_STATE_CHANGED flg=0x20000010 Intent: act=android.net.nsd.STATE_CHANGED flg=0x44000010 Intent: act=android.net.wifi.STATE_CHANGE flg=0x4000010 Intent: act=android.net.wifi.WIFI_STATE_CHANGED flg=0x4000010 Intent: act=android.net.wifi.action.WIFI_SCAN_AVAILABILITY_CHANGED flg=0x4000010 Intent: act=android.net.wifi.p2p.STATE_CHANGED flg=0x4000010 Intent: act=android.net.wifi.p2p.action.WIFI_P2P_PERSISTENT_GROUPS_CHANGED flg=0x4000010 Intent: act=android.net.wifi.supplicant.STATE_CHANGE flg=0x24000010 Intent: act=android.os.UpdateLock.UPDATE_LOCK_CHANGED flg=0x44000010 Intent: act=android.telephony.action.DEFAULT_SMS_SUBSCRIPTION_CHANGED flg=0x21000010 Intent: act=android.telephony.action.DEFAULT_SUBSCRIPTION_CHANGED flg=0x21000010 Intent: act=android.telephony.action.SERVICE_PROVIDERS_UPDATED flg=0x10 options=Bundle[{android.pendingIntent.backgroundActivityAllowed=false, android:broadcast.temporaryAppWhitelistDuration=10000}] options=Bundle[{android.pendingIntent.backgroundActivityAllowed=false}]
So, instead, we need to use a sledgehammer to crack a nut - we can use Tasker to automatically launch the Zepp app (at least) once a day.
There is, however, still an issue with this.
I configured a tasker profile to run at 12:42 (i.e. a few minutes ago) and launch
Zepp
.It did exactly that.
But, Zepp was a little misleading - when I unlocked the screen it started syncing with the watch. This gave the impression that it only syncs when the screen is unlocked. However, as far as I can see, it had synced on launch - it must just launch a new sync when the display is unlocked.
26-Aug-23 15:59
mentioned in issue gadgetbridge_to_influxdb#8
02-Sep-23 16:51
Closing as Won't Fix - see #9