If you ask me what I am saying, well I do not know, the matter is that this smartphone, Chinese, of medium to low quality and economic is known as LEAGOO Z5 LTE 37m, but here comes the strange issue, it is its processor , that on the internet, it is like mt6735, but the same device seen in flashtool is mt6737, and here the confusion begins, which is why not, for such echo with so many doubts take out the status of the aforementioned device in the context of recovery, and this is what I get,
petName=Z5
Lte
versionName=6.0-1488765164
resolution=854 * 480
versionCode=23
SDK_VERSION=23
RELEASE=6.0
Globe.REQUEST_HEADER_IMSI=748070103222388
Globe.REQUEST_HEADER_IMEI=352478081946651
BOARD=Android
BOOTLOADER=unknown
BRAND=LEAGOO
CPU_ABI=armeabi-v7a
CPU_ABI2=armeabi
DEVICE=Z5
DISPLAY=LEAGOO Z5 Lte(37m)_OS2.0_A_20170306
FINGERPRINT=alps/full_bd6737m_35g_a_m0/bd6737m_35g_a_m0:6.0/MRA58K/1488765164:user/dev-keys
HARDWARE=mt6735
HOST=jyunspl2-PowerEdge-R720
ID=MRA58
K
IS_DEBUGGABLE=false
MANUFACTURER=LEAGOO
MODEL=Z5 Lte
PRODUCT=Z5
RADIO=unknown
SERIAL=0123456789
ABCDEF
SUPPORTED_32_BIT_ABIS=[Ljava.lang.String;@758aea8
SUPPORTED_64_BIT_ABIS=[Ljava.lang.String;@3e9bdc
1
SUPPORTED_ABIS=[Ljava.lang.String;@69cc966
TAG=Build
TAGS=dev-keys
TIME=1488765741000
TYPE=user
UNKNOWN=unknown
USER=huchao
crashTime=2018-02-07_14-33-44
STACK_TRACE=java.lang.RuntimeException:
Unable to start activity ComponentInfo{com.android.settings/com.android.settings.Settings$NotificationAccessSettingsActivity}: android.app.Fragment$Instantiation
Exception: Unable to instantiate fragment com.android.settings.notification.ManagedServiceSettings$ScaryWarning
DialogFragment: make sure class name exists, is public, and has an empty constructor that is public
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2576)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2658)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4321)
at android.app.ActivityThread.-wrap15(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5737)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
Caused by: android.app.Fragment$Instantiation
Exception: Unable to instantiate fragment com.android.settings.notification.ManagedServiceSettings$ScaryWarning
DialogFragment: make sure class name exists, is public, and has an empty constructor that is public
at android.app.Fragment.instantiate(Fragment.java:635)
at android.app.FragmentState.instantiate(Fragment.java:111)
at android.app.FragmentManagerImpl.restoreAllState(FragmentManager.java:1885)
at android.app.FragmentController.restoreAllState(FragmentController.java:122)
at android.app.Activity.onCreate(Activity.java:927)
at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:648)
at android.app.Activity.performCreate(Activity.java:6390)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2523)
... 10 more
Caused by: java.lang.Instantiation
Exception: java.lang.Class<com.android.settings.notification.ManagedServiceSettings$ScaryWarningDialogFragment>
has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at android.app.Fragment.instantiate(Fragment.java:624)
... 18 more
android.app.Fragment$Instantiation
Exception: Unable to instantiate fragment com.android.settings.notification.ManagedServiceSettings$ScaryWarning
DialogFragment: make sure class name exists, is public, and has an empty constructor that is public
at android.app.Fragment.instantiate(Fragment.java:635)
at android.app.FragmentState.instantiate(Fragment.java:111)
at android.app.FragmentManagerImpl.restoreAllState(FragmentManager.java:1885)
at android.app.FragmentController.restoreAllState(FragmentController.java:122)
at android.app.Activity.onCreate(Activity.java:927)
at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:648)
at android.app.Activity.performCreate(Activity.java:6390)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2523)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2658)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4321)
at android.app.ActivityThread.-wrap15(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5737)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
Caused by: java.lang.
InstantiationException: java.lang.Class<com.android.settings.notification.ManagedServiceSettings$ScaryWarningDialogFragment>
has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at android.app.Fragment.instantiate(Fragment.java:624)
... 18 more
java.lang.Instantiation
Exception: java.lang.Class<com.android.settings.notification.ManagedServiceSettings$ScaryWarningDialogFragment>
has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at android.app.Fragment.instantiate(Fragment.java:624)
at android.app.FragmentState.instantiate(Fragment.java:111)
at android.app.FragmentManagerImpl.restoreAllState(FragmentManager.java:1885)
at android.app.FragmentController.restoreAllState(FragmentController.java:122)
at android.app.Activity.onCreate(Activity.java:927)
at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:648)
at android.app.Activity.performCreate(Activity.java:6390)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2523)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2658)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4321)
at android.app.ActivityThread.-wrap15(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5737)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
the issue is, according to this info, if we go to the information collected on the internet, there is only one leagoo z5 lte 37, and this is mtk6735, therefore this device in my possession is a clone? or is it original ?, although deadly and even so the PC sometimes detects it, I do not know how to recover it with so many doubts,
with flashtool the skatter is 6737, because the skater of the 6735 gives me incorrect, although I also have an error in the 6737 when I want to flash it,
the mistake is:
ERROR: S-DL-GET-DRAM-SETTING-FAIL (0x13be)
[EMI]: Obtain DRAM Failed!
[HINT]lease check your load matches to your target which is to be downloade
I hope I have been as specific as possible to the respect
good to the geniuses of this forum I appreciate I can advise the respect, to at least recover it and know that diantres is really an abraso to all
Related
Hi everyone,
I am new here on the forum, and the Streak is my very first Android phone. Just wanted to quickly say I really enjoy the community here and I like how everyone tries to help each other.
I noticed that a lot of people have been having problems with Camera forced close issues, which is what I've been experiencing as well. Please mind that this is my first Android phone, and my understanding of Linux is very limited.
I thought I'd post my findings so far in the forced close issues I've been experiencing. Here are some of what I think are the culprits behind the forced close:
Main Log:
1. First it tries to set unsupported parameters for the audio input, followed by more failed attempts to set other parameters
Code:
11-21 02:00:11.475 E/audio_input( 91): unsupported parameter:
x-pvmf/media-input-node/cap-config-interface;valtype=key_specific_value
11-21 02:00:11.475 E/audio_input( 91): VerifyAndSetParameter failed
2. Big Fail! It tries to load what looks to be a video encoder, and can't find it:
Code:
11-21 02:00:11.525 E/PVOMXEncNode( 91): PVMFOMXEncNode-Video_M4V::DoPrepare(): Cannot get component OMX.qcom.video.encoder.mpeg4 handle, try another component if available
11-21 02:00:11.525 E/PVOMXEncNode( 91): PVMFOMXEncNode-Video_M4V::DoPrepare(): Cannot get component OMX.PV.mpeg4enc handle, try another component if available
11-21 02:00:11.525 E/AuthorDriver( 91): Command 13 completed with error -17
11-21 02:00:11.535 E/MediaRecorder( 754): prepare failed: -17
11-21 02:00:11.535 E/videocamera( 754): prepare failed for /mnt/sdcard/DCIM/Camera/VID_20101121_020011.3gp
3. Dalvik Virtual Machine pops up an error, and throws it at Android for error handling:
Code:
11-21 02:00:11.545 F/dalvikvm( 754): Exception!!! threadid=1: thread exiting with uncaught exception (group=0x4001d7d8)
11-21 02:00:11.565 E/AndroidRuntime( 754): FATAL EXCEPTION: main
11-21 02:00:11.565 E/AndroidRuntime( 754): java.lang.RuntimeException: java.io.IOException: prepare failed.
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera.initializeRecorder(VideoCamera.java:1297)
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera.access$300(VideoCamera.java:99)
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera$MainHandler.handleMessage(VideoCamera.java:300)
Events Log:
1. Pretty straightforward -- video camera -- problem returns to android for handling during use of Media Recorder?
Code:
11-21 02:00:11.575 I/am_crash( 148): [754,com.android.camera,48709,java.io.IOException,prepare failed.,MediaRecorder.java,-2]
11-21 02:00:11.585 I/am_finish_activity( 148): [1193151496,8,com.android.camera/.VideoCamera,crashed]
11-21 02:00:11.585 I/am_pause_activity( 148): [1193151496,com.android.camera/.VideoCamera]
11-21 02:00:12.095 I/am_resume_activity( 148): [1190436808,2,com.dell.launcher/.Launcher]
System Log:
1. Same below -- start video camera, crash, Android handles the "oh no"s...
Code:
cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.android.camera/.Camera }
11-21 02:00:10.445 I/ActivityManager( 148): Starting activity: Intent { flg=0x4000000 cmp=com.android.camera/.VideoCamera (has extras) }
11-21 02:00:11.565 E/AndroidRuntime( 754): FATAL EXCEPTION: main
11-21 02:00:11.565 E/AndroidRuntime( 754): java.lang.RuntimeException: java.io.IOException: prepare failed.
I've also attached the processes log, processesthread log, and system.prop files for reference (I removed all wifi and carrier information at the bottom of the system.prop, but I don't think it's relevant)
I think the main cause of the crash is the media recorder trying to set unsupported parameters and missing video encoder. Not sure though. Any assistance would be greatly appreciated -- I am still looking into the problems, and will get back to everyone on my findings.
Good job...Guess the codec might also be dealing with audio and the bad parm is caused by the unregistered/missing codec? [noob]
Yes - I think definitely there were some serious problems with updating it from a non-00 baseband version.
I think dependencies are missing/broken from either updating from a non 00 baseband version or the flashboot method itself. Those with 00 baseband have it easier, as they already have all the dependencies and can upgrade using the
"copy package to /sdcard/update.pkg" method.
I gave up trying to find the dependencies that were broken, instead went the "downgrading, converting to baseband 00 version and upgrading back to Froyo" method.
I've finally got everything working (including 720p recording) with a combination of Homeiss' "How To Install Official Dell 2.2 Upgrade.pkg" and Geek78's "How to go back from 21 to 00 builds" guide with a little alteration suggested by llecaroz (from modaco forum).
I think this downgrade first to Baseband 00 first than upgrade should fix all problems. The trick is to downgrade to downgrade to 1.6 that matches your baseband (21,31) first! In my case, I had a baseband 21 version.
Suggestions:
- I suggest to downgrade using Geek78's guide first (because, based on my experience, downgrading from 21 2.1 -> 00 1.6 ends up with DELL forever logo).
- If you end up with a "FOTA version error" thingy, you need to flash with a different recovery file (it changes the recovery version from 21 to 00)
- If getting "flash_image: not found" error, it means you are missing the binary. Get it from cyanogen.
Good luck with Homeiss' and Geek78's guide.
I can re-compile a more comprehensive guide, but I think I am unable to place links in here.
If you have upgraded the fastboot way (with the 3 files Stephen provided) You will have FCs on 720p recording! I have downgraded mine to 6267 and then upgraded with the pkg file! Now 720p works perfect!
Hi.
Summary: the AndroidRuntime process fails when starting the Connectivity Service, causing my phone into a boot loop.
Sorry for the very verbose post.
Background: I've spent quite a bit of time trying to resolve a problem that causes my Sony Ericsson Xperia X10 Mini (from O2) to go into a boot loop. I've rooted the phone some time ago using this process: (sorry the forum prevents me from posting link, please copy and paste this: android.doshaska.net/x10miniroot).
I then proceeded to remove some of the redundant programs from /system/app.
Everything worked fine for several weeks until the phone started complaining about the storage being filled up. I could see that /data was getting full and I suspected that the K9 email client I had installed was using lots f space to keep the IMAP folders synced.
I can't remember if the phone rebooted itself or if I did it manually, but it never managed to boot up again, and is ever since stuck at the Sony Ericsson logo.
adb logcat tells me that the AndroidRuntime process fails when starting the Connectivity Service. It's stuck in this loop, but I've isolated one single loop in the attachment logcat.txt. The crash file references has been attached as 1279210811.txt.
The final fatal crash is:
I/SystemServer( 1297): Starting Connectivity Service.
W/dalvikvm( 1297): threadid=51: thread exiting with uncaught exception (group=0x2aac9a28)
E/AndroidRuntime( 1297): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception
E/AndroidRuntime( 1297): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 1297): java.lang.NullPointerException
E/AndroidRuntime( 1297): at android.app.ActivityThread.getProvider(ActivityThread.java:3938)
E/AndroidRuntime( 1297): at android.app.ActivityThread.acquireProvider(ActivityThread.java:3967)
E/AndroidRuntime( 1297): at android.app.ApplicationContext$ApplicationContentResolver.acquireProvider(ApplicationContext.java:1527)
E/AndroidRuntime( 1297): at android.content.ContentResolver.acquireProvider(ContentResolver.java:579)
E/AndroidRuntime( 1297): at android.content.ContentResolver.query(ContentResolver.java:147)
E/AndroidRuntime( 1297): at android.provider.Settings$NameValueCache.getString(Settings.java:476)
E/AndroidRuntime( 1297): at android.provider.Settings$Secure.getString(Settings.java:1701)
E/AndroidRuntime( 1297): at android.provider.Settings$Secure.getInt(Settings.java:1741)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.getPersistedNetworkPreference(ConnectivityService.java:182)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:123)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:47)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:87)
I've had a look at the JavDoc for android.app.ActivityThread.getProvider, but I've not been able to find any useful information. I have to guess that the start-up process fails to read the provider (network) specific settings for some reason. I don't have a clue whether the source is a file, database or something else.
A wild guess is that something got corrupted when the data partition filled up. There are some upset earlier in the log (line 180) when the PackageManager is reading an XML file that relates to the PackageManager settings that seems to have been corrupted:
E/PackageManager( 1297): Error reading package manager settings E/PackageManager( 1297): org.xmlpull.v1.XmlPullParserException:
Premature end of document. (position:line -1, column -1) caused by:
org.apache.harmony.xml.ExpatParser$ParseException: At line 1, column 0: no element found
I've seen a few similar posts, but nothing exactly like this nor anything that I could use to resolve it.
Stupid section
I've got myself into this through a combination of stupidity and bad luck. I've backed up all .APK that I've removed and created a log of what I removed (that I'm still looking for). I thought this was all that I needed and I don't have a full backup.
Unfortunately, the root access now gives me a segmentation fault and the root process requires the GUI to work, so I can't repeat the process. I don't want to try another root process before I've tried what I can to get the phone back in a reasonable state.
Fortunately, I still have full adb access, so I have visibility and some control over the phone.
Any help on this would be much appreciated. At least I've saved you the time pointing out that I'm an idiot not doing a full backup
Regards,
Dan
As the title says, whenever I open a folder on the desktop File Manager crashes. Remix OS version is 2.0.102, build 5.1.1-B2016030106. Has anyone else experienced this?
Error message:
Code:
exceptionClassName: java.lang.NullPointerException
exceptionMessage: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
throwFileName: DocumentsActivity.java
throwClassName: com.jide.filemanager.DocumentsActivity
throwMethodName: getParentDirectory
throwLineNumber: 1571
stackTrace: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
at com.jide.filemanager.DocumentsActivity.getParentDirectory(DocumentsActivity.java:1571)
at com.jide.filemanager.DirectoryFragment.onCreateView(DirectoryFragment.java:379)
at android.app.Fragment.performCreateView(Fragment.java:2053)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:894)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.BackStackRecord.run(BackStackRecord.java:834)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1452)
at android.app.FragmentManagerImpl$1.run(FragmentManager.java:447)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5401)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
How do you get anything to open from the desktop? I have to use the toolbar to do anything.
putr4s said:
As the title says, whenever I open a folder on the desktop File Manager crashes. Remix OS version is 2.0.102, build 5.1.1-B2016030106. Has anyone else experienced this?
Error message:
Code:
exceptionClassName: java.lang.NullPointerException
exceptionMessage: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
throwFileName: DocumentsActivity.java
throwClassName: com.jide.filemanager.DocumentsActivity
throwMethodName: getParentDirectory
throwLineNumber: 1571
stackTrace: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
at com.jide.filemanager.DocumentsActivity.getParentDirectory(DocumentsActivity.java:1571)
at com.jide.filemanager.DirectoryFragment.onCreateView(DirectoryFragment.java:379)
at android.app.Fragment.performCreateView(Fragment.java:2053)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:894)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.BackStackRecord.run(BackStackRecord.java:834)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1452)
at android.app.FragmentManagerImpl$1.run(FragmentManager.java:447)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5401)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Click to expand...
Click to collapse
hi,
I created a folder and placed some apps in it on desktop, afterwards tried to open folder, but it did not respon.d I had to delete folder eventually.
So, yes, i agree the folders are buggy.,
(Not working.?)
good luck
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
fsuinnc said:
How do you get anything to open from the desktop? I have to use the toolbar to do anything.
Click to expand...
Click to collapse
hi,
i double click on the app icon (desktop) and it launches /open.
Good luck
Hi,
Ive decompiled the miui camera (miui 12, Redmi Note 8 Pro) and have recompiled it and included some libs, I have renamed the package and a few permissions (is this the cause of the error?) so as not to cause conflicts with the system camera app. I run into a problem with registerMarshalQueryable.. which from what I can tell is a camera2 method/class, so really it should just be there in the system, unless its looking in the wrong place?
Below is the error
2020-09-06 16:11:26.182 2694-2694/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.android.newcamera, PID: 2694
java.lang.NoSuchMethodError: No static method registerMarshalQueryable(Landroid/hardware/camera2/marshal/MarshalQueryableV in class Landroid/hardware/camera2/marshal/MarshalRegistry; or its super classes (declaration of 'android.hardware.camera2.marshal.MarshalRegistry' appears in /system/framework/framework.jar)
at com.android.camera2.vendortag.struct.MarshalQueryableRegister.preload(MarshalQueryableRegister.java:1)
at com.android.camera.CameraAppImpl.onCreateApplicationDelegate(CameraAppImpl.java:11)
at com.android.camera.CameraAppImpl.onCreateApplicationDelegate(CameraAppImpl.java:1)
at miui.external.Application.attachBaseContext(Application.java:4)
at android.app.Application.attach(Application.java:376)
at android.app.Instrumentation.newApplication(Instrumentation.java:1156)
at android.app.LoadedApk.makeApplication(LoadedApk.java:1222)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6562)
at android.app.ActivityThread.access$1500(ActivityThread.java:230)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1911)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:224)
at android.app.ActivityThread.main(ActivityThread.java:7551)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:539)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:995)
Click to expand...
Click to collapse
Happens with the stock MIUI Dialler as well as Google Dialler. I can't find anything wrong in settings, and a reflash didn't help. Never had this problem on stock global MIUI.
java.lang.NullPointerException: Attempt to invoke virtual method 'int android.os.Bundle.getInt(java.lang.String, int)' on a null object reference
at com.android.incallui.aiassistant.AiAssistantUtil.getAiVersionCode(Unknown Source:19)
at com.android.incallui.aiassistant.AiAssistantUtil.supportAi(Unknown Source:0)
at com.android.incallui.aiassistant.AiAssistantUtil.getAiStatus(Unknown Source:9)
at com.android.incallui.CallCardPresenter.updateSingleDisplayInfo(Unknown Source:238)
at com.android.incallui.CallCardPresenter.handleCallCardViewByCallCardState(Unknown Source:40)
at com.android.incallui.CallCardPresenter.updateInfoByState(Unknown Source:24)
at com.android.incallui.CallCardPresenter.onStateChange(Unknown Source:403)
at com.android.incallui.CallCardPresenter.init(Unknown Source:79)
at com.android.incallui.CallCardFragment.onActivityCreated(Unknown Source:17)
at android.app.Fragment.performActivityCreated(Unknown Source:13)
at android.app.FragmentManagerImpl.moveToState(Unknown Source:631)
at android.app.FragmentManagerImpl.addAddedFragments(Unknown Source:46)
at android.app.FragmentManagerImpl.executeOpsTogether(Unknown Source:129)
at android.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(Unknown Source:99)
at android.app.FragmentManagerImpl.execPendingActions(Unknown Source:21)
at android.app.FragmentManagerImpl$1.run(Unknown Source:2)
at android.os.Handler.handleCallback(Unknown Source:2)
at android.os.Handler.dispatchMessage(Unknown Source:4)
at android.os.Looper.loop(Unknown Source:242)
at android.app.ActivityThread.main(Unknown Source:98)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(Unknown Source:11)
at com.android.internal.os.ZygoteInit.main(Unknown Source:275)
Click to expand...
Click to collapse