Develop Bugs

Has anyone have MATICS folder in LG G4?

Hi. I'm korean and i'm using Korea Telecom's LG G4 (LG-F500K) (So I'm not good at english. Plz understand it..)
2~4 Weeks ago, suddenly in my LG G4's Storage, has created 'MATICS' folder.
I asked Korea LG Online Service senter, and they said they sent my log file to their lab to analyze it. They'll be contact again to me but they hasn't no contact to me.
So i searched google, xda-forum, korea LG forum but each has different answer. I feel desperate because I can't find a solution with MATICS folder.. It had many log file (When i turned on the Mobile DATA, Alarm, etc...)
So i want to know what is MATICS folder, and how to solve don't creat MATICS folder with log file.
This is a part of my log file:
04-05 22:07:03.489 com.smartmoca.IntentReceiver: SmartMOCA onReceive!!! : com.lge.moca.receive.Event_Alarm
04-05 22:07:03.534 com.smartmoca.IntentReceiver: SmartMOCA ALARM_CODE!!! : 8204
04-05 22:16:32.327 com.smartmoca.IntentReceiver: SmartMOCA onReceive!!! : com.lge.moca.receive.Event_Alarm
04-05 22:16:32.332 com.smartmoca.IntentReceiver: SmartMOCA ALARM_CODE!!! : 8204
04-05 22:16:58.282 com.smartmoca.IntentReceiver: SmartMOCA onReceive!!! : com.lge.moca.receive.Event_Alarm
04-05 22:16:58.288 com.smartmoca.IntentReceiver: SmartMOCA ALARM_CODE!!! : 8204
I'm using banking app and card app, so MATICS folder makes me create an air of anxiety.
Have a nice day. Plz how to solve it my problem.
P.S. I want to attach LG's E-MAIL answer, but i don't know how to attach it.

아크레 said:
Hi. I'm korean and i'm using Korea Telecom's LG G4 (LG-F500K) (So I'm not good at english. Plz understand it..)
2~4 Weeks ago, suddenly in my LG G4's Storage, has created 'MATICS' folder.
I asked Korea LG Online Service senter, and they said they sent my log file to their lab to analyze it. They'll be contact again to me but they hasn't no contact to me.
So i searched google, xda-forum, korea LG forum but each has different answer. I feel desperate because I can't find a solution with MATICS folder.. It had many log file (When i turned on the Mobile DATA, Alarm, etc...)
So i want to know what is MATICS folder, and how to solve don't creat MATICS folder with log file.
This is a part of my log file:
04-05 22:07:03.489 com.smartmoca.IntentReceiver: SmartMOCA onReceive!!! : com.lge.moca.receive.Event_Alarm
04-05 22:07:03.534 com.smartmoca.IntentReceiver: SmartMOCA ALARM_CODE!!! : 8204
04-05 22:16:32.327 com.smartmoca.IntentReceiver: SmartMOCA onReceive!!! : com.lge.moca.receive.Event_Alarm
04-05 22:16:32.332 com.smartmoca.IntentReceiver: SmartMOCA ALARM_CODE!!! : 8204
04-05 22:16:58.282 com.smartmoca.IntentReceiver: SmartMOCA onReceive!!! : com.lge.moca.receive.Event_Alarm
04-05 22:16:58.288 com.smartmoca.IntentReceiver: SmartMOCA ALARM_CODE!!! : 8204
I'm using banking app and card app, so MATICS folder makes me create an air of anxiety.
Have a nice day. Plz how to solve it my problem.
P.S. I want to attach LG's E-MAIL answer, but i don't know how to attach it.
Click to expand...
Click to collapse
install root explorer then find data/data/com.lge.matics and delete ,find data/user/0/com.lge.matics and delete,find system/app/MOCA and delete that is all.

please help in call audio

