Solution 1: set offline mode (to ensure not receiving sms while doing this) Solution 2: transaction? - should definately be used
Solution 1: automatic check interval (daemon?) Personal note: I would like to trigger it as soon as I see a problematic message/let it happen automatically for me) Solution 2: on sms send --> (.js) --> check database - may be really slow (needs to be tested)--> is modifying the sqlite database from js possible? --> can the system be notified? is there already such a solution? (afaik there is a solution to send sms from commandline) --> could just check the last entry and fix it if it failed - how to determine if sms sending really failed or who is the contact to update the entryPossible solution for the "who is the contact the sms was sent to": set the field to an identifier nobody would ever use on a real name (e.g.: "_smsSendCorruption") where all a utility could read out all those fields containing that text and present the user the option to choose the right one (on device))
--> is modifying the sqlite database from js possible? --> can the system be notified? is there already such a solution? (afaik there is a solution to send sms from commandline) --> could just check the last entry and fix it if it failed - how to determine if sms sending really failed or who is the contact to update the entry
Possible solution for the "who is the contact the sms was sent to": set the field to an identifier nobody would ever use on a real name (e.g.: "_smsSendCorruption") where all a utility could read out all those fields containing that text and present the user the option to choose the right one (on device))