Develop Bugs

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

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

Stock camera and gcam crashes after flashing 4k enable fix in twrp rn5

Hey, so i flashed a 4k fix so i could shoot 4k videos with gcam on stock 12.0.2 rom rooted with magisk and bootloader unlocked and all hell broke loose. Both stock camera and every gcam i try crashes. Please, if you can save me without losing my data it would be a dream. Im not an expert so I'll just post the logs below and pray an expert sees them and helps me.
" java.lang.RuntimeException: java.lang.IllegalStateException: Unable to get camera characteristics for 1
at lmg.run(Unknown Source:26)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
at lky.run(Unknown Source:5)
Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Unable to get camera characteristics for 1
at java.util.concurrent.FutureTask.report(FutureTask.java:123)
at java.util.concurrent.FutureTask.get(FutureTask.java:193)
at oxa.get(Unknown Source:4)
at lmg.run(Unknown Source:15)
... 4 more
Caused by: java.lang.IllegalStateException: Unable to get camera characteristics for 1
at mjt.a(Unknown Source:73)
at mju.a(Unknown Source:115)
at mkl.b(Unknown Source:4)
at mks.b(Unknown Source:2)
at lvz.b(Unknown Source:26)
at lwb.b(Unknown Source:9)
at lwb.b(Unknown Source:9)
at jzk.a(Unknown Source:161)
at ebv.get(Unknown Source:33)
at pmn.get(Unknown Source:15)
at ebs.get(Unknown Source:10)
at pmn.get(Unknown Source:15)
at pmu.a(Unknown Source:78)
at ebg.get(Unknown Source:16)
at pmn.get(Unknown Source:15)
at pmu.a(Unknown Source:35)
at bmr.a(Unknown Source:29)
at oxf.run(Unknown Source:29)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
at lmh.run(Unknown Source:2)
at lmg.run(Unknown Source:0)
... 4 more
Caused by: android.hardware.camera2.CameraAccessException: CAMERA_DISCONNECTED (2): Camera service is currently unavailable
at android.hardware.camera2.CameraManager.getCameraCharacteristics(CameraManager.java:264)
at mjt.a(Unknown Source:15)
... 26 more

Just try and flash the module again so TWRP will delete it
Update me if you already formated the phone or if i truly helped

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

[Help Request] Huawei Watch 3-F60 [Model GLL-AL00] install GMS / Play Store

Trying to follow this thread, says the HW3 is eligible, but unsuccessful in logging into MicroG. Has anyone else been able to install Play Store?
Steps so far:
Code:
adb shell pm disable-user com.android.packageinstaller
adb install huagu3.apk
adb shell appops set com.bishua666.luxxx1 GET_USAGE_STATS allow
Disable route to internet.
Set date on phone to July 20, 2020 and sync watch.
Open huagu3 on watch and allow full access
Step 1 successful.
Step 2 immediately closes app
adb install 01_MicroG.apk -> success
Open MicroG and try to add account, app immediately closes.
logcat:
Code:
--------- beginning of crash huagu3
07-20 15:56:27.370 12290 12290 E AndroidRuntime: FATAL EXCEPTION: main
07-20 15:56:27.370 12290 12290 E AndroidRuntime: Process: com.bishua666.luxxx1, PID: 12290
07-20 15:56:27.370 12290 12290 E AndroidRuntime: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.DATE_SETTINGS }
MicroG:
07-20 15:56:37.557 12395 12395 E AndroidRuntime: FATAL EXCEPTION: main
07-20 15:56:37.557 12395 12395 E AndroidRuntime: Process: com.google.android.gms:ui, PID: 12395
07-20 15:56:37.557 12395 12395 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.gms/org.microg.gms.auth.login.LoginActivity}: java.lang.UnsupportedOperationException
Appreciate any assistance in advance, thanks.
Ref:
Install native GMS, Google Play Store directly on Harmony OS 3.0 (Tested Feb 2023)
How to install GMS Harmony OS 3.1 has newer processes https://forum.xda-developers.com/t/install-native-gms-on-harmony-os-3-1-tested-may-2023-on-huawei-mate-x3.4583737/ *** IMPORTANT NOTE *** I am working on the step by step instructions, stay...
forum.xda-developers.com
Current Eligible Devices:
Huawei Wear Series
HUAWEI WATCH 3

Hi,
Exactly the same for me ...