[help]CM14.0 boot failed and stuck at CM logo - Nexus 5 Developer Discussion [Developers Only]

I just compiled CM14 and build success. But it failed to boot. Screen freeze after seconds of CM boot animation.
Here's the logcat ,
I'll appreciate if someone can help me

Might I ask how did you get the logcat?
I'm getting stuck at the boot logo myself, but I could not dump the logcat. Did you use a UART cable?

morphvale said:
Might I ask how did you get the logcat?
I'm getting stuck at the boot logo myself, but I could not dump the logcat. Did you use a UART cable?
Click to expand...
Click to collapse
I don't have an UART cable,so I lunched a cm_hammerhead-eng version for the logcat. eng version is for debug itself. then run " adb logcat > *.txt" as sudoer with just a normal cable connected to PC. But you can't get full booting logcat.
I think we need to wait for something new until anyone can fix the errors

So, I managed to finally boot it, but com.android.phone keeps crashing. Again could not get the log, probably because usb debugging might be off by default.
{
"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"
}
Sent from my Nexus 5 using Tapatalk

@morphvale how have you managwr to boot it? Anf which zip have you used??

Not sure what you mean.. It's a personal build, using some CM source and some of the current CM merges.
LE: Alright, so I've managed to boot it up fine. CM Setup Wizard keeps crashing, but I just deleted the apk. There's also a new commit which I think should fix it, but did not pick it yet.
As before, com.android.phone keeps crashing, but I've managed to get the logs now, and it seems related to this. Will have to dig in deeper to see what causes it.
01-03 18:49:38.111 1754 1754 D AndroidRuntime: Shutting down VM
01-03 18:49:38.116 1754 1754 E AndroidRuntime: FATAL EXCEPTION: main
01-03 18:49:38.116 1754 1754 E AndroidRuntime: Process: com.android.phone, PID: 1754
01-03 18:49:38.116 1754 1754 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.internal.telephony.Phone.startMonitoringImsService()' on a null object reference
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5364)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.app.ActivityThread.-wrap2(ActivityThread.java)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1528)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6077)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.internal.telephony.Phone.startMonitoringImsService()' on a null object reference
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:223)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:93)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java:285)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at com.android.phone.PhoneApp.onCreate(PhoneApp.java:41)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1025)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5361)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: ... 8 more
Worst part is, no GSM network so far, and baseband appears as unkown.

aby good bews??

morphvale said:
Not sure what you mean.. It's a personal build, using some CM source and some of the current CM merges.
LE: Alright, so I've managed to boot it up fine. CM Setup Wizard keeps crashing, but I just deleted the apk. There's also a new commit which I think should fix it, but did not pick it yet.
As before, com.android.phone keeps crashing, but I've managed to get the logs now, and it seems related to this. Will have to dig in deeper to see what causes it.
01-03 18:49:38.111 1754 1754 D AndroidRuntime: Shutting down VM
01-03 18:49:38.116 1754 1754 E AndroidRuntime: FATAL EXCEPTION: main
01-03 18:49:38.116 1754 1754 E AndroidRuntime: Process: com.android.phone, PID: 1754
01-03 18:49:38.116 1754 1754 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.internal.telephony.Phone.startMonitoringImsService()' on a null object reference
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5364)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.app.ActivityThread.-wrap2(ActivityThread.java)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1528)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6077)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.internal.telephony.Phone.startMonitoringImsService()' on a null object reference
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:223)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:93)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java:285)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at com.android.phone.PhoneApp.onCreate(PhoneApp.java:41)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1025)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5361)
01-03 18:49:38.116 1754 1754 E AndroidRuntime: ... 8 more
Worst part is, no GSM network so far, and baseband appears as unkown.
Click to expand...
Click to collapse
yeap now there's no com.android.phone FCs but It reboots when make phone call

That was fixed some time ago by this commit, which also got merged yesterday: http://review.cyanogenmod.org/#/c/162359/
However, baseband is still unknown for some reason.

They have this running on N6 its quite nice i have both phones N5 too. Im sure this will get done soon

Related

