Android 14 segfault - com.zulipmobile.MainActivity (server) is unresponsive

Android 14 is causing near instant crashes when the app is opened, and restarts to try again, causing restart loops. Sometimes it will remain open just long enough to type one message and then crash on send or crash while simply looking at the app. There doesn't seem to be any inherent connection between actions in the app and when it is crashing so I suspect it has something to do with the background server communications. This issue only appeared after updating to Android 14 and have never experienced this issue before. Have tried both zulip beta and zulip release versions with no success.
Any hints or pointers?
Thanks

2023-06-26 13:44:05.488 10357-10357 cr_AwContents           com.zulipmobile                      W  WebView.destroy() called while WebView is still attached to window.
2023-06-26 13:44:05.503  1922-5302  ActivityManager         system_server                        I  Killing 12878:com.google.android.webview:sandboxed_process0:org.chromium.content.app.SandboxedProcessService0:5/u0a440i322 (adj 0): isolated not needed
2023-06-26 13:44:05.509  1922-2249  libprocessgroup         system_server                        I  Successfully killed process cgroup uid 99322 pid 12878 in 5ms
2023-06-26 13:44:05.529  1922-2200  DisplayManagerService   system_server                        D  Drop pending events for gone uid 99322
2023-06-26 13:44:05.529  2820-2820  Zygote                  webview_zygote                       I  Process 12878 exited cleanly (0)
2023-06-26 13:44:05.886  1082-2554  sensors-hal<EMAIL_ADDRESS>I  [ssc_utils]get_qmi_debug_flag:243, support_qmi_debug : false
2023-06-26 13:44:05.977  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253583.970: [Capo] Count NOT Validate in-motion sample2var=0.073225 (#sample 25)
2023-06-26 13:44:05.985  1082-2554  sensors-hal<EMAIL_ADDRESS>I  [ssc_utils]get_qmi_debug_flag:243, support_qmi_debug : false
2023-06-26 13:44:06.031  1922-2572  ConnectivityService     system_server                        D  NetReassign [no changes] [c 2] [a 2] [i 1]
2023-06-26 13:44:06.170  2193-2210  pixel-thermal           and...ardware.thermal-service.pixel  I  skin-therm-monitor:37.5 raw data: skin-therm-monitor:37500
2023-06-26 13:44:06.172  1082-1251  CHRE<EMAIL_ADDRESS>D  @ 253584.165: [ActivityPlatform] type 2, confidence 90
2023-06-26 13:44:06.216 10357-10357 com.zulipmobile         com.zulipmobile                      E  Invalid resource ID 0x00000389.
2023-06-26 13:44:06.583  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253584.576: [Capo] Count NOT Validate in-motion sample2var=0.106700 (#sample 25)
2023-06-26 13:44:06.813 10357-10357 com.zulipmobile         com.zulipmobile                      E  Invalid resource ID 0x00000a69.
2023-06-26 13:44:06.856 10357-10357 AndroidRuntime          com.zulipmobile                      D  Shutting down VM
2023-06-26 13:44:06.864 10357-10357 AndroidRuntime          com.zulipmobile                      E  FATAL EXCEPTION: main
                                                                                Process: com.zulipmobile, PID: 10357
                                                                                java.lang.NullPointerException: Attempt to invoke virtual method 'android.graphics.drawable.Drawable android.graphics.drawable.Drawable$ConstantState.newDrawable(android.content.res.Resources)' on a null object reference
                                                                                at android.graphics.drawable.DrawableContainer$DrawableContainerState.createAllFutures(DrawableContainer.java:879)
                                                                                at android.graphics.drawable.DrawableContainer$DrawableContainerState.getOpacity(DrawableContainer.java:1162)
                                                                                at android.graphics.drawable.DrawableContainer.getOpacity(DrawableContainer.java:433)
                                                                                at android.graphics.drawable.InsetDrawable.getOpacity(InsetDrawable.java:260)
                                                                                at android.view.View.computeOpaqueFlags(View.java:20143)
                                                                                at android.view.View.setBackgroundDrawable(View.java:25348)
                                                                                at androidx.appcompat.widget.AppCompatEditText.setBackgroundDrawable(AppCompatEditText.java:112)
                                                                                at android.view.View.setBackground(View.java:25241)
                                                                                at android.view.View.<init>(View.java:6242)
                                                                                at android.widget.TextView.<init>(TextView.java:1155)
                                                                                at android.widget.EditText.<init>(EditText.java:101)
                                                                                at android.widget.EditText.<init>(EditText.java:97)
                                                                                at androidx.appcompat.widget.AppCompatEditText.<init>(AppCompatEditText.java:74)
                                                                                at androidx.appcompat.widget.AppCompatEditText.<init>(AppCompatEditText.java:69)
                                                                                at androidx.appcompat.widget.AppCompatEditText.<init>(AppCompatEditText.java:65)
                                                                                at com.facebook.react.views.textinput.ReactEditText.<init>(ReactEditText.java:134)
                                                                                at com.facebook.react.views.textinput.ReactTextInputManager.createViewInstance(ReactTextInputManager.java:182)
                                                                                at com.facebook.react.views.textinput.ReactTextInputManager.createViewInstance(ReactTextInputManager.java:83)
                                                                                at com.facebook.react.uimanager.ViewManager.createViewInstance(ViewManager.java:139)
                                                                                at com.facebook.react.uimanager.ViewManager.createView(ViewManager.java:76)
                                                                                at com.facebook.react.uimanager.NativeViewHierarchyManager.createView(NativeViewHierarchyManager.java:281)
                                                                                at com.facebook.react.uimanager.UIViewOperationQueue$CreateViewOperation.execute(UIViewOperationQueue.java:194)
                                                                                at com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.dispatchPendingNonBatchedOperations(UIViewOperationQueue.java:1110)
                                                                                at com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.doFrameGuarded(UIViewOperationQueue.java:1081)
                                                                                at com.facebook.react.uimanager.GuardedFrameCallback.doFrame(GuardedFrameCallback.java:29)
                                                                                at com.facebook.react.modules.core.ReactChoreographer$ReactChoreographerDispatcher.doFrame(ReactChoreographer.java:175)
                                                                                at com.facebook.react.modules.core.ChoreographerCompat$FrameCallback$1.doFrame(ChoreographerCompat.java:85)
                                                                                at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1337)
                                                                                at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1348)
                                                                                at android.view.Choreographer.doCallbacks(Choreographer.java:952)
                                                                                at android.view.Choreographer.doFrame(Choreographer.java:878)
                                                                                at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1322)
                                                                                at android.os.Handler.handleCallback(Handler.java:958)
                                                                                at android.os.Handler.dispatchMessage(Handler.java:99)
                                                                                at android.os.Looper.loopOnce(Looper.java:205)
                                                                                at android.os.Looper.loop(Looper.java:294)
                                                                                at android.app.ActivityThread.main(ActivityThread.java:8176)
                                                                                at java.lang.reflect.Method.invoke(Native Method)
                                                                                at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
                                                                                at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:971)
2023-06-26 13:44:06.873  1922-3071  Compatibil...geReporter system_server                        D  Compat change id reported: 161145287; UID 10440; state: DISABLED
2023-06-26 13:44:06.889 10357-10357 Sentry                  com.zulipmobile                      I  Not possible to read external files directory
2023-06-26 13:44:06.948 10357-10508 TrafficStats            com.zulipmobile                      D  tagSocket(184) with statsTag=0xffffffff, statsUid=-1
2023-06-26 13:44:07.102  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253585.095: [Capo] Count NOT Validate in-motion sample2var=0.026399 (#sample 25)
2023-06-26 13:44:07.214 10357-10396 AndroidRuntime          com.zulipmobile                      E  FATAL EXCEPTION: mqt_native_modules
                                                                                Process: com.zulipmobile, PID: 10357
                                                                                java.lang.NullPointerException: Attempt to invoke virtual method 'android.graphics.drawable.Drawable android.graphics.drawable.Drawable$ConstantState.newDrawable(android.content.res.Resources)' on a null object reference
                                                                                at android.graphics.drawable.DrawableContainer$DrawableContainerState.createAllFutures(DrawableContainer.java:879)
                                                                                at android.graphics.drawable.DrawableContainer$DrawableContainerState.getOpacity(DrawableContainer.java:1162)
                                                                                at android.graphics.drawable.DrawableContainer.getOpacity(DrawableContainer.java:433)
                                                                                at android.graphics.drawable.InsetDrawable.getOpacity(InsetDrawable.java:260)
                                                                                at android.view.View.computeOpaqueFlags(View.java:20143)
                                                                                at android.view.View.setBackgroundDrawable(View.java:25348)
                                                                                at android.view.View.setBackground(View.java:25241)
                                                                                at android.view.View.<init>(View.java:6242)
                                                                                at android.widget.TextView.<init>(TextView.java:1155)
                                                                                at android.widget.EditText.<init>(EditText.java:101)
                                                                                at android.widget.EditText.<init>(EditText.java:97)
                                                                                at android.widget.EditText.<init>(EditText.java:93)
                                                                                at android.widget.EditText.<init>(EditText.java:89)
                                                                                at com.facebook.react.views.textinput.ReactTextInputShadowNode.createInternalEditText(ReactTextInputShadowNode.java:265)
                                                                                at com.facebook.react.views.textinput.ReactTextInputShadowNode.setThemedContext(ReactTextInputShadowNode.java:85)
                                                                                at com.facebook.react.uimanager.UIImplementation.createView(UIImplementation.java:254)
                                                                                at com.facebook.react.uimanager.UIManagerModule.createView(UIManagerModule.java:505)
                                                                                at java.lang.reflect.Method.invoke(Native Method)
                                                                                at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
                                                                                at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:188)
                                                                                at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
                                                                                at android.os.Handler.handleCallback(Handler.java:958)
                                                                                at android.os.Handler.dispatchMessage(Handler.java:99)
                                                                                at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
                                                                                at android.os.Looper.loopOnce(Looper.java:205)
                                                                                at android.os.Looper.loop(Looper.java:294)
                                                                                at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:228)
                                                                                at java.lang.Thread.run(Thread.java:1012)
