[GH-ISSUE #1044] Call log entries stored into wrong Google Calendar #833

New issue

Closed

opened 2026-02-26 01:32:02 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 01:32:02 +03:00

Owner

Originally created by @fuxoft on GitHub (Nov 26, 2020).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1044

All my Call log entries don't appear in "Call log" calendar but in calendar "Pupen rozvrh", which is (coincidentally?) the most recent Google calendar I've created. Curiously, in the "Call log settings" page, the option "Calendar used for call logs" is set to "None" and is greyed out (cannot be clicked / changed).

Expected behaviour

Call log entries should appear in my "Call log" Google Calendar.

Actual behaviour

All call log entries appear in my "Pupen rozvrh" Google Calendar.

Steps to reproduce the behaviour

Configure SMS Backup+, do initial backup.

Please specify the following:

Android version
Android 10
Phone model / brand
Nokia 7.2
SMS Backup+ version installed
SMS Backup+ 1.6.0-BETA2
Messaging app
Google Messages

Originally created by @fuxoft on GitHub (Nov 26, 2020). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1044 All my Call log entries don't appear in "Call log" calendar but in calendar "Pupen rozvrh", which is (coincidentally?) the most recent Google calendar I've created. Curiously, in the "Call log settings" page, the option "Calendar used for call logs" is set to "None" and is greyed out (cannot be clicked / changed). ### Expected behaviour Call log entries should appear in my "Call log" Google Calendar. ### Actual behaviour All call log entries appear in my "Pupen rozvrh" Google Calendar. ### Steps to reproduce the behaviour Configure SMS Backup+, do initial backup. ### Please specify the following: * Android version Android 10 * Phone model / brand Nokia 7.2 * SMS Backup+ version installed SMS Backup+ 1.6.0-BETA2 * Messaging app Google Messages

kerem closed this issue

2026-02-26 01:32:02 +03:00

kerem commented

2026-02-26 01:32:02 +03:00

Author

Owner

@kurahaupo commented on GitHub (Jan 6, 2021):

When I investigated a similar issue, the it was one of those "this code is so simple how can it possibly go wrong" kind of errors, so the only reasonable conclusion is that it's an error in a library somewhere.

@fuxoft I'm closing this as a duplicate, but feel free to add comments to #963. If it turns out to be a separate issue then this can be reopened.

@kurahaupo commented on GitHub (Jan 6, 2021): When I [investigated a similar issue](./963#issuecomment-711801677), the it was one of those "this code is so simple how can it possibly go wrong" kind of errors, so the only reasonable conclusion is that it's an error in a library somewhere. @fuxoft I'm closing this as a duplicate, but feel free to add comments to #963. If it turns out to be a separate issue then this can be reopened.