[GH-ISSUE #494] Restore triggers the messaging app notification for new messages #420

New issue

Closed

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

kerem commented

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

Owner

Originally created by @ricferr1976 on GitHub (Nov 11, 2014).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/494

In a Oneplus One running Android 4.4.4 and using Hangouts as default messaging app, when using the SMS Backup + beta to restore, after restoring i get a recurrent notification from the Messaging app saying that i have new messages. The number of new messages is the same as the messages i just restored. I can't get rid of the notification.

Steps:

Successfully restore SMS with SMS Backup + beta.
Messaging app notification appears saying i have X new messages.
Enter messaging app through the notification. It warns that i have Hangouts as default.
The notification appears again.

This is not a show stopper but is annoying.

Originally created by @ricferr1976 on GitHub (Nov 11, 2014). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/494 In a Oneplus One running Android 4.4.4 and using Hangouts as default messaging app, when using the SMS Backup + beta to restore, after restoring i get a recurrent notification from the Messaging app saying that i have new messages. The number of new messages is the same as the messages i just restored. I can't get rid of the notification. Steps: 1. Successfully restore SMS with SMS Backup + beta. 2. Messaging app notification appears saying i have X new messages. 3. Enter messaging app through the notification. It warns that i have Hangouts as default. 4. The notification appears again. This is not a show stopper but is annoying.

kerem closed this issue

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

kerem commented

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

Author

Owner

@ella2 commented on GitHub (Dec 29, 2014):

Gracias

@ella2 commented on GitHub (Dec 29, 2014): Gracias

kerem commented

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

Author

Owner

@jberkel commented on GitHub (Jun 12, 2015):

sorry not fixing this

@jberkel commented on GitHub (Jun 12, 2015): sorry not fixing this

kerem commented

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

Author

Owner

@bmedici commented on GitHub (Jul 6, 2015):

Do you have anything new about this? Having the same troubles, though it doesn't seem to be related to any restoration method.

@bmedici commented on GitHub (Jul 6, 2015): Do you have anything new about this? Having the same troubles, though it doesn't seem to be related to any restoration method.