Skip to main content

Recent apps button not working in Launcher

With recent version, I am unable to see the recently opened apps. Suppose I have open chrome, brave, or X apps, I was able to see them when click on Default recent apps button. Now it's goes to default app search or home page.

This is issue not happening if I am switching to my OnePlus Default Launcher.

Manufacturer and Device Name
Android Version
Problem occurs with other Launchers
Third-Party Launchers Tested
Niagara Launcher Version
4 comments

Log in to comment and vote

Comments4

  • Gaga Renanto

    •

    Sep 9, 2025

    •

    Merged request

    •

    1 vote

    Recent Apps and kill tasks

    I couldn't use recent tasks button in my Infinix Hot 20 (XOS based on Android 12), to easily acces or monitor the apps I have used.. And to kill tasks /apps that no longer use…

    Please mke that feature available. Thanks

  • Tamino Fackler

    Team•

    Sep 1, 2025

    Could you please check whether the issue also appears with other third-party launchers? If it does, then the issue is caused by the system rather than Niagara Launcher. That information would be valuable to know.

    • Karolus_Africanus

      •

      Sep 2, 2025

      For me it is the same with at least one other third-party launcher.

      Doesn't happen with MagicOS (Honor phone).

  • Lifell

    •

    Aug 28, 2025

    I have this same issue on a Fairphone 5 (FP5.VT28.C.042.20250623). Android v15, also on v1.14.5 of Niagara.

    For me, it doesn’t return to the home page or default search app. It just does nothing. Unresponsive until I restart the device and then it almost instantly stops working again.

    Seems it’s a global issue on the latest Android versions? Well that’s terrible…
    https://feedback.niagaralauncher.com/p/recent-apps-gesturebutton-not-working-2

    EDIT:

    Seems configuring these developer settings on my Fairphone 5


    "Windows animation scale"
    "Transition animation scale"
    "Animator duration scale"


    To 0.0 or "Animation off" causes the issue for me. Setting it back to "1.0” seems to fix it. Setting it to 0.1 also seems to work through ADB commands but that option isn’t available through the menus.

    adb shell settings put global window_animation_scale 0.1
    adb shell settings put global transition_animation_scale 0.1
    adb shell settings put global animator_duration_scale 0.1

    If you haven’t touched any of the settings this likely won’t work for you.