FrontlineSync Network and Power Management

Introduction

Android's power management and wi-fi policy features affect the FrontlineSync experience. There's a distinct difference in the behavior of FrontlineSync when a user is actively using their android device and when the device is left idle. In the first instance, FrontlineSync functions normally and syncs with FrontlineCloud. However, in the second instance, the sync can fail. This can be noted by the users if there are obvious delays in the sending of messages or there's an error message on the dashboard reading 'Sync Failed' after the device was left idle for a while.

Technical Information

Android devices are designed to conserve battery unless a user is interacting with the device. This is done to increase battery backup time for the user. When the device screen light goes off, the CPU goes into sleep mode.

This is why FrontlineSync sometimes stops syncing with FrontlineCloud after a few minutes of the Android device being idle.

The Android device's idle mode restricts network access.

Connection to Wi-Fi and mobile data is lost after the android device has been left idle for a few minutes because the device goes into sleep mode to reduce over-utilization of CPU.

The same issue is experienced when using Power Management apps.

Solution

The solution to this problem is to simply change your Android device Wi-Fi policy and disable power management.

Below are steps and high-level screenshots (specific to the device manufacturer and Android version running) on how to disable power management and change your Wi-Fi policy to always allow connection during sleep mode. Please note that the flow of instructions depends on your original equipment manufacturer.

Power Management: Settings > Power Saving Management > On

Wi-Fi Policy: Settings > Wireless and Networks/Wi-Fi > Advanced > Wi-Fi sleep policy/Keep Wi-Fi on during sleep > Always

Screenshot_20180125-163151.png .    Screenshot_20180125-163214.png 

Screenshot_20180125-163243.png            Screenshot_20180125-163252.png

 Screenshot_20180125-163301.png

 

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.