Frequent Exit/Enter actions using Android sample app


#1

I have found multiple posts on this issue for the past several years, but there does not seem to be an exact solution. I’m hoping I have missed it and someone can help me…

Using the Estimote Cloud service, I downloaded the sample Notification app using one beacon. With that sample app, the beacon is sitting within 36" of the phone on my desk. Without moving or waking the phone, this is the activity log from the Android device (Google Pixel 2 XL with Android Pie).

2018-10-22 09:16:30.022 15729-15729/com.estimote.notification E/context change: onEnter
2018-10-22 09:16:54.089 15729-15729/com.estimote.notification E/context change: onExit
2018-10-22 09:16:58.288 15729-15729/com.estimote.notification E/context change: onEnter
2018-10-22 09:18:42.791 15729-15729/com.estimote.notification E/context change: onExit
2018-10-22 09:18:53.217 15729-15729/com.estimote.notification E/context change: onEnter
2018-10-22 09:23:07.981 15729-15729/com.estimote.notification E/context change: onExit
2018-10-22 09:23:28.055 15729-15729/com.estimote.notification E/context change: onEnter
2018-10-22 09:29:30.775 15729-15729/com.estimote.notification E/context change: onExit
2018-10-22 09:29:35.195 15729-15729/com.estimote.notification E/context change: onEnter
2018-10-22 09:30:39.016 15729-15729/com.estimote.notification E/context change: onExit
2018-10-22 09:30:42.387 15729-15729/com.estimote.notification E/context change: onEnter
2018-10-22 09:35:24.035 15729-15729/com.estimote.notification E/context change: onExit
2018-10-22 09:35:44.866 15729-15729/com.estimote.notification E/context change: onEnter
2018-10-22 09:36:26.012 15729-15729/com.estimote.notification E/context change: onExit
2018-10-22 09:36:46.165 15729-15729/com.estimote.notification E/context change: onEnter
2018-10-22 09:37:27.397 15729-15729/com.estimote.notification E/context change: onExit
2018-10-22 09:37:48.909 15729-15729/com.estimote.notification E/context change: onEnter

As you can see, that’s pretty frequent and not all that helpful for a user when they’re constantly being notified of the beacon presence.

I have attempted to adjust the time intervals through the Estimote Cloud, but that does not seem to alleviate the problem.

Are there other suggestions or work arounds to address this issue?

Thank you


#2

Try experimenting with the range of your Proximity Zone, i.e., in NotificationsManager find:

.inCustomRange(3.0)

… and try increasing it. This should put the phone more firmly/deeply “inside” the proximity zone, and hence reduce the flickering between inside and outside. (= enters and exits)


#3

Ok, I’ll try that. The current setting is 3.0 for the custom range and the phone just sits within a few inches of the beacon (no movement at all).


#4

I’d say give it a try anyway and let us know how it goes. In the Android world especially, a signal strength that corresponds to 3 m on one smartphone, might be 6 m on another smartphone, and 1 m on yet another.

But if increasing the range doesn’t help, there might be something else going on here.


#5

Just an idea : If an exit message was sent less than 10s before, I won’t create a notification.