I have e/OS installed on 2 phones. On both I want to use an alternative Launcher.
On the moment that is Kvaesito, but I had the same issue with Discrete launcher.
A few times a day when I want to select an app, the screen freeze.
As workaround I go to settings > apps and stop the laucher app.
Any suggestions?
Try another alternative launcher. No problem for me with KISS launcher, available from F-Droid.
Not sure if related, but I have a pretty similar issue with Lawnchair on 2 phones (Pixel 7a and Fairphone 6).
Few times a day, when I want to unlock my phone, home screen appears but is frozen (can’t open app drawer or open any app)
I juste have to lock and unlock again (sometimes twice) to get it working normally.
I already had this issue on Android 14, and found a related open issue upstream on LineageOS, and I hoped that the upgrade to A15 would solve it…however even if it seems to happen less frequently, I still have this bug 
Haven’t searched if an issue still exists upstream though
@Baziluz Sounds pretty simalar to me.
Do you have a link tot that issue?
The same happens to me since /e/OS v3.1 or 3.2 with FOSSify launcher - sometimes it doesn’t react to swipe up.
Locking the phone by pressing the power button and unlocking via fingerprint sensor makes everything work again.
I will trie your handling when it happens. See or my phone reacts the same.
The alternative launchers do have a dependency on Bliss Launcher to enable switching. I has been found on occasion to Clear storage in Bliss Launcher will fix certain issues.
Well I just tried to find it without success… I might not use the proper keywords for the search on their Gitlab. The first time I found it after lots of research about that issue, and eventually saw it following one link after another 
As @aibd said, clearing cache and/or storage on Bliss Launcher helps for some time, but the bug comes back after a while, so not a permanent fix I’m afraid
For what it’s worth I’ve used both Fossify and Lawnchair on my Teracube. Fossify occasionally bugged, but I kind of expected that with where development is. It was by no means unuseable though.
Both solutions mentioned in the topic worked on my phones. But the issue comes eventuelly back.
It seems I have to get used to it.
Thanks for the advices.