Is anyone having this problem whilst building and testing roms , Can someone review this cat log and suggest a fix its for in call volume this is the problem:
Code:
02-05 18:10:40.748 8670 8670 W System : ClassLoader referenced unknown path: /system/priv-app/Dialer/lib/arm
02-05 18:10:40.759 7021 7021 I InCall : CallList - onUpdate - [Call_2, ACTIVE, [Capabilities: CAPABILITY_HOLD CAPABILITY_SUPPORT_HOLD CAPABILITY_MUTE CAPABILITY_CANNOT_DOWNGRADE_VIDEO_TO_AUDIO], [Properties:], children:[], parent:null, conferenceable:[], videoState:Audio Only, mSessionModificationState:0, VideoSettingsCameraDir:-1), mIsActivSub:false]
02-05 18:10:40.759 7021 7021 I InCall : InCallPresenter - Phone switching state: INCALL -> INCALL
02-05 18:10:40.761 7021 7021 E QtiImsExtUtils: getImsPhoneId failed. Exception = org.codeaurora.ims.QtiImsException: ImsService is not running
02-05 18:10:40.761 7021 7021 E QtiImsExtUtils: getConfigForPhoneId phoneId is invalid
02-05 18:10:40.761 7021 7021 E QtiImsExtUtils: isCarrierConfigEnabled bundle is null
02-05 18:10:40.761 7021 7021 E QtiImsExtUtils: getImsPhoneId failed. Exception = org.codeaurora.ims.QtiImsException: ImsService is not running
02-05 18:10:40.761 7021 7021 E QtiImsExtUtils: getConfigForPhoneId phoneId is invalid
02-05 18:10:40.761 7021 7021 E QtiImsExtUtils: isCarrierConfigEnabled bundle is null
02-05 18:10:40.789 531 531 I hash_map_utils: key: 'volume_boost' value: ''
02-05 18:10:40.789 531 3072 I hash_map_utils: key: 'volume_boost' value: ''
02-05 18:10:40.792 7021 7021 E QtiImsExtUtils: getImsPhoneId failed. Exception = org.codeaurora.ims.QtiImsException: ImsService is not running
02-05 18:10:40.792 7021 7021 E QtiImsExtUtils: getConfigForPhoneId phoneId is invalid
02-05 18:10:40.792 7021 7021 E QtiImsExtUtils: isCarrierConfigEnabled bundle is null
02-05 18:10:40.792 7021 7021 E QtiImsExtUtils: getImsPhoneId failed. Exception = org.codeaurora.ims.QtiImsException: ImsService is not running
02-05 18:10:40.792 7021 7021 E QtiImsExtUtils: getConfigForPhoneId phoneId is invalid
02-05 18:10:40.792 7021 7021 E QtiImsExtUtils: isCarrierConfigEnabled bundle is null

[HELP] Google Camera crashing with cam2api enable and rooted on Pixel Experience

