Android Question Activity Recognition stops firing

[Rusty]

I have an Activity Recognition app that works great for a while. For example, it will "accurately" notify of the activities and their confidence. It will keep reporting for 30 minutes or so and then stops "firing".
The device is sitting idle on a table when it stops. (i.e. 4 hours)
After a long period of waiting (4 hours as a test), I touch a button on the activity which issues a STOP; then INITIALIZES the AR; then CONNECTS. When this happens, over a period of several minutes, all the activity information that has occurred over the 4 hour period start "firing" and the data finally arrives.
It appears to queue up all the activity events while the phone is "sleeping".
Is this normal? If so, is there a way for the RecongitionService to keep firing and emptying the queue (while updating the database and UI)?
Advice is appreciated.
Thanks,
Rusty

 

[Erel]

See the answer here: http://stackoverflow.com/questions/...gnition-api-doesnt-send-motions-after-a-while
It probably does it to conserve battery power. You can test it by acquiring a partial lock with PhoneWakeState together with a foreground service. This will prevent the OS from sleeping.

 

[Rusty]

Thanks Erel,
Does this mean that as activities change while the phone is sleeping (i.e. still to walking/on-foot) the events are queued? or are they completely ignored/unsensed?
So that when the phone wakes the queued events then fire?
I understand and appreciate your suggestion of PhoneWakeState...
Rusty

 

[Erel]

It is not exactly clear what will happen to these events.