Has anyone have MATICS folder in LG G4? - G4 Q&A, Help & Troubleshooting

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.

Related

Need Help Accessing com_broadcom_bt_service_fm_FmReceiverService

Hi,
I'm tracing through the HTCFMRadio app on my EVO to figure out how it works. I eventually want to create a program that records radio without having to use the mic. From my tracing I can see taht the program continually calls:
com_broadcom_bt_service_fm_FmReceiverService.cpp
Here's logcat:
07-14 10:20:33.769: VERBOSE/FmReceiverEventLoop(94): onRadioRdsUpdateEvent() WOSU 89.7 : station website
07-14 10:20:33.769: VERBOSE/FmReceiverService(94): onRadioRdsUpdateEvent(0,9,42,WOSU 89.7 : station website )
07-14 10:20:33.769: WARN/FmReceiverService(94): Handling OPERATION_RDS_DATA_EVENT_CALLBACK: calls sendRdsDataEventCallback
07-14 10:20:33.769: INFO/BTL_IFC(94): btl_ifc_ctrl_rx: [BTL_IFC CTRL] recv BTLIF_FM_RDS_UPDATE (FM) 79 pbytes (hdl 189)
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): decodePendingEvent: Event ID: 4370
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): decodePendingEvent: RDS UPDATE EVENT
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: event ID: 9, ATTACHING THREAD
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: THREAD ATTACHED OK
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): [JNI] - TRANSMITTING EVENT UP : event = 9
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, 0x 6d4fb8
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, previous_rdsWOSU 89.7 : station website
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, new_rdsWOSU 89.7 : station website
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, memcmp 0x 20
07-14 10:20:33.769: VERBOSE/FmReceiverEventLoop(94): onRadioRdsUpdateEvent() WOSU 89.7 : station website
07-14 10:20:33.769: VERBOSE/FmReceiverService(94): onRadioRdsUpdateEvent(0,9,42,WOSU 89.7 : station website)
07-14 10:20:33.779: WARN/FmReceiverService(94): Handling OPERATION_RDS_DATA_EVENT_CALLBACK: calls sendRdsDataEventCallback
07-14 10:20:33.779: INFO/BTL_IFC(94): btl_ifc_ctrl_rx: [BTL_IFC CTRL] recv BTLIF_FM_RDS_UPDATE (FM) 79 pbytes (hdl 189)
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): decodePendingEvent: Event ID: 4370
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): decodePendingEvent: RDS UPDATE EVENT
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: event ID: 9, ATTACHING THREAD
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: THREAD ATTACHED OK
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): [JNI] - TRANSMITTING EVENT UP : event = 9
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, 0x 6d4fb8
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, previous_rdsWOSU 89.7 : station website
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, new_rdsWOSU 89.7 : station webstie
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, memcmp 0x 0
07-14 10:20:34.316: INFO//system/bin/btld(10221): ##### USerial_Ioctl: BT_Sleep, 0x8004 ####
07-14 10:20:35.020: INFO//system/bin/btld(10221): ##### USerial_Ioctl: BT_Wake, 0x8003 ####
07-14 10:20:35.049: INFO/BTAPP_FM(10222): BTAPP_FM: btui_fm_cback: 10
07-14 10:20:35.049: INFO/BTAPP_FM(10222): BTAPP_FM: BTA_FM_AUD_DATA_EVT
07-14 10:20:35.049: INFO/BTL-IFS(10222): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_FM_GET_AUDIO_QUALITY (FM) 12 pbytes (hdl 15)
Can someone explain to me how I can access the music stream created by this file? or at least give me direction in how to figure this out? Thanks!
Respectfully,
Jerry Balderas
solved
file in question is called by com.broadcom.bt.service.fm.FmReceiverService which can be extracted from framework.odex
copy framework.odex to same directory as HtcFMRadio.odex then:
baksmali -d <framework directory> -x framework.odex

Htc one X loosing signal and stuck on airplane mode

