View Single Post
Old November 21st, 2013, 07:08 PM   #13 (permalink)
alostpacket
Over Macho Grande?
 
alostpacket's Avatar
 
Join Date: Nov 2009
Location: NY
Posts: 7,920
 
Device(s): GlassXE, MotoX, N5, N4, N7'12, GNex, N1, SGT10.1, Revue, Xoom, Eris, OG Droid
Carrier: TMO

Thanks: 4,603
Thanked 3,579 Times in 1,530 Posts
Default

Just FYI, Google Play Services provides a Location API for all the apps on the phone to use. (among many other APIs)

This is separate from Android's built in LocationManager API.

In other words, a lot of apps use Google Play Services to get location without accessing the GPS directly.

Google's API is generally better, faster, more reliable, and uses LESS battery than the default LocationManager API.

However, a badly programmed app, could cause Google Play Services to keep looking up your location. This probably would show in the battery stats as Google Play Services being the battery hog. So it could make it quite tricky to track down the true offending app.

There may be an additional bug that I am not aware of though.

However, I find it much more likely that there are a lot of apps out there that dont properly "stop" asking for location updates from Google Play Services. It's a very common mistake among not-so-good developers.
alostpacket is offline  
Reply With Quote
The Following User Says Thank You to alostpacket For This Useful Post:
breadnatty08 (November 22nd, 2013)