Hello everyone!
I need to record 1080p60fps videos on my Redmi Note 5 (pro) global. I have official Pixel Experience rom. I don't really care about Google Cam, but it seems like the only app that allows to record in 60fps (open camera record in 4k, but not in 1080p60), so I tried to install it. I have Magisk v16.0 with Camera2 API Enabler installed (checked using getprop and it is enabled), but I practically every google camera mod I tried is crashing. Here is log (same for all):
HTML:
07-18 11:27:15.713 746 796 E ANDR-PERF-RESOURCEQS: Failed to apply optimization [2, 0]
07-18 11:27:15.779 3205 3475 D AudioService: Stream muted, skip playback
07-18 11:27:15.780 3205 8023 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.Pixel2Mod/com.android.camera.CameraLauncher bnds=[30,880][234,1172]} from uid 10026
07-18 11:27:15.835 3205 3963 I ActivityManager: Start proc 9448:com.google.android.Pixel2Mod/u0a122 for activity com.google.android.Pixel2Mod/com.android.camera.CameraLauncher
07-18 11:27:15.923 4495 4495 I MicroDetector: Keeping mic open: false
07-18 11:27:15.923 4495 4288 I DeviceStateChecker: DeviceStateChecker cancelled
07-18 11:27:15.923 4495 2001 I AudioController: internalShutdown
07-18 11:27:15.924 4495 9439 I MicroRecognitionRunner: Stopping hotword detection.
07-18 11:27:15.924 4495 1171 I MicroRecognitionRunner: Detection finished
07-18 11:27:15.952 720 7863 D audio_hw_primary: in_standby: enter: stream (0xe64c4800) usecase(18: audio-record)
07-18 11:27:15.993 9448 9466 I CameraManagerGlobal: Connecting to camera service
07-18 11:27:16.000 9448 9466 W CameraManagerGlobal: [soar.cts] ignore the status update of camera: 2
07-18 11:27:16.001 9448 9466 W CameraManagerGlobal: [soar.cts] ignore the status update of camera: 3
07-18 11:27:16.003 833 891 I mmid : select timeout: wait for receiving msg
07-18 11:27:16.007 720 7863 D audio_hw_primary: disable_audio_route: reset and update mixer path: audio-record
07-18 11:27:16.008 720 7863 D soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_id 18 of type 1 for Event 2, with Raise=0
07-18 11:27:16.008 720 7863 D hardware_info: hw_info_append_hw_type : device_name = voice-rec-mic
07-18 11:27:16.008 720 7863 D audio_hw_primary: disable_snd_device: snd_device(95: voice-rec-mic)
07-18 11:27:16.008 720 7863 D msm8916_platform: platform_split_snd_device: snd_device(95) num devices(0) new_snd_devices(0)
07-18 11:27:16.011 720 7863 I soundtrigger: audio_extn_sound_trigger_update_device_status: device 0x5f of type 1 for Event 0, with Raise=1
07-18 11:27:16.011 720 7863 D sound_trigger_platform: platform_stdev_check_and_update_concurrency: concurrency active 0, tx 0, rx 0, concurrency session_allowed 1
07-18 11:27:16.013 722 1748 I QCamera : <HAL><INFO> getCameraInfo: 397: Camera id 0 API version 256
07-18 11:27:16.013 722 1748 I QCamera : <HAL><INFO> getCamInfo: 10404: camera 0 resource cost is 100
07-18 11:27:16.013 720 7863 D audio_hw_primary: in_set_parameters: enter: kvpairs=routing=0
07-18 11:27:16.014 2715 3296 I SoundTriggerHwService::Module: onCallbackEvent no clients
07-18 11:27:16.015 4495 2002 I MicrophoneInputStream: mic_close SR : 16000 CC : 16 SO : 1999
07-18 11:27:16.017 720 7863 D audio_hw_primary: adev_close_input_stream: enter:stream_handle(0xe64c4800)
07-18 11:27:16.017 720 7863 D audio_hw_primary: in_standby: enter: stream (0xe64c4800) usecase(18: audio-record)
07-18 11:27:16.035 9448 9466 I CAM_MaxNativeMemory: Max native memory overridden (device): 1160
07-18 11:27:16.036 9448 9466 I CAM_MemoryManager: Max native memory: 1160000000 bytes. (1160MB).
07-18 11:27:16.046 9448 9448 I CAM_Instrumentation: CameraActivity: App OnCreate duration: 8ms
07-18 11:27:16.047 9448 9448 I CAM_Instrumentation: CameraActivity: App OnCreate End to Activity OnCreate Start: 24ms
07-18 11:27:16.047 9448 9448 I CAM_GcaActivity: [f75a52b] GcaActivity#onCreate
07-18 11:27:16.050 9448 9466 W linker : "/data/app/com.google.android.Pixel2Mod-jEj88MEA0xdz3YI6ZIKzOA==/lib/arm64/libgcam_swig_jni.so" unused DT entry: type 0xf arg 0x46e68
07-18 11:27:16.054 722 1748 I QCamera : <HAL><INFO> getCameraInfo: 397: Camera id 1 API version 256
07-18 11:27:16.054 722 1748 I QCamera : <HAL><INFO> getCamInfo: 10404: camera 1 resource cost is 100
07-18 11:27:16.064 9448 9448 I CAM_CameraUiInflater: Initializing Window Flags
07-18 11:27:16.066 9448 9467 I CAM_PermissionsChecker: Checking for critical permissions.
07-18 11:27:16.076 3205 3963 I ActivityManager: START u0 {act=android.content.pm.action.REQUEST_PERMISSIONS pkg=com.android.packageinstaller cmp=com.android.packageinstaller/.permission.ui.GrantPermissionsActivity (has extras)} from uid 10122
07-18 11:27:16.104 9448 9448 I CAM_CameraUiInflater: Initializing Camera Ui
07-18 11:27:16.106 9448 9466 I CAM_MemoryManager: Registering feature: HDR_PLUS
07-18 11:27:16.108 9448 9466 I CAM_MemoryManager: State updated. Free Memory: 1160000000
07-18 11:27:16.203 9448 9448 I CAM_CameraUiInflater: Initializing Action Bar
07-18 11:27:16.213 9448 9448 I CAM_Instrumentation: CameraActivity: OnCreate duration: 166ms
07-18 11:27:16.213 9448 9448 I CAM_GcaActivity: [f75a52b] GcaActivity#onStart
07-18 11:27:16.215 9448 9448 I CAM_Instrumentation: CameraActivity: OnCreate End to OnResume Start: 2ms
07-18 11:27:16.215 9448 9448 I CAM_GcaActivity: [f75a52b] GcaActivity#onResume
07-18 11:27:16.216 9448 9448 I CAM_Instrumentation: CameraActivity: OnResume duration: 0ms
07-18 11:27:16.220 9448 9474 D OpenGLRenderer: HWUI GL Pipeline
07-18 11:27:16.226 9448 9448 I CAM_GcaActivity: [f75a52b] GcaActivity#onPause
07-18 11:27:16.239 9448 9448 I CAM_MemoryManager: State updated. Free Memory: 1160000000
07-18 11:27:16.239 9448 9448 I CAM_MemoryManager: State updated. Free Memory: 1160000000
07-18 11:27:16.239 9448 9448 D AndroidRuntime: Shutting down VM
07-18 11:27:16.239 9448 9448 E AndroidRuntime: FATAL EXCEPTION: main
07-18 11:27:16.239 9448 9448 E AndroidRuntime: Process: com.google.android.Pixel2Mod, PID: 9448
07-18 11:27:16.239 9448 9448 E AndroidRuntime: java.lang.NullPointerException: Attempt to get length of null array
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at cok.a(Unknown Source:166)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at ccv.a(Unknown Source:54)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at com.a(Unknown Source:58)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at jxg.a(Unknown Source:15)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at con.run(Unknown Source:36)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at gvc.run(Unknown Source:8)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at hzy.run(Unknown Source:2)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at java.lang.Thread.run(Thread.java:764)
07-18 11:27:16.239 9448 9448 E AndroidRuntime: at avv.run(Unknown Source:5)
07-18 11:27:16.244 9448 9448 E CAM_SilentFeedback: Could not find SilentFeedbackService, not sending crash info.
07-18 11:27:16.248 3205 3298 I ActivityManager: Showing crash dialog for package com.google.android.Pixel2Mod u0
07-18 11:27:17.333 14120 14231 D ClClient: Not sending keepalive. Current connection state=STOPPED
07-18 11:27:18.877 4495 1171 I EventLogSendingHelper: Sending log events.
07-18 11:27:19.006 833 891 I mmid : select timeout: wait for receiving msg
07-18 11:27:19.195 4470 4525 I cr_BindingManager: Release moderate connections: 1
07-18 11:27:22.009 833 891 I mmid : select timeout: wait for receiving msg
07-18 11:27:25.811 3205 3295 W ActivityManager: Launch timeout has expired, giving up wake lock!
07-18 11:27:25.012 833 891 I mmid : select timeout: wait for receiving msg
07-18 11:27:27.333 14120 14231 D ClClient: Not sending keepalive. Current connection state=STOPPED
07-18 11:27:28.015 833 891 I mmid : select timeout: wait for receiving msg
It immediately crashes right after I open it. It just asks for camera and microphone permissions. I think there is some internal issue (maybe?). Crashing at:
HTML:
java.lang.NullPointerException: Attempt to get length of null array

