mirror of
https://github.com/seemoo-lab/AirGuard.git
synced 2026-04-25 15:35:49 +03:00
[GH-ISSUE #94] Location data always "not available" #64
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AirGuard#64
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 @lbdroid on GitHub (Jan 4, 2023).
Original GitHub issue: https://github.com/seemoo-lab/AirGuard/issues/94
Background:
Pixel 6 Pro running GrapheneOS, withOUT google services.
Rationale:
Objective is to maximize privacy by decreasing the ability for anyone/anything to track the device, including google. This is very much consistent with the purpose of AirGuard, to find things that may be tracking you so you can disable them.
Issue:
Without google services, network/celltower based approximate location is entirely unavailable, which means that GPS is the only option for determining the device's position.
GPS takes a while to lock on. If depending on a GPS fix, enough time has to be provided in order for it to work most of the time, at least when conditions permit.
Pixel 6 Pro typically takes around 15-20 seconds. It could take more if conditions are challenging. AirGuard appears to time out the location request at 8 seconds, which is just not enough time for a GPS lock on most devices unless its already warm or locked.
Solution: Increase GPS timeout to substantially higher value, such as 1 minute, which is probably high enough most of the time for most devices when outside but in a pocket, and likely not the end of the world if indoors where signal is just not good enough.
https://github.com/seemoo-lab/AirGuard/blob/main/app/src/main/java/de/seemoo/at_tracking_detection/detection/ScanBluetoothWorker.kt#L252
@Sn0wfreezeDev commented on GitHub (Jan 23, 2023):
An Update fixing this is coming soon.