mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-26 01:15:58 +03:00
[GH-ISSUE #45] Backing Up Deleted SMS #44
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#44
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 @hirenshah on GitHub (Sep 27, 2010).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/45
I just moved over from SMS BackUp to your more advanced version and seem to have found one issue. What I liked about SMS BackUp was that messages were backed up instantly. Now if I was to delete a received or sent item straight away, it will not be backed up. Is there any way for you to store all the messages and then back them up as per the schedule?
@jberkel commented on GitHub (Sep 27, 2010):
You mean incoming messages? they'll get backed up a little bit later than in SMS Backup, (3 minutes) mainly to conserve battery. you can change it back to 1 min in Advanced Settings.
@hirenshah commented on GitHub (Sep 27, 2010):
But if that incoming message is deleted before the 1 minute, it won't be backed up...
@jberkel commented on GitHub (Sep 27, 2010):
sms backup's schedule was 1 minute after arrival, so it would behave exactly the same if you changed it in sms backup+ to 1 minute.
@hirenshah commented on GitHub (Sep 27, 2010):
Are sent items included in that? What exactly is the difference between regular backup and incoming?
Would it be possible for you to store all incoming and outgoing messages and upload them as per the schedule? So even if messages were deleted before the schedule time they would still be backed up? This way we can say battery by not constantly uploading too.
@jberkel commented on GitHub (Sep 27, 2010):
yes, sent items are included as well. it is a bit confusing, whenever a backup is triggered both incoming/sent messages are backed up. the difference is that a backup is done N minutes after arrival of a message OR N minutes as specified by "regular backup schedule". i'm happy to change terminology if you can find better names for the preferences, i know it's not obvious.
@hirenshah commented on GitHub (Sep 28, 2010):
I'll have a think about new terminology and let you know if I think of something.
What about my storing suggestion? Any comment on that?
@jberkel commented on GitHub (Sep 28, 2010):
it would be possible to store them as you suggest, but it would make the app more complex and therefore more likely to have bugs, so i'd rather not have this feature.
@hirenshah commented on GitHub (Sep 28, 2010):
Fair enough. I just thought I would mention it because I am sure there are others who would like a similar feature.
@hirenshah commented on GitHub (Sep 30, 2010):
The Change Log for the latest version says that this issue is fixed... how?
@jberkel commented on GitHub (Sep 30, 2010):
oh it's actually 46+47. shouldn't release software at 4am in the morning ;)