When I attempt to utilise split screen mode with LogFox 2.0.6 and Droid-ify 0.6.5, it fails, spectacularly. This appears to apply to any combination of applications, though, since I’ve tried Fenix Nightly and WhatsApp Business, too.
Summarily, QuickStep (V14) crashes!
FATAL EXCEPTION: main
Process: com.android.launcher3, PID: 5246
java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.quickstep.views.FloatingTaskView.getBoundsOnScreen(android.graphics.Rect)' on a null object reference
at com.android.quickstep.views.RecentsView.confirmSplitSelect(RecentsView.java:4700)
at com.android.quickstep.views.TaskView.confirmSecondSplitSelectApp(TaskView.java:763)
at com.android.quickstep.views.TaskView.onClick(TaskView.java:747)
at com.android.quickstep.views.TaskView.$r8$lambda$2dErZAYzRAWboZR0vn31kIz_HGY(Unknown Source:0)
at com.android.quickstep.views.TaskView$$ExternalSyntheticLambda2.onClick(Unknown Source:2)
at android.view.View.performClick(View.java:7660)
at android.view.View.performClickInternal(View.java:7637)
at android.view.View.-$$Nest$mperformClickInternal(Unknown Source:0)
at android.view.View$PerformClick.run(View.java:30165)
at android.os.Handler.handleCallback(Handler.java:958)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:294)
at android.app.ActivityThread.main(ActivityThread.java:8223)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:977)
Can anyone reproduce this? It’ll assist me when I attempt to report this to FP’s ZenDesk. I’m using FP5.UT2M.B.113.20250319.
@Nabalazs, it applies to all applications. I’ve now tested it with pretty much every one on my phone, and they all crash QuickStep. Thanks for being so dilligent, though.
If this topic was a steam game, I’d suggest verifying the integrity of files. Does Android have some sort of self repair diagnose feature that checks core system files?
@Nabalazs, OEM unlocking being disabled enables Verified Boot, which helps. I did some rudimentary searching, and there weren’t any satisfying answers:
On that note, I’d like to provide a more useful stack trace, but it’s difficult:
Consequently, if anyone primarily uses Windows and has Android Studio installed, would you tell me whether developer.android.com/studio/debug/index#startdebug[1] is of use in this situation? I don’t have time to switch OSes…