I tried this and mine does retain the settings, even thru a forced quit.
Hoping to see some geofences tomorrow.
Yeah, that is the plan... I am working on a restructuring of the app's architecture that will include some low-level network enhancements. Going to have to play around a bit with it, though, as the later versions of Android are pretty aggressive in shutting out wake-locks. I suspect it may be that the time between tries will need to be the minutes if the initial retries don't work. For example, perhaps keep the wake lock for up to 5 seconds of retries, then sleep for 2 minutes, wake up and try again. At some point we have to abandon it as today, though, lest device battery be affected.Looks like Adam's going to have to use a queue instead. I'd mess around with it in a test app, but ... Java, ugh, too old for that.
Unfortunately, no... long story short, Google is forcing us to change the way we do push notifications and after having followed their migration guide, the sh!t doesn't work and I have been fighting for weeks and weeks now trying to make it do so. Unfortunately, I have to get this part working in the new version because they have upped the target OS version and I can no longer publish in the older version's branch (don't worry, I can support older devices, it is a bit complicated and technical, but long story short Google is REALLY pissing me off but I am trying...)Any news on this? It's still not working