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

Bluetooth requires location to be turned on (Mi Smart Scale 2 / OnePlus NordCE 5G) #937

Open
ohsotech opened this issue Mar 6, 2023 · 2 comments · May be fixed by #1057
Open

Bluetooth requires location to be turned on (Mi Smart Scale 2 / OnePlus NordCE 5G) #937

ohsotech opened this issue Mar 6, 2023 · 2 comments · May be fixed by #1057

Comments

@ohsotech
Copy link

ohsotech commented Mar 6, 2023

Mi Smart Scale 2 requires location to be enabled on OnePlus NordCE 5G. This was not the case a few weeks ago.

If I press the bluetooth icon (or have it enabled to auto turn on) it shows this screen, opens the 'enable location' screen and doesn't turn on bluetooth unless location is already on.

openscale

This should only be required for finding a bluetooth scale for the first time, no? If I click on my already-paired scale in the settings, it opens the same window, with the small difference that it has a 'no' button too.

So seems like a bug?

FAQ info which I believe was mentioned in #887 :

Why do openScale needs permission to the coarse location?
The answer is simple because the Android API >= 6.0 needs access to the coarse location to search for Bluetooth devices. The App openScale doesn't read your location at any time. Read the official Android Bluetooth Developer Guide or read the Android 6.0 Changelog for a more technical description.

In android app settings, location is not allowed for openscale. And if I enable location permission, the exact same thing happens. The permission doesn't matter to openscale, only whether location is currently turned on or not.

Of course this could be a OnePlus weirdness

@suncoastkid
Copy link

Same issue on LineageOS Redfin device. Very disappointing.

@0xDB6
Copy link

0xDB6 commented Sep 10, 2023

Bump. Same issue here on a Samsung device with Android 13. I vaguely remember this having been working before.

@xshyne xshyne linked a pull request Aug 14, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

3 participants