mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #420] Feature Request: Allow user to manually set 'skip' date #354
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#354
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 @Yakhobian on GitHub (Jan 13, 2014).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/420
When installing SMS Backup+ a second time after wiping a phone or changing phones, you are given the option to 'skip' the backup, so as to prevent messages being backed up twice.
This generally works, but I am currently in the situation where this worked for SMS but not for WhatsApp. As such, when I attempt to do a backup now, while only the few new SMS messages will be backed up, SMS Backup+ attempts to back up every single WhatsApp message on my phone. At this point I am cancelling the backup, so as to prevent all my WhatsApp messages being duplicated on Gmail.
My suggestion for a feature would be an advanced setting to manually set the date and time cut-off value for back-ups, so as to allow the user to get around such a scenario.
If this feature was available, the problem could be solved by the following steps:
After this point, only new messages should get backed up for both SMS and WhatsApp.
I hope you will take this suggestion into consideration.
@Yakhobian commented on GitHub (Jan 13, 2014):
After looking at the file "/data/data/com.zegoggles.smssync/shared_prefs/com.zegoggles.smssync_preferences.xml", I think this would probably be even easier to implement than I initially thought.
The preferences file has separate time stamps for last backup of each service (sms, call logs, whatsapp, etc). Perhaps the feature could just be to allow the user to edit any of these time stamps as required.
I also realised that there is no need for the 4th step in my original message as the last backup time value will automatically be set to the latest message date and time after performing the backup in the 3rd step.
Furthermore, since each backup type has its own last backup date, the first and last steps of my original message would also seem to be unnecessary.
@jberkel commented on GitHub (Nov 21, 2014):
sorry, won't do this