I've had the same error.
So i enabled cam2api in build.prop manualy
Steps to follow on this ROM, else you will face force closes
1. Go to /system/ & copy build.prop to internal storage for backup
2. Open the system/build.prop with text editor
3. Scroll to the last & leave a space after the last line
4. Add the below lines
#Camera2 API
persist.camera.HAL3.enabled=1
5. reboot

burish said:
I've had the same error.
So i enabled cam2api in build.prop manualy
Steps to follow on this ROM, else you will face force closes
1. Go to /system/ & copy build.prop to internal storage for backup
2. Open the system/build.prop with text editor
3. Scroll to the last & leave a space after the last line
4. Add the below lines
#Camera2 API
persist.camera.HAL3.enabled=1
5. reboot
Click to expand...
Click to collapse
OH YEEEEAAAAAHHH! Thanks a lot! It is working now!

Damm. It's working, but there is no 60fps recording. Any ideas?

Which Version of GCAM do you use?
In https://forum.xda-developers.com/redmi-note-5-pro/themes/app-arnova8g2s-google-camera-port-t3784423 its actually listed as a feature
Maybe you should try the listed gcam from 1 post

I am also on Pixel Experience. For me Arnovas GCAM Pixel2 Mod v.8.1. works without any bugs. I flashed camera2api as zip file trough twrp. Now im waiting for stock camera port.

