Skip to content

Scan Rate Configuration

Scan rates control how frequently Network Survey collects data for each technology. Adjusting these rates allows you to balance battery life, data density, and storage requirements.

TechnologyDefault RateTypeNotes
Cellular5 secondsPeriodicSmallest battery impact
Wi-Fi15 secondsPeriodicScan throttling may apply
Bluetooth30 secondsPeriodic23 minimum due to scan duration
GNSS45 secondsPeriodicHeavy battery usage
Device Status120 secondsPeriodicBattery, heart beat
Phone StateEvent-drivenNetwork ChangesRecords when network state changes occur
CDREvent-drivenNetwork ChangesRecords when communication events occur

How it works:

  • Android notifies Network Survey when changes occur
  • Examples for Phone State: Tower changes, technology changes (5G to 4G), etc

Advantages:

  • No missed events
  • Captures all network changes
  • Efficient (only logs when needed)

Time-Based (Cellular, Wi-Fi, Bluetooth, GNSS)

Section titled “Time-Based (Cellular, Wi-Fi, Bluetooth, GNSS)”

How it works:

  • Network Survey actively scans at regular intervals
  • Timer triggers each scan

Advantages:

  • Predictable data rate
  • Consistent sampling
  • Easy to analyze time series

Scan rates directly affect battery consumption:

Different survey technologies have vastly different battery consumption profiles. Understanding these differences helps you optimize your surveys for battery life.

Impact Ranking (Least to Most):

RankSurvey TypeImpact LevelReason
1Phone StateMinimalEvent-driven, no scanning
2CDRMinimalEvent-driven, no scanning
3CellularLowPassive queries only, location adds overhead
4Wi-FiModerateActive scans + location overhead
5BluetoothModerateActive scans + location overhead
6GNSSHighRaw measurements are battery intensive

Why they’re most efficient:

  • No active scanning required
  • Android notifies Network Survey when events occur (tower changes, calls, etc.)
  • Network Survey wakes up, grabs location if available, logs the event, then goes back to sleep
  • Battery impact is minimal and proportional to how often network events actually occur

Best for: Continuous monitoring with minimal battery drain

Why they’re low impact:

  • Your phone is always scanning for cell towers in the background (this is how cellular networks work)
  • When Network Survey “scans,” it simply asks Android for the latest values already in memory
  • The query itself has virtually no battery impact
  • The only battery drain comes from getting location data to attach to each record

Why they’re moderate impact:

  • These technologies require real scans that have a measurable battery cost
    • Wi-Fi: Radio actively searches for access points
    • Bluetooth: Scans for both BLE and Classic Bluetooth devices (22-23 seconds total)
  • Each scan consumes power to activate the radio and process results
  • Location retrieval adds additional battery overhead on top of the scan itself

Best for: Targeted surveys in specific areas where you need Wi-Fi or Bluetooth coverage data

Why they’re highest impact:

  • Network Survey uses Android’s raw GNSS measurements feature for detailed satellite data
  • This feature is highly battery intensive as it processes raw signals from GPS, GLONASS, Galileo, and BeiDou satellites
  • Raw GNSS measurements always arrive at 1-second intervals (not configurable by apps)

Smart Battery Optimization:

Network Survey includes an intelligent optimization to reduce GNSS battery drain:

  • Scan interval ≥ 30 seconds:

    • Turns on raw GNSS measurements for 15 seconds
    • Waits for warmup period (measurements need time to stabilize)
    • Captures one measurement
    • Turns off raw GNSS measurements until next scan interval
    • Result: Significant battery savings with good data quality
  • Scan interval ≤ 29 seconds:

    • Keeps raw GNSS measurements continuously enabled
    • No warmup delays between measurements
    • Result: Maximum accuracy and data density at cost of higher battery drain

Choosing your GNSS scan rate:

30+ seconds → Battery-conscious mode (intermittent measurements)
29- seconds → Accuracy mode (continuous measurements)

Best for:

  • Precision surveys: Use ≤29s intervals for best accuracy
  • Long-duration surveys: Use ≥30s intervals to conserve battery

For maximum battery life:

  1. Prioritize event-driven surveys (CDR, Phone State) when possible
  2. Use cellular surveys as your baseline time-based technology
  3. Add Wi-Fi and Bluetooth only in areas where you need that data
  4. Use GNSS sparingly, with ≥30s intervals unless precision is critical
  5. Disable technologies you don’t need for your specific survey
  1. Open Network Survey
  2. Tap (menu) → Settings
  3. Find “Scanning Rate” section
  4. Adjust desired technology:
    • Cellular Scan Interval
    • Wi-Fi Scan Interval
    • Bluetooth Scan Interval
    • GNSS Scan Interval
    • Device Status Message Interval

Value: Enter interval in seconds

Example: Setting Wi-Fi to 5 means scan every 5 seconds.

Administrators can configure scan rates via Mobile Device Management

See MDM Configuration for details.

Some technologies have minimum scan intervals:

Why:

  • BLE scan requires 10 seconds
  • Classic Bluetooth scan requires 12 seconds
  • Total: 22-23 seconds for both

If you set lower:

  • Network Survey automatically adjusts to 23 seconds

Android 9+ Throttling:

  • Max 4 scans per 2 minutes (30 seconds effective minimum)

Workaround:

  • Enable developer options → Disable “Wi-Fi scan throttling”

Lower scan interval = More data, more battery drain Higher scan interval = Less data, less battery drain

Scan rate changes are applied immediately:

  • No need to restart survey
  • New interval takes effect on next scan
  • Previously logged data unaffected

Example Workflow:

  1. Start survey with 30-second intervals (battery-conscious)
  2. Enter area of interest
  3. Change to 5-second intervals (detailed scan)
  4. Leave area
  5. Change back to 30-second intervals

For long surveys:

  1. Use default or higher scan intervals
  2. Disable unused technologies
  3. Use external power if possible
  4. Monitor battery level
  5. Enable battery pause feature (Settings → Pause at battery level)

Faster scans don’t always mean better data:

  • GPS accuracy doesn’t improve with faster GNSS scans
  • CDR and Phone State events are captured regardless of scan interval
  • Wi-Fi networks don’t change that frequently
  • Bluetooth devices may not advertise continuously

Balance data density with practical needs:

  • 10 seconds is usually sufficient for most surveys
  • 30 seconds captures enough data for analysis
  • 60+ seconds for monitoring, not detailed surveys

Scans seem slower than configured:

  • Check Android Wi-Fi scan throttling (Android 9+)
  • Verify battery optimization is disabled (in settings)
  • Check Data Saver mode isn’t enabled

Battery drains too fast:

  • Increase scan intervals
  • Disable unused technologies
  • Use default rates as baseline