[Google Pixel 4 Questions & Answers] Caliden2020:
Thank you - A/B

Hi

Thanks for the tip to look into A/B seamless system updates. I've been investigating and it seems to be involved in the issues I'm having.

More over, it's making the issue really tricky to research.

I got ADB back up and running on my PC to have a good look at the logfiles. I ran logcat -d and saved it to a file.

My Mum then called (always welcome) but one of the issues I'd been having with call quality kicked in. When we finished I reran logcat and saved to a new file. I also had a CMD prompt window open with one I'd not exported,.

A = First Export

B = Second export

C = CMD record

Date/Time marker chosen for spot comparison: 11-30 09:22:41.123

Test A=B=C = True (to ensure logging is reliable between runs and methods)

Results:

A=B=C	A=B	A=C	B=C

FALSE	TRUE	TRUE	TRUE

FALSE	TRUE	FALSE	FALSE

FALSE	TRUE	FALSE	FALSE

FALSE	TRUE	FALSE	FALSE

FALSE	TRUE	FALSE	FALSE

FALSE	TRUE	FALSE	FALSE

FALSE	TRUE	FALSE	FALSE

FALSE	TRUE	FALSE	FALSE

FALSE	TRUE	FALSE	FALSE

FALSE	TRUE	FALSE	FALSE

FALSE	TRUE	FALSE	FALSE

FALSE	TRUE	FALSE	FALSE

FALSE	TRUE	FALSE	FALSE

FALSE	TRUE	TRUE	TRUE

Summary:

Whilst the log entries look the same to user, they are not

A always matches B - outputting to the same format was consistent for the sample

Format of export causes inconsistent matching

"

11-30 09:22:41.123 939 1047 I ASH : @ 1431.144: tmd3702v: Calibrating POFFSET

11-30 09:22:41.123 2873 11564 E AsyncOperation: operation=xlb	opStatusCode=12009 [CONTEXT service_id=45 ]

11-30 09:22:41.123 2873 11564 E AsyncOperation: OperationException[Status{statusCode=unknown status code: 12009	resolution=null}]

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at aqyf.g(:com.google.android.gms@204217046@20.42.17 (150400-342117392):1)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at aqyf.fP(:com.google.android.gms@204217046@20.42.17 (150400-342117392):31)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at ywh.run(:com.google.android.gms@204217046@20.42.17 (150400-342117392):9)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at bmxp.run(:com.google.android.gms@204217046@20.42.17 (150400-342117392):2)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at rgn.c(:com.google.android.gms@204217046@20.42.17 (150400-342117392):6)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at rgn.run(:com.google.android.gms@204217046@20.42.17 (150400-342117392):8)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at rmi.run(:com.google.android.gms@204217046@20.42.17 (150400-342117392):0)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at java.lang.Thread.run(Thread.java:923)"

11-30 09:22:41.123 939 1047 I CHRE : @ 1431.145: [gesture] dropping duplicate proximity!

11-30 09:22:41.123 939 1047 I chatty : uid=1000(system) sensors@2.0-ser expire 9 lines

11-30 09:22:41.123 2873 11564 E AsyncOperation: operation=xlb	opStatusCode=12009 [CONTEXT service_id=45 ]

11-30 09:22:41.123 2873 11564 E AsyncOperation: OperationException[Status{statusCode=unknown status code: 12009	resolution=null}]

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at aqyf.g(:com.google.android.gms@204217046@20.42.17 (150400-342117392):1)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at aqyf.fP(:com.google.android.gms@204217046@20.42.17 (150400-342117392):31)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at ywh.run(:com.google.android.gms@204217046@20.42.17 (150400-342117392):9)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at bmxp.run(:com.google.android.gms@204217046@20.42.17 (150400-342117392):2)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at rgn.c(:com.google.android.gms@204217046@20.42.17 (150400-342117392):6)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at rgn.run(:com.google.android.gms@204217046@20.42.17 (150400-342117392):8)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at rmi.run(:com.google.android.gms@204217046@20.42.17 (150400-342117392):0)"

"11-30 09:22:41.123 2873 11564 E AsyncOperation:	at java.lang.Thread.run(Thread.java:923)"	"

Expecting to find an extra space or two, imagine my suprise when I found two things happening reported at the same time from the same device; only caught because I happened to leave a command prompt window open.

The fact that this could be different.... well it certainly can't be called tanmperproof beyond reasonable doubt; sadly.