Develop Bugs

ICS reboots due to 4g/WiMax

I've noticed that multiple people, including myself, have had multiple issues with random reboots on various ICS roms. Well it was driving me crazy, so I decided to catch it in the act. Please see this from my logcat:
Code:
04-18 17:04:36.799 E AlarmManagerService: android_server_AlarmManagerService_set to type=2, 115438.634000000
04-18 17:04:36.799 V AlarmManager: trigger WAKEUP Alarm{41c5fcd8 type 2 android}
04-18 17:04:36.809 W dalvikvm: threadid=13: thread exiting with uncaught exception (group=0x40c231f8)
04-18 17:04:36.809 E android.os.Debug: [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_sys_error
04-18 17:04:36.809 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
04-18 17:04:36.809 E AndroidRuntime: java.lang.NoSuchMethodError: com.android.server.WimaxService.access$1002
04-18 17:04:36.809 E AndroidRuntime: at com.android.server.WimaxService$4.onReceive(WimaxService.java:1150)
04-18 17:04:36.809 E AndroidRuntime: at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:728)
04-18 17:04:36.809 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:605)
04-18 17:04:36.809 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:92)
04-18 17:04:36.809 E AndroidRuntime: at android.os.Looper.loop(Looper.java:137)
04-18 17:04:36.809 E AndroidRuntime: at com.android.server.ServerThread.run(SystemServer.java:986)
04-18 17:04:36.834 I dumpstate: Check if stand-alone
04-18 17:04:36.859 I dumpstate: begin
I went back through several saved logcats after these reboots, and the signature looks the same. It looks to me as if the WiMax service (WimaxService.java) is calling an invalid method (com.android.server.WimaxService.access$1002), and causing android server to crash with a FATAL exception.
Now, I'm not a programmer, but does anyone have any ideas on how we can investigate the code and see if we can make a workaround? Thoughts anyone? I'll keep at this.

I'm not a program either, but I know Team Nocturnal had this same issue on a couple of their ROMs and Mijjah was working on it. Not sure if he has any logs of it happening.
I do know he's working on an AOKP rom as well, which I'm using, and I haven't had the issue yet.

Maybe post this in the dev thread of the rom you are using. I think we can all benefit from this Im sick of my phone rebooting while using 4g!!

Random reboots (logcat is inside), please advise