my htc one x is now losing signal and stucking on airplane mode with no imei and baseband,he work couple of hours and then again lost signal with that simptom i dont know what is the problem,maybe in hboot but i dont know here is the logchat log so pls help me:
C:\Users\Home\Desktop\root>adb logcat -s MODEM:V xgold-fw:V
- waiting for device -
--------- beginning of /dev/log/main
--------- beginning of /dev/log/system
E/MODEM ( 388): Poweron_modem_fls.sh version: 1.0.2
E/MODEM ( 392): ttyACMX0 is null. Create it.
E/MODEM ( 407): /rca folder mounted.
E/MODEM ( 409): cp calib.nvm to work folder
E/MODEM ( 410): setprop ril.nvm.cal.dir /data/modem_work/
E/MODEM ( 413): setprop ril.nvm.work.dir /data/modem_work/
E/MODEM ( 422): Gen. sec.bin SUCC in /rfs/
E/MODEM ( 467): Double confirm sec.bin is in /rfs/ and SUCC.
E/MODEM ( 468): NVM Injecting file: new InjectionTool will generate empty nvm
file if it doesn't exist
I/MODEM ( 483): Delete sec.bin in /rfs/
I/MODEM ( 497): Checking malog_status
I/MODEM ( 498): insmod /system/lib/modules/cdc-acm.ko 1
E/MODEM ( 500): IMCdownload -V0x1130 -X0 -x800 -y30 -z50

Liquidsmooth 2.37 bluetooth bug fix

hello guys this is my first fix. I hope it fixes the bluetooth bug on liquidsmooth 2.37 for galaxy ace 2 (http://forum.xda-developers.com/showthread.php?t=2573302)
As @judas1977 said it was from kernel and gives some help and idea how to change it, I tried to make a fix for it. just download and flash it from recovery It worked for my device and I hope it will work for you too =)
here is the link
https://drive.google.com/file/d/0B-8__H0BBJIJRkxYVmZxTXlSM00/edit?usp=sharing
thanks for 
 @judas1977
 @Rox
 @shine911
and everyone who helped to developed this awesome rom
development
If i find enough time i will try to update rom with new updates or some fixes
blastos01 said:
If i find enough time i will try to update rom with new updates or some fixes
Click to expand...
Click to collapse
While you're at it, you wouldn't happen to know the bluetooth fix for the GT-S7560?
fix
BT was the biggest for me. I changed the kernel with the latest cm10.2 kernel. So the patch has to change all kernel related issues.
idk
SamsungGalaxySamsung said:
While you're at it, you wouldn't happen to know the bluetooth fix for the GT-S7560?
Click to expand...
Click to collapse
As i dont have your device i dont know what is the problem with BT un your device. i think i need too much time for it.
Sorry for my bad english.
Thanks no problem
Sent from my GT-S7560 using XDA Premium 4 mobile app
wi-fi ?
I guess wi-fi feature has been improved. can any body confirm?
I think my device catches wi-fi signal more effectively after flashing patch
blastos01 said:
As i dont have your device i dont know what is the problem with BT un your device. i think i need too much time for it.
Sorry for my bad english.
Click to expand...
Click to collapse
Here is the logcat for BT on boot:
Code:
E/bt-btif ( 1433): btif_enable_service: current services:0x2000000
E/bt-btif ( 1433): btif_enable_service: current services:0x2000040
E/bt-btif ( 1433): btif_enable_service: current services:0x2040040
E/bt-btif ( 1433): warning : no command pending, ignore ack
E/bt-btif ( 1433): btif_enable_service: current services:0x2140040
E/bt_vendor_qcom( 1433): open(/sys/class/rfkill/rfkill1/type) failed: No such file or directory (2)
E/bt_vendor_qcom( 1433): open() failed: No such file or directory (2)
E/bt_vendor_qcom( 1433): open() failed: No such file or directory (2)
E/bt_h4 ( 1433): [h4] Unknown HCI message type drop this byte 0x0
E/BluetoothAdapterState( 1433): Error enabling Bluetooth
E/BluetoothManagerService( 896): recoverBluetoothServiceFromError
E/BluetoothServiceJni( 1433): Callback env check fail: env: 0x11ca8, callback: 0x62b00
E/BluetoothServiceJni( 1433): Callback: 'adapter_state_change_callback' is not called on the correct thread
Anas Karbila said:
Here is the logcat for BT on boot:
Code:
E/bt-btif ( 1433): btif_enable_service: current services:0x2000000
E/bt-btif ( 1433): btif_enable_service: current services:0x2000040
E/bt-btif ( 1433): btif_enable_service: current services:0x2040040
E/bt-btif ( 1433): warning : no command pending, ignore ack
E/bt-btif ( 1433): btif_enable_service: current services:0x2140040
E/bt_vendor_qcom( 1433): open(/sys/class/rfkill/rfkill1/type) failed: No such file or directory (2)
E/bt_vendor_qcom( 1433): open() failed: No such file or directory (2)
E/bt_vendor_qcom( 1433): open() failed: No such file or directory (2)
E/bt_h4 ( 1433): [h4] Unknown HCI message type drop this byte 0x0
E/BluetoothAdapterState( 1433): Error enabling Bluetooth
E/BluetoothManagerService( 896): recoverBluetoothServiceFromError
E/BluetoothServiceJni( 1433): Callback env check fail: env: 0x11ca8, callback: 0x62b00
E/BluetoothServiceJni( 1433): Callback: 'adapter_state_change_callback' is not called on the correct thread
Click to expand...
Click to collapse
I have exams and too much work with my master thesis. for now I can't tell you when will I try to change the problem or... sorry for these =(
blastos01 said:
I have exams and too much work with my master thesis. for now I can't tell you when will I try to change the problem or... sorry for these =(
Click to expand...
Click to collapse
Alright thanks for reply.