com.android.statementservice regularly crashing on LineageOS for microg

Hi,
I have just installed LineageOS for microg 19 (19-20220522-microg-bramble) on my Pixel 4a 5g and I am receiving a regular popup every few minutes saying that "Intent Filter Verification Service has stopped".
From what I have read this is used to call another application on the phone (based on what type of thing needs to be handled)??
The logs I am getting with logcat do not seem to lead me towards anything (see below from two examples). I'm not sure if anyone has any suggestions on what could be causing this or where else I can look??
My suspicion is that this is something to do with not having the google apps (using microg instead) but not sure. I did find one other mention of it here, but no solution
Note: I did have LineageOS for microg 18 installed previously which did not exhibit this behaviour...
Example1:
Code:
05-31 23:53:49.627 966 966 D Zygote : Forked child process 10622
05-31 23:53:49.628 1718 2114 I ActivityManager: Start proc 10622:com.android.statementservice/u0a74 for service {com.android.statementservice/androidx.work.impl.background.systemjob.SystemJobService}
05-31 23:53:49.632 10622 10622 I libc : SetHeapTaggingLevel: tag level set to 0
05-31 23:53:49.644 1357 1429 I adbd : jdwp connection from 10622
05-31 23:53:49.646 10622 10622 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
05-31 23:53:49.638 0 0 I : c7 10622 binder: 10622:10622 ioctl 40046210 7fea0fb8d4 returned -22
05-31 23:53:49.651 1718 14826 D CompatibilityChangeReporter: Compat change id reported: 168419799; UID 10074; state: DISABLED
05-31 23:53:49.655 10622 10622 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10074; state: DISABLED
05-31 23:53:49.658 10622 10622 D ApplicationLoaders: Returning zygote-cached class loader: /system/framework/android.test.base.jar
05-31 23:53:49.667 10622 10622 V GraphicsEnvironment: ANGLE Developer option for 'com.android.statementservice' set to: 'default'
05-31 23:53:49.667 10622 10622 V GraphicsEnvironment: ANGLE GameManagerService for com.android.statementservice: false
05-31 23:53:49.668 10622 10622 V GraphicsEnvironment: Neither updatable production driver nor prerelease driver is supported.
05-31 23:53:49.668 10622 10622 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:53:49.668 10622 10622 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:53:49.687 10622 10639 D CompatibilityChangeReporter: Compat change id reported: 160794467; UID 10074; state: DISABLED
05-31 23:53:49.689 1718 14826 D CompatibilityChangeReporter: Compat change id reported: 171306433; UID 10074; state: DISABLED
05-31 23:53:49.757 10622 10641 E AndroidRuntime: FATAL EXCEPTION: pool-3-thread-2
05-31 23:53:49.757 10622 10641 E AndroidRuntime: Process: com.android.statementservice, PID: 10622
05-31 23:53:49.757 10622 10641 E AndroidRuntime: java.lang.IllegalStateException: Data cannot occupy more than 10240 bytes when serialized
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.Data.toByteArrayInternal(Data.java:417)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.Data$Builder.build(Data.java:846)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.OverwritingInputMerger.merge(OverwritingInputMerger.java:44)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.runWorker(WorkerWrapper.java:227)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:137)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at java.lang.Thread.run(Thread.java:920)
05-31 23:53:49.761 1718 10645 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
05-31 23:53:49.762 10622 10641 I Process : Sending signal. PID: 10622 SIG: 9
05-31 23:53:49.782 1718 14826 I ActivityManager: Process com.android.statementservice (pid 10622) has died: cch+5 CEM
05-31 23:53:49.782 1718 2118 I libprocessgroup: Successfully killed process cgroup uid 10074 pid 10622 in 0ms
05-31 23:53:49.782 966 966 I Zygote : Process 10622 exited due to signal 9 (Killed)
Example2:
Code:
05-31 23:54:24.620 966 966 D Zygote : Forked child process 10707
05-31 23:54:24.620 1718 2114 I ActivityManager: Start proc 10707:com.android.statementservice/u0a74 for service {com.android.statementservice/androidx.work.impl.background.systemjob.SystemJobService}
05-31 23:54:24.625 10707 10707 I libc : SetHeapTaggingLevel: tag level set to 0
05-31 23:54:24.639 1357 1429 I adbd : jdwp connection from 10707
05-31 23:54:24.640 10707 10707 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
05-31 23:54:24.633 0 0 I : c3 10707 binder: 10707:10707 ioctl 40046210 7fea0fb8d4 returned -22
05-31 23:54:24.650 1718 14826 D CompatibilityChangeReporter: Compat change id reported: 168419799; UID 10074; state: DISABLED
05-31 23:54:24.654 10707 10707 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10074; state: DISABLED
05-31 23:54:24.660 10707 10707 D ApplicationLoaders: Returning zygote-cached class loader: /system/framework/android.test.base.jar
05-31 23:54:24.678 10707 10707 V GraphicsEnvironment: ANGLE Developer option for 'com.android.statementservice' set to: 'default'
05-31 23:54:24.678 10707 10707 V GraphicsEnvironment: ANGLE GameManagerService for com.android.statementservice: false
05-31 23:54:24.679 10707 10707 V GraphicsEnvironment: Neither updatable production driver nor prerelease driver is supported.
05-31 23:54:24.680 10707 10707 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:54:24.680 10707 10707 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:54:24.699 10707 10724 D CompatibilityChangeReporter: Compat change id reported: 160794467; UID 10074; state: DISABLED
05-31 23:54:24.700 1718 4358 D CompatibilityChangeReporter: Compat change id reported: 171306433; UID 10074; state: DISABLED
05-31 23:54:24.726 1315 1315 I cnss-daemon: nl80211 response handler invoked
05-31 23:54:24.726 1315 1315 I cnss-daemon: nl80211_response_handler: cmd 103, vendorID 4980, subcmd 13 received
05-31 23:54:24.727 1017 2427 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-31 23:54:24.765 10707 10726 E AndroidRuntime: FATAL EXCEPTION: pool-3-thread-2
05-31 23:54:24.765 10707 10726 E AndroidRuntime: Process: com.android.statementservice, PID: 10707
05-31 23:54:24.765 10707 10726 E AndroidRuntime: java.lang.IllegalStateException: Data cannot occupy more than 10240 bytes when serialized
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.Data.toByteArrayInternal(Data.java:417)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.Data$Builder.build(Data.java:846)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.OverwritingInputMerger.merge(OverwritingInputMerger.java:44)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.runWorker(WorkerWrapper.java:227)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:137)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at java.lang.Thread.run(Thread.java:920)
05-31 23:54:24.768 1718 10731 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2

