tmo1
tmo1
> I did not Good - it should generally not be set. As per the README, please try to construct a minimal reproducible example, and provide a logcat (as well...
This was recently discussed [here](https://github.com/tmo1/sms-ie/issues/7#issuecomment-2073650929), and may be implemented at some point.
The behavior you describe, as well as the solution you arrived at of wiping messages before restoring, [is discussed in the README](https://github.com/tmo1/sms-ie#limitations). The reason the app does not attempt to...
I'm going to leave this issue open, as a place for discussion of the feasibility and desirability of implementing some sort of deduplication, but I don't currently have any plans...
Noted. I'm not sure I plan to implement deduplication in SMS I/E, but I'll consider it.
Not at present - sorry. If I do implement something, I'll try to remember to post it here.
> could you implement a wipe for call.logs ? [Android has call log wiping built in](https://support.google.com/phoneapp/answer/2811854?hl=en#zippy=%2Cdelete-your-entire-call-history).
> It can be done programmatically as other apps do it. Would be nice to have it in the app. Maybe even as a prompt option when importing calls. I'm...
I'm happy to consider adding VVM support to SMS I/E, although I myself don't use VVM, so I don't know much about i. I won't be able to implement it...
It looks as though your original Android message database has multiple MMS messages linked to the same binary file attachment, and Android's Zip libraries are throwing an exception when SMS...