If the application has configured Global Navigation Satellite System (GNSS) to track position, any sleep type might be interrupted by GNSS activity.
The application must react to a sleep interrupt notification immediately by activating hardware components and making resources available for the modem. A delay in reacting to the sleep interrupt notification impacts the modem's and GNSS's performance. When sleep is resumed after GNSS activity, the remaining sleep time is notified.
A delay in the application’s reaction to a sleep interrupt notification is inevitable, and even a small delay affects the GNSS performance. Using GNSS and controlling resources according to sleeps must be considered case by case to determine if it offers power savings.
The following notification example indicates that the modem sleeps due to Extended Discontinuous Reception (eDRX):
%XMODEMSLEEP: 2,120000The following notification example indicates that GNSS activity interrupts the sleep:
%XMODEMSLEEP: 5,0%XMODEMSLEEP: 6,70000