Dialing '0 to 999' followed by '#' causes phone app to crash

Some kind of speed dial thingy? SIM card contact shortcut?
Couldn't find any info on it. Doesn't happen to everyone though.
Nexus 6 Rooted 6.0.1 crashes
Nexus 5 Rooted 6.0.1 works
Nexus 5 Stock 6.0.1 crashes
Moto G 2014 Stock Works
Dialed: 1#
Code:
01-04 16:55:25.720 16988 16988 E AndroidRuntime: FATAL EXCEPTION: main
01-04 16:55:25.720 16988 16988 E AndroidRuntime: Process: com.google.android.dialer, PID: 16988
01-04 16:55:25.720 16988 16988 E AndroidRuntime: android.view.WindowManager$BadTokenException: Unable to add window -- token null is not for an application
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewRootImpl.setView(ViewRootImpl.java:571)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:310)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:85)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.app.Dialog.show(Dialog.java:319)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at com.android.dialer.SpecialCharSequenceMgr.handleAdnQuery(SpecialCharSequenceMgr.java:286)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at com.android.dialer.SpecialCharSequenceMgr.handleAdnEntry(SpecialCharSequenceMgr.java:257)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at com.android.dialer.SpecialCharSequenceMgr.handleChars(SpecialCharSequenceMgr.java:140)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at com.android.dialer.dialpad.DialpadFragment.afterTextChanged(DialpadFragment.java:301)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.widget.TextView.sendAfterTextChanged(TextView.java:8004)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.widget.TextView$ChangeWatcher.afterTextChanged(TextView.java:10165)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.text.SpannableStringBuilder.sendAfterTextChanged(SpannableStringBuilder.java:1043)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.text.SpannableStringBuilder.replace(SpannableStringBuilder.java:560)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.text.SpannableStringBuilder.replace(SpannableStringBuilder.java:492)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.text.SpannableStringBuilder.replace(SpannableStringBuilder.java:491)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.text.method.NumberKeyListener.onKeyDown(NumberKeyListener.java:121)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.widget.TextView.doKeyDown(TextView.java:6095)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.widget.TextView.onKeyDown(TextView.java:5908)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at com.android.dialer.dialpad.DialpadFragment.keyPressed(DialpadFragment.java:809)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at com.android.dialer.dialpad.DialpadFragment.onPressed(DialpadFragment.java:883)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at com.android.phone.common.dialpad.DialpadKeyButton.setPressed(DialpadKeyButton.java:120)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.View.setPressed(View.java:7871)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.View.onTouchEvent(View.java:10313)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.View.dispatchTouchEvent(View.java:9300)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2547)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2240)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2553)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2254)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2553)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2254)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2553)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2254)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2553)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2254)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2553)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2254)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2553)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2254)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2553)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2254)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2553)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2254)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2553)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2254)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2553)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2254)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2553)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2254)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2553)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2254)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at com.android.internal.policy.PhoneWindow$DecorView.superDispatchTouchEvent(PhoneWindow.java:2403)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at com.android.internal.policy.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1737)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at android.app.Activity.dispatchTouchEvent(Activity.java:2771)
01-04 16:55:25.720 16988 16988 E AndroidRuntime: at com.android.dialer
Whoa, crashes the phone app on my Nexus 6 - 6.0.1 (MMB29K) - Rooted.
Ugly....
-C
wonder why you do this? dial a number which followed by #!! what kind of number you trying to dial!!
and it crashes for me too.
Nexus 6 with PureNexus 1/03 6.0.1, no crash.And I find out that for example if you dial 4# it will automatically load the forth number in your contact so you could dial it right away. Kinda connivent.
Sent from my Nexus 6 using Tapatalk

Magisk Manager keeps force stopping after update from 17.1 to 18

