Support

Contact ZenSMS support

Use this page to include the details that help diagnose SMS, MMS, folder, and missing-message issues faster.

What to include

Include your phone model, Android version, carrier, ZenSMS version, what you expected, what actually happened, and the steps to reproduce it.

For MMS or missing-message issues

Please attach a Diagnostic Bundle. It helps identify carrier, APN, network, permission, and MMS state-machine issues specific to your device.

  1. Open ZenSMS.
  2. Go to Settings -> Diagnostics.
  3. Tap Run MMS Diagnostics if you want to see the checks before sharing.
  4. Tap Generate Debug Bundle.
  5. Tap Share Bundle.
  6. Email the bundle to support@zensms.app.

The bundle includes device/app settings, permission states, message counts, self-test results, and recent MMS send/download events. It does not include message bodies, contact names, attachment content, or phone numbers in readable form.

For SMS or MMS delivery issues

For folder and inbox organization issues

ZenSMS has system folders and custom folders. System folders organize messages automatically. Custom folders and rules are premium features.

For RCS-related missing messages

No third-party SMS app can receive RCS. If messages from some contacts disappear after switching from Samsung Messages, Google Messages, Verizon Messages+, or another RCS-capable app, deregister RCS at messages.google.com/disable-chat.

If the web form does not complete, temporarily install Google Messages, open it, keep ZenSMS as your default SMS app, turn off RCS chats inside Google Messages, wait 5-15 minutes, then test again.

Privacy note

Do not paste private message content into a support email unless you intentionally choose to share it. ZenSMS diagnostic tools are opt-in and are designed to avoid including message bodies or attachment content.

Security scans and false positives

Some mobile security apps use generic rules for apps that can send, receive, or read SMS. Those permissions are required for a default SMS replacement app, but they are also permissions that real SMS malware can abuse. That is why a generic label like AdLibrary:Generisk or trojan.adlibrary/generisk is a weak signal by itself, not the same thing as a confirmed malware finding.

A stronger warning would be multiple major vendors flagging the same build with a specific malware family, especially vendors such as Bitdefender, Google, Microsoft, Kaspersky, ESET, Sophos, Malwarebytes, or similar high-signal engines.

Current production

Build 126, v1.1.88

VirusTotal shows 2 of 68 vendors flagging this APK. The visible labels are generic, including trojan.adlibrary/generisk and AdLibrary:Generisk.

Open Build 126 report

Pending rollout

Build 127, v1.1.89

VirusTotal shows 1 of 67 vendors flagging this APK with a generic AdLibrary:Generisk label. This build is still waiting for Google acceptance and will roll out in stages because it contains sensitive MMS and routing changes.

Open Build 127 report

How ZenSMS handles AV reports

We currently submit current release builds to Avast's whitelisting program because Avast/AVG engines ship on some OEM phones and can affect users during install. Older ZenSMS versions are not submitted retroactively because every AV vendor submission takes extra setup and follow-up time.

For third-party antivirus apps, we do not chase every generic warning. We focus on current builds, Google Play distribution, OEM-impacting scanners, and transparent public scan links so users can see the signal quality directly.

Independent privacy check

Exodus Privacy's public ZenSMS report currently shows 0 trackers. Their latest indexed report can trail the newest Google Play release, so treat it as independent evidence of the app's tracker profile, not as a scan of every current rollout build.

Open Exodus Privacy report
Email support@zensms.app