Nope, we are awaiting an update which is newer than 9.1.300 for mate 20x. I read that in mate 20pro forum that it has updated with 9.1.306 and they reported that crash problem was solved for mate 20 pro
Nope, we are awaiting an update which is newer than 9.1.300 for mate 20x. I read that in mate 20pro forum that it has updated with 9.1.306 and they reported that crash problem was solved for mate 20 pro
Nope, we are awaiting an update which is newer than 9.1.300 for mate 20x. I read that in mate 20pro forum that it has updated with 9.1.306 and they reported that crash problem was solved for mate 20 pro
i have already installed 9.1.300 + patch1 update it's still crashing. Especially on youtube.He is saying that a patch to 9.1.0.300 was released yesterday via HiSuite. It does not change the version number, and the release notes say that it fixes sound problems with 9.1.0.300. Perhaps it also fixes the problems with crashing experienced by some users?
AJP
Sometimes chrome some time other apps are crashing after using a minute or more and then OS crash and display goes black and lock the screen then I have to unlock again. Any body facing this issue? .......
.........
Update-5
11-7-2019:- Today an update popup I don't know what kind of update it is because in the Emui version there is no change but came a update and unfortunately I can not read the update text I just press the install button and install the update I think some kind of "Patch" word written there in update popup.
So waiting and observing what is that update actually
Hmm... So, the patch did not fix the random restarts problem? WTF!
I have the same problem after updating to 9.1. Currently. I'm running on a rolled back's 9.0!
[ 07-11 23:50:31.239 3860: 3860 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.mgoogle.android.gms, PID: 3860
java.lang.RuntimeException: Unable to start receiver org.microg.gms.gcm.TriggerReceiver: java.lang.IllegalStateException: Not allowed to start service Intent { act=org.microg.gms.gcm.mcs.CONNECT cmp=com.mgoogle.android.gms/org.microg.gms.gcm.McsService (has extras) }: app is in background uid UidRecord{cbfd8fe u0a198 RCVR idle change:uncached procs:1 seq(0,0,0)}
at android.app.ActivityThread.handleReceiver(ActivityThread.java:3978)
at android.app.ActivityThread.access$2300(ActivityThread.java:273)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2036)
at android.os.Handler.dispatchMessage(Handler.java:112)
at android.os.Looper.loop(Looper.java:216)
at android.app.ActivityThread.main(ActivityThread.java:7593)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:987)
Caused by: java.lang.IllegalStateException: Not allowed to start service Intent { act=org.microg.gms.gcm.mcs.CONNECT cmp=com.mgoogle.android.gms/org.microg.gms.gcm.McsService (has extras) }: app is in background uid UidRecord{cbfd8fe u0a198 RCVR idle change:uncached procs:1 seq(0,0,0)}
at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1810)
at android.app.ContextImpl.startService(ContextImpl.java:1765)
at android.content.ContextWrapper.startService(ContextWrapper.java:664)
at android.content.ContextWrapper.startService(ContextWrapper.java:664)
at android.support.v4.content.WakefulBroadcastReceiver.startWakefulService(WakefulBroadcastReceiver.java:102)
at org.microg.gms.gcm.TriggerReceiver.onReceive(TriggerReceiver.java:88)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:3969)
[ 07-12 00:38:19.883 1242:12805 E/AndroidRuntime ]
*** FATAL EXCEPTION IN SYSTEM PROCESS: ThreadName
java.lang.UnsatisfiedLinkError: No implementation found for long com.huawei.wallet.tz.WalletCa.walletTaUnInitImpl() (tried Java_com_huawei_wallet_tz_WalletCa_walletTaUnInitImpl and Java_com_huawei_wallet_tz_WalletCa_walletTaUnInitImpl__)
at com.huawei.wallet.tz.WalletCa.walletTaUnInitImpl(Native Method)
at com.huawei.wallet.tz.WalletCa.walletTaUnInit(WalletCa.java:59)
at com.huawei.wallet.sdk.common.ta.WalletTaManager.unInitTA(WalletTaManager.java:882)
at com.huawei.wallet.sdk.business.diploma.util.DiplomaUtil.unInitTA(DiplomaUtil.java:339)
at com.huawei.wallet.sdk.WalletFactory.checkResetProgress(WalletFactory.java:810)
at com.huawei.wallet.sdk.WalletFactory.access$000(WalletFactory.java:39)
at com.huawei.wallet.sdk.WalletFactory$1.run(WalletFactory.java:247)
at android.os.Handler.handleCallback(Handler.java:907)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:216)
at android.os.HandlerThread.run(HandlerThread.java:65)
actually how to solve this annoying issue?I'm experiencing the same random crashes on my Mate 20 X (EVR-L29C636) running 9.1.0.300(patch01).
At surface level there is no specific action/app that seems to be causing the crash (it restarts at random, even when i leave the phone on overnight)
Wiping the phone both from settings & recovery menu did not solve the issue.
However, looking at the logcat yielded some interesting finds. Out of the 12 Crash Logs obtained, there were 2 major fatal errors:
Code:[ 07-11 23:50:31.239 3860: 3860 E/AndroidRuntime ] FATAL EXCEPTION: main Process: com.mgoogle.android.gms, PID: 3860 java.lang.RuntimeException: Unable to start receiver org.microg.gms.gcm.TriggerReceiver: java.lang.IllegalStateException: Not allowed to start service Intent { act=org.microg.gms.gcm.mcs.CONNECT cmp=com.mgoogle.android.gms/org.microg.gms.gcm.McsService (has extras) }: app is in background uid UidRecord{cbfd8fe u0a198 RCVR idle change:uncached procs:1 seq(0,0,0)} at android.app.ActivityThread.handleReceiver(ActivityThread.java:3978) at android.app.ActivityThread.access$2300(ActivityThread.java:273) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2036) at android.os.Handler.dispatchMessage(Handler.java:112) at android.os.Looper.loop(Looper.java:216) at android.app.ActivityThread.main(ActivityThread.java:7593) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:987) Caused by: java.lang.IllegalStateException: Not allowed to start service Intent { act=org.microg.gms.gcm.mcs.CONNECT cmp=com.mgoogle.android.gms/org.microg.gms.gcm.McsService (has extras) }: app is in background uid UidRecord{cbfd8fe u0a198 RCVR idle change:uncached procs:1 seq(0,0,0)} at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1810) at android.app.ContextImpl.startService(ContextImpl.java:1765) at android.content.ContextWrapper.startService(ContextWrapper.java:664) at android.content.ContextWrapper.startService(ContextWrapper.java:664) at android.support.v4.content.WakefulBroadcastReceiver.startWakefulService(WakefulBroadcastReceiver.java:102) at org.microg.gms.gcm.TriggerReceiver.onReceive(TriggerReceiver.java:88) at android.app.ActivityThread.handleReceiver(ActivityThread.java:3969)
com.mgoogle.android.gms & org.microg.gms.gcm refers to the MicroG plugin used for Google login in Youtube VancedCode:[ 07-12 00:38:19.883 1242:12805 E/AndroidRuntime ] *** FATAL EXCEPTION IN SYSTEM PROCESS: ThreadName java.lang.UnsatisfiedLinkError: No implementation found for long com.huawei.wallet.tz.WalletCa.walletTaUnInitImpl() (tried Java_com_huawei_wallet_tz_WalletCa_walletTaUnInitImpl and Java_com_huawei_wallet_tz_WalletCa_walletTaUnInitImpl__) at com.huawei.wallet.tz.WalletCa.walletTaUnInitImpl(Native Method) at com.huawei.wallet.tz.WalletCa.walletTaUnInit(WalletCa.java:59) at com.huawei.wallet.sdk.common.ta.WalletTaManager.unInitTA(WalletTaManager.java:882) at com.huawei.wallet.sdk.business.diploma.util.DiplomaUtil.unInitTA(DiplomaUtil.java:339) at com.huawei.wallet.sdk.WalletFactory.checkResetProgress(WalletFactory.java:810) at com.huawei.wallet.sdk.WalletFactory.access$000(WalletFactory.java:39) at com.huawei.wallet.sdk.WalletFactory$1.run(WalletFactory.java:247) at android.os.Handler.handleCallback(Handler.java:907) at android.os.Handler.dispatchMessage(Handler.java:105) at android.os.Looper.loop(Looper.java:216) at android.os.HandlerThread.run(HandlerThread.java:65)
com.huawei.wallet refers to Huawei Wallet
After removing Youtube Vanced & MicroG, only the Huawei Wallet error remained. However, there was no Wallet app installed on my phone. I tried installing the apk from Aptoide but it could not initialise after installing.
So I'm stuck at the moment on how to solve this issue. Those of you who are experiencing crashes may have the same issue. Feel free to check your logcat and share your findings. Here are some guides on how to generate them:
https://android.stackexchange.com/questions/33216/how-can-i-get-a-logcat
https://support.citrix.com/article/CTX232375
https://www.xda-developers.com/how-to-take-logs-in-android/
Be sure to format your post so as to not create really long text walls.
Cheers.
i got "Cause: seccomp prevented call to disallowed arm64 system call 116" from logcat.
Is there any difference with 9.1.0.300 (C636E3R1P11) and 9.1.0.300 (C636E3R2P1)?
Is there any updates for 9.1.0.300? Patch 02 etc..? I have to returned to hiversion 9.0.0.206 four days ago.
I see from forums that mate 20 pro has received lots of updates to solve this problem, May the mate 20x is a stepchild for Huawei.
I'm not sure about the error.
For the 2nd question. R2P1 has few more preloaded Apps than R1P1.1 That's all. They are the same EMUI 9.1 technically. So, random restarts is still there be it running on R2P1 or R1P11!.
---------- Post added at 01:30 AM ---------- Previous post was at 01:28 AM ----------
Has the patches finally fixed the random restarts in Mate 20 Pro once and for all?
Let's hope that Huawei will push the fixes to Mate 20X users asap.
In the mean time! I'm enjoying the loud speaker output on EMUI 9.0! That's the only positive side of being stuck with EMUI 9.0! Haha!
I think mine is fine now. I did clear cache and format in erecovery, then changed vpn so i got 9.1 ota and when installed i did clear cache and format again in erecovery. No crashes so far.
You mean you connect via VPN to download the 9.1 file instead of normal wifi network?
Yeah, i live in sweden, so connected via vpn to Hong Kong, then i got new update ota.
Thank you very much for these ROMs, much appreciated! How did you get them btw? The only source i found was Easy-Firmware but they required payment. Did you have a rooted phone and extracted the firmware?Here The Firmware
I testet only for C432 and if the mistakes are gone I can not say yet
C432 9.1.0.310
C636 9.1.0.310
Thank you. Does the Call Recorder only work with Huawei Dialer or any Dialer, eg Truecaller?For people who miss the Emui Call Recorder and AR Measure can Download in Attachment.
Unpack the zip and install as normal apk.
After install Call Recorder reboot the Phone!
Yes you can interchange between R1P11 and R2P1 without any issues, as long as the Model region is the same (eg C636)I believe there are different models of C636. I have C636E3R1P11. Do you think your file would flash fine on my device?
C185 = Middle East. Here are the full region codesOk what can i say,Audio Quality is better,No cashes or reboots.After install 310 i do a Factory Reset.
On 300 after Factory Reset after setup crashes and Bootloops,but not with 310 and all is ok.
---------- Post added at 12:26 PM ---------- Previous post was at 12:18 PM ----------
Sorry not at this Moment,i found no Firmware from c185.Which Region is C185?
[ 07-11 23:50:31.239 3860: 3860 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.mgoogle.android.gms, PID: 3860
java.lang.RuntimeException: Unable to start receiver org.microg.gms.gcm.TriggerReceiver: java.lang.IllegalStateException: Not allowed to start service Intent { act=org.microg.gms.gcm.mcs.CONNECT cmp=com.mgoogle.android.gms/org.microg.gms.gcm.McsService (has extras) }: app is in background uid UidRecord{cbfd8fe u0a198 RCVR idle change:uncached procs:1 seq(0,0,0)}
at android.app.ActivityThread.handleReceiver(ActivityThread.java:3978)
at android.app.ActivityThread.access$2300(ActivityThread.java:273)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2036)
at android.os.Handler.dispatchMessage(Handler.java:112)
at android.os.Looper.loop(Looper.java:216)
at android.app.ActivityThread.main(ActivityThread.java:7593)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:987)
Caused by: java.lang.IllegalStateException: Not allowed to start service Intent { act=org.microg.gms.gcm.mcs.CONNECT cmp=com.mgoogle.android.gms/org.microg.gms.gcm.McsService (has extras) }: app is in background uid UidRecord{cbfd8fe u0a198 RCVR idle change:uncached procs:1 seq(0,0,0)}
at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1810)
at android.app.ContextImpl.startService(ContextImpl.java:1765)
at android.content.ContextWrapper.startService(ContextWrapper.java:664)
at android.content.ContextWrapper.startService(ContextWrapper.java:664)
at android.support.v4.content.WakefulBroadcastReceiver.startWakefulService(WakefulBroadcastReceiver.java:102)
at org.microg.gms.gcm.TriggerReceiver.onReceive(TriggerReceiver.java:88)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:3969)
[ 07-12 00:38:19.883 1242:12805 E/AndroidRuntime ]
*** FATAL EXCEPTION IN SYSTEM PROCESS: ThreadName
java.lang.UnsatisfiedLinkError: No implementation found for long com.huawei.wallet.tz.WalletCa.walletTaUnInitImpl() (tried Java_com_huawei_wallet_tz_WalletCa_walletTaUnInitImpl and Java_com_huawei_wallet_tz_WalletCa_walletTaUnInitImpl__)
at com.huawei.wallet.tz.WalletCa.walletTaUnInitImpl(Native Method)
at com.huawei.wallet.tz.WalletCa.walletTaUnInit(WalletCa.java:59)
at com.huawei.wallet.sdk.common.ta.WalletTaManager.unInitTA(WalletTaManager.java:882)
at com.huawei.wallet.sdk.business.diploma.util.DiplomaUtil.unInitTA(DiplomaUtil.java:339)
at com.huawei.wallet.sdk.WalletFactory.checkResetProgress(WalletFactory.java:810)
at com.huawei.wallet.sdk.WalletFactory.access$000(WalletFactory.java:39)
at com.huawei.wallet.sdk.WalletFactory$1.run(WalletFactory.java:247)
at android.os.Handler.handleCallback(Handler.java:907)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:216)
at android.os.HandlerThread.run(HandlerThread.java:65)
Just an estimate, I could be wrong. Then again, so could youwhere do you know that only %10 experienced this random crash problem. Your estimation is totaly wrong, i guess.
Don't downgrade your firmware just yet. Try these few stepsSorry, just to clarify, you mean I should downgrade firmware with HiSuite and afterwards HiSuite will be able to update firmware to the latest .310 version?
Just don't want to go through all this and stay on the same current .300 firmware
Follow thisWhat is dload method? Any thread that explains how to use method and what method actually is?