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?

com.android.phone crashes - anyone have source code for mediatek telephony apk?

I have a Q7 (LM-Q610YM) which crashes whenever I put a SIM in it. Boots fine without a SIM, but as soon as it connects to the network the com.android.phone process crashes. I have never rooted the phone, and have tried a full factory reset.
The top of the stack trace in the logcat is:
Code:
--------- beginning of crash
E AndroidRuntime: FATAL EXCEPTION: DcHandlerThread
E AndroidRuntime: Process: com.android.phone, PID: 1955
E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Enum.ordinal()' on a null object reference
E AndroidRuntime: at com.mediatek.internal.telephony.dataconnection.DcFailCauseManager.getSuggestedRetryDelayByOp(DcFailCauseManager.java:218)
E AndroidRuntime: at com.mediatek.internal.telephony.dataconnection.MtkDataConnection.getSuggestedRetryDelay(MtkDataConnection.java:1541)
E AndroidRuntime: at com.mediatek.internal.telephony.dataconnection.MtkDataConnection$MtkDcActivatingState.processMessage(MtkDataConnection.java:937)
E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:992)
E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:809)
E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
And I'm trying to find out exactly what it is trying to do here in case there is something I can do to fix it.
Does anyone have any idea where I can find the source to the com.mediatek.internal.telephony.dataconnection.DcFailCauseManager?
Alternatively, I have the KDZ file for a similar build (Q610YM10e_00_0117.kdz). I have extracted the dz file and the contained bin files, but not having any luck trying to combine the multiple "system_a_999999.bin" files into a useable file system. The first file has what looks like a valid ext4 header, but if I just concatenate them all together the resulting file appears to be too small and fails to mount with the following error:
Code:
EXT4-fs (loop1): bad geometry: block count 932166 exceeds size of device (620672 blocks)
LM-Q610YM
Android Version: 8.1.0
Kernel Version 3.18.79
Build Number: Q11019
Software Version: V10e-AUS-XX
Thanks

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 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