android-beacon-library: Android 7 scanning stops after 30 minutes

Expected behavior

Scanning continues indefinitely once ranging starts

Actual behavior

Scanning stops after 30 minutes

Steps to reproduce this behavior

Create an Android Things app that starts ranging

Mobile device model and OS version

Raspberry Pi 3, androidthings_rpi3_devpreview_4

Android Beacon Library version

2.10

Right after the last ranging detection the following shows up in LogCat:

06-11 19:00:22.848  5123  5147 D BtGatt.ScanManager: clientIf set to scan opportunisticly: 6
06-11 19:00:22.848  5123  5147 D BtGatt.ScanManager: configureRegularScanParams() - queue=1
06-11 19:00:22.848  5123  5147 D BtGatt.ScanManager: configureRegularScanParams() - ScanSetting Scan mode=-1 mLastConfiguredScanSetting=2
06-11 19:00:22.848  5123  5147 D BtGatt.ScanManager: configureRegularScanParams() - queue emtpy, scan stopped
06-11 19:00:22.849  5123  5147 D BtGatt.ScanManager: stop scan

This is almost exactly 30 minutes after the scanning started.

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 18 (8 by maintainers)

Most upvoted comments

For my understanding:

Do I need to do more (e.g. set foregroundScanPeriod and the “between” setting) if using the longScanForcingEnabled=true approach?

Is it possible to set this value programmatically?

Cheers

andersborgabiro on Sep 9, 2017