Hello techy people,
I have bought XA2, unlocked bootloader and installed latest LOS 15 (30 Nov build). Installed Magisk, MicroG, Afwall, all worked well and today random reboots started to happen. Sometimes it happens when I play with location settings in maps app, sometimes when I use the messenger. I did a few logcats and all of them have the following bit:
12-02 39.242 12603 12689 D ConnectivityService: handleLingerComplete for NetworkAgentInfo [MOBILE (LTE) - 100]
12-02 39.258 12449 12488 W IptablesRestoreController: iptables-restore process 12453 terminated status=256
12-02 39.262 12449 12488 E Netd : failed to change iptables rule that sets incoming packet mark
12-02 39.262 12449 12488 E Netd : failed to change permission on interface rmnet_data0 of netId 100 from 0 to 1
12-02 39.266 12603 12689 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityServiceThread
12-02 39.266 12603 12689 E AndroidRuntime: java.lang.IllegalStateException: command '67 network permission network set NETWORK 100' failed with '400 67 setPermissionForNetworks() failed (Remote I/O error)'
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NetworkManagementService.setNetworkPermission(NetworkManagementService.java:2707)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService.updateCapabilities(ConnectivityService.java:4708)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService.handleLingerComplete(ConnectivityService.java:4879)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService.-wrap9(Unknown Source:0)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService$NetworkStateTrackerHandler.maybeHandleNetworkAgentInfoMessage(ConnectivityService.java:2213)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.ConnectivityService$NetworkStateTrackerHandler.handleMessage(ConnectivityService.java:2225)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.internal.util.WakeupMessage.onAlarm(WakeupMessage.java:111)
12-02 39.266 12603 12689 E AndroidRuntime: at android.app.AlarmManager$ListenerWrapper.run(AlarmManager.java:243)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:790)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
12-02 39.266 12603 12689 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:65)
12-02 39.266 12603 12689 E AndroidRuntime: Caused by: com.android.server.NativeDaemonConnector$NativeDaemonFailureException: command '67 network permission network set NETWORK 100' failed with '400 67 setPermissionForNetworks() failed (Remote I/O error)'
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NativeDaemonConnector.executeForList(NativeDaemonConnector.java:505)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:401)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:396)
12-02 39.266 12603 12689 E AndroidRuntime: at com.android.server.NetworkManagementService.setNetworkPermission(NetworkManagementService.java:2702)
12-02 39.266 12603 12689 E AndroidRuntime: ... 12 more
12-02 39.284 12603 12689 I Process : Sending signal. PID: 12603 SIG: 9
12-02 39.440 889 889 I adbd : Framework disconnect
12-02 39.445 859 859 I lowmemorykiller: ActivityManager disconnected
12-02 39.445 859 859 I lowmemorykiller: Closing Activity Manager data connection
12-02 39.446 924 924 E LocSvc_GnssInterface: serviceDied] service died. cookie: 0, who: 0x70de233c20
12-02 39.447 924 924 E LocSvc_APIClientBase: locAPIStopTracking:339] invalid session: 0.
12-02 39.447 924 924 E GnssHal_GnssGeofencing: serviceDied] service died. cookie: 0, who: 0x70de233fe0
12-02 39.447 924 924 E LocSvc_GnssNiInterface: serviceDied] service died. cookie: 0, who: 0x70de2b3020
12-02 39.451 12727 12744 W Sensors : sensorservice died [0x722207c3e0]
12-02 39.451 598 598 D SurfaceFlinger: Set power mode=2, type=0 flinger=0x750ae5f000
12-02 39.451 575 575 I ServiceManager: service 'launcherapps' died
12-02 39.452 14342 14420 W Sensors : sensorservice died [0xe6b374c0]
12-02 39.452 575 575 I ServiceManager: service 'media_projection' died
12-02 39.452 575 575 I ServiceManager: service 'media.camera.proxy' died
12-02 39.453 575 575 I ServiceManager: service 'autofill' died
12-02 39.453 575 575 I ServiceManager: service 'imms' died
12-02 39.453 575 575 I ServiceManager: service 'profile' died
12-02 39.454 575 575 I ServiceManager: service 'usb' died
12-02 39.454 575 575 I ServiceManager: service 'serial' died
12-02 39.455 575 575 I ServiceManager: service 'hardware_properties' died
12-02 39.457 12445 12445 E Zygote : Exit zygote because system server (12603) has terminated
Click to expand...
Click to collapse
I understand that bootloops are caused by setPermissionForNetworks() but not sure how to fix it.
Any help would be appreciated.

All sorted, many thanks

pupsidze said:
All sorted, many thanks
Click to expand...
Click to collapse
How did you fix it?

