mirror of
https://codeberg.org/Freeyourgadget/Gadgetbridge
synced 2024-10-11 07:38:15 +02:00
da7de378d3
Details: when we ask to fetch activity samples from date:time:tz+dst, the band, under certain conditions, will send us back date:time:tz (without the dst offset) We're fine with that, so we start fetching. When it's done, we take the last sample's timestamp (still without dst offset), convert it to a unix timestamp, create a Calendar using current tz and apply the unix timestamp. Then we send that timestamp again to the band in order to fetch activity samples from then, but we again add the dst offset to the tz, so send as date:time:tz+dst without changing the timestamp. That way, we may end up at the timestamp we began with, fetching the same activity data again and not progressing. We first need to thorougly understand how the devices behave, before we can reenable and fix this. |
||
|---|---|---|
| .. | ||
| btclassic | ||
| btle | ||
| devices | ||
| receivers | ||
| serial | ||
| AbstractDeviceSupport.java | ||
| DeviceCommunicationService.java | ||
| DeviceSupport.java | ||
| DeviceSupportFactory.java | ||
| NotificationCollectorMonitorService.java | ||
| ServiceDeviceSupport.java | ||