mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-26 01:15:58 +03:00
[GH-ISSUE #526] [Minor] A single call log entry has the incorrect date. Always shows: Last item backup up: Jan 1, 2035, 1:00:00 AM #446
Labels
No labels
AM+RCS
FAQ
awaiting response
backup
bespoke
bug
calendar
call log
cannot reproduce
cloudless
device-specific
documentation
dual- & multi-SIM
duplicate
feature-request
fixed in beta
good first issue
half-missing
help wanted
helpful
meta
misattribution
mms
other message sources
pull-request
question
rejuvenation
restore
schedule
security
stale
task
thanks
v1.5.1
v1.5.10
v1.5.11
v1.5.2
v1.5.3
v1.5.3
v1.5.4
v1.5.4
v1.5.5
v1.5.5
v1.5.6
v1.5.7
v1.5.8
v1.5.9
v1.6β
xoauth
~$ bounty $~
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sms-backup-plus-jberkel#446
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kev007 on GitHub (Jan 20, 2015).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/526
My last item backup up always shows Jan 1, 2035, 1:00:00 AM because one entry in the call log was dated incorrectly after flashing a ROM. I never noticed because I would check my backups by looking at the contents of the IMAP folder in my GMail. It hasn't really bothered me, but it might be troublesome for others.
Solutions?
@kev007 commented on GitHub (Jan 20, 2015):
It was stupid of me not to check the call log! It hasn't been backed up since 17/5/2013, presumably when the error occurred!
@jberkel commented on GitHub (Feb 7, 2016):
you'll need to reset the sync state.