[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
HOW TO INSTALL LINEAGEOS:
- Official instructions
- In short: sideload in Lineage recovery (suggested) / flash in TWRP
HOW TO UPDATE LINEAGEOS:
- Download update from Updater app
- Install update
DOWNLOADS:
LineageOS 18.1: Official Oneplus 5, Official Oneplus 5T
Google Apps: MindTheGapps
Recovery: Suggested: Lineage recovery for Oneplus 5, Oneplus 5T | Alternative: TWRP
DEVELOPER RESOURCES
LineageOS source code:
- https://github.com/LineageOS
Device tree:
- android_device_oneplus_cheeseburger
- android_device_oneplus_dumpling
- android_device_oneplus_msm8998-common
Kernel:
- android_kernel_oneplus_msm8998
Android version: Android 11
Kernel version: Linux 4.4.y
Required firmware: OxygenOS 10.0.1 (shipped with ROM, no need to install manually)
Telegram group: https://t.me/los_op5

Issues:
- Safetynet does not pass. Magisk hide & MagiskHide Props Config help here.
- Wireless display does not work
Notes:
- Relocking bootloader https://forum.xda-developers.com/t/...s-18-1-for-oneplus-5-5t.4173997/post-84770085 (thanks for @Eric_Lev ) (not suggested though)

Really appreciate your efforts dude
Will try this out

Would you consider removing the lineage recovery from future builds?

Any idea about oneplus 5t

Added to the OnePlus 5 Index Thread here.

T1mb3 said:
ROM OS Version: 2.3.x Gingerbread
Click to expand...
Click to collapse
You most probably forgot to update this entry, just wanted to let you know. Thanks for this ROM Really appreciated!

JulianXhokaxhiu said:
You most probably forgot to update this entry, just wanted to let you know. Thanks for this ROM Really appreciated!
Click to expand...
Click to collapse
There actually is no option higher than Android 10 yet

JulianXhokaxhiu said:
You most probably forgot to update this entry, just wanted to let you know. Thanks for this ROM Really appreciated!
Click to expand...
Click to collapse
T1mb3 said:
There actually is no option higher than Android 10 yet
Click to expand...
Click to collapse
As you can read in Big Changes To XDA Forums are Coming Soon with the transition to Xenforo all DevDB threads will eventually be reverted to "normal" threads. For this reason, it was decided not to add the option "A 11" anymore.

T1mb3 said:
There actually is no option higher than Android 10 yet
Click to expand...
Click to collapse
Having said this...
Oswald Boelcke said:
As you can read in Big Changes To XDA Forums are Coming Soon with the transition to Xenforo all DevDB threads will eventually be reverted to "normal" threads. For this reason, it was decided not to add the option "A 11" anymore.
Click to expand...
Click to collapse
...you can always edit the first post using the edit button at the end of the post (instead of using the edit project option for DevDB threads) and manually change it to Android 11.

Is it rooted?
Does this pass SafetyNet?

sergio_sant said:
Is it rooted?
Does this pass SafetyNet?
Click to expand...
Click to collapse
This is not rooted by default. Latest Magisk works for that purpose.
This does not pass safetynet. I will have to look for a solution. Other ROMs use kernel-side patches for safetynet and those are not allowed in LineageOS.

UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* TWRP does not get overwritten by Lineage recovery for now. This may change when LineageOS makes their decision on the topic.
* More detailed changelog
* Download

T1mb3 said:
UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* TWRP does not get overwritten by Lineage recovery for now. This may change when LineageOS makes their decision on the topic.
* More detailed changelog
* Download
Click to expand...
Click to collapse
Hi，bro. I am trying to build los18 for oneplus5t, should I use pick this commit https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/287931 as you said to avoid that TRWP does get overwritten by Lineage recovery， is it right？

kpzhao said:
Hi，bro. I am trying to build los18 for oneplus5t, should I use pick this commit https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/287931 as you said to avoid that TRWP does get overwritten by Lineage recovery， is it right？
Click to expand...
Click to collapse
I did it this way: https://github.com/LineageOS-cheese...mmit/65b18d38368955a5a9cac58d09bf5c867624fb53

Great work, thanks for this rom. I LOVE IT
this is the 1st custom rom i install and the instructions were smooth. I did upgrade because oneplus stopped supporting OP5 and just sent a message in the community app giving fake excuses for the delays.
I noticed this bug
some apps that has the option to login with fingerprint doesn't work properly ( i.e. TD Canada Trust, Manulife)
as soon as the phone tries to communicate with the fingerprint reader, it freezes. 1st login in Manulife app, it asks if you want to allow or deny access to fingerprint reader, if you deny, it will let you login with the password if you remember it. if you accept, it hangs.
In TD Canada Trust app, first time you login with your password, it gives you a popup asking you if you want to enable fingerprint login, and you cant press anything other than closing the app.

T1mb3 said:
UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* TWRP does not get overwritten by Lineage recovery for now. This may change when LineageOS makes their decision on the topic.
* More detailed changelog
* Download
Click to expand...
Click to collapse
Can't call through VoLte, Volte cannot call!
Cannot tap to wake(settings-Display-Advanced-Tap to wake)

Hello，I build los18 for 5t successfully as your building guild . However it is no sim card and I get this log
10-12 10:12:46.522 21233 21233 E PhoneInterfaceManager: [PhoneIntfMgr] getIccId: No UICC
10-12 10:12:46.621 21233 21233 E AndroidRuntime: FATAL EXCEPTION: main
10-12 10:12:46.621 21233 21233 E AndroidRuntime: Process: com.android.phone, PID: 21233
10-12 10:12:46.621 21233 21233 E AndroidRuntime: java.lang.IllegalArgumentException: value of system property 'gsm.version.baseband' is longer than 91 characters: MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1,MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.SystemProperties.set(SystemProperties.java:236)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.sysprop.TelephonyProperties.baseband_version(TelephonyProperties.java:140)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.telephony.TelephonyManager.setBasebandVersionForPhone(TelephonyManager.java:10107)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.telephony.GsmCdmaPhone.handleMessage(GsmCdmaPhone.java:2850)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7656)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-12 10:12:46.656 764 3655 E IPCThreadState: attemptIncStrongHandle(77): Not supported
10-12 10:12:46.656 764 3545 E IPCThreadState: attemptIncStrongHandle(82): Not supported
10-12 10:12:46.656 764 3830 E IPCThreadState: attemptIncStrongHandle(79): Not supported
10-12 10:12:46.657 764 3545 E IPCThreadState: attemptIncStrongHandle(78): Not supported
10-12 10:12:46.784 21323 21323 E CarrierIdProvider: read carrier list from ota pb failure: java.io.FileNotFoundException: /data/misc/carrierid/carrier_list.pb: open failed: ENOENT (No such file or directory)
10-12 10:12:47.593 0 0 E [20201012_10:12:47.591117]@3 synaptics,s3320: all finger up
Could you give me some suggestion?