Back to the Sheldon/p stock version

Hello everybody,
after unlocking the bootloader and rooting, I tried to install LineageOS. Everything was fine, but I liked the original version of the system more. So I flashed the stock image again.
Now it happens that for every video I start, the system crashes and restarts.
This is a part of the logcat.
Code:
04-05 10:12:06.191 366 10755 D vdec_app: [MtkVdecH265SecInit] + secureHandle:5702, size:36651
04-05 10:12:06.192 366 10755 I vdec_app: UREE_RegisterSharedmemWithTag: 0, line:316, gMemSession(1)
04-05 10:12:06.192 366 10755 I chatty : uid=1046(mediacodec) MtkOmxVdecDecod identical 1 line
04-05 10:12:06.192 366 10755 I vdec_app: UREE_RegisterSharedmemWithTag: 0, line:316, gMemSession(1)
04-05 10:12:06.193 7924 10646 I AmazonVideo: Sending com.amazon.avod.event.START_PLAYBACK broadcast for amzn1.dv.gti.aeb8bacc-365b-0844-4d98-79a41bf5c427
04-05 10:12:06.197 7924 10760 I AmazonVideo: MediaCodec for {sample-rate=48000, mime=audio/mp4a-latm, channel-count=2} indicates output format changed to {sample-rate=48000, pcm-encoding=2, mime=audio/raw, channel-count=2}
04-05 10:12:06.198 7924 10682 I : T10682: AIVDashFragmentJNI::Java_com_amazon_avod_smoothstream_dash_Mp4FragmentJni_parse: Parsing fragment (size 103154)
04-05 10:12:06.200 7924 10671 I platform-utils: onDownloadComplete(): BolaTransient OnDownloadComplete transientBufferSeconds 119.700, realBufferSeconds 37.496
04-05 10:12:06.201 7924 10671 I platform-utils: reportDownloadProgress(): BOLA Video completed request FragmentInfo{fragmentIndex: 13, timeAllowedMillis: 8016, sizeInBytes: 103154, bytesDownloaded: 103154} | Reason: DOWNLOAD_STATUS_SUCCESS, BufferSeconds 37.50, elapsedMillis 85, StallMillis 0.00
04-05 10:12:06.201 7924 10671 I platform-utils: getBolaBitRate(): getBolaBitRate FragmentIndex 14 SelectedBitrate 9.00 mbps Note: BufferDurationSec 119.700 ParamV/Gamma 5.260/18.759 BitRate/GoodnessValue 0.05MB/-0.000677529 0.10MB/-0.000279987 0.18MB/-0.000127860 0.25MB/-0.000080918 0.40MB/-0.000040611 0.80MB/-0.000012959 1.00MB/-0.000008458 1.30MB/-0.000004799 2.20MB/-0.000000814 4.00MB/0.000000820 9.00MB/0.000001128 optimalValue 0.000001128 idealGoodnessValue 0.000001117
04-05 10:12:06.218 7924 10682 I AmazonVideo: DownloadRequest downloading url: https://pop-it-cf.dash.pv-cdn.net/dm/2$KEynCzMEy6b-nofKzOAqu3cWR-0~/[email protected]/e151/56f7/0eea/43c1-9c6b-68f785cc1551/[email protected]_UCEAMggA==/52d2f173-ad2e-4fa6-8de0-35e01f9c2646_video_9.mp4 | headers: {Range=bytes=4013276-4748948} | expectedSizeKB: 718 | timeoutMillis: 9000
04-05 10:12:06.224 7924 10671 I platform-utils: submitDownloadRequests(): BOLA Video requested download | FragmentIndex 14, bitrateMbps 9.00, timeoutMillis 9000, State LOW_TRANSIENT, BufferSec:(Compensated 119.70, Effective 119.70, Real 37.50, Stall 0.02), maxBufferSec 126.00
04-05 10:12:06.225 7924 10707 I : T10707: AIVDashFragmentJNI::Java_com_amazon_avod_smoothstream_dash_Mp4FragmentJni_parse: Parsing fragment (size 33375)
04-05 10:12:06.230 7924 10678 I AmazonVideo: DownloadRequest downloading url: https://pop-it-cf.dash.pv-cdn.net/dm/2$KEynCzMEy6b-nofKzOAqu3cWR-0~/[email protected]/e151/56f7/0eea/43c1-9c6b-68f785cc1551/[email protected]_cYCMAMggA==/52d2f173-ad2e-4fa6-8de0-35e01f9c2646_audio_45.mp4 | headers: {Range=bytes=672902-705888} | expectedSizeKB: 32 | timeoutMillis: 6000
04-05 10:12:06.238 7924 10675 I platform-utils: submitDownloadRequests(): BOLA Audio requested download for fragmentIndex 19 timeoutMillis 6000 downloadHandle 34
04-05 10:12:06.238 7924 10675 I platform-utils: reportDownloadProgress(): BOLA Audio completed request | Reason: DOWNLOAD_STATUS_SUCCESS, fragmentIndex 18, elapsedTimeMillis 101 ms, latency 54 ms
04-05 10:12:06.238 523 542 W ActivityManager: Slow operation: 59ms so far, now at startProcess: returned from zygote!
04-05 10:12:06.248 10765 10765 E evice.messagin: Not starting debugger since process cannot load the jdwp agent.
04-05 10:12:06.449 9452 9474 E SystemStatusMonitorSys_MultimediaMetrics: Other information is not supported
04-05 10:12:06.682 339 339 I perfmonitord:StatUtil: CPUUtilization crossed 95%. Current - 98%
04-05 10:12:06.449 9452 9474 E SystemStatusMonitorSys_MultimediaMetrics: Other information is not supported
04-05 10:12:07.531 9416 9451 D SystemStatusMonitorApp_DataManager: update Audio Focus
04-05 10:12:07.531 9416 9451 D SystemStatusMonitorApp_DataManager: Get Audio Focus Cursor
04-05 10:12:07.533 9452 9464 D SystemStatusMonitorSys_SSMProvider: query called
04-05 10:12:07.947 9416 9450 D SystemStatusMonitorApp_MultimediaModel: Multimedia updated
04-05 10:12:07.947 9416 9450 D SystemStatusMonitorApp_DataManager: update Multimedia
04-05 10:12:07.947 9416 9450 D SystemStatusMonitorApp_DataManager: Get Multimedia Cursor
04-05 10:12:07.948 9452 9468 D SystemStatusMonitorSys_SSMProvider: query called
04-05 10:12:08.447 9452 9475 E SystemStatusMonitorSys_MultimediaMetrics: Other information is not supported
04-05 10:12:08.448 9452 9475 E SystemStatusMonitorSys_MultimediaMetrics: Other information is not supported
04-05 10:12:10.448 9452 9472 E SystemStatusMonitorSys_MultimediaMetrics: Other information is not supported
04-05 10:12:10.448 9452 9472 E SystemStatusMonitorSys_MultimediaMetrics: Other information is not supported
04-05 10:12:16.241 7924 7934 E com.amazon.avo: Timed out waiting for threads to suspend, waited for 10.000s
04-05 10:12:26.241 7924 7934 E com.amazon.avo: Timed out waiting for threads to suspend, waited for 20.000s
04-05 10:12:36.241 7924 7934 E com.amazon.avo: Timed out waiting for threads to suspend, waited for 30.000s
04-05 10:12:37.769 1206 1290 I zon.tv.launche: Waiting for a blocking GC ProfileSaver
04-05 10:12:46.241 7924 7934 E com.amazon.avo: Timed out waiting for threads to suspend, waited for 40.000s
Is there any way to completely remove TWRP and bootloader to go back to stock version?
Your question is already answered multiple times...
Why not read a few posts backwards in the unlock (or the lineage) thread, to see the solution?
Sus_i said:
Your question is already answered multiple times...
Why not read a few posts backwards in the unlock (or the lineage) thread, to see the solution?
Click to expand...
Click to collapse
Thanks for the reply!
I had already read, but hadn't paid attention.
I managed to solve!
I took the tz.img file and replaced it inside the kamakiri BIN folder. now everything is working!
kisspachyousee said:
Thanks for the reply!
I had already read, but hadn't paid attention.
I managed to solve!
I took the tz.img file and replaced it inside the kamakiri BIN folder. now everything is working!
Click to expand...
Click to collapse
Would you mind telling me where I can locate the TZ.img in the original ROM?
I have downloaded the 7.2.4.2 ROM, & want to extract the tz.img, too.
just unzip the file you downloaded as if it were a zip file

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.

Categories

Resources