Sorry I don't have a solution for you but since you are using LineageOS+microG on a Pixel phone, you might be interested in switching to CalyxOS as they seem to already have a workaround in place even though the bug isn't fixed yet.
See here under "Issues":
CalyxOS News
📰 Read about what we're working on, important announcements, and upcoming events.
calyxos.org
Relevant commit:
https://review.calyxos.org/c/CalyxOS/vendor_calyx/+/7976
As a bonus, with CalyxOS you also get better security than just LineageOS+microG thanks to bootloader relocking.

I am suffered by that bug too. I can't see any harm by this, but it is annoying. The patch in CalyxOS is just to hide that problem as a workaround.

I filed a bug report here:
Intent filter verification service / com.android.statementservice regularly crashing on LineageOS for microg · Issue #1740 · microg/GmsCore
I am aware this is a very unclear specification of a bug. It is not clear who and what is responsible for this - can be also Android12 (LOS). But it seems to be that the combination of LOS and micr...
github.com
Please report there all your findings @maloo1 and @johnfocker

So I ended up following @johnfocker's suggestion and installed CalyxOS (android 12) and it does "fix" the issue.
I guess Calyx is a perfect fit for my needs anyway (microg, locked boot loader, great polished daily driver) so Ill probably stick with it unless I end up with a phone that is not supported.
It would make sense to have it fixed in microg thou if thats the root cause... I'll see what I can add to the bug...
Thanks again!

Very strange. The messages disappear to pop up after some time.
Lately I installe the new Magisk 25 and BetterBatteryStats (XDA) and it appears again - althoug I am not sure that was really reason. There is continiously changes in phone, so difficult to nail it down.

