5 minutes is not configurable in setWakeUpAlarm

Hello, right now the time between wake up alarms can’t be less than 5 minutes:

    // wake up time will be the maximum of 5 minutes, the scan period, the between scan period         long milliseconds = 1000l * 60 * 5; /* five minutes */

Is there a reason for this particular value? Can you probably make it configurable?

[yankeppey]

I think the purpose of the wake up alarm is to ensure that device continues to scan beacons periodically even being in sleep mode. Right now, as I got it, there are three cases:

• foreground mode (i.e. at least one activity is in resumed state) - device scans beacons with period defined by foregroundBetweenScanPeriod, using handler to post delayed scans
• background mode (all activity are in paused state) - device scans beacons with period defined by backgroundBetweenScanPeriod, using handler to post delayed scans
• sleep mode (user turned off the screen, no wake locks are hold) - everything stops, device wakes up and scans beacons every 5 minutes (that value is hardcoded). And the last case is pretty common - the most of the time the phone sleeps in user’s pocket. I want the phone to vibrate-notify if the user comes in area of a particular beacon, that provides, for example, some deal/discount, and 5 minutes is pretty long period for this (user can go though the whole beacon area without any notification). Please correct me if I’m wrong somewhere.

[pollux-]

@davidgyoung Thanks for your response… If you got anything regarding that, please keep me posted. I really appreciate that…