0

I currently have a class named LocationCheck. 

public class SpeedCheck {

Here the location is retrieved every 3 seconds and is ongoing until the user stops it. To start checking for locations, the class is called in the Main Activity:

startLoc = new LocationCheck(this);

What i am wondering is if the code needs to be in a Service class rather than just an ordinary class (like it currently is). It works so far with no issues, but i may be misunderstanding the concept of Services etc and could be unaware of problems it may face over checking over a long period of time (fairly new to Android dev).

I have looked into Background Service for location updates, but with FusedLocationProvider (which i am using) it is only possible to receive several updates over an hour. This would not be helpful as i need an update every 3 seconds.

Any advice would be greatly appreciated.

Basmatti
  • 27
  • 8

1 Answers1

0

If you need to keep checking location in background then use service else you can just simply use it in activity. Simply stop the service when you no longer need it because it will consume more battery if left running in background.

jatin rana
  • 825
  • 1
  • 9
  • 21
  • Reading into documentation for FusedLocationProvider it notes that within a Background Service the "location updates only a few times each hour." Is it best to use a Foreground Service then? – Basmatti Jun 02 '18 at 10:13
  • It depends on what you are trying to achieve. If you need accurate location consistently then use foreground service . – jatin rana Jun 02 '18 at 10:22
  • Thanks jatlin, put it all into a service running in the foreground and all works well. – Basmatti Jun 08 '18 at 09:18