kpzhao said:
Hello，I build los18 for 5t successfully as your building guild . However it is no sim card and I get this log
10-12 10:12:46.522 21233 21233 E PhoneInterfaceManager: [PhoneIntfMgr] getIccId: No UICC
10-12 10:12:46.621 21233 21233 E AndroidRuntime: FATAL EXCEPTION: main
10-12 10:12:46.621 21233 21233 E AndroidRuntime: Process: com.android.phone, PID: 21233
10-12 10:12:46.621 21233 21233 E AndroidRuntime: java.lang.IllegalArgumentException: value of system property 'gsm.version.baseband' is longer than 91 characters: MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1,MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.SystemProperties.set(SystemProperties.java:236)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.sysprop.TelephonyProperties.baseband_version(TelephonyProperties.java:140)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.telephony.TelephonyManager.setBasebandVersionForPhone(TelephonyManager.java:10107)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.telephony.GsmCdmaPhone.handleMessage(GsmCdmaPhone.java:2850)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7656)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-12 10:12:46.656 764 3655 E IPCThreadState: attemptIncStrongHandle(77): Not supported
10-12 10:12:46.656 764 3545 E IPCThreadState: attemptIncStrongHandle(82): Not supported
10-12 10:12:46.656 764 3830 E IPCThreadState: attemptIncStrongHandle(79): Not supported
10-12 10:12:46.657 764 3545 E IPCThreadState: attemptIncStrongHandle(78): Not supported
10-12 10:12:46.784 21323 21323 E CarrierIdProvider: read carrier list from ota pb failure: java.io.FileNotFoundException: /data/misc/carrierid/carrier_list.pb: open failed: ENOENT (No such file or directory)
10-12 10:12:47.593 0 0 E [20201012_10:12:47.591117]@3 synaptics,s3320: all finger up
Could you give me some suggestion?
Click to expand...
Click to collapse
Hi,
Pick this commit: https://github.com/LineageOS-cheese...mmit/def355758a279ff756f2f6f580db161aa0fb805b

T1mb3 said:
Hi,
Pick this commit: https://github.com/LineageOS-cheese...mmit/def355758a279ff756f2f6f580db161aa0fb805b
Click to expand...
Click to collapse
You are a good man, sir. I am very appreciated for your help.

Question Pixel 6 Pro Reboots after enabling SIM or eSim

Hi all,
I have a very strange issue with my Pixel 6 Pro. Not rooted and original Android 13 firmware. The phone reboots whenever I enable the physical SIM or eSim. Then it shows me a screen to reboot or do a factory reset.
If I select the reboot option and keep the SIM enabled, it reboots, loads the UI and whenever the Sim is connected, it reboots again. This keeps going on forever.
After a reboot, when I quickly go to the menu and disable the sim, it will restart one more time and stop restarting after that since the sim is disabled.
Recently, I received the latest Android 13 Security Patch and issue started then (I was already on 13). I had the same issue also when I installed the Android 13 Beta firmware and I even created a bug on Android Beta issue tracker.
See: https://issuetracker.google.com/issues/236862868
Since it took some time before they responded, I went back to the stable 12 and updated to the stable 13 when it came out. I experienced no issues until the latest security patch.
Long story, but I'm just wondering, do you have any ideas what I can try more? Right now, I can't use any mobile services on this phone. Everything, including wifi works fine when the sim is disabled btw.

