Introduction
To maintain a consistent RTK fixed solution and ensure your mock location remains active, Android’s aggressive power-saving features must be managed. If the operating system "optimizes" the Bad Elf Flex app, it may cut the Bluetooth connection or stop background data processing, leading to position jumps or loss of signal.
What You’ll Learn
- How to disable battery optimization for the Bad Elf Flex app.
- How to ensure unrestricted background data usage.
Configuring Bad Elf Flex App Settings
1. Locate the Bad Elf Flex app icon on your home screen or app drawer.
2. Long-press the icon and tap the "i" (App Info) button in the corner.
Alternatively, navigate to Settings > Apps > Bad Elf Flex.
3. Scroll down and tap on Battery.
4. Select Unrestricted.
This ensures Android will never put the app to "sleep" while you are working, even if your screen is off or you are using another app.
5. From the same App Info screen, tap on Mobile Data.
6. Ensure Allow background data usage is toggled ON.
7. Ensure Allow data usage while Data saver is on is toggled ON.
8. From the same App Info screen, tap on App permissions.
9. Verify Location, Nearby devices, and Notifications permissions are allowed.
10. To prevent your GIS software from crashing or losing the stream from the Flex, repeat the steps above for your primary collection app (e.g., PointMan, ArcGIS Field Maps, or QField).
Frequently Asked Questions
Q: Why does my GNSS position stop updating when I turn off the screen?
A: Android often suspends background processes to save battery. If the Bad Elf Flex app is set to "Optimized," the OS may kill the Bluetooth service when the screen is off, severing the link between the receiver and your GIS app.
Q: Will "Unrestricted" battery usage drain my phone?
A: While it allows the app to use more power, the actual impact is usually minimal. The stability of your RTK correction stream and data integrity is worth the slight increase in battery consumption.
Q: Does "Data Saver" mode affect my RTK?
A: Yes. If Data Saver is on and the Bad Elf Flex app isn't granted an exception, the app may be blocked from receiving the NTRIP corrections needed for a centimeter-level fix.
Q: I’ve done this, but my location is still jumping. What else should I check?