AntiMap Log: run in background

[trentbrooks]

Need to update both the openframeworks/iphone and processing/android version of the mobile applications so they run in the background. At the moment the app needs to be active to record the stats, so if you accidentally hit the sleep button or something the stats do not record.

This may require a full port from openframeworks to native ios, and from processing to java. Need to do some more research and tests before making this decision.

[atypical]

Not sure if this is why, but check your plist and make sure that UIApplicationExitsOnSuspend is checked off. When it's on, the app exits entirely when it goes to the background.

[atypical]

Check this too - http://forum.openframeworks.cc/index.php?topic=5877.0

Love your work on AntiMap btw. Thank you for making it opensource!

[trentbrooks]

Hey,

Last I checked, I could not get any openframeworks application to 'run in
background' with all sensors running and data being logged - is this what
you were after? I would definitely like to find a solution to this, if you
have tested and know it works I will implement.

Note: in the setup function, line 188, I had...
'ofxiPhoneDisableIdleTimer()' which calls '[UIApplication sharedApplication
].idleTimerDisabled = true;'. Which should be the same thing as mentioned
in the forum post. This only disables the phone from automatically going to
sleep, eg after a minute or two of no interaction.

In the plist, I have 'Application does not run in background' set to 'YES',
this is on purpose until i can find a way to get all sensor data logged
whilst sleeping. I haven't checked it out, but modifying the
ofxiPhoneAppDelegate.mm
might work... http://forum.openframeworks.cc/index.php/topic,5297.0.html

Cheers,
Trent

On Tue, Aug 28, 2012 at 3:38 AM, MDavid Low [email protected]:

Check this too - http://forum.openframeworks.cc/index.php?topic=5877.0

Love your work on AntiMap btw. Thank you for making it opensource!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-8063696.