mrhnn said:
Hi all,
I have a very strange issue with my Pixel 6 Pro. Not rooted and original Android 13 firmware. The phone reboots whenever I enable the physical SIM or eSim. Then it shows me a screen to reboot or do a factory reset.
If I select the reboot option and keep the SIM enabled, it reboots, loads the UI and whenever the Sim is connected, it reboots again. This keeps going on forever.
After a reboot, when I quickly go to the menu and disable the sim, it will restart one more time and stop restarting after that since the sim is disabled.
Recently, I received the latest Android 13 Security Patch and issue started then (I was already on 13). I had the same issue also when I installed the Android 13 Beta firmware and I even created a bug on Android Beta issue tracker.
See: https://issuetracker.google.com/issues/236862868
Since it took some time before they responded, I went back to the stable 12 and updated to the stable 13 when it came out. I experienced no issues until the latest security patch.
Long story, but I'm just wondering, do you have any ideas what I can try more? Right now, I can't use any mobile services on this phone. Everything, including wifi works fine when the sim is disabled btw.
Click to expand...
Click to collapse
Did you buy it on eBay?

FoneWatcher said:
Did you buy it on eBay?
Click to expand...
Click to collapse
No, no. I bought it in the electronics store in Jan-22.

mrhnn said:
No, no. I bought it in the electronics store in Jan-22.
Click to expand...
Click to collapse
I've never used eSIM, but, I looked around & found this:
How to use dual SIMs on your Google Pixel phone - Pixel Phone Help
New to Pixel? Use our setup guide If you have a Pixel 3a or later Pixel phone, you can use two
support.google.com
Namely, have you checked/verified that your carrier(s) allow for Dual-Sim?
Other than that, my only guess is that the phone is SIM locked, but, if you bought it new & the phone is paid off, that can be ruled out.

Thank you. The phone was completely working fine with both eSim as well as with physical SIM.
Right now, it doesn't even matter which sim i choose / enable. Both ways it reboots.
For example: I disable and delete eSim completely and just put in the sim card, phone reboots after connecting to the carrier.
Seems to be an issue with some services on the phone.
I have a logcat from previous error (back in June when i had Android 13 Beta). I will try to get a new logcat with current stable version
Here you can see some fatal errors regarding com.shannon.qualifiednetworksservice
06-23 09:50:38.876 2877 3331 D CellBroadcastConfigService: mAlwaysOn is set to true, enable the range: 4370:4370
06-23 09:50:38.876 2358 2358 I VvmSimStateTracker: android.intent.action.SIM_STATE_CHANGED
06-23 09:50:38.878 3308 3326 E AndroidRuntime: FATAL EXCEPTION: QualifiedNetworksService
06-23 09:50:38.878 3308 3326 E AndroidRuntime: Process: com.shannon.qualifiednetworksservice, PID: 3308
06-23 09:50:38.878 3308 3326 E AndroidRuntime: java.lang.IllegalArgumentException: Source access networks contains unknown. "source=geran|utran|eutran|ngran|iwlan, target=geran|utran|eutran|ngran|iwlan, type=disallowed, capabilities=eims|mms|xcap|cbs"
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.android.internal.telephony.data.DataNetworkController$HandoverRule.<init>(DataNetworkController.java:717)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ConfigurationManager.updateCarrierConfigInfo(ConfigurationManager.java:229)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ConfigurationManager.<init>(ConfigurationManager.java:78)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ShannonQualifiedNetworksService$ShannonNetworkAvailabilityProvider.<init>(ShannonQualifiedNetworksService.java:133)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ShannonQualifiedNetworksService.onCreateNetworkAvailabilityProvider(ShannonQualifiedNetworksService.java:207)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.telephony.data.QualifiedNetworksService$QualifiedNetworksServiceHandler.handleMessage(QualifiedNetworksService.java:222)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
06-23 09:50:38.880 1744 2497 D CompatibilityChangeReporter: Compat change id reported: 184323934; UID 1000; state: ENABLED
06-23 09:50:38.882 1744 3335 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
06-23 09:50:38.882 1744 3306 W ActivityManager: Process com.shannon.qualifiednetworksservice has crashed too many times, killing! Reason: crashed quickly
06-23 09:50:38.883 3308 3326 I Process : Sending signal. PID: 3308 SIG: 9

