Waiting for a verification code to arrive on your phone while you're sitting at your computer is one of the small frictions that adds up. On Android, Octoclip can solve this directly: the official direct-download build includes an SMS source that, after you grant the permission, reads incoming verification-code SMS on-device and auto-syncs the code to your other devices.
The SMS source is available in the official direct-download Android build only. It is not included in the Google Play version due to Google Play's SMS-permission policy. If you installed Octoclip from the Play Store, you will not see this option.
Verification codes are single-use passwords. Only enable SMS sync on devices you trust. You can revoke the SMS permission anytime in Android system settings → Apps → Octoclip → Permissions. If you'd rather not keep codes in your history, shorten clip-history retention or clear it after use. Free history covers the last 24 hours; with a one-time license, history has no time limit.
For Cloud Sync users: Cloud Sync content is end-to-end encrypted between your own devices — each clip is encrypted on-device with a key you set, and only devices configured with that same key can decrypt it. Octoclip never sees your content or your key.
How It Works on Android vs. iOS
Android and iOS handle SMS access in fundamentally different ways, so Octoclip's approach differs on each platform:
| Platform | How Octoclip gets the code | What Octoclip reads |
|---|---|---|
| Android (direct-download build) | Reads incoming verification-code SMS directly, after you grant the SMS permission | The code from the SMS, synced to other devices |
| iOS | Cannot read SMS — Apple doesn't allow it. An Apple Shortcut reads the code and copies it to the clipboard; Octoclip syncs the clipboard | The clipboard content only — never the SMS |
Both approaches are honest per-platform realities. If you're on iPhone, see How to Set Up iOS SMS Verification Code Sync.
Prerequisites
Before enabling SMS sync on Android:
- Octoclip installed from the official direct-download page (not Google Play).
- Nearby Sync or Cloud Sync configured on your Android device and your computer so codes can reach the other side.
- Android version that supports runtime permissions (Android 6.0+).
Enable SMS Verification-Code Sync
Open Octoclip and Enable the SMS Source
Open Octoclip on your Android device and navigate to the SMS or sources settings. Enable the SMS source / grant the SMS permission when Octoclip prompts you.
The exact in-app label for this setting is unconfirmed — follow the on-screen prompt in your version of the app.
Grant the SMS Permission at the System Prompt
When Android asks whether to allow Octoclip to read SMS, tap Allow. Without this permission the SMS source cannot function.
Verify the Connection
Send yourself a test SMS containing a verification-code-style number (e.g., "Your code is 123456"). Within a few seconds, the code should appear in your clip history on your other devices.
Revoke or Disable at Any Time
You remain in control:
- To temporarily turn it off: disable the SMS source inside Octoclip's settings.
- To fully remove permission: go to Android Settings → Apps → Octoclip → Permissions → SMS and set it to Deny.
After revoking, Octoclip stops reading any new SMS immediately.
Chinese OEM Devices: Extra Steps Often Required
Some Chinese Android systems — including MIUI / HyperOS (Xiaomi), ColorOS / realmeUI (OPPO / realme), EMUI / HarmonyOS (Huawei), OriginOS / Funtouch (vivo), and others — apply additional restrictions that can prevent SMS sync from working even after the permission is granted. These are Android system settings, not Octoclip-specific:
| System setting | Why it matters |
|---|---|
| SMS permission | Grant it in Settings → Apps → Octoclip → Permissions |
| Autostart / 自启动 | Allows the app to start in the background on reboot — required for background SMS detection |
| Lock in recents / 锁定后台 | Prevents the OS from killing Octoclip when you switch apps |
| Battery optimization | Disable battery optimization for Octoclip so it isn't suspended |
| Notification access | Some ROMs require notification-listener permission for certain background behaviors |
If auto-sync stops working after a restart or after switching apps, the most common culprit is autostart being disabled or battery optimization killing the background process.
For exhaustive per-ROM step-by-step instructions on SMS permissions, autostart, and battery settings for each of these systems, refer to the open-source SMS Forwarder project's documentation at github.com/pppscn/SmsForwarder. SMS Forwarder is an unaffiliated third-party project — it is cited here only because its per-ROM permission guides are thorough and widely referenced in the Android community. Its content does not imply any affiliation with Octoclip.
How Synced Codes Reach Your Computer
Once Octoclip reads the verification code from the incoming SMS, it syncs it according to your sync settings. The receiving device can run any operating system — the code lands on whichever of your devices you're using, whether that's an iPhone, iPad, Mac, or Windows PC. The Android phone is only the source; the destination isn't tied to any one platform.
- Nearby Sync — works over your local network. Read the code on Android, paste it on any of your other devices immediately, no cloud involved. Free Nearby Sync connects one device; a one-time license connects unlimited devices.
- Cloud Sync via WebDAV / S3 — works anywhere you have an internet connection. Clips are encrypted on-device with your key before upload. See how to configure S3 Cloud Sync for setup details.
For a broader look at cross-device text transfer, see How to Send Text Between Your Phone and Computer and How to Copy and Paste Between Devices.
Frequently Asked Questions
Can Octoclip read my verification codes automatically on Android?
Yes — but only under three conditions: (1) you must be using the official direct-download build, not the Google Play version; (2) you must grant the SMS permission when prompted; and (3) you can revoke it anytime in Android system settings. This is a user-enabled capability, not something that runs silently or reads all your messages.
Why doesn't SMS sync work on my Xiaomi / Huawei / OPPO phone?
Chinese Android systems often restrict background apps and SMS access beyond the standard Android permission. The most common fixes are: grant the SMS permission explicitly, enable autostart for Octoclip, lock the app in recents, and disable battery optimization for Octoclip. For detailed per-ROM steps, see the SMS Forwarder project's documentation at github.com/pppscn/SmsForwarder (unaffiliated third party, cited for its thorough per-ROM permission guides).
Is this in the Play Store version?
No. The Google Play version of Octoclip does not include the SMS source due to Google Play's SMS-permission policy. To use SMS verification-code sync, install from the official direct-download page.
Does this work on iPhone?
No — Apple does not allow apps to read SMS. On iPhone, you use an Apple Shortcut to extract the code and copy it to the clipboard; Octoclip then syncs the clipboard content. See How to Set Up iOS SMS Verification Code Sync for the full iOS setup.
Are my verification codes safe if they sync?
With Nearby Sync, codes travel over your local network between your own devices — no cloud involved. With Cloud Sync, each clip is encrypted on-device with a key you set before it leaves your phone; only your other devices configured with that same key can decrypt it. Octoclip never sees your content or your key. Even so, verification codes are credentials — only enable SMS sync on trusted devices, and shorten or clear your clip history if you'd rather not retain them.
Troubleshooting
The code doesn't appear on my computer after the SMS arrives
- Confirm Octoclip has the SMS permission: Android Settings → Apps → Octoclip → Permissions → SMS.
- Check that sync is connected: open Octoclip on both devices and verify Nearby Sync or Cloud Sync shows as active.
- On Chinese OEM devices: check autostart and battery optimization settings as described above.
- Try sending a test SMS again after confirming all permissions.
SMS sync stopped working after I restarted my phone
Autostart is likely disabled. Enable autostart for Octoclip in your system settings (path varies by ROM — check the SMS Forwarder documentation for your specific ROM for guidance).
Codes sync but appear as the full SMS text, not just the number
<!-- 待确认 -->The SMS source is designed to extract the verification code from the message. If the full message body is syncing instead, check whether there is a "verification code extraction" or similar option in the SMS source settings. The exact behavior is dependent on your app version — update to the latest direct-download build if this occurs.
Still Not Solved?
Visit the Community Forum or email support@octoclip.app with:
- Android Version and ROM — e.g., Android 14 / MIUI 15
- Octoclip Version — e.g., 1.13.0 (direct-download)
- Build Type — direct-download or Play Store
- SMS Permission Status — granted or denied
- Autostart Status — enabled or disabled
- Description — what happened vs. what you expected
Related Guides
- How to Set Up iOS SMS Verification Code Sync — the iOS path using Apple Shortcuts
- How to Send Text Between Your Phone and Computer — general cross-device text transfer, all platform pairs
- How to Copy and Paste Between Devices — the full platform-pair breakdown