You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exporting contacts (as vCard), call logs as well as SMS messages (as CSV).
622KiB 0:00:00 [ 745KiB/s] [ <=> ]
mv: kan status van './backup-tmp/open-android-backup-temp/SMS_Messages.csv' niet opvragen: Bestand of map bestaat niet
I checked the backup-tmp/ directory and indeed the SMS files weren't there.
The Open Android Backup Companion app mentioned in the Export Data section:
Exported 2783 contact(s) out of 2783. Found 527 SMS messages to process, of which 547 have been exported. 992 call log(s) have been found, 992 of which have been exported.
Some thoughts
Perhaps it is related to me using a custom SMS app Simple SMS Messenger, although the companion app has mentioned the back-upped SMS files.
I noticed the same issue mentioned in this issue for adb so perhaps it is a more common issue? #68
The text was updated successfully, but these errors were encountered:
Got this too. I think open-android-backup should at least not stop at this point and display an error or warning an carry on with the rest of the backup.
Device info
Manufacturer: Fairphone
Android version: Android 13
Custom ROM/rooted? No. FP4.TP29.C.0101.20240121
Model: Fairphone 4
System info
Available disk space: enough (no issue)
Operating system: Debian 12 bookworm
Backup method
Version: Open Android Backup Stable - v1.0.16 from .zip
Method: tar
Connection: Wired
Cache variant: fast
Describe the issue below.
The backup failed because SMS weren't available:
I checked the
backup-tmp/
directory and indeed the SMS files weren't there.The Open Android Backup Companion app mentioned in the Export Data section:
Some thoughts
Perhaps it is related to me using a custom SMS app Simple SMS Messenger, although the companion app has mentioned the back-upped SMS files.
I noticed the same issue mentioned in this issue for
adb
so perhaps it is a more common issue? #68The text was updated successfully, but these errors were encountered: