Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not detecting beacons after app killed #690

Closed
aashu09 opened this issue May 29, 2018 · 4 comments
Closed

Not detecting beacons after app killed #690

aashu09 opened this issue May 29, 2018 · 4 comments

Comments

@aashu09
Copy link

aashu09 commented May 29, 2018

Hi Support,
I have been using Altbeacon library since last year but now facing problems in some device.
Please resolve it.

Expected behavior

After killing the app, beacon detection should work same as foreground or background.

Actual behavior

After killing the app, beacon detection never works.

Steps to reproduce this behavior

  1. Open the app
  2. Detect beacon
  3. Kill the App

Mobile device model and OS version

device model - HUAWEI_NEM-L22
OS version - 6.0

Android Beacon Library version

2.14

IMPORTANT: This forum is reserved for feature requests or reproducible bugs with the library itself. If you need help with using the library with your project, please open a new question on StackOverflow.com.

@davidgyoung
Copy link
Member

Please repeat this test with the reference app here:

https://github.com/AltBeacon/android-beacon-library-reference

Then reboot the phone with a beacon transmitting and attach a LogCat trace for 1 minute before and 5 minutes after the phone reboot.

If you can attach these logs I will review and investigate

@davidgyoung
Copy link
Member

closing due to inactivity

@chintan-mishra
Copy link

In most Chinese ROMs, the Android OS is customized for extensive battery conservation. As a result, scheduled jobs, pending intents, START_STICKY services, etc. never get delivered.

@davidgyoung
Copy link
Member

I have not seen myself that Huawei blocks START_STICKY, but if confirmed, it may be possible to use a scheduled job to restart the library's scanning services on a 15 minute cycle for manufacturers known to do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants