Skip to content
Fyndi docs
Polski

Device requirements#

Fyndi runs on any phone with Android 8.0 or newer — the AR view (“character's eyes”) needs ARCore, i.e. Google Play Services for AR, though. When they are missing the app still starts and works normally (map, routes, finds, account), and the explanatory screen appears only after you tap the camera. This page lists exactly what the AR view requires — it is opened by the Help button on that screen.

Minimum#

Without the first two things the AR view will not open — the map, routes and finds keep working. Without the other four you cannot install or run the app itself.

What you needValueWhat for
SystemAndroid 8.0 (API 26) or newerthe minimum version the app installs and runs on
Google Play Services for AR (ARCore)the newest version from Google Playwithout them the AR view will not open; the map, routes and finds work as usual
Camerapermission to access itthe camera image is the background of the AR view (“character's eyes”)
Precise locationpermission for the precise location, not “approximate”map, routes and completing stops
Internetwhile playingroutes, stops, finds, your character and your progress come from the server
Free space on the phoneabout 100 MBthe APK alone is ~80 MB and the system needs room for the installation too

What is optional#

These elements make the game better but do not block startup — without them the app starts and works.

ElementWhat it givesWhat happens without it
Physical activity permissionsteps and walking distance from the motion sensorthe kilometre counter still works, but counts from GPS
Notification permission (Android 13 and newer)the “app is running in the background” bar and the nearby-stop notificationthe game works, it just will not remind you about a stop or show the bar
Location services turned on in the systemthe map fixes your positionwithout them the map shows the area but not your place — turn them on in your phone settings

How to check your device#

  1. System version — phone Settings → About phone (some makers: “Phone information”) → Android version. It must be 8.0 or newer.
  2. Google Play Services for AR — open Google Play and search for “Google Play Services for AR” (publisher: Google LLC). An Install or Update button means the service needs action; an Open button means it is already installed in the newest version.
  3. ARCore support — if the service still does not work after installation, check whether your phone model is on the list of devices supported by ARCore: developers.google.com/ar/devices.

What to do when the screen says AR is missing#

That screen appears after tapping the camera (the tile in the top right corner of the map or Open AR on a stop card) and says exactly what is missing: “Install Google Play Services for AR”, “Update AR Services”, “This phone does not support AR” or “Could not check AR — try again”. The order of action is always the same:

  1. Update Google Play Services for AR — Google Play → “Google Play Services for AR” → Update (and if there is no such button, Install first). You can also tap Open Google Play on the screen.
  2. Restart the phone — the AR service loads together with the system, so a plain restart can unlock it when the update arrived in the background.
  3. Tap “Check again” on the screen — once ARCore answers, the AR view opens right away.
  4. Check your model's support — the ARCore device list. If your model is not on it, the AR view will not work on this phone — the rest of the game will.

The screen leaves you two more ways out: Help opens this page in the browser and Back to the map closes it and returns to the game (the app is not shut down). If steps 1–4 did not help, describe the case in Reports and bug reports — write your phone model and Android version, it shortens the diagnosis. The most common questions are collected in Frequently asked questions.

The “Requirements” screen in the app#

From the version shipped with this package (P-184) you can check the same requirements inside the game: Account → Settings → Requirements (the row sits between “Permissions” and “Appearance and language”). The screen has two parts:

  1. This device — phone manufacturer and model, Android version (with API level), app version and screen resolution. These are the details worth attaching to a bug report.
  2. Checklist — six rows, each with a mark:
MarkWhat it means
✅ green tickall good, this thing works
⚠️ triangleit works, but worse, or something should be fixed (e.g. approximate location only)
❌ crossthis will not work until you fix it (e.g. no camera permission)
❓ question markcould not check — tap “Check again”

The rows are: Android version, AR (ARCore), location, camera, notifications and internet. A row that needs action carries a button: “Install” / “Update” (opens Google Play on the Google Play Services for AR page), “Settings” (app permissions), “Turn on” (the system location switch) or “Check again”.

After you come back from the system settings the screen recomputes the state by itself — no need to restart the app.

What Fyndi does not support#

  • Phones without ARCore — including those for which Google Play Services for AR are not released at all (among others devices without Google services, e.g. some Huawei models).
  • Systems older than Android 8.0 — the app will not install.
  • Emulators and computers — they lack the sensors and AR services, so the AR view shows “This phone does not support AR” (the map and the rest of the game work).
  • Tablets without ARCore support — a big screen does not replace sensors; the device model decides.

What happens after a correct start — the map, routes, stops and the AR view — is described on the Installation, First steps and AR view pages.


Documented for app version 0.357.3 (updated 2026-11-12).

Machine translation — the Polish version prevails.

App version: 0.357.3 API version: 0.73.0

docs.fyndi.app · 2026-11-12