mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-26 09:25:55 +03:00
[GH-ISSUE #346] Not able to backup Call log #285
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#285
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 @madhur on GitHub (Jul 16, 2013).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/346
I have been facing issue since July 8th that my call log is not getting backed up. The screen says the last call log backed up was on 8th July, although I have made several calls after that as well.
I am using Cyanogenmod 10.1 latest nightly. I believe the nightly on 8th July made some change on the ROM that broke this functionality.
I am not sure if its Cyanogenmod bug or SMS Backup +.
@pak101 commented on GitHub (Jul 16, 2013):
Same issue, I am on HTC One Developer Edition Stock Version (rooted). No call backup since Jul 9th. On SMS Backup+ 1.5.5
@bolet commented on GitHub (Jul 16, 2013):
The issue was fixed for me in 1.5.5. ZTE Blade, CyanogenMod 10.1 (Android 4.2.2).
@madhur commented on GitHub (Jul 16, 2013):
I see this issue has been resolved in the update which was rolled out today. Thanks.
@pak101 commented on GitHub (Jul 16, 2013):
thanks this issue is resolved in todays update. appreciate your help.