tmo1

Thank you for reporting this. You may be hitting [issue #128](https://github.com/tmo1/sms-ie/issues/128), which has been fixed in the latest code. Please check the `sub_id`s of your messages as per the discussion...

> I had a similar issue (Pixel 4a to Pixel 7a) and the build as of https://github.com/tmo1/sms-ie/commit/76cd8b571393a10c8273080c5dcb40d4a81d279f fixed it for me—thanks for the pointer. Sure! Thanks for confirming that the...

> may be some kind of warning dialog if someone tries to enable it on A14+? Just a suggestion. This issue is discussed in the [README](https://github.com/tmo1/sms-ie#subscription-ids), but a warning dialog...

Thanks for reporting this - I have confirmed the problem. I see that others have reported similar problems and solutions with the SMS Backup and Restore app (which was an...

> Maybe it would work for everyone to set the value to -1 for all messages? I think I know what's going on: the `sub_id` field contains a "Subscription ID."...

I've pushed a commit that sets all sub_ids to `-1` upon import (the old behavior is still available via a settings toggle). Please test and report the results here.

> Another data point as this seems the most comprehensive coverage of this issue (I use SMS Backup and Restore, but came across this app while investigating the issue). This...

> it may also explain the Chomp behaviour, as the counts may be reflecting hidden duplicates with bad sub_ids You can check whether the problem is due to caching or...

> If they are being suppressed due to a missing entry in the sub db then an alternative solution might be to add that entry in the db. I'm not...

> The issue and the solution(the app converting all sub_id to -1) also makes SMS apps to show imported messages timestamps to fall on the date of import rather the...