[GH-ISSUE #411] restore on KitKat #345

Closed
opened 2026-02-26 00:36:54 +03:00 by kerem · 13 comments
Owner

Originally created by @handonam on GitHub (Dec 17, 2013).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/411

currently, the messages get wiped out after a restore on kit Kat. I am currently using Moto X with 4.4 and the messages keep deleting. I think I seen this issue on the Nexus 5 as well according to the play Store reviews.

just wanted to give you guys a heads up on that.

Originally created by @handonam on GitHub (Dec 17, 2013). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/411 currently, the messages get wiped out after a restore on kit Kat. I am currently using Moto X with 4.4 and the messages keep deleting. I think I seen this issue on the Nexus 5 as well according to the play Store reviews. just wanted to give you guys a heads up on that.
kerem 2026-02-26 00:36:54 +03:00
Author
Owner

@dserodio commented on GitHub (Dec 27, 2013):

👍

<!-- gh-comment-id:31276493 --> @dserodio commented on GitHub (Dec 27, 2013): :+1:
Author
Owner

@flipsa commented on GitHub (Mar 7, 2014):

Update: Nevermind, just found the beta which works fine under KitKat.

I see similar behaviour. Moved from stock Android 4.3 on my Galaxy Nexus (maguro) to Cyanogenmod 11 (=4.4.2) and trying to restore my old messages and call logs. SMS Backup+ finds my ~10.000 SMS and downloads / processes them for around 15 minutes, during which I can see individual messages popping up in the SMS app, but only for a split-second and then they disappear again.

After finishing all ~10.000 messages without error, SMS Backup+ reports that all my SMS were duplicates (and hence not restored), while my SMS app is still completely empty. Any way to deal with this? These old texts are really important...

<!-- gh-comment-id:37027549 --> @flipsa commented on GitHub (Mar 7, 2014): Update: Nevermind, just found the beta which works fine under KitKat. I see similar behaviour. Moved from stock Android 4.3 on my Galaxy Nexus (maguro) to Cyanogenmod 11 (=4.4.2) and trying to restore my old messages and call logs. SMS Backup+ finds my ~10.000 SMS and downloads / processes them for around 15 minutes, during which I can see individual messages popping up in the SMS app, but only for a split-second and then they disappear again. After finishing all ~10.000 messages without error, SMS Backup+ reports that all my SMS were duplicates (and hence not restored), while my SMS app is still completely empty. Any way to deal with this? These old texts are really important...
Author
Owner

@devurandom commented on GitHub (Mar 20, 2014):

I confirm the behaviour @flipsa sees. I am using SMS Backup+ 1.5.5 on stock KitKat / Android 4.4.2 on my Motorola Moto G. There is no 1.5.6-beta of the app available anymore.

<!-- gh-comment-id:38182072 --> @devurandom commented on GitHub (Mar 20, 2014): I confirm the behaviour @flipsa sees. I am using SMS Backup+ 1.5.5 on stock KitKat / Android 4.4.2 on my Motorola Moto G. There is no 1.5.6-beta of the app available anymore.
Author
Owner

@DippyDawg1932 commented on GitHub (Mar 22, 2014):

Same exact problem here.

<!-- gh-comment-id:38343483 --> @DippyDawg1932 commented on GitHub (Mar 22, 2014): Same exact problem here.
Author
Owner

@AndyRatchick commented on GitHub (Mar 29, 2014):

Same kind of problem here. Samsung S4 recently upgraded to 4.4.2 and somehow a chunk of my texts got deleted (still not sure how, suspect a bug in another app). Anyway, I tried restoring from my backed up messages in GMail and it ran through several thousand quite happily (the last backup had been minutes before, luckily), but on going back into my usual SMS app, no restored items were visible. So I checked the stock app, and for callers that already had existing messages, nothing had changed or been added. However, about 20 threads had been created for numbers that didn't have existing messages still on the phone but these were blank apart from the caller number. When I deleted these, it left me with a series of threads saying "Unknown Number (no subject)" that wouldn't delete. Thankfully a reboot finally cleared them out.

I saw somebody mention Hangouts, but I don't use them. The app itself is disabled as I haven't rooted my phone and hence I'm using the stock S4 ROM.

Results from my log file show nothing for the restores, just the backups. But the app itself said "1 item restored. 5672 dups." That was a call log I deleted and seems to have restored. But the SMS messages are all seen and treated as duplicates.

<!-- gh-comment-id:38993482 --> @AndyRatchick commented on GitHub (Mar 29, 2014): Same kind of problem here. Samsung S4 recently upgraded to 4.4.2 and somehow a chunk of my texts got deleted (still not sure how, suspect a bug in another app). Anyway, I tried restoring from my backed up messages in GMail and it ran through several thousand quite happily (the last backup had been minutes before, luckily), but on going back into my usual SMS app, no restored items were visible. So I checked the stock app, and for callers that already had existing messages, nothing had changed or been added. However, about 20 threads had been created for numbers that didn't have existing messages still on the phone but these were blank apart from the caller number. When I deleted these, it left me with a series of threads saying "Unknown Number (no subject)" that wouldn't delete. Thankfully a reboot finally cleared them out. I saw somebody mention Hangouts, but I don't use them. The app itself is disabled as I haven't rooted my phone and hence I'm using the stock S4 ROM. Results from my log file show nothing for the restores, just the backups. But the app itself said "1 item restored. 5672 dups." That was a call log I deleted and seems to have restored. But the SMS messages are all seen and treated as duplicates.
Author
Owner

@nonbinary commented on GitHub (Apr 1, 2014):

Kitkat changed how SMS apps are handled - apps now need to be registered as the Main SMS App to be able to add SMS messages, and SMS backup+ doesn't do that yet.

I've tried that beta, but doesn't work on CyanogenMod 11 ATM. However, I tried using Google Hangouts, and its actually showing all my old SMS messages. So I'll use that for the time being.

OK Edit #2:
After engaging Google Hangouts, I found a Settings button that said "import again". After clicking that,all my old, restored, SMS's showed up in my main messaging SMS app.
So I guess I found an acceptable workaround.

<!-- gh-comment-id:39233722 --> @nonbinary commented on GitHub (Apr 1, 2014): Kitkat changed how SMS apps are handled - apps now need to be registered as the Main SMS App to be able to add SMS messages, and SMS backup+ doesn't do that yet. I've tried that beta, but doesn't work on CyanogenMod 11 ATM. However, I tried using Google Hangouts, and its actually showing all my old SMS messages. So I'll use that for the time being. OK Edit #2: After engaging Google Hangouts, I found a Settings button that said "import again". After clicking that,all my old, restored, SMS's showed up in my main messaging SMS app. So I guess I found an acceptable workaround.
Author
Owner

@flipsa commented on GitHub (Apr 1, 2014):

Since some people seem to be having trouble finding the beta i mentioned (and which DOES work on Kitkat), it's here: https://plus.google.com/communities/113290889178902750997 (see the upper right where it says "become a beta tester").

<!-- gh-comment-id:39234073 --> @flipsa commented on GitHub (Apr 1, 2014): Since some people seem to be having trouble finding the beta i mentioned (and which DOES work on Kitkat), it's here: https://plus.google.com/communities/113290889178902750997 (see the upper right where it says "become a beta tester").
Author
Owner

@pyzro commented on GitHub (Apr 2, 2014):

I've been able to correct my issue. It seems that by default, the application does not have "write SMS/MMS" privledges
This is what I've done to get around it:

  1. Install AppOps 4.3/4.4 (https://play.google.com/store/apps/details?id=com.colortiger.appopsinstaller)
  2. Open AppOps and select 'Native AppOps'
  3. Swipe left until you get to the Messaging tab
  4. Select SMS Backup+
  5. Locate 'Write SMS/MMS' option and turn to ON.
  6. Launch SMS Backup+ and do a restore.

I sat and was able to watch each message reappear.

<!-- gh-comment-id:39382458 --> @pyzro commented on GitHub (Apr 2, 2014): I've been able to correct my issue. It seems that by default, the application does not have "write SMS/MMS" privledges This is what I've done to get around it: 1) Install AppOps 4.3/4.4 (https://play.google.com/store/apps/details?id=com.colortiger.appopsinstaller) 2) Open AppOps and select 'Native AppOps' 3) Swipe left until you get to the Messaging tab 4) Select SMS Backup+ 5) Locate 'Write SMS/MMS' option and turn to ON. 6) Launch SMS Backup+ and do a restore. I sat and was able to watch each message reappear.
Author
Owner

@AndyRatchick commented on GitHub (Apr 2, 2014):

Thank you. This is how mine was fixed too. It worked fine. It remains to be seen if the permission remains on with a new update of the app though, as it is a feature of Kit Kat, limiting write SMS/MMS permission in apps not set as the default messaging client, rather than a bug with the app itself.

<!-- gh-comment-id:39397462 --> @AndyRatchick commented on GitHub (Apr 2, 2014): Thank you. This is how mine was fixed too. It worked fine. It remains to be seen if the permission remains on with a new update of the app though, as it is a feature of Kit Kat, limiting write SMS/MMS permission in apps not set as the default messaging client, rather than a bug with the app itself.
Author
Owner

@samy commented on GitHub (Jul 9, 2014):

App Ops 4.3/4.4 is no longer available, but you can use App Ops : https://play.google.com/store/apps/details?id=com.findsdk.apppermission&hl=fr

<!-- gh-comment-id:48436033 --> @samy commented on GitHub (Jul 9, 2014): App Ops 4.3/4.4 is no longer available, but you can use App Ops : https://play.google.com/store/apps/details?id=com.findsdk.apppermission&hl=fr
Author
Owner

@awadood commented on GitHub (Jul 13, 2014):

any of the app ops application is no more working.

<!-- gh-comment-id:48838946 --> @awadood commented on GitHub (Jul 13, 2014): any of the app ops application is no more working.
Author
Owner

@samy commented on GitHub (Jul 13, 2014):

@awadood I used App Ops some days ago, it worked perfectly

<!-- gh-comment-id:48839066 --> @samy commented on GitHub (Jul 13, 2014): @awadood I used App Ops some days ago, it worked perfectly
Author
Owner

@jberkel commented on GitHub (Nov 21, 2014):

dup of #475

<!-- gh-comment-id:63964964 --> @jberkel commented on GitHub (Nov 21, 2014): dup of #475
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/sms-backup-plus-jberkel#345
No description provided.