{"action":"created","issue":{"url":"https://api.github.com/repos/AltBeacon/android-beacon-library/issues/361","repository_url":"https://api.github.com/repos/AltBeacon/android-beacon-library","labels_url":"https://api.github.com/repos/AltBeacon/android-beacon-library/issues/361/labels{/name}","comments_url":"https://api.github.com/repos/AltBeacon/android-beacon-library/issues/361/comments","events_url":"https://api.github.com/repos/AltBeacon/android-beacon-library/issues/361/events","html_url":"https://github.com/AltBeacon/android-beacon-library/issues/361","id":148003686,"number":361,"title":"v2.8 is unstable?","user":{"login":"lubeast","id":3817355,"avatar_url":"https://avatars.githubusercontent.com/u/3817355?v=3","gravatar_id":"","url":"https://api.github.com/users/lubeast","html_url":"https://github.com/lubeast","followers_url":"https://api.github.com/users/lubeast/followers","following_url":"https://api.github.com/users/lubeast/following{/other_user}","gists_url":"https://api.github.com/users/lubeast/gists{/gist_id}","starred_url":"https://api.github.com/users/lubeast/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lubeast/subscriptions","organizations_url":"https://api.github.com/users/lubeast/orgs","repos_url":"https://api.github.com/users/lubeast/repos","events_url":"https://api.github.com/users/lubeast/events{/privacy}","received_events_url":"https://api.github.com/users/lubeast/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-04-13T09:36:43Z","updated_at":"2016-04-13T15:11:00Z","closed_at":null,"body":"Today i found this library has 2.8 release, so i update library from v2.7 to v2.8.\r\n![90f3c0f0-dc91-4944-8d8b-384b32da61b0](https://cloud.githubusercontent.com/assets/3817355/14488652/d3657c70-019b-11e6-94db-4d2d315e50f4.png)\r\nAnd i didn't change the configuration when i update library. But you can see it's becoming very unstable and i didn't change device or beacon.\r\nSo i change v2.8 back to v2.7 it becomes normal.\r\n\r\n![f674e440-4d54-4daf-9e02-fe8ca1b09283](https://cloud.githubusercontent.com/assets/3817355/14489097/eefa4c70-019d-11e6-8002-1f75ce0e6b4d.png)\r\n\r\nMy test device is `moto x pro`, system version is `5.0.2`\r\n\r\nWhat may cause this problem? Or i need to change my old configuration after i update to v2.8?"},"comment":{"url":"https://api.github.com/repos/AltBeacon/android-beacon-library/issues/comments/209499382","html_url":"https://github.com/AltBeacon/android-beacon-library/issues/361#issuecomment-209499382","issue_url":"https://api.github.com/repos/AltBeacon/android-beacon-library/issues/361","id":209499382,"user":{"login":"davidgyoung","id":1044849,"avatar_url":"https://avatars.githubusercontent.com/u/1044849?v=3","gravatar_id":"","url":"https://api.github.com/users/davidgyoung","html_url":"https://github.com/davidgyoung","followers_url":"https://api.github.com/users/davidgyoung/followers","following_url":"https://api.github.com/users/davidgyoung/following{/other_user}","gists_url":"https://api.github.com/users/davidgyoung/gists{/gist_id}","starred_url":"https://api.github.com/users/davidgyoung/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidgyoung/subscriptions","organizations_url":"https://api.github.com/users/davidgyoung/orgs","repos_url":"https://api.github.com/users/davidgyoung/repos","events_url":"https://api.github.com/users/davidgyoung/events{/privacy}","received_events_url":"https://api.github.com/users/davidgyoung/received_events","type":"User","site_admin":false},"created_at":"2016-04-13T15:11:00Z","updated_at":"2016-04-13T15:11:00Z","body":"Based on these logs, I see the app is in the background, and the library is configured to do a full scan to look for beacons for 1100ms every 5000 ms, deferring to hardware filters the rest of the time.  There was a detection at 20:42:20.239, which was triggered by a hardware filter.  Because beacons were in the vicinity, hardware filters were then temporarily disabled.  So the library spent 1100ms scanning for beacons at:  20:42:24.211 and  then again at 20:42:30.302 but none were seen.  The library then fired a region exit at  20:42:31.461 because no beacons had been detected in 10 seconds.\r\n\r\nDoes this sound like incorrect behavior?  Do you believe the beacon was transmitting the whole time?  I don't see any OS-level log messages for bluetooth advertisements being received, suggesting Android is really not seeing them."}}