Quote from flipreverse:
This seems to be a bug in AOSP: https://android.googlesource.com/platform/frameworks/base/+/4978d1ad10293900e9b5feea349abd09ceb6e710
The LOS repo android_frameworks_base does not have this commit at the moment. I'll cherry-pick that one, and give it a try.
Click to expand...
Click to collapse

ale5000 said:
Quote from flipreverse:
Click to expand...
Click to collapse
ist this the bug fix?
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/334683

kurtn said:
ist this the bug fix?
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/334683
Click to expand...
Click to collapse
Yes.

ale5000 said:
Yes.
Click to expand...
Click to collapse
Just too late for the lineage.microg.org August round of builds.

Question Self-compiled ROM reboot

Here is the log that caused the restart
04-05 09:33:57.788 31933 31977 E AndroidRuntime: FATAL EXCEPTION: pool-5-thread-1
04-05 09:33:57.788 31933 31977 E AndroidRuntime: Process: com.shannon.imsservice, PID: 31933
04-05 09:33:57.788 31933 31977 E AndroidRuntime: java.lang.RuntimeException: failed to set system property (check logcat for reason)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at android.os.SystemProperties.native_set(Native Method)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at android.os.SystemProperties.set(SystemProperties.java:235)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.setCallWaitingSyncProperty(ImsUt.java:1393)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.lambda$refreshCallWaiting$28(ImsUt.java:1211)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.$r8$lambda$A880XJDdCNHXPHCDkqclCeZT2U8(Unknown Source:0)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt$$ExternalSyntheticLambda22.execute(Unknown Source:6)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.runStoredUtRequest(ImsUt.java:999)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.runNewUtRequest(ImsUt.java:946)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.executeIfAvailable(ImsUt.java:940)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.executeIfAvailable(ImsUt.java:933)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.refreshCallWaiting(ImsUt.java:1201)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.lambda$refreshCallWaitingAsync$27(ImsUt.java:1155)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt.$r8$lambda$V3-4-1Ak7OCWx7C1l3QhRu_06mA(Unknown Source:0)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at com.shannon.imsservice.ut.ImsUt$$ExternalSyntheticLambda15.run(Unknown Source:4)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
04-05 09:33:57.788 31933 31977 E AndroidRuntime: at java.lang.Thread.run(Thread.java:1012)
04-05 09:33:57.788 523 565 D display : setActiveConfigWithConstraints:: PrimaryDisplay config(36) test(0)
04-05 09:33:57.788 31933 31971 D SHANNON_IMS: 0161 [CONN] triggerRegistering by WIFI_CONNECT_CHANGE [SLID:0] (ImsConnectivityMgr%triggerRegistering:3534)
04-05 09:33:57.789 2690 2746 D LocalImageResolver: Couldn't use ImageDecoder for drawable, falling back to non-resized load.
04-05 09:33:57.789 31933 31979 D SHANNON_IMS: 0162 [UT##] Other Ut request already running. Add request in pending queue [SLID:0 ] (ImsUt%runNewUtRequest:948)
04-05 09:33:57.791 1452 1525 W ActivityManager: Process com.shannon.imsservice has crashed too many times, killing! Reason: crashed quickly
04-05 09:33:57.791 31933 31977 I Process : Sending signal. PID: 31933 SIG: 9
04-05 09:33:57.793 1452 1526 W RescueParty: Attempting rescue level WARM_REBOOT
04-05 09:33:57.794 1452 1526 D PackageManager: Finished rescue level WARM_REBOOT for package com.shannon.imsservice

Post sources links, maybe there's something in there
I'm compiling my own custom rom and never found this error

Schnedi said:
发布资源链接，也许那里有东西
我正在编译自己的自定义 ROM，但从未发现此错误
Click to expand...
Click to collapse
rom sources https://github.com/exthmui
kernel sources https://android.googlesource.com/device/google/raviole-kernel/
vendor image https://dl.google.com/dl/android/aosp/google_devices-raven-tq2a.230305.008.f1-54772b94.tgz

As the log says, the error is caused by: com.shannon.imsservice
Didn't see anything on the rom sources that may cause the error, and kernel is stock, so I'd say not its fault
Not sure how that vendor image file works, but shannon ims is provided by the vendor (also the needed permissions): https://gitlab.com/schnedi3/vendor_...13/proprietary/system_ext/priv-app/ShannonIms
I recommend you to use a vendor tree extracted with adevtool (or even lineageos extract tool)

Schnedi said:
As the log says, the error is caused by: com.shannon.imsservice
Didn't see anything on the rom sources that may cause the error, and kernel is stock, so I'd say not its fault
Not sure how that vendor image file works, but shannon ims is provided by the vendor (also the needed permissions): https://gitlab.com/schnedi3/vendor_...13/proprietary/system_ext/priv-app/ShannonIms
I recommend you to use a vendor tree extracted with adevtool (or even lineageos extract tool)
Click to expand...
Click to collapse
I modified the device tree and added some SELinux rules, but this happened again in the compilation
FAILED: /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy.cil/android_common/pub_policy.cil
/mnt/ubuntu/home/ghhc/exui/out/host/linux-x86/bin/checkpolicy -C -M -c 30 -o /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy.cil/android_common/pub_policy.cil /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy.conf/android_common/pub_policy.conf && /mnt/ubuntu/home/ghhc/exui/out/host/linux-x86/bin/build_sepolicy filter_out -f /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/reqd_policy_mask.cil/android_common/reqd_policy_mask.cil -t /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy.cil/android_common/pub_policy.cil # hash of input list: aa6039e1ca8cac20dc39c60dd5d085ec691a6a1094a3c1fa4f3948e274bc8992
device/google/gs101-sepolicy/whitechapel/vendor/google/chre.te:16:ERROR 'syntax error' at token 'usf_low_latency_transport' on line 38138:
usf_low_latency_transport(chre)
# Allow CHRE to use the USF low latency transport
checkpolicy: error(s) encountered while parsing configuration
21:34:40 ninja failed with: exit status 1

Revert this commit for now
Add policy for USF low latency transport gralloc usage. · RealSchnedi/[email protected]
Bug: 183233052 Test: Verified regular and direct report sampling on Raven with shared memory transport enabled. Test: See details in testing done comment in https://googleplex-android-review.git....
github.com

Schnedi said:
Revert this commit for now
Add policy for USF low latency transport gralloc usage. · RealSchnedi/[email protected]
Bug: 183233052 Test: Verified regular and direct report sampling on Raven with shared memory transport enabled. Test: See details in testing done comment in https://googleplex-android-review.git....
github.com
Click to expand...
Click to collapse
I have restored this commit, but I get an error like the following
[ 50% 180/355] //system/sepolicyub_policy_for_vendor.cil Building cil for pub_policy_for_vendor.cil [common]
FAILED: /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy_for_vendor.cil/android_common/pub_policy_for_vendor.cil
/mnt/ubuntu/home/ghhc/exui/out/host/linux-x86/bin/checkpolicy -C -M -c 30 -o /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy_for_vendor.cil/android_common/pub_policy_for_vendor.cil /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy_for_vendor.conf/android_common/pub_policy_for_vendor.conf && /mnt/ubuntu/home/ghhc/exui/out/host/linux-x86/bin/build_sepolicy filter_out -f /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/reqd_policy_mask_for_vendor.cil/android_common/reqd_policy_mask_for_vendor.cil -t /mnt/ubuntu/home/ghhc/exui/out/soong/.intermediates/system/sepolicy/pub_policy_for_vendor.cil/android_common/pub_policy_for_vendor.cil # hash of input list: ff0f05a68765c0a567c7a6b5bb400a51419bef0bfa17d3fdd1bdda6c7d41d03f
device/google/gs101-sepolicy/whitechapel/vendor/google/hal_audio_default.te:26:ERROR 'unknown type hal_audio_default' at token ';' on line 39333:
#line 26
typeattribute hal_audio_default halclientdomain;
checkpolicy: error(s) encountered while parsing configuration
06:09:05 ninja failed with: exit status 1

any luck figuring this out? I'm seeing the same thing with my AOSP build on a Pixel 6a ... works fine on a 4a but not the 6a ... if I remove the SIM card it's fine but with the SIM card in, it'll reboot the phone with this error

I got this reboot to stop by disabling SELinux as it was an SELinux violation causing the issue... not sure what the root cause is though. I'm only doing testing so disabling SELinux isn't a big deal.