You are evaluating GPS tracking software for your security team. The sales pitch sounds good, live guard positions, faster response coordination, patrol verification, incident evidence. Then your operations manager asks the question that kills half of these conversations:
"If every guard runs this app for 12 hours a day, will their phones be dead by mid-shift?"
It is a fair question. Early GPS tracking systems were notorious for draining batteries in hours, burning through mobile data, and making phones run hot. Guards would switch off the app to save battery, which defeated the entire purpose. Some security companies abandoned GPS tracking altogether because of it.
We decided to answer this question with real data instead of marketing promises. We connected two Android devices to diagnostic tools, ran MyProtektor in active duty mode for extended periods, and measured what the app actually consumed. We then combined those baseline measurements with typical shift activity to estimate realistic per-shift ranges.
This article shares those results.
Why This Question Matters More in Southern Africa
Battery drain is not just an inconvenience in South Africa, it is an operational risk.
Load shedding removes charging access unpredictably. A guard whose phone dies at 3 AM during Stage 4 cannot simply plug in somewhere. If the tracking app consumed 30% of the battery before midnight, that guard is now invisible to the control room during the highest-risk hours of the shift.
Data costs are real. Many security companies issue guards prepaid SIM cards with limited data bundles. If a tracking app consumes 500 MB per shift, the monthly data cost per guard becomes a line item that finance notices. For a team of 50 guards, that adds up fast.
Guards use personal or budget devices. Not every company can afford to issue Samsung flagships. Many guards carry budget Android phones with 4 000–5 000 mAh batteries. If the app drains 25% per shift on a flagship, it drains 40% on a budget device. That is the difference between a phone that lasts the shift and one that does not.
These are not theoretical concerns. They are real objections we hear from security company owners across Gauteng, KwaZulu-Natal, and the Western Cape every week.
How We Tested
We tested on real devices, during real duty periods, with the app running in production configuration, not in a lab.
The setup:
We connected two Android smartphones to ADB (Android Debug Bridge) and collected detailed battery and network statistics over extended duty periods. Both devices ran MyProtektor with active location tracking, push notifications, and the foreground service that keeps everything running reliably. These measurements capture the background tracking baseline. We then estimated full-shift usage by accounting for typical guard activity, filing incidents, scanning patrol points, responding to assignments.
| Parameter | Device 1 | Device 2 |
|---|---|---|
| Manufacturer | Huawei | Samsung |
| Battery capacity | 4 000 mAh | 4 000 mAh |
| Test duration | approximately 20 hours | approximately 17 hours |
| Network | WiFi | WiFi |
| GPS interval | 120 seconds (every 2 minutes) | 120 seconds |
| App configuration | Production build, foreground service active | Production build, foreground service active |
We deliberately chose two different manufacturers because Android devices do not all behave the same way in the background. Huawei applies aggressive battery management that kills background processes. Samsung handles background tasks more efficiently. Between these two, we captured a realistic range of what security companies will encounter in the field.
The Results: How Much Battery Does a Guard Tracking App Actually Use?
Here is what the diagnostic data showed for location tracking alone (no active app usage on screen):
| Huawei | Samsung | |
|---|---|---|
| Battery consumed (tracking only, per 8 hours) | approximately 2–3% | under 1% |
| GPS active time over full test period | 52 minutes | 3 minutes |
| Background jobs completed successfully | 3 out of 592 | 173 out of 173 |
The difference between the two devices is striking. The Samsung completed every single background location job without interruption. The Huawei's battery management system cancelled 589 out of 592 background jobs, but MyProtektor's foreground service compensated and continued tracking reliably.
What about real shift activity? Tracking alone is only part of the picture. During a normal shift, guards also file incident reports (often with photos), scan QR patrol checkpoints, respond to assignment alerts, and check the dashboard. All of that adds screen time and data transfer.
When we account for typical shift activity, the numbers look like this:
| 8-hour shift | 12-hour shift | |
|---|---|---|
| Battery | 5–8% | 8–12% |
That is the full picture: GPS tracking in the background, plus normal app usage throughout the shift. In typical conditions, a guard starting with a fully charged phone will end a 12-hour shift with roughly 88–92% battery remaining from MyProtektor usage alone, leaving plenty of capacity for calls, messaging, and other apps.
The Results: How Much Mobile Data Does Guard Tracking Cost?
| Per 8-hour shift | |
|---|---|
| Background tracking only | approximately 4–5 MB |
| Normal shift (incidents, patrols, assignments) | 10–30 MB |
The range depends primarily on one thing: photos. Location coordinates, QR scan confirmations, push notifications, and assignment data are all tiny, a few kilobytes each. But each photo attached to an incident report adds 0.5–2 MB depending on the phone's camera resolution and the app's compression settings.
A guard who files five incident reports with three photos each during a shift will use more data than a guard who files one report with no photos. Both are well within normal operating parameters.
Monthly data budget per guard
| Shift pattern | Per shift | 26 shifts per month |
|---|---|---|
| Mostly quiet shifts | 10–15 MB | 260–390 MB |
| Mix of quiet and busy shifts | 15–20 MB | 390–520 MB |
| Mostly busy shifts with photos | 20–30 MB | 520–780 MB |
A 500 MB to 1 GB prepaid SIM covers a full month of guard duty for MyProtektor. At current South African data rates, that is R30–R99 per guard per month for the data component, less than the cost of a single radio battery replacement.
Why Most Tracking Apps Drain Batteries (and How to Avoid It)
The battery drain problem with GPS tracking is real, but it is a design problem, not a physics problem. The difference comes down to how often and how aggressively the app requests location data.
Continuous tracking (every 1–5 seconds): This is what early fleet tracking systems used. The GPS radio stays active permanently, polling satellites every few seconds. It generates highly detailed movement trails, but at a severe cost: 15–25% battery drain per 8 hours, phones running hot, and guards switching off the app in frustration.
Interval-based tracking (every 1–2 minutes): This approach requests a position fix at set intervals and reduces GPS wake-ups between them. The trade-off is slightly less granular movement trails in exchange for dramatically lower battery consumption. For security operations, where you need to know where a guard is, not how they walked between two points, this is more than sufficient.
Adaptive tracking (interval + movement + emergency awareness): This approach builds on interval-based tracking by adding situational awareness. The GPS polls at a fixed interval to keep battery drain low, but the system evaluates each position fix and decides whether the control room needs to see it now. It works like this:
- Guard moving (driving to a scene, patrolling between sites), the system detects significant distance covered and shares the position without waiting for the next scheduled update.
- Guard stationary (posted at a gate, on break), fewer updates since the position has not changed, saving data and battery.
- Panic or emergency, the system prioritises sending every location update as quickly as the device and network allow.
- Poor GPS signal (indoors, near dense structures), low-quality readings are filtered out to prevent false movement on the map.
The result: more tracking detail during the moments that matter, active responses, emergencies, guard movement, and lower resource consumption during quiet periods.
Event-based tracking (on scan or check-in only): Some systems only record a position when the guard actively does something, scanning a checkpoint, filing a report. This uses almost no battery, but it provides no passive oversight. If a guard skips a checkpoint or wanders off route, the control room will not know until the next expected check-in time passes.
MyProtektor uses adaptive tracking at 120-second GPS intervals. The system shares locations more frequently when a guard is moving or responding to an emergency, and less frequently when stationary, giving the control room more timely detail during active situations while keeping battery drain minimal during quiet periods.
What to Ask Before Choosing a Security Guard Tracking App
If you are comparing GPS tracking solutions, ask these questions before signing up:
1. What is the actual GPS polling interval, and does it adapt?
If the vendor says "real-time tracking" but cannot tell you the specific interval in seconds, be cautious. True real-time (every 1–5 seconds) will drain batteries fast. Every 60–120 seconds is the practical sweet spot for security work. Better still, ask whether the system adjusts its behaviour based on what is happening, sharing locations more frequently during emergencies and less frequently when a guard is stationary.
2. Does the app use a foreground service on Android?
Android's background execution limits mean that apps without a foreground service will eventually be killed by the operating system, especially on Huawei, Xiaomi, and Oppo devices. If the vendor does not mention a foreground service or persistent notification, their tracking will be unreliable on a significant portion of the Android devices your guards carry.
3. Can the vendor provide measured battery and data figures?
"Low battery usage" is a marketing claim. Specific percentages per shift, measured on real devices, is evidence. If a vendor cannot tell you approximately how much battery their app consumes during an 8-hour shift, they either have not tested it or do not want to share the results.
4. How does the app handle poor connectivity?
In South Africa, guards regularly move through areas with weak or no signal. A well-designed app queues location data locally and syncs when connectivity returns. A poorly designed app either loses the data or retries aggressively, which drains both battery and data.
Practical Recommendations for Security Companies
For operations managers planning a deployment
- Budget R50–R100 per guard per month for data. A 500 MB to 1 GB package from Vodacom, MTN, or Telkom Mobile is sufficient.
- Choose devices with 4 000+ mAh batteries. This is standard in most smartphones from 2021 onwards. See our device buying guide for specific recommendations and ZAR pricing.
- Test on your worst-case device before full rollout. If the app works reliably on your cheapest Huawei or Xiaomi budget phone, it will work on everything else.
- Brief your guards on battery settings. Certain Android manufacturers kill background apps aggressively. A two-minute settings change during onboarding prevents tracking gaps. We cover this in our battery and data usage guide.
For guards receiving the app
- Do not force-close the app. The notification that says "MyProtektor is running" is supposed to be there. It keeps your location tracking and emergency alerts active. Swiping it away makes you invisible to the control room.
- Check your battery settings. On Huawei and Xiaomi phones, go to Settings > Battery > App Launch and set MyProtektor to manual management with all toggles enabled. Without this, the phone may kill the app during your shift.
- Your phone will last the full shift. The app uses 5–8% battery over 8 hours. You will not need to charge mid-shift because of MyProtektor.
The Bottom Line
GPS guard tracking does not have to drain batteries or burn through data. The technology has moved past the era of always-on GPS and aggressive polling. With interval-based tracking, a well-designed foreground service, and efficient data handling, a guard can run a tracking app through a 12-hour shift and barely notice it on their battery meter.
We measured it. The numbers are public. And we are confident enough in them to put them on our product page and in our admin documentation, because security companies deserve to make procurement decisions based on evidence, not promises.
MyProtektor is a mobile-first security management platform built for security companies in Southern Africa. GPS tracking, incident management, QR patrol verification, and panic alert routing, built for modern Android and iPhone devices. See how it works or view pricing.
