title: AltBeacon Ranging in the background (when not killed)
body: <p>I'm trying to move my perfectly valid iOS scenario over to Android via AltBeacon:</p>
  
  <p>The mobile app monitors for beacons. When mobile is in beacon range, didDetermineState is launched, in iOS it is done automatically when entering/leaving zones so I guess (hope) AltBeacon follows this. didDetermineState checks if we just went inside the region and if so, it launches ranging, if not - it stops ranging. The ranging decides what to do next based on distance. It works both in Foreground (then displays proper information) or in the background (then it displays notifications). </p>
  
  <p>For me it is obvious and almost perfect scenario. However most examples treat Monitoring/Ranging like it is something competing (or at least totally separate), not cooperating.</p>
  
  <p>I didn't want to make notifications when the app is killed (if possible), only when in Foreground or in the Background (when you go to the "desktop" or any other app without killing our app).</p>
  
  <p>I tried to follow this scenario on Android and things doesn't look like I was hoping:</p>
  
  <ol>
  <li>At launch the didDetermineState is launched automatically at start and it usually returns OUTSIDE.</li>
  <li>The AltBeacon documentation clearly states, that BeaconConsumer should extend Activity or Service - does it mean that I can't range in Application class?</li>
  <li>Is it even possible to Monitor and Range when App is in Background but not killed?</li>
  </ol>
  
  <p>Please help.</p>