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
Creates almost 6GB file, but doesn't seem to take very long to complete the "Restore".
First tried this when upgrading from A10 to A14 and noticed my messaging app was completely blank and I couldn't even send/receive new messages. Went back to my original A10 phone and tried to restore the backup, but after the 1ish minute restore process it doesn't change anything (should take much longer).
Going to View the log just brings up an empty window saying "The filtered list is empty"
The text was updated successfully, but these errors were encountered:
Should also add that while it "restores" the files, they are all essentially empty. Over 8000 images that show file sizes, but none can be opened once restored and after rebooting they are all deleted. The mmssms.db that the backup creates is also void of data, only has the structure. The size should also be in the mb.
Of course this wouldn't have been such a huge issue if my dumb self didn't empty the message storage on the wrong phone - leaving this as the only backup.
Description
A clear and concise description of what the bug is.
Steps To Reproduce
Expected behavior
All messages should be restored
Screenshots
Only if there's no clear logs, add screenshots to help explain your problem.
System Information(please complete the following information):
Creates almost 6GB file, but doesn't seem to take very long to complete the "Restore".
First tried this when upgrading from A10 to A14 and noticed my messaging app was completely blank and I couldn't even send/receive new messages. Went back to my original A10 phone and tried to restore the backup, but after the 1ish minute restore process it doesn't change anything (should take much longer).
Going to View the log just brings up an empty window saying "The filtered list is empty"
The text was updated successfully, but these errors were encountered: