3

I just basically want to add about 20 and sometimes 80 Proximity Alerts with no time expiration with a radius of around 500 meters. Just wondering whether by doing this will suck up the battery real quick? also would it make any difference by reducing the radius?

tshepang
  • 12,111
  • 21
  • 91
  • 136
Chiwai Chan
  • 4,716
  • 4
  • 30
  • 33

1 Answers1

10

This will definitely eat your battery real quick. You never want to be setting more than a couple of proximity alerts in any case, the use-case you describe isn't really catered for in Proximity Alerts.

Proximity Alerts should switch between GPS and Network as required, but in my experience they tend to stick to GPS whenever it's available, and your battery will suffer as a result.

A better alternative would be to use an Alarm and a Service to check your current location against your set of 20 to 80 locations as required. This will let you manage the LBS you want to use (GPS or Cell ID), as well as the frequency of checks, all in one place. Doing it this way will let you manage your battery use much more effectively.

Reto Meier
  • 96,655
  • 18
  • 100
  • 72
  • Thanks for the alternative solution. – Chiwai Chan Jul 12 '09 at 13:21
  • Did one of you implemented this solution and could share some code ? Even with a low number of alerts, Google's proximity alerts are reported to be power hungry (much more than needed). So this would be a rather useful piece of software... – acapola Mar 31 '14 at 21:47