mrhnn said:
Thank you. The phone was completely working fine with both eSim as well as with physical SIM.
Right now, it doesn't even matter which sim i choose / enable. Both ways it reboots.
For example: I disable and delete eSim completely and just put in the sim card, phone reboots after connecting to the carrier.
Seems to be an issue with some services on the phone.
I have a logcat from previous error (back in June when i had Android 13 Beta). I will try to get a new logcat with current stable version
Here you can see some fatal errors regarding com.shannon.qualifiednetworksservice
06-23 09:50:38.876 2877 3331 D CellBroadcastConfigService: mAlwaysOn is set to true, enable the range: 4370:4370
06-23 09:50:38.876 2358 2358 I VvmSimStateTracker: android.intent.action.SIM_STATE_CHANGED
06-23 09:50:38.878 3308 3326 E AndroidRuntime: FATAL EXCEPTION: QualifiedNetworksService
06-23 09:50:38.878 3308 3326 E AndroidRuntime: Process: com.shannon.qualifiednetworksservice, PID: 3308
06-23 09:50:38.878 3308 3326 E AndroidRuntime: java.lang.IllegalArgumentException: Source access networks contains unknown. "source=geran|utran|eutran|ngran|iwlan, target=geran|utran|eutran|ngran|iwlan, type=disallowed, capabilities=eims|mms|xcap|cbs"
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.android.internal.telephony.data.DataNetworkController$HandoverRule.<init>(DataNetworkController.java:717)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ConfigurationManager.updateCarrierConfigInfo(ConfigurationManager.java:229)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ConfigurationManager.<init>(ConfigurationManager.java:78)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ShannonQualifiedNetworksService$ShannonNetworkAvailabilityProvider.<init>(ShannonQualifiedNetworksService.java:133)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ShannonQualifiedNetworksService.onCreateNetworkAvailabilityProvider(ShannonQualifiedNetworksService.java:207)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.telephony.data.QualifiedNetworksService$QualifiedNetworksServiceHandler.handleMessage(QualifiedNetworksService.java:222)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
06-23 09:50:38.880 1744 2497 D CompatibilityChangeReporter: Compat change id reported: 184323934; UID 1000; state: ENABLED
06-23 09:50:38.882 1744 3335 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
06-23 09:50:38.882 1744 3306 W ActivityManager: Process com.shannon.qualifiednetworksservice has crashed too many times, killing! Reason: crashed quickly
06-23 09:50:38.883 3308 3326 I Process : Sending signal. PID: 3308 SIG: 9
Click to expand...
Click to collapse
Hi,
I just curious to you solved or not this issue, beauce i have the same problem et its really interesting. I tried lots of things but not working

akbulut00 said:
Hi,
I just curious to you solved or not this issue, beauce i have the same problem et its really interesting. I tried lots of things but not working
Click to expand...
Click to collapse
Hi, yes I solved it by changing the phone language from Turkish to English.
Steps:
Turn on the phone and as soon as you see the menu, turn on airplane mode (disable all networking options)
Phone will reboot again but since airplane mode is active, phone services will not be activated
Once the phone stops rebooting, change the language to English.
Just to make sure, reboot the phone with the new language.
Turn off airplane mode
Let me know if this works for you as well!

mrhnn said:
Hi, yes I solved it by changing the phone language from Turkish to English.
Steps:
Turn on the phone and as soon as you see the menu, turn on airplane mode (disable all networking options)
Phone will reboot again but since airplane mode is active, phone services will not be activated
Once the phone stops rebooting, change the language to English.
Just to make sure, reboot the phone with the new language.
Turn off airplane mode
Let me know if this works for you as well!
Click to expand...
Click to collapse
i realized to not completed security update, now im installing it. I will try again after completed.
i ll tell you the resault.

akbulut00 said:
i realized to not completed security update, now im installing it. I will try again after completed.
i ll tell you the resault.
Click to expand...
Click to collapse
Dissolved. The problem was the incomplete update.
sagolasin yine de

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.