Existing conversion support is flaky #1
Assignees
Labels
Comments
ghost
assigned 
t413
added a commit
that referenced
this issue
Oct 11, 2012
This is a huge change! Provide a list of files to import,
it autodetectes each's format, merges the results,
sorts them, and exports them to either XML or mmssms.db (sqlite).
Use it just like cp:
python sms_db_importer.py sms-iOS-5.db gv.csv android.xml out.xml
Now imports:
- iOS 5 databases, iMessages and all
- iOS 6 databases (better architecture, actually)
- Android XML from the com.riteshsahu.SMSBackupRestore app.
- CSV of google voice data
Now saves:
- XML format for use with SMSBackupRestore
- mmssms.db Android sms database format
Requires adb root access.
Why use this option? WAY faster
and much better database performance.
SMSBackupRestore is great, but it doesn't handle
tens of thousands of messages.
Fixes #1 where existing threads were not properly handled.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When populating a mmssms.db that already has data, existing conversations are not updated, they're added anew.
Fix:
Either populate the convoMap object (which is a lookup table to go from a csv entry contactId to a thread id) with threads that already exist in the mmssms.db (very tricky) or use the existing table
canonical_addressesfor this. (less tricky).The text was updated successfully, but these errors were encountered: