Quickstep keeps stopping

Help Fairphone 5
71

@olivierf, if you’ve reproduction steps and a trace like that, Google may accept the bug at their issue tracker. That’s because, luckily (for us), since the recent removal of in-progress source releases for ⪆ A15, we’ve little way to ascertain whether a bug is upstream or downstream (Fairphone)'s fault. Consequently, you should be able to report it directly to them.

However, format it in a semantic manner:

08-13 08:56:19.945 24611 24611 E AndroidRuntime: FATAL EXCEPTION: main
08-13 08:56:19.945 24611 24611 E AndroidRuntime: Process: com.android.launcher3, PID: 24611
08-13 08:56:19.945 24611 24611 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method ‘boolean java.lang.String.contains(java.lang.CharSequence)’ on a null object reference
08-13 08:56:19.945 24611 24611 E AndroidRuntime: at com.android.launcher3.uioverrides.QuickstepLauncher.isOrangeApp(QuickstepLauncher.java:1049)
08-13 08:56:19.945 24611 24611 E AndroidRuntime: at com.android.launcher3.uioverrides.QuickstepLauncher.onStateSetEnd(QuickstepLauncher.java:621)
08-13 08:56:19.945 24611 24611 E AndroidRuntime: at com.android.launcher3.uioverrides.QuickstepLauncher.onStateSetEnd(QuickstepLauncher.java:222)
08-13 08:56:19.945 24611 24611 E AndroidRuntime: at com.android.launcher3.statemanager.StateManager.onStateTransitionEnd(StateManager.java:426)
08-13 08:56:19.945 24611 24611 E AndroidRuntime: at com.android.launcher3.statemanager.StateManager.-$$Nest$monStateTransitionEnd(Unknown Source:0)
08-13 08:56:19.945 24611 24611 E AndroidRuntime: at com.android.launcher3.statemanager.StateManager$1.onAnimationSuccess(StateManager.java:402)

For all others, if you’ve a desire to assist:

  1. Add an A15-compatible logcat --buffer=crash observer, like github.com/F0x1d/LogFox, and authenticate it with Shizuku, so that it’s able to access Quickstep’s logs.

  2. If you choose LogFox, enable its retroactive crash parser.

Afterward, you’ll be able to compare your traces with his. If yours differ in any manner, please post them, because it may indicate that you’re encountering different problems.

Tangentially, what build number are you all on? FP5.VT28.C.042.20250623?