I posted this possible solution in a two other threads with similar third party launcher issues. It works for third party launchers using 3 button navigation and experiencing issues with the recent button, it's worth trying for your issue as well:
Go into Developer Options and try different "Animator duration scale" settings (try "off," try "0.5x," etc). If that doesn't fix your issue, try playing with other animation settings in Developer Options.
graphie This is not good advice and insecure.
UndercoverBozo How is disabling animations or changing the speed of animations insecure?
UndercoverBozo I don't see how is enabling Developer options insecure (if you don't change things you don't have a clue about). But you can remove animations also by going to Settings > Accessibility > Colour and motion > Remove animations
Thank you all for your comments on this, very much appreciated!
I've given up using Lawnchair and Neo Launcher, as they're both having pretty nasty bugs (home screen layout is completely messed when changing settings, folder backgrounds and other UI elements not being rendered on screen, etc.). They're definitively out.
@User2288 what you describe is exactly the same issue I'm having too. To me the launcher/home screen has to work flawlessly, no lags and hickups tolerating at all, I'd have to force stop and restart it constantly, that's no option.
UndercoverBozo There is 0 reason to support this application, hopefully people will see that sooner than later.
That's my opinion on actual Nova too.
@graphie Thanks for the advice with the animation settings. I've animations generally off, so that didn't help. I'll try the animation duration scaling, would be great if it helps...!
UndercoverBozo This is not good advice and insecure.
Dev options can be set individually with adb, isn't it? So no need to enable dev options permanently...?
TRInvictus To me the launcher/home screen has to work flawlessly, no lags and hickups tolerating at all, I'd have to force stop and restart it constantly, that's no option.
I'd say before you move on at least give it a try. Like I said for me this is not constant, its a rare and occasional issue. Given that no good alternatives exist I'd say give it a try first. But if its too much trouble then go back to default launcher. The thing is we are living in a world of varying degrees of discomfort. Find out which option gives you less discomfort, and don't eliminate your options too soon. You don't have many.
Ultimately your call friend 😊. Just helpin.
User2288 Any help, or comments, always very much appreciated my friend 😃
Rate of discomfort is actually very high on any option, the home screen and recents is where everything starts and happens while using the phone from A to the Z, its not just a tool one randomly uses, its the phone actually.
@ GOS
Is there a way we can help nailing issues down with 3rd party launchers, if you plan on doing investigations? It seems to be a persistent issue to quite some users.
Ok guys, I think I have found something. Logs of Launcher3, yes the stock launcher, not the 3rd party launcher, throws the following exception when I swipe up to the recents screen and getting a blank black screen instead. (I assume the stock launcher is still running in the background due to "quickstep" or something similar...?)
`type: logcat
osVersion: google/husky/husky:14/AP1A.240505.005/2024050700:user/release-keys
packageName: com.android.launcher3:34
buffers: main,system,crash,events,kernel
level: error
--------- beginning of main
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: RecentsView destination page is invalid
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: java.lang.IllegalStateException
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.quickstep.AbsSwipeUpHandler.handleNormalGestureEnd(AbsSwipeUpHandler.java:1381)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.quickstep.AbsSwipeUpHandler.lambda$onGestureEnded$14(AbsSwipeUpHandler.java:1108)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.quickstep.AbsSwipeUpHandler.$r8$lambda$GUlUNPxlN5wUIt1E4ajyapS2w5Y(Unknown Source:0)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.quickstep.AbsSwipeUpHandler$$ExternalSyntheticLambda58.run(D8$$SyntheticClass:0)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.launcher3.PagedView.onPageScrollsInitialized(PagedView.java:715)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.launcher3.PagedView.runOnPageScrollsInitialized(PagedView.java:709)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.quickstep.AbsSwipeUpHandler.onGestureEnded(AbsSwipeUpHandler.java:1111)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.quickstep.inputconsumers.OtherActivityInputConsumer.finishTouchTracking(OtherActivityInputConsumer.java:444)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.quickstep.inputconsumers.OtherActivityInputConsumer.onMotionEvent(OtherActivityInputConsumer.java:376)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.quickstep.inputconsumers.NavHandleLongPressInputConsumer.onMotionEvent(NavHandleLongPressInputConsumer.java:92)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.quickstep.inputconsumers.OneHandedModeInputConsumer.onMotionEvent(OneHandedModeInputConsumer.java:138)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.quickstep.TouchInteractionService.onInputEvent(TouchInteractionService.java:840)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.quickstep.TouchInteractionService.$r8$lambda$JDK2db7a_ZtzI6D1EJ5hYukunXo(Unknown Source:0)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.quickstep.TouchInteractionService$$ExternalSyntheticLambda5.onInputEvent(D8$$SyntheticClass:0)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.systemui.shared.system.InputChannelCompat$InputEventReceiver$1.onInputEvent(InputChannelCompat.java:74)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:267)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at android.os.MessageQueue.nativePollOnce(Native Method)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at android.os.MessageQueue.next(MessageQueue.java:344)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at android.os.Looper.loopOnce(Looper.java:189)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at android.os.Looper.loop(Looper.java:317)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at android.app.ActivityThread.main(ActivityThread.java:8532)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at java.lang.reflect.Method.invoke(Native Method)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.internal.os.ExecInit.main(ExecInit.java:50)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
05-17 09:24:41.674 2490 2490 E AbsSwipeUpHandler: at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:359)
`
@GOS Could you please check this? I am having this issue since months, would be great, thank you very much and best regards.
It's not a GrapheneOS issue. We didn't change anything which could have caused this.
GrapheneOS I do not know who is responsible and could help to fix that. Is it Google to check this, as Launcher3 is Google's? I am in the situation that I avoid using my Pixel 8 Pro since month, and keep using my old Andorid 10 phone which is unpatched since years (!), because 3rd party launchers do seem to not run propertly on GOS (I have tried a lot of em and they all show the same issue). I'm not pointing with the finger to GOS or anyone else, I am just looking for help. I ask for help since several month in this matter and do the best I can do by investigate and provide informations myself, with the very limited knowledge and possibilties I have. What else can I do?
I know this doesn't really help you, but I have no issues like the one you are facing using Lawnchair 14.
Vagabond8630 I know this doesn't really help you, but I have no issues like the one you are facing using Lawnchair 14.
Thank you for your feedback. Which version are you using exactly? Owner profile only, or other profiles as well? The last tests I did with Lawnchair was some weeks/month ago and had the described issue (as well as a couple of other 3rd party launchers too). Lawnchair honestly isn't on my list anymore, as changing settings completely messed up the whole home screen (widgets gone, layout gone).
Is split screen working with Lawnchair? When I use split screen with a 3rd party launcher, I get a crash too in launcher3. Same issue, using a 3rd party launcher, but the stock launcher crashed in background (quickstep?).
Have tons of issues as well with O launcher, freezes every now and than, sometimes app drawer does not open and you have to force stop launcher app for some reason in settings.
TRInvictus Which version are you using exactly? Owner profile only, or other profiles as well?
I've been with Lawnchair 14 Beta 2 since they released it (Apr-3) and no issues. And yes, split screen works.
I use it in the Owner profile only with no fancy features enabled.
I'm on the nightly version, and I have no such updates as the ones that you are seeing.
Owner profile only, and changing the settings does not impact my setup. If you are afraid of your home set up breaking, Lawnchair has a backup feature, so you can create a backup of your homescreen before making any changes.
Also no issues using split screen in Lawnchair.
One "issue" that I have with Lawnchair is that Lawnchair's Home settings menu is like 30fps and is super slow, which is jarring to see after getting used to the 120hz high refresh screen. But nothing breaks, and all the menus all work, so it's only a cosmetic issue.
Thank you all for sharing your experiences, very much appreciated.
Oggyo I've been with Lawnchair 14 Beta 2
Tried that release now too, but still the same issue, black screen now and then, and an exception in Launcher3.
Vagabond8630 Owner profile only, and changing the settings does not impact my setup
When I add a row/column to the home screen, or to the dock, for example, the complete home screen is reset and messed up. I'd say ok that this happen when removing a row (as there might not be enough space left), but adding one, or even add one more icon to the dock, that mess should not happen :-(
Vagabond8630 Also no issues using split screen in Lawnchair.
Oggyo And yes, split screen works.
Good that you mention that, I get an exception when using split screen. Happens with other 3rd party launchers too.
May I kindly ask which device you're running GOS on?
I'm on a Pixel 8 Pro. Maybe there's an incosistency in the implementation of Launcher3 not causing issues on every Pixel....?
Anyhow, I'm desperate. Tried so many launchers, same issue since month. Repeating myself, using the phone is a pain, exposing myself to risks by keeping my holey Android 10 for everyday-use.
What shall I do? Reset, re-flash the phone? Loosing everything I set up carefully, with zero guarantee for success?
Launcher3 is part of the system, I cannot imaging how I messed that up, making it that "bitchy" versus 3rd party launchers?
Any advices? Thank you
