Skip to main content

Home screen stuck open behind app tray

Bug Reports

Home screen stuck open behind app tray

Description:
When I tap the Overview (recent apps) button and then immediately tap Home before the app tray/overview screen finishes appearing, the home screen loads underneath, but the app tray stays stuck on top of it instead of closing. The screen shows both at once — home screen visible behind, app tray still open in front.

Steps to reproduce:
1. Tap the Overview (square) button;
2. Immediately tap the Home (circle) button, before the recent apps screen fully appears;
3. The app tray stays open on screen, with the home screen visibly stuck behind it.


Additional notes:
• Tapping Home again doesn't dismiss the stuck app tray. Though it DOES it make harder to fix the situation.

• The only way out is to tap overview again, which forces you to select an app (you can't back out of it) — selecting any app clears the stuck state.
• If the home button is pressed again, once the bug happens, simply pressing overview again doesn't seem to resolve the issue. In my testing, pressing both buttons and the app tray (random order/number of presses) worked as a way of getting out of the bug then, though I'm unsure of the exact method/order.

Manufacturer and Device Name
Android Version
Problem occurs with other Launchers
Niagara Launcher Version
Posted by Darkkdn ·
1 comment

Log in to comment and vote

Comments1

  • Surfer Bot

    Team•

    Sep 15

    Thanks for the report, the reproduction steps are unusually precise and that helps a lot.

    One thing worth knowing up front: the navigation buttons and the recent apps screen are drawn by the system rather than by Niagara, so a launcher has very little influence over how the overview shows up and goes away. That is spelled out under "Navigation issues" in Commonly reported bugs. It doesn't make what you are seeing any less real, it only changes where the cause is likely to sit.

    Your form says the comparison with another launcher hasn't been tried yet, and that is the single detail that would pin this down: does the same thing happen when another third-party launcher, Nova for example, is set as default? If it does not happen there, that points back at us and is worth digging into. Either way, adding the answer here in the thread is the most useful next step.