2023-06-26 13:44:07.219 10357-10396 Sentry                  com.zulipmobile                      I  Not possible to read external files directory
2023-06-26 13:44:07.257 10357-10508 TrafficStats            com.zulipmobile                      D  tagSocket(184) with statsTag=0xffffffff, statsUid=-1
2023-06-26 13:44:07.623  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253585.616: [Capo] Count NOT Validate in-motion sample2var=0.024463 (#sample 25)
2023-06-26 13:44:08.173  2193-2210  pixel-thermal           and...ardware.thermal-service.pixel  I  skin-therm-monitor:37.5 raw data: skin-therm-monitor:37500
2023-06-26 13:44:08.229  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253586.222: [Capo] Count NOT Validate in-motion sample2var=0.005874 (#sample 25)
2023-06-26 13:44:08.748  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253586.742: [Capo] Count NOT Validate in-motion sample2var=0.005398 (#sample 25)
2023-06-26 13:44:08.760  1082-1251  CHRE<EMAIL_ADDRESS>D  @ 253586.753: StationaryDetect
2023-06-26 13:44:08.771  1082-1251  CHRE<EMAIL_ADDRESS>D  @ 253586.764: MagGyroCal(0)=OFF
2023-06-26 13:44:08.836  1082-1251  ASH<EMAIL_ADDRESS>D  @ 253586.829: SensorType 195 resampler quality 0
2023-06-26 13:44:08.836  1082-1251  ASH<EMAIL_ADDRESS>D  @ 253586.830: SensorType 195 resampler quality 0
2023-06-26 13:44:09.045  1922-2572  ConnectivityService     system_server                        D  NetReassign [no changes] [c 1] [a 3] [i 2]
2023-06-26 13:44:09.270  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253587.263: [Capo] Count NOT Validate in-motion sample2var=0.002732 (#sample 25)
2023-06-26 13:44:09.379  1082-1251  CHRE<EMAIL_ADDRESS>D  @ 253587.372: [ActivityPlatform] type 2, confidence 85
2023-06-26 13:44:09.800  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253587.793: [Capo] Count NOT Validate in-motion sample2var=0.000947 (#sample 25)
2023-06-26 13:44:10.177  2193-2210  pixel-thermal           and...ardware.thermal-service.pixel  I  skin-therm-monitor:37.497 raw data: skin-therm-monitor:37497
2023-06-26 13:44:10.398  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253588.391: [Capo] Count NOT Validate in-motion sample2var=0.000233 (#sample 25)
2023-06-26 13:44:10.443 22880-12924 CastDatabase            com.google.android.gms.persistent    I  Saving the database
2023-06-26 13:44:10.454 22880-12924 SQLiteCastStore         com.google.android.gms.persistent    I  [CastNetworkInfo] saved: 1, skipped: 0, [CastDeviceInfo]: saved 2, skipped 0, [Paired Guest Mode DeviceInfo] saved: 0, skipped: 0. [ProbedNetworks]: saved 0, skipped: 0, [ProbedSocketAddress]: saved 2, skipped: 0, [Network-Device pairs]: saved: 2
2023-06-26 13:44:10.915  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253588.908: [Capo] Count NOT Validate in-motion sample2var=0.019425 (#sample 25)
2023-06-26 13:44:11.435  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253589.429: [Capo] Count NOT Validate in-motion sample2var=0.009514 (#sample 25)
2023-06-26 13:44:11.634  1922-2290  DisplayPow...roller2[0] system_server                        I  BrightnessEvent: disp=0, physDisp=local:4630946523002478721, brt=0.36609778, initBrt=0.23956636, rcmdBrt=0.36609778, preBrt=0.23956636, lux=57.500233, preLux=32.912056, hbmMax=1.0, hbmMode=off, rbcStrength=89, thrmMax=1.0, powerFactor=1.0, wasShortTermModelActive=true, flags=, reason=automatic, autoBrightness=true, strategy=InvalidBrightnessStrategy
2023-06-26 13:44:11.635  1922-2202  DisplayManagerService   system_server                        D  Ignore redundant display event 0/4 to 10263/12557
2023-06-26 13:44:11.635  1922-2202  DisplayManagerService   system_server                        D  Ignore redundant display event 0/4 to 10373/23710
2023-06-26 13:44:11.635  1922-2202  DisplayManagerService   system_server                        D  Ignore redundant display event 0/4 to 10195/26070
2023-06-26 13:44:11.635  1922-2202  DisplayManagerService   system_server                        D  Ignore redundant display event 0/4 to 10209/27468
2023-06-26 13:44:11.635  1922-2202  DisplayManagerService   system_server                        D  Ignore redundant display event 0/4 to 10206/28535
2023-06-26 13:44:11.636  1922-2202  DisplayManagerService   system_server                        D  Ignore redundant display event 0/4 to 10263/12557
2023-06-26 13:44:11.636  1922-2202  DisplayManagerService   system_server                        D  Ignore redundant display event 0/4 to 10373/23710
2023-06-26 13:44:11.636  1922-2202  DisplayManagerService   system_server                        D  Ignore redundant display event 0/4 to 10195/26070
2023-06-26 13:44:11.636  1922-2202  DisplayManagerService   system_server                        D  Ignore redundant display event 0/4 to 10209/27468
2023-06-26 13:44:11.636  1922-2202  DisplayManagerService   system_server                        D  Ignore redundant display event 0/4 to 10206/28535
2023-06-26 13:44:11.636  1922-1922  BrightnessSynchronizer  system_server                        I  [3654] New Update 0.36609778(f) set brightness values:  94(i)
2023-06-26 13:44:11.636  1922-1922  BrightnessSynchronizer  system_server                        I  New PendingUpdate: {[3655] 0.36609778(f), mUpdatedTypes=0, mConfirmedTypes=0, mTimeUpdated=0}, prev=null
2023-06-26 13:44:11.638  1922-1922  BrightnessSynchronizer  system_server                        I  Swallowing update of 94(i) by update: {[3654] 0.36609778(f), mUpdatedTypes=1, mConfirmedTypes=1, mTimeUpdated=253581186}
2023-06-26 13:44:11.638  1922-1922  BrightnessSynchronizer  system_server                        I  Completed Update: {[3654] 0.36609778(f), mUpdatedTypes=1, mConfirmedTypes=1, mTimeUpdated=253581186}
2023-06-26 13:44:11.958  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253589.951: [Capo] Count NOT Validate in-motion sample2var=0.032637 (#sample 25)
2023-06-26 13:44:12.060  1922-2572  ConnectivityService     system_server                        D  NetReassign [no changes] [c 2] [a 3] [i 2]
2023-06-26 13:44:12.488  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253590.481: [Capo] Count NOT Validate in-motion sample2var=0.011208 (#sample 25)
2023-06-26 13:44:12.587  1082-1251  CHRE<EMAIL_ADDRESS>D  @ 253590.580: [ActivityPlatform] type 2, confidence 75
2023-06-26 13:44:13.082  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253591.075: [Capo] Count NOT Validate in-motion sample2var=0.004049 (#sample 25)
2023-06-26 13:44:13.258  1082-1251  VSC<EMAIL_ADDRESS>D  @ 253591.251: [Significant Motion] Request motion_detect, interval<PHONE_NUMBER>7136.0 ms, latency 0.0 ms
2023-06-26 13:44:13.259  1082-1251  VSC<EMAIL_ADDRESS>D  @ 253591.251: [Significant Motion] Stop accel
2023-06-26 13:44:13.262  1082-1251  ASH<EMAIL_ADDRESS>D  @ 253591.255: SensorType 195 resampler quality 2
2023-06-26 13:44:13.473  1922-2539  InputDispatcher         system_server                        W  Window fad5352 com.zulipmobile/com.zulipmobile.MainActivity (server) is unresponsive: fad5352 com.zulipmobile/com.zulipmobile.MainActivity (server) is not responding. Waited 5000ms for MotionEvent
2023-06-26 13:44:13.473  1922-2539  InputDispatcher         system_server                        W  Canceling events for fad5352 com.zulipmobile/com.zulipmobile.MainActivity (server) because it is unresponsive
2023-06-26 13:44:13.473  1922-2539  WindowManager           system_server                        I  ANR in Window{fad5352 u0 com.zulipmobile/com.zulipmobile.MainActivity}. Reason:Input dispatching timed out (fad5352 com.zulipmobile/com.zulipmobile.MainActivity (server) is not responding. Waited 5000ms for MotionEvent)
2023-06-26 13:44:13.476  1922-12956 ActivityManager         system_server                        D  created ANR temporary file:/data/anr/temp_anr_489472697458337685.txt
2023-06-26 13:44:13.476  1922-12956 ActivityManager         system_server                        I  Collecting stacks for pid 10357 into temporary file temp_anr_489472697458337685.txt
2023-06-26 13:44:13.479  1922-12956 system_server           system_server                        I  libdebuggerd_client: started dumping process 10357
2023-06-26 13:44:13.483 10357-10362 com.zulipmobile         com.zulipmobile                      I  Thread[6,tid=10362,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a5116f0,peer=0x16100000,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:13.483   749-749   tombstoned              tombstoned                           I  registered intercept for pid 10357 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:13.483 10357-10362 com.zulipmobile         com.zulipmobile                      I
2023-06-26 13:44:13.561  1922-2199  Compatibil...geReporter system_server                        D  Compat change id reported: 184838306; UID 10440; state: DISABLED
2023-06-26 13:44:13.561  1922-2199  Compatibil...geReporter system_server                        D  Compat change id reported: 185004937; UID 10440; state: DISABLED
2023-06-26 13:44:13.565  1922-2199  Compatibil...geReporter system_server                        D  Compat change id reported: 184838306; UID 1000; state: DISABLED
2023-06-26 13:44:13.566  1922-2199  Compatibil...geReporter system_server                        D  Compat change id reported: 185004937; UID 1000; state: DISABLED
2023-06-26 13:44:13.567  1922-2199  Compatibil...geReporter system_server                        D  Compat change id reported: 168419799; UID 10206; state: DISABLED
2023-06-26 13:44:13.567  1922-2199  Compatibil...geReporter system_server                        D  Compat change id reported: 273564678; UID 10206; state: DISABLED
2023-06-26 13:44:13.570  1922-2199  Compatibil...geReporter system_server                        D  Compat change id reported: 168419799; UID 1210226; state: DISABLED
2023-06-26 13:44:13.570  1922-2199  Compatibil...geReporter system_server                        D  Compat change id reported: 273564678; UID 1210226; state: DISABLED
2023-06-26 13:44:13.572  1922-2199  Compatibil...geReporter system_server                        D  Compat change id reported: 168419799; UID 10262; state: DISABLED
2023-06-26 13:44:13.572  1922-2199  Compatibil...geReporter system_server                        D  Compat change id reported: 273564678; UID 10262; state: DISABLED
2023-06-26 13:44:13.574  1922-2199  Compatibil...geReporter system_server                        D  Compat change id reported: 168419799; UID 10423; state: DISABLED
2023-06-26 13:44:13.575  1922-2199  Compatibil...geReporter system_server                        D  Compat change id reported: 273564678; UID 10423; state: DISABLED
2023-06-26 13:44:13.583  1082-2554  sensors-hal<EMAIL_ADDRESS>I  [ssc_utils]get_qmi_debug_flag:243, support_qmi_debug : false
2023-06-26 13:44:13.585  1922-2199  Looper                  system_server                        W  Slow dispatch took 111ms android.fg h=android.os.Handler c=com.android.server.wm.AnrController$$ExternalSyntheticLambda2@45b12da m=0
2023-06-26 13:44:13.586  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253591.580: [Capo] Count NOT Validate in-motion sample2var=0.047007 (#sample 25)
2023-06-26 13:44:13.590  1922-12957 ActivityManager         system_server                        I  dumpStackTraces pids={1762=true, 3387=true, 3648=true, 3884=true, 3906=true, 3953=true, 4494=true, 5070=true, 5081=true, 5100=true, 5144=true, 5148=true, 5344=true, 5448=true, 5519=true, 5707=true, 5792=true, 5813=true, 5955=true, 5979=true, 5985=true, 6003=true, 6041=true, 6083=true, 6171=true, 6347=true, 6397=true, 6462=true, 6971=true, 7273=true, 7829=true, 7883=true, 8584=true, 8707=true, 8720=true, 9208=true, 9231=true, 9284=true, 9456=true, 9472=true, 9492=true, 9536=true, 9613=true, 9660=true, 9931=true, 9955=true, 10447=true, 10550=true, 10690=true, 12027=true, 12253=true, 12520=true, 12536=true, 12557=true, 14722=true, 15479=true, 18218=true, 20771=true, 22455=true, 22588=true, 22841=true, 22861=true, 22880=true, 23484=true, 23710=true, 23772=true, 24133=true, 24873=true, 25386=true, 26070=true, 26399=true, 27468=true, 27904=true, 28535=true, 28599=true, 28724=true, 29426=true, 29433=true, 29508=true, 29867=true, 31826=true, 32025=true, 32571=true}
2023-06-26 13:44:13.590  1922-12957 ActivityManager         system_server                        I  Dumping to /data/anr/anr_2023-06-26-13-44-13-590
2023-06-26 13:44:13.653  1082-2554  sensors-hal<EMAIL_ADDRESS>I  [ssc_utils]get_qmi_debug_flag:243, support_qmi_debug : false
2023-06-26 13:44:13.920  1082-2554  sensors-hal<EMAIL_ADDRESS>I  [ssc_utils]get_qmi_debug_flag:243, support_qmi_debug : false
2023-06-26 13:44:13.966   749-749   tombstoned              tombstoned                           I  received crash request for pid 10357
2023-06-26 13:44:13.966   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 10357 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:13.967 10357-10362 com.zulipmobile         com.zulipmobile                      I  Wrote stack traces to tombstoned
2023-06-26 13:44:13.967   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:13.969  1922-12956 system_server           system_server                        I  libdebuggerd_client: done dumping process 10357
2023-06-26 13:44:13.977  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 1922
2023-06-26 13:44:13.989  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 1922
2023-06-26 13:44:13.990   749-749   tombstoned              tombstoned                           I  registered intercept for pid 1922 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:13.991  1922-1955  system_server           system_server                        I  Thread[2,tid=1955,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a5116f0,peer=0x12c80148,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:13.991  1922-1955  system_server           system_server                        I
2023-06-26 13:44:14.000  2193-2210  pixel-thermal           and...ardware.thermal-service.pixel  I  skin-therm-monitor:37.49 raw data: skin-therm-monitor:37490
2023-06-26 13:44:14.117  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253592.110: [Capo] Count NOT Validate in-motion sample2var=0.041224 (#sample 25)
2023-06-26 13:44:14.282  1922-15775 AidlSensorManager       system_server                        I  aidl_ssvc_poll: spurious wake up, back to work
2023-06-26 13:44:14.291  1922-18940 HidlSensorManager       system_server                        I  hidl_ssvc_poll: spurious wake up, back to work
2023-06-26 13:44:14.319  2193-2193  pixel-thermal           and...ardware.thermal-service.pixel  I  skin-therm-monitor:37.49 raw data: skin-therm-monitor:37490
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 1922
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 10357
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 651
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 1461
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 654
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 30485
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 32021
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 11
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 12
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 48
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 64
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 313
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 504
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 505
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 595
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 1099
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 1159
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 4040
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 5605
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 11644
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 22785
2023-06-26 13:44:14.330  1922-12962 ActivityManager         system_server                        I  Skipping next CPU consuming process, not a java proc: 27215
2023-06-26 13:44:14.336  2668-2716  ControlsLi...rollerImpl com.android.systemui                 D  Subscribing callback, service count: 1
2023-06-26 13:44:14.348  1922-3071  Compatibil...geReporter system_server                        D  Compat change id reported: 261072174; UID 10166; state: ENABLED
2023-06-26 13:44:14.357  2668-2716  ControlsLi...rollerImpl com.android.systemui                 D  Unsubscribing callback
2023-06-26 13:44:14.400  2668-2716  QuickAccessWalletTile   com.android.systemui                 I  Successfully retrieved wallet cards.
2023-06-26 13:44:14.435   749-749   tombstoned              tombstoned                           I  received crash request for pid 1922
2023-06-26 13:44:14.435   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 1922 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:14.437  1922-1955  system_server           system_server                        I  Wrote stack traces to tombstoned
2023-06-26 13:44:14.437   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:14.437  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 1922
2023-06-26 13:44:14.444  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 4455
2023-06-26 13:44:14.453  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 4455
2023-06-26 13:44:14.454   749-749   tombstoned              tombstoned                           I  registered intercept for pid 4455 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:14.455  4455-4470  putmethod.latin         com...gle.android.inputmethod.latin  I  Thread[5,tid=4470,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a51a200,peer=0x14cc01c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:14.455  4455-4470  putmethod.latin         com...gle.android.inputmethod.latin  I
2023-06-26 13:44:14.539  3387-3545  BtGatt.ScanManager      com.google.android.bluetooth         W  Moving filtered scan client to downgraded scan (scannerId 2)
2023-06-26 13:44:14.541  3387-3545  bt_stack                com.google.android.bluetooth         I  [INFO:le_scanning_manager.cc(167)] Scan in shim layer stopped
2023-06-26 13:44:14.543  3387-3423  bluetooth               com.google.android.bluetooth         I  packages/modules/Bluetooth/system/gd/hci/le_address_manager.cc:193 unregister_client: Client unregistered
2023-06-26 13:44:14.543  3387-3545  bt_stack                com.google.android.bluetooth         I  [INFO:le_scanning_manager.cc(345)] SetScanParameters in shim layer
2023-06-26 13:44:14.544  3387-3545  bt_stack                com.google.android.bluetooth         I  [INFO:le_scanning_manager.cc(167)] Scan in shim layer started
2023-06-26 13:44:14.544  1046-1046  vendor.qti..._transport<EMAIL_ADDRESS>D  SocRxDWakeup: Flow off->Change UART baudrate to 38.4kbs->send 0x00->Change UART baudrate to max->Flow on
2023-06-26 13:44:14.544  1046-1046  vendor.qti..._transport<EMAIL_ADDRESS>I  ## userial_vendor_ioctl: UART Flow Off
2023-06-26 13:44:14.556  1046-1046  vendor.qti..._transport<EMAIL_ADDRESS>I  ## userial_vendor_set_baud: 17
2023-06-26 13:44:14.567  1046-1046  vendor.qti..._transport<EMAIL_ADDRESS>I  SetBaudRate: in BOTHER
2023-06-26 13:44:14.567  1046-1046  vendor.qti..._transport<EMAIL_ADDRESS>I  ## userial_vendor_ioctl: UART Flow On
2023-06-26 13:44:14.567  1046-3499  vendor.qti...bs_handler<EMAIL_ADDRESS>I  ProcessIbsCmd: Received IBS_WAKE_ACK: 0xFC
2023-06-26 13:44:14.567  1046-3499  vendor.qti...bs_handler<EMAIL_ADDRESS>I  ProcessIbsCmd: Signal wack_cond_
2023-06-26 13:44:14.568  1046-3499  vendor.qti...bs_handler<EMAIL_ADDRESS>I  ProcessIbsCmd: Received IBS_WAKE_ACK: 0xFC
2023-06-26 13:44:14.568  1046-3499  vendor.qti...bs_handler<EMAIL_ADDRESS>I  ProcessIbsCmd: Signal wack_cond_
2023-06-26 13:44:14.568  1046-1046  vendor.qti...bs_handler<EMAIL_ADDRESS>D  DeviceWakeUp: Unblocked from waiting for FC
2023-06-26 13:44:14.568  3387-3423  bluetooth               com.google.android.bluetooth         I  packages/modules/Bluetooth/system/gd/hci/le_scanning_manager.cc:588 stop_scan: Scanning already stopped, return!
2023-06-26 13:44:14.568  3387-3423  bluetooth               com.google.android.bluetooth         I  packages/modules/Bluetooth/system/gd/hci/le_address_manager.cc:178 register_client: Client registered
2023-06-26 13:44:14.659  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253592.652: [Capo] Count NOT Validate in-motion sample2var=0.002086 (#sample 25)
2023-06-26 13:44:14.805   749-749   tombstoned              tombstoned                           I  received crash request for pid 4455
2023-06-26 13:44:14.805   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 4455 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:14.805  4455-4470  putmethod.latin         com...gle.android.inputmethod.latin  I  Wrote stack traces to tombstoned
2023-06-26 13:44:14.805   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:14.807  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 4455
2023-06-26 13:44:14.813  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 5244
2023-06-26 13:44:14.815  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 5244
2023-06-26 13:44:14.816   749-749   tombstoned              tombstoned                           I  registered intercept for pid 5244 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:14.816  5244-5266  eui:sui_service         com...services.secureui:sui_service  I  Thread[3,tid=5266,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a50fb20,peer=0x12ec01c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:14.816  5244-5266  eui:sui_service         com...services.secureui:sui_service  I
2023-06-26 13:44:14.913   749-749   tombstoned              tombstoned                           I  received crash request for pid 5244
2023-06-26 13:44:14.913   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 5244 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:14.913  5244-5266  eui:sui_service         com...services.secureui:sui_service  I  Wrote stack traces to tombstoned
2023-06-26 13:44:14.913  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 5244
2023-06-26 13:44:14.914   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:14.916  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 5224
2023-06-26 13:44:14.918  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 5224
2023-06-26 13:44:14.918   749-749   tombstoned              tombstoned                           I  registered intercept for pid 5224 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:14.919  5224-5233  malpowermanager         com...nnectivitythermalpowermanager  I  Thread[4,tid=5233,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a5132c0,peer=0x132001c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:14.919  5224-5233  malpowermanager         com...nnectivitythermalpowermanager  I
2023-06-26 13:44:15.003   749-749   tombstoned              tombstoned                           I  received crash request for pid 5224
2023-06-26 13:44:15.003   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 5224 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.004  5224-5233  malpowermanager         com...nnectivitythermalpowermanager  I  Wrote stack traces to tombstoned
2023-06-26 13:44:15.004  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 5224
2023-06-26 13:44:15.004   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:15.007  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 5174
2023-06-26 13:44:15.009  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 5174
2023-06-26 13:44:15.009   749-749   tombstoned              tombstoned                           I  registered intercept for pid 5174 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.010  5174-5186  .ims.rcsservice         com.android.ims.rcsservice           I  Thread[4,tid=5186,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a5132c0,peer=0x136801c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:15.011  5174-5186  .ims.rcsservice         com.android.ims.rcsservice           I
2023-06-26 13:44:15.072  1922-2572  ConnectivityService     system_server                        D  NetReassign [no changes] [c 1] [a 2] [i 2]
2023-06-26 13:44:15.102   749-749   tombstoned              tombstoned                           I  received crash request for pid 5174
2023-06-26 13:44:15.102   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 5174 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.102   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:15.102  5174-5186  .ims.rcsservice         com.android.ims.rcsservice           I  Wrote stack traces to tombstoned
2023-06-26 13:44:15.103  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 5174
2023-06-26 13:44:15.106  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 5206
2023-06-26 13:44:15.109  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 5206
2023-06-26 13:44:15.109   749-749   tombstoned              tombstoned                           I  registered intercept for pid 5206 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.110  5206-5212  RestartDetector         com.google.SSRestartDetector         I  Thread[5,tid=5212,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a5116f0,peer=0x12e401c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:15.110  5206-5212  RestartDetector         com.google.SSRestartDetector         I
2023-06-26 13:44:15.179  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253593.172: [Capo] Count NOT Validate in-motion sample2var=0.000763 (#sample 25)
2023-06-26 13:44:15.189   749-749   tombstoned              tombstoned                           I  received crash request for pid 5206
2023-06-26 13:44:15.189   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 5206 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.190  5206-5212  RestartDetector         com.google.SSRestartDetector         I  Wrote stack traces to tombstoned
2023-06-26 13:44:15.190  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 5206
2023-06-26 13:44:15.190   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:15.194  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 5171
2023-06-26 13:44:15.196  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 5171
2023-06-26 13:44:15.196   749-749   tombstoned              tombstoned                           I  registered intercept for pid 5171 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.198  5171-5181  com.android.nfc         com.android.nfc                      I  Thread[6,tid=5181,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a51a200,peer=0x13f401c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:15.198  5171-5181  com.android.nfc         com.android.nfc                      I
2023-06-26 13:44:15.345   749-749   tombstoned              tombstoned                           I  received crash request for pid 5171
2023-06-26 13:44:15.345   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 5171 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.346  5171-5181  com.android.nfc         com.android.nfc                      I  Wrote stack traces to tombstoned
2023-06-26 13:44:15.346  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 5171
2023-06-26 13:44:15.346   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:15.349  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 3033
2023-06-26 13:44:15.353  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 3033
2023-06-26 13:44:15.354   749-749   tombstoned              tombstoned                           I  registered intercept for pid 3033 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.354  3033-3076  m.android.phone         com.android.phone                    I  Thread[5,tid=3076,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a5132c0,peer=0x16b001c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:15.354  3033-3076  m.android.phone         com.android.phone                    I
2023-06-26 13:44:15.496   749-749   tombstoned              tombstoned                           I  received crash request for pid 3033
2023-06-26 13:44:15.496   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 3033 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.496  3033-3076  m.android.phone         com.android.phone                    I  Wrote stack traces to tombstoned
2023-06-26 13:44:15.496   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:15.499  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 3033
2023-06-26 13:44:15.503  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 2963
2023-06-26 13:44:15.505  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 2963
2023-06-26 13:44:15.505   749-749   tombstoned              tombstoned                           I  registered intercept for pid 2963 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.506  2963-2973  .codeaurora.ims         org.codeaurora.ims                   I  Thread[6,tid=2973,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a50fb20,peer=0x130401c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:15.506  2963-2973  .codeaurora.ims         org.codeaurora.ims                   I
2023-06-26 13:44:15.588   749-749   tombstoned              tombstoned                           I  received crash request for pid 2963
2023-06-26 13:44:15.588   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 2963 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.589  2963-2973  .codeaurora.ims         org.codeaurora.ims                   I  Wrote stack traces to tombstoned
2023-06-26 13:44:15.589   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:15.589  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 2963
2023-06-26 13:44:15.592  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 2974
2023-06-26 13:44:15.594  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 2974
2023-06-26 13:44:15.594   749-749   tombstoned              tombstoned                           I  registered intercept for pid 2974 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.595  2974-3031  com.android.se          com.android.se                       I  Thread[4,tid=3031,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a51a200,peer=0x12e801c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:15.595  2974-3031  com.android.se          com.android.se                       I
2023-06-26 13:44:15.676   749-749   tombstoned              tombstoned                           I  received crash request for pid 2974
2023-06-26 13:44:15.676   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 2974 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.676   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:15.676  2974-3031  com.android.se          com.android.se                       I  Wrote stack traces to tombstoned
2023-06-26 13:44:15.677  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 2974
2023-06-26 13:44:15.680  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 2986
2023-06-26 13:44:15.681  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 2986
2023-06-26 13:44:15.681   749-749   tombstoned              tombstoned                           I  registered intercept for pid 2986 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.682  2986-3006  atisticsservice         com...m.qti.devicestatisticsservice  I  Thread[6,tid=3006,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a50fb20,peer=0x12dc01c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:15.682  2986-3006  atisticsservice         com...m.qti.devicestatisticsservice  I
2023-06-26 13:44:15.730  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253593.723: [Capo] Count NOT Validate in-motion sample2var=0.000286 (#sample 25)
2023-06-26 13:44:15.730  1082-1251  CHRE<EMAIL_ADDRESS>D  @ 253593.724: [ActivityPlatform] type 2, confidence 84
2023-06-26 13:44:15.761   749-749   tombstoned              tombstoned                           I  received crash request for pid 2986
2023-06-26 13:44:15.761   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 2986 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.762  2986-3006  atisticsservice         com...m.qti.devicestatisticsservice  I  Wrote stack traces to tombstoned
2023-06-26 13:44:15.762  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 2986
2023-06-26 13:44:15.762   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:15.765  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 2967
2023-06-26 13:44:15.766  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 2967
2023-06-26 13:44:15.767   749-749   tombstoned              tombstoned                           I  registered intercept for pid 2967 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.767  2967-2985  .qcrilmsgtunnel         com.qualcomm.qcrilmsgtunnel          I  Thread[5,tid=2985,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a5132c0,peer=0x12e401c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:15.767  2967-2985  .qcrilmsgtunnel         com.qualcomm.qcrilmsgtunnel          I
2023-06-26 13:44:15.846   749-749   tombstoned              tombstoned                           I  received crash request for pid 2967
2023-06-26 13:44:15.846   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 2967 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.847  2967-2985  .qcrilmsgtunnel         com.qualcomm.qcrilmsgtunnel          I  Wrote stack traces to tombstoned
2023-06-26 13:44:15.847  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 2967
2023-06-26 13:44:15.847   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:15.851  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 3007
2023-06-26 13:44:15.853  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 3007
2023-06-26 13:44:15.853   749-749   tombstoned              tombstoned                           I  registered intercept for pid 3007 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.854  3007-3018  snetworkmonitor         com...droid.apps.cbrsnetworkmonitor  I  Thread[5,tid=3018,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a5132c0,peer=0x12d801c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:15.854  3007-3018  snetworkmonitor         com...droid.apps.cbrsnetworkmonitor  I
2023-06-26 13:44:15.927   749-749   tombstoned              tombstoned                           I  received crash request for pid 3007
2023-06-26 13:44:15.927   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 3007 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.928  3007-3018  snetworkmonitor         com...droid.apps.cbrsnetworkmonitor  I  Wrote stack traces to tombstoned
2023-06-26 13:44:15.928   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:15.928  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 3007
2023-06-26 13:44:15.932  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 2929
2023-06-26 13:44:15.933  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 2929
2023-06-26 13:44:15.934   749-749   tombstoned              tombstoned                           I  registered intercept for pid 2929 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:15.934  2929-2960  oid.grilservice         com.google.android.grilservice       I  Thread[6,tid=2960,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a50fb20,peer=0x12e001c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:15.934  2929-2960  oid.grilservice         com.google.android.grilservice       I
2023-06-26 13:44:16.003  2193-2210  pixel-thermal           and...ardware.thermal-service.pixel  I  skin-therm-monitor:37.497 raw data: skin-therm-monitor:37497
2023-06-26 13:44:16.018   749-749   tombstoned              tombstoned                           I  received crash request for pid 2929
2023-06-26 13:44:16.019   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 2929 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:16.019  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 2929
2023-06-26 13:44:16.019  2929-2960  oid.grilservice         com.google.android.grilservice       I  Wrote stack traces to tombstoned
2023-06-26 13:44:16.019   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:16.022  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 2922
2023-06-26 13:44:16.024  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 2922
2023-06-26 13:44:16.024   749-749   tombstoned              tombstoned                           I  registered intercept for pid 2922 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:16.025  2922-2935  com.qti.phone           com.qti.phone                        I  Thread[3,tid=2935,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a5116f0,peer=0x12e801c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:16.025  2922-2935  com.qti.phone           com.qti.phone                        I
2023-06-26 13:44:16.036  1099-1196  rlsservice              rlsservice                           D  MonitorDisplayStatus client num 1, display status 1, sensor status 1
2023-06-26 13:44:16.106   749-749   tombstoned              tombstoned                           I  received crash request for pid 2922
2023-06-26 13:44:16.106   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 2922 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:16.107   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:16.107  2922-2935  com.qti.phone           com.qti.phone                        I  Wrote stack traces to tombstoned
2023-06-26 13:44:16.107  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 2922
2023-06-26 13:44:16.110  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 2897
2023-06-26 13:44:16.112  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 2897
2023-06-26 13:44:16.112   749-749   tombstoned              tombstoned                           I  registered intercept for pid 2897 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:16.113  2897-2933  qtidataservices         .qtidataservices                     I  Thread[6,tid=2933,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a50fb20,peer=0x133001c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:16.113  2897-2933  qtidataservices         .qtidataservices                     I
2023-06-26 13:44:16.237  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253594.230: [Capo] Count NOT Validate in-motion sample2var=0.000283 (#sample 25)
2023-06-26 13:44:16.251   749-749   tombstoned              tombstoned                           I  received crash request for pid 2897
2023-06-26 13:44:16.251   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 2897 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:16.251  2897-2933  qtidataservices         .qtidataservices                     I  Wrote stack traces to tombstoned
2023-06-26 13:44:16.251   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:16.252  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 2897
2023-06-26 13:44:16.254  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 2894
2023-06-26 13:44:16.255  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 2894
2023-06-26 13:44:16.256   749-749   tombstoned              tombstoned                           I  registered intercept for pid 2894 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:16.257  2894-2905  .dataservices           .dataservices                        I  Thread[6,tid=2905,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a50fb20,peer=0x12ec01c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:16.257  2894-2905  .dataservices           .dataservices                        I
2023-06-26 13:44:16.334   749-749   tombstoned              tombstoned                           I  received crash request for pid 2894
2023-06-26 13:44:16.334   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 2894 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:16.335  2894-2905  .dataservices           .dataservices                        I  Wrote stack traces to tombstoned
2023-06-26 13:44:16.335  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 2894
2023-06-26 13:44:16.336   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:16.338  3387-3545  BtGatt.ScanManager      com.google.android.bluetooth         W  Moving filtered scan client to downgraded scan (scannerId 3)
2023-06-26 13:44:16.338  3387-3545  bt_stack                com.google.android.bluetooth         I  [INFO:le_scanning_manager.cc(167)] Scan in shim layer stopped
2023-06-26 13:44:16.338  3387-3423  bluetooth               com.google.android.bluetooth         I  packages/modules/Bluetooth/system/gd/hci/le_address_manager.cc:193 unregister_client: Client unregistered
2023-06-26 13:44:16.338  3387-3545  bt_stack                com.google.android.bluetooth         I  [INFO:le_scanning_manager.cc(345)] SetScanParameters in shim layer
2023-06-26 13:44:16.338  3387-3545  bt_stack                com.google.android.bluetooth         I  [INFO:le_scanning_manager.cc(167)] Scan in shim layer started
2023-06-26 13:44:16.339  1046-1046  vendor.qti..._transport<EMAIL_ADDRESS>D  SocRxDWakeup: Flow off->Change UART baudrate to 38.4kbs->send 0x00->Change UART baudrate to max->Flow on
2023-06-26 13:44:16.339  1046-1046  vendor.qti..._transport<EMAIL_ADDRESS>I  ## userial_vendor_ioctl: UART Flow Off
2023-06-26 13:44:16.340  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 2877
2023-06-26 13:44:16.342  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 2877
2023-06-26 13:44:16.342   749-749   tombstoned              tombstoned                           I  registered intercept for pid 2877 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:16.343  2877-2882  id.hbmsvmanager         com.android.hbmsvmanager             I  Thread[6,tid=2882,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a50fb20,peer=0x12e401c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:16.343  2877-2882  id.hbmsvmanager         com.android.hbmsvmanager             I
2023-06-26 13:44:16.350  1046-1046  vendor.qti..._transport<EMAIL_ADDRESS>I  ## userial_vendor_set_baud: 17
2023-06-26 13:44:16.360  1046-1046  vendor.qti..._transport<EMAIL_ADDRESS>I  SetBaudRate: in BOTHER
2023-06-26 13:44:16.360  1046-1046  vendor.qti..._transport<EMAIL_ADDRESS>I  ## userial_vendor_ioctl: UART Flow On
2023-06-26 13:44:16.360  1046-3499  vendor.qti...bs_handler<EMAIL_ADDRESS>I  ProcessIbsCmd: Received IBS_WAKE_ACK: 0xFC
2023-06-26 13:44:16.360  1046-3499  vendor.qti...bs_handler<EMAIL_ADDRESS>I  ProcessIbsCmd: Signal wack_cond_
2023-06-26 13:44:16.361  1046-3499  vendor.qti...bs_handler<EMAIL_ADDRESS>I  ProcessIbsCmd: Received IBS_WAKE_ACK: 0xFC
2023-06-26 13:44:16.361  1046-3499  vendor.qti...bs_handler<EMAIL_ADDRESS>I  ProcessIbsCmd: Signal wack_cond_
2023-06-26 13:44:16.361  1046-1046  vendor.qti...bs_handler<EMAIL_ADDRESS>D  DeviceWakeUp: Unblocked from waiting for FC
2023-06-26 13:44:16.361  3387-3423  bluetooth               com.google.android.bluetooth         I  packages/modules/Bluetooth/system/gd/hci/le_scanning_manager.cc:588 stop_scan: Scanning already stopped, return!
2023-06-26 13:44:16.361  3387-3423  bluetooth               com.google.android.bluetooth         I  packages/modules/Bluetooth/system/gd/hci/le_address_manager.cc:178 register_client: Client registered
2023-06-26 13:44:16.453  3906-4029  StateService            com.google.android.apps.scone        D  Country ISO: us
2023-06-26 13:44:16.477  2668-2668  GlobalActionsDialogLite com.android.systemui                 D  Service changed before actions created
2023-06-26 13:44:16.477  2668-2668  GlobalActionsDialogLite com.android.systemui                 D  Service changed before actions created
2023-06-26 13:44:16.480  3906-4029  StateService            com.google.android.apps.scone        D  Country ISO: us
2023-06-26 13:44:16.481  3906-3906  Connectivi...ateMachine com.google.android.apps.scone        D  [onServiceStateChanged] {subId=6} ServiceState= {mVoiceRegState=0(IN_SERVICE), mDataRegState=0(IN_SERVICE), mChannelNumber=66961, duplexMode()=1, mCellBandwidths=[], mOperatorAlphaLong=null, mOperatorAlphaShort=null, isManualNetworkSelection=false(automatic), getRilVoiceRadioTechnology=14(LTE), getRilDataRadioTechnology=14(LTE), mCssIndicator=unsupported, mNetworkId=-1, mSystemId=-1, mCdmaRoamingIndicator=-1, mCdmaDefaultRoamingIndicator=-1, mIsEmergencyOnly=false, isUsingCarrierAggregation=false, mArfcnRsrpBoost=0, mNetworkRegistrationInfos=[NetworkRegistrationInfo{ domain=PS transportType=WLAN registrationState=HOME networkRegistrationState=HOME roamingType=NOT_ROAMING accessNetworkTechnology=IWLAN rejectCause=0 emergencyEnabled=false availableServices=[DATA] cellIdentity=null voiceSpecificInfo=null dataSpecificInfo=null nrState=**** rRplmn= isUsingCarrierAggregation=false}, NetworkRegistrationInfo{ domain=CS transportType=WWAN registrationState=HOME networkRegistrationState=HOME roamingType=NOT_ROAMING accessNetworkTechnology=LTE rejectCause=0 emergencyEnabled=false availableServices=[VOICE,SMS,VIDEO] cellIdentity=null voiceSpecificInfo=VoiceSpecificRegistrationInfo { mCssSupported=false mRoamingIndicator=0 mSystemIsInPrl=0 mDefaultRoamingIndicator=0} dataSpecificInfo=null nrState=**** rRplmn=310260 isUsingCarrierAggregation=false}, NetworkRegistrationInfo{ domain=PS transportType=WWAN registrationState=HOME networkRegistrationState=HOME roamingType=NOT_ROAMING accessNetworkTechnology=LTE rejectCause=0 emergencyEnabled=false availableServices=[DATA] cellIdentity=null voiceSpecificInfo=null dataSpecificInfo=android.telephony.DataSpecificRegistrationInfo :{ maxDataCalls = 16 isDcNrRestricted = false isNrAvailable = false isEnDcAvailable = false mLteAttachResultType = 0 mLteAttachExtraInfo = 0 LteVopsSupportInfo :  mVopsSupport = 2 mEmcBearerSupport = 2 } nrState=**** rRplmn=310260 isUsingCarrierAggregation=false}], mNrFrequencyRange=0, mOperatorAlphaLongRaw=Google Fi, mOperatorAlphaShortRaw=Google Fi, mIsDataRoamingFromRegistration=false, mIsIwlanPreferred=false}
2023-06-26 13:44:16.481  3906-3906  Connectivi...ateMachine com.google.android.apps.scone        D  [onServiceStateChanged] {subId=6} vops:true
2023-06-26 13:44:16.481  2668-2668  StatusBarIconController com.android.systemui                 D  ignoring old pipeline callbacks, because the new mobile icons are enabled
2023-06-26 13:44:16.481  3906-11235 Connectivi...ateMachine com.google.android.apps.scone        D  [Default] {subId=6} processMessage(SERVICE_STATE_CHANGED) { when=0 what=544768 obj={mVoiceRegState=0(IN_SERVICE), mDataRegState=0(IN_SERVICE), mChannelNumber=66961, duplexMode()=1, mCellBandwidths=[], mOperatorAlphaLong=null, mOperatorAlphaShort=null, isManualNetworkSelection=false(automatic), getRilVoiceRadioTechnology=14(LTE), getRilDataRadioTechnology=14(LTE), mCssIndicator=unsupported, mNetworkId=-1, mSystemId=-1, mCdmaRoamingIndicator=-1, mCdmaDefaultRoamingIndicator=-1, mIsEmergencyOnly=false, isUsingCarrierAggregation=false, mArfcnRsrpBoost=0, mNetworkRegistrationInfos=[NetworkRegistrationInfo{ domain=PS transportType=WLAN registrationState=HOME networkRegistrationState=HOME roamingType=NOT_ROAMING accessNetworkTechnology=IWLAN rejectCause=0 emergencyEnabled=false availableServices=[DATA] cellIdentity=null voiceSpecificInfo=null dataSpecificInfo=null nrState=**** rRplmn= isUsingCarrierAggregation=false}, NetworkRegistrationInfo{ domain=CS transportType=WWAN registrationState=HOME networkRegistrationState=HOME roamingType=NOT_ROAMING accessNetworkTechnology=LTE rejectCause=0 emergencyEnabled=false availableServices=[VOICE,SMS,VIDEO] cellIdentity=null voiceSpecificInfo=VoiceSpecificRegistrationInfo { mCssSupported=false mRoamingIndicator=0 mSystemIsInPrl=0 mDefaultRoamingIndicator=0} dataSpecificInfo=null nrState=**** rRplmn=310260 isUsingCarrierAggregation=false}, NetworkRegistrationInfo{ domain=PS transportType=WWAN registrationState=HOME networkRegistrationState=HOME roamingType=NOT_ROAMING accessNetworkTechnology=LTE rejectCause=0 emergencyEnabled=false availableServices=[DATA] cellIdentity=null voiceSpecificInfo=null dataSpecificInfo=android.telephony.DataSpecificRegistrationInfo :{ maxDataCalls = 16 isDcNrRestricted = false isNrAvailable = false isEnDcAvailable = false mLteAttachResultType = 0 mLteAttachExtraInfo = 0 LteVopsSupportInfo :  mVopsSupport = 2 mEmcBearerSupport = 2 } nrState=**** rRplmn=310260 isUsingCarrierAggregation=false}], mNrFrequencyRange=0, mOperatorAlphaLongRaw=Google Fi, mOperatorAlphaShortRaw=Google Fi, mIsDataRoamingFromRegistration=false, mIsIwlanPreferred=false} target=agh }
2023-06-26 13:44:16.481  1922-5842  LocationAccessPolicy    system_server                        I  com.acmeaom.android.myradar is aware of fine but the app-ops permission is specifically denied.
2023-06-26 13:44:16.482  1922-5842  LocationAccessPolicy    system_server                        I  com.acmeaom.android.myradar is aware of coarse but the app-ops permission is specifically denied.
2023-06-26 13:44:16.482  3906-11235 Connectivi...ateMachine com.google.android.apps.scone        D  [updateServiceState] {subId=6} ServiceState Changed: 0 -> 0
2023-06-26 13:44:16.484  1922-5842  ContextImpl             system_server                        W  Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1270 android.content.Context.sendBroadcastMultiplePermissions:2476 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:3548 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1728 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:534
2023-06-26 13:44:16.486  1922-5842  ContextImpl             system_server                        W  Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1303 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:3553 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1728 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:534 android.os.Binder.execTransactInternal:1339
2023-06-26 13:44:16.487  1922-5842  ContextImpl             system_server                        W  Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1303 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:3562 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1728 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:534 android.os.Binder.execTransactInternal:1339
2023-06-26 13:44:16.488  1922-5842  ContextImpl             system_server                        W  Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1303 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:3568 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1728 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:534 android.os.Binder.execTransactInternal:1339
2023-06-26 13:44:16.490  3033-3033  ServiceStateProvider    com.android.phone                    D  subId=6
2023-06-26 13:44:16.491  1922-2220  ActivityManager         system_server                        D  sync unfroze 12253 com.google.android.cellbroadcastreceiver for 3
2023-06-26 13:44:16.493 12253-12253 CellBroadcastReceiver   com...android.cellbroadcastreceiver  D  onReceive Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 cmp=com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver (has extras) }
2023-06-26 13:44:16.493 12253-12253 CellBroadcastReceiver   com...android.cellbroadcastreceiver  D  onServiceStateChanged, ss: 0
2023-06-26 13:44:16.494 12253-12253 CellBroadcastReceiver   com...android.cellbroadcastreceiver  D  networkOperator: 310260
2023-06-26 13:44:16.495 12253-12253 CellBroadcastReceiver   com...android.cellbroadcastreceiver  D  update supported roaming operator as
2023-06-26 13:44:16.503  3033-3033  PhoneGlobals            com.android.phone                    W  Can't get phone with sub id = -1
2023-06-26 13:44:16.503  3033-3033  Telephony               com.android.phone                    I  TelecomAccountTelephonyCallback: onServiceStateChanged: newState=0, mServiceState=0
2023-06-26 13:44:16.506  3033-3033  Telephony               com.android.phone                    I  isRttCurrentlySupported -- regular acct, hasVoiceAvailability: true
                                                                                isRttSupported: false
                                                                                alwaysAllowWhileRoaming: false
                                                                                isRoaming: false
                                                                                isOnWfc: false
2023-06-26 13:44:16.514   749-749   tombstoned              tombstoned                           I  received crash request for pid 2877
2023-06-26 13:44:16.514   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 2877 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:16.514  2877-2882  id.hbmsvmanager         com.android.hbmsvmanager             I  Wrote stack traces to tombstoned
2023-06-26 13:44:16.514   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:16.514  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 2877
2023-06-26 13:44:16.516  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 2837
2023-06-26 13:44:16.518  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 2837
2023-06-26 13:44:16.518   749-749   tombstoned              tombstoned                           I  registered intercept for pid 2837 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:16.518  2837-2842  rkstack.process         com.android.networkstack.process     I  Thread[5,tid=2842,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a5132c0,peer=0x148001c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:16.519  2837-2842  rkstack.process         com.android.networkstack.process     I
2023-06-26 13:44:16.604   749-749   tombstoned              tombstoned                           I  received crash request for pid 2837
2023-06-26 13:44:16.604   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 2837 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:16.605   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:16.605  2837-2842  rkstack.process         com.android.networkstack.process     I  Wrote stack traces to tombstoned
2023-06-26 13:44:16.605  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 2837
2023-06-26 13:44:16.608  1922-12957 ActivityManager         system_server                        I  Collecting stacks for pid 2668
2023-06-26 13:44:16.614  1922-12957 system_server           system_server                        I  libdebuggerd_client: started dumping process 2668
2023-06-26 13:44:16.614   749-749   tombstoned              tombstoned                           I  registered intercept for pid 2668 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:16.615  2668-2674  ndroid.systemui         com.android.systemui                 I  Thread[5,tid=2674,WaitingInMainSignalCatcherLoop,Thread*=0xb40000754a5132c0,peer=0x12c801c8,"Signal Catcher"]: reacting to signal 3
2023-06-26 13:44:16.615  2668-2674  ndroid.systemui         com.android.systemui                 I
2023-06-26 13:44:16.779  1082-1251  CHRE<EMAIL_ADDRESS>I  @ 253594.772: [Capo] Count NOT Validate in-motion sample2var=0.000255 (#sample 25)
2023-06-26 13:44:17.019   749-749   tombstoned              tombstoned                           I  received crash request for pid 2668
2023-06-26 13:44:17.019   749-749   tombstoned              tombstoned                           I  found intercept fd 512 for pid 2668 and type kDebuggerdJavaBacktrace
2023-06-26 13:44:17.020  2668-2674  ndroid.systemui         com.android.systemui                 I  Wrote stack traces to tombstoned
2023-06-26 13:44:17.020  1922-12957 system_server           system_server                        I  libdebuggerd_client: done dumping process 2668
2023-06-26 13:44:17.020   749-749   tombstoned              tombstoned                           W  skipping tombstone file creation due to intercept
2023-06-26 13:44:17.023  1922-12957 ActivityManager         system_server                        I  dumpStackTraces nativepids=null
2023-06-26 13:44:17.023  1922-12957 ActivityManager         system_server                        I  dumpStackTraces extraPids=[]
2023-06-26 13:44:17.024  1922-12957 ActivityManager         system_server                        I  Done dumping
2023-06-26 13:44:17.028  1922-12957 ActivityManager         system_server                        E  ANR in com.zulipmobile (com.zulipmobile/.MainActivity)
                                                                                PID: 10357
                                                                                Reason: Input dispatching timed out (fad5352 com.zulipmobile/com.zulipmobile.MainActivity (server) is not responding. Waited 5000ms for MotionEvent)
                                                                                Parent: com.zulipmobile/.MainActivity
                                                                                ErrorId: 10348bba-335f-474d-9b56-db77afd03054
                                                                                Frozen: false
                                                                                Load: 2.42 / 2.44 / 2.53
                                                                                ----- Output from /proc/pressure/memory -----
                                                                                some avg10=0.00 avg60=0.05 avg300=0.17 total=1177794752
                                                                                full avg10=0.00 avg60=0.01 avg300=0.05 total=660323581
                                                                                ----- End output from /proc/pressure/memory -----
                                                                                ----- Output from /proc/pressure/cpu -----
                                                                                some avg10=1.86 avg60=7.31 avg300=5.32 total=6357599806
                                                                                ----- End output from /proc/pressure/cpu -----
                                                                                ----- Output from /proc/pressure/io -----
                                                                                some avg10=0.00 avg60=0.15 avg300=0.52 total=3300686045
                                                                                full avg10=0.00 avg60=0.08 avg300=0.31 total=2375960036
                                                                                ----- End output from /proc/pressure/io -----

                                                                                CPU usage from 279845ms to -1ms ago (2023-06-26 13:39:33.740 to 2023-06-26 13:44:13.585):
                                                                                26% 10357/com.zulipmobile: 22% user + 3.7% kernel / faults: 121931 minor 258 major
                                                                                21% 28724/com.google.android.apps.messaging: 16% user + 4.7% kernel / faults: 352717 minor 3395 major
                                                                                17% 1922/system_server: 12% user + 4.6% kernel / faults: 91955 minor 160 major
                                                                                16% 4455/com.google.android.inputmethod.latin: 14% user + 1.9% kernel / faults: 80378 minor 768 major
                                                                                14% 651/surfaceflinger: 10% user + 4.2% kernel / faults: 512 minor 28 major
                                                                                5.1% 2668/com.android.systemui: 3.9% user + 1.2% kernel / faults: 47509 minor 233 major
                                                                                4.5% 10690/android.process.acore: 2.8% user + 1.6% kernel / faults: 27986 minor 26 major
                                                                                3.8% 654/vendor.qti.hardware.display.composer-service: 2.3% user + 1.5% kernel / faults: 2092 minor 41 major
                                                                                3.1% 1461/adbd: 1.2% user + 1.9% kernel / faults: 67360 minor 1 major
                                                                                3.1% 8584/android.process.acore: 2% user + 1.1% kernel / faults: 18729 minor 2 major
                                                                                19% TOTAL: 12% user + 6.3% kernel + 0.1% iowait + 0.8% irq + 0.2% softirq
                                                                                CPU usage from 22ms to 724ms later (2023-06-26 13:44:13.607 to 2023-06-26 13:44:14.309):
                                                                                75% 1922/system_server: 37% user + 37% kernel / faults: 3673 minor 583 major
                                                                                44% 1955/Signal Catcher: 28% user + 15% kernel
                                                                                20% 12962/AnrAuxiliaryTas: 6.2% user + 14% kernel
                                                                                1.5% 1958/HeapTaskDaemon: 1.5% user + 0% kernel
                                                                                1.5% 1964/binder:1922_2: 0% user + 1.5% kernel
                                                                                1.5% 2219/android.bg: 0% user + 1.5% kernel
                                                                                1.5% 2514/SensorService: 1.5% user + 0% kernel
                                                                                1.5% 2517/NativeTombstone: 0% user + 1.5% kernel
                                                                                1.5% 2522/CachedAppOptimi: 0% user + 1.5% kernel
                                                                                1.5% 3151/CallAudioModeSt: 1.5% user + 0% kernel
                                                                                1.5% 12957/AnrConsumer: 0% user + 1.5% kernel
                                                                                38% 10357/com.zulipmobile: 26% user + 12% kernel / faults: 11417 minor 25 major
                                                                                31% 10362/Signal Catcher: 19% user + 12% kernel
                                                                                5.2% 10386/RenderThread: 5.2% user + 0% kernel
                                                                                7.4% 651/surfaceflinger: 5.9% user + 1.4% kernel
                                                                                4.4% 651/surfaceflinger: 2.9% user + 1.4% kernel
                                                                                1.4% 694/binder:651_2: 1.4% user + 0% kernel
                                                                                1.4% 757/HwBinder:651_1: 1.4% user + 0% kernel
                                                                                1.4% 759/TimerDispatch: 1.4% user + 0% kernel
                                                                                1.4% 765/RegionSampling: 1.4% user + 0% kernel
                                                                                6.2% 1461/adbd: 3.1% user + 3.1% kernel / faults: 339 minor
                                                                                3.1% 1461/adbd: 1.5% user + 1.5% kernel
                                                                                3.1% 9455/UsbFfs-worker: 0% user + 3.1% kernel
                                                                                2.9% 654/vendor.qti.hardware.display.composer-service: 1.4% user + 1.4% kernel / faults: 2 minor
                                                                                2.9% 28108/HwBinder:654_3: 1.4% user + 1.4% kernel
                                                                                3.8% 30485/kworker/u16:8-MODEM_CNTL: 0% user + 3.8% kernel / faults: 2 minor
                                                                                3.8% 32021/kworker/u16:13-kverityd: 0% user + 3.8% kernel / faults: 2 minor
                                                                                1.4% 11/rcu_preempt: 0% user + 1.4% kernel
                                                                                1.4% 12/rcu_sched: 0% user + 1.4% kernel
                                                                                1.4% 48/rcuop/4: 0% user + 1.4% kernel
                                                                                1.4% 64/rcuop/6: 0% user + 1.4% kernel
                                                                                1.4% 313/kgsl_worker_thr: 0% user + 1.4% kernel
                                                                                1.4% 504/crtc_commit:105: 0% user + 1.4% kernel
                                                                                1.4% 505/crtc_event:105: 0% user + 1.4% kernel
                                                                                1.4% 595/logd: 0% user + 1.4% kernel
                                                                                1.5% 1099/rlsservice: 0% user + 1.5% kernel
2023-06-26 13:44:17.028  1922-12957 ActivityManager         system_server                        E      1.5% 8708/rlsservice: 0% user + 1.5% kernel
                                                                                1.5% 1159/vendor.google.wifi_ext-service-vendor: 0% user + 1.5% kernel / faults: 11 minor
                                                                                1.6% 4040/kworker/u17:12-kgsl-events: 0% user + 1.6% kernel
                                                                                1.6% 5605/kworker/u16:6-SENSORS_DCI: 0% user + 1.6% kernel / faults: 4 minor
                                                                                1.7% 11644/kworker/3:1-mm_percpu_wq: 0% user + 1.7% kernel
                                                                                1.8% 22785/kworker/u16:16+CDSP_CNTL: 0% user + 1.8% kernel
                                                                                1.8% 27215/kworker/u16:12-kgsl_devfreq_wq: 0% user + 1.8% kernel
                                                                                23% TOTAL: 11% user + 10% kernel + 0.9% iowait + 0.7% irq + 0.1% softirq
2023-06-26 13:44:17.031  1922-12957 ActivityManager         system_server                        D  Completed ANR of com.zulipmobile in 3556ms, latency 0ms

Stack trace posted above, might be an underlying library update, but unsure where to start looking. Any hints?

Thanks for the report, and for taking the time to provide that stacktrace! That sounds like a very frustrating issue.
This looks like an error that has affected React Native apps for years: https://github.com/facebook/react-native/issues/17530. React Native is the framework used to build zulip-mobile, the current Zulip mobile apps. It looks like a purported fix was actually merged in React Native quite recently: https://github.com/facebook/react-native/commit/98789e9da646e889632aaf14af4f39841c79ea10. That change doesn't appear in any React Native releases yet, but I assume it will soon if it doesn't get reverted.
As a workaround, does it help if you uninstall and reinstall the app?
Realistically, with the effort required to upgrade to new React Native versions as they come out, our most likely path to a permanent fix is to develop and release the new Zulip mobile apps built in Flutter.

Linking an old discussion of a same-looking error: https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/RN.2067.3A.20add.20to.20styles.2Exml.3F/near/1395349

@chrisbobbe understood, both efforts are substantial. It makes sense to put that coding time into flutter if that's the path forward vs the myriad of react upgrades required to get from .68 to .72.
I did a complete erase of the app, delete cache, delete storage, and reinstall, and the crash remains the same.

I did a complete erase of the app, delete cache, delete storage, and reinstall, and the crash remains the same.

Dang. Thanks for the update (and the original report).
We'll keep an eye on this issue. If we hear more reports of it as the Android 14 beta progresses, so that it sounds like it's widely affecting Android 14 users, then we may have to take further action on it.
Depending on how early Google sends Android 14 to general release (likely either August or September, based on history), we may have zulip-flutter to beta stage by then. In that case I think the recommendation for anyone who's enough of an early adopter to jump straight on the new OS release will be to use the zulip-flutter beta :slightly_smiling_face:
If this issue affects a wide range of React Native apps on Android 14, then there might also be further developments upstream that give us more options for fixing it — for example the fix might get backported to older release series.
For anyone else seeing this issue, please chime in here to help us gauge how widespread it is. In the meantime, the best workaround will be to open Zulip in your mobile device's web browser.

@gnprice while thinking about flutter, there are a few other features missing from the zulip mobile client such as unread badge counts on iOS and Android. Is there a good place in the flutter dev repo to post these?

Indeed! Our tracker for that project is https://github.com/zulip/zulip-flutter/issues, and it's accepting new issues.
When filing an issue there, it would be helpful to check a few things first, to minimize its chance of being closed:

Has the feature already been implemented? Some features will naturally take less effort to implement in zulip-flutter than in zulip-mobile, and it may already be done. This will become easier to check during the public beta period, of course, but in the meantime you can send a quick question in #mobile or #mobile-team in the Zulip development community.
Is there an open issue in zulip-flutter tracking the feature already? (For example, badge counts on iOS is open as zulip/zulip-flutter#153.)
Is there an open issue in zulip-mobile tracking the feature? We have a plan to sweep through the zulip-mobile issues, opening zulip-flutter issues for points that also apply there.

Linking CZO discussion: https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/RN.2067.3A.20add.20to.20styles.2Exml.3F/near/1599036

@darren1713 reports that the crashes stopped upon upgrading to v27.213, where we disable Sentry: https://github.com/zulip/zulip-mobile/issues/5766#issuecomment-1741143191
That suggests that these had the same cause as #5757, related to Sentry. Details of that issue here: https://github.com/zulip/zulip-mobile/issues/5757#issuecomment-1728692990
Closing this issue because it appears that disabling Sentry resolved it. We have an open issue #5757 for re-enabling Sentry in our JavaScript and Kotlin code, but with its native code kept inactive, which should avoid the crashes it was causing. When we do that, I'll definitely be interested in hearing whether the crashing remains fixed for @darren1713, as well as for the folks in the #5757 thread; I'll update when we have a build to try out. Thanks again @darren1713 for the report and the updates!

Recording for the thread (though of course I'm glad that v27.213 seems to have fixed these crashes!):
I think we've been getting events with this issue's error output much more frequently on Android versions other than 14, than on Android 14. And in both cases, the frequency graph doesn't have the ominous-uptick shape that was characteristic of the crashes that became the focus of #5757.

Android 14
Not Android 14

Hmm I see, thanks for pointing that out.
Looking at numbers for these crashes, I'm a bit puzzled now, but in any case it no longer seems like v27.213 fixed these crashes in general (even though they apparently did so for @darren1713). So I'll reopen.
Specifically, in the data Google Play gives us, we've been seeing this crash just as often on v27.213 as we did on older versions. Our total number of crashes has gone way down — way back down, to where it was before #5757 emerged, after being elevated for a couple of weeks. But this one is unchanged.
Puzzlingly, though, in the Google Play data I see zero crash reports from Android 14 that have anything like this stack trace. There's plenty of reports from Android 14 that look like #5757 — so it's not like Android 14 isn't reporting data for some reason — but none for this issue. (Those data only go back 60 days, so don't cover when @darren1713 saw the crash posted at https://github.com/zulip/zulip-mobile/issues/5741#issuecomment-1607952269 ; though it's also possible his device isn't reporting crashes to Google Play.)
So, maybe Android 14 somehow fixed this? We'll get a better idea once it rolls out to a general release… err, which I guess just happened today, so we'll get a better idea very soon as people upgrade and we start having a much larger share of our users on it.

@gnprice Great details there. Some quick behavior notes on my Android 14 experience, I'm on Pixel 5, running Android beta, and have gone through Android 14 beta releases UP1, UP2, UP3, and currently on UP4, with all of them exhibiting the same crash in 30 seconds or less behavior and grabbed the log that opened this ticket. The update to UP4 was about 6 weeks ago, crashes remained, and then 2 weeks ago the crashed stopped out of the blue, so I went to investigate. Found the zulip app had a new release, so dug into changelog and what might be the connection. I don't have any other relevant data so technically it could be something else that was patched in the latest release quite honestly, but wanted to point this out as an item to investigate before re-enabling sentry. PS: Glad to test any builds you want to check for this error on Android 14.

@darren1713 Thanks for those further details!
We just today posted a v27.214 release to beta; it re-enables Sentry, but leaving the native side disabled (i.e. it does #5766). In our own testing that continues to prevent the crashes, just like v27.213 did by disabling Sentry completely, but I'd definitely be interested in hearing how it works for you too. If you're not already on the beta channel, see here to join.

We've now sent v27.216 to all users. As discussed at #5778, it turned out that this:

We just today posted a v27.214 release to beta; it re-enables Sentry, but leaving the native side disabled (i.e. it does #5766). In our own testing that continues to prevent the crashes, just like v27.213 did by disabling Sentry completely

did not hold when we got wider testing from our beta users, so for v27.216 we went back to disabling Sentry entirely (on Android) like v27.213 did.
@darren1713 I'll be curious to hear whether you've seen the "crash in 30 seconds or less" symptoms on v27.216, or whether you do after upgrading if you haven't yet.