Simple-SMS-Messenger VS OpenBoard

Check out Simple SMS Messenger[1], been using it since Signal dropped SMS support.

[1]: https://f-droid.org/en/packages/com.simplemobiletools.smsmes...

[2]: https://f-droid.org/en/packages/com.simplemobiletools.thanky...

[3]: https://github.com/SimpleMobileTools/Simple-SMS-Messenger

I accidentally my whole phone. I do have a Titanium Backup of Simple SMS Messenger, from which I can extract the conversations.db. However, when I launch the app, it replaces the conversations. I do not have an export. I would like a method of merging / importing the old conversations from the database. I'm techy and can write SQL, Python, etc. I've had a quick look at the exporter to see if I can replicate the JSON format of the exported conversations. But I thought I might ask in case anyone here has already solved this or has better advice. Cheers!

For SMS -> https://github.com/SimpleMobileTools/Simple-SMS-Messenger

SMS → Simple SMS

Simple SMS Messenger (version 5.16.1): SMS messaging and MMS messaging app for Android, send messages fast, nice UI

There is an open-source implementation of an RCS stack that these apps (QKSMS and Simple SMS) might be able to use.

I wasn't impressed with Simple SMS, the devs are a bit slow to fix issues such as the one i reported.

I take about sms app...QKSMS (https://github.com/moezbhatti/qksms) seems dead...But there is an active fork, PartisanSMS (https://github.com/wrwrabbit/Partisan-SMS), cons : it's not on f-droid...Simple SMS (https://github.com/SimpleMobileTools/Simple-SMS-Messenger/) not a huge fan of Simple apps... but on f-droid.Sad about all of this... It was a pro to migrate some people...

After reading a lengthy GitHub discussion at the Openboard repo that went into the logistical options and challenges I decided to go with the less-than-ideal option of using Helium314's Openboard fork with the proprietary Google swipe library (libjni_latinimegoogle.so) imported. I've been using it for a few weeks now and though it feels slightly different than the Gboard I'm used to, the difference has been negligible and I'll be sticking with this setup for the foreseeable future.

Pretty easy search ngl... https://github.com/openboard-team/openboard

Keyboard → OpenBoard (FlorisBoard when the v4 will be released...)

If you're willing to switch keyboards, OpenBoard has a fix for it.

You can give OpenBoard a try till florisboard is a complete app... And also... My case is also same in terms of boost... So imho the best thing you can do is used a cleaned apk of boost (basically a cleaned version of the app with all ads, trackers and analytics disabled)

OpenBoard and don't look back.

GBoard → OpenBoard (FlorisBoard when the v4 will be released)