On Android, when you terminate your app with the BackgroundGeolocation plugin configured with stopOnTerminate: false, your Javascript code is completely terminated -- only the plugin's native Android background service continues running.  If you've configured the plugin with an #url, its Android background Service will continue posting locations to your server.

But what if you need to implement some custom business logic in the "headless" state, such as posting a local notification or executing #getCurrentPosition in a heartbeat event?

Read the story...