Hi, so I am using this launcher without network for a while now in my Pixel7 and I just love the minimalism and the navigation system with the thumb over a list of icons, just wonderful.

The thing is since the last (given or take) 6 releases the 3 button navigation + Niagara fail, froze and other random stuff that includes lag or slowness or "not flowing" feeling.

Anyone else is experiencing this or similar? I said Pixel7 because my gf is using the same setup on her Pixel5 and she has no issue.

Besides that, anyone knows of another launcher doing this list (with icons) thumb search/selection method?

Thanks in advance

    For a while now, I've also been having various problems with this launcher, lags, freezes, buttons that don't really respond and so on with Pixel 7a.
    Not annoying on a daily basis, it doesn't happen every day, but sometimes it can be annoying.

    gonzalo

    Not since HgLauncher do I recall an iteration with a similar, thumb-driven list of apps. Had a "minimalist" feel with just enough features. So naturally, the app was abandoned shortly after yours truly, here adopted it.

    Features including custom icon packs within the nifty app list AAAND (this is important) the ability to pick an alternate logo if for when your chosen pack inevitably doesn't have dedicated icons created for any particlar apps. Launchers like Rooted Pixel Launcher (a dated example, tbf) that merely apply icons automatically to matching apps -- with no option to manually select them for others -- defeat the entire purpose of custom packs to begin with in most cases.

    I mean, what kind of demented, tortured-soul of a monster would use, say...Arcticons White alongside random, colorful icons?!? I shudder to think, friends.

    Really though, I mention this in case our mighty devs happen to upgrade the standard launcher down the road, themselves (understandably, prob not a priority atm). IMO, the aforementioned implementation along with the ability to simply hide apps from the drawer would satisfy most users.

      25 days later

      This behaviour seems fixed since the last 2 GrapheneOS releases, so far I can't reproduce it anymore. Thanks.