mirror of
https://github.com/seemoo-lab/AirGuard.git
synced 2026-04-25 15:35:49 +03:00
[GH-ISSUE #65] Location bug on Pixel 5? #41
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AirGuard#41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mmueller on GitHub (Apr 19, 2022).
Original GitHub issue: https://github.com/seemoo-lab/AirGuard/issues/65
I left home today at 10:15. I got notified of several trackers today, and when I look at the timestamps and the locations of the pings, there are pings at my home at 11:00, 11:05, 11:20 mixed in with pings at my actual location (not home) at 11:15, 11:32. I don't own any trackers, but I'm probably near some in town right now. I've been in the same spot for the last two hours.
Is this a bug with location services on Android? If my phone gave AirGuard locations in different places while I sat near the same air tag, I can easily imagine it generating false positives as if that tracker was following me. Is this a known issue on Pixel phones, or maybe just me? Is there any way for AirGuard to know when it's getting a "stale" location from the system, or is that not really a thing?
In settings, AirGuard has location permission "all the time" and "use precise location" is enabled. The global "Google Location Accuracy" (aka "Improve Location Accuracy") is also enabled, but I wonder if this can actually introduce errors? I just dug into the developer options to see if a mock location app is configured, and no, there isn't one.
@larsdennert commented on GitHub (Jan 1, 2023):
I have an issue where air guard rarely records location when it gets a hit. Almost all tags don't have location data. No permissions have been denied.
@Sn0wfreezeDev commented on GitHub (Mar 23, 2023):
Should be fixed in the next update