WAI
Status Update
Comments
am...@google.com <am...@google.com>
am...@google.com <am...@google.com> #2
Thank you for reporting this issue.
Please provide the below details to debug this issue further.
1. Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
2. Steps followed during the time of bug report captured.
Sample and steps would be helpful.
Please provide the below details to debug this issue further.
1. Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
2. Steps followed during the time of bug report captured.
Sample and steps would be helpful.
l8...@gmail.com <l8...@gmail.com> #3
Please find my comments inline and the attached bug report
1. Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
- We have taken logs as mentioned in above point. Please find attachment.
Device : Google Pixel XL with Android 8.1
2. Steps followed during the time of bug report captured.
Sample and steps would be helpful.
- Background service is running in our application which contains BLEScanner to scan RSSI for connected device. When Mobile device screen gets turn off it is suspending BLEScanner and application is not receiving Scan Results in callback.
Please let us know if more information required.
1. Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
- We have taken logs as mentioned in above point. Please find attachment.
Device : Google Pixel XL with Android 8.1
2. Steps followed during the time of bug report captured.
Sample and steps would be helpful.
- Background service is running in our application which contains BLEScanner to scan RSSI for connected device. When Mobile device screen gets turn off it is suspending BLEScanner and application is not receiving Scan Results in callback.
Please let us know if more information required.
el...@hp.com <el...@hp.com> #4
This issue should be industry-wide. Google, please let us know how to proceed to workaround, or fix this issue.
l8...@gmail.com <l8...@gmail.com> #5
Hi,
Please let us know if you have an update on this issue.
Thanks,
Lokesh
Please let us know if you have an update on this issue.
Thanks,
Lokesh
am...@google.com <am...@google.com> #6
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
jp...@google.com <jp...@google.com> #7
We don't stop filtered scans. Allowsing non-filtered scans was badly impacting battery.
See ScanManager.java file for defails:
void handleSuspendScans() {
for (ScanClient client : mRegularScanClients) {
if (!mScanNative.isOpportunisticScanClient(client) && (client.filters == null
|| client.filters.isEmpty())) {
/*Suspend unfiltered scans*/
if (client.stats != null) {
client.stats.recordScanSuspend(client.scannerId);
}
handleStopScan(client);
mSuspendedScanClients.add(client);
}
}
}
See ScanManager.java file for defails:
void handleSuspendScans() {
for (ScanClient client : mRegularScanClients) {
if (!mScanNative.isOpportunisticScanClient(client) && (client.filters == null
|| client.filters.isEmpty())) {
/*Suspend unfiltered scans*/
if (client.stats != null) {
client.stats.recordScanSuspend(client.scannerId);
}
handleStopScan(client);
mSuspendedScanClients.add(client);
}
}
}
l8...@gmail.com <l8...@gmail.com> #8
Hi,
I have below queries...
1. This is similar to the GPS and we think this should be a user acceptable case like GPS
2. Is there any alternatives ?
Please let us know.
Thanks,
Lokesh
I have below queries...
1. This is similar to the GPS and we think this should be a user acceptable case like GPS
2. Is there any alternatives ?
Please let us know.
Thanks,
Lokesh
pa...@gmail.com <pa...@gmail.com> #9
Ty b cz xc
Description
BLE scanner does not work in our application in Android 8.1 release, if Phone display is turned off.
Same BLE scanner works with Android 8.0 release.
Expected Application behavior:
We are using BLE Scanner in our application to detect the proximity of the devices.
We need to continuously check the proximity (RSSI values) even if phone display is turned off.
References:
In below source code of Android 8.1
Display Listener mDisplayListener is used onDisplayChanged() function checks is screen status and if it is OFF then BLE Scans are suspended.
public void onDisplayChanged(int displayId) {
if (isScreenOn()) {
sendMessage(MSG_RESUME_SCANS, null);
} else {
sendMessage(MSG_SUSPEND_SCANS, null);
}
}
Questions/Alternatives?:
1. Is there any way to get the continues RSSI values even if display of the phone if OFF?
2. Can we override this behavior in any way?
3. Is there any other alternative way to detect the proximity of the device?
Thanks,
Lokesh