Despite having the app excempted from battery optimization, the background scan is not working. Every time when opening it the "Last scan" field is from I have last opened the app.

I use LineageOS 18.1 (Android 11) and would be happy to provide any debugging information (adb logcat, whatnot) as needed

I very appreciate your app, thanks for the possibility to get notified about possible tracking devices. What I don't understand is the 'last scan' section on the status screen, what does that mean? My 'last scan' is often some hours ago, in worst cases some days. I did exclude the app from battery saving and use a phone without google services (microG installed, but only partly activated).

Some devices move with me but are known. Examples may include a tag owned by myself or a known trusted associate. I would rather label those devices instead of just ignoring them, so I can remember why they are ignored.

Great software by the way, thanks for all your hard work.

Hello, the app finds devices with different mac addresses every 15 minutes on the map and in the manual scan, but in the same place. Possibly mac books. What devices could that be? If there are no trackers, can you exclude them from the search?

After upgrading to 1.1.0 the history of found devices is lost, but also it does not find devices 1.0.6 (still) does find.

FP3 with LineageOS 18.1.

What else is helpful for you?

Klaus

You should be able to whitelist devices, so that the app will not warn you every time you enter it. For example, I own a tile, and I keep it in my wallet, and even though I've muted it, the app shows that I am unsafe.

Thanks, SteadyStatus21

Description

The "Use Low Energy Scan" setting is described differently in German and English

Statement of the translations:

EN: This option is required to detect all devices DE: If this option is enabled, some devices may not be detected

Screenshot

"This may result in some devices not being recognized." Translation by DeepL.com

Version affected

F-Droid: 1.2 (I could not install versions 1.1.0 and 1.1.0 due to an unknown error)

Play Store: Downloaded on 17.3.2022 17:15

Changes "Make sure that you don’t move to a safe place before you have deactivated the tracker." to "Make sure that you don’t move to another location before deactivating the tracker."

Telling users to avoid going to "a safe place" seems to be a mistranslation from the German string "Stelle sicher, dass du dich nicht an einen anderen Ort begibst bevor du den Tracker gefunden hast". "Deactivating" is a shorter way to say "you have deactivated" in the sentence.

The text defined in https://github.com/seemoo-lab/AirGuard/blob/bdbf32f64dd2a49dfe5f9ea58e1f12fcaf6fcdef/app/src/main/res/values-de/strings.xml#L136 is cut off on my Huawei P Smart 2019 with Android 10 and the latest version of AirGuard (from Google Play Store) installed:

Hi I’ve version 1.0.4 installed and It found two air tags the other day but I never got a notification they were detected. Is there something I’m missing or do notifications trigger under certain situations?

I’m running it on a Pixel 2XL running CalyxOS (android 11).

Please let me know if any additional information would be helpful.

I cleaned up typos and clarified the wording of various strings in strings.xml. (Most memorable is separating "Find My", capitalizing Bluetooth, and replacing "Low Power" with "Low Energy" - even though power is actually more accurate from an electrical engineering perspective.) Feel free to alter my edits as desired.

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

[Question] why are all iphones (Apple devices) etc. found, are they only devices that are connected to an ipod or airtag or only have the myfind network activated? Not all iphones are found in the search. A question of understanding

Um, where's the ignore device button?

Is it the "mark as false positive" button? It seems to forget that mark as soon as I exit the individual result screen.

I've been able to test the manual scan feature before, but when I actually want to use it, it seems to always be "already scanning", and waiting 10s doesn't change that :/

Recently AirGuard started crashing with an SQLite OutOfMemoryError on my GrapheneOS Pixel 4:

type: crash
osVersion: google/flame/flame:13/TP1A.221005.002/2022102600:user/release-keys
package: de.seemoo.at_tracking_detection:35
process: de.seemoo.at_tracking_detection

java.lang.OutOfMemoryError: Failed to allocate a 32 byte allocation with 1301384 free bytes and 1270KB until OOM, target footprint 536870912, growth limit 536870912; giving up on allocation because <1% of heap free after GC.
	at android.database.sqlite.SQLiteDatabase.createSession(SQLiteDatabase.java:600)
	at android.database.sqlite.SQLiteDatabase$$ExternalSyntheticLambda0.get(Unknown Source:2)
	at java.lang.ThreadLocal$SuppliedThreadLocal.initialValue(ThreadLocal.java:284)
	at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:180)
	at java.lang.ThreadLocal.get(ThreadLocal.java:170)
	at android.database.sqlite.SQLiteDatabase.getThreadSession(SQLiteDatabase.java:591)
	at android.database.sqlite.SQLiteDatabase.inTransaction(SQLiteDatabase.java:787)
	at f4.a.M(Unknown Source:2)
	at a4.r.inTransaction(Unknown Source:6)
	at androidx.room.c$a.run(Unknown Source:54)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
	at java.lang.Thread.run(Thread.java:1012)

Ignoring an airtag is a temporary solution, but it soon reappears as a "new" airtag...

Is there any way to connect to it and read the serial number or something? (Maybe requires the private key?)