mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #419] Restore not working on CM11 #353
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#353
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 @maxdraki on GitHub (Jan 10, 2014).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/419
I'm trying to restore SMS from an earlier backup. If I open the messaging app while the restore is running the messages flash up and then disappear. When the restore completes the messaging app is empty. Call log is restores successfully though
thank you
@RoadXY commented on GitHub (Jan 11, 2014):
What phone and Android version?
@maxdraki commented on GitHub (Jan 11, 2014):
The phone is an HTC One running newly installed cyanogenmod 11
this is the log file from last night:
11-01 01:01 Backup requested (regular)
11-01 01:01 Starting backup (REGULAR)
11-01 01:01 Skipped (no items found)
11-01 01:01 Backup finished
11-01 01:01 Next backup scheduled for: 03:01
11-01 03:01 Backup requested (regular)
11-01 03:01 Starting backup (REGULAR)
11-01 03:01 Skipped (no items found)
11-01 03:01 Backup finished
11-01 03:01 Next backup scheduled for: 05:01
11-01 05:01 Backup requested (regular)
11-01 05:01 Starting backup (REGULAR)
11-01 05:01 Skipped (no items found)
11-01 05:01 Backup finished
11-01 05:01 Next backup scheduled for: 07:01
11-01 07:01 Backup requested (regular)
11-01 07:01 Starting backup (REGULAR)
11-01 07:01 Skipped (no items found)
11-01 07:01 Backup finished
11-01 07:01 Next backup scheduled for: 09:01
@RoadXY commented on GitHub (Jan 11, 2014):
That's a problem with Android 4.2.2 with SMS Backup+
The developer is aware of the issue and working on it.
@maxdraki commented on GitHub (Jan 11, 2014):
I assume you mean 4.4.2 - but thanks for letting me know
is there an existing bug I can track? (I looked but couldn't find one) - would be good to mark this as a duplicate
@RoadXY commented on GitHub (Jan 11, 2014):
Sorry, 4.4.2 I meant indeed
@RoadXY commented on GitHub (Jan 11, 2014):
https://github.com/jberkel/sms-backup-plus/issues/389
Is the issue to track
@maxdraki commented on GitHub (Jan 11, 2014):
thanks for that - I used App ops and managed to get it to restore successfully
thank you
@Prismerlin commented on GitHub (Feb 15, 2014):
@maxdraki could you help me plz, I have the same problem.
thanks
@maxdraki commented on GitHub (Feb 15, 2014):
@Prismerlin
I'm really not an expert - but if I remember correctly I used the instructions here:
http://www.androidpolice.com/2013/12/06/non-default-sms-apps-in-kitkat-can-still-write-to-the-sms-database-using-a-switch-in-app-ops-no-root-required/
unfortunately it seems that App Ops is no longer available..
but you might be able to use https://github.com/jclehner/AppOpsXposed which obviously requires you to use the Xposed framework - which I have no experience of I'm afraid
good luck
@Prismerlin commented on GitHub (Feb 15, 2014):
@maxdraki
Thanks a lot for your kind help. I'm gonna try.
@false9striker commented on GitHub (Apr 29, 2014):
If your problem is still not solved try following these steps.
Everything should be fine.
Thanks.
@jwvdm commented on GitHub (May 1, 2014):
@false9striker The "Become a beta tester" link does not currently seem to be working. I get the following message:
@false9striker commented on GitHub (May 2, 2014):
@jwvdm Oh that's strange. I tried with a diff google and and seems working still. Could you please try again?
@jwvdm commented on GitHub (May 2, 2014):
@false9striker I don't use google+, so I also made sure to create a profile with one of my accounts but that did not help. I just tried with a different account, but got the same result.
In the mean time, I was able to work around this issue in CyanogenMod 11 by enabling
@busytrucker commented on GitHub (Jun 1, 2014):
The fix above worked for my GS3 CM11 4.4.2
@maphy-psd commented on GitHub (Jun 29, 2014):
fix @jwvdm works on Galaxy S4 CM11-M7 4.4.2..thanks for it!
@JollyDevelopment commented on GitHub (Jul 14, 2014):
@jwvdm 's fix worked for a Sprint Galaxy S4 running Cyanogen 11
@gilles1394 commented on GitHub (Nov 14, 2014):
Using CM 11-M11 on Samsung Galaxy Note 2 LTE (N7105) with app version 1.5.5, I had the same issue. The work around from @jwvdm solved it.
Thank you.
@jberkel commented on GitHub (Dec 28, 2014):
fixed in 1.5.6