A calmer way to get connected.

Get started

1. Download the Android 12+ local APK and macOS 14+ DMG from Downloads.
2. Open the DMG and drag AndroidSync to Applications. Read the Mac signing notice below before opening this local build.
3. Put both devices on the same private Wi-Fi network. Open Devices on Mac to show an invitation.
4. On Android, scan the invitation QR code. Pair each additional Mac separately.
5. In Android Setup, enable notification access, clipboard sharing or optional capabilities only when you need them.

Developer ID signing and Apple notarization

AndroidSync 1.1.2 is signed with Muhammad Sanaullah's Apple Developer ID Application identity. The exported app is notarized by Apple and its stapled ticket has been validated.

Build your own APK or Mac app

For additional control, we recommend reviewing the source and compiling your own APK or Mac app. This does not guarantee security, and a personal signing key may prevent updating an installation signed with a different key.

The README includes step-by-step Apple Developer signing and notarization instructions and Android build instructions. Keep your credentials outside the source tree. Signing a personal copy does not change the license or ownership.

Android release signing

The Full APK uses the AndroidSync release key. Its package and certificate were recorded as verified through Google's Android developer verification. Google does not sign this APK or certify its contents. Older debug-signed installations require a fresh installation; save important data first.

Clipboard on Android

Android does not provide unrestricted background clipboard reading to ordinary apps. AndroidSync captures automatically while it is visible and focused. From another Android app, use Share to Android Sync, the persistent notification action, Quick Settings, or an in-app capture. Mac clipboard changes sync automatically while sharing is enabled.

Notifications and replies

Enable Android's Notification access for Android Sync and macOS notification permission for native banners. The Mac inbox works even when native banners are disabled. Replies are available only when a current Android notification exposes a free-form reply action. A reply accepted by Android is not proof that the messaging provider delivered it.

Files and photos

Use Files on either app to send files. The Mac can browse Android shared storage when the private Android build has All files access. Photo on Mac browses Android MediaStore photos and videos. Received files go to Downloads / Android Sync by default; you can choose another Mac folder.

Mirroring and remote control

Every new screen-mirroring session shows Android's capture consent dialog. Remote touch control requires the private Android build, Accessibility permission, and a separate grant for the connected Mac. Secure fields and protected content remain unavailable.

Calls and messages

Carrier SMS, contacts, call history and dialing require optional permissions in the private Android build. Answer and End were verified with a Galaxy S25 Ultra and Mac mini. Call audio stays on the phone. MMS and RCS are not supported.

If devices do not connect

• Check that both devices are on the same private network and that guest-network isolation is off.
• Allow the Mac app through the local firewall and permit Local Network access.
• Try invitation text or a manual local address if discovery is blocked.
• On Android, review battery restrictions and the persistent connection notification.
• Reconnect after changing network; a different local address may need to be entered.

Which file transfer mode should I use?

Keep encrypted Wi-Fi enabled for private transfers. Version 1.1 streams file bytes over TLS, saves progress about every 8 MiB and checks SHA-256 before making received files available. Interrupted transfers can resume from saved progress.

The optional Insecure transfer (faster) setting sends file bytes over unencrypted local TCP. Anyone who can observe that network can read the files. Offers and transfer tokens still travel over TLS, and hashes check integrity, but neither makes the file bytes private. The setting syncs between paired devices and is remembered after restart.

Turning the option off cancels active unencrypted batches. Start them again to use TLS. A batch does not silently change transport while running. If unencrypted transfers cannot connect, turn the option off and retry. Actual speed depends on Wi-Fi, storage and both devices; this option is not guaranteed to be faster.

Why does a large gallery selection take time to start?

Android prepares and hashes the selected files before offering them. Large photo and video batches can take time even with the new binary transport.

What has been verified?

The GitHub release notes list the build checks completed for this package and its testing limits. Installation and build documentation are in the repository README.