this post was submitted on 05 Dec 2025
595 points (98.2% liked)
Open Source
42767 readers
163 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It used to have a feature that would beep faster the closer you got to an AP. I used it in cafes and libraries to figure out where to sit for the best WiFi. But they killed it, and I have no idea why :'(
I think it's an OS limitation which throttles the Wifi scanning to slower intervals (and also requires you to enable location(??))
That doesn't make sense to me. I have root. I should be able to allow the app any scanning interval I want.
I think you can disable the "WiFi scan throttling" option in the Developer Options, which might remove this default limitation
Still no idea why Location is needed for this
Edit: Apparently it's a safety feature against malicious developers who can pinpoint your location based on scan results. To make the user aware, they force you to enable location permission
So it works then if you enable this?
Kinda, when I pull down to refresh it seems more responsive rather than doing nothing