AltBeacon - reliability issues: "didExitRegion" is frequently called even if a beacon is right besides the android device <p><strong>Brief process of how AltBeacon works in the app:</strong></p> <ul> <li>Detect iBeacon of specified ids (UUID, major/minor id)</li> <li>Run a thread when "didEnterRegion" called (and keep running until the beacon is out of range)</li> <li>When "didExitRegion" called, wait 30 seconds before stop the thread (this is to assure that the beacon is definitely out of the range)</li> <li>Continue to run the thread when "didEnterRegion" called again during the 30 seconds delay and stop the thread, otherwise.</li> </ul> <p><strong>And I found some reliability problems:</strong></p> <blockquote> <ul> <li>"didExitRegion" is frequently called even when a iBeacon is right besides the app.</li> <li>Once "didExitRegion" is called, it takes several seconds, even more than a minute sometimes, to re-scan the iBeacon even with having a<br> very short scanning period setting.</li> </ul> </blockquote> <p>My objective is to run a thread until a beacon is definitely out of a range -- in other words, I would like to secure the high reliability of the app with iBeacon integration. </p> <p>Any suggestions? Am I missing something?</p> <p>Any insight from you will be greatly appreciated!</p> <p>Regards,</p>