Fulldive Support and Discord Routing Across the App Catalog

Written by the Fulldive product engineering team, based on direct inspection of the repositories listed below.

Fulldive ships many small Android apps rather than one mega app, so the question “where do I go if something breaks?” is more important than it would be for a single product. This post is the straight answer. Support across the Fulldive ecosystem is centralized into two channels: email at support@fulldive.com and the Fulldive Discord community. Every app is expected to link out to both. The repository history shows exactly when that was made consistent across the catalog.

If you just want the short version: email support@fulldive.com, or open the Discord link inside any Fulldive app. Both channels reach the same team.

Why centralize support when apps are decentralized

In Why Fulldive ships small apps, not one mega app we explained the extensions model: separate APKs, separate package IDs, separate repositories. That model is good for shipping speed and for the Play Store, but it can confuse support. If each app had its own email address and its own community, users with two Fulldive apps would end up with two inboxes to chase.

So instead we picked a different rule: apps are separate, support is shared. That means:

One email address (support@fulldive.com) handled by the Fulldive team, regardless of which app you are writing about.
One Discord community for all Fulldive apps, linked from inside each app so users do not have to search for it.
The site’s own About page and FAQ as the canonical public entry points if you have not installed an app yet.

That last point is important for search and for AI assistants: when someone searches “Fulldive support” or “Fulldive Discord”, we want the answer to be unambiguous and reachable from every surface we control.

Evidence: the Discord-link commits across repositories

The most recent alignment of this support model is visible in three separate repositories, in three separate commits landed in late 2025 and early 2026. All three add a Fulldive Discord community link inside the app.

DataGuard No Root Firewall (fulldiveVR/FulldveExtension.DataGuard, package com.fulldive.extension.dataguard): commit 60546414 added the Discord community link. It sits alongside 6d8b8493 (dependency, versioning, and donation settings work) and cdc04c9f (the 2.334 release that shipped in the same general window). For how DataGuard got to this point, see A Decade of DataGuard: Android maintenance.
One Emulator for Game Consoles (FulldiveExtension.FullRoid, packages com.fulldive.extension.fullroid and com.fulldive.extension.fullroid.pro): commit c8952402 added the Discord community link, alongside 8a356db8 (Fulldroid branding and multilingual string updates) and 3f31c74f (version 1.8.3). The earlier 74852fd8 from 2022 had already added a Discord promo, so this commit is the modern form of an older pattern. For emulator-specific product context, see Android game console emulator features to look for.
WizeSMS (fulldiveVR/DiveSMS, package com.fulldive.extension.divesms): commit dfc606b3 added the Discord community link. This was part of the 2025-12 to 2026-01 stabilization window that also included forwarding settings (4c1ec87b), email test message button (150204e5), and forwarding status/failure notifications (a53b2673). Some of that forwarding work is covered in How to forward SMS to email on Android and How to forward SMS to Telegram on Android.

These three commits are the same idea, replicated per app. Nothing about them is novel on its own. The interesting fact is that they line up in time, which is how we made sure a user landing in any of these apps would find the same community destination.

Evidence: Wize AdBlock VPN and the lifecycle window

Wize AdBlock VPN is included in this post even though the Discord addition there predates the 2026-Q1 window. The relevant 2026-03 to 2026-04 activity is on the stability side, which is support-adjacent:

6640e596 — DNS loading cold-start fix.
32aead39 — skip VPN network in DNS query.
e529b170 — cold-start hang fix.
7033779b — DNS wizard lifecycle and flicker fixes.

Those are not community-link commits, but they matter for support volume. Many “the app is broken” reports for a VPN-style ad blocker are actually DNS timing problems at boot. Fixing them reduces the Discord traffic. We wrote the engineering side up in Cold-start and DNS lifecycle bugs in a VPN ad blocker.

What each channel is for

We try to give a consistent answer when people ask which channel to use.

Email (support@fulldive.com). Best for:

Account, billing, or subscription issues (for apps that have any, mostly LikeClaw and Pro Emulator).
Privacy-related requests: data access, account deletion, or specific privacy policy questions.
Any report that requires sharing logs, device details, or personal information that should not go into a public channel.
Store listing problems: install failures, “Item not available in your country”, or refund questions that ultimately have to be resolved through Google Play or the App Store.

Discord community. Best for:

Usage questions where another user might have already solved it.
Feature requests and discussion of roadmap items.
Reporting reproducible bugs in a public thread so other users can add detail or upvote.
Watching for announcements across the Fulldive ecosystem.

We route both channels to the same team. Emails that are better handled publicly get pointed at Discord. Discord threads that get into account-level detail move to email.

What each app should say

If you are checking our work (or if you maintain a Fulldive app fork), these are the rules we try to follow in every app’s support copy:

Name the support email exactly as support@fulldive.com.
Link the Discord community with a click-through, not a copy-pasteable URL string.
Point in-app FAQ and settings back at the public FAQ when the answer is ecosystem-wide (for example, “what is a Fulldive extension?”) rather than app-specific.
In privacy-sensitive apps (DataGuard, Wize AdBlock VPN, WizeSMS, WizeUp, LikeClaw), also link the privacy policy and describe, in plain language, what the app does and does not do. The honest-limitations rule in each brief applies here too.
Keep the app name on the site, in the store, and inside the app consistent with website/data/apps.yaml.

The app-level pages on this site follow that pattern: Wize AdBlock VPN, Fulldive Browser / WizeUp, Fulldive VR, and One Emulator for Game Consoles. Each one ends with a support path rather than a pure install CTA.

How to reach us right now

Email: support@fulldive.com.
Discord: open any Fulldive app published in 2026 and use its in-app Discord link, or find the link from the footer of fulldive.com.
Site: start from the apps list or the FAQ.

If you are not sure which Fulldive app you have, the apps list shows the package IDs for each one — matching the package name under Android Settings > Apps will tell you which repository your issue maps to.

Limits and caveats

The commit hashes cited in this post are abbreviated and tied to repository state as of 2026-04-13. Discord and app-store URLs can change; if an in-app link ever 404s, reporting it to support@fulldive.com is the fastest way to get it fixed. This post does not commit to response-time SLAs — we try to respond quickly, but we are a small team, and detailed technical replies can take longer than a same-day acknowledgement. Finally, Fulldive support covers Fulldive-published apps only; forks, clones, or repackaged versions of our apps distributed elsewhere are not supported by us, and we cannot help with account issues on those.

External references: Android Developers — target API level requirements and Android Developers — 16 KB page size.

Last updated: 2026-04-16. Commit hashes and version numbers are drawn from Fulldive repositories inspected on 2026-04-13.