Fossify Messages: A GPL-3.0 Fork With No Ads
Fossify Messages review: why RCS typing indicators and read receipts stay missing, plus group MMS APN fixes and Google-free SMS/MMS backups.
App summary
- App
- Fossify Messages
- Developer
- Fossify (FossifyOrg) — community-maintained fork of the Simple Mobile Tools 'Simple SMS Messenger'
- License
- GPL-3.0
- Version
- unknown
- Size
- unknown
- Price
- Free — fully open source. No paid tiers, no subscription, no ads, no in-app purchases.
Fossify Messages vs RCS: Why Typing Indicators and Read Receipts Still Won’t Appear
If you installed Fossify Messages expecting the three-dot typing bubble and a small “Read” label under your last text, you are going to be disappointed, and no amount of digging through settings will fix it. Fossify Messages is an SMS and MMS client. Its job is to hand a message to your carrier and show you what comes back. RCS — the Rich Communication Services protocol behind typing indicators, read receipts, high-resolution photos, and end-to-end encrypted chat in Google Messages — is not part of its feature set.
That is not a missing toggle. RCS chat features depend on an RCS-capable client negotiating with a carrier, or with the Google-hosted backend most carriers rely on, and on both people in the conversation supporting it. Google Messages ships that client. Fossify does not. So when you text a friend who uses Google Messages, your message leaves as a plain SMS, their reply arrives as a plain SMS, and neither side gets the chat-style interface. The other person may see a normal text bubble on their end while you see a green one on yours. Nothing is broken; you are simply not on the same protocol.
It is also not an iMessage or Signal replacement, and it is worth being blunt about why. SMS and MMS are not end-to-end encrypted. They cross the carrier’s network in a form the carrier can read, log, retain, and hand over on request. Signal dropped SMS support in 2022 precisely because mixing encrypted and unencrypted conversations inside one app gave people a false sense of cover. If end-to-end encryption is a requirement rather than a nice-to-have, Fossify is the wrong tool, and no configuration makes it the right one.
If you want to know whether RCS is on the roadmap, read the project’s own channels — fossify.org and the FossifyOrg/Messages repository on GitHub — instead of assuming a future update will add it. A community fork moves at the pace of its contributors, and a messaging protocol is a large piece of work with carrier certification attached to it. Check before you plan around it.
Fossify Messages Group MMS Not Working? Check APN, Mobile Data, and SMS Fallback
Group texting is where carrier messaging falls apart, and Fossify inherits every one of those failure modes. MMS is not a data service in the way a chat app is. It is a carrier feature with its own gateway, its own size limits, and its own rules about whether a group conversation stays a group conversation or gets split into separate one-to-one threads. Fossify’s stated position is that group and picture quality depends on the mobile network, and that is the honest answer rather than a dodge.
Before blaming the app, verify three things. First, Fossify has to hold the default SMS role. On modern Android, only the default SMS app can write to the message database, so a non-default install will look broken in ways that have nothing to do with the app’s code. Second, mobile data must be on. MMS is fetched over the carrier’s data connection even when you are sitting on Wi-Fi, and a phone with data switched off will show a download spinner that never resolves. Third, check the APN. The MMSC URL, MMS proxy, and MMS port come from your carrier, and a wrong or missing entry breaks picture messaging while leaving plain SMS working perfectly — which is exactly the pattern that makes people think the app is at fault.
On a dual-SIM phone, add a fourth check: per-SIM MMS configuration. Fossify supports per-SIM handling, but the carrier still has to provision MMS on the SIM you are sending from. Plenty of people run a cheap data SIM alongside a talk SIM and then wonder why pictures fail; the MMS APN is attached to the wrong subscription. Send a test group message from each SIM, and send a plain SMS to the same people, so you can tell whether the failure is group-specific or MMS-wide.
If messages still will not go through, the remaining variables sit outside the app. Pull your carrier’s official MMS settings, compare them against what is stored on the device, and check the Fossify site for notes on the current build. No SMS app can bypass a carrier’s MMS limits, and none can persuade a gateway to accept a file it is configured to reject.
One persistent myth deserves a correction here: that an app without an internet permission cannot handle MMS. MMS delivery runs through the carrier’s MMS gateway over mobile data, and behavior depends on the carrier and the system messaging stack rather than on whether the app ships an analytics endpoint. The privacy point that actually matters with Fossify is simpler — there is no account, no cloud sync, and no analytics service in its stated design, and messages live locally on the device.
Moving to Fossify Messages: Back Up SMS/MMS and Restore Without Google Cloud
Switching messaging apps is the part nobody warns you about. Fossify backs up and restores SMS and MMS messages to a local file. That is the entire story: a file, on your device or wherever you copy it. There is no Fossify account, no cloud sync, and no way to pull down the cloud backup Google Messages keeps on your behalf. If you have years of threads sitting in Google’s backup and you want them inside Fossify, be prepared for that to be the hard part of the migration.
The order of operations matters more than people expect. Export from your old app first, while it still holds the default SMS role and can read the message database. Then install Fossify, assign it the default SMS role, and import. Do it the other way around and the old app may lose access to the very data you were about to save, which turns a routine switch into a data loss story.
Expect some friction around formats. Fossify’s restore works with its own backup file; a backup produced by a different app is not guaranteed to import cleanly, and the two sides have to agree on structure before anything else works. Check the official site for the current backup format and any documented limits before you wipe a phone or hand it to a family member.
MMS restore is the flakier half of the job. Text messages are small rows in a database. MMS is a container with media parts attached, and restoring them depends on what the backup file actually captured and on how the carrier handles those parts on the way back. Some MMS content can come back as a placeholder or a missing attachment, which is a limitation of the format as much as of the app.
Because there is no cloud service in the design, keep a copy of the backup off the device — a computer, an SD card, a home server. If the phone is lost, stolen, or factory reset, the backup goes with it otherwise. That is the trade you make for not having an account: nobody else holds your data, and nobody else can restore it for you.
Set Fossify Messages as Default on Android 14/15: Roles, Notifications, and Dual-SIM
Android 14 and 15 treat the default SMS app as a role rather than a preference. Go to Settings > Apps > Default apps > SMS app and pick Fossify Messages. Some manufacturer skins bury the same screen under Special access or a “Default applications” entry, and Samsung and Xiaomi both move it around between versions. After assigning it, send yourself a message from another phone, confirm it arrives, then reply and confirm the reply actually leaves. Receiving and sending are separate code paths, and one can work while the other does not.
Notifications are a separate permission on Android 13 and later. Grant it, or the app will receive messages silently and you will conclude it is broken. Once notifications are flowing, test quick reply from the notification shade — it is one of the features Fossify lists, and it is the one you will use most often in practice. If quick reply does nothing, the notification permission or the role assignment is usually the culprit.
Dual-SIM setup deserves ten minutes before you trust the app with anything important. Set the default SIM for SMS, then verify per-SIM sending by choosing the other SIM on an individual thread. Scheduled, delayed sending is worth testing once as well: queue a message a few minutes out and confirm it fires. A scheduled message that silently fails is worse than no scheduled message at all, particularly if you were using it to remember something.
If behavior changes after an update, compare builds before you assume a regression. Fossify ships through F-Droid and GitHub releases, and release notes are where fixes and known issues get called out. Check the official site or the GitHub releases page rather than guessing from a single bad afternoon.
Pricing & Plans
Fossify Messages costs nothing. There is one tier, and it is the whole app:
- Free — $0. Full feature set, no ads, no in-app purchases, no subscription, no “pro” unlock that turns off a nag screen.
The GPL-3.0 license means you can read the source, build it yourself, and fork it if the project ever stalls. That is a real form of insurance rather than a slogan: the code cannot be pulled out from under you the way a proprietary app can when a company changes hands or shuts down.
What you actually pay is your carrier’s SMS and MMS bill, plus mobile data for MMS. That is the cost model, and it is worth checking. If your plan charges per MMS or caps picture messages, that is the number that matters, not the app’s price tag. Someone sending a dozen group photos a week on a metered plan is paying more for messaging than someone on an unlimited plan pays for anything.
There is no paid support tier and no help desk. Community-maintained means community support: GitHub issues, release notes, and whatever documentation the project publishes. For a messaging app that is mostly a fair trade, because the failure modes are usually carrier-side and the answers are already written down somewhere.
Who Should Use Fossify Messages
Fossify Messages fits a specific kind of Android user: someone who still relies on SMS for the boring, essential traffic — bank alerts, delivery notifications, two-factor codes, the dentist’s office — and wants that traffic handled by an app with no ads and no account attached.
- People who want a plain SMS app with no advertising. The stock app on a budget phone is often a carrier-branded client with promotional messages baked in. Fossify is the opposite of that.
- Privacy-minded users who want to verify claims rather than trust them. The source is public under GPL-3.0, and builds are published on F-Droid and GitHub, so the “no trackers” claim can be checked instead of taken on faith.
- Dual-SIM owners who need per-SIM sending. Two numbers, two carriers, one app, and a clear choice of which SIM a given message leaves from.
- Anyone who needs scheduled sends. A reminder text to a family member, a message to a client in another time zone, a note you want to arrive tomorrow morning rather than tonight.
- Users on de-Googled phones or AOSP builds. If Google Messages is not installed and you do not want it, you need an SMS client that works without Google services.
Search, blocking, archiving, and conversation management are all present and behave the way you would expect. None of it is novel. The point is that the basics are done without an advertising SDK riding along.
Who Should Skip Fossify Messages
This app is not for everyone, and the mismatch is usually about protocol rather than quality. Be honest with yourself about which camp you are in before you spend an evening migrating threads.
- Users who need RCS typing indicators, read receipts, and high-quality media. Google Messages is the practical answer, and it is preinstalled on most Android devices.
- iPhone or iMessage users expecting blue-bubble behavior. Fossify will never produce a blue bubble, and the person on the other end will see a green one.
- People who want end-to-end encrypted messaging by default. Signal is the right choice, with the caveat that both parties have to use it.
- Users who need cloud sync across devices or web messaging. There is no account and no browser client, so your threads live on one phone.
- Samsung users expecting One UI messaging features such as conversation categories and the Samsung-specific extras. Those live in Samsung Messages, not here.
- Power users who want automation and advanced rules. Scheduled send and blocking are there; scripted workflows and conditional routing are not.
Comparison with Alternatives
The honest comparison is less about features than about which protocol you are willing to give up.
| Feature | Fossify Messages | Google Messages | Textra SMS | Signal |
|---|---|---|---|---|
| Price | Free ($0) | Free | Free with ads; paid unlock removes them | Free |
| License | GPL-3.0, open source | Proprietary | Proprietary | Open source (GPL-3.0) |
| RCS chat features | No | Yes, with carrier/Google support | No | No (own protocol instead) |
| End-to-end encryption | No | Yes, for RCS chats | No | Yes, by default |
| Sends plain SMS | Yes | Yes | Yes | No (SMS support removed) |
| Local backup file | Yes | Limited | Yes | Yes (app-specific) |
| Cloud backup restore | No | Yes, via Google account | No | No |
| Dual-SIM per-SIM handling | Yes | Yes | Yes | Yes |
| Ads and trackers | None | None | Ads in free version | None |
Google Messages is the default answer for most people, and it is a good one: RCS with end-to-end encryption between Google Messages users, cloud backup tied to your Google account, and no ads. The cost is Google’s ecosystem, which is precisely what Fossify’s users are trying to step away from.
Textra SMS is the choice for someone who wants deep visual customization and a polished proprietary interface, and who does not mind ads or a paid unlock in the free version. It is also SMS/MMS only, so it solves a different problem than Google Messages does.
Signal is the answer when encryption matters more than reach. It dropped SMS support, so both people have to be on Signal. For a family group that is fine. For your bank’s two-factor codes it is irrelevant, because those arrive as SMS no matter what you install.
QKSMS is the ancestor of this codebase, and it has been effectively unmaintained for years. Choose it only if you specifically want the original project. Fossify Messages exists because the Simple Mobile Tools suite was sold to ZipoApps in early 2024, and the community fork is the maintained path forward — not a rebrand of the same abandoned app.
Verdict
Fossify Messages is a credible daily SMS and MMS app for privacy-minded Android users who accept carrier-bound, unencrypted messaging. It does the boring work well: threads, search, blocking, archiving, scheduled sends, dual-SIM handling, quick reply, and a local backup file you control. It asks nothing of you — no account, no ads, no subscription, no analytics — and its GPL-3.0 license means the claims can be checked rather than believed.
It is not a Google Messages substitute, and it is certainly not a Signal substitute. No RCS means no typing indicators, no read receipts, and no encrypted chat, and that gap is structural rather than temporary. If those features are why you message people, install Google Messages and stop reading. If end-to-end encryption is the requirement, install Signal and accept that both parties have to join you.
The right way to think about it is as a replacement for the stock SMS app, not as a replacement for a messenger. Banks, delivery drivers, appointment reminders, and two-factor codes still arrive over SMS, and that traffic deserves an app that is not quietly profiling you. Fossify Messages fills that slot cleanly, and it does so without pretending to be something it is not.
Pros
- Fully open source (GPL-3.0) — code can be audited, forked, and self-built
- No advertisements, no analytics SDKs, and no paid unlocks; the entire feature set is free
- Actively maintained as a community fork after the original Simple Mobile Tools apps were sold to ZipoApps
- Distributed on F-Droid as well as via GitHub releases, so you can install it without the Play Store
Cons
- No RCS support — it is an SMS/MMS client only, unlike Google Messages
- Fewer cloud/multi-device or web-client features than some proprietary messengers
- Relies on the carrier for MMS, so group/picture messaging quality depends on the mobile network
- Smaller development team than commercial messaging apps; feature roadmap is community-driven
The link goes straight to Fossify (FossifyOrg) — community-maintained fork of the Simple Mobile Tools 'Simple SMS Messenger'. We do not host app files.
Frequently asked questions
Is Fossify Messages free?
The recorded pricing model is Free — fully open source. No paid tiers, no subscription, no ads, no in-app purchases..
What license does it use?
It is listed under GPL-3.0.
Where can I download the official version?
The official link points to https://github.com/FossifyOrg/Messages.