Page 1 of 1

beacon and app closed

Posted: 10:25, 13 Oct 2014
by maxborgatti
hi guys

you made a great tutorial on estimote beacon discovery

did you know that they assure that device can be alerted also when app are killed/closed?

https://community.estimote.com/hc/en-us ... -is-killed

is it somewhat tha can be translated under our framework? i offer myself as beta tester :D

Re: beacon and app closed

Posted: 19:49, 28 Oct 2014
by micke
Thanks for the link! Adding background notifications is on our todo-list.

Thanks for signing up as a tester :)

Best regards, Mikael

Re: beacon and app closed

Posted: 23:04, 20 Jan 2015
by josephshirk
maxborgatti wrote:did you know that they assure that device can be alerted also when app are killed/closed?

https://community.estimote.com/hc/en-us ... -is-killed

is it somewhat tha can be translated under our framework? i offer myself as beta tester :D


I was about to ask a related question for android 4.3. According to Estimote:
On Android 5.0 the app still has to be running in the background, but the background scanning was redesigned to greatly improve power efficiency.


Do I correctly understand that this means that when the android screen times out, or the app goes to sleep, a message from the arduino can wake up the app? the application I'm making is for electric touring bikes. obviously it would suck the battery down to keep the screen on for long periods. it will be necessary to wake up the droid when some important event or alert happens.

I have one device that is android 4.3 and another that is android 5. I did not let one upgrade because the RedBear demo (I believe) android app does not support 5.0.

in the case of evothings, does it matter or is one better supported?

Re: beacon and app closed

Posted: 18:50, 22 Jan 2015
by micke
Hi Joseph,

when the android screen times out, or the app goes to sleep, a message from the arduino can wake up the app?

My understanding is that a message from Arduino can send the app to the foreground if it is in the back. You would need a Cordova plugin to bring the app from background to front using a JavaScript call.

But I don't think you can programmatically unlock the Android lock screen. Hmmm, indeed this seems to be possible:

http://stackoverflow.com/questions/1272 ... amatically
http://stackoverflow.com/questions/1435 ... mmatically
http://stackoverflow.com/questions/3793 ... -is-locked

Don't know how practical the above is. This would also need to be implemented in a Cordova plugin to work with JavaScript. Perhaps there are such plugins available already?

[Android 4.3 vs 5.9] in the case of evothings, does it matter or is one better supported?

Evothings Workbench does not care about the Android version used. The Cordova plugins used, could however have issues with particular Android versions or need upgrading to 5.0, so this would affect plugins used in the app and also Evothings Client, which is a Cordova app with several plugins included.

Best, Mikael