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

Scanning possible when bluetooth is off #628

Open
juniorsaraviao opened this issue Feb 26, 2024 · 6 comments
Open

Scanning possible when bluetooth is off #628

juniorsaraviao opened this issue Feb 26, 2024 · 6 comments
Labels
bug Something isn't working cannot reproduce

Comments

@juniorsaraviao
Copy link

Describe the bug
When the Bluetooth is off, the plugin can still detect Bluetooth devices (this only happens on Android). Even it's possible to connect.

To Reproduce
Steps to reproduce the behavior:

  1. Clone the project https://github.com/juniorsaraviao/BluetoothSample/tree/master
  2. Run the project on Android.
  3. Turn off the Bluetooth.
  4. Tap Scan.

Expected behavior
The plugin shouldn't be able to detect devices when the Bluetooth is off.

Screenshots

Issue
Bluetooth.off.issue.mp4

Plugin version:

  • @capacitor-community/bluetooth-le: v3.1.2

Desktop (please complete the following information):

  • OS: Android

Smartphone (please complete the following information):

  • Device: Samsung Galaxy A53
  • OS: Android
  • Version 14
@juniorsaraviao juniorsaraviao added the bug Something isn't working label Feb 26, 2024
@juniorsaraviao
Copy link
Author

any updates related to this issue?

@pwespi
Copy link
Member

pwespi commented Apr 6, 2024

I cannot reproduce this on my test devices. Were you able to reproduce this on multiple different devices?

@peitschie
Copy link
Collaborator

Just passing through... I've have seen this with some Android phones (specifically with a Nokia device on Android 10). No idea why some phones allow it... But it never seemed to me to be a plugin kind of bug.

If the firmware and hardware in Android allow it... Should the plugin really be concerned about preventing this?

@juniorsaraviao
Copy link
Author

juniorsaraviao commented Apr 16, 2024

Hi everyone, I could replicate the same issue using a Samsung Galaxy A11 (Android 12) physical device

@ehsieh-semios
Copy link

I recall this is a defect from the firmware (seen in Samsung phones), maybe you can try to "normalize" it by off and on before the next scanning

@abdh-dev
Copy link

abdh-dev commented Aug 27, 2024

Oh yeah this also happened to me with my samsung galaxy a12 (android version 13) phone, at first it was unusual but i never paid much attention to it until i found this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cannot reproduce
Projects
None yet
Development

No branches or pull requests

5 participants