Hi,
I just updated my Magisk Manager from within the app from v17.1 to v18, and now it keeps force stopping. Logcat output when it crashes is as follows:
Code:
12-11 13:41:05.720 21419 21484 E AndroidRuntime: FATAL EXCEPTION: AsyncTask #3
12-11 13:41:05.720 21419 21484 E AndroidRuntime: Process: com.topjohnwu.magisk, PID: 21419
12-11 13:41:05.720 21419 21484 E AndroidRuntime: java.lang.NullPointerException: Attempt to read from field 'int a.zi.c' on a null object reference
12-11 13:41:05.720 21419 21484 E AndroidRuntime: at a.uv.a(Unknown Source)
12-11 13:41:05.720 21419 21484 E AndroidRuntime: at a.uv.b(Unknown Source)
12-11 13:41:05.720 21419 21484 E AndroidRuntime: at a.uv.lambda$ZFQE15Y-O-EDUdsm62tZ8CmB2-A(Unknown Source)
12-11 13:41:05.720 21419 21484 E AndroidRuntime: at a.-$$Lambda$uv$ZFQE15Y-O-EDUdsm62tZ8CmB2-A.run(lambda)
12-11 13:41:05.720 21419 21484 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
12-11 13:41:05.720 21419 21484 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
12-11 13:41:05.720 21419 21484 E AndroidRuntime: at java.lang.Thread.run(Thread.java:818)
12-11 13:41:05.723 881 3514 W ActivityManager: Force finishing activity com.topjohnwu.magisk/a.b
I tried flashing the v18 zip file and encountered the same problem. Flashing back to v17.1 fixed the problem, haven't tried 17.2 though.
My device is a Nexus 5X running Android 6.0.1.
How do I fix this?

FileProvider Crash

Hi,
I have a problem with file provider of my Redmi.
Some app can not share file beetween other app and the activity crash.
Can you help me?
Thanks.
P.S.
Below some piece of logcat
01-13 23:20:29.945 15457 15457 E AndroidRuntime: FATAL EXCEPTION: main
01-13 23:20:29.945 15457 15457 E AndroidRuntime: Process: system:ui, PID: 15457
01-13 23:20:29.945 15457 15457 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{android/com.android.internal.app.ResolverActivity}: android.os.FileUriExposedException: file:///storage/emulated/0/Android/data/com.speedsoftware.rootexplorer/cache/temp/.retemp_1642112425148/xxx.apk exposed beyond app through Intent.getData()
01-13 23:20:29.945 15457 15457 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3520)
01-13 23:20:29.945 15457 15457 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3692)
01-13 23:20:29.945 15457 15457 E AndroidRuntime: at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:85)
01-13 23:20:29.945 15457 15457 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
01-13 23:20:29.945 15457 15457 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
01-13 23:20:29.945 15457 15457 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2142)
01-13 23:20:29.945 15457 15457 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
01-13 23:20:29.945 15457 15457 E AndroidRuntime: at android.os.Looper.loop(Looper.java:236)
01-13 23:20:29.945 15457 15457 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7864)
01-13 23:20:29.945 15457 15457 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-13 23:20:29.945 15457 15457 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:620)
01-13 23:20:29.945 15457 15457 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1011)

Question [Xiaomi 12 Pro] System Launcher - Launcher crashes when trying to change search bar provider

Hi, I've recently installed MIUI EEA on my Xiaomi 12 Pro and I've tried changing the search bar provider to Sesame.
When I'm trying to click on the setting it just crashes without a message so I've searched for the crash in the logs, here's what I found.
Code:
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: FATAL EXCEPTION: main
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: Process: com.miui.home, PID: 15821
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=eu.xiaomi.ext.intent.action.SEARCH_BAR_APP }
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2087)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.app.Instrumentation.execStartActivity(Instrumentation.java:1747)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.app.Activity.startActivityForResult(Activity.java:5532)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:597)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.app.Activity.startActivityForResult(Activity.java:5485)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:583)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.app.Activity.startActivity(Activity.java:5891)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.app.Activity.startActivity(Activity.java:5844)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at androidx.preference.Preference.performClick(Preference.java:1199)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at androidx.preference.Preference.performClick(Preference.java:1166)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at androidx.preference.Preference$1.onClick(Preference.java:181)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.view.View.performClick(View.java:7750)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.view.View.performClickInternal(View.java:7727)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.view.View.access$3700(View.java:861)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.view.View$PerformClick.run(View.java:29133)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:210)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.os.Looper.loop(Looper.java:299)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8108)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:556)
2022-08-20 18:44:49.317 15821 15821 com.miui.home E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1045)
[Lines 107 - 132, complete logcat of System Launcher is attached]
I'm running on the latest EEU version (13.0.19 Stable SLBEUXM)
{
"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"
}

