Skip to main content

Android requirements

Use this page for supported versions, install links, and Android-specific permissions for the Seamless mobile app. For site selection, onboarding, and day-to-day tasks, see the Mobile App hub and the topic pages in the sidebar.

Supported versions and devices​

  • Android 8.0 (API 26) or later on a phone that supports Bluetooth Low Energy (BLE).
  • Some OEMs vary BLE behavior; keep Google Play system components up to date when possible.

Install the app​

Download Seamless from Google Play.

Permissions​

What Seamless requests depends on your Android version:

  • Android 12 (API 31) through Android 12L (API 32) — BLUETOOTH_SCAN and BLUETOOTH_CONNECT for BLE discovery and sessions. Location is not requested for BLE on these versions.
  • Android 13 (API 33) and newer — the same Bluetooth permissions plus POST_NOTIFICATIONS where the system requires it (for example foreground update notifications).
  • Android 11 (API 30) and older — Android historically tied BLE scanning to location permissions. Seamless may request ACCESS_FINE_LOCATION (and on some API 29–30 devices ACCESS_BACKGROUND_LOCATION where applicable) along with legacy Bluetooth permissions. The in-app location required prompt when location services are off is shown only on API 30 and below, matching how the app gates that screen.

The Camera permission is requested when you use the lock-code scanner to identify a device. It is not required for an ordinary Bluetooth unlock.

You can review or change permissions later under Settings → Apps → Seamless → Permissions. If you are on Android 12 or newer and locks never appear, check Bluetooth and Nearby devices first—not location.

Google Wallet (optional)​

If your admin enables wallet access for you in the Seamless dashboard, you can add your Last Lock pass to Google Wallet from the app’s Profile tab when offered for your selected site. Quick Access and presentation behavior follow Google Wallet and your device—not Seamless alone.

Account and identity​

Sign-in uses SSO. Password changes, MFA, and recovery happen in the browser identity flow.