App Permissions

What each permission supports, what stops working without it and how to grant what was denied before.

The App Permissions screen lists everything the app may request and shows the current status of each permission. It is the place to grant in one go whatever was left pending during the initial setup.

This screen is worth a closer look, because most cases of "the app stopped recording on its own" are solved here, by reviewing the permissions.
Each permission is used only by the features described under it.

  1. Start with location

    Location and Use precise location are the two most important permissions, and they follow an order: the foreground one has to exist before the system accepts the background request.

    The background permission is what supports recording continuing with the screen off, saving the parking spot after you have already left the car and, on Android 14 and later, the very start of the service that keeps the recording alive.

    Choose the option that grants access all the time, not the one for use only with the app open. When the app is not in use, no location is collected.

  2. Turn precise location on

    Use precise location is a separate switch. Denying only that leaves the app with an approximate position, accurate to within hundreds of meters.

    The consequences go beyond precision: the route comes out distorted, the distance covered is wrong and the parking spot points at the next block.

  3. Allow Bluetooth

    Nearby devices is the permission that makes it possible to scan for and connect the adapter. Without it, the scan on the Connection screen returns no results.

    On Android 11 and earlier, the Bluetooth scan also requires the location permission, by decision of the operating system itself.

  4. Turn notifications on

    Notifications deliver reminders, maintenance warnings, vehicle fault alerts and the parking alarm.

    On Android it is also a prerequisite of the foreground service: the persistent notification is what keeps the service alive while a trip is being recorded. Denying the permission leads the system to end the service, and the recording stops with it.

  5. Grant motion access

    The motion and physical activity permission lets the app tell driving apart from walking or riding public transport.

    With it, the app wakes up and reconnects to the adapter only when you are in the car, rather than at every movement. That saves battery and avoids questions about trips where you are a passenger.

    It also works as an alternative for anyone without the car stereo paired: the system tells the app when it works out that a vehicle has started moving, so the trip is not lost when the adapter is slow to answer.

  6. Turn battery optimization off

    The Battery optimization option, on Android, keeps the system from limiting background work.

    It is the most common cause of trips cut in half on phones from certain manufacturers, and the effect is not limited to the trip: with the app restricted, sensor collection, route recording and the driving score all lose precision.

    If you use battery saver mode, add the app to the exceptions list.

  7. Grant the rest as you need them

    Camera serves the dashcam and the photo of the parking spot. Microphone serves only to record audio with the dashcam; without it, the video has no sound. USB adapter serves the wired adapter on Android, and the system asks for the authorization once per adapter, with the use-by-default option making it permanent.

    None of the three is needed for the app to work.


← All guidesIn the FAQ: Adapters and connection →