Connection overview
See the device, network interface, carrier, signal, and connection state together.
INDEPENDENT MACOS UTILITY
4G Dongle
Manager
View and manage supported USB 4G dongles on a Mac. Bring connection state, network information, messages, and contacts into one clear desktop interface.
01
CAPABILITIES
BUILT FOR CLARITY
Turn complex device state into information you can act on.
Messages
Read and organize messages stored on the dongle when supported by the hardware and firmware.
Contacts
Keep frequently used contacts locally and reduce repetitive entry.
Honest updates
Check a public HTTPS JSON manifest for real releases—never an upgrade that does not exist.
LICENSING ROADMAP
Accounts and licensing open only after the real backend is ready.
These are roadmap items, not active services. There are no fake sign-ins, balances, or payment buttons before email delivery, Aliyun SMS, licensing, and WeChat Pay are integrated.
01NOT OPEN
Unified email account
The website and Mac app will share one users record and one user_id. Email codes will be the preferred sign-in method; the endpoint remains HTTP 503 until the sending service is connected.
02NOT OPEN
Phone sign-in and binding
Binding a phone to an email user must merge it into the current user_id, never create a second account. No SMS is sent before the Aliyun service is ready.
03COMING LATER
Two free initialization credits
Signed-in users will be able to see the remaining module-initialization credits. No fictitious balance or usage record is shown today.
04NOT OPEN
Purchase additional credits
There is no purchase, payment, or simulated checkout before WeChat Pay and the order backend are connected.
ACCOUNT & MULTI-DEVICE SYNC
Local capabilities stay free of sign-in. Cloud features wait for a real service.
Connectivity, messages, contacts, and this Mac's traffic do not require an account. Only cross-Mac totals, two free initialization credits, and future purchases need sign-in. The website and Mac app always share the same user_id.
CURRENT STATUSCONTRACT PUBLIC · SERVICE UNAVAILABLE (HTTP 503)
Local traffic
Remains in the desktop client and works without registration.
Cross-device total
After launch, Macs signed in to one account can show cycle totals.
POST /api/auth/email/requestRequest an email sign-in code
503 · SERVICE NOT OPENPOST /api/auth/email/verifyVerify email and create a session
503 · SERVICE NOT OPENPOST /api/auth/sms/requestRequest an SMS code
503 · SERVICE NOT OPENPOST /api/auth/sms/verifyVerify SMS and create a device session
503 · SERVICE NOT OPENPOST /api/auth/refreshRotate a per-device refresh token
503 · SERVICE NOT OPENPOST /api/account/phone/requestRequest phone binding while signed in
503 · SERVICE NOT OPENPOST /api/account/phone/verifyMerge the phone into the current user_id
503 · SERVICE NOT OPENPOST /api/content/readSync content read state after sign-in
503 · SERVICE NOT OPENPOST /api/usage/syncSync cumulative traffic for a device and cycle
503 · SERVICE NOT OPENMinimum sync boundary
After launch, the service will upload only the account identifier, random device ID, device name, billing cycle, counter ID, cumulative received and sent bytes, and sample time. Re-uploading the same cumulative value will not double-count or double-charge; deleting local data starts a new counter ID.
Message bodies and contacts must never be uploaded. Aliyun SMS can be called only from the server, with phone, IP, and device rate limits, CAPTCHA 2.0, anti-bombing controls, and a cost ceiling. Credentials never enter the webpage or desktop app.
Email and SMS codes are server-side hashed, valid for five minutes, single-use, and locked after five failed attempts. The website uses an HttpOnly, Secure, SameSite cookie; the Mac app uses short-lived access tokens and revocable, rotating per-device refresh tokens stored in macOS Keychain.
Anonymous read state stays in first-party browser storage and never uses an IP address or device fingerprint as identity. Cross-device read sync begins only after account sign-in is real.
DOWNLOAD / MACOS
Only a real, verified installer gets published.
The current stable version remains 0.3.0. No signed installer is public, and the update center will not trigger a fictitious upgrade.
Signed installer not yet publicNo empty link and no fake download button
- Version
- 0.3.0
- Published
- July 16, 2026
- SHA-256
- Added when the installer is published
02
REQUIREMENTS
Check the environment before using the app.
- macOS 13.0 or later
- Apple Silicon Mac
- Compatibility target includes the first-generation DJI 4G module and supported USB 4G dongles
- Device detection, network interfaces, and messaging features depend on the hardware and mobile carrier
Independent development notice
This software is an independently developed third-party tool. References to the first-generation DJI 4G module describe compatibility only. It is not an official DJI product and does not imply authorization, partnership, or endorsement by DJI or any other hardware maker. All trademarks belong to their respective owners.
FAQ
Clarify the boundaries before downloading.
Confirm hardware compatibility and back up important data before use. The software is provided as-is and may not support every device, firmware, carrier, or network environment.
Is this an official DJI product?
No. 4G Dongle Manager is an independently developed third-party tool. It is not affiliated with, authorized by, partnered with, or endorsed by DJI. This site does not use the DJI logo.
Why is there no installer download yet?
The update center publishes only real installers that are downloadable and have passed signing verification. No current file meets that threshold, so the version stays at 0.3.0 and the download area clearly says it is not yet public.
What can the app manage?
For supported hardware, the app is designed to show connection status and network information and to manage messaging and contacts. Exact capabilities depend on the device model, firmware, driver, and carrier network.
How does the desktop app check for updates?
It reads the public HTTPS manifest at /updates/4g-dongle-manager/latest.json. The JSON endpoint requires no account and returns version, release notes, minimum macOS version, and checksum.
Does it upload device data or message content?
Basic connectivity, messages, contacts, and local traffic statistics work locally without sign-in. Future multi-device statistics will sync only the account identity, random device ID, device name, cycle, counter ID, and cumulative bytes. Message bodies and contacts must never be uploaded.
Can I use cross-Mac traffic totals now?
Not yet. The website and Mac app will share one user_id, but email, SMS, token refresh, phone binding, read-state sync, and traffic sync all return explicit HTTP 503 responses. No fake tokens or aggregate data are produced.