Purpose Statement

This article explains how to access and configure Android device-level app settings for the First Due Mobile Response App. Proper configuration ensures accurate unit tracking, reliable notifications, and optimal performance for Fire and EMS users in the field.

Background Information

The First Due Mobile Response App relies on specific Android permissions to function correctly. These settings are initially requested during first login but can be reviewed and adjusted at any time through the Android Settings app. Correct configuration is especially important for departments utilizing unit tracking, notifications, and background updates.

Common use cases include:

• Enabling precise unit location tracking
• Ensuring notifications are received
• Allowing the app to refresh data in the background

Prerequisites:

• An Android device with the First Due app installed
• Initial login to the First Due Mobile Response App

Required Permissions

• Admin--Allows Mobile App Sign in
• Admin > Allow Offline Sign in: Allows user to sign into the Mobile App while Offline

Video

Step-by-Step Guide

1. Access the First Due App Settings in Android

• Return to the home screen, then open the Settings app.

2. Access First Due App Settings

• Select Apps, then locate and tap First Due.

3. Configure Notifications

Select Notifications to determine how and when First Due notifications are displayed.

Configure the available options as needed:

• (A) Use Allow notifications to enable or disable all First Due notifications.
• (B) Choose whether notifications use sound and vibration or are silent.
• (C) Configure where notifications appear, which may include:
  • Lock screen
  • App badge icon
  • Banner or pop-up notifications
• (D) If lock screen notifications are enabled, choose whether notification content is displayed or hidden on the lock screen.

4. Open Permissions

Return to the First Due app settings and select Permissions.

Review the permissions available for First Due. Depending on whether the device is personally owned or department-owned, specific permissions may be required, prohibited, or optional.

5. Configure Camera Access

Set Camera access to an allowed option when permitted by departmental policy.

Camera access supports features such as:

• Taking pictures
• Reading barcodes
• Using camera functionality available within First Due modules

6. Configure Location Access

Enable Location access as appropriate.

Location access supports:

• Routing
• Device location sharing within First Due

7. Configure Microphone Access

Enable Microphone access as appropriate.

Microphone access supports voice-based functionality, including voice-to-text and AI-assisted documentation.

8. Configure Notification Permission

Ensure the Notifications permission is allowed when First Due notifications should be delivered to the device.

9. Configure Phone Access

Enable the applicable Phone permission when this functionality is needed.

This allows supported phone numbers provided within First Due to use the device's phone functionality, including numbers available in areas such as Responder, Pre-Plans, or Inspections.

10. Review the Remove Permissions If App is Unused Setting

Depending on the Android operating system and version, the device may provide an option to automatically remove permissions when an app is unused.

It is recommended that this option not be enabled for First Due. If enabled, Android may reset First Due's permissions after a period of app inactivity, requiring the permissions to be granted again.

Best Practices

• Enable the device permissions required for the First Due features your department uses.
• Follow departmental policies when configuring personally owned or department-owned devices.
• Keep notifications enabled when the device is expected to receive First Due alerts.
• Review notification display settings to ensure alerts appear in the appropriate locations.
• Avoid enabling the Android option that automatically removes permissions from unused apps.
• If First Due functionality stops working as expected, verify that Android has not removed or changed the required app permissions.
• Be aware that Android settings, terminology, and available options can differ by device manufacturer and operating system version.

Troubleshooting & FAQs

Q. Why am I not receiving First Due notifications?
A. Open the Android Settings app, navigate to Apps > First Due > Notifications, and verify that notifications are allowed. Also review the notification display, sound, and vibration settings.

Q. Why isn't routing or device location sharing working?
A. Check the First Due app permissions on the Android device and confirm that the appropriate Location permission is enabled.

Q. Why can't I use the camera or scan a barcode in First Due?
A. Verify that Camera permission is enabled for First Due in the Android app settings.

Q. Why isn't voice-to-text or microphone functionality working?
A. Verify that First Due has permission to access the device's Microphone.

Q. Why did First Due lose permissions that were previously enabled?
A. Some Android versions can automatically remove permissions when an app has not been used for a period of time. Check the First Due app settings for an option to remove permissions when the app is unused and ensure it is disabled when appropriate.

Q. Why do my Android settings look different from the steps shown here?
A. The exact names, locations, and available settings can vary based on the Android version and device manufacturer.