mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #341] Cant sync call logs/calendar intergration #281
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#281
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 @parkcity on GitHub (Jul 11, 2013).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/341
Galaxy Nexus using Jelly Belly ROM 14.3. I am able to backup/restore SMS fine (Manual and Auto) but call logs/calendar integration will not sync UNLESS I disable sync for SMS, then the call log with calendar integration works.
@buzypi commented on GitHub (Jul 11, 2013):
I see the same issue.
I can confirm that, if you disable SMS backup, then call logs are backed up.
@copecu commented on GitHub (Jul 14, 2013):
I have the same problem. Android 4.2.2
Sync log says after manual sync:
14-07 10:00 Backup requested (manual)
14-07 10:00 Starting backup (MANUAL)
14-07 10:00 Backing up (0 SMS, 0 MMS, 50 call log)
14-07 10:00 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://xoauth2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=0, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=MANUAL, debug=true}
14-07 10:00 Backup finished
@palv1to commented on GitHub (Jul 15, 2013):
I have the same problem also, only after version 1.5.4. The only way to backup call log is to disable SMS backup.
Device: MTK6573 / Hero H7300
Android version: 2.3.5
Rom: Hero H7300 (HD7/T9299) Cooked ROM by Bunta v9
SMS Backup plus version: 1.5.4
@ChintanRaval commented on GitHub (Jul 15, 2013):
SMS Backup + @ 1.5.4 (but the issue is since before the app upgrade)
Samsung Galaxy Nexus @ 4.2.2
Same issue. In addition to Call logs, WhatsApp logs too don't sync. After reading this post, I disabled SMS/Text backup and then the pending Call logs & WhatsApp messages synced fine upon triggering a manual sync.
Nothing special in the logs too.. same as copecu's logs above (https://github.com/jberkel/sms-backup-plus/issues/341#issuecomment-20933282), just a different number for call log.
Thanks @parkcity for reporting this one to start the thread.
@jberkel commented on GitHub (Jul 15, 2013):
can you try out the beta (https://github.com/jberkel/sms-backup-plus#beta-testing) and see if it's fixed there? planning to release soon
@palv1to commented on GitHub (Jul 15, 2013):
Tried to become beta tester from SMS Backup+ community page and got:
404. That’s an error.
The requested URL was not found on this server. That’s all we know.
The link was: https://play.google.com/apps/testing/com.zegoggles.smssync
Am I doing something wrong?
@jberkel commented on GitHub (Jul 15, 2013):
@palv1to you need to join the community first
@palv1to commented on GitHub (Jul 15, 2013):
Yeap sorry my mistake, I have different account for the phone.
I just installed 1.5.5 and tested it, problem fixed!!! :)
Thank you! Keep up the good work! :)
@jberkel commented on GitHub (Jul 15, 2013):
fixed in 1.5.5
@ChintanRaval commented on GitHub (Jul 16, 2013):
@jberkel Thanks for the quick fix. Sorry, I couldn't test the beta yesterday since I was on the road. I've updated the app to 1.5.5 and things seem to be in place now.