[GH-ISSUE #1112] Calendars created on android 15 cannot be selected #891

New issue

Open

opened 2026-02-26 01:32:14 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @danielegobbetti on GitHub (Mar 22, 2025).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1112

Hello,
I noticed the bug mentioned in the title.

In a local build I verified that changing line
https://github.com/jberkel/sms-backup-plus/blob/master/app/src/main/java/com/zegoggles/smssync/calendar/CalendarAccessorPost40.java#L82

               CalendarContract.Calendars.NAME,

To:

               CalendarContract.Calendars.CALENDAR_DISPLAY_NAME,

Correctly shows all calendars.

Originally created by @danielegobbetti on GitHub (Mar 22, 2025). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1112 Hello, I noticed the bug mentioned in the title. In a local build I verified that changing line https://github.com/jberkel/sms-backup-plus/blob/master/app/src/main/java/com/zegoggles/smssync/calendar/CalendarAccessorPost40.java#L82 > CalendarContract.Calendars.NAME, To: > CalendarContract.Calendars.CALENDAR_DISPLAY_NAME, Correctly shows all calendars.

kerem commented

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

Author

Owner

@ltguillaume commented on GitHub (Nov 4, 2025):

Android 16
SMS Backup+ 1.5.11 and 1.6.0-BETA2

Confirmed to some extent:
Calendars created using DAVx5 are not listed by SMS Backup+ anymore, but all calendars coming from ICSx5 (which are all read-only subscriptions) are listed, which makes no sense...

@ltguillaume commented on GitHub (Nov 4, 2025): Android 16 SMS Backup+ 1.5.11 and 1.6.0-BETA2 Confirmed to some extent: Calendars created using DAVx5 are not listed by SMS Backup+ anymore, **but** all calendars coming from ICSx5 (which are all **read-only subscriptions**) _are_ listed, which makes no sense...

kerem commented

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

Author

Owner

@sshaikh commented on GitHub (Nov 4, 2025):

If it helps, the change in this report fixed the issue for me. But you would have to make your own build.

@sshaikh commented on GitHub (Nov 4, 2025): If it helps, the change in this report fixed the issue for me. But you would have to make your own build.

kerem commented

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

Author

Owner

@ltguillaume commented on GitHub (Nov 4, 2025):

No chance of this getting merged @jberkel @kurahaupo?

@ltguillaume commented on GitHub (Nov 4, 2025): No chance of this getting merged @jberkel @kurahaupo?