Monitor should be a service?

teze / speakerproximity

Automatically exported from code.google.com/p/speakerproximity

0 stars 0 forks source link

Monitor should be a service? #2

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

Description of functionality:
proximity monitoring should be handled in a proper service that starts with the 
accept broadcast of the call and ends itself after the end call broadcast

Implementation idea:
Implement it as a service instead of an activity

Original issue reported on code.google.com by michel.racic on 3 Sep 2010 at 11:26

GoogleCodeExporter commented 8 years ago

Actually its a broadcast receiver that just starts the listener.
I have to find out how to implement this the proper way.

Original comment by michel.racic on 4 Sep 2010 at 5:03

Changed title: Monitor should be a service?
Changed state: Started

GoogleCodeExporter commented 8 years ago

Original comment by michel.racic on 4 Sep 2010 at 5:03

Added labels: Priority-Medium

GoogleCodeExporter commented 8 years ago

in v.0.2f

Original comment by michel.racic on 5 Sep 2010 at 12:35

Changed state: Implemented

GoogleCodeExporter commented 8 years ago

App works nicely with service so far

Original comment by michel.racic on 6 Sep 2010 at 7:24

Changed state: Verified