G5s+: Failed to generate attestation certificate chain

Hello,
I'm using ArrowOs to run the Munich's local transport's app "MVG Fahrinfo", which allows to buy tickets for the local bus&subway services.
I was able to buy those tickets until at least May 25th, 2022.
I remember, there has been an update to the app, but since I needed no ticket, I noticed by end-June, that I could no longer buy tickets. The app just crashed.
Turning on the logging, I'm getting the following error in the log:
Code:
07-13 07:33:35.097 8070 8092 D TransportRuntime.JobInfoScheduler: Scheduling upload for context TransportContext(cct, HIGHEST, MSRodHRwczovL2NyYXNobHl0aWNzcmVwb3J0cy1wYS5nb29nbGVhcGlzLmNvbS92MS9maXJlbG9nL2xlZ2FjeS9iYXRjaGxvZ1xBSXphU3lCcnBTWVQ0RkZMMDlyZUhKaTZIOUZZZGVpU25VVE92Mk0=) with jobId=1899902110 in 1000ms(Backend next call timestamp 1657115477558). Attempt 1
--------- beginning of crash
07-13 07:33:35.113 8070 8070 E AndroidRuntime: FATAL EXCEPTION: main
07-13 07:33:35.113 8070 8070 E AndroidRuntime: Process: de.swm.mvgfahrinfo.muenchen, PID: 8070
07-13 07:33:35.113 8070 8070 E AndroidRuntime: java.security.ProviderException: Failed to generate attestation certificate chain
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.security.keystore.AndroidKeyStoreKeyPairGeneratorSpi.getAttestationChain(AndroidKeyStoreKeyPairGeneratorSpi.java:611)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.security.keystore.AndroidKeyStoreKeyPairGeneratorSpi.createCertificateChain(AndroidKeyStoreKeyPairGeneratorSpi.java:498)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.security.keystore.AndroidKeyStoreKeyPairGeneratorSpi.generateKeyPair(AndroidKeyStoreKeyPairGeneratorSpi.java:475)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at java.security.KeyPairGenerator$Delegate.generateKeyPair(KeyPairGenerator.java:727)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at b.b(Unknown Source:28)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at c$a.invokeSuspend(SourceFile:6)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(SourceFile:4)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at kotlinx.coroutines.DispatchedTask.run(SourceFile:22)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7665)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:594)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: Caused by: android.security.KeyStoreException: Not implemented
07-13 07:33:35.113 8070 8070 E AndroidRuntime: at android.security.KeyStore.getKeyStoreException(KeyStore.java:1306)
07-13 07:33:35.113 8070 8070 E AndroidRuntime: ... 15 more
07-13 07:33:35.116 2534 9249 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
07-13 07:33:35.117 2534 6885 W ActivityTaskManager: Force finishing activity de.swm.mvgfahrinfo.muenchen/.mobilityticketing.MobilityTicketingActivity
07-13 07:33:35.120 2534 9249 W DropBoxManagerService: Dropping: data_app_crash (1578 > 0 bytes)
I have another sanders phone, which has the same problem.
Today, I've reverted one of those phones to stock Oreo, and there I could buy a ticket successfully. But updating the phone again to an ArrowOs version (Offical of January 2022), which allowed to buy a ticket in January (I still have the receipt...), leads to the problem again.
So my guess is: the app got changed, such that it now requests something, that leads to the error. Using it on an older version does not show this error, so it must handle that request differently.
From what I found on XDA and elsewhere was the info, that a key is being requested, that seems to be missing.
Is that correct? Does anybody know, how I can resolve this issue?
Thanks a lot.
kniffte

Categories

Resources