I am unable to utilise split screen mode with 3rd-party launchers

Help Fairphone 5
, , ,
1

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.

2

I can use split screen without issues when testing (dont use it normally) with various apps incl WA B, however I dont use Logfox or Droidify.

1 Like
3

I seem to have no trouble splitting them.
But I did just download them for the purpose of this test. Maybe something breaks if you use them harder?

Screenshot_20250425-164835
Screenshot_20250425-1648351224×2700 154 KB

Screenshot_20250425-164941
Screenshot_20250425-1649411224×2700 210 KB

4

@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.

1 Like
5

I’m gonna get to the bottom of this:

  1. xdaforums.com/t/how-do-i-debug-a-debuggable-app-on-a-physical-phone-over-usb-with-windows-developer-options-debugging-is-turned-on-but-what-do-i-do-next.4674852/#post-90067516

  2. android.stackexchange.com/q/260306 [1]

  1. android.stackexchange.com/revisions/260306/1 ↩︎

6

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?

1 Like
7

@Nabalazs, OEM unlocking being disabled enables Verified Boot, which helps. I did some rudimentary searching, and there weren’t any satisfying answers:

  1. reddit.com/r/AndroidQuestions/comments/pvtqeu

  2. xdaforums.com/t/how-to-verify-integrity-of-installed-android-image.3073949

  3. forums.tomsguide.com/threads/is-there-a-way-to-check-the-integrity-of-my-android-os-files.542894/

I’ve located information about verifying the filesystem’s integrity (just treat it like any ext4 one), but that’s improbably the cause:

I’m gonna have to ask this too. Poor Android SE are gonna get sick of me.

9

i have exact (ofcourse not PID :slight_smile: same crash as you if using NovaLauncher,
when i switch to stock launcher, then split work without problem…

EDIT: now also i try some of other 3rd launcher, and same crash as with NovaLauncher

1 Like
10

@k3dAR, ya clever bloke! That fixes it for me, too:

image
image568×1253 111 KB

Reported at support.fairphone.com/hc/en-us/requests/1268276. If anyone else files a request, cite “Request #1268276” (for assistance in triage).

12

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…

  1. xdaforums.com/t/how-do-i-debug-a-debuggable-app-on-a-physical-phone-over-usb-with-windows-developer-options-debugging-is-turned-on-but-what-do-i-do-next.4674852/#post-90070374 ↩︎

13

AS is working now, and I’ve learnt to utilise LLDB. However, I’ve since ascertained that AOSP doesn’t permit debugging installed applications unless their manifest states that they’re debuggable. I’ve no desire to gain superuser access on my installation, because I want to pass Play Integrity, so I shan’t.

I’ve instead submitted this to issuetracker.google.com/issues/423310056, since FP Support hasn’t even bothered to respond. They’ve been of use to me thus far, apparently contacting FP via their product team despite it not being a bug in upstream AOSP.