microg / GmsCore

Free implementation of Play Services
https://microg.org
Apache License 2.0
8.36k stars 1.7k forks source link

No exposure warning on Fairphone 4 (FP4) with both CWA and CCTG (Pixel 4 has warning since days) #1857

Closed rugk closed 1 year ago

rugk commented 1 year ago

Describe the bug I usually carry two devices with me. And almost always I carry both with me!

One is the Fairphone 4 (FP4) and the other is Pixel 4 (flame). Both have both the official Corona-Warn-App (CWA) and the fork Corona Contact Tracing Germany (CCTG). The CWA may be suspended via CalyxOS mechanism though sometimes, but that should not matter, as the data should be collected by microG IIRC.

Now, only the Pixel 4 shows red encounter warnings for days, while the FP4 shows none (green card).

To Reproduce

Use both devices with Bluetooth and microG/exposure notifications turned on. Get some red warnings on Pixel 4.

FYI, on FP4 I today (2022-12-26) also uploaded my own positive rapid antigen test (RAT) via the Corona-Warn-App (CWA), so possibly the other device should show that, too? Also a PCR test is already in progress on the same device/same app (i.e. FP4, CWA).

Expected behavior

Even though the Pixel 4 shows red warnings since Wednesday last week (2022-12-21), the Fairphone 4 shows none. However, microG shows it has collected IDs and that generally also looks similar to what the Pixel 4 shows.

Screenshots

(in German, i am sorry)

Both CWA and CCTG on each device, show the same results.

Pixel 4

Screenshot_20221226-180621

Screenshot_20221226-190040

Screenshot_20221226-185651

Fairphone 4 (FP4)

Screenshot_20221226-180720

Screenshot_20221226-180342

Screenshot_20221226-185942

System

Pixel 4

Device: Pixel 4 (flame)
OS: Android 13, CalyxOS 4.4.0
Build-ID: TQ1A.221205.011.22404000
CWA: v2.27.2 (ENV v 1.8 [18223616000); CCL v 3.5.1) CCTG: v2.27.2.0 (using external microG v1822361600); CCL v 3.5.1 microG: 0.2.26.223616-37 (23ae934)

FP4

Device: Fairphone 4 (FP4)
OS: Android 13, CalyxOS 4.3.1
Build-ID: TQ1A.221205.011.22404010 CWA: v2.28.3 (ENV v 1.8 [18223616000); CCL v 3.5.1) CCTG: v2.28.3.1 (using external microG v18223616000); CCL v 3.5.1 microG: 0.2.26.223616-37 (23ae934)

Additional context

Just confirmed self-check on both devices is all green.

I can provide the exposure data (that you export, i.e. exposure.db) and logcat for both devices upon request privately.

Note I am fully aware that the exposures between apps, i.e. CCTG and CWA and so it can vary between two devices, too somewhat. However, there must be a bug here, because such a high variation is IMHO not explanable.

rugk commented 1 year ago

From my evaluation of the data it seems that Pixel 4 reports way too many exposures (it even has near exposures at the night while I am sleeping) and FP4 does the contrasting thing, i.e. reports no exposures at all.

Edit: Ah, of course! The exposures at the night I am by myself, I am sorry. As said, I published my self-test result, so of course the app is green.

rugk commented 1 year ago

Uff, can I somehow filter my own self-test out of the data?

Arg, of course Pixel 4 warns about an exposure, because that is me having uploaded it on FP4. That makes sense uff, I am sorry…

If you want to evaluate the data anyway, feel free, but my mind messed it up. Should get recovered… :(

Ein-Tim commented 1 year ago

Just so that I understand it: You warned on your FP4, thus the Pixel shows a warning. If you have not also warned on your Pixel, why should the FP4 show a warning? 😅

Maybe I'm also missing the point of the issue, sorry.

rugk commented 1 year ago

Yeah that was the point and you got it correct. I initially thought the warning came came from somewhere else, but was to dizzy to notify it was my own. :facepalm:

I am sorry…

Ein-Tim commented 1 year ago

@rugk

I am sorry…

There's no need to be sorry! I hope you get well soon!

rugk